9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] [GSOC] plan9 which arch code to use?
Date: Thu,  8 May 2014 09:45:36 -0400	[thread overview]
Message-ID: <27dd15538e47e44bea054fd0656e7616@mikro.quanstro.net> (raw)

> But maybe, just maybe, if the community can get its act together to
> support a "codereview" type approach, we can ask Coraid to sponsor the
> minimum resources required by it.  I don't have a clue to the details,
> but I would be thrilled to contribute.

i think you're suggesting using some sort of corporate sponsorship as
an implicit endorsement.  endorsements are for polititians.  :-)

9front does have a lightly used review system.

all 9atom patches are submitted through apatch, and all apatches are
sent to sources klammeraffe 9atom punkt org.  apatch/note can be
used by anyone to post comments about a patch.  these comments are
sent to the list.

9atom is currently single committer, with the possibility of delegation
(like linux).  i'd love to delegate parts of the system.  if you want to
bend or replace apatch to your wishes, i'm all for it.  but i won't accept
dependencies on python or external web sites(see postscript)

> (1) Bell Labs are lagging behind 9atom and 9front in support for a lot
> of hardware (old and new), a situation that, by getting progressively
> worse may cause them to drop out of the race altogether and (2) The
> amount of effort and ego bashing required to bring the different
> releases in line is considerable and no one is likely to take such a
> mission on without knowing that, at minimum, the "owners" of the
> various distributions are willingly supportive of such efforts.

for what it's worth, i review all the changes made to plan 9 and 9front
and apply what makes sense.  david actually has a script that automaticly
packages any changes to sources and creates a 9atom patch.  many thanks
to him.

- erik

p.s. i am not using codereview for two reasons.  1.  codereview might be
neat, but for me it brings all the baggage of hg, but most of the good bits
are left out  2.  i don't want to depend on mercurial, hg, and google's
good graces.  (good grief.)  plan 9 is currently self-sufficient, and for me
this is a first-class goal.



             reply	other threads:[~2014-05-08 13:45 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 13:45 erik quanstrom [this message]
2014-05-08 13:55 ` Kurt H Maier
2014-05-08 16:35   ` Jeremy Jackins
2014-05-08 17:16     ` Kurt H Maier
2014-05-08 17:47       ` Jeremy Jackins
  -- strict thread matches above, loose matches on Subject: below --
2014-05-07 23:37 sl
2014-05-07 23:29 sl
2014-05-07 23:42 ` andrey mirtchovski
2014-05-07 22:36 sl
2014-05-07 21:38 sl
2014-05-07 22:32 ` Charles Forsyth
2014-05-07 22:39   ` Bakul Shah
2014-05-08  1:38   ` Kurt H Maier
2014-05-08  8:41     ` Charles Forsyth
2014-05-08 14:06     ` erik quanstrom
2014-05-08 14:14       ` balaji
2014-05-08 14:20         ` Charles Forsyth
2014-05-07 22:46 ` Anthony Sorace
2014-05-07 23:01 ` Charles Forsyth
2014-05-07 23:51   ` erik quanstrom
2014-05-07 20:56 sl
2014-05-07 21:17 ` Anthony Sorace
2014-05-07 21:33   ` Lyndon Nerenberg
2014-05-08 11:57     ` lucio
2014-05-08 12:03       ` erik quanstrom
2014-05-08 12:39         ` lucio
2014-05-07 19:57 sl
2014-05-07 20:06 ` erik quanstrom
2014-05-07 20:11   ` Jacob Todd
2014-05-07 20:19     ` Lyndon Nerenberg
2014-05-08 12:11       ` lucio
2014-05-07 18:56 sl
2014-05-07 19:53 ` erik quanstrom
2014-05-07 18:29 sl
2014-05-07 18:48 ` erik quanstrom
2014-05-08  5:56   ` lucio
2014-05-08  8:58     ` cinap_lenrek
2014-05-08 11:20       ` lucio
2014-05-08 12:07         ` erik quanstrom
2014-05-08 12:46           ` lucio
2014-05-08 13:15             ` Charles Forsyth
2014-05-08 13:48               ` Kurt H Maier
2014-05-08 14:07                 ` lucio
2014-05-08 14:04               ` lucio
2014-05-08 14:15                 ` erik quanstrom
2014-05-08 14:51                   ` lucio
2014-05-08 14:56                     ` Charles Forsyth
2014-05-08 15:16                       ` lucio
2014-05-08 10:55     ` erik quanstrom
2014-05-07  1:14 sl
2014-05-06 21:00 yan cui
2014-05-06 21:33 ` cinap_lenrek
2014-05-06 21:48   ` yan cui
2014-05-06 21:47 ` Charles Forsyth
2014-05-06 21:53   ` yan cui
2014-05-06 21:56   ` Charles Forsyth
2014-05-06 21:59     ` Charles Forsyth
2014-05-06 22:02       ` cinap_lenrek
2014-05-06 22:05       ` Charles Forsyth
2014-05-07  5:14         ` lucio
2014-05-07  5:38           ` David du Colombier
2014-05-07  6:59             ` lucio
2014-05-07  8:38               ` Riddler
2014-05-07  8:59                 ` Charles Forsyth
2014-05-07  9:05             ` erik quanstrom
2014-05-07  9:10               ` Charles Forsyth
2014-05-07  9:16                 ` erik quanstrom
2014-05-07  9:42                 ` erik quanstrom
2014-05-07  9:23               ` David du Colombier
2014-05-07  9:25                 ` erik quanstrom
2014-05-07  9:31             ` David du Colombier
2014-05-07 11:13               ` lucio
2014-05-07 11:30                 ` Charles Forsyth
2014-05-07 14:36                 ` erik quanstrom
2014-05-07 17:51                   ` lucio
2014-05-07 18:22                     ` erik quanstrom
2014-05-08  5:39                       ` lucio
2014-05-07  8:45           ` Charles Forsyth
2014-05-07  9:12             ` erik quanstrom
2014-05-07  9:20               ` Charles Forsyth
2014-05-07  9:21                 ` erik quanstrom
2014-05-07 12:59                 ` Kurt H Maier
2014-05-07 13:36                   ` Charles Forsyth
2014-05-07 14:39                     ` erik quanstrom
2014-05-06 22:09 ` Kurt H Maier
2014-05-07  0:40 ` erik quanstrom
2014-05-07  1:01   ` Charles Forsyth
2014-05-07  1:12     ` Kurt H Maier
2014-05-07  1:39       ` Charles Forsyth

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=27dd15538e47e44bea054fd0656e7616@mikro.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).