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 14:12:48 +0200	[thread overview]
Message-ID: <6510eff66ace16056446e1280057ab43@posteo.de> (raw)
In-Reply-To: <20140719120351.GA798@polynum.com>

Please, be so kind and stop this "Bazaar" thread.

The proposal was to use some maybe more scalable tools while
maintaining the current responsibilities.
This could allow for more contributions to be done with the same burden
for the maintainers.

An example for what it's worth could be OpenBSD.
They have AFAIK a central package system with a couple of maintainers
and nightly builds and many-many contributors.

Not Linux. Linux is nowadays so complex that no one can understand the
whole kernel.
Linux is IMHO way too lax about new, orthogonal interfaces,
functionality overlap and rewriting in a different flavour.

Kind Regards,
Dante


On 19.07.2014 14:03, tlaronde@polynum.com wrote:
> On Sat, Jul 19, 2014 at 01:49:10PM +0200, pmarin wrote:
>>
>> Plan9 in general doesn't follow the Bazaar model ( the current usual
>> way of doing things ).
>>
> The Bazaar model is the one for not doing or undoing.
>
> Small is beautiful. The attraction for Plan9 is its consistency and
> size.
>
> As far as I'm concerned, the current organization is not a drawback
> from contributing more---time is. Another organization will not
> offer, for me, more opportunity to contribute. When I have something
> to contribute (and for now, this is only user level kerTeX), nothing
> impeds me from doing.
>
> This is for user level.
>
> For kernel, the problems may be more involved. But clearly, the number
> of persons able to contribute is far more limited. And consistency
> shall
> be the primary aim. So an organization good for a "small team" is an
> organization good for kernel level.
>
> My 1 cent,
> --
>         Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
>                       http://www.kergis.com/
>               http://www.renaissance-francaise.fr/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2014-07-19 12:12 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
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 [this message]
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=6510eff66ace16056446e1280057ab43@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).