To wrap this up for up for budget request I am thinking: - 2,000 “Geoserver Team operations” giving PSC ability to react to opportunities and challenges without waiting for board. - 10,000 for CiTE test automation, around which we would expect to fund raise an additional 20k. Approach used is contract for automation and sprint fixing and passing as many tests as we can.
I will write this up on the wiki, and invite feedback and revision ahead of board meeting on 21st. On Sat, Jan 12, 2019 at 2:04 AM Andrea Aime <[email protected]> wrote: > On Tue, Jan 8, 2019 at 10:30 PM Jody Garnett <[email protected]> > wrote: > >> So two approaches, set up as a sprint or set up as a contract. >> >> Given that this is both mission critical (we are a server) and important >> for osgeo+ogc partner relationship what will it take to get it done? >> >> Perhaps we should do both, a contract to set up the build chain followed >> by a sprint to pass the tests and submit certification request? >> > > As noted previously, I guess someone would have to first spend some time > researching the best option. > Docker image wise, I'm guessing one could build one that has all the tests > we need, and if needs be, we might customize it with > specific version numbers that refer to patched versions of the tests. > > Sprint wise, it's important to understand up front that getting to the end > of it with all tests passing against the official versions > might be an unreasonable goal, when working on CITE compliance I always > find a bunch of bugs in the tests themselves, > and that takes some time fixing, even if we make the corrective pull > requests to the tests ourselves. > Some suites, like the WCS 1.0 one, might just be un-fixable (as in, they > are kept around but don't think they get any maintenance). > More reasonable approaches would be to: > > - Fix as much as possible in GeoServer and open tickets for the tests, > and wait (may be a very long time) > - Fix as much as possible, and open PR for the tests, and wait (still > going to be a few weeks or more in my experience) > - Fix as much as possible, open PR, and prepare forks of the suites > with fixes, run the forks (only way to get > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > <https://maps.google.com/?q=Via+di+Montramito+3/A%0D%0A55054++Massarosa&entry=gmail&source=g> > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > -- -- Jody Garnett
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
