It allows us to give access only to a list of people. That's good enough to start with. Let's not get too fancy yet.
The problem is that, if we want to get fancier, we have to write all the code ourselves. Which means it'll probably never happen.
True, on the other hand, if it's decided to investigate and implement
something else, the whole project will probably never happen.
Why does that have to be true?
The current explosion of interest and demand for instant activity sounds to me very much like the development team who starts coding as early as possible, instead of designing and planning, because then they seem to be making progress.
The key metric is how quickly it gets finished, not how quickly it gets started. If we spend two weeks investigating and picking the most suitable back-end technology, the worst that could happen is that we end up choosing CVS and so have something usable two weeks later. The best is that we choose something which turns out to be a lot more suitable, and reap gains for the lifetime of the project.
"Mozilla must use the best open source solution to solve a well-understood problem." - Brendan Eich, original Mozilla Roadmap.
Rather taken out of context... he was talking about creating stuff, not actually using it.
He's talking about using GTK, if I remember correctly.
I _particularly_ didn't mention Zope on purpose - in fact, I said "I don't care which one it is", to prevent old Zope issues clouding the picture. It's two years later, an eternity in Internet time. I'm sure both Zope and it's many competitors have improved a lot since we last looked.
But again, if we decide to start looking, we'll be arguing about different systems (no doubt, clouded by much discussion of the Zope incident) for months.
Again, why does that have to be true? Brendan says he supports the iron hand in the velvet glove. So let's look around, make recommendations and have our iron-handed supremo make a decision at a particular deadline.
CVS is part of the problem, but I don't think it's the biggest part.
Even if that's true, that doesn't mean we can't solve that part. If there's a big problem and a small problem, the fact that we have to attack the big one doesn't mean we should do nothing about the smaller one.
Gerv _______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
