There is apparently a GN5 code sprint next week.
I believe it’s great to move forward with code sprints, but I would prefer official “community code sprints” to be organized directly within the community.
Who have decided of this code sprint, and the date ? As a PSC member, I expect that I am aware of such initiatives, so we could discuss the availability of developers, the agenda of the sprint, and choose the best dates for all stakeholders.
This should be natural, GeoNetwork is an OSGeo community project.
Thanks
Hi
This sprint was discussed at last PSC meeting. It was more seen has a time to continue experimentation for GeoNetwork 5 which raise many questions. The idea is to try to answer some of them for the migration added in the version 5 project board. With Jose at least, we are looking at how to organize spring boot project and evaluate how to make modules taking a project use case about data analysis.
The last PSC meeting was canceled at last minute. Now, you are referring to a meeting where you were the only member of the PSC present. That, in my opinion, is not a community consultation.
On the same trend, why are you the only committer of the geonetwork5 repository ? Incredible.
Hey @fgravin I moved the repo over and could use some help sorting out permissions. Anything you see there is because of my inexperience moving repositories around.
Please be calm.
Update: Matched permissions with core-geonetwork please check your access is as expected
Yes sorry for last PSC meeting last minute changes and difficulties to set a new time slot due to holiday period of some of us.
About the sprint, it was initially planned as an internal project sprint and the idea to put it on public was more like a tentative to share our uncertainties and inexperienced and try to answer some of the questions raised on the draft GeoNetwork 5 roadmap. In that busy end of year period, we will rollback to an internal project sprint and try to be better on organization in the future … Sorry about that and thanks Jody for helping on the repository configuration.