On 09/04/2014 13:22, Jody Garnett wrote: > I am glad you have come back?
Me too. > Just a couple basic questions: > > Q: Have you got a contribution agreement signed? No, I did not. Moreover, I think such an agreement should be signed by Comune di Prato, not by phoops s.r.l. nor by myself: we had a contract with Comune di Prato to develop the OpenLS extension, but the deliverable is their own, they are contributing it to the community. We (phoops) are just the developer. > I notice that many of the files lack a header, let alone the geoserver > header. Ooops, please point me in the direction of what misses to make the work acceptable as a community module. Is there a wiki page or some other documentation available? Is there a review process? I would gladly complete the work in the terms of community module acceptance. > Q: What are your plans for the module? > > Work is usually taken on as a community module initially, with an option > to be nominated to an extension when documentation and tests are sorted > out. We also like to see a commitment to sticking around as a module > maintainer, keeping the code up to date and fielding questions from the > user list. Well, I think you can imagine my answer reading the above lines... phoops had a contract that covered just development and community acceptance. I just spoke with Alessandro Radaelli from Comune di Prato and he agreed on that. He said they need some more time to understand what should be done and how to manage it compatibly with other projects they or other Public Administrations are currently handling or will soon start. In the meanwhile, I would gladly answer any technical question may arise from the list. > For example your pom.xml > <https://github.com/phoops/geoserver/blob/13D_CPO_TP2/src/community/ols/pom.xml> > - > does not list a developers section? Should we list the executor (phoops s.r.l.) or the contributor (Comune di Prato)? Many thanks for your time! Bye, UP ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
