MongoEngine / MongoEngine/mongoengine
Is the wiki helping for managing/planning the mongoengine repository?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 11
Description
To all the maintainers @MongoEngine/mongoengine and all the passionated contributors:
We have seen some problems in maintaining mongoengine last year and part of that is the suboptimal communication. On the dev group (https://groups.google.com/forum/#!forum/mongoengine-dev), it works very poorly, very few people seem to use it (though the subscription tuning is very powerful) and in the list of issues on Github, it quickly gets flooded by the current number of open issues.
This is why I want to ask your opinion about activating the wiki on this repository. We should limit its content to the minimum required, but I think it could be nice for:
- roadmap
- bigger refactoring
- prototype/alpha/imprecise ideas
Contributor guide
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
No files, tests, or entry points are identified. Start by reviewing the proposed wiki use cases—roadmap, bigger refactoring, and prototype or imprecise ideas—and determine whether maintainers want to activate the wiki and what minimum content it should contain.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100