I would say to support Ben getting the voting open the day after collection
ends, it is important for the IoT to be continuously vetting the
contributions as they coming in Mar 2-16. I'm teaching all week but I'll
add it to my calendar to review names while proctoring the exam at the end
of the week.
It has been a long time since I (or any of) was involved in naming Fedora
releases but I remember the submission wiki having some guidelines for what
to check before submitting a name so it would not get tossed as an obvious
bad candidate.
Will the collection wiki have a place for noting that a name will be
discarded as a bad candidate?
I'm too lazy to review those ancient pages but I have faith in Ben
researching that stuff before creating the page :)
-Susan
On Thu, Feb 27, 2020 at 2:57 PM Geoffrey Marr <gmarr(a)redhat.com> wrote:
This looks great to me. The only thing that I see that stands in the
way
of us using the second option and getting the name to legal faster is,
well... How quickly bcotton wants to set up the election app. :P
Ben, if you're alright with getting the election going the day after
potential name collection ends, I'm +1 to option 2. You can count on some
help from me getting that going should we decide to go that route.
Geoff Marr
IRC: coremodule
On Thu, Feb 27, 2020 at 12:40 PM Ben Cotton <bcotton(a)redhat.com> wrote:
> As discussed in yesterday's meeting, here's a draft plan for naming
> the IoT edition. Note that this gives Legal a fairly short window to
> vet and approve our final names, so I've also prepared a compressed
> version (that's still a short window for Legal, but slightly less
> short). Either way, we should come to agreement quickly and I'll post
> the wiki page first thing Monday (my) morning.
>
> I'm open to other suggestions (e.g. a shorter name suggestion window),
> but we do need to move quickly.
>
> ## Schedule 1
> 2 March: Begin collecting name suggestions on the wiki page (bcotton to
> create)
> 16 March: End name collection, IoT team removes obvious bad candidates
> 20 March: bcotton sets up an election in the Elections app (open to
> all contributors with CLA+1)
> 23-30 March: voting period for naming
> 31 March: top 3 names sent to Red Hat Legal for final vetting
>
>
> ## Schedule 2 (compressed)
> 2 March: Begin collecting name suggestions on the wiki page (bcotton to
> create)
> 16 March: End name collection, IoT team removes obvious bad candidates
> 17 March: bcotton sets up an election in the Elections app (open to
> all contributors with CLA+1)
> 18-25 March: voting period for naming
> 26 March: top 3 names sent to Red Hat Legal for final vetting
>
>
> --
> Ben Cotton
> He / Him / His
> Senior Program Manager, Fedora & CentOS Stream
> Red Hat
> TZ=America/Indiana/Indianapolis
> _______________________________________________
> IoT mailing list -- iot(a)lists.fedoraproject.org
> To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
>
_______________________________________________
IoT mailing list -- iot(a)lists.fedoraproject.org
To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
--
Susan Lauber, (CCAH, RHCX, RHCA, RHCSS, RHCVA, CISSP)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974