FYI I see this thread referencing the GDAL github team organization. As
far as I know, nobody has "designed" it with deep thoughts. It has the
current structure most likely as an accident of history... If I were to
design it, I would keep it simple and stupid. With git workflows, the
concept
On Fri, 8 Mar 2024 at 09:10, Ondřej Pešek wrote:
>
> @Vaclav: Do you have some more points against the master-children
> schema? It seems that the general agreement is *for* the restructuring
> into parent and children teams. So far the only point against was "I
> didn't find team nesting
Hi Markus, all,
sorry to hear about this fuss. I will contact Zenodo asap.
On the bright side, this is another proof of the (frustrating) service quality
hickups we encounter.
EGU has invited me to talk about these issues in April and I will use this
opportunity to demonstrate our case.
Hi Peter, all,
So GRASS GIS 8.3.2 has been published and no trace of it in Zenodo:
https://zenodo.org/records/10685321
The GitHub-Zenodo bridge seems to be unstable?
Ideas welcome,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
