If I will find some time I will have a closer look again to set up and use SVN. But even in the case of an SVN "Write access to the SVN archive will be provided to developers who are making frequent contributions to the codebase." This is the usual policy how the SVN's I know are set up (the quote comes from Postgis svn).
Until a svn exists, it's possible for users to provide me with extensions, code, themes, etc. by mail. So far, this just happened once (the second one was not really usable and implementable). In any case, I found it normal that a contribution is discussed at least shortly before sending it as zip file. armin ps: contributions to the p.mapper documentation were already possible for everybody on the wiki since March, I haven't seen anybody writing a single line for it... Ideas could be added and discussed since several months. Alessandro Pasotti wrote: > Il 19:42, venerdì 20 ottobre 2006, Paolo Cavallini ha scritto: >> That's right, but perhaps somebody else can take care of this? >> I noticed that, given the relatively small size of the project, and the >> relative ease at modifying it, many people tend to fix bugs in their >> particular installation, develop small new tools etc, but all this work >> does not flow back into the main project. >> All the best. >> pc > > Well Paolo, I would say that this kind of decisions should be taken by the > original author and actual maintainer. > > So the main question is: Armin where do you want to go with pmapper? > > Should it become a real cooperative project or continue like now as a > one-man-project with you as leader, developer, maintainer etc. etc. > > I personally think that you (Armin) have done an impressive very good job, I > like pmapper and continue to use it in my projects, but I agree with Paolo > (and other members of this list) that sometimes a broader discussion about > new features or how to fix some issues and bug should be taken. > > Ok, now we are just saying we would like to participate more in pmapper > development, also contributing patches, plugins, code, ideas documentation > etc. > > But to allow a better cooperation we definitely need a code repository and a > bugtracking system plus a comitee of major contributors who will take the > final decision on controversial topics. At least this is how other Open > Source projects work. > > As a final note, I (and probably others) will not duplicate our job inserting > bugs and fixes in two systems or discussing in two lists, I really hope we > will find a constructive and cooperative way of improving pmapper. > > Regards. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
