9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Latchesar Ionkov <lucho@ionkov.net>
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:52:06 -0600	[thread overview]
Message-ID: <CAOha14xbA6zQEitXq0z3dcoftR2oOD8r5C_RA_jhH4vajpqQYA@mail.gmail.com> (raw)
In-Reply-To: <CAEAzY38ZybH=BVrM1zOKJ0VyHoAPgn=HL5QO1fPHMx_DfDT+=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]

Stop whining. If you want something done your way, do it yourself, or pay
somebody to do it.

If you think Nemo and his group (or anybody else) are not following the
grants' rules, complain to the funding organizations. I don't remember
seeing any funding coming with "researchers have to publish their work
hourly" rules, but I might be wrong.

    Lucho


On Sat, Sep 7, 2013 at 7:56 AM, Aram Hăvărneanu <aram.h@mgk.ro> wrote:

> > we got not a single cent for nix. As far as lsub is concerned,
> > it's been a free time effort.
>
> You are seriously misrepresenting nix and/or yourself.
>
> From http://lsub.org:
>   "Nix is joint work of Laboratorio de Sistemas with Bell Laboratories,
>   Sandia National Labs, and Vitanuova."
>
> Lsub is part of GSyC which is an academic institution funded with
> public money. Sandia National Labs is funded by the DOE. People are
> getting paid to work on nix. This is not "Nemo and his friends hack
> on Plan 9" project. It that would be the case, using the lsub name
> everywhere would constitute grave academic misconduct. You publish
> papers with lsub credentials.
>
> My personal projects are not my employers (in fact some people place
> huge disclaimers stating that; I find the practice silly). Nix is
> not a personal project. It's listed right there on the lsub page
> along with other Plan 9-related project. Some of them even list
> their grants:
>
>   "Finnancial support, in part, by Spanish MCYT TIN2010-17344 and
>   Madrid CAM S-2009/TIC-1692."
>
>   "This work is supported in part by grants CAM CLOUDS S2009/TIC-1692
>   and MCyTTIN-2007-67353-C02-02"
>
> You are paid by your university to work on Plan 9-related projects.
> It's part of your everyday job.
>
> Let's take a look at other misinformation:
>
> > Today it continues using a public development process, as described
> > above.
>
> It does not. It's done in secret. It wasn't always done like this.
> For a short while, development was public. It stopped being public
> when you (nemo) and Ron fighted and couldn't find common ground.
> Then you took the toys and locked them in your fortress.
>
> > there is no private nix development going on
>
> Let's quote something from a recent nix paper:
>
>   "We are grateful to Charles Forsyth for his advice regarding this
>   work, and to the new Plan 9 secret society."
>
> Ahem.
>
> --
> Aram Hăvărneanu
>
>

[-- Attachment #2: Type: text/html, Size: 3181 bytes --]

  parent reply	other threads:[~2013-09-07 14:52 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
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 [this message]
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=CAOha14xbA6zQEitXq0z3dcoftR2oOD8r5C_RA_jhH4vajpqQYA@mail.gmail.com \
    --to=lucho@ionkov.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).