On Fri, May 08, 2009 at 10:54:47AM -0700, Zach Welch wrote: > Hi all, > > I hereby solicit opinions for how the OpenOCD community should be run. > > Please reply with your list of policy and process ideas in this thread > (in bullet list form, preferably). Brevity and clarity will make it > easy for your suggestions to be incorporated into any first drafts. > > Please do _not_ reply to others' replies to this thread. If you have > more ideas to add later, reply to your _own_ post and do _not_ address > other posters ideas directly. Copy and paste the ideas you like into > your own original post if you feel the need to "me too"; I want > everyone's individual opinions to be as clear as possible. > > To wit, I do not want this thread to turn into a debate. That will only > impede the consensus process at this time. Instead, this should be a > freestyle session of brainstorming that precedes any actual debate. > No one is wrong; everyone is right. Let us assign those labels later. > > With a public record of the way everyone thinks things should be done, > any one of us can draft a set of policies that represent the majority. > One or more drafts can be presented, the best ideas selected and honed, > and then the community can vote to accept the final document (or not).
- offical source release managed with git. I think using git instead of svn would have prevented most of the recent conflicts (jeffw patches, dick's ft2232 patches, and the in_handler churn). Moreover I think it would have facilitated concurrent development and the eventual merge of all three of these contributions back into the mainline tree. -Mar. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
