From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Date: Sat, 19 Jul 2014 13:50:50 +0200 From: dante To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: References: <1fc1c403eaecd8cae89f761a68b0d605@posteo.de> Message-ID: <1cad9c24011b1a4aaafbb5b11f0accd0@posteo.de> User-Agent: Posteo Webmail Subject: Re: [9fans] Plan9 Sources Repository Topicbox-Message-UUID: 065c6fce-ead9-11e9-9d60-3106f5b1d025 Hi, On 19.07.2014 13:20, Riddler wrote: >> 3. Contrib packages are tied to people; there is no common=20 >> repository. > > =C2=A0 =C2=A0 This leads to the situation where you can't update a pac= kage > of a long gone user. > > =C2=A0 =C2=A0 Please tell me how many Mercurial packages you can find = in=20 > Contrib! >=20 > I don't see how a repository would fix this. When the user is gone > you would still lose the only person with write access to the repo. > You would need to fork it. The only difference is now people just copy > it. Well, it takes 1 minute to "hg mv" a project from=20 long_gone_user/project to contrib/project. As it is now, I have to convince the master to *create* the central=20 contrib repository, then to copy the project there etc. Moreover, as the stuff is now spread all around, it is hard to set up a=20 nightly build for all the stuff. As I said, the status quo is perfect for a small team, but I doubt that=20 is encourages the project to get some traction. >> I maintain my impression that the Status Quo, though good for a small=20 >> team, does not allow the project to grow. > > Were there any efforts to change this? > > Or is it a controversial matter and it stays as it is? > > Or is the team indeed so small (or even loosing members), s.t. > that a change won't make sense? >=20 > In the short time I've been here I think its came up twice. So it is > something at least some people are interested in looking at. I'm sure > it will keep coming up. I could help (a bit, time permitting), but I think that the most=20 important thing is to get support from the current project maintainers=20 (the people you submit patches to). This discussion can only be started by the veterans. I think that a solution that does not increase the burden on the=20 current volunteer maintainers is possible. What do you people think? Kind Regards, Dante