On Thu, 7 Jul 2022 at 14:11, Craig Russell <apache....@gmail.com> wrote: > > Hi Sebb, > > I don't think my message was understood. > > > On Jul 7, 2022, at 04:22, sebb <seb...@gmail.com> wrote: > > > > On Thu, 7 Jul 2022 at 03:52, Craig Russell <apache....@gmail.com> wrote: > >> > >> I'm happy to write a patch if you can give me a hint where the code is > >> that looks at reserved-ids so I can write an update to the red box. > > > > Note that re-using a reserved ID could mess up code provenance - > > effectively it means someone can take over someone else's ID. > > Not exactly identity theft, but with many of the same potential > > consequences. > > I understand that a reserved id cannot be used again. That was not what I was > asking for.
OK > > > > Sorry, but I see no valid reason to differentiate why an id is > > disallowed, so doing research on it is work I don't wish to undertake. > > Again, I am not asking for the reason that an id is reserved, just the fact > that it is. > > > > If you wish to know personally whether an entry is in the reserved > > list or not, just look at the file which I think is a sibling to > > iclas.txt. > > All i'm asking for is that if a user requests an id that is reserved, that > the secretary tool add a line to the response "The id requested is not > available. Please contact the (P)PMC with a different id." and add a red box > "The id is not available. Continue?" > > The secretary tool is supposed to be a help to the secretary/assistant. > Having mysterious red boxes with no obvious way for the user to tell what is > happening is a bug. Regardless of whether the id is reserved or is currently in use, the user must choose a new id. Why does the user need to know the exact reason? > Regards, > Craig > > > >> Thanks, > >> Craig > >> > >> On Jul 6, 2022, at 16:05, sebb <seb...@gmail.com> wrote: > >> > >> On Wed, 6 Jul 2022 at 23:53, Craig Russell <apache....@gmail.com> wrote: > >> > >> > >> Thanks for the explanation. How do we prevent it in future? > >> > >> > >> How often does it occur? > >> > >> Can we add reserved names to > >> https://people.apache.org/committer-index.html which is where we send > >> people to check if their preferred id is already available? > >> Perhaps entries like this: > >> SVN ID Name > >> jacek <reserved> > >> > >> And surely we can add a red box warning for the secretary to understand > >> that this is a reserved name? Warning: the requested id is in the > >> reserved-ids.yml list. > >> (Proceed anyway?) > >> > >> > >> Does it really matter why the id is invalid? > >> > >> Whatever the reason, it cannot be used. > >> > >> Seems like completely unnecessary work, given how infrequent this is. > >> > >> Thanks, > >> Craig > >> > >> On Jul 6, 2022, at 14:48, sebb <seb...@gmail.com> wrote: > >> > >> Because it is not allowed. > >> > >> See reserved-ids.yml > >> > >> On Wed, 6 Jul 2022 at 19:14, Craig Russell <apache....@gmail.com> wrote: > >> > >> > >> I filled the form and the committer id should be jacek. But the field is > >> red and it does not try to request the account. > >> > >> Any ideas? > >> > >> Thanks, > >> Craig > >> > >> Craig L Russell > >> Assistant Secretary, Apache Software Foundation > >> c...@apache.org http://db.apache.org/jdo > >> > >> > >> Craig L Russell > >> c...@apache.org > >> > >> > >> Craig L Russell > >> c...@apache.org > >> > > Craig L Russell > c...@apache.org >
