On Mon, Dec 17, 2012 at 4:35 PM, Dirkjan Ochtman <d...@gentoo.org> wrote: > On Mon, Dec 17, 2012 at 7:32 PM, Roy Bamford <neddyseag...@gentoo.org> wrote: >> Suppose the team in [1] above wrote the specification, who needs to >> agree it? >> > > I don't think the whole body of devs has to agree to it. The trustees > definitely have to, since they have to fork over the cash. The council > probably also makes sense.
Most logical thing is for the website team to get together and suggest something, and then can work with the rest of the devs to gather input as they see fit. They can then put together a proposal for the trustees. Generally speaking as long as the website team has done reasonable due diligence we aren't going to shoot holes in it. That would be about as productive as getting into a debate with the infra team about how many data centers we want to have hardware in, etc. Those who care should step up and join the appropriate project. Those who don't care that much should try not to get in the way in the name of offering advice. The biggest thing the trustees are likely to help with are ensuring we've done due diligence around bids/etc. Generally funding requests involve all of a few emails and a vote - this should be no different as we shouldn't be contemplating some $20k development project. > > Is the website team actually active these days? I think that should be our focus. Rather than just going back and forth about all the wonderful things that could happen if somebody actually cared about our website, we need people to actually step up and be willing to do something about it. Our website is at least functional for the moment. It certainly could be better, but it takes more than dollars to make that happen. We can't pay people to care. Rich
