Document how the conda.org emails work
- Dominant language
- Python
- Stars
- 13
- Forks
- 15
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 15
Description
### Checklist
- [X] I added a descriptive title
- [X] I searched open requests and couldn't find a duplicate
### What is the idea?
We've started to use the conda.org domain for the Code of Conduct committee, but it's currently maintained by Anaconda IT. This should be documented so the Conda Organization knows how to request changes and/or additional email addresses.
### Why is this needed?
This came up while reviewing https://github.com/conda-incubator/governance/pull/62.
### What should happen?
_No response_
### Additional Context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
No documentation file or entry point is named. Start by reviewing governance PR 62 and determining how Anaconda IT currently manages conda.org email changes and additional addresses. Done means the repository contains clear instructions for the Conda Organization to request and maintain those changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100