this post was submitted on 25 Jun 2023
437 points (100.0% liked)
/kbin meta
110 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If possible what I've seen help very much is to have a second person join on as being the "ticket review guy." That person will act as a community manager and really won't do that much coding. Usually they'll have a technical background and will understand the code they're reading in pull requests, but for the most part they're there to allow the primary code writer to focus on writing big features and executing core vision while the community at large contributes fixes, tweaks, and features that hadn't been baked into the core vision