On Fri, 2011-09-09 at 00:07 -0700, Andy Grover wrote: > Hi Jerome and Nick, > Hi Andy, > 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". > I don't think it's fair to say that the primary developer never responds to email. We have had summer vacations and being a small company our email + work load is very high. If you don't get a response please keep pinging us. > 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. > We are always open to constructive criticism, so I would hope that you would share your perspective with specifics for us to consider wrt to improvements to make your job of integrating easier before wanting to fork rtslib/configshell/rtsadmin. Can you share with us your primary points of frustration that are making you consider this..? --nab -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
