Should Circup move to the CircuitPython Organization?
- Dominant language
- Python
- Stars
- 172
- Forks
- 41
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
@tannewt asked about moving Circup to the CircuitPython organization on Discord and I thought we could track\discuss in an Issue better.
@lesamouraipourpre, @Neradoc and @joedevivo do you have any concerns about making such a move?
It makes sense to me. Feels very much like a tool the community should (does) support.
Please "@" anyone else who should be informed\consulted. ty!
Contributor guide
Research direction
This issue is a discussion about moving Circup to the CircuitPython organization, with no files, tests, or implementation entry point identified. Read the existing comments and confirm whether the organizational move has a decision and what concrete repository changes, if any, are required; done means the decision and ownership are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100