11 ms·

Gitea – A community-managed fork of Gogs

158 points by ausjke 10y ago

pryelluw 10y ago
The gogs and gitea websites feature the same basic content on the front page. Is it also open source? Im curious and dont mean to stir up shit.
- scaryclam 10y ago
  The front page states that it's under the MIT license, so I'm guessing yes.
  - pryelluw 10y ago
    Missed that. :) Thx.
dqv 10y ago
It was forked because they wanted a different management model that included more people. https://blog.gitea.io/2016/12/welcome-to-gitea/ https://blog.gitea.io/2016/12/welcome-to-gitea/
ausjke 10y ago
I played with gogs half-year ago and gitea is my first software try-out in 2017, it worked beautifully for pretty much everything I wanted and it requires way less cpu/mem to run(comparing to gitlab,etc), I'm sold.
mongrelion 10y ago
I wonder how long it's going to take before gogs and gitea get merged, just like it has happened in the past with major forks , nodejs + iojs being one example.
- benley 10y ago
  Personally, I tend to consider that to be a wildly successful outcome for an OSS project fork. The project community continues to exist, conflicts get resolved (hopefully amicably), users benefit, developers benefit. Everyone wins!
- carwyn 10y ago
  They've split and merged before. This is the second time gitea has forked.
  - 0942v8653 10y ago
    What did gitea contribute the last time they merged?
    - bedonnant 10y ago
      I think it was at a time when the original maintainer kept silent for a while. When he came back online, gitea stepped back.
      - MetalMatze 10y ago
        Exactly, but then he went silent again for over a month in December. We will continue development of Gitea, even now that he's back.
  - deleted 10y ago
    [deleted]
  - ahacker15 10y ago
    Yep. The first time was until the owner came back, but he refused to merge the changes on Gogs. The community stopped with Gitea when this happened. This time, the community patience ended, and Gitea will continue on its own way.
- MetalMatze 10y ago
  We will never merge, unless Gogs gets merged into Gitea. We won't merge into Gogs because then only one person will be left as an owner which was the reason for the fork in the first place.
zyang 10y ago
Hosted on github...
- ahacker15 10y ago
  It will be hosted on a Gitea instance soon. It wasn't done yet because of few missing features, etc.
- papaf 10y ago
  This is my biggest complaint about gogs. I use it for personal projects but it is harder to collaborate with and get pull requests from other developers using gogs than it is with github. It is a pain if you have to register with every gogs instance that you want to prepare a pull request for. I think if gogs/gitea was self-hosting it would encourage the developers to find easier ways of collaborating. This is my only complaint about gogs. It is amazing otherwise, suits my needs, is low maintenance and is an impressive piece of work. I would encourage anyone to try it that wants to have private repositories for personal projects.
  - vertex-four 10y ago
    Github has OAuth2 - couldn't gogs have a "log in with Github" option that pulls all the data it needs from there automatically?
    - bkcsoft 10y ago
      When Gitea gets support for consuming OAuth2 this will be make possible Tracking Issue is https://github.com/go-gitea/gitea/issues/26 https://github.com/go-gitea/gitea/issues/26
  - ahacker15 10y ago
    You may want to take a look at this issue: https://github.com/go-gitea/gitea/issues/184 https://github.com/go-gitea/gitea/issues/184
  - tboerger 10y ago
    We will integrate OAuth2 and after that we also want to integrate federated pull requests so that you can create pull requests from other gitea instances as well.
Sir_Cmpwn 10y ago
This is a pretty immature community IMO. The gogs maintainer just has life sometimes and they want to fork because he leaves some PRs open for a while. Learn some patience, the project will be better off for it.
- ahacker15 10y ago
  We can for sure understand that one is not available all time. Everyone has a life, and sometimes need many weeks away, etc. This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going. Before the first time he went AFK, he even removed write access from the 2 or 3 other people that had it.
  - Sir_Cmpwn 10y ago
    That's his prerogative. Learn patience. Not all PRs have to be merged on your schedule. As a FOSS maintainer myself this sort of behavior sickens me and reeks of entitlement. Gogs is worse off for your involvement.
    - Mithaldu 10y ago
      Forking when you're unhappy about something and can't come to an agreement is EXACTLY what OSS is about. Saying this as another OSS maintainer.
      - Sir_Cmpwn 10y ago
        I would completely understand and agree if they had a rational reason for forking, but they don't. I have a very low opinion of unwarranted forks.
        akerl_ 10y ago
        Why does somebody forking need to justify that their fork is warranted based on your standards?
vvarp 10y ago
As someone who's currently using gogs I'd like to know what are the primary differences between gogs and gitea - right now the website doesn't talk too much of benefits coming from the switch. Sure, community managed sounds great, but does that automatically guarantee a solid project vision, predictable release cycle and lots of new features? Don't want to sound negative but I think reasons for the fork needs to be clearly presented and potential switchers (like myself) got to be assured there's a better future with the fork rather than original
- sondr3 10y ago
  The main difference is mainly in who contributes and the speed of development right now, who knows what'll happen in a few months. The main issue is that the sole maintainer of Gogs has a habit of going missing for months at a time, this normally wouldn't be an issue if he gave other contributors write access to the repo, but he doesn't. He actually removed a few the first time he went missing. Right now, the initial release was pretty much just a cleanup effort to get the codebase ready for the new changes that are coming down the line. If you look at the PRs open for 1.1 there's a lot of goodies coming that I'm looking forward to.
  - smarx007 10y ago
    Well, say what you want but I see 33 open PRs and 1039 closed ones on the original gogs repo. Doesn't look like an unmaintained repo to me.
    - JasonSage 10y ago
      Yes, this is what it looks like when he hasn't disappeared for three months straight.
      - cweagans 10y ago
        Three whole months? How dare he! /s
  - xorcist 10y ago
madeofpalk 10y ago
Ahhh gogs. This project has always rubbed me the wrong way with how much of a blatant steal of Github it is. Sure, 'copy' the features, and take inspiration from the UI and layout, but so much of gogs looks identical to GitHub that it's nothing but stealing.
- funjjhcc 10y ago
  The issue of calling IP property. I mean it's not like someone's breaking into GutHub's server room and stealing equipment. You want to say it's a breech of copyright, patent or trademark? Maybe. But then FreeBSD "stole" Unix, Windows stole Mac, Mac stole Xerox, Microsoft stole WordPerfect, and so on.
  - madeofpalk 10y ago
    Isn't that semantics? I'm obviously quite aware there wasn't any physical theft. My point was around the developers being seemingly okay with ripping off Github's UI.
    - Mithaldu 10y ago
      The thing you're missing is that in this case UI is not something you can usefully make different without harming yourself in the process, due to it being a huge contributor to function beyond form, and "ripping it off" doesn't hurt anyone else as long as you don't actually impersonate them by copying their logos.
      - madeofpalk 10y ago
        Stash, Bitbucket and Gitlab all tend to disagree that theres only one way to build a UI for git websites. I agree that no one is being harmed, but personally I just thing it's shameful.
        Mithaldu 10y ago
        Stash and Bitbucket are horrible to use imo, and last time i looked Gitlab looked almost the same as Github.
throw2016 10y ago
I think a fork should not be a casual decision as the main developer would have put in hundreds or thousands of hours on the project and was motivated to get it to this state. A project by a small team or even a single person will obviously be constrained in many ways. Now if the project has potential or takes off a 'community' should fork it only if all other avenues have been exhausted and with good reasons. Its important for a 'community fork' to let the community know the exact rationale or 'community' can easily becomes a excuse for some to seek to control or capitalise on others work. This does not help open source especially if the main developers are too busy developing while those who fork have time to market the fork to a community.
- freshhawk 10y ago
  If the main developer doesn't want forks then don't use an free/open source license. It is very simple. "Capitalise on others work"? That's insane, that license is very explicit that this work was donated to the public under well specified terms. It welcomes all of us to capitalise on it, that's the whole damn point. There is a single sufficient "good reason" to fork a project. You want to. People are free to use your fork or ignore it.
  - throw2016 10y ago
    The point was not against forks but transparency and good faith. Open source is not just about forking but also contributing, no? What have the forkers contributed to the product so far? Where are the technical reasons for the fork? Where is the community discussion and consensus? Has there been any kind of democratic action? So on what basis is the word 'community' used? A fork shoud not simply be about people misusing the word 'community' for seeking control and ownership because that's not what open source is about, is it?
    - foepys 10y ago
      > What have the forkers contributed to the product so far? A lot of the forkers and go-gitea group members wrote essential features for Gogs and contributed thousands of lines of code. They simply got impatient waiting sometimes 3 months for their PRs to get merged. Especially bkcsoft did tremendous work on Gogs. As a contributor to Gogs that stopped contributing because whose last PR wasn't merged for a very long time, I welcome Gitea's idea of a faster development schedule.
kureikain 10y ago
His reply is very reasonable and some of Gitea dev is a bit of harsh in tone IMHO. Or maybe that's because of my English level. Anyway, I think this is how OSS should be. We shouldn't have to force people to merge the code that we want. At the end of the day, it's his project anyway. Good luck to both of projects.
- jhasse 10y ago
  Where can I see his reply?
  - dqv 10y ago
    >In my point of view, it's a sign of success of Gogs that Gitea forked it. Gogs is under MIT license and there is no problem with me totally that Gitea is developing its own version. It happens often in open source community(when you are not satisfied with upstream version, I fork a lot actually). Seen here: https://github.com/gogits/gogs/issues/1304#issuecomment-124664775 https://github.com/gogits/gogs/issues/1304#issuecomment-1246...
- tboerger 10y ago
  Who of the gitea developers is harsh?
hkt 10y ago
This seems positive. It means that the big weakness of Gogs (bus factor) goes away. I'll be interested to know if they opt for anything more sophisticated than "more than one person has admin on the repo" as a governance model.
anondon 10y ago
My major issue with Gogs and Gitea is that they lack a cache to store the git history/log. So if you work with repos that have many commits (example, the git repo itself or the linux kernel repo), you will forever be waiting for the commit message for each file to load because Gogs/Gitea scans the entire git log for each file. This was an issue when I tested Gogs a few months and I don't see any mention of a cache so I think it's still an issue. For smaller repos though, Gogs works incredibly well. Regarding this fork, it makes sense if the owner of gogs is not giving write access to others. At the same time it would be a shame if Gitea becomes popular and overshadows Gogs. I hope they can work out a mutually acceptable solution and merge.
- tboerger 10y ago
  We are aware of that issue, and hopefully we will find a proper solution to improve the load time for bigger repos.
zsj 10y ago
A community is not about how many people have permission to write the main repository. Linux kernel is the example. Linus is only one who has permission to write the mainline tree.
- cyphar 10y ago
  True. But Linus also doesn't disappear for several months at a time. Not to mention that Linus is not the only decision maker in the project. Greg KH maintains the stable kernels (which is ironically where most people get their kernel from).
alkonaut 10y ago
Question to any gitea devs/users: How can I get rid of the (terrible) i18n?? I'm trying out the app but it's complete gibberish! It appears to do some kind of User Agent detected i18n - (which by the way an app should never do imho). I just want english so I can have some kind of understanding of what I'm doing but I can't find the setting either in my user profile nor in the app configuration.
- PascalW 10y ago
  I haven't tried but I think you might be able to add this to your config to fix that: [i18n] LANGS = en-US NAMES = English https://gogs.io/docs/features/i18n https://gogs.io/docs/features/i18n Edit: tried and indeed it seems to work.
  - lunny 10y ago
    Right. But I would you change `custom/conf/app.ini`
  - alkonaut 10y ago
    Thanks, that worked perfectly. Odd to implement i18n and then automatically choose based on UA, but not have a user option?
    - jhasse 10y ago
      I can select the language on the bottom right of every page of my Gogs instance.
      - alkonaut 10y ago
        Lol: it's the same in Gitea. I spent a lot of time carefully going through every settings page I could find, did not look in the footer.
- bkcsoft 10y ago
  It is infact using `Accept-Language`-header and `lang`-cookie as seen in this[1] file on line 168, 184 and 196. This is according to W3C[2] a good starting point :) [1] https://github.com/go-macaron/i18n/blob/ef57533c3b0fc2d8581deda14937e52f11a203ab/i18n.go https://github.com/go-macaron/i18n/blob/ef57533c3b0fc2d8581d... [2] https://www.w3.org/International/questions/qa-accept-lang-locales https://www.w3.org/International/questions/qa-accept-lang-lo...
guomanmin 10y ago
Participate in Atlassian Research My name is Angela and I do research for Atlassian. I’m kicking off a round of discussions with people who use Git tools. Ideally, I’d like to talk to people that sit on a team of 3 or more. If this is you, I would love to talk to you about your experience with <using> Git tools, or just some of the pain points that are keeping you up at night when doing your jobs.    We’ll just need 30 mins of your time, and as a token of my thanks to those that participate, I’d like to offer a US$50 Amazon gift voucher.   If you’re interested, just shoot me an email with your availability over the next few weeks and we can set up a time to chat for 30 minutes. Please also include your timezone so we can schedule a suitable time (as I’m located in San Francisco). Hope to talk to you soon! Cheers,   Angela Guo aguo@atlassian.com

158 points by ausjke 10y ago

The gogs and gitea websites feature the same basic content on the front page. Is it also open source? Im curious and dont mean to stir up shit.

scaryclam 10y ago
The front page states that it's under the MIT license, so I'm guessing yes.
- pryelluw 10y ago
  Missed that. :) Thx.

dqv 10y ago

It was forked because they wanted a different management model that included more people. https://blog.gitea.io/2016/12/welcome-to-gitea/ https://blog.gitea.io/2016/12/welcome-to-gitea/

ausjke 10y ago

I played with gogs half-year ago and gitea is my first software try-out in 2017, it worked beautifully for pretty much everything I wanted and it requires way less cpu/mem to run(comparing to gitlab,etc), I'm sold.

mongrelion 10y ago

I wonder how long it's going to take before gogs and gitea get merged, just like it has happened in the past with major forks , nodejs + iojs being one example.

benley 10y ago
Personally, I tend to consider that to be a wildly successful outcome for an OSS project fork. The project community continues to exist, conflicts get resolved (hopefully amicably), users benefit, developers benefit. Everyone wins!
carwyn 10y ago
They've split and merged before. This is the second time gitea has forked.
- 0942v8653 10y ago
  What did gitea contribute the last time they merged?
  - bedonnant 10y ago
    I think it was at a time when the original maintainer kept silent for a while. When he came back online, gitea stepped back.
    - MetalMatze 10y ago
      Exactly, but then he went silent again for over a month in December. We will continue development of Gitea, even now that he's back.
- deleted 10y ago
  [deleted]
- ahacker15 10y ago
  Yep. The first time was until the owner came back, but he refused to merge the changes on Gogs. The community stopped with Gitea when this happened. This time, the community patience ended, and Gitea will continue on its own way.
MetalMatze 10y ago
We will never merge, unless Gogs gets merged into Gitea. We won't merge into Gogs because then only one person will be left as an owner which was the reason for the fork in the first place.

zyang 10y ago

Hosted on github...

ahacker15 10y ago
It will be hosted on a Gitea instance soon. It wasn't done yet because of few missing features, etc.
papaf 10y ago
This is my biggest complaint about gogs. I use it for personal projects but it is harder to collaborate with and get pull requests from other developers using gogs than it is with github. It is a pain if you have to register with every gogs instance that you want to prepare a pull request for. I think if gogs/gitea was self-hosting it would encourage the developers to find easier ways of collaborating. This is my only complaint about gogs. It is amazing otherwise, suits my needs, is low maintenance and is an impressive piece of work. I would encourage anyone to try it that wants to have private repositories for personal projects.
- vertex-four 10y ago
  Github has OAuth2 - couldn't gogs have a "log in with Github" option that pulls all the data it needs from there automatically?
  - bkcsoft 10y ago
    When Gitea gets support for consuming OAuth2 this will be make possible Tracking Issue is https://github.com/go-gitea/gitea/issues/26 https://github.com/go-gitea/gitea/issues/26
- ahacker15 10y ago
  You may want to take a look at this issue: https://github.com/go-gitea/gitea/issues/184 https://github.com/go-gitea/gitea/issues/184
- tboerger 10y ago
  We will integrate OAuth2 and after that we also want to integrate federated pull requests so that you can create pull requests from other gitea instances as well.

Sir_Cmpwn 10y ago

This is a pretty immature community IMO. The gogs maintainer just has life sometimes and they want to fork because he leaves some PRs open for a while. Learn some patience, the project will be better off for it.

ahacker15 10y ago
We can for sure understand that one is not available all time. Everyone has a life, and sometimes need many weeks away, etc. This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going. Before the first time he went AFK, he even removed write access from the 2 or 3 other people that had it.
- Sir_Cmpwn 10y ago
  That's his prerogative. Learn patience. Not all PRs have to be merged on your schedule. As a FOSS maintainer myself this sort of behavior sickens me and reeks of entitlement. Gogs is worse off for your involvement.
  - Mithaldu 10y ago
    Forking when you're unhappy about something and can't come to an agreement is EXACTLY what OSS is about. Saying this as another OSS maintainer.
    - Sir_Cmpwn 10y ago
      I would completely understand and agree if they had a rational reason for forking, but they don't. I have a very low opinion of unwarranted forks.
      - akerl_ 10y ago
        Why does somebody forking need to justify that their fork is warranted based on your standards?

vvarp 10y ago

As someone who's currently using gogs I'd like to know what are the primary differences between gogs and gitea - right now the website doesn't talk too much of benefits coming from the switch. Sure, community managed sounds great, but does that automatically guarantee a solid project vision, predictable release cycle and lots of new features? Don't want to sound negative but I think reasons for the fork needs to be clearly presented and potential switchers (like myself) got to be assured there's a better future with the fork rather than original

sondr3 10y ago
The main difference is mainly in who contributes and the speed of development right now, who knows what'll happen in a few months. The main issue is that the sole maintainer of Gogs has a habit of going missing for months at a time, this normally wouldn't be an issue if he gave other contributors write access to the repo, but he doesn't. He actually removed a few the first time he went missing. Right now, the initial release was pretty much just a cleanup effort to get the codebase ready for the new changes that are coming down the line. If you look at the PRs open for 1.1 there's a lot of goodies coming that I'm looking forward to.
- smarx007 10y ago
  Well, say what you want but I see 33 open PRs and 1039 closed ones on the original gogs repo. Doesn't look like an unmaintained repo to me.
  - JasonSage 10y ago
    Yes, this is what it looks like when he hasn't disappeared for three months straight.
    - cweagans 10y ago
      Three whole months? How dare he! /s
- xorcist 10y ago

madeofpalk 10y ago

Ahhh gogs. This project has always rubbed me the wrong way with how much of a blatant steal of Github it is. Sure, 'copy' the features, and take inspiration from the UI and layout, but so much of gogs looks identical to GitHub that it's nothing but stealing.

funjjhcc 10y ago
The issue of calling IP property. I mean it's not like someone's breaking into GutHub's server room and stealing equipment. You want to say it's a breech of copyright, patent or trademark? Maybe. But then FreeBSD "stole" Unix, Windows stole Mac, Mac stole Xerox, Microsoft stole WordPerfect, and so on.
- madeofpalk 10y ago
  Isn't that semantics? I'm obviously quite aware there wasn't any physical theft. My point was around the developers being seemingly okay with ripping off Github's UI.
  - Mithaldu 10y ago
    The thing you're missing is that in this case UI is not something you can usefully make different without harming yourself in the process, due to it being a huge contributor to function beyond form, and "ripping it off" doesn't hurt anyone else as long as you don't actually impersonate them by copying their logos.
    - madeofpalk 10y ago
      Stash, Bitbucket and Gitlab all tend to disagree that theres only one way to build a UI for git websites. I agree that no one is being harmed, but personally I just thing it's shameful.
      - Mithaldu 10y ago
        Stash and Bitbucket are horrible to use imo, and last time i looked Gitlab looked almost the same as Github.

throw2016 10y ago

I think a fork should not be a casual decision as the main developer would have put in hundreds or thousands of hours on the project and was motivated to get it to this state. A project by a small team or even a single person will obviously be constrained in many ways. Now if the project has potential or takes off a 'community' should fork it only if all other avenues have been exhausted and with good reasons. Its important for a 'community fork' to let the community know the exact rationale or 'community' can easily becomes a excuse for some to seek to control or capitalise on others work. This does not help open source especially if the main developers are too busy developing while those who fork have time to market the fork to a community.

freshhawk 10y ago
If the main developer doesn't want forks then don't use an free/open source license. It is very simple. "Capitalise on others work"? That's insane, that license is very explicit that this work was donated to the public under well specified terms. It welcomes all of us to capitalise on it, that's the whole damn point. There is a single sufficient "good reason" to fork a project. You want to. People are free to use your fork or ignore it.
- throw2016 10y ago
  The point was not against forks but transparency and good faith. Open source is not just about forking but also contributing, no? What have the forkers contributed to the product so far? Where are the technical reasons for the fork? Where is the community discussion and consensus? Has there been any kind of democratic action? So on what basis is the word 'community' used? A fork shoud not simply be about people misusing the word 'community' for seeking control and ownership because that's not what open source is about, is it?
  - foepys 10y ago
    > What have the forkers contributed to the product so far? A lot of the forkers and go-gitea group members wrote essential features for Gogs and contributed thousands of lines of code. They simply got impatient waiting sometimes 3 months for their PRs to get merged. Especially bkcsoft did tremendous work on Gogs. As a contributor to Gogs that stopped contributing because whose last PR wasn't merged for a very long time, I welcome Gitea's idea of a faster development schedule.

kureikain 10y ago

His reply is very reasonable and some of Gitea dev is a bit of harsh in tone IMHO. Or maybe that's because of my English level. Anyway, I think this is how OSS should be. We shouldn't have to force people to merge the code that we want. At the end of the day, it's his project anyway. Good luck to both of projects.

jhasse 10y ago
Where can I see his reply?
- dqv 10y ago
  >In my point of view, it's a sign of success of Gogs that Gitea forked it. Gogs is under MIT license and there is no problem with me totally that Gitea is developing its own version. It happens often in open source community(when you are not satisfied with upstream version, I fork a lot actually). Seen here: https://github.com/gogits/gogs/issues/1304#issuecomment-124664775 https://github.com/gogits/gogs/issues/1304#issuecomment-1246...
tboerger 10y ago
Who of the gitea developers is harsh?

hkt 10y ago

This seems positive. It means that the big weakness of Gogs (bus factor) goes away. I'll be interested to know if they opt for anything more sophisticated than "more than one person has admin on the repo" as a governance model.

anondon 10y ago

My major issue with Gogs and Gitea is that they lack a cache to store the git history/log. So if you work with repos that have many commits (example, the git repo itself or the linux kernel repo), you will forever be waiting for the commit message for each file to load because Gogs/Gitea scans the entire git log for each file. This was an issue when I tested Gogs a few months and I don't see any mention of a cache so I think it's still an issue. For smaller repos though, Gogs works incredibly well. Regarding this fork, it makes sense if the owner of gogs is not giving write access to others. At the same time it would be a shame if Gitea becomes popular and overshadows Gogs. I hope they can work out a mutually acceptable solution and merge.

tboerger 10y ago
We are aware of that issue, and hopefully we will find a proper solution to improve the load time for bigger repos.

zsj 10y ago

A community is not about how many people have permission to write the main repository. Linux kernel is the example. Linus is only one who has permission to write the mainline tree.

cyphar 10y ago
True. But Linus also doesn't disappear for several months at a time. Not to mention that Linus is not the only decision maker in the project. Greg KH maintains the stable kernels (which is ironically where most people get their kernel from).

alkonaut 10y ago

Question to any gitea devs/users: How can I get rid of the (terrible) i18n?? I'm trying out the app but it's complete gibberish! It appears to do some kind of User Agent detected i18n - (which by the way an app should never do imho). I just want english so I can have some kind of understanding of what I'm doing but I can't find the setting either in my user profile nor in the app configuration.

PascalW 10y ago
I haven't tried but I think you might be able to add this to your config to fix that: [i18n] LANGS = en-US NAMES = English https://gogs.io/docs/features/i18n https://gogs.io/docs/features/i18n Edit: tried and indeed it seems to work.
- lunny 10y ago
  Right. But I would you change `custom/conf/app.ini`
- alkonaut 10y ago
  Thanks, that worked perfectly. Odd to implement i18n and then automatically choose based on UA, but not have a user option?
  - jhasse 10y ago
    I can select the language on the bottom right of every page of my Gogs instance.
    - alkonaut 10y ago
      Lol: it's the same in Gitea. I spent a lot of time carefully going through every settings page I could find, did not look in the footer.
bkcsoft 10y ago
It is infact using `Accept-Language`-header and `lang`-cookie as seen in this[1] file on line 168, 184 and 196. This is according to W3C[2] a good starting point :) [1] https://github.com/go-macaron/i18n/blob/ef57533c3b0fc2d8581deda14937e52f11a203ab/i18n.go https://github.com/go-macaron/i18n/blob/ef57533c3b0fc2d8581d... [2] https://www.w3.org/International/questions/qa-accept-lang-locales https://www.w3.org/International/questions/qa-accept-lang-lo...

guomanmin 10y ago

Participate in Atlassian Research My name is Angela and I do research for Atlassian. I’m kicking off a round of discussions with people who use Git tools. Ideally, I’d like to talk to people that sit on a team of 3 or more. If this is you, I would love to talk to you about your experience with <using> Git tools, or just some of the pain points that are keeping you up at night when doing your jobs.    We’ll just need 30 mins of your time, and as a token of my thanks to those that participate, I’d like to offer a US$50 Amazon gift voucher.   If you’re interested, just shoot me an email with your availability over the next few weeks and we can set up a time to chat for 30 minutes. Please also include your timezone so we can schedule a suitable time (as I’m located in San Francisco). Hope to talk to you soon! Cheers,   Angela Guo aguo@atlassian.com