Draft: 0003-name-change-plan
This is still draft. Leaving it here so we can slowly and collectively contribute to planning what is needed for a transition go to without major hickups
Merge request reports
Activity
added ongoing label
assigned to @pabloyoyoista
mentioned in issue postmarketos.org#195
mentioned in issue artwork#17 (closed)
- 0003-name-change-plan.md 0 → 100644
116 3. Add new aliases for matrix rooms 117 4. Rename gitlab group and repositories with the name 118 5. Create email aliases for everybody? 119 5. Do a blog post as retrospective 120 121 ### The proposer 122 123 Pablo Correa Gomez, a Core Contributor. I am basically opening this so we can 124 start discussing on things that need change, and start drafting a plan. I do not 125 have infra access, but could totally do any parts of the other work. 126 127 ### Blocking issues 128 129 * Decide on voting mechanism. We need to make sure that we have a voting process 130 that is fair with a situation that is not black and white, but people might 131 have multiple acceptable preferences. - Comment on lines +129 to +131
FWIW Linux TAB uses CIVS for ranked-choice voting, could use that (or equivalent process) for at least initial rounds of thinning the list.
There needs to be a formal criteria which is used to evaluate how much the name suits the project. E.g. you've mentioned that postmarketOS is a name which is hard to pronunciate, while some people may think it's not that hard. Then it needs to be determined which letters/sounds should not be present in the name in addition to the rules those have been introduced in the blog post. Like a lot of people going to have a problem with "th". Using "j" is questionable. In general, just aim for a name which can be pronounced almost uniformly in any language. The best fitting example is "Android"
The other part of criteria is search optimization and localization. I'm not an expert in this, but my idea is that you have to check the name in multiple search engines and multiple languages, because an innocent name may give bad results here or there. E.g. Lumia in Spanish (https://es.wiktionary.org/wiki/lumia) or "wayland" search in Yandex.Images.
There might be more parts which I didn't think of, think of it as a reference for voting, each part can be given an importance score and then names can be rated via total score which is a sum of importance*rating given by team member for that part.
Edited by Anri Dellal
0003-name-change-plan.md 0 → 10064480 ## Draft implementation plan 81 82 The plan has too parts: 83 84 ### Finish making the decision 85 86 1. Set a deadline for the collection of names in the form 87 2. Discuss different alternatives withing CC and TC team 88 3. Research trademarks of the alternatives. postmarketOS was not possible 89 to trademark. 90 4. Come with a set of preferred alternatives (2, 3, 4?), and vote on them. 91 Voting should probably be done in a way that people's preferrences are 92 respected (and not top 1). Asking for votes outside the team was deemed 93 not-appropriate due to the risk of trolling (e.g: people registering 94 domains or trademarks). Finding some alternative so it can be discussed with 95 a broader community would be great. - Comment on lines +86 to +95
After v25.06 is released (depending on how much is to do, maybe one or a few weeks after) would be a good time to start the voting process.
My suggestion / what we just discussed in the Core Contributors meeting is: each of the Core Contributors and Trusted Contributors takes a look at all submitted name ideas and picks the ones they like. Then we take this list and discuss them in depth, until we land on one we like. (If we don't find one we like, then obviously we don't move forward).
Edited by Oliver Smith
