Hi,
The following is a draft ballot for comment. The order of the
candidates names was determined by a virtual coin toss.
manoj
==
Voting period starts 00:00:01 UTC on Sunday, March 30th, 2008
On Thu, Mar 27, 2008 at 07:04:09PM +, Ian Jackson wrote:
> Josip Rodin writes ("Re: Technical committee resolution"):
> > Instead, I would suggest to do two things - first, institute a better
> > process, one that doesn't so much focus on intricate stalemates (like the
> > present 6.2 does), bu
Ian Jackson wrote:
> The main symptom of the TC's brokenness is that it is not making
> decisions, or not making them fast enough.
Agreed.
> I haven't heard anyone suggest that the TC is actually making wrong
> decisions.
Well..
#104101: The TCs resolution that kernel sould have VESA fb compi
Ian Jackson wrote:
> The causes seem to include:
Isn't the main cause that the Technical Committee is well, a committee?
(Recall the old saying about many heads and no brain.)
That seems to be the core reason for all the problems you listed.
> I think we could fix these by
>
> * Increasing the
On jeu, 2008-03-27 at 19:06 +, Ian Jackson wrote:
> The main symptom of the TC's brokenness is that it is not making
> decisions, or not making them fast enough. I haven't heard anyone
> suggest that the TC is actually making wrong decisions.
Even the glibc maintainers?
--
.''`.
: :' :
OK, here is a go at some personal observations:
The main symptom of the TC's brokenness is that it is not making
decisions, or not making them fast enough. I haven't heard anyone
suggest that the TC is actually making wrong decisions.
The causes seem to include:
* Some TC members not being ve
Josip Rodin writes ("Re: Technical committee resolution"):
> Instead, I would suggest to do two things - first, institute a better
> process, one that doesn't so much focus on intricate stalemates (like the
> present 6.2 does), but one that focuses on how to generally get things done
> - such as a
7 matches
Mail list logo
