home.social

Search

27 results for “jodygarnett”

  1. Managed to communicate enough with both @camptocamp and @geosolutions_it folks to make it happen. And they were both receptive, but cautious that their bosses could not approve time unless funded.

    Fork is merged. No more manual install hell for - an amazing result for this community.

    It would be wise for GeoNode folks to fund collaboration that benefits their install base in the future.

  2. The post also has a small update from the @osgeo
    [opengis harmonization](osgeo.org/opengis-harmonizatio) code-sprint activity.

    A lot of @osgeo projects are going to be affected, indeed we found blockers with and during the activity.

  3. is parallel-play for open source!

    Looking forward to @osgeo code sprint in Bolsena next week!

  4. GeoServer had great time at - here are our community presentations: geoserver.org/announcements/20

  5. @jodygarnett Greetings to the #Bolsena Community sprint from #OSGeo! Wonderful pictures.The beautiful former monastery is a great place to work together. Enjoy the week! #foss4g @osgeo @foss4g #gischat #fossgis

  6. @jodygarnett Greetings to the Community sprint from ! Wonderful pictures.The beautiful former monastery is a great place to work together. Enjoy the week! @osgeo @foss4g

  7. @jodygarnett Greetings to the #Bolsena Community sprint from #OSGeo! Wonderful pictures.The beautiful former monastery is a great place to work together. Enjoy the week! #foss4g @osgeo @foss4g #gischat #fossgis

  8. @jodygarnett Greetings to the #Bolsena Community sprint from #OSGeo! Wonderful pictures.The beautiful former monastery is a great place to work together. Enjoy the week! #foss4g @osgeo @foss4g #gischat #fossgis

  9. @jodygarnett Greetings to the #Bolsena Community sprint from #OSGeo! Wonderful pictures.The beautiful former monastery is a great place to work together. Enjoy the week! #foss4g @osgeo @foss4g #gischat #fossgis

  10. Heading out to FOSS4G Europe 2025

  11. The software architect in me just wishes to pause.

    As was open source, combined with some personal attitude on my part, has allowed me to recover the situation for this 2.3.0 release.

  12. @geosolutions_it folks showed up with a fork and added functionality, but since both companies are primarily consultants they did not have budget to collaborate. And camptocamp had not established procedures to collaborate.

    so a fork is an understandable response.

  13. i am sure there are lesson to be learned here on sustainability.

    @camptocamp abandoned this, with some pretty muddled communication.

    Understandable. Looking at the other active players they were partnered with on this technology, GeoExt crew, there was not much chance of Java developers to collaborate and share maintenance.

  14. So I am getting ready to go to and have not had time to share / promote @geoserver talks and workshops ahead of the event

    If you are part of the community we could use a hand on the communication side of things!