connorshea

8 ms·

1. 31.▲
   by connorshea 9y ago

   Just for the record, I believe most of the community has moved from Gogs to Gitea (a fork) because of management issues in the original project.
2. 32.▲
   by connorshea 9y ago

   I don't think MediaWiki uses Hack, only PHP with HHVM (though I could be wrong).
3. 33.▲
   by connorshea 9y ago

   We do have project templates now for a few web frameworks, and the web editor can give you .gitignore templates, but yeah we don't currently have a way of adding these files by default when creating a project.
4. 34.▲
   by connorshea 9y ago

   Thanks, we'll keep making the product better. :) Glad to hear you're happy with the transition!
5. 35.▲
   by connorshea 9y ago

   To be clear, this is only relevant for Windows. Otherwise, GitLab will work fine with clients on 2.14.0. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13344
6. 36.▲
   by connorshea 9y ago

   I'm not Chloe, but I do work at GitLab. This depends on the role, but if you can DM me on twitter ( https://twitter.com/connorjshea ) I'd be happy to forward you to whoever I can.
7. 37.▲
   by connorshea 9y ago

   I'm a Community Advocate at GitLab, what features are you missing from GitLab issues that prevented you from switching?
8. 38.▲
   by connorshea 9y ago

   We describe our plans for Gitter / Mattermost in this blog post: https://about.gitlab.com/2017/03/15/gitter-acquisition/ We intend to keep both around as they serve different purposes :)
9. 39.▲
   by connorshea 9y ago

   Why do you say it's messy? Would love to get feedback on improvements we can make :)
10. 40.▲
    by connorshea 10y ago

    We have some relevant issues linked from the Postmortem blog post: https://about.gitlab.com/2017/02/10/postmortem-of-database-o...
11. 41.▲
    by connorshea 10y ago

    This section specifically has the comparisons: https://about.gitlab.com/products/#compare-options
12. 42.▲
    by connorshea 10y ago

    We've been improving performance for all users over the last year, in the last few weeks we introduced a custom load balancer among other things. One thing these changes _should_ do is decrease the strain on the shared runners so you d
13. 43.▲
    by connorshea 10y ago

    Fair criticism, I've brought it up with the team. Thanks :)
14. 44.▲
    by connorshea 10y ago

    I can't find an issue for this specifically, could you open one so we can get it tracked? https://gitlab.com/gitlab-org/gitlab-ce/issues
15. 45.▲
    by connorshea 10y ago

    Thanks for switching to GitLab, glad to hear you're loving it! :D We have this demo from our most recent summit where we put together an entire GitLab instance in ~20 minutes on a Kubernetes cluster, though I'm not sure that'
16. 46.▲
    by connorshea 10y ago

    We have open source self-hosted (Community Edition), open core self-hosted (Enterprise Edition), or hosted (GitLab.com). It's more like GitHub + Chat + CI + CD + Heroku + New Relic (early stages). Where Heroku forces you to use their p
17. 47.▲
    by connorshea 10y ago

    I'd argue that extra screen real estate for the content that matters often lends itself toward better UX, but any specific suggestions for improvements would be appreciated. :)
18. 48.▲
    by connorshea 10y ago

    I'd personally (not speaking on behalf of the company) love to acquire Sublime, but it's probably too expensive at this point. I'm pretty sad to see Atom eclipse Sublime so much recently, Sublime is so much faster and change
19. 49.▲
    by connorshea 10y ago

    Yeah, unfortunately that's because we made a mistake, here's the relevant issue if you want more info (PDF because it's a private repo so I can't link directly to it unfortunately): https://drive.google.com&#x
20. 50.▲
    by connorshea 10y ago

    Why not use Mattermost for something like this? We ship it with GitLab Omnibus and it's open core. https://about.mattermost.com/ EDIT: Previously said open source, open core is the correct term.
21. 51.▲
    by connorshea 10y ago

    Sorry this happened to you, I’ve brought it up with our PeopleOps team and we’re looking into it. Something like this absolutely shouldn’t be happening. If you have any more information you can share, it'd be great if you could send it
22. 52.▲
    by connorshea 10y ago

    More like `git merge gitter` :)
23. 53.▲
    by connorshea 10y ago

    Ha! Any suggestions? ;)
24. 54.▲
    by connorshea 10y ago

    For us it was natural to open the source code, we prefer to work that way. All our source code is publicly viewable and most of it is open source.
25. 55.▲
    by connorshea 10y ago

    Thanks for the confidence in our approach :D Being open and honest about everything is super important to our company culture. We definitely have some great stuff in the pipeline for the next few months.
26. 56.▲
    by connorshea 10y ago

    Whoops, sorry. Opened a merge request to fix that. https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
27. 57.▲
    by connorshea 10y ago

    The git data itself was untouched, but in the eyes of the DB there was no project that got created due to the lost DB data, so the git repo isn't hooked up. If you can give me the username and project name I can have support fix it up
28. 58.▲
    by connorshea 10y ago

    To be clear, we lost six hours of data. Not something we're proud of at all, but I figured an exact number would be useful.
29. 59.▲
    by connorshea 10y ago

    Looks like it's back up now, sorry about that :(
30. 60.▲
    by connorshea 10y ago

    Yeah, we've wanted that ourselves. There's an issue for it, but it's not scheduled yet. If you know Go, feel free to take a crack at it :)