On Samstag 25 April 2009, Christian Stroetmann OntoLab wrote: > Jason, > > > Volker, > > > >>> First, please following mailing list etiquette and don't top post > >> > >> it is pretty much his mailing list. > > > > Just because he is the "maintainer". > > > > Am I wrong, but the community owns the code, not Edward. > > I have had the same impression in the past, but now I have learned > something new. > people who write the code own the code. How many reiserfs or reiser4 related patches from you two got into the kernel in the last... lets say 4 years? > > I mean, I could host a reiser list on my mail server. > > I can do it too ;) if you want to - nobody is stopping you. > > >>> Third, if the community only relied on you to progress reiserfs, it > >>> has been years at this point and nothing significant. it is basically > >>> somewhat dead. > >> > >> reiserfs is in maintenance mode - there aren't much changes. In > >> fact, less > >> changes is a good thing. > > > > maintenance mode = stagnant, no? wrong. maintenance mode = stable. > > > >> Edward is also pretty much the last person working on reiser4. You are > >> attacking him, but I don't see patches from you. Gives someone > >> something to > >> think about. > > > > Right because he has slammed heads with everyone that was willing to > > help him. I was willing and when I tried talking with him he blew me > > off. So I forked. OntoLab too. > > Yes, that's exactly the point. and then you stayed in your little corner. Nobody knows about your forks. Nobody can use your forks. Or are you sending your patches to Andrew Morton for -mm inclusion? > >> look at the archives. Edward has good reasons to feel ripped of. > >> Maybe it is all a big miscommunication. But that isn't solved when > >> ontolabs > >> guys agressively advertise for themselves. > > > > But what else is there when a snails pace is being achieved otherwise? 'diplomacy' look into it, a very interesting topic. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html