> On Thursday, June 23, 2011 4:18 AM, Jeremiah Foster wrote: > On Tue, Jun 21, 2011 at 11:13 PM, Selbak, Rolla N <[email protected]> > wrote: >> On 6/21/11 9:46 AM, "Andre Klapper" <[email protected]> wrote: >> >>>[Reposting for a second time as I still have not received an answer to >>>this by MeeGo's Release Engineering team in the last two weeks.] >> >> Yes, discussions can happen within the bugzillas themselves, through the >> mailing lists, etc. > > When you say "etc." does this also include closed mailing lists, i.e. > internal corporate mailing lists? If the answer is yes, I might argue > that internal corporate lists stand in stark contrast to how Open > Source projects traditionally work.
Rolla and I both work for Intel. There are no Intel internal corporate MeeGo mail list to use. I've explained it before (more than two weeks ago) and I'll explain it again. When Rolla as Release Engineering lead wants to know which bugs to accept as update blockers, she asks the program managers, via email or voice. The program managers make recommendation based on: 1. Bug priority as reflected by bugzilla and in discussion with project team. 2. Progress toward bug fix as reflected in bugzilla and in discussion with bug assignee 3. Impact to other projects of proposed bug fix as reflected by discussion with bug owner and possibly with other project PM These discussions happen either via email or voice between PM and bug owner, or PM and PM, or PM and RE, one on one, or in project team or CCB meetings. I see mail on the meego mail list all the time about these CCB and Triage bug meetings. Based on the information above the decision is made to accept or reject the bug as an update blocker (by RE and PM). Jeremiah, if you have missed some of this perhaps it is because you have not been attending the project team meetings lately. There is really only one way bugs get fixed in a release or update. Someone submits a patch and a package maintainer reviews and accepts the patch. People using this process will get their bugs fixed. Some patches may langor because there is no active package maintainer. So a volunteer is needed in this case to be package maintainer. No bugs get fixed by folks who just want to have meetings to discuss how things ought to be done or what the priorities ought to be. They only get fixed by people who send patches and people who accept them. >> Release Engineering is currently not looking for new candidates for Meego, >> although we always appreciate feedback and support. > > But that would imply that there is one central decision making body > for Meego and not an open community of decision makers. Is this the > case? Is "Release Engineering" a closed body? The real decision makers are the folks that submit bug fix patches. Even Release Engineering is just a collection of folks that patch and accept patches to the MeeGo code base. Jeremiah, you are part of the Release Engineering closed body. How many patches have you submitted or accepted lately? > > Jeremiah Regards Joel _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
