On Tue, 10 Oct 2023 at 21:56, Matt Sicker <m...@musigma.org> wrote: > > Well, I wouldn’t say we disallow them entirely. The problem is that 99% of > the time, people put their userid in the public name field without intending > that to be their public name. If someone’s pen name is their userid, that’s > fine, but we want them to verify that in such a case. Perhaps we should > include a note in that description about it?
That would help, but rather than rejecting the application, we should ask if they intended to use their id as the public id. Or just allow it, and fix the name later. > The general idea here is that we want people to use some sort of public name > intentionally and non-maliciously (i.e., no impersonations). Using their user id as their public name is definitely not malicious or an impersonation. It may not be ideal, but it can always be changed later if they did not intend it. > We want to allow people to safely contribute to projects here without having > to expose their legal name or any of the complications that can involve when > it differs from their name they normally go by (e.g., I go by “Matt” instead > of “Matthew”, and some systems break if I use the short name; other people > have entirely different first or last names from what their current “legal” > name might be, or they use their middle name, or they just wish to remain > mostly anonymous). That is not relevant to the issue of rejecting ICLAs. > > On Sep 26, 2023, at 5:02 PM, sebb <seb...@gmail.com> wrote: > > > > On Tue, 26 Sept 2023 at 21:59, <mattsic...@apache.org> wrote: > >> > >> This is an automated email from the ASF dual-hosted git repository. > >> > >> mattsicker pushed a commit to branch master > >> in repository https://gitbox.apache.org/repos/asf/whimsy.git > >> > >> > >> The following commit(s) were added to refs/heads/master by this push: > >> new 5e47f5a9 Add pen name option to rejection template > >> 5e47f5a9 is described below > >> > >> commit 5e47f5a97fe987dc542737f795263472092c7a82 > >> Author: Matt Sicker <boa...@gmail.com> > >> AuthorDate: Tue Sep 26 15:58:19 2023 -0500 > >> > >> Add pen name option to rejection template > >> > >> Since we've clarified that pen names are allowed for public names, this > >> updates the template used for rejecting invalid use of public names to > >> indicate that. > >> --- > >> www/secretary/workbench/views/actions/incomplete.json.rb | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/www/secretary/workbench/views/actions/incomplete.json.rb > >> b/www/secretary/workbench/views/actions/incomplete.json.rb > >> index 61f33611..ee4252e3 100644 > >> --- a/www/secretary/workbench/views/actions/incomplete.json.rb > >> +++ b/www/secretary/workbench/views/actions/incomplete.json.rb > >> @@ -16,7 +16,7 @@ REASONS = { > >> '@missing_address' => 'missing or incomplete postal address', > >> '@missing_email' => 'missing email address', > >> '@corporate_postal' => 'the postal address does not appear to be a > >> personal postal address', > >> - '@invalid_public' => 'the public name should be a real name and not a > >> user id', > >> + '@invalid_public' => 'the public name should be a real name or pen name > >> and not a user id', > > > > Is there a reason why we disallow user ids for public names? > > > > It does not make sense to me to discriminate on that basis. > > > > > >> '@separate_signature' => 'the document and signature must be sent > >> attached to the same email', > >> '@unauthorized_signature' => 'the signature must be from an authorized > >> person, usually a company executive', > >> '@empty_form' => 'the form appears to be completely empty', > >> >
