I've been talking with Walter about this for a couple weeks, and I think it's just been a mis-communication that this has been directed at core. While we are certainly looking to get this supported in core eventually, I've been assuming basically the same process as you're describing here. Having said that, we're only at the design discussion stage, so we're actually not yet ready to request an unsupported module to support this work (though that will be coming shortly).
On 10 August 2011 00:32, Andrea Aime <andrea.a...@geo-solutions.it> wrote: > On Tue, Aug 9, 2011 at 3:49 PM, Andrea Aime > <andrea.a...@geo-solutions.it> wrote: >> On Tue, Aug 9, 2011 at 3:09 PM, Jody Garnett <jody.garn...@gmail.com> wrote: >>> Andrea do you have another suggested way to work on this then? So far a >>> proposal is the only way we have to communicate. We are not going to start >>> implementing with out a direction. >> >> Odd, current versioning and process both started with a mail/irc >> discussion and wiki >> pages without the need to stick stuff in core from day one. >> They are actually both still in unsupported > > Btw, if I were in your place and needed to push versioning into core I would > first fix the current versioning postgis store (or write a new one), make it > good for supported status (tested and so on) and ask around for a check > by other people doing versioning in parallel, to give people time to answer. > Once the store is good to be graduated and you have feedback > (and probably one or two months have passed) then you are good to go > to make a proposal and should get very little resistance to make that > going. > > This is especially true when you are a new developer, first you prove > yourself then you make proposals for core changes. > They once said "in internet no one knows you're a dog", that works > also the other way, "in internet no one knows you're an excellent > developer/designer", you have to prove that. > > Cheers > Andrea > > -- > ------------------------------------------------------- > Ing. Andrea Aime > GeoSolutions S.A.S. > Tech lead > > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584 962313 > fax: +39 0584 962313 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.youtube.com/user/GeoSolutionsIT > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > ------------------------------------------------------- > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > Geotools-devel mailing list > Geotools-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > -- Mark Leslie Geospatial Software Architect LISAsoft ------------------------------------------------------------- Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61 Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009 ------------------------------------------------------------- LISAsoft is part of the A2end Group of Companies http://www.ardec.com.au http://www.lisasoft.com http://www.terrapages.com ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
