I don't think we should allow IDs to be "reserved": Imagine you've been granted committer privileges but you can't pick the ID you want because it has been "reserved" by a non-committer, it seems backward.
Gary On Wed, Mar 20, 2024 at 8:37 AM Paulo Motta <pa...@apache.org> wrote: > > This is right Claude. Essentially, the people.apache.org handle can be seen > as a “handle reservation” to a future ASF ID handle, that will be granted > when the contributor becomes a committee. > > So it’s basically a pre-ASF ID handle granted to contributors without any > privileges or login (except the people.apache.org auto-generated > contributor page). > > On Wed, 20 Mar 2024 at 09:19 Claude Warren <cla...@xenei.com> wrote: > > > On Wed, Mar 20, 2024 at 12:55 AM Paulo Motta <pa...@apache.org> wrote: > > > > > > > > 3. John Doe fills a simple form and selects the username "doejohn", which > > > is not an ASF id, but just a handle to a people.apache.org page. If an > > ASF > > > id exists with the same name, then the request is rejected. > > > 6. After some years of contributions, John Doe is invited to be a > > committer > > > of Apache Foo. > > > a. John can "convert" its username "doejohn" into an ASF ID, or can > > > choose another ASF ID handle when becoming a committer. > > > b. This kicks-off an update to people.apache.org/~doejohn to change > > the > > > role from "ASF Contributor" to "Committer at Apache Foo" > > > > > > > > The above 2 points indicate that our new committer registration would > > require that no handles used on people.apache.org be granted as an ASF id. > > Seems like we need a way to track the union of ASF Id and > > people.apache.org > > handles. > > > > > > -- > > LinkedIn: http://www.linkedin.com/in/claudewarren > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
