Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-21 Thread BJ Hargrave
and OSGi Specification Project lead // mobile: +1 386 848 3788 hargr...@us.ibm.com From: equinox-dev on behalf of Aleksandar Kurtakov Date: Monday, June 20, 2022 at 07:17 To: Equinox development mailing list Subject: [EXTERNAL] Re: [equinox-dev] Committer disagreement resolution guidelines I

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Aleksandar Kurtakov
I' ve opened https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1437 to see what we can get out of this discussion. Please vote/comment/etc. so we can get some good longterm solution. On Mon, Jun 20, 2022 at 1:28 PM Christoph Läubrich wrote: > Yes, but as you mention I need to > > a) got

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Christoph Läubrich
Yes, but as you mention I need to a) got to project site (often hard to find if not linked as project name != github repo name) b) got to https://projects.eclipse.org/content/thomas-watson-project-lead-equinox for exmaple c) then click on the user d) then there is a small button to gihub

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Ed Merks
Note that every project has portal information where you can see who is involved and see who leads: https://projects.eclipse.org/projects/eclipse.equinox/who That also has navigation (PROJECT LINKS section on the right) to the container in the project hierarchy, e.g.,

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Christoph Läubrich
Alright, do you think it would be possible to have (beside the private groups) maybe have for each Gitgub repo one @commiters @project-lead @pmc I really miss that info (not only in eclipse projects) to have a clue how to ask "anyone" e.g. for PR or in this case clearance of disagreement, so

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Aleksandar Kurtakov
Link definitely is correct but seems to be "protected" in some way. As a project lead I can even start discussion among project leads. On Mon, Jun 20, 2022 at 1:02 PM Ed Merks wrote: > It's not visible to me either... Maybe the link is wrong... > > On 20.06.2022 11:59, Christoph Läubrich

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Ed Merks
It's not visible to me either...  Maybe the link is wrong... On 20.06.2022 11:59, Christoph Läubrich wrote: Hm.. it seems this is not visible because I'm not part of the group... that's really annoying... Am 20.06.22 um 11:51 schrieb Aleksandar Kurtakov: We have

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Christoph Läubrich
Hm.. it seems this is not visible because I'm not part of the group... that's really annoying... Am 20.06.22 um 11:51 schrieb Aleksandar Kurtakov: We have https://github.com/orgs/eclipse-platform/teams/eclipse-platform-project-leads

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Aleksandar Kurtakov
We have https://github.com/orgs/eclipse-platform/teams/eclipse-platform-project-leads . Maybe there is smth similar for equinox. On Mon, Jun 20, 2022 at 10:50 AM Christoph Läubrich wrote: > To make usage of this guidelines easier, I think it would be good to > hava a group for > > - project

Re: [equinox-dev] Committer disagreement resolution guidelines

2022-06-20 Thread Christoph Läubrich
To make usage of this guidelines easier, I think it would be good to hava a group for - project lead - pmc on github e.g. we have @eclipse-equinox/eclipse-equinox-committers so would be nice to have: @eclipse-equinox/eclipse-equinox-project-lead @eclipse-equinox/eclipse-equinox-pmc as

[equinox-dev] Committer disagreement resolution guidelines

2022-06-15 Thread Aleksandar Kurtakov
Hey everyone, We have seen a number of heated discussions lately and after discussion at the PMC meeting today we decided to write some guidance on how resolutions should happen to prevent escalation. Please read it at