linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: Jerome Martin <jxm@risingtidesystems.com>,
	Nicholas Bellinger <nab@risingtidesystems.com>
Cc: target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: target userspace utils (rtsadmin) project is dysfunctional
Date: Fri, 09 Sep 2011 00:07:21 -0700	[thread overview]
Message-ID: <4E69BB29.2030800@redhat.com> (raw)

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

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.

Regards -- Andy

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09  7:07 Andy Grover [this message]
2011-09-09 14:14 ` target userspace utils (rtsadmin) project is dysfunctional Douglas Gilbert
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=4E69BB29.2030800@redhat.com \
    --to=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 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).