-
Notifications
You must be signed in to change notification settings - Fork 38
migrate to GitLab #446
Comments
I was sort of wondering why Gratipay wasn't built in GitLab. Would they be interested in using Gratipay? |
It's getting nicer… but it's still missing a basic feature: watching a repository. |
See also: https://github.com/dear-github/dear-github/ and dear-github/dear-github#56. I predict 2016 will be the Year of GitLab ... which means we may make the jump in 2017. ;-) |
https://gitlab.com/gitlab-org/gitlab-ce/issues/3414#note_2712093 Does that only apply to projects one owns/is a member of? |
GitLab employee here, found this thread via dear-github/dear-github#56 :)
@Changaco You can actually star a repository (like https://gitlab.com/gitlab-org/gitlab-ce) and see its activity on your "Starred Projects" dashboard: https://gitlab.com/dashboard/projects/starred
@whit537 Yeah, the "Watching" notification level only applies to projects one is a member of. Getting email for every new issue on a project you're not a member of is not (currently) possible. Let me know if you have any other questions! |
Thanks @DouweM. Welcome! :-)
Can you link us to the ticket for this on the GitLab repo? |
@whit537 I'm not aware of one, the closest thing is the feedback thread, but we're moving away from the feedback forum and moving to issues for everything. Feel free to create an issue! |
Watchers don't want to log into GitLab regularly to check for activity, they want notifications to come to them. |
Done! :-) |
How big is the GitLab userbase? Are we losing out on not being able to tag people directly? |
@mattbk I don't have a number right now, but if you want I can get back to you on that. I don't think the smaller user base will be an issue, because the people you would be likely to want to @mention, core team members, users filing issues or users contributing code, have already created an account on GitLab.com to be able to do that in the first place. Of course you lose some amount of discoverability and the immense network effect that GitHub brings with it, but how much of a problem that will be depends on the project. We certainly haven't seen any decrease in people contributing when we moved the main GitLab repository from https://github.com/gitlabhq/gitlabhq to https://gitlab.com/gitlab-org/gitlab-ce :) |
https://about.gitlab.com/2016/01/11/being-a-good-open-source-steward/ |
|
GitHub's new pricing (#617) pushes us further in this direction. |
This seems to have been released in 8.8 and deployed. |
From @sampablokuper in #724:
|
The big thing GitLab is missing is critical mass. Reopen when open source has moved there. |
GitLab is gettin' nicer and nicer. They now use GitLab as their primary feedback loop for GitLab, via award emoji! :-)
Is it time to make the move yet? We're certainly more philosophically aligned with them than we are with GitHub. Maybe we should test it out with a small project?
The text was updated successfully, but these errors were encountered: