Re: Technical committee workflow
* Ian Jackson (firstname.lastname@example.org) [090106 01:24]:
> Andreas Barth writes ("Re: Technical committee workflow"):
> > Ian Jackson (email@example.com) [081231 18:20]:
> > > * The Rapporteur discusses the issue - off the main TC list - with
> > > the various parties. debian-devel might be a good place, with
> > > an initial CC to other lists and the bug of course. Other TC
> > > members could participate there if they had time available.
> > > Other Developers could show their usefulness as future TC
> > > candidates by their contributions to these discussions.
> > I'd like to see the discussion either on list or in the relevant bug
> > report(s) so that other people can follow the discussion if needed. (Or
> > re-read it, or whatever.)
> I think it would be sufficient to have a note in the bug giving the
> discussion title in debian-devel, and to have the debian-devel thread
> have the bug number. We can use the debian-devel archives to review
> if necessary.
"On list" didn't mean "On tech ctte", but "on a public debian list" -
whichever that is. (If a disagreement is between python-team-members,
d-python could be the right one as well.)
Oh, and we should fix the off-by-one-bug on number of votes for