Tuesday, June 30, 2009

JGrass and its sick community...

Today I closed 2 of the 3 active mailinglists of JGrass.
What a horrible feeling... it is now about 10 years I develop for FOSS software and never had to act like this.

Killing the mailinglists kills an open source project, needless to say.

But not killing them would kill us... so let's see if users will make the effort to keep at least the jgrass-users list alive. I really hope that converging efforts into on single list might do better.
The developers have been redirected to the udig developers list, since many of the questions were anyway related to udig core.

JGrass has always been a small kid with a lot of problems and an incredible difficulty to gather friends. This is due to it's nature and some dynamics I don't understand even now.

JGrass is a scientific based tool, that also wants to be a full powered desktop GIS. So what?

Let me think out loud and write down some comments:

With JGrass you can do complete hydrological risk studies, from the begin to the end of the study JGrass has all the tools. These tools are mainly useful to Engineers and Geologists. The problem is that most of those do a hydrological study once a year. Which means that at that time they come into the list, ask newbie questions and get help to do the job. Then for the rest of the year they disappear, since they have something else to do. When a "JGrass-job" comes again, here they come again, with almost the same questions, since JGrass evolved and no one was paying attention. Quite frustrating being always in need of founding to develop JGrass and having to help people doing their jobs for free.

Differently from other hydro-morphological toolkits, JGrass contains some heavy models and it is not possible to think it as a library. Instead we need a friendly yet powerful environment to get things rolling at the last state of art of technology.
Luckily we found that framework in uDig and we are glad of the migration we did every day since then. In fact, JGrass right now is at one of its best moments and quickly evolving (which makes me even more sad right now).

HydroloGIS is not able to be the only developer, the only release maintainer, the only docs writer, the only mailinglist answerer, and so on... Therefore the decision to cut away something. And what would that something be? Sad to say, but the only thing that we as HydroloGIS do not need and that we initially set up only for the community... a community that even now doesn't get what they are losing.

I am not telling it is not my fault. It probably is in some way. I am instead telling that I want to make things better. If I have time I want to spend it on developing, making better releases and write some documentation... not on newbie questions that other users would be able to answer.
Post a Comment