3 ms·

Nice! I really hope some competitor to GitHub will arrive someday soon.

by romanovcode 11y ago

sytse 11y ago
I think we're already there, what would you like to see?
- izolate 11y ago
  Please copy GitHub's CSS styles for its markdown files. This may sound petty, but I really think it's part of the reason why open source projects do so well there. GitHub nailed it. It's a pleasure to read compared to the competition's representation. This will help: http://sindresorhus.com/github-markdown-css/ http://sindresorhus.com/github-markdown-css/
  - sytse 11y ago
    Obviously copying anything is not possible unless they have a free license. I agree that GitHub's rendering of markdown files is much better than ours. We hope to improve it. Our first interaction engineer just started and we're looking to hire more https://about.gitlab.com/jobs/ https://about.gitlab.com/jobs/ Of course, you're very welcome to submit improvements yourself, as long as you do not submit proprietary code.
    - izolate 11y ago
      Cool, I'd be pleased to submit a merge request. :)
      - sytse 11y ago
        Please do!
        sytse 11y ago
        I'm happy to report we just improved the markdown file rendering in GitLab, this started because of the comments here.
        izolate 11y ago
        Ah, that was going to be my excuse to start contributing to GitLab! But either way, happy it's been taken care of.
        sytse 11y ago
        :) there is still enough to do, see http://feedback.gitlab.com/forums/176466-general/status/796455 http://feedback.gitlab.com/forums/176466-general/status/7964...
- shabble 11y ago
  Having switched over for a week or two now to a self-hosted instance, there are some major workflow issues we've encountered. Odds are good that some are just undiscoverd features/user error, but: * Navigation between 'root' project and per-user forks is terrible. There's no way I can see to go from the root proj (where all the issues/MRs are) to my fork. All the necessary data is available over the API, just not present on in the UI. * Issue labelling is kinda nasty. You default to no labels for a new project, but you can 'generate' the default set. If you want to add a new label from teh 'new issue' page, it doesn't show up as an option after adding. Make it a modal or refresh teh list or something. * You don't seem to eb able to search by commit # in the search fields? * 'merge this MR' button sometimes just arbitrarily fails, and refreshign the page and hitting it again will work (no commits/repo changes in teh meantime) * No equiv. of the github 'network graph' that also shows other forks. * It took a bunch of pissing around to disable gravatar which was giving mixed content SSL warnings even though it shouldn't. * Live preview of teh markdown input for comments/messages would be nice, especially with some apparently odd heuristics for deciding whether to autolink something like a same-repo/file:line type. * Having read the various docs I can find a few times now, I still have no clue how to set up gitlab-CI on a self-hosted instance. As I say, some of this is probably just not knowing where things are, but it's not for want of looking.
  - sytse 11y ago
    Thanks for sharing the issues you encountered! * I agree it is too hard to find forks. https://gitlab.com/gitlab-org/gitlab-ce/issues/2406 https://gitlab.com/gitlab-org/gitlab-ce/issues/2406 * I agree we should make it easier to add new labels to an issue https://gitlab.com/gitlab-org/gitlab-ce/issues/2574 https://gitlab.com/gitlab-org/gitlab-ce/issues/2574 * I would normally replace the full commit sha1 in the url of another commit. But feel free to add it to the search. * That is strange, hopefully this gets better when we get rid of satellites in 8.0 * Indeed, the graph is for one repo, the calculations are done live and are cached, but doing it for many forks could take too long. * We load the gravatar's over https by default if you enable https in gitlab.yml https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L110 https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/g..., it is strange that you had a mixed content warning. * Issue comments should have a preview tab. * The documentation is in https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/gitlab-ci/README.md https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc... but after 8.0 it will be integrated in GitLab itself so you no longer have to set it up separately.
- drewcrawford 11y ago
  Let me tell you my regular frustration, as a person migrating tons of stuff to GitLab. 1. Google "GitLab [obvious feature]" 2. Land on feedback.gitlab.com, on a feature request with hundreds of upvotes 3. "We're accepting pull requests" 4. Filed in 2013 5. Still open 6. Sigh loudly. 7. Check the blog for what evidently more important features they've been working on instead 8. "We're very excited to announce that we'll ship GitLab Mattermost, an open source, on-premises messaging app" 9. Sigh loudly 10. Conclude that they are probably an open source company strapped for cash and to cut them some slack 11. See HN article about closing series A 12. "Oh good, now they can finally get to their epic feature backlog" 13. "I think we're already there, what would you like to see?" 14. Sigh loudly. Don't get me wrong, I love GL. But wow is that workflow annoying.
  - sytse 11y ago
    There are 1000+ features open on feedback.gitlab.com, we can't make them all. If people contribute them that is a strong signal they are wanted. What is the feature you would like to see?

Nice! I really hope some competitor to GitHub will arrive someday soon.

sytse 11y ago

I think we're already there, what would you like to see?

izolate 11y ago
Please copy GitHub's CSS styles for its markdown files. This may sound petty, but I really think it's part of the reason why open source projects do so well there. GitHub nailed it. It's a pleasure to read compared to the competition's representation. This will help: http://sindresorhus.com/github-markdown-css/ http://sindresorhus.com/github-markdown-css/
- sytse 11y ago
  Obviously copying anything is not possible unless they have a free license. I agree that GitHub's rendering of markdown files is much better than ours. We hope to improve it. Our first interaction engineer just started and we're looking to hire more https://about.gitlab.com/jobs/ https://about.gitlab.com/jobs/ Of course, you're very welcome to submit improvements yourself, as long as you do not submit proprietary code.
  - izolate 11y ago
    Cool, I'd be pleased to submit a merge request. :)
    - sytse 11y ago
      Please do!
      - sytse 11y ago
        I'm happy to report we just improved the markdown file rendering in GitLab, this started because of the comments here.
        izolate 11y ago
        Ah, that was going to be my excuse to start contributing to GitLab! But either way, happy it's been taken care of.
        sytse 11y ago
        :) there is still enough to do, see http://feedback.gitlab.com/forums/176466-general/status/796455 http://feedback.gitlab.com/forums/176466-general/status/7964...
shabble 11y ago
Having switched over for a week or two now to a self-hosted instance, there are some major workflow issues we've encountered. Odds are good that some are just undiscoverd features/user error, but: * Navigation between 'root' project and per-user forks is terrible. There's no way I can see to go from the root proj (where all the issues/MRs are) to my fork. All the necessary data is available over the API, just not present on in the UI. * Issue labelling is kinda nasty. You default to no labels for a new project, but you can 'generate' the default set. If you want to add a new label from teh 'new issue' page, it doesn't show up as an option after adding. Make it a modal or refresh teh list or something. * You don't seem to eb able to search by commit # in the search fields? * 'merge this MR' button sometimes just arbitrarily fails, and refreshign the page and hitting it again will work (no commits/repo changes in teh meantime) * No equiv. of the github 'network graph' that also shows other forks. * It took a bunch of pissing around to disable gravatar which was giving mixed content SSL warnings even though it shouldn't. * Live preview of teh markdown input for comments/messages would be nice, especially with some apparently odd heuristics for deciding whether to autolink something like a same-repo/file:line type. * Having read the various docs I can find a few times now, I still have no clue how to set up gitlab-CI on a self-hosted instance. As I say, some of this is probably just not knowing where things are, but it's not for want of looking.
- sytse 11y ago
  Thanks for sharing the issues you encountered! * I agree it is too hard to find forks. https://gitlab.com/gitlab-org/gitlab-ce/issues/2406 https://gitlab.com/gitlab-org/gitlab-ce/issues/2406 * I agree we should make it easier to add new labels to an issue https://gitlab.com/gitlab-org/gitlab-ce/issues/2574 https://gitlab.com/gitlab-org/gitlab-ce/issues/2574 * I would normally replace the full commit sha1 in the url of another commit. But feel free to add it to the search. * That is strange, hopefully this gets better when we get rid of satellites in 8.0 * Indeed, the graph is for one repo, the calculations are done live and are cached, but doing it for many forks could take too long. * We load the gravatar's over https by default if you enable https in gitlab.yml https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example#L110 https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/g..., it is strange that you had a mixed content warning. * Issue comments should have a preview tab. * The documentation is in https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/gitlab-ci/README.md https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc... but after 8.0 it will be integrated in GitLab itself so you no longer have to set it up separately.
drewcrawford 11y ago
Let me tell you my regular frustration, as a person migrating tons of stuff to GitLab. 1. Google "GitLab [obvious feature]" 2. Land on feedback.gitlab.com, on a feature request with hundreds of upvotes 3. "We're accepting pull requests" 4. Filed in 2013 5. Still open 6. Sigh loudly. 7. Check the blog for what evidently more important features they've been working on instead 8. "We're very excited to announce that we'll ship GitLab Mattermost, an open source, on-premises messaging app" 9. Sigh loudly 10. Conclude that they are probably an open source company strapped for cash and to cut them some slack 11. See HN article about closing series A 12. "Oh good, now they can finally get to their epic feature backlog" 13. "I think we're already there, what would you like to see?" 14. Sigh loudly. Don't get me wrong, I love GL. But wow is that workflow annoying.
- sytse 11y ago
  There are 1000+ features open on feedback.gitlab.com, we can't make them all. If people contribute them that is a strong signal they are wanted. What is the feature you would like to see?