Document process for name changes across LLVM Services
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
[lnihlen](https://github.com/lnihlen) documented much of the process by doing this herself on the [llvm forums](https://discourse.llvm.org/t/community-o-workshop-us-llvm-dev-meeting-2023/73994/2?u=cishida). It would be great to have this information on a live doc that includes the work it takes, who to follow up with if it requires manual work and if it's a similar process for folks who may only want to e.g. change their email address.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with lnihlen's LLVM forum post linked in the issue and compare it with the current Community.o documentation structure. Document the steps and effort for name changes, identify who handles manual follow-up, and note whether the same process applies to email-address changes. Done means the process is available in a live project document.
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
- Mostly clear
- Newbie friendliness
- 42/100