From: Francisco J Ballesteros <nemo@lsub.org>
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 01:00:58 +0200 [thread overview]
Message-ID: <DFA497C6-48DA-4B23-A27F-A7A49E74AAEB@lsub.org> (raw)
In-Reply-To: <1a806fac73b7f5d77492e855f816fca4@quintile.net>
I think its almost ready at least to
try and take a look, I will try to
put out a copy next week,
unless other authors ask me not to.
any useful bit for "production" usage
will be shared, anyway, we have always done it
that way.
In short, I agree 100% with Steve.
On Sep 6, 2013, at 10:27 AM, "Steve Simon" <steve@quintile.net> wrote:
>> Aram's point, obviously, is not that working on nix is insulting.
>> Pretending you are a better judge than the whole world on whether
>> something is 'ready to be shared' is insulting. Unless you have
>> lawyers pointing metaophorical guns at your job, in which case just
>> say that.
>
> Good grief, I write lots of code for plan9, only some of which I decide
> is successfull and well written enough to release. This is my choice
> and only mine, I created it I do what I want with it.
>
> I don't believe any different rules apply to nemo.
>
> If somone where to priviately, politely ask him off-line asking
> for a copy of the work in progress he might be willing to share,
> though he might not, I don't know what state this code is in or how
> he feels about what has been written.
>
> Fundamentally I don't understand how people beleive they can complain
> when they don't have access to other peoples private work.
>
> Don't get me wrong, I am all for sharing code but its to authors right
> to decide not to share if they wish.
>
> -Steve
next prev parent reply other threads:[~2013-09-06 23:00 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 [this message]
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
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=DFA497C6-48DA-4B23-A27F-A7A49E74AAEB@lsub.org \
--to=nemo@lsub.org \
--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).