James R. Perkins
Principal Software Engineer
The GOVERNANCE.md for WildFly AS that we adopted last week includes a
"Maintainer" role. Alongside that GOVERNANCE.md we have a Team.md
where we'll list the people in the various roles. We need to populate
that document.
I've sent up https://github.com/wildfly/wildfly-governance/pull/7 to
do that for the Maintainer role, plus a subset of those in the
'Publisher' role -- those who publish the main wildfly/wildfly repo.
Your inputs on this are most welcome!
The GOVERNANCE.md defines Maintainers as:
"Contributors eligible for write access to a code repository for a
WildFly Application Server project. Responsible for driving
initiatives and reviewing/merging contributions in their area of
expertise. Write access might be limited to particular repositories."
So I started from the premise that our initial maintainers are those
who we've given write perms in the past. I did some tool-drive Github
inspection + discussion with various folks who deal with GH orgs where
my tool didn't work, plus some permission list cleanup discussions.
The resulting set of names is in the PR.
Thank you to those of you who helped me with this!
Going forward, before any grants write access to any of the dozens of
WF AS repos we should check that they are on the Maintainer list and
if not have a discussion to get them added.
Best regards,
Brian Stansberry
WildFly project lead
He/him/his
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/QZRSPQZAN75L5QGFEU62QSL3Z3K5OAUL/