https://github.com/RadioAstronomySoftwareGroup/pyuvdata
Revision 844ecbdff755561cfb463edbd64e37f5408d9447 authored by Matthew Kolopanis on 07 June 2022, 16:04:50 UTC, committed by Bryna Hazelton on 07 June 2022, 20:39:37 UTC
try using micromamba in circleci

set micromamba to the /bin

put micromamba in home, add home to path

give tar output directory

extract to / instead

give -C before file

sudo tar

remove duplicate --name

remove docker declaration from doctest

delete unnecessary line

have doctest run on ubuntu

use login shell; try to init

add init after the install

replace pathing with evals because those are fun

some dangling ./bin's

try using micromamba docker

explicit - in image

no sudo

remove install gcc g++ curl installs

install gcc and gxx from conda

install gcc and gxx into environment

add executor, add shebang to ci config script

remove hanging docker tab

remove pipefail from shell script

add set back

try ignoring bash script

try initing the shell early

different mamba config

set entrypoint for docker image

try using build int activate shell script

try explicitly activating again

source the activate script

explicitly declare -n 2 for xdist

return to the linux macine, add activate env script to repo


use which not an env variable for activate script
1 parent d91c7a3
Raw File
Tip revision: 844ecbdff755561cfb463edbd64e37f5408d9447 authored by Matthew Kolopanis on 07 June 2022, 16:04:50 UTC
change setup-miniconda to use mamba instead
Tip revision: 844ecbd
CODE_OF_CONDUCT.md
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal
appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
  advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
  address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the RASG managers at [rasgmanagers@gmail.com](mailto:rasgmanagers@gmail.com).
The list of managers who will receive the email is in the [readme](README.md).
To report an issue involving any of the managers, you can email any subset of the managers directly.

All complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The RASG managers are
obligated to maintain confidentiality with regard to the reporter of an incident.

Project maintainers or contributors who do not follow or enforce the Code of
Conduct in good faith may be temporary or permanently removed from the project
team or blocked from RASG repositories, Slack channels or telecons.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
back to top