Re: [rock-user] Announce: T2 2.1.0-alpha
"Tobias C. Rittweiler" <[email protected]> Mon, 4 Oct 2004 20:32:16 +0200
| Newsgroups | gmane.linux.distributions.rock.user,gmane.linux.distributions.rock.devel |
|---|---|
| Message-ID | <[email protected]> |
On Monday, October 4, 2004 at 4:32:35 PM,
Valentin Ziegler <[email protected]> wrote:
> ------------ official T2 NEWS file (2004-10-03) -------------------
>
> At October the 3rd, "German Unification Day", 1:56:48 MEST the "T2" project
> tagged the internal milestone 2.1.0-alpha ("Way to heaven"). [...]
Congratulations!
> "T2" is a community driven fork from the ROCK Linux project which aims at
> simplicity and clean and lightweight implementation instead of adding every
> random feature that comes to someone's mind.
>
> "T2" aims to be open for active maintainers and currently seven (!) people
> have write access to the "T2" Subversion repository (which to our knowledge
> are six people more than a ROCK Linux tree currently has).
Heh. Now this caused a slight amusement, because this is a small oxymoron
to the end of the paragraph above. Aware of that?
> This organization provides for delivery of quick bug and security fixes
> (not relying on a single person in the process), offers a nice
> development climate and does not loose version control on renames (as
> the submaster thing currently does).
Ah, well, that's pretty much all handwaving. I understand that you
probably wanted to get something out and as a consequence actual
substance wasn't likely to be on top of your list. But I *strongly* put
it onto your heart to change that crucially as soon as possible.
What *exactly* was the reason for the fork? What *exactly* do you want
to do better? What *exactly* is your goal? What *exactly* is your long,
mid and short term plan? Etc. ad nauseum.
Because of that I suggest the responsibles to get together for a weekend
and collect and unify what you're actually aiming for. After everyone of
your team has a reasonably clear picture of the whole thing, take the
upcomming two weeks for articulating that picture well to the outside
world.
Right, your topmost priority at this point of time shouldn't be code at
all, but "documentation" in the sense of "program charter". Do that, and
you'll have done at least one thing considerably better than Rock.
And another suggestion: Get it straight (eventually!) what you're doing:
either a build kit or an advanced customizable source-based distribution.
And you'll have the second thing done which step Rock is still missing.
> [...]
>
> Major plans for "T2" 3.0:
>
> * build system rewrite (maybe in C++)
Hehe. Nice joke. :-)
> [List of one-sentence enumeration points]
That's unsubstantial handwaving---and that it is, you should have been
taught so at school.
-- tcr (tcr\@freebits\.de) ``Ho chresim'eidos uch ho poll'eidos sophos''