Skip to content

Latest commit

 

History

History
104 lines (73 loc) · 5.57 KB

COMMITTERS.md

File metadata and controls

104 lines (73 loc) · 5.57 KB
Raw

Project Committers

Who are the committers? (GitHub Username)

Committers Emeriti

  • Anthony Colebourne (acolebourne)
  • Christian Cousquer (cousquer)
  • Daniel McCallum (dmccallum)
  • Drew Wills (drewwills)
  • Eric Dalquist (edalquist)
  • James Wennmacher (jameswennmacher)
  • Jeff Cross (jeffbcross)
  • Jen Bourey (bourey)
  • Josh Helmer (jhelmer-unicon)
  • Mairi Fraiser (mairi)
  • Misagh Moayyed (mmoayyed)
  • Nicholas Blair (nblair)
  • Paul Spaude (pspaude)
  • Tim Levett (timlevett)
  • Timothy A Vertein (vertein)
  • William G. Thompson, Jr. (wgthom)

What's a Committer?

Committers are stewards of the project.

Committership is a state of mind. Committers are Committers because the other Committers recognize them as Committers and because they recognize themselves as (and act like) Committers.

Committership is not access to write changes. Committers are entitled to write access and other like infrastructural privileges, but "write access" isn't the point, it's just a tool. You aren't a Committer because you have write access; you might have write access because you're a Committer.

How do I become a Committer?

Committership is a state of mind. Of your mind, and of the minds of the other Committers. You become a Committer because the other committers recognize you as a Committer and because you recognize yourself as (and act like) a Committer.

Formally, you become a Committer when the other Committers acknowledge this state of mind by formal nomination and vote on the email list.

What happens to inactive Committers?

Committership is for life. If you once acted as a steward of the project, you could almost certainly get back into that state of mind.

Inactive committers tend to lose access privileges, through entropy and through minimizing unneeded security exposure. This doesn't mean Committers stop being Committers - it just means they may need infrastructure to be fixed up if and when they are again active.

Inactive committers may be characterized as "emeriti" by request or by vote of the Committers. This is a convenient label for managing expectations about who is likely to be active. Votes that have heard from all active Committers need not wait for emeriti, for instance. Committers emeriti will be restored as regular Committers upon request. In addition, committers that have not authored a commit to any uPortal related repos for two or more years are automatically "emeriti". Again, their privileges shall be restored upon request.

Rules?

We adopt the rules and culture of the Apache Software Foundation.

We make necessary or pragmatic local adaptations.

  • Committers form the "PMC" for purposes of Apache rules.
  • We use the lists we have. Currently, the go-to list is public [email protected]. If we had more differentiated lists we'd use them in the way an Apache project would use them.

Governance fail safe: the uPortal Steering Committee

The uPortal Steering Committee or successor governance body may at any time for any reason arbitrarily change the Committer roster of this project.

This is a fail-safe. If it has to be invoked, it's because something failed.

Governance fail safe: the freedom to fork

This is an open source project under the Apache 2 open source software license.

Like all open source projects, the ultimate fail-safe is the freedom to fork. Anyone can adopt this source code, re-plant it somewhere else, and re-bootstrap a living, breathing project around it.

Anyone can do that. But they probably shouldn't. Preferable to engage here instead.

References

Apache Software Foundation on