8 ms·

Why are they not dogfooding? If they will use Github to develop Gogs, the potential audience may think why they should not use Github itself. I am not trying

Why are they not dogfooding? If they will use Github to develop Gogs, the potential audience may think why they should not use Github itself. I am not trying to put them down, it's very difficult to dog food when your product is in its early state but their page suggests that they already support Issue Tracking. I think it is in a state where they can use Gogs to develop Gogs. This will ensure that they work on those items which affects developers the most.

maratd 12y ago
> If they will use Github to develop Gogs, the potential audience may think why should I not use Github itself? Because you have to pay for private repos and pay even more to host your own deployment?
- duiker101 12y ago
  also, they might be using github because it's already open to the wide audience that might want to contribute.
  - solutionyogi 12y ago
    Their feature comparison shows that they do support Issue Tracking.
    - deleted 12y ago
      [deleted]
maaaats 12y ago
To be fair, Gogs is about having your own, possibly private to a company, Git service. Github is about collaboration. Most people wanting to contribute to this are probably already on Github.
dewey 12y ago
They don't support issue tracking yet. Not really something you'd want for the development process.
- __david__ 12y ago
  I see issue tracking on the demo site: https://try.gogs.io/moulaf/VLC-git/issues https://try.gogs.io/moulaf/VLC-git/issues
  - dewey 12y ago
    Oh, indeed. My bad, that's good to know - It seems that I misread that code review section where they were talking about GitHub issues. Thanks!
lsaferite 12y ago
If a primary stated goal is self-hosting private repositories, why would you expect them to self-host? Especially when it's an open-source project and GitHub is a large nexus of OSS development.
- delinka 12y ago
  I expect dog-fooding by people making tools for other people. There is no reason they can't self-host (without publishing the interface to the entire 'net) and then just use GitHub as another remote to handle external collaboration.
swah 12y ago
Tried the product again (w/ no repos..) and it looks very nice. Dogfooding, drop the "written in Go" like technomancy says, big-ass buttons "Import from my Github" and "Import from existing repository". This should be more popular!
- thawkins 12y ago
  Written in GO is important for us as we have inhouse GO skills, we dont have ruby skills. This tool would be perfect for us, if it had AD/LDAP integration. Being written in GO means we can consider doing it ourselves.
  - Vendan 12y ago
    Go look at the code, it's crappily written and virtually unmaintainable. I'm using it right now, but only by breaking it's concurrency. If I let it handle more then 1 request at a time, it starts 404'ing random resources....

maratd 12y ago

> If they will use Github to develop Gogs, the potential audience may think why should I not use Github itself? Because you have to pay for private repos and pay even more to host your own deployment?

duiker101 12y ago
also, they might be using github because it's already open to the wide audience that might want to contribute.
- solutionyogi 12y ago
  Their feature comparison shows that they do support Issue Tracking.
  - deleted 12y ago
    [deleted]

maaaats 12y ago

To be fair, Gogs is about having your own, possibly private to a company, Git service. Github is about collaboration. Most people wanting to contribute to this are probably already on Github.

dewey 12y ago

They don't support issue tracking yet. Not really something you'd want for the development process.

__david__ 12y ago
I see issue tracking on the demo site: https://try.gogs.io/moulaf/VLC-git/issues https://try.gogs.io/moulaf/VLC-git/issues
- dewey 12y ago
  Oh, indeed. My bad, that's good to know - It seems that I misread that code review section where they were talking about GitHub issues. Thanks!

lsaferite 12y ago

If a primary stated goal is self-hosting private repositories, why would you expect them to self-host? Especially when it's an open-source project and GitHub is a large nexus of OSS development.

delinka 12y ago
I expect dog-fooding by people making tools for other people. There is no reason they can't self-host (without publishing the interface to the entire 'net) and then just use GitHub as another remote to handle external collaboration.

swah 12y ago

Tried the product again (w/ no repos..) and it looks very nice. Dogfooding, drop the "written in Go" like technomancy says, big-ass buttons "Import from my Github" and "Import from existing repository". This should be more popular!

thawkins 12y ago
Written in GO is important for us as we have inhouse GO skills, we dont have ruby skills. This tool would be perfect for us, if it had AD/LDAP integration. Being written in GO means we can consider doing it ourselves.
- Vendan 12y ago
  Go look at the code, it's crappily written and virtually unmaintainable. I'm using it right now, but only by breaking it's concurrency. If I let it handle more then 1 request at a time, it starts 404'ing random resources....