Archived
15
23
Fork
You've already forked meta
6

Pick a name #1

Closed
opened 2022年11月06日 11:06:13 +01:00 by Ghost · 15 comments

The selection process is as follows:

  • Put the names below in a separate pad
  • Create a sub-heading behind each name
  • Where people can leave their vote + some short remarks.
  • Maybe people can choose 3 options 1. 2. 3. that relate to points.
  • After voting round ends, count points and select top 3 (or 5) as shortlist.
  • Create a new pad with these.
  • Describe what we need to find out that is important for the choice (a bullet list of factors)
  • Now add pros and cons to the remaining names
  • Discuss
  • Another vote, and done.
The selection process is as follows: * Put the names below in a separate pad * Create a sub-heading behind each name * Where people can leave their vote + some short remarks. * Maybe people can choose 3 options 1. 2. 3. that relate to points. * After voting round ends, count points and select top 3 (or 5) as shortlist. * Create a new pad with these. * Describe what we need to find out that is important for the choice (a bullet list of factors) * Now add pros and cons to the remaining names * Discuss * Another vote, and done.
Ghost added this to the Launch milestone 2022年11月06日 11:06:51 +01:00

@fr33domlover Codeberg e.V. has informally agreed to the proposal. It means launching the fork as soon as next week is a possibility. This is great news but also means picking the name is now a blocker to the launch, which is more pressure than there was 24h ago 😅

@fr33domlover Codeberg e.V. has informally agreed to the proposal. It means launching the fork as soon as next week is a possibility. This is great news but also means picking the name is now a blocker to the launch, which is more pressure than there was 24h ago 😅
Contributor
Copy link

Working on it 👍

Working on it 👍

This is the pad for choosing the name: https://pad.gusted.xyz/WaHYGTUDSqWkWZ-B6PwhFw#

This is the pad for choosing the name: https://pad.gusted.xyz/WaHYGTUDSqWkWZ-B6PwhFw#

Hi, since you're discussing whether the new name should include "Git", I just wanted to alert you that the Software Freedom Conservancy has a trademark for "Git" and their trademark policy explicitly prohibts a use like this without permission:

In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a portmanteau to refer to a product or service's use of Git code.

Back in 2017, when they introduced the policy, they retroactively allowed a few existing projects like GitHub and GitLab to keep their name:

So GitHub is essentially outside the scope of the trademark policy, due to the history. We also decided to explicitly grandfather some major projects that were using similar portmanteaus, but which had generally been good citizens of the Git ecosystem (building on Git in a useful way, not breaking compatibility). Those include GitLab, JGit, libgit2, and some others. The reasoning was generally that it would be a big pain for those projects, which have established their own brands, to have to switch names. It's hard to hold them responsible for picking a name that violated a policy that didn't yet exist.

(Sorry if you're already aware of this but I didn't see any mention in the pads, so I thought it was better to bring this up before you've decided on a name.)

Hi, since you're discussing whether the new name should include "Git", I just wanted to alert you that the Software Freedom Conservancy has a trademark for "Git" and their [trademark policy](https://git-scm.com/about/trademark) explicitly prohibts a use like this without permission: > In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a portmanteau to refer to a product or service's use of Git code. Back in 2017, when they introduced the policy, they [retroactively allowed a few existing projects like GitHub and GitLab to keep their name](https://public-inbox.org/git/20170202022655.2jwvudhvo4hmueaw@sigill.intra.peff.net/): > So GitHub is essentially outside the scope of the trademark policy, due to the history. We also decided to explicitly grandfather some major projects that were using similar portmanteaus, but which had generally been good citizens of the Git ecosystem (building on Git in a useful way, not breaking compatibility). Those include GitLab, JGit, libgit2, and some others. The reasoning was generally that it would be a big pain for those projects, which have established their own brands, to have to switch names. It's hard to hold them responsible for picking a name that violated a policy that didn't yet exist. (Sorry if you're already aware of this but I didn't see any mention in the pads, so I thought it was better to bring this up before you've decided on a name.)

Thanks for raising this: it is indeed a legal risk. As a member of Codename I believe this is a legal risk that is in the acceptable range. The odds that it manifests itself requires that:

  • Software Freedom Conservancy engage a legal action against the project
  • They obtain a favorable first ruling although there is a bazillion organizations doing the same

In addition it would be the first time in history that SFC tries that. Unlike copyright, a trademark that is never actively enforced becomes increasingly difficult to enforce as time passes.

Thanks for raising this: it is indeed a legal risk. As a member of Codename I believe this is a legal risk that is in the acceptable range. The odds that it manifests itself requires that: * Software Freedom Conservancy engage a legal action against the project * They obtain a favorable first ruling although there is a bazillion organizations doing the same In addition it would be the first time in history that SFC tries that. Unlike copyright, a trademark that is never actively enforced becomes increasingly difficult to enforce as time passes.

For the record, a copy of the pad used to propose names

Feedback for Gitea fork's name choice

Written by fr33domlover, public domain under CC0.

Starting to collect feedback: 2022-Nov-7. Hoping to process the feedback by: 2022-Nov-13.

There are 3 sections here. Please read all 3 and add your comments according to the instructions. This will help us pick the name that most fits what's important to us and most advances us towards our vision and purpose!

(1) Common criteria

These are criteria on which I didn't find conflicts, let's see if we all agree on them:

  • Short simple name, easy to remember and identify visually, not weird to pronounce
  • Desirable/relevant domain name(s) are available for us to rent
  • If we pick a name identical/similar to a name of some popular commercial product, be sure there's no real risk of being sued by that company for using the name
  • Alignment with vision: Free software development lifecycle (FSDL) that:
    • Uses Free Software for the tools themselves, including the forge software
    • Supports community, participation, healthy collaboration, thriving of developer and maintainer teams
    • Orients towards filling actual human needs rather than maximizing profit
  • Has a background story of our FLOSS culture and its vision, to which the name refers, relates, fits
  • Have branding that is less attractive for the corporates, appealing for FOSS folks

Do you accept this basic set of criteria? Do you have concerns or worries about any of them? Please add a line below explaining your thoughts. The first 2 lines are just examples.

  • Alice: I approve these considerations
  • Bob: I'm not sure having a background story is relevant. Different people have different stories. I'd like to appeal both to the free software community, and to the open-source-corporations who don't care about software freedom. Thoughts?
  • fr33domlover: Seems fine to me, all of these seem important
  • circlebuilder: Seems fine to me too (PS. I added FSDL acronym above)
  • tallship: I don't know why branding that is unappealing to corporations is relevant - The Apache Foundation and The Document Foundation are corporations like most FOSS projects desirous of protecting their brands, identities, intellectual property, and products. Also, "unambiguous" should be a requirement for a domain name "registraion" (not "rental"). i.e., "4sale.tld" is ambiguous.
  • Ryuno-Ki: „Supports community, participation, healthy collaboration, thriving of developer and maintainer teams" puts developer and maintainer on a pedestal. Can we just speak of teams?
  • fnetX: agree, but want to point out that "weird to pronounce" is highly subjective. I liked Gitea, but some found it weird to pronounce ... I think that pronounciation should mostly be intuitive to most, so they don't think about it. It's OK if folks pronounce it the "wrong way", if their intuitive way of speaking differs.
  • Gusted: Agrees the points and with tallship's comment about branding that's unappealing for corporations.
  • fundur: I think the rules are good and help the project to not get in trouble.
  • Dodecahedron: These rules look good to me.
  • Oliverpool: agree with tallship (overall good / unappealing for corporations not needed IMHO)
  • Caesar: Agree with most points, also agree with tallship that "unappealing to corporations" is unnecessary and perhaps unproductive (better to think about positives than negatives).
  • Add your line here...

(2) Controversial criteria

Now, there are also a few choices to make, directions to pick. The following criteria are in some conflict:

  • Use "Git" in the name, so that it resembles "Git" and "Gitea"
  • Use a VCS-agnostic name, so that support for other VCSs can be added without having to change the name
  • Avoids overused naming such as "Libre" and even "Git". This brings it to GNU-like FOSS fanatic only appeal

Which brings us to 2 questions:

  1. Is it important to us, and do we expect, to have support for more VCSs in addition to Git?
  2. Do we want to avoid the overused "Git" and "Libre" and pick something more original? Or use these terms, to highlight our values (Libre) and our toolchain (Git, Gitea)?

Do you have thoughts, preferences about these questions? What is important to you? You may comment here be by adding a line below. If you aren't sure, this is okay, you can proceed to the next section. (The first 2 lines below are just examples.)

  • Alice: I use only Git, but I know other people use things like Mercurial, Fossil, etc. and I'd also like to allow for innovation in VCSs and not declare ourselves as Git-specific (e.g. there's a GitLab fork called Heptapod that adds Mercurial support; why not have such support integrated right into our Gitea fork, if people wanted that?)
  • Bob: I'm okay with all these options, but I'd prefer to have "Libre" in the name, to emphasize we're committed to be fully FLOSS forever
  • fr33domlover: I can live with either, but leaning towards an original name without "Git" and "Libre", they indeed seem overused to me
  • SiB64: I second that, no libre please.
  • circlebuilder: I am advocating as mentioned in 1) for seeing the 'code forge' (an app) in a broader light, i.e. "forging free software". As mentioned this covers the entire FSDL. And potentially many, many different functionalities (think GH and GL here). Hence, no "Libre" and no "Git" as that is too narrow.
  • tallship: ditch FLOSS (and Libre), it's redundantant (sic), like "Mount Fujiyama" is redundant. Also, I think "fanatic" is rather offensive and "zealot" more appropriately describes that level of passion.
  • Onepict I see software like gitea or other web frontends as a community hub. Folks tend to coalese and interact on various websites. They become community hubs. Just because this is mainly focused on code building doesn't make it very different. Git and VCs can often be very powerful organisational tools. So choosing a name to encourage that idea of community of building not just projects but that community is important.
  • fnetx: I think that "Git" in the name narrows the scope of the project. It's software development. VCS is a core part, yes, but issue communication channels (e.g. issue trackers), review tooling and other features are important, too. But I would not have this as a strict criteria: If we find a "good" name that fits our other criteria, it should be okay to have both parts in it ("GitLibre" xD). I think that having other VCS support (as plugins?) could be a potential feature, yes.
  • Gusted: While I doubt if Gitea ever incorporate another VCS system, I'd like the idea to not be tied to the "Git" name and instead allow a broader set of names. Be it more forge-centric name.
  • Dodecahedron: I'd prefer something original without "Git" or "libre", but I'm also fine if the name does contain them.
  • Caesar: I'd also prefer to see something without 'Git' and especially without 'Libre', which to me makes the name sound formal, boring, and unmemorable.
  • Daniele: I agree with Caesar, 'Git' could be avoided in the name and 'Libre' sound a bit pedantic (perhaps since it's mostly used in "Free Libre Open Source Software")
  • Ryuno-Ki: I assume, there won't be any other VCS than git for the time being. Perhaps hq at best. I second fnetx and Gusted here. I understand why some people would like to have Libre, but I find it too confusing (e.g. OpenOffice vs. LibreOffice)

(3) Choosing the name!

Please go over all the proposed names first. Make 3 lists below like in the Alice example below, with the same titles as in the example. Any name you don't mention, is considered "a name you could live with", so especially put emphasis on listing all the names you don't like or have concerns about!

  • Alice

    • 1-3 names I'm most excited about + short why
      • Smithy (sounds great and original, fits forgers guild vision, fits forge metaphor)
      • Smelt (same)
    • Names I can happily live with
      • Artisan
      • Gimli
      • Smithea
      • Gitoffee
    • Names I don't like + why/concerns
      • Telibre (doesn't communicate it's a forge, "libre" takes most of the name's length)
      • ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi(b) (none sound catchy enough to me)
      • The names in non-english languages/translations, they sound kinda weird to me (unless you speak that language?)
      • Brigid (sounds like Frigid? And like Brigitte Bardot?)

  • circlebuilder

    • Names most excited about (unsurprisingly)
      • Smithy (dictionary substitute for forge, fits friendlier narrative, fits Forgers Guild concept real well)
    • Names I can happily live with
      • Forge
      • Smithea (though a bit too much dependence / reactionary to Gitea)
      • Gitenburg (name with "git" I dig, but only if a true project provided by Codeberg under same branding)
    • Names I do not prefer
      • forgefriends (great name, but keep it where it is)
      • Smelt (was doubting here, but not so familiar name for non-english folks, plus association with past tense "smells")
      • Furnace (too unspecific, the furnace at home / the bakery / the pizzeria, etc)
      • The remaining candidates

  • talkship:

    • names I like the most:
      ForgeFed it's the name of the project from which this effort was derived. the domain name is already registered and under our control (forgefed.org). The Domain Name is
    1. ) Short
    2. ) Meaningful
    3. ) Relevant
    4. ) Unambiguous
    • names I can live with:
      pretty much anything without the word "Libre" in it, and "Furnace" is actually a pretty good RCS agnostic noun that meets the four requirements above too, and rolls off the tongue nicely.
    • names I really don't much prefer:
      Anything with the word "Libre" or "FLOSS" in it. I don't care for the word "smith" to refer to a non person either very much, and it doesn't have enough consonance when it rolls off the tongue either, IMO. i.e., a Smith is a person, a forge is a thing, but I could actually live with simply "Smithy". Just my 2¢

  • Onepict

    • 1-3 names I'm most excited about
      • Smithy - I liked this from the beginning.
      • Forgejo - I like Esperanto, the language is about finding community together through language as it takes words from lots of languages.
      • Hearth - This I like, as I tend to see front end software for organising and managing issues as your community hub. This fosters that feeling.
    • Names I can happily live with
      • Atelier
      • Furnace
      • gimli
    • Names I don't like + why/concerns
      I think we want a fresh start for this fork. We also want to be VCS agnostic in the future.
      So anything with Git, Libre or Open, I don't think is a good idea. We want to foster colaboration and this fork is also about forge federation. Ideally we want this to reach beyond FOSS.
      Smelt is too close to smelling as past tense in English

  • dachary

    • Names most excited about
      • Smithy
      • LibreForge
      • FediForge
    • Names I can happily live with
      • Forge
      • Smithea
      • Gitenburg
    • Names I do not prefer
      • none

  • fnetX

    • 1-3 names I'm most excited about + short why
      • FediForge (most interesting aspect)
      • Forja, Fucina, Forgejo: Interesting and simple
    • Names I can happily live with
      • GitLibre
      • Gitoli (althogh conflicting with Gitolite a little)
      • LibreForge, OpenForge (simle, but boring)
      • Forgo (although a little weird)
      • Smelt, Smithy
      • Atelier (or Gitelier?): maybe too few relation to software?
      • CodeLab (boring, but ok)
      • Smithea
      • Gitoffee
      • GitSmith
    • Names I don't like + why/concerns
      • Telibre: Very unintuitive, you don't think of a forge
      • sago, chago etc: only sticking to the tea part is weird
      • GoForLib: weird
      • Gitenberg
      • Gitli (conflict with Gitly)
      • ForgeLib, ForLibre, Forli(b): forge library and freedom fights?
      • Brigid (unintuivie relation, sounds agressive to me, and I don't like gods)
      • Gimli (not a fan of series or movies)

  • Gusted

    • 1-3 names I'm most excited about + short why:
      • Smithy: really a good thoughtfull name for any forge, not specific to a "Gitea fork".
      • Artisan: The meaning of this word has something to do with forges.
    • Names I can happily live with
      • LibreForge, well it's FLOSS-centric, I think it's intuitive and simple.
      • Smithli, see reason for Smithy.
      • forgefriends, bit awkward as it would change the meaning of Forgefreinds, but otherwise like the name.
      • sago, chago, cha-go-yu, Like the name but doesn't really have any relevance to a fork.
    • Names I don't like + why
      • Gitenberg: Feels like Codeberg chose this name + git-centric.
      • GitLibre, GitSmith, GitoLi, GitLi: Git-centric.
      • Telibre: FLOSS-centric not related to a forge.
      • ForgeLi(b), ForLibre, ForLi(b): "li" is awkward to pronounce.
      • GoForLi(b), ForGo: Lets not continue the trend of adding the program language to it. Feels like: We made (for the first time) something interesting in X language, which is not the case.
      • OpenForge: "open" is broad.
      • Fed(i)Forge: Big scam, Gitea isn't even federated yet.
      • Brigid, Brigit: Theist-centric.
      • Smelt: This is a verb
      • Atelier: Branding this would be quite hard.
      • CodeLab: Cannot get rid of a reference to "GitLab".
      • Smithea, Gitoffee: Reference to drinks again.

  • Dodecahedron

    • 1-3 names I'm most excited about + short why:
      • Forja, Fucina, Forgejo: These don't include "Git" or "libre" and sound nice.
    • Names I can happily live with
      • Gitoffee
      • Smithy
    • Names I don't like + why
      • Gitenberg, GitLibre, Telibre, GitoLi, ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi: weird spellings or sound awkward or cumbersome when pronounced

  • Oliverpool

    • 1-3 names I'm most excited about + short why:
      • Forgejo: short and memorable, seems easy to pronounce in many languages
      • Githea
    • Names I can happily live with
      • Smithea: nice to have a link to the previous project (see below regarding "th")
      • Smithy: main drawback, the "th" is quite english-centric
    • Names I don't like + why
      I can happily live with any name

  • Caesar

    • 1-3 names I'm most excited about + short why
      • Smithy (sounds great and original, fits Forgers' Guild vision, fits forge metaphor)
      • Furnace
      • Smelt
    • Names I can happily live with
      • Atelier
      • Gimli
      • Garfo
      • Forja, Forgejo
      • CodeLab – a bit generic but I quite like the 'lab', might be worth thinking about more names around that
      • GitSmith - if we wanted Git in the name (though I prefer not to have it)
    • Names I don't like + why/concerns
      • Telibre – doesn't communicate it's a forge, 'libre' takes most of the name's length
      • ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi(b) – none sound catchy enough to me + don't like 'libre'
      • GitoLi or GitLi – ditto plus too close to Gitolite
      • GoForLi(b), ForGo – ditto, plus I don't like having the language in the name
      • sago, chago etc – only sticking to the tea part is weird
      • ForgeFriends, Fed(i)Forge – we don't have federation yet, and we hope other forges will have it in future, so it's not a distinguisihng feature
      • Gitoffee, Giteine – I don't think emphasizing being a Gitea fork is important, and I don't like Git in the name

  • codedotjs

    • 1-3 Names I'm most excited about + short why
      • Smithea: good mixture of Smithy and Gitea (Smithy looks too much like a name). Includes both the Gitea (history) and Smithy (forging code) aspects. I added Smitty/Smittea to the name list in case we want to avoid the "th".
      • CodeLab: Two syllables thus easy to remember. Fits the names of Codeberg (hosting platform - shows where the project comes from) and GitLab (a similar project - people reading the name will instantly think of a git web client). A lab is similar to a smithy but with the focus on experimenting rather than building things after a fixed plan.
      • Forgejo: Esperanto wants to be an easy language for as much people as possible. This is also kind of what we want with our project. The forging aspect is also applied here. In other words: "A place where people all around the world are forging code together."
    • Names I can happily live with
      • Smithy, Forja, Atelier
      • Brigid, Gimli
      • sago, chago, cha-go-yu
      • Gitsmith
      • Gitoffee, Giteine
      • Tisane
      • Codebox, Codeshelf, Codecup
    • Names I don't like + why/concerns
      • Telibre: Sounds like telephone or television to me.
      • GitLibre: If we want to link the name to GitHub or GitLab it should be pronounced as easy as they are. GitLibre has three syllables.
      • Gitenberg: Git in a german word looks like "Gift" (poison) on first sight.
      • forgefriends: This should be the name of a group not a software.
      • Fed(i)forge: As already mentioned above this should only be applied if Gitea gets federation support in the future.
      • Codebin: sounds like a pastebin instance
      • Gitorium: Not intuitive for a non english speaker. Ressembles at Imperium (empire).

  • Daniele

    • 1-3 names I'm most excited about + short why
      • Tisane (like tea but without caffeine, suggests me the link to the original project without the greed. Quick, easy and refreshing)
      • Atelier (a place where one can build nice things. I like it very much!)
    • Names I can happily live with
      • Gimli
      • Smithy
      • Forgejo
      • CodeLab (perhaps a bit too CodeBerg-like, but ok nevertheless)
      • sago, chago
    • Names I don't like + why/concerns
      • GitSmith. Git* - I don't like the idea of "Git" in the name, especially to begin with it since it adds a strong connection to the original project
      • *Libre - I don't like the idea of "Libre" in the name
      • Garfo, Smelt - sound weird in my own language (I'm italian)
      • Hearth - too generic
      • Furnace - too hot :)
      • ForgeFriends, Fed(i)Forge – we don't have federation yet, and we hope other forges will have it in future, so it's not a distinguisihng feature

  • KaKi87

    • Names most excited about
      • ForgeFed : I fully support the idea of federation taking a central place in the project.
    • Names I can happily live with
      • LibreForge : speaks for itself.
    • Names I don't like + why/concerns
      • Smithy, Smelt, Artisan, Smithli, Hearth, Atelier, GitSmith, Smithli : non-native speakers may not guess the meaning of these names at first glance.
        • Artisan : can also be confused with Laravel software.
        • Atelier : despite that fact, I actually do like it.
      • Gimli, Brigid : people unfamiliar with the origin of those names may not guess their meaning at first glance.
      • Smithea, Gitoffee, Giteine, Tisane : controvertial reference to Gitea and/or drinks.
        • Smithea : cf. Smithy
        • Tisane: despite that fact, I actually do like it.
      • Telibre, Forgo, Forgejo, Forja, Fucina, sago, chago, GoForLib, cha-go-yu : I can't find the meaning of those names.
        • Telibre : also homophone of French "t'es libre".
      • (Git|For|Forge)Li(b(re)), Gitenburg, forgefriends, Furnace, Fed(i)Forge, Gitoli, OpenForge, Gitelier, CodeLab : subjectively sounds unattractive.
      • Forge : too generic.

  • Sanjibukai

    • Names most excited about
      • forgit : Short for "Forge it" while knowing that's a git server (Let's be honest most of the people is using Git)
      • forgeit : This one I added after checking that 'geit' actually means somehow goat.. And we can then keep "Forge it" and have a Goat as a mascot? This mountain climbing animal somehow can be related to the forge/smiths
    • Names I can happily live with
      • everything that's <=7 characters
    • Names I do not prefer
      • everything else

  • JustPassingBy

    • Names most excited about
      • Latte - beverage theme, short and nice
      • Giticious - git + delicious
      • Gitorium - code emporium (but combines with git a lot better)
      • Codeshop - code workshop
      • Codeshelf, Codebox - storage theme
    • Names I can happily live with
      • Atelier
      • Smithy
      • Forge
      • Tisane
      • Giteine
      • CodeLab
      • CodeForge
    • Names I do not prefer
      • libre/open/etc. - sounds boring/nerdy
      • berg/burg - something feels wrong with these, idk

  • Ryuno-Ki

    • Names most excited about
      • Artisan
      • Atelier
      • Sago (yummy - we have a dish with yeast dumplings and sago for a fruit sauce)
      • Chagoyu (I'm a tea lover)
      • Smithea
    • Names I can happily live with
      • Smithy
      • Gitenberg
      • Smithli
      • Smelt (possible confusion with Svelte when hearing)
      • Furnace
      • Brigit (could be considered sexist?)
      • Gitmate (mate as in partner?)
      • Codeshop (a bit boring, though)
    • Names I do not prefer
      • GitLibre
      • Telibre, Tisane (too far fetched)
      • GitoLi / GitLi (too easy too confuse, would have to be spelled)
      • ForgeLi(b), LibreForge, ForLibre, ForLi(b) (I don't like the casing, but without you struggle with reading)
      • GoForLi(b) (go for what?)
      • ForGo (foregone)
      • OpenForge
      • LibreForge
      • Fed(i)Forge (Fed as in fat?)
      • Forkly, Forkit, Forkist, Forklift (sounds more like knife and spoon than like VCS)
      • Herrero, Ferreiro (did you mean Ferrero?)
      • Faber (like the German company Faber-Castell?)
      • Gimli (I fear trademark issues. Tolkiens family have a reputation...)
      • CodeLab (taken by several, among them Google)
      • Gitoffee
      • Giteine
      • GitSmith (sounds like a name)
      • Latte (hard to search. See also programming language R)
      • Giticious (I already had trouble with del.icio.us)
      • Gitorium

  • steko

    • Names most excited about
      • Forgejo, I like the "forge" meaning, I like Esperanto
    • Names I can happily live with
      • Smithy
      • FediForge
      • Furnace
      • forgefriends
      • CodeForge (I'm not sure it's in the list but it's a nice variation of the various word combinations .. to my ears)
    • Names I do not prefer
      • Forge or Smithy in other languages (apart from Forgejo, see above)
      • Gitenberg, sounds too specific to this moment of change rather than a long-lasting name, I don't like having Git in the name
      • GitLibre, I don't think "git" should be in the same, it sounds very amateurish to just juxtapose two words, and "libre" is overused
      • Telibre, "libre" is overused
      • Gitoli or Gitli
      • ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi(b)
      • GoForLi(b), ForGo, ...
      • OpenForge
      • Brigid (the entire initiative is already abundantly Europe-centric without adding Celtic goddesses to the mix)
      • Blacksmith in other languages
      • Gimli (pretty sure the Tolkien Estate is going to sue asap)
      • CodeLab (too similar to GitLab)
      • sago, chago, cha-go-yu - I don't see why the "tea" from upstream should be kept
      • Smithea, same as above
      • Gitoffee
      • Gitmate, already in use (?)
      • Giteine (no Git in the name)
      • GitSmith (no Git in the name)
      • Gitorium (no Git in the name)
      • Giticious no Git in the name)
      • Tisane (too generic)
      • Latte (too generic)
      • Codeshop
      • Codeshelf or similar (storage theme) ... but see CodeForge above

  • Add your own 3 lists here...

(4) What's next

Once we gather everyone's feedback into this pad, I'll prepare a summary of results, with the best options we picked, and we'll see if there's one that fits all criteria the most, and that nobody opposes :-)

Feedback/questions/concerns about this document itself, or about the selection process? Write to fr33domlover on Matrix (@fr33domlover:matrix.org) or on the Fediverse (@fr33domlover@todon.nl).

For the record, a copy of the pad used to propose names --- # Feedback for Gitea fork's name choice *Written by [fr33domlover](https://todon.nl/@fr33domlover), public domain under CC0.* *Starting to collect feedback: 2022-Nov-7. Hoping to process the feedback by: 2022-Nov-13.* There are 3 sections here. **Please read all 3 and add your comments according to the instructions**. This will help us pick the name that most fits what's important to us and most advances us towards our vision and purpose! ## (1) Common criteria These are criteria on which I didn't find conflicts, let's see if we all agree on them: - Short simple name, easy to remember and identify visually, not weird to pronounce - Desirable/relevant domain name(s) are available for us to rent - If we pick a name identical/similar to a name of some popular commercial product, be sure there's no real risk of being sued by that company for using the name - Alignment with vision: Free software development lifecycle (FSDL) that: * Uses Free Software for the tools themselves, including the forge software * Supports community, participation, healthy collaboration, thriving of developer and maintainer teams * Orients towards filling actual human needs rather than maximizing profit - Has a background story of our FLOSS culture and its vision, to which the name refers, relates, fits - Have branding that is less attractive for the corporates, appealing for FOSS folks Do you accept this basic set of criteria? Do you have concerns or worries about any of them? **Please add a line below** explaining your thoughts. The first 2 lines are just examples. - Alice: I approve these considerations - Bob: I'm not sure having a background story is relevant. Different people have different stories. I'd like to appeal both to the free software community, and to the open-source-corporations who don't care about software freedom. Thoughts? - fr33domlover: Seems fine to me, all of these seem important - circlebuilder: Seems fine to me too (PS. I added FSDL acronym above) - tallship: I don't know why branding that is unappealing to corporations is relevant - The Apache Foundation and The Document Foundation are corporations like most FOSS projects desirous of protecting their brands, identities, intellectual property, and products. Also, **"unambiguous"** should be a requirement for a domain name *"registraion"* (not "rental"). i.e., "4sale.tld" is ambiguous. - Ryuno-Ki: „Supports community, participation, healthy collaboration, thriving of developer and maintainer teams" puts developer and maintainer on a pedestal. Can we just speak of teams? - fnetX: agree, but want to point out that "weird to pronounce" is highly subjective. I liked Gitea, but some found it weird to pronounce ... I think that pronounciation should mostly be intuitive to most, so they don't think about it. It's OK if folks pronounce it the "wrong way", if their intuitive way of speaking differs. - Gusted: Agrees the points and with tallship's comment about branding that's unappealing for corporations. - fundur: I think the rules are good and help the project to not get in trouble. - Dodecahedron: These rules look good to me. - Oliverpool: agree with tallship (overall good / unappealing for corporations not needed IMHO) - Caesar: Agree with most points, also agree with tallship that "unappealing to corporations" is unnecessary and perhaps unproductive (better to think about positives than negatives). - **Add your line here...** ## (2) Controversial criteria Now, there are also a few choices to make, directions to pick. The following criteria are in some conflict: - Use "Git" in the name, so that it resembles "Git" and "Gitea" - Use a VCS-agnostic name, so that support for other VCSs can be added without having to change the name - Avoids overused naming such as "Libre" and even "Git". This brings it to GNU-like FOSS fanatic only appeal Which brings us to 2 questions: 1. Is it important to us, and do we expect, to have support for more VCSs in addition to Git? 2. Do we want to avoid the overused "Git" and "Libre" and pick something more original? Or use these terms, to highlight our values (Libre) and our toolchain (Git, Gitea)? Do you have thoughts, preferences about these questions? What is important to you? You may comment here be by **adding a line below**. If you aren't sure, this is okay, you can proceed to the next section. (The first 2 lines below are just examples.) - Alice: I use only Git, but I know other people use things like Mercurial, Fossil, etc. and I'd also like to allow for innovation in VCSs and not declare ourselves as Git-specific (e.g. there's a GitLab fork called Heptapod that adds Mercurial support; why not have such support integrated right into our Gitea fork, if people wanted that?) - Bob: I'm okay with all these options, but I'd prefer to have "Libre" in the name, to emphasize we're committed to be fully FLOSS forever - fr33domlover: I can live with either, but leaning towards an original name without "Git" and "Libre", they indeed seem overused to me - SiB64: I second that, no _libre_ please. - circlebuilder: I am advocating as mentioned in 1) for seeing the 'code forge' (an app) in a broader light, i.e. "forging free software". As mentioned this covers the entire FSDL. And potentially many, many different functionalities (think GH and GL here). Hence, no "Libre" and no "Git" as that is too narrow. - tallship: ditch FLOSS (and Libre), it's redundantant (sic), like "Mount Fujiyama" is redundant. Also, I think "fanatic" is rather offensive and "zealot" more appropriately describes that level of passion. - Onepict I see software like gitea or other web frontends as a community hub. Folks tend to coalese and interact on various websites. They become community hubs. Just because this is mainly focused on code building doesn't make it very different. Git and VCs can often be very powerful organisational tools. So choosing a name to encourage that idea of community of building not just projects but that community is important. - fnetx: I think that "Git" in the name narrows the scope of the project. It's software development. VCS is a core part, yes, but issue communication channels (e.g. issue trackers), review tooling and other features are important, too. But I would not have this as a strict criteria: If we find a "good" name that fits our other criteria, it should be okay to have both parts in it ("GitLibre" xD). I think that having other VCS support (as plugins?) could be a potential feature, yes. - Gusted: While I doubt if Gitea ever incorporate another VCS system, I'd like the idea to not be tied to the "Git" name and instead allow a broader set of names. Be it more forge-centric name. - Dodecahedron: I'd prefer something original without "Git" or "libre", but I'm also fine if the name does contain them. - Caesar: I'd also prefer to see something without 'Git' and especially without 'Libre', which to me makes the name sound formal, boring, and unmemorable. - Daniele: I agree with Caesar, 'Git' could be avoided in the name and 'Libre' sound a bit pedantic (perhaps since it's mostly used in "Free *Libre* Open Source Software") - Ryuno-Ki: I assume, there won't be any other VCS than git for the time being. Perhaps hq at best. I second fnetx and Gusted here. I understand why some people would like to have Libre, but I find it too confusing (e.g. OpenOffice vs. LibreOffice) ## (3) Choosing the name! Please go over all the _[proposed names](https://pad.gusted.xyz/s/CHF4F4dZB#Naming-the-fork)_ first. **Make 3 lists below** like in the Alice example below, **with the same titles** as in the example. Any name you don't mention, is considered "a name you could live with", so especially put emphasis on **listing all the names you don't like or have concerns about!** - Alice - 1-3 names I'm most excited about + short why - Smithy (sounds great and original, fits forgers guild vision, fits forge metaphor) - Smelt (same) - Names I can happily live with - Artisan - Gimli - Smithea - Gitoffee - Names I don't like + why/concerns - Telibre (doesn't communicate it's a forge, "libre" takes most of the name's length) - ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi(b) (none sound catchy enough to me) - The names in non-english languages/translations, they sound kinda weird to me (unless you speak that language?) - Brigid (sounds like Frigid? And like Brigitte Bardot?) - circlebuilder - Names most excited about (unsurprisingly) - Smithy (dictionary substitute for forge, fits friendlier narrative, fits Forgers Guild concept real well) - Names I can happily live with - Forge - Smithea (though a bit too much dependence / reactionary to Gitea) - Gitenburg (name with "git" I dig, but _only_ if a true project provided by Codeberg under same branding) - Names I do not prefer - forgefriends (great name, but keep it where it is) - Smelt (was doubting here, but not so familiar name for non-english folks, plus association with past tense "smells") - Furnace (too unspecific, the furnace at home / the bakery / the pizzeria, etc) - _The remaining candidates_ - talkship: - names I like the most: ForgeFed it's the name of the project from which this effort was derived. the domain name is already registered and under our control (forgefed.org). The Domain Name is 1. ) Short 2. ) Meaningful 3. ) Relevant 4. ) Unambiguous - names I can live with: pretty much anything without the word "Libre" in it, and **"Furnace"** is actually a pretty good RCS agnostic noun that meets the four requirements above too, and rolls off the tongue nicely. - names I really don't much prefer: Anything with the word "Libre" or "FLOSS" in it. I don't care for the word "smith" to refer to a non person either very much, and it doesn't have enough consonance when it rolls off the tongue either, IMO. i.e., a Smith is a person, a forge is a thing, but I could actually live with simply **"Smithy"**. Just my 2¢ - Onepict - 1-3 names I'm most excited about * Smithy - I liked this from the beginning. * Forgejo - I like Esperanto, the language is about finding community together through language as it takes words from lots of languages. * Hearth - This I like, as I tend to see front end software for organising and managing issues as your community hub. This fosters that feeling. - Names I can happily live with * Atelier * Furnace * gimli - Names I don't like + why/concerns I think we want a fresh start for this fork. We also want to be VCS agnostic in the future. So anything with Git, Libre or Open, I don't think is a good idea. We want to foster colaboration and this fork is also about forge federation. Ideally we want this to reach beyond FOSS. Smelt is too close to smelling as past tense in English - dachary - Names most excited about - Smithy - LibreForge - FediForge - Names I can happily live with - Forge - Smithea - Gitenburg - Names I do not prefer - none - fnetX - 1-3 names I'm most excited about + short why - FediForge (most interesting aspect) - Forja, Fucina, Forgejo: Interesting and simple - Names I can happily live with - GitLibre - Gitoli (althogh conflicting with Gitolite a little) - LibreForge, OpenForge (simle, but boring) - Forgo (although a little weird) - Smelt, Smithy - Atelier (or Gitelier?): maybe too few relation to software? - CodeLab (boring, but ok) - Smithea - Gitoffee - GitSmith - Names I don't like + why/concerns - Telibre: Very unintuitive, you don't think of a forge - sago, chago etc: only sticking to the tea part is weird - GoForLib: weird - Gitenberg - Gitli (conflict with Gitly) - ForgeLib, ForLibre, Forli(b): forge library and freedom fights? - Brigid (unintuivie relation, sounds agressive to me, and I don't like gods) - Gimli (not a fan of series or movies) - Gusted - 1-3 names I'm most excited about + short why: - Smithy: really a good thoughtfull name for any forge, not specific to a "Gitea fork". - Artisan: The meaning of this word has something to do with forges. - Names I can happily live with - LibreForge, well it's FLOSS-centric, I think it's intuitive and simple. - Smithli, see reason for Smithy. - forgefriends, bit awkward as it would change the meaning of Forgefreinds, but otherwise like the name. - sago, chago, cha-go-yu, Like the name but doesn't really have any relevance to a fork. - Names I don't like + why - Gitenberg: Feels like Codeberg chose this name + git-centric. - GitLibre, GitSmith, GitoLi, GitLi: Git-centric. - Telibre: FLOSS-centric not related to a forge. - ForgeLi(b), ForLibre, ForLi(b): "li" is awkward to pronounce. - GoForLi(b), ForGo: Lets not continue the trend of adding the program language to it. Feels like: We made (for the first time) something interesting in X language, which is not the case. - OpenForge: "open" is broad. - Fed(i)Forge: Big scam, Gitea isn't even federated *yet*. - Brigid, Brigit: Theist-centric. - Smelt: This is a verb - Atelier: Branding this would be quite hard. - CodeLab: Cannot get rid of a reference to "GitLab". - Smithea, Gitoffee: Reference to drinks *again*. - Dodecahedron - 1-3 names I'm most excited about + short why: - Forja, Fucina, Forgejo: These don't include "Git" or "libre" and sound nice. - Names I can happily live with - Gitoffee - Smithy - Names I don't like + why - Gitenberg, GitLibre, Telibre, GitoLi, ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi: weird spellings or sound awkward or cumbersome when pronounced - Oliverpool - 1-3 names I'm most excited about + short why: - Forgejo: short and memorable, seems easy to pronounce in many languages - Githea - Names I can happily live with - Smithea: nice to have a link to the previous project (see below regarding "th") - Smithy: main drawback, the "th" is quite english-centric - Names I don't like + why _I can happily live with any name_ - Caesar - 1-3 names I'm most excited about + short why - Smithy (sounds great and original, fits Forgers' Guild vision, fits forge metaphor) - Furnace - Smelt - Names I can happily live with - Atelier - Gimli - Garfo - Forja, Forgejo - CodeLab – a bit generic but I quite like the 'lab', might be worth thinking about more names around that - GitSmith - if we wanted Git in the name (though I prefer not to have it) - Names I don't like + why/concerns - Telibre – doesn't communicate it's a forge, 'libre' takes most of the name's length - ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi(b) – none sound catchy enough to me + don't like 'libre' - GitoLi or GitLi – ditto plus too close to Gitolite - GoForLi(b), ForGo – ditto, plus I don't like having the language in the name - sago, chago etc – only sticking to the tea part is weird - ForgeFriends, Fed(i)Forge – we don't have federation yet, and we hope other forges will have it in future, so it's not a distinguisihng feature - Gitoffee, Giteine – I don't think emphasizing being a Gitea fork is important, and I don't like Git in the name - codedotjs - 1-3 Names I'm most excited about + short why - **Smithea**: good mixture of Smithy and Gitea (Smithy looks too much like a name). Includes both the Gitea (history) and Smithy (forging code) aspects. I added Smitty/Smittea to the name list in case we want to avoid the "th". - **CodeLab**: Two syllables thus easy to remember. Fits the names of Codeberg (hosting platform - shows where the project comes from) and GitLab (a similar project - people reading the name will instantly think of a git web client). A lab is similar to a smithy but with the focus on experimenting rather than building things after a fixed plan. - **Forgejo**: Esperanto wants to be an easy language for as much people as possible. This is also kind of what we want with our project. The forging aspect is also applied here. In other words: "A place where people all around the world are forging code together." - Names I can happily live with - Smithy, Forja, Atelier - Brigid, Gimli - sago, chago, cha-go-yu - Gitsmith - Gitoffee, Giteine - Tisane - Codebox, Codeshelf, Codecup - Names I don't like + why/concerns - **Telibre**: Sounds like telephone or television to me. - **GitLibre**: If we want to link the name to GitHub or GitLab it should be pronounced as easy as they are. GitLibre has three syllables. - **Gitenberg**: Git in a german word looks like "Gift" (poison) on first sight. - **forgefriends**: This should be the name of a group not a software. - **Fed(i)forge**: As already mentioned above this should only be applied if Gitea gets federation support in the future. - **Codebin**: sounds like a pastebin instance - **Gitorium**: Not intuitive for a non english speaker. Ressembles at Imperium (empire). - Daniele - 1-3 names I'm most excited about + short why - Tisane (like tea but without caffeine, suggests me the link to the original project without the greed. Quick, easy and refreshing) - Atelier (a place where one can build nice things. I like it very much!) - Names I can happily live with - Gimli - Smithy - Forgejo - CodeLab (perhaps a bit too CodeBerg-like, but ok nevertheless) - sago, chago - Names I don't like + why/concerns - GitSmith. Git* - I don't like the idea of "Git" in the name, especially to begin with it since it adds a strong connection to the original project - \*Libre - I don't like the idea of "Libre" in the name - Garfo, Smelt - sound weird in my own language (I'm italian) - Hearth - too generic - Furnace - too hot :) - ForgeFriends, Fed(i)Forge – we don't have federation yet, and we hope other forges will have it in future, so it's not a distinguisihng feature - KaKi87 - Names most excited about - ForgeFed : I fully support the idea of federation taking a central place in the project. - Names I can happily live with - LibreForge : speaks for itself. - Names I don't like + why/concerns - Smithy, Smelt, Artisan, Smithli, Hearth, Atelier, GitSmith, Smithli : non-native speakers may not guess the meaning of these names at first glance. - Artisan : can also be confused with Laravel software. - Atelier : despite that fact, I actually do like it. - Gimli, Brigid : people unfamiliar with the origin of those names may not guess their meaning at first glance. - Smithea, Gitoffee, Giteine, Tisane : controvertial reference to Gitea and/or drinks. - Smithea : cf. Smithy - Tisane: despite that fact, I actually do like it. - Telibre, Forgo, Forgejo, Forja, Fucina, sago, chago, GoForLib, cha-go-yu : I can't find the meaning of those names. - Telibre : also homophone of French "t'es libre". - (Git|For|Forge)Li(b(re)), Gitenburg, forgefriends, Furnace, Fed(i)Forge, Gitoli, OpenForge, Gitelier, CodeLab : subjectively sounds unattractive. - Forge : too generic. - Sanjibukai - Names most excited about - forgit : Short for "Forge it" while knowing that's a git server (Let's be honest most of the people is using Git) - forgeit : This one I added after checking that 'geit' actually means somehow goat.. And we can then keep "Forge it" and have a Goat as a mascot? This mountain climbing animal somehow can be related to the forge/smiths - Names I can happily live with - everything that's <=7 characters - Names I do not prefer - everything else - JustPassingBy - Names most excited about - Latte - beverage theme, short and nice - Giticious - git + delicious - Gitorium - code emporium (but combines with git a lot better) - Codeshop - code workshop - Codeshelf, Codebox - storage theme - Names I can happily live with - Atelier - Smithy - Forge - Tisane - Giteine - CodeLab - CodeForge - Names I do not prefer - libre/open/etc. - sounds boring/nerdy - berg/burg - something feels wrong with these, idk - Ryuno-Ki - Names most excited about - Artisan - Atelier - Sago (yummy - we have a dish with yeast dumplings and sago for a fruit sauce) - Chagoyu (I'm a tea lover) - Smithea - Names I can happily live with - Smithy - Gitenberg - Smithli - Smelt (possible confusion with Svelte when hearing) - Furnace - Brigit (could be considered sexist?) - Gitmate (mate as in partner?) - Codeshop (a bit boring, though) - Names I do not prefer - GitLibre - Telibre, Tisane (too far fetched) - GitoLi / GitLi (too easy too confuse, would have to be spelled) - ForgeLi(b), LibreForge, ForLibre, ForLi(b) (I don't like the casing, but without you struggle with reading) - GoForLi(b) (go for what?) - ForGo (foregone) - OpenForge - LibreForge - Fed(i)Forge (Fed as in fat?) - Forkly, Forkit, Forkist, Forklift (sounds more like knife and spoon than like VCS) - Herrero, Ferreiro (did you mean Ferrero?) - Faber (like the German company Faber-Castell?) - Gimli (I fear trademark issues. Tolkiens family have a reputation...) - CodeLab (taken by several, among them Google) - Gitoffee - Giteine - GitSmith (sounds like a name) - Latte (hard to search. See also programming language R) - Giticious (I already had trouble with del.icio.us) - Gitorium - steko - Names most excited about - Forgejo, I like the "forge" meaning, I like Esperanto - Names I can happily live with - Smithy - FediForge - Furnace - forgefriends - CodeForge (I'm not sure it's in the list but it's a nice variation of the various word combinations .. to my ears) - Names I do not prefer - Forge or Smithy in other languages (apart from **Forgejo**, see above) - Gitenberg, sounds too specific to this moment of change rather than a long-lasting name, I don't like having Git in the name - GitLibre, I don't think "git" should be in the same, it sounds very amateurish to just juxtapose two words, and "libre" is overused - Telibre, "libre" is overused - Gitoli or Gitli - ForgeLi(b), LibreForge, Smithli, ForLibre, ForLi(b) - GoForLi(b), ForGo, ... - OpenForge - Brigid (the entire initiative is already abundantly Europe-centric without adding Celtic goddesses to the mix) - Blacksmith in other languages - Gimli (pretty sure the Tolkien Estate is going to sue asap) - CodeLab (too similar to GitLab) - sago, chago, cha-go-yu - I don't see why the "tea" from upstream should be kept - Smithea, same as above - Gitoffee - Gitmate, already in use (?) - Giteine (no Git in the name) - GitSmith (no Git in the name) - Gitorium (no Git in the name) - Giticious no Git in the name) - Tisane (too generic) - Latte (too generic) - Codeshop - Codeshelf or similar (storage theme) ... but see **CodeForge** above - **Add your own 3 lists here...** ## (4) What's next Once we gather everyone's feedback into this pad, I'll prepare a summary of results, with the best options we picked, and we'll see if there's one that fits all criteria the most, and that nobody opposes :-) Feedback/questions/concerns about this document itself, or about the selection process? Write to *fr33domlover* on Matrix (`@fr33domlover:matrix.org`) or on the Fediverse (`@fr33domlover@todon.nl`).

Voting for the name (either Smithy or Forgejo) is in this pad https://pad.gusted.xyz/s/BatxQqSKI#

Voting for the name (either Smithy or Forgejo) is in this pad https://pad.gusted.xyz/s/BatxQqSKI#

@fr33domlover I'm a little confused as to what happens now as it seems another round of discussion started.

The last voting phase of the process is complete as of today, which means that counting votes decides on a name.

Can we do that and move on? Unless there is a grave concern that requires doing another round of discussions and votes?

@fr33domlover I'm a little confused as to what happens now as it seems another round of discussion started. The [last voting phase of the process](https://codeberg.org/codename/meta/issues/1#issue-198941) is complete [as of today](https://pad.gusted.xyz/s/BatxQqSKI), which means that counting votes decides on a name. Can we do that and move on? Unless there is a grave concern that requires doing another round of discussions and votes?

For the record, a message in the chatroom from @fr33domlover

name choice news: Considering the worries about the Amazon project named Smithy, and considering the suggestions to use IPA and audio to clarify the pronounciation of Forgejo (and/or just let people pronounce it whatever way they prefer), I propose we go with the Forgejo name. Is anyone disappointed / strongly opposed to that? Tomorrow, i.e. Wednesday, is the last day to express these concerns. If none are expressed and addressed until Wednesday, 23:59 UTC, we'll be going with Forgejo.

There are 2 points to handle:

᠎ suggested to use 'Forgeyo' to clarify pronounciation (

᠎ , could you write this suggestion on the issue if it's still relevant?)
The 'g' in Forgejo is supposed to have that little sign above it, 'ĝ', we'll need to decide whether and where to use this special sign VS using a plain regular 'g'

But these 2 issues will be tackled on the issue tracker, to avoid exhausting everyone's energy/attention here :) We'll bring them here if resolving them proves challenging

For the record, a message [in the chatroom](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/6ドルvrd-67XbUdgjb_WMBLrCAprU70DT0YKU327ruJbLG4?via=matrix.org&via=exozy.me&via=tchncs.de) from @fr33domlover > name choice news: Considering the worries about the Amazon project named Smithy, and considering the suggestions to use IPA and audio to clarify the pronounciation of Forgejo (and/or just let people pronounce it whatever way they prefer), I propose we go with the Forgejo name. Is anyone disappointed / strongly opposed to that? Tomorrow, i.e. Wednesday, is the last day to express these concerns. If none are expressed and addressed until Wednesday, 23:59 UTC, we'll be going with Forgejo. > > There are 2 points to handle: > > ᠎ suggested to use 'Forgeyo' to clarify pronounciation ( > > ᠎ , could you write this suggestion on the issue if it's still relevant?) > The 'g' in Forgejo is supposed to have that little sign above it, 'ĝ', we'll need to decide whether and where to use this special sign VS using a plain regular 'g' > > But these 2 issues will be tackled on the issue tracker, to avoid exhausting everyone's energy/attention here :) We'll bring them here if resolving them proves challenging

@fr33domlover could you please publish the raw data collected from the form?

@fr33domlover could you please publish the raw data collected from the form?

I asked previously, but it wasn't planned: https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/5ドルTR5mZ45BWPhJGH-rUfnFu75wLnfTP3gVW5X3C2fTGs?via=matrix.org&via=tchncs.de&via=exozy.me

If it's helpful, I will (preferring to focus on concerns instead of numbers, to avoid confusing people; we're all used to majority-voting based systems so trying not to activate our habits from those systems)

AFAIK the only published number was:

11 out of 16 people "value the Esperanto idea more"

I asked previously, but it wasn't planned: https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/5ドルTR5mZ45BWPhJGH-rUfnFu75wLnfTP3gVW5X3C2fTGs?via=matrix.org&via=tchncs.de&via=exozy.me > If it's helpful, I will (preferring to focus on concerns instead of numbers, to avoid confusing people; we're all used to majority-voting based systems so trying not to activate our habits from those systems) AFAIK the only published number was: > 11 out of 16 people "value the Esperanto idea more"

@fr33domlover I think it would be helpful at this point to have the raw data. I'm not concerned about activating any habit right now because ... the governance is yet to be decided. The absence of data is confusing me, as you can see.

@fr33domlover I think it would be helpful at this point to have the raw data. I'm not concerned about activating any habit right now because ... the [governance is yet to be decided](https://codeberg.org/codename/meta/issues/19). The absence of data is confusing me, as you can see.
Contributor
Copy link

I'm attaching raw data from the form. Note that I removed people's nicknames from it, because I didn't ask in advance for consent to publish what people fill into the form (but the form text inputs aren't personal info, so publishing here without names; if anyone wants their comments deleted from here, let me know). Summary of numbers is:

  • 20 people filled the form
  • Happy with Smithy: 12 ; having concerns: 8
  • Happy with Forgejo: 13; having concerns: 7
  • Considering the criteria we've collected, which name would you go with: 13 for Forgejo, 7 for Smithy
I'm attaching raw data from the form. Note that I removed people's nicknames from it, because I didn't ask in advance for consent to publish what people fill into the form (but the form text inputs aren't personal info, so publishing here without names; if anyone wants their comments deleted from here, let me know). Summary of numbers is: - 20 people filled the form - Happy with Smithy: 12 ; having concerns: 8 - Happy with Forgejo: 13; having concerns: 7 - Considering the criteria we've collected, which name would you go with: 13 for Forgejo, 7 for Smithy

For the record, a message from @fr33domlover in the chatroom:

The purpose of the name choice process is to choose a name that best fills the criteria we collected together, as much as possible within our collective capacity here, and that everyone here can embrace as their own choice. It does mean that someone of us would prefer some other name, for example I like the sound of "Hearth". But I'm asking a different question: When we put ourselves for a moment (or longer) in a leadership orientation, looking at the concerns of everyone in this group, which names can we all embrace and that align with our shared purpose? In the name of that question, I proposed we embrace the Forgejo name :)

And it's perfectly welcome to mourn that some other cool names weren't picked (and reminder, they're still available for use in other projects!)

I'm also up for facilitating a text/audio/video meeting about it, in a format that would allow people to express themselves and be heard in a safe environment

And one more thing: If anyone feels their concerns aren't being heard, please do tell me / write to me ❤️ there are 70 people in this globally distributed asnchronously-discussing chatroom/group, so some voices may be lost, but I do wish there every voice has space to be heard ❤️

For the record, a message from @fr33domlover [in the chatroom](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$uOAAawQFU1RxLt0-rUPtd2nYwizUEy4fqO0ZvWsz61I?via=matrix.org&via=exozy.me&via=tchncs.de): > The purpose of the name choice process is to choose a name that best fills the criteria we collected together, as much as possible within our collective capacity here, and that everyone here can embrace as their own choice. It does mean that someone of us would prefer some other name, for example I like the sound of "Hearth". But I'm asking a different question: When we put ourselves for a moment (or longer) in a leadership orientation, looking at the concerns of everyone in this group, which names can we all embrace and that align with our shared purpose? In the name of that question, I proposed we embrace the Forgejo name :) > > And it's perfectly welcome to mourn that some other cool names weren't picked (and reminder, they're still available for use in other projects!) > > I'm also up for facilitating a text/audio/video meeting about it, in a format that would allow people to express themselves and be heard in a safe environment > > And one more thing: If anyone feels their concerns aren't being heard, please do tell me / write to me ❤️ there are 70 people in this globally distributed asnchronously-discussing chatroom/group, so some voices may be lost, but I do wish there every voice has space to be heard ❤️ >

The name picked for the project is Forgejo.

The name picked for the project is **Forgejo**.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/meta#1
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?