Development Process #61
davemoore-
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm opening this thread to welcome ideas from current and hopeful contributors on how to create a more collaborative development process 🚀
zentity has had a sole contributor since its creation in 2018. My freedom from any process let me focus on building a solid foundation for the concept, code, and messaging of zentity. Steadily its community of users and contributors has grown, creating more demands and more potential for creativity. The time has come to create a collaborative development process, one that taps this creative potential and meets the growing demands of the community, with greater reliability than one person with a day job and family can reasonable deliver.
The ongoing goal of this discussion should be to codify a development process in writing, so that contributors know how best to contribute to the project. Recently I updated the CONTRIBUTING guide, but there is more that should be put into writing. Branching strategies, version policies, testing requirements, the release process, acknowledging contributions, and certainly more. I've followed some unwritten conventions from the beginning, and I can share those to kick off the discussion.
Beta Was this translation helpful? Give feedback.
All reactions