Archived
15
23
Fork
You've already forked meta
6

forgejo tagline #42

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

What should forgejo tagline be?

What should forgejo tagline be?
Ghost added this to the Launch milestone 2022年11月20日 18:13:15 +01:00

Disclaimer: although I created the issue, I'm entirely unable to ensure it yields to something good. I won't contribute to the design by committee anti-pattern ;-)

AFAIK @circlebuilder and @fnetX are the only one among the people currently invovled in Forgejo with the skills to come up with something sensible. Although I would appreciate that my input is taken into consideration, I will ultimately trust their best judgement.

Disclaimer: although I created the issue, I'm entirely unable to ensure it yields to something good. I won't contribute to the [design by committee](https://en.wikipedia.org/wiki/Design_by_committee) anti-pattern ;-) AFAIK @circlebuilder and @fnetX are the only one among the people currently invovled in Forgejo with the skills to come up with something sensible. Although I would appreciate that my input is taken into consideration, I will ultimately trust their best judgement.
Member
Copy link

@circlebuilder suggested in Matrix:

Forgejo. Forging code for Everyone

@circlebuilder [suggested in Matrix](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$slXcFiBD5oDXbSSBEOi-xMjG-XyjuKvsxSGxTpNitxw): > Forgejo. Forging code for Everyone
Contributor
Copy link

We are looking for a tagline. Have an idea?

Code for libre forging. Forging for libre code.

> We are looking for a tagline. Have an idea? Code for libre forging. Forging for libre code.
Contributor
Copy link

Indeed @caesar

Forgejo. Forging code for Everyone

It has some nice aspects:

  • Forgejo as community project: Is forging a code forge for the benefit of everyone, and where everyone can participate.
  • Forgejo as product / software: Is code forge software for everyone to use (100% FOSS).
  • Fits into the broad vision to give meaning to "forging free software" that The Forgers Guild promotes.
Indeed @caesar **Forgejo. Forging code for Everyone** It has some nice aspects: - Forgejo as community project: Is forging a code forge for the benefit of everyone, and where everyone can participate. - Forgejo as product / software: Is code forge software for everyone to use (100% FOSS). - Fits into the broad vision to give meaning to "forging free software" that The Forgers Guild promotes.

I'm used to "Software forge" and the idea of "Forging software", in my imagination, is about code and all that's around it. As a developer I really like "Forging code", obviously :-) Don't you think it could be perceived as less inclusive because people who do not write code could feel they do not belong?

I don't have strong feelings on the matter, it's just a thought I had 😄

I'm used to "Software forge" and the idea of "Forging software", in my imagination, is about code and all that's around it. As a developer I really like "Forging code", obviously :-) Don't you think it could be perceived as less inclusive because people who do not write code could feel they do not belong? I don't have strong feelings on the matter, it's just a thought I had 😄
Member
Copy link

"Forging software for everyone"?

"Forging software for everyone"?
Contributor
Copy link

Don't you think it could be perceived as less inclusive because people who do not write code could feel they do not belong?

Agreed. Maybe Forgejo needs a space created explicitly for those who don't write code, like the proposal of oss-codesign(which, as I understand from @Ryuno-Ki, you've referenced); With that supported feature, the idea of a forge would be more inclusive.

> Don't you think it could be perceived as less inclusive because people who do not write code could feel they do not belong? Agreed. Maybe Forgejo needs a space created explicitly for those who don't write code, like the proposal of [oss-codesign](https://github.com/jazlynhellman/oss-codesign)(which, as I understand from @Ryuno-Ki, you've referenced); With that supported feature, the idea of a forge would be more inclusive.
Owner
Copy link

Some thoughts if we want to refer to the inclusiveness of our project:

Stop coding, start forging.
Software forging – more than (just) code.
Forging Software - Participation for everyone.

They kinda refer to the fact that Forgejo/Gitea offer more than just a plain Git web frontend, and the last one eventually to forge federation, too.

I happen to dislike most of my other ideas, because they just appear like randomly dicing combinations of Software, forge, libre, everyone and connection words inbetween.

Some thoughts if we want to refer to the inclusiveness of our project: Stop coding, start forging. Software forging – more than (just) code. Forging Software - Participation for everyone. They kinda refer to the fact that Forgejo/Gitea offer more than just a plain Git web frontend, and the last one eventually to forge federation, too. I happen to dislike most of my other ideas, because they just appear like randomly dicing combinations of Software, forge, libre, everyone and connection words inbetween.
Member
Copy link

How about something like "forging community"?
(Or maybe "forging community for everyone"?)

How about something like "forging community"? (Or maybe "forging community for everyone"?)
Contributor
Copy link

@fnetX "Stop coding, start forging" is a really strong one, I think.

And @dachary is right about "code" vs. "software" in terms of inclusion.

Forgejo. Forging software for Everyone

Join our inclusive community. Software is created together. Stop coding, start forging.

@fnetX "Stop coding, start forging" is a really strong one, I think. And @dachary is right about "code" vs. "software" in terms of inclusion. --- **Forgejo. Forging software for Everyone** Join our inclusive community. Software is created together. Stop coding, start forging.
Contributor
Copy link

I think forge and all its derivatives are implicit in the name. I would avoid repeating it. Maybe hosting software for everyone, collaborative software for everyone...

Community, collaboration, inclusion, is there a word in English like meeting place? or collective work place? something like that? hosting not includes working, collaborative not includes place...

(In Chile we have the minga (a mapuche word) which is a "party" where everyone goes to work to (literally) move a house from its place to another place. The host provides all the food, drink, etc. and when they invite say we will have a minga.)

I think forge and all its derivatives are implicit in the name. I would avoid repeating it. Maybe *hosting software for everyone*, *collaborative software for everyone*... Community, collaboration, inclusion, is there a word in English like meeting place? or collective work place? something like that? hosting not includes working, collaborative not includes place... (In Chile we have the *minga* (a mapuche word) which is a "party" where everyone goes to work to (literally) move a house from its place to another place. The host provides all the food, drink, etc. and when they invite say we will have a minga.)
Owner
Copy link

Repeating this central word might not be bad, but help better memorize our name. But I'm also open to the proposals that avoid this redundancy.

Repeating this central word might not be bad, but help better memorize our name. But I'm also open to the proposals that avoid this redundancy.
Contributor
Copy link

Stube used to be the central place in a farmhouse kitchen (and could play into the guild framing).

Stop coding, start forging.

Is my favourite so far.

Libre was turned down in the name choice: #1 (comment)

Therefore I think we will avoid it here as well.

[Stube](https://en.wikipedia.org/wiki/Farmhouse_kitchen) used to be the central place in a farmhouse kitchen (and could play into the guild framing). > Stop coding, start forging. Is my favourite so far. Libre was turned down in the name choice: https://codeberg.org/forgejo/meta/issues/1#issuecomment-686529 Therefore I think we will avoid it here as well.

Stop coding, start forging.

is definitely very memorable.

> Stop coding, start forging. is definitely very memorable.

Stop coding, start forging.

is definitely very memorable.

Yes it is very memorable but I think choosing a sentence that starts with a negative verb like stop is not a good choice. Let's focus on the positive side of Forgejo. I can think of something like

Start forging, together

Even though it's less obvious that we're a software forge.

> > Stop coding, start forging. > > is definitely very memorable. Yes it is very memorable but I think choosing a sentence that starts with a negative verb like *stop* is not a good choice. Let's focus on the positive side of Forgejo. I can think of something like > Start forging, together Even though it's less obvious that we're a software forge.
Contributor
Copy link

choosing a sentence that starts with a negative verb like stop is not a good choice. Let's focus on the positive side of Forgejo.

I very much agree.

> choosing a sentence that starts with a negative verb like *stop* is not a good choice. Let's focus on the positive side of Forgejo. I very much agree.

I think forge and all its derivatives are implicit in the name. I would avoid repeating it. Maybe hosting software for everyone, collaborative software for everyone...

Community, collaboration, inclusion, is there a word in English like meeting place? or collective work place? something like that? hosting not includes working, collaborative not includes place...

(In Chile we have the minga (a mapuche word) which is a "party" where everyone goes to work to (literally) move a house from its place to another place. The host provides all the food, drink, etc. and when they invite say we will have a minga.)

This is where "hearth" could be good. Sometimes you hear the phrase welcome to my hearth (although it's usually in stories)

Although we do sometimes in english talk about something being the heart of the community. Usually when a bar or a community centres been shut down. People comment on the heart of a place being torn out.

So perhaps Forgejo could be:

"Forge the heart of your community."

> I think forge and all its derivatives are implicit in the name. I would avoid repeating it. Maybe *hosting software for everyone*, *collaborative software for everyone*... > > Community, collaboration, inclusion, is there a word in English like meeting place? or collective work place? something like that? hosting not includes working, collaborative not includes place... > > (In Chile we have the *minga* (a mapuche word) which is a "party" where everyone goes to work to (literally) move a house from its place to another place. The host provides all the food, drink, etc. and when they invite say we will have a minga.) This is where "hearth" could be good. Sometimes you hear the phrase welcome to my hearth (although it's usually in stories) Although we do sometimes in english talk about something being the heart of the community. Usually when a bar or a community centres been shut down. People comment on the heart of a place being torn out. So perhaps Forgejo could be: "Forge the heart of your community."

This is where "hearth" could be good. Sometimes you hear the phrase welcome to my hearth (although it's usually in stories)

Although we do sometimes in english talk about something being the heart of the community. Usually when a bar or a community centres been shut down. People comment on the heart of a place being torn out.

So perhaps Forgejo could be:

"Forge the heart of your community."

Would this be hearth 🔥 or heart ❤️?

> This is where "hearth" could be good. Sometimes you hear the phrase welcome to my hearth (although it's usually in stories) > > Although we do sometimes in english talk about something being the heart of the community. Usually when a bar or a community centres been shut down. People comment on the heart of a place being torn out. > > So perhaps Forgejo could be: > > "Forge the heart of your community." Would this be *hearth* 🔥 or *heart* ❤️?
Member
Copy link

"Forge the heart of your community."

I like that. I like having "community" in there; I think it's important to emphasize that Forgejo is both by and for the community, and is for community-building.

Would this be hearth 🔥 or heart ❤️?

Heart. I think hearth would sound a bit strange in that context.

Another slight variation on the community theme / mixup of previous suggestions could be:

"Forging community together"

> "Forge the heart of your community." I like that. I like having "community" in there; I think it's important to emphasize that Forgejo is both by and for the community, and is for community-building. > Would this be hearth 🔥 or heart ❤️? Heart. I think hearth would sound a bit strange in that context. --- Another slight variation on the community theme / mixup of previous suggestions could be: ***"Forging community together"***

Is anyone willing to make a final decision on the tagline when the time comes?

Is anyone willing to make a final decision on the tagline when the time comes?

I think @caesar and myself feel quite strongly about the idea of community in the tagline.

Because it's an answer to what the larger centralised forges claim to be. It's an answer to what Gitea was supposed to be with it being owned by the community.

Free Software Philosophy is meant to be about freedom for everyone.

Code is important yes, but code needs to be used by a larger community, so a community is developers, testers, users.

We are considering Open Source Design's ideas of this wider definition. When we were looking at the names, I stated that I saw the frontends of git as a community hub.

We have an issue tracker, that fosters discussion beyond the traditional idea of a bug tracker. We have the functionality of wikis to help to documents our projects.

We have the idea of discoverability.

This is community beyond commits to code.

So if there is a vote. I'd vote for:

"Forging community together"

I think @caesar and myself feel quite strongly about the idea of community in the tagline. Because it's an answer to what the larger centralised forges claim to be. It's an answer to what Gitea was supposed to be with it being owned by the community. Free Software Philosophy is meant to be about freedom for everyone. Code is important yes, but code needs to be used by a larger community, so a community is developers, testers, users. We are considering Open Source Design's ideas of this wider definition. When we were looking at the names, I stated that I saw the frontends of git as a community hub. We have an issue tracker, that fosters discussion beyond the traditional idea of a bug tracker. We have the functionality of wikis to help to documents our projects. We have the idea of discoverability. This is community beyond commits to code. So if there is a vote. I'd vote for: "Forging community together"

Just had a quick conversation with someone else testing that tagline.

He suggested that perhaps just:

"Forging Community"

Which is snappier.

Just had a quick conversation with someone else testing that tagline. He suggested that perhaps just: "Forging Community" Which is snappier.

@onepict don't you think a vote would lead to a design by committee antipattern? I'm in favor of

  • floating many ideas and opinions (what is being done now)
  • rely on one or two person with the right skill set ( @fnetX and/or @circlebuilder would be my pick ) to make a decision
@onepict don't you think a vote would lead to a [design by committee antipattern](https://en.wikipedia.org/wiki/Design_by_committee)? I'm in favor of * floating many ideas and opinions (what is being done now) * rely on one or two person with the right skill set ( @fnetX and/or @circlebuilder would be my pick ) to make a decision

TLDR: Sometimes voting is necessary, but I am happy for ideas to float and for someone to pick the tagline.

Well we did see some passion with the choosing of the name. But I am glad we did that. Because of the possible conflict of smithy with Amazons tooling ideas. I was worried about the real prospect of down the line choosing another name and the possible blockages with that. Now in the tagline case there is no danger of that.

I think it depends what the community is aiming to think about itself. To also consider how people considering joining that community may think about it. But ultimately the tagline is something you use to publise the project on social media feeds etc. It needs to be simple.

Some want a brand to be able to associate with, to help to stick in folks minds, others aren't branding orientated.

The question we need to be asking is what do we think Forgejo is? What do we think it should be? Who do we want contributing to it?

The tagline needs to reflect that. Taking the comments above some things like actions we don't want to repeat twice.

I see this being discussed as part of governance today, as there may well be some important project directions that the community needs to take a decision on. So it's a case of trust and priority.

Some decisions will affect the life of a project and how it functions. The decisions made, may be hard to undo, so the community should vote on these directional decisions.

But votes need to be bounded, and I'm more of a fan of voting like STV (Single transferable votes) or preference votes. They need to be timelimited and clear on the deadlines. I felt that the voting times for the naming were unclear and I feel it did lead to some tension.

I don't always agree with debians decisions, but their community is involved in making those decisions. Which is important for a community owned project. Otherwise you are rehashing the dangers with gitea, and why gitea publically felt it needed to fork.

But in the case of a tagline, I'm willing for people to float ideas and then someone decides.

TLDR: Sometimes voting is necessary, but I am happy for ideas to float and for someone to pick the tagline. Well we did see some passion with the choosing of the name. But I am glad we did that. Because of the possible conflict of smithy with Amazons tooling ideas. I was worried about the real prospect of down the line choosing another name and the possible blockages with that. Now in the tagline case there is no danger of that. I think it depends what the community is aiming to think about itself. To also consider how people considering joining that community may think about it. But ultimately the tagline is something you use to publise the project on social media feeds etc. It needs to be simple. Some want a brand to be able to associate with, to help to stick in folks minds, others aren't branding orientated. The question we need to be asking is what do we think Forgejo is? What do we think it should be? Who do we want contributing to it? The tagline needs to reflect that. Taking the comments above some things like actions we don't want to repeat twice. I see this being discussed as part of governance today, as there may well be some important project directions that the community needs to take a decision on. So it's a case of trust and priority. Some decisions will affect the life of a project and how it functions. The decisions made, may be hard to undo, so the community should vote on these directional decisions. But votes need to be bounded, and I'm more of a fan of voting like STV (Single transferable votes) or preference votes. They need to be timelimited and clear on the deadlines. I felt that the voting times for the naming were unclear and I feel it did lead to some tension. I don't always agree with debians decisions, but their community is involved in making those decisions. Which is important for a community owned project. Otherwise you are rehashing the dangers with gitea, and why gitea publically felt it needed to fork. But in the case of a tagline, I'm willing for people to float ideas and then someone decides.

FWIW I think the process for deciding on the name was good. Some people criticized it for being bad choice and an example of the "design by committee" antipattern. But I do not agree.

FWIW I think the process for deciding on the name was good. Some people criticized it for being bad choice and an example of the "design by committee" antipattern. But I do not agree.

I think it's knowing when something should be voted for really.

We needed to vote on the name, because its what the community would know the fork as. The discussion preceding the name vote, demonstrated why we needed to vote.

I'm happy to trust someone to pick the tagline. Hopefully the discussion on here will encourage others.

But perhaps if you want more of the community to float ideas then we need to link to this issue on the matrix chat.

Which could cause a delay, but could also encourage community interest and more of a feeling of ownership before the formal launch.

To some extent the tagline will also help to inform the mascot design as well.

I think it's knowing when something should be voted for really. We needed to vote on the name, because its what the community would know the fork as. The discussion preceding the name vote, demonstrated why we needed to vote. I'm happy to trust someone to pick the tagline. Hopefully the discussion on here will encourage others. But perhaps if you want more of the community to float ideas then we need to link to this issue on the matrix chat. Which could cause a delay, but could also encourage community interest and more of a feeling of ownership before the formal launch. To some extent the tagline will also help to inform the mascot design as well.

Hi all,

I am not related to the project, but very interested in it since I currently self-host a private Gitea instance.

From what I read in the discussion, I'd like to share that with a lot of sentences containing forging I often have a second association with forgery.
Not sure if that is relevant, but others might have that association as well.

Independent on what you decide, I whish this project all the success and I am curious about which tagline you will decide on.

Hi all, I am not related to the project, but very interested in it since I currently self-host a private Gitea instance. From what I read in the discussion, I'd like to share that with a lot of sentences containing `forging` I often have a second association with `forgery`. Not sure if that is relevant, but others might have that association as well. Independent on what you decide, I whish this project all the success and I am curious about which tagline you will decide on.
Member
Copy link

Just had a quick conversation with someone else testing that tagline.

He suggested that perhaps just:

"Forging Community"

Which is snappier.

I think that's my favourite suggestion so far. Short, snappy, and to the point.

I think there's something to be said for @mkroehnert 's point about forgery – but that said, we're pretty invested in the "forge" terminology at this point, what with the name and all...

Whilst it's true that the concept of a "code forge" (or at least that name for it) will be alien to many, context is everything, and I think that a tagline such as "Forging Community" seems (to me at least) to unambiguously refer to the 2nd meaning in the Oxford Dictionary:

create (something) strong, enduring, or successful

and so I don't feel it is likely to be associated with the negative sense of "forgery" (3rd meaning in the Oxford dictionary).

That said that's just my own feeling!

As for the selection process, I don't think we need anything too formal, but on the other hand I do feel a reasonable level of consensus is important.
I don't think decisions, particularly about the public persona / image of the project, should be made by a single person where that can be avoided.
But it would be fine for someone to make a proposal and see whether there are any objections, just as I did with the interim logo for example.

Forging community would get my vote!

> Just had a quick conversation with someone else testing that tagline. > > He suggested that perhaps just: > > "Forging Community" > > Which is snappier. I think that's my favourite suggestion so far. Short, snappy, and to the point. I think there's something to be said for @mkroehnert 's point about forgery – but that said, we're pretty invested in the "forge" terminology at this point, what with the name and all... Whilst it's true that the concept of a "code forge" (or at least that name for it) will be alien to many, context is everything, and I think that a tagline such as ***"Forging Community"*** seems (to me at least) to unambiguously refer to the 2nd meaning in the Oxford Dictionary: > create (something) strong, enduring, or successful and so I don't feel it is likely to be associated with the negative sense of "forgery" (3rd meaning in the Oxford dictionary). That said that's just my own feeling! --- As for the selection process, I don't think we need anything too formal, but on the other hand I do feel a reasonable level of consensus is important. I don't think decisions, particularly about the public persona / image of the project, should be made by a single person where that can be avoided. But it would be fine for someone to make a proposal and see whether there are any objections, just as I did with the interim logo for example. --- ***Forging community*** would get my vote!

Whilst it's true that the concept of a "code forge" (or at least that name for it) will be alien to many

Sourceforge has been around for 23 years!

> Whilst it's true that the concept of a "code forge" (or at least that name for it) will be alien to many Sourceforge has been around for 23 years!

@steko that was also my first thought when @circlebuilder told me that the concept of a "software forge" is not as common as I thought. And indeed, if you look at the communication of GitHub or GitLab, they never use "software forge".

Now, I do not think this is a problem because the Forgejo audience is the FOSS community and they are aware of what a "software forge" means. Even better, it is a concept that sets Forgejo appart from GitHub or GitLab. It is an opportunity to build on a term that is not tained by centralized forges.

@steko that was also my first thought when @circlebuilder told me that the concept of a "software forge" is not as common as I thought. And indeed, if you look at the communication of GitHub or GitLab, they never use "software forge". Now, I do not think this is a problem because the Forgejo audience is the FOSS community and they are aware of what a "software forge" means. Even better, it is a concept that sets Forgejo appart from GitHub or GitLab. It is an opportunity to build on a term that is not tained by centralized forges.

Just had a quick conversation with someone else testing that tagline.

He suggested that perhaps just:

"Forging Community"

Which is snappier.

I like the simplicity and the clarity of this one. It stands on its own, but could also be punctuated as two distinct things like "Forging. Community." or "Forging+Community".

> Just had a quick conversation with someone else testing that tagline. > > He suggested that perhaps just: > > "Forging Community" > > Which is snappier. I like the simplicity and the clarity of this one. It stands on its own, but could also be punctuated as two distinct things like "Forging. Community." or "Forging+Community".

@circlebuilder @fnetX as the launch date is closing, would you be so kind as to make a decision? Any other decision process is fine by me ... as long as it can complete before November 29th so that the tagline can be applied wherever relevant. I'm also perfectly fine with setting the deadline to a later date, as long as someone assigns themselves the issue and is committed to see it complete before the deadline.

To help with the decision I compiled all the tag lines mentionned in this issue with references.

Forgejo. Forging code for Everyone
Code for libre forging. Forging for libre code.
Forging software for everyone
Stop coding, start forging
Software forging – more than (just) code
Forging Software - Participation for everyone
Forging community
Forging community for everyone
Hosting software for everyone
Collaborative software for everyone
Start forging, together
Forge the heart of your community
Forging community together
Forging community together
Forging Community
Forging. Community
Forging+Community

@circlebuilder @fnetX as the launch date is closing, would you be so kind as to make a decision? Any other decision process is **fine by me** ... as long as it can complete before November 29th so that the tagline can be applied wherever relevant. I'm also perfectly fine with setting the deadline to a later date, as long as someone assigns themselves the issue and is committed to see it complete before the deadline. To help with the decision I compiled all the tag lines mentionned in this issue with references. [Forgejo. Forging code for Everyone](https://codeberg.org/forgejo/meta/issues/42#issuecomment-692893) [Code for libre forging. Forging for libre code.](https://codeberg.org/forgejo/meta/issues/42#issuecomment-692502) [Forging software for everyone](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693236) [Stop coding, start forging](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693328) [Software forging – more than (just) code](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693328) [Forging Software - Participation for everyone](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693328) [Forging community](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693369) [Forging community for everyone](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693369) [Hosting software for everyone](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693535) [Collaborative software for everyone](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693535) [Start forging, together](https://codeberg.org/forgejo/meta/issues/42#issuecomment-693843) [Forge the heart of your community](https://codeberg.org/forgejo/meta/issues/42#issuecomment-694071) [Forging community together](https://codeberg.org/forgejo/meta/issues/42#issuecomment-694077) [Forging community together](https://codeberg.org/forgejo/meta/issues/42#issuecomment-694143) [Forging Community](https://codeberg.org/forgejo/meta/issues/42#issuecomment-694144) [Forging. Community](https://codeberg.org/forgejo/meta/issues/42#issuecomment-695763) [Forging+Community](https://codeberg.org/forgejo/meta/issues/42#issuecomment-695763)
Contributor
Copy link

Taglines can change later on, when e.g. there's a change in course of a project or its direction is better clarified.

Right now "code forges" are clearly mostly aimed at a technical audience, and in particular to Devs. We might say "Forging community (for everyone)" but it has very little meaning yet. "What kind of software is this?" people will think. A community tool?

Hence I wouldn't be afraid to use the word "Code". The app offered is a "code forge" after all.

In terms of taglines 2 stand out to me..

  1. Forgejo. Forging code for Everyone: It is a code forge, but the direction of the project is to focus on the entire process of software development and inclusive participation of all roles.

  2. Stop coding, start forging: Short and snappy. Implies that coding isn't the whole picture, and with "forging" implies the same project direction as the other tagline.

Now I agree that "stop" as negative word is best avoided. So you might change the tagline to:

  • Go beyond coding. Start forging
  • Beyond coding. We forge.

Either of the taglines can be chosen, and they can also be combined...

Forgejo

Beyond coding. We forge.

Forging code for Everyone. That is the objective of the Forgejo project. Forgejo recognizes that there is more to software development than coding alone. Many people are involved in creating good quality software. Applying different skills and collaborating in coordinated processes all the time. Good communication between everyone involved is key. More than merely technical, coding is social in nature. [..]

Taglines can change later on, when e.g. there's a change in course of a project or its direction is better clarified. Right now "code forges" are clearly mostly aimed at a technical audience, and in particular to Devs. We might say "Forging community (for everyone)" but it has very little meaning yet. "What kind of software is this?" people will think. A community tool? Hence I wouldn't be afraid to use the word "Code". The app offered is a "code forge" after all. In terms of taglines 2 stand out to me.. 1. **Forgejo. Forging code for Everyone**: It is a code forge, but the direction of the project is to focus on the entire process of software development and inclusive participation of all roles. 2. **Stop coding, start forging**: Short and snappy. Implies that coding isn't the whole picture, and with "forging" implies the same project direction as the other tagline. Now I agree that "stop" as negative word is best avoided. So you might change the tagline to: - **Go beyond coding. Start forging** - **Beyond coding. We forge.** Either of the taglines can be chosen, and they can also be combined... --- ### Forgejo #### Beyond coding. We forge. _Forging code for Everyone._ That is the objective of the Forgejo project. Forgejo recognizes that there is more to software development than coding alone. Many people are involved in creating good quality software. Applying different skills and collaborating in coordinated processes all the time. Good communication between everyone involved is key. More than merely technical, coding is social in nature. [..]

@circlebuilder choose "Beyond coding. We forge.".

Let's go with this tagline ✨

@circlebuilder [choose "Beyond coding. We forge."](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$e59-rXM6y3hcqLWaoiK71lJe00m4DTo8s_9Ys16qolQ?via=matrix.org&via=exozy.me&via=tchncs.de). Let's go with this tagline ✨
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
11 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta#42
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?