Repost including target-devel and linux-scsi lists. Sorry for the noise. On Sat, Sep 10, 2011 at 10:30 PM, Jerome Martin <jxm@xxxxxxxxxxxxxxxxxxxxx> wrote: > Hi Andy, > I am not so much interested in your "calculation" than on having a list of > checkpoints that you feel would be important to improve in order to have a > better OSS project. In all good faith, I can assure you this is all I (we) > are looking for, within the limits of time & resources available. > As for the emails I did not (never, really ?) answer, apart from the > vacation pointed out by Nic, I guess I must have erased part of my mailbox > inadvertently then, because I do not have them in my todo box, in which I > normally have everything not handled yet. > > Anyway, thanks for saying rtsadmin is a nice piece of code, I hope we can > improve it with as much enlightened (read from people using it ;-) ) input > as possible. > And again, I really am eager to take your suggestions about how to improve > the docs and processes, these are vast topics and the best places to start > might not be always intuitive when you are deep into the code itself. I > engaged huge efforts in making rtsadmin self-documenting as possible, with a > lot of documentation in the code itself, but clearly this is not enough. I > assume there might be some easy to do pieces of doc that could improve > dramatically the user experience, but am unsure what they are (install ? > packaging ? building from source ? quickstart ? so many things to do...). > As for what's planned, the next items on my community todo are to adapt the > build process to export a versioned tarball so distros and everyone else can > get a fixed version release without having to go through the git-dependent > build process, fix the tags exports to the community repository (some script > is blocking somewhere in the chain of autocommits) and write a quick "how to > build packages" howto. Do those sound reasonable to you or would you put > something higher on the priority list ? > One last thing I need to say is that the company as a whole as a very > favorable view of anything that can improve the community experience, so > every misimplementation of that policy is to blame on me. Unfortunately I > might have a hard time managing priorities and workload, and this apparently > led to regrettable effects on the OSS project. > Thanks for both the kind and critical words, but now you've said too much to > withhold the constructive mentoring any longer ;-) > Kind Regards, > Jerome > On Fri, Sep 9, 2011 at 10:07 AM, Andy Grover <agrover@xxxxxxxxxx> 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 >> >> 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 > > > > -- > Jérôme Martin > -- Jérôme Martin -- 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
