[OpenAFS-devel] RT, Gerrit, Release Management changes

[Troy Benjegerdes]

Would it be feasible for us to 'eat our own dogfood', so to speak, and 
use SPNEGO and cross-realm Kerberos to log into RT? (If this is already
implemented, and I haven't noticed, then I will volunteer myself to go
document it better)

(I used to have an RT instance that sort of did this, but I did not
open the whole can of worms I expect general cross-realm trust will
open)

> The powers granted to current developer-users have been expanded and
> should cover this. Mechanisms to grant additional users(*) developer or
> commenter status will be coming, as will a mechanism to verify people
> creating RT accounts are "real users".
> 
> * Anyone who has contributed five accepted patches in the previous year
>   will be added to the "developer" group, not to be revoked except by
>   the Gatekeepers in case of problems.  Any contributor may be a
>   commenter.
> 
> 
> OpenAFS Gerrit (http://gerrit.openafs.org)
> 
> Currently, de facto action is that substantial changes will not be
> merged without multiple reviewers, but +1s are not cumulative and so
> only a gatekeeper +2 will allow a patchset to be merged.
> 
> Once "Approval" guidelines have been written, individuals who have
> contributed five accepted patches in the previous year will be granted
> the ability to +2/-2 patchsets.  A +2 vote will be an indication that a
> substantial review has been completed by someone with appropriate
> expertise to evaluate the patchset.
> 
> The granting of +2/-2 permissions will be performed on a semi-regular
> basis by the Gatekeepers until such time as an automated mechanism for
> approval is designed and implemented.
> 
> 
> Release Management
> 
> The Gatekeepers are seeking qualified volunteers to take on the
> responsibility of release management for the 1.4 and 1.6 branches.
> Release managers will be responsible to coordinating release schedules
> for these branches with the Gatekeepers, performing pullups, generating
> release notes, and certifying when pre-release and final releases are
> ready for tagging and distribution.
> 
> 
> The Gatekeepers believe that these steps will increase the participation
> by the community and speed up the rate of stable releases.
> 
> -- 
> Derrick
> for the gatekeepers
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel