trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2012

Re: [trinity-devel] Plan B

From: /dev/ammo42 <mickeytintincolle@...>
Date: Sat, 18 Feb 2012 02:40:35 +0100
On Thu, 16 Feb 2012 21:34:42 -0800 (PST)
Darrell Anderson <humanreadable@...> wrote:

> Let me rephrase: if Tim became unavailable for a long period or
> forever, do we have a plan in place to continue the project or does
> Trinity fizzle away without Tim?
I just did a partial clone of Trinity repositories on my Gitorious
account. As of now, the purpose of the repo is to concentrate
Slackware-specific (or rather not-Debian-specific ?) development. I have
uploaded tdebase and tdelibs, but I won't upload all the repositories
because Gitorious' Terms of Service won't let there be more than 500
MB/mo of bandwith without impunity (although I'm not sure there has to
be extensive bandwith beyond my initial uploads; perhaps the big
downloads can all be made from trinitydesktop.org, but still pure
Slackware users/packagers who want to use the repo will just "git
clone" from gitorious).
Are there other repositories where there are especially many Slackware
patches ?
Anyway as of now, I did neither attempt to build the repo on Slackware,
nor put any patch on it, so it is useless. I just wanted to set up the
foundations :)
The URL of the repositories (grouped as a "project" in Gitorious terms)
is https://www.gitorious.org/trinity-slackware .
And I forgot the important part: since I am the admin of these repos I
can grant you (or any other Slackware developer :)) commit rights,
without wrecking havoc in Tim's official repos.