indygreg / indygreg/PyOxidizer
Move project to GitHub organization?
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Many open source projects exist as their own top-level GitHub organization, detached from their primary author. It might make sense to do this for PyOxidizer.
I'm filing this issue to track exploring that.
While I'm pretty familiar with how GitHub organizations behave on a technical level, this isn't something I've considered for a personal open source project before. If there are any resources outlining the pros and cons of transitioning an open source project to organizational ownership, I'd love to read up!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing GitHub’s documentation on organization ownership and resources comparing organizational versus personal ownership of open source projects. Summarize the relevant pros and cons for PyOxidizer, then use that comparison to decide whether moving the project is appropriate; this issue does not identify any files or tests to change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100