9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ports duplication
Date: Sun,  7 Mar 2010 14:02:39 -0600	[thread overview]
Message-ID: <F45D676E-632D-41BA-A60E-765DE72F4A9E@gmail.com> (raw)
In-Reply-To: <4d33d2aa22b5c83c1e4348c73d008097@yyc.orthanc.ca>

Augment the contrib tools (or a fork or facsimile thereof) to including user-defined rankings and reviews.  Forks and duplication sometimes make sense, sometimes they don't -- but the better versions will percolate to the top.

Its a community driven thing, we need the right tools to enable that.

     -eric


On Mar 7, 2010, at 1:49 PM, Lyndon Nerenberg (VE6BBM/VE7TFX) wrote:

> I really think this idea that duplication of things in contrib is bad,
> is bad (or just a red herring).
> 
> For ports of big applications (python, say), the amount of work involved
> is going to self-limit the number of ports right up front. And the ones
> that do make it will self-select based on the quality of the port.
> 
> As for the smaller things, I would prefer to see ten different bits of
> code that achieve the same end vs. just one. Diversity is good, and a
> broader selection of code gives a bigger field to mine for ideas and
> concepts.
> 
> --lyndon
> 
> 
> 




  reply	other threads:[~2010-03-07 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-07 19:49 Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-07 20:02 ` Eric Van Hensbergen [this message]
2010-03-08  4:26 ` lucio
2010-03-08 12:17   ` Iruata Souza

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=F45D676E-632D-41BA-A60E-765DE72F4A9E@gmail.com \
    --to=ericvh@gmail.com \
    --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).