All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Andy Grover <agrover@redhat.com>
Cc: Jerome Martin <jxm@risingtidesystems.com>,
	Nicholas Bellinger <nab@risingtidesystems.com>,
	target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: target userspace utils (rtsadmin) project is dysfunctional
Date: Fri, 09 Sep 2011 10:14:06 -0400	[thread overview]
Message-ID: <4E6A1F2E.6080601@interlog.com> (raw)
In-Reply-To: <4E69BB29.2030800@redhat.com>

On 11-09-09 03:07 AM, Andy Grover wrote:
> Hi Jerome and Nick,
>
> I happened upon this website:
>
> http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html

I totted up 70 each for my open source packages so I
reckon that list should be taken with a large grain
of salt.

This one amused me:
  "Your code tries to install into /opt or /usr/local [ +10 points of FAIL ]"
Installing into /usr/local is the default for autotools.

> According to my calculations (available upon request), rtsadmin comes in
> at 220 points: "so much fail, your code should have its own reality TV
> show".
>
> I could also add some more like "primary developer never responds to
> email", "CLA discourages external contributions", and "uses executable
> name as corporate marketing tool".
>
> Admittedly rtsadmin is a nice piece of code, thanks btw, but your
> company is falling short of accepted standards for stewardship of a
> FLOSS project. Please tell me why we all wouldn't be better off if I
> forked rtsadmin tomorrow.

One reason from the above link:
   "Your code is a fork of another project [ +10 points of FAIL ]"
:-)

Doug Gilbert


  reply	other threads:[~2011-09-09 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09  7:07 target userspace utils (rtsadmin) project is dysfunctional Andy Grover
2011-09-09 14:14 ` Douglas Gilbert [this message]
2011-09-09 20:56 ` Nicholas A. Bellinger
     [not found] ` <CAN4SboCi7C9iB+GNH85yfMkvDQdf4BN4CunUuJjvc+a-cfaCFQ@mail.gmail.com>
2011-09-11  5:37   ` Jerome Martin
2011-09-12 19:56     ` Andy Grover

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=4E6A1F2E.6080601@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=agrover@redhat.com \
    --cc=jxm@risingtidesystems.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@risingtidesystems.com \
    --cc=target-devel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.