I'm not certain about splitting coders into two committees, but your arguments in that direction are compelling. This might come in part because I'm from a sort of crossover background, in that I've done both back and front, so for someone like me I would love a centralized place for all coders. I also find it easier to pass work back and forth, especially on asynchronous web apps. Do you think some kind of two-tier structure would work? A coding committee with front and back subcommittees? Or maybe a coding committee that manages feature development across both teams and maintaining consistent development standards, presiding over front and back end committees that are more focused on volunteer management, community-building, knowledge-sharing, etc. within the expertise groups?
If you are unable to use this captcha for any reason, please contact us by email at firstname.lastname@example.org