9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: pmarin <pmarin.mail@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Closed nix development is an insult
Date: Sat,  7 Sep 2013 08:24:37 +0200	[thread overview]
Message-ID: <CAOe8CcbK2XbREt0Nu5f5QmQ3=RL3-9SET2vycsOeXvND0nFNMg@mail.gmail.com> (raw)
In-Reply-To: <CAJQxxw=dmehpWt-OYFOwvebXa0_mL1znK5GqteGErayq3Nsoww@mail.gmail.com>

I thought all the discussion of how the development process should be
more open ended with the creation of 9front.
For me one of the best things about 9front is that I can follow all
the changes in the code by reading their mailing list.

pmarin

On Sat, Sep 7, 2013 at 6:36 AM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> I don't really understand this thread. I thought it was a stupid flame war,
> in which case I can only say that I miss Boyd calling a spade a fucking
> shovel.
>
> I was disturbed by the claim that v10 had been lost because of bullshit, but
> said nothing.
>
> If indeed someone has lost their v10 I can replace it. If you are in
> australia it's easy. Contact me with the details of your import license and
> I will arrange for a copy on TK50 for you. I'm not allowed to
> export/sell/destroy it so I'm stuck with it. Nearly all of cmd is on the web
> anyway!
>
> And a complete rack of plan9 servers is a lot quieter, faster, and uses lest
> power than my Vax.
>
> But I digress, voting nemo Plan9 innovator of the month. Shoot me.
>
> brucee
>
>
> On 7 September 2013 14:06, Devon H. O'Dell <devon.odell@gmail.com> wrote:
>>
>> 2013/9/6 erik quanstrom <quanstro@quanstro.net>:
>> >> > I created it I do what I want with it.
>> >>
>> >> I believe the rules are different when the work is research, sponsored
>> >> by public money. People are getting research grants to work on nix.
>> >
>> > who is getting grants to work on nix?
>> >
>> >> > as far as i know, there is no private nix development going on
>> >>
>> >> Who are you kidding. This is the norm around here. I have been
>> >> personally invited in multiple private Plan 9-related projects by some
>> >> of the few proemiment members of this community that still write code.
>> >> This has always been the norm; read 15 year old 9fans posts and find
>> >> that the same attitude (and complaints) prevail.
>> >
>> > i'm not sure if you're complaining or bragging.
>> >
>> > but anyway, we're talking about current nix (which i take to mean
>> > current 64-bit intel/amd development of any sort).
>> >
>> > so have you been invited to participate in private nix development?
>>
>> I've been invited. I'm too busy, and I feel like a dick, because I
>> think it'd be a lot of fun. I'm happy that people are contributing.
>>
>> But I do wish that this list and the software produced by the people
>> on it was more transparent. I'm sure nobody likes bitbucket or github
>> here, but I'm pretty sure everyone would be happy with a 9p mount of
>> ongoing development. It's amazing what commented changesets do for
>> software engineering in organizations (public or private) to quell
>> worries about those projects.
>>
>> --dho
>>
>> > - erik
>> >
>>
>



  reply	other threads:[~2013-09-07  6:24 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 22:13 Aram Hăvărneanu
2013-09-05 22:35 ` erik quanstrom
2013-09-06  8:49   ` Richard Miller
2013-09-06  9:52     ` Francisco J Ballesteros
2013-09-06 10:24       ` hiro
2013-09-05 22:36 ` Francisco J Ballesteros
2013-09-05 23:07   ` Kurt H Maier
2013-09-06  8:27     ` Steve Simon
2013-09-06 22:59       ` BurnZeZ
2013-09-06 23:00       ` Francisco J Ballesteros
2013-09-07 19:15         ` Christopher Nielsen
2013-09-06 23:10       ` Kurt H Maier
2013-09-06 23:35       ` Aram Hăvărneanu
2013-09-06 23:42         ` Nemo
2013-09-07  2:49         ` erik quanstrom
2013-09-07  4:06           ` Devon H. O'Dell
2013-09-07  4:36             ` Bruce Ellis
2013-09-07  6:24               ` pmarin [this message]
2013-09-07 13:21               ` Kurt H Maier
2013-09-07 13:28                 ` Bruce Ellis
2013-09-07 13:33                   ` Kurt H Maier
2013-09-07 13:41                     ` Bruce Ellis
2013-09-07 13:56                       ` Aram Hăvărneanu
2013-09-07 14:32                         ` Bruce Ellis
2013-09-07 14:52                         ` Latchesar Ionkov
2013-09-07 16:28                         ` erik quanstrom
2013-09-07 17:01                           ` Latchesar Ionkov
2013-09-07 17:48                         ` Gorka Guardiola
2013-09-07 20:46                         ` Charles Forsyth
2013-09-07 23:47                           ` Matthew Veety
2013-09-08  0:19                             ` Charles Forsyth
2013-09-08  7:00                               ` Bruce Ellis
2013-09-07 14:58           ` Anthony Sorace
2013-09-07 15:05             ` Bruce Ellis
2013-09-07 15:14             ` tlaronde
2013-09-07 15:46               ` lucio
2013-09-07 16:06                 ` tlaronde
2013-09-07 16:40                   ` lucio
2013-09-07 16:56                     ` Ethan Grammatikidis
2013-09-07 17:45                       ` lucio
2013-09-07 17:50                         ` lucio
2013-09-07 16:57                     ` tlaronde
2013-09-07 16:35         ` Ethan Grammatikidis
2013-09-06 23:48 Terry Wendt

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='CAOe8CcbK2XbREt0Nu5f5QmQ3=RL3-9SET2vycsOeXvND0nFNMg@mail.gmail.com' \
    --to=pmarin.mail@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).