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
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@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@lists.fedoraproject.org To unsubscribe send an email to iot-leave@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
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@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@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@lists.fedoraproject.org To unsubscribe send an email to iot-leave@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@lists.fedoraproject.org To unsubscribe send an email to iot-leave@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
On Thu, Feb 27, 2020 at 3:14 PM Susan Lauber laubersm@fedoraproject.org wrote:
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.
Agreed. Setting up the election will be a fairly quick process. It's the vetting of names that will take time, so if we're doing that as we go, that helps.
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'd planned on saying we'll reject: - Trademarks - Obviously offensive/derogatory names (or initialisms) - References to living people
Anything else we should add to the rejection list? I'll also include an optional "explain why this ties in to IoT" so that if it's an in-community reference, we can consider that.
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.
Agreed. Setting up the election will be a fairly quick process. It's the vetting of names that will take time, so if we're doing that as we go, that helps.
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'd planned on saying we'll reject:
- Trademarks
- Obviously offensive/derogatory names (or initialisms)
- References to living people
Anything else we should add to the rejection list? I'll also include an optional "explain why this ties in to IoT" so that if it's an in-community reference, we can consider that.
Just refer to "IoT or device edge".
All the rest of this looks good to me. Thanks for kicking this off.
Peter
Okay, I went with the short schedule, slightly adjusted (I made the end date for name submissions the 15th for the sake of less ambiguity, but we can take late submissions).
Peter just published a Community Blog post: https://communityblog.fedoraproject.org/help-us-name-the-fedora-iot-edition/
Spread the word and help us get some not-crappy names :-D
On Mon, Mar 2, 2020 at 4:24 PM Ben Cotton bcotton@fedoraproject.org wrote:
Okay, I went with the short schedule, slightly adjusted (I made the end date for name submissions the 15th for the sake of less ambiguity, but we can take late submissions).
Peter just published a Community Blog post:
https://communityblog.fedoraproject.org/help-us-name-the-fedora-iot-edition/
I have to say I'm somewhat confused by this. Why don't we keep using "Fedora IoT" name? Why do we need a new name, most probably much less clear about the edition's purpose?
On Tue, Mar 3, 2020 at 11:32 AM Kamil Paral kparal@redhat.com wrote:
On Mon, Mar 2, 2020 at 4:24 PM Ben Cotton bcotton@fedoraproject.org wrote:
Okay, I went with the short schedule, slightly adjusted (I made the end date for name submissions the 15th for the sake of less ambiguity, but we can take late submissions).
Peter just published a Community Blog post: https://communityblog.fedoraproject.org/help-us-name-the-fedora-iot-edition/
I have to say I'm somewhat confused by this. Why don't we keep using "Fedora IoT" name? Why do we need a new name, most probably much less clear about the edition's purpose?
The reasons were discussed a number of times in the meetings so I would check out the meeting notes.
But it comes down, and I'm missing a lot of detail here, "edge" "device edge" "IoT" means a lot of different things to different people. Also similar reasons to the different naming for things like SilverBlue, CoreOS, or Atomic.
Peter