Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move inactive maintainers to emeritus #910

Merged
merged 1 commit into from
May 10, 2022

Conversation

jdolitsky
Copy link
Member

As stated in EMRITUS.md:

We would like to acknowledge previous OCI image spec maintainers and their huge contributions to our collective success ... We thank these members for their service to the OCI community.

The last activity from these maintainers appears to be Jun 30, 2017, which predates my involvement in this community. As we make progress in areas such as the OCI Reference Types WG, it becomes critical to have active maintainers on this repository.

In my opinion, If you do not support this motion, it says a lot about your motivations and political agendas. Please consider this and do the right thing.

Signed-off-by: Josh Dolitsky <josh@dolit.ski>
@jdolitsky
Copy link
Member Author

For more context, see opencontainers/tob#95

@jdolitsky
Copy link
Member Author

Pick the popcorn out of your teeth and give me a +1

Copy link
Member

@cyphar cyphar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. As much as it pains me to say it, given the 2/3 LGTM requirement for releases and certain kinds of motions, having maintainers which have been inactive for 5 years affects the project's ability to function.

If any of the maintainers want to rejoin actively working on the project, we'd welcome them back with open arms.

But in the sake of fairness we should wait a reasonable amount of time for @brendandburns and @jstarks to reply. This motion requires a 2/3 vote anyway...

Copy link
Member

@vbatts vbatts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The topic has come up before, in a particularly heated time. I'm glad that things have cooled off now and the references WG is rocking along.
And while this does appear to be a dropping of @microsoft.com emails, it is not such. I have not updated from my community address to my MSFT work address, and additionally @sajayantony has been very active and involved (and likely a good future maintainer candidate, but that's unrelated to this PR).

@jdolitsky
Copy link
Member Author

@vbatts - spot on. Thank you. This has 0% to do with Microsoft, and everything to do with the health and future of opencontainers.

Wholeheartedly agree that Sajay makes a great candidate. So much so that I have opened #911 :)

@vrothberg
Copy link
Contributor

I am surprised. Other suggestions have been rejected due to a lack of a track record and @sajayantony has no commit history in the image-spec.

This is not meant as an attack at all. I just want to understand the reasoning and if something has changed compared to last year.

@jdolitsky
Copy link
Member Author

There is more than commit history that indicates dedication. There is also participation on the weekly calls, which Sajay attends nearly all. Besides, #911 is just my personal nomination which maintainers can take or leave. As Vince said, it's unrelated.

@vrothberg do you disagree with the contents of this PR itself?

@vrothberg
Copy link
Contributor

There is more than commit history that indicates dedication. There is also participation on the weekly calls, which Sajay attends nearly all.

Totally agree. I have no doubts on Sajay being a great candidate.

@vrothberg do you disagree with the contents of this PR itself?

No, I very much agree. I would love to see the image-spec move forward.

Last year, some (all?) proposals were closed (including mine). It remained unclear to me how the maintainership criteria look like and it somehow still is.

I think it would help to provide references on why a certain candidate is a good fit.

@jdolitsky
Copy link
Member Author

@vrothberg completely understand. I've just opened #912 to see if we can get this clarified.

@vbatts
Copy link
Member

vbatts commented May 4, 2022 via email

@jdolitsky
Copy link
Member Author

2 more approvals will get us to two-thirds quorum. cc @jonboulle @stevvooe

(However, it's unclear from governance docs if quorum is even needed here)

Copy link
Contributor

@stevvooe stevvooe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jdolitsky
Copy link
Member Author

Just one more LGTM needed here. Ping @jonboulle @brendandburns @jstarks

@stevvooe stevvooe merged commit 37d82a2 into opencontainers:main May 10, 2022
@jdolitsky jdolitsky deleted the old-maintainers branch May 10, 2022 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants