> > > Sorry, I didn't want to sound rude. > I just have the feeling that uDig lives in too much burocracy and QA, > while we have issues and no manpower to solve important issues, > showstopping bugs and release problems. > > I hear you; I was quite disappointed our release party did not work out in > December :( > I am keen to look at recruiting more developers under the location tech > banner (and am glad that is moving along). > > I find the "procedures" about normal for an open source project, but I > think we could cut down on the description to make them easier to follow. >
I have had different experiences and find them a bit oversized. But I understand your point. The problem is that we are creating a "how to develop uDig" book and lack a decent developer manpower in the community. > I am doing this work *without* funding. We do it to continue to > improve the processing part of uDig, in the hope to attract > contributors. If the hassle of creating (maybe even already existing) > documentation is too big, contributions will not make it to the show. > We really need to find a better equilibrium in this. > > I am hesitant to add functionality without documentation (or video?) > providing a clue on how to use it. > I am ok with adding docs with new functionality, which I think is what I have been doing. We have usual problem of uDig having this double face of framework and user GIS. It disperses our force :) I will most probably try to nail down the editor part and missing doc/code this weekend. If you are hacking, we can do some together. Everyone is invited obviously, let's hope in some bad weather :) Cheers, Andrea > > Jody > > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
