makeplane / makeplane/plane-python-sdk
Question: potential org adoption/transfer of plane-cli
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 24
- Avg merge
- 8d 9h
- Merged PRs (30d)
- 2
Description
Maintainers question: would Makeplane consider taking plane-cli under the company/org?
Hi team,
Separate from feature discussion, I wanted to ask about ownership/maintenance.
I created plane-cli here: https://github.com/jzakirov/plane-cli
Would Makeplane be open to taking this repository under the company umbrella (transfer to your org), if you find it useful?
I’m open to:
- transfer to
makeplane/* - shared maintainer model
- contributor/maintainer role while aligning with your standards
If that’s interesting, I can also prepare:
- roadmap/proposal
- release process notes
- test coverage + CI cleanup for handover
Thank you.
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 by reviewing the linked plane-cli repository and this issue's ownership proposals; no implementation files, tests, or entry points are named here. Done would require a maintainer decision about organizational transfer, shared maintenance, or contributor alignment rather than a defined code change.
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
- 15/100