[BioRuby] development updates?

[Andrew Grimm]

While there may be a difference between making suggestions and doing
stuff, there's also a difference between making suggestions and
personally criticising people. I think that personal criticisms should
be avoided when possible.

I am no longer surprised when Rails people behave in an incivil way,
but I hoped that non-Rails ruby people would still follow "Matz is
nice, so we are nice".

Andrew Grimm

On Mon, Aug 9, 2010 at 4:43 PM, Pjotr Prins <pjotr.public14 at thebird.nl> wrote:
> Sorry, that was a bit rabid. Basically you think we should be
> organised differently, and/or share information differently. On the
> mailing list you'll find a history of that.
>
> Every OSS project is different. There is no single way. If you want
> it differently, take initiative - rather than talking about 'culture'
> in other projects.
>
> BioRuby has grown this way, and it works for us. As I see it, all
> major developments have been discussed via the list. The latest
> developments are GSoC, plugins and BioLib BAM/SAM support (which is
> on the biolib mailing list).
>
> Again, I don't mind you want it different. But the way to change
> things is to act. With actions gain you respect. And most respect is
> gained by writing code. That is true in every OSS project I know.
>
> Everyone can criticise, few really change things.
>
> Pj.
>
> On Mon, Aug 09, 2010 at 08:00:25AM +0200, Pjotr Prins wrote:
>> First you steal our announcement of a paper - I am sure Jan did not
>> intend you to blurt that out on the list. Second you breach my trust
>> by quoting a private message on the list. Third, you assume our
>> development process is not transparent. Based on what?
>>
>> Maybe there is a simple answer: we don't need to communicate that
>> much.
>>
>> BioRuby is not a centrally run project, business or organisation.
>> BioRuby is OSS. Feel free to run with the project. Fork, code,
>> document, organise, whatever.
>>
>> So far, I see talk and hand waving. If you want to organise something,
>> be factual and concrete. Actions speak louder than words. You also may
>> want to read the history of the mailing list.
>>
>> I suggest you earn your stripes with getting your code accepted to
>> BioRuby, first. That is a pretty steep hill anyway. Last time I
>> checked your code.
>>
>> And I suggest at least two apologies, if you want further responses
>> from me.
>>
>> Pj
>>
>> On Mon, Aug 09, 2010 at 11:01:13AM +0530, Anurag Priyam wrote:
>> > >
>> > > What does the fact that *you* are not aware of a manuscript have to do
>> > > with the development process? I miss the connection.
>> > >
>> >
>> > I just thought it would be better if *all* the developers( important
>> > or less important ) are updated on what is happening. I see it
>> > happening on the few other lists I have been subscribed to all the
>> > time.
>> >
>> > > As BioRuby is an OSS project, feel free to take the lead. You
>> > > understand OSS development, right?
>> > >
>> >
>> > Well to be very frank this has been my very first attempt at OSS
>> > contribution. So, may be I really do not understand it very well.
>> >
>> > > Talk is cheap. Making stuff happen - that is what counts.
>> > >
>> >
>> > FYI, that is exactly what I am trying to do. I see very different
>> > culture in other development teams and I find it better. I was trying
>> > to bring some of it in. If it is unwelcome, I have no issues.
>> >
>> > Out of the things I suggested, there is only one thing that I can do
>> > in my capacity : update the list on what I have been doing, and I do
>> > that.
>> >
>> > --
>> > Anurag Priyam,
>> > 3rd Year Undergraduate,
>> > Department of Mechanical Engineering,
>> > IIT Kharagpur.
>> > +91-9775550642
> _______________________________________________
> BioRuby Project - http://www.bioruby.org/
> BioRuby mailing list
> BioRuby at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioruby
>