9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dante <subscriptions@posteo.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 Sources Repository
Date: Sat, 19 Jul 2014 13:50:50 +0200	[thread overview]
Message-ID: <1cad9c24011b1a4aaafbb5b11f0accd0@posteo.de> (raw)
In-Reply-To: <CAGMcHPrVUCHuWA_CJEtrYZHMfPaKKnKUXZzepPP3PQ7TpA3bTA@mail.gmail.com>

Hi,

On 19.07.2014 13:20, Riddler wrote:
>> 3. Contrib packages are tied to people; there is no common 
>> repository.
>  >     This leads to the situation where you can't update a package
> of a long gone user.
>  >     Please tell me how many Mercurial packages you can find in 
> Contrib!
> 
> 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 
long_gone_user/project to contrib/project.
As it is now, I have to convince the master to *create* the central 
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 
nightly build for all the stuff.

As I said, the status quo is perfect for a small team, but I doubt that 
is encourages the project to get some traction.

>> I maintain my impression that the Status Quo, though good for a small 
>> 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?
> 
> 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 
important thing is to get support from the current project maintainers 
(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 
current volunteer maintainers is possible.

What do you people think?

Kind Regards,
Dante




  reply	other threads:[~2014-07-19 11:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 13:19 dante
2014-07-18 14:14 ` Aram Hăvărneanu
2014-07-18 14:18 ` cam
2014-07-18 14:36 ` erik quanstrom
2014-07-19  9:31   ` dante
2014-07-19 11:20     ` Riddler
2014-07-19 11:50       ` dante [this message]
2014-07-19 11:49     ` pmarin
2014-07-19 11:51       ` dante
2014-07-19 12:02         ` dante
2014-07-19 19:06           ` Anthony Sorace
2014-07-20  0:12           ` Brian L. Stuart
2014-07-20  7:33             ` dante
2014-07-19 12:03       ` tlaronde
2014-07-19 12:12         ` dante
2014-07-19 14:41     ` erik quanstrom
2014-07-19 15:06       ` dante
2014-07-19 15:11         ` Jacob Todd
2014-07-19 15:49           ` dante
2014-07-19 18:00             ` Kurt H Maier
2014-07-19 23:19               ` Brian L. Stuart
2014-07-19 18:17             ` erik quanstrom
2014-07-19 19:20               ` Christopher Nielsen
2014-07-19 20:13                 ` Aram Hăvărneanu
2014-07-19 22:10               ` dante
2014-07-19 22:30                 ` erik quanstrom
2014-07-20  7:33                   ` dante
2014-07-19 22:54                 ` Brian L. Stuart
2014-07-19 17:31         ` hiro
2014-07-19 17:48           ` dante
2014-07-19 15:03     ` Aram Hăvărneanu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1cad9c24011b1a4aaafbb5b11f0accd0@posteo.de \
    --to=subscriptions@posteo.eu \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).