Re: [GRASS-dev] GRASS Teams on GitHub

Hi there, st 13. 3. 2024 v 1:36 odesílatel Vaclav Petras napsal: > 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.

Re: [GRASS-dev] GRASS Teams on GitHub

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

Re: [GRASS-dev] GRASS Teams on GitHub

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

Re: [GRASS-dev] GRASS Teams on GitHub

Hi again, Sorry to start revive the conversation from the silence but I have the feeling that it would be good to reach some consensus before we should let it rest. @Vaclav: Do you have some more points against the master-children schema? It seems that the general agreement is *for* the

Re: [GRASS-dev] GRASS Teams on GitHub

Hello guys, Thanks for this discussion. I went through all of your explanations and reasoning, and while I agree we have more repos and hence the need for more groups, I do think the GDAL teams structure gives a much better image of structure, unity and organization than our loose groups all over

Re: [GRASS-dev] GRASS Teams on GitHub

Hi Vaclav, Huidae, I was afraid of a long discussion (I know that the teams were changed recently and expected the consolidation to need more talks) and that's why I wanted to split it into two different threads: 1) master team and child teams, 2) necessity of all the teams we have. But whatever,

Re: [GRASS-dev] GRASS Teams on GitHub

Huidae and Ondrej, I recently restructured the teams to reflect GitHub workflows and resulting needs for access (the original team structure was just used from Subversion access). Another reason was getting a better control over who can change the code directly (this is connected to the required

Re: [GRASS-dev] GRASS Teams on GitHub

Ondrej, I agree with you that there are too many teams for GRASS [1] and they should be consolidated (or not, but at least moved) as child teams. Do we still need these subversion teams? * grass-subversion-committers GRASS GIS

[GRASS-dev] GRASS Teams on GitHub

Sweet devs, Looking at the GitHub teams within the OSGeo organisation [1], it is impossible not to notice the fact that the GRASS people are very good in making themselves visible through visual weed infestation. On one side, it is nice to see GRASS all over the dance floor; on the other one, I