News for hackers. Stuff that matters.
Re:New GitHub Terms of Service require removing many open-so... by akerro on Wednesday March 01, 2017 @02:14PM (#13767168)
Here, have it: https://gitlab.com/explore move your code here, thank me later.
Re:New GitHub Terms of Service require removing many open-so... by programbreeding on Wednesday March 01, 2017 @02:30PM (#13767362)
Nothing wrong with gitlab, I personally use their self-hosted product. But just a reminder to all that they lost a bunch of data 1 month ago today [0].

However they were completely open and transparent about what happened, and they handled it as well as they could have.

[0] https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-...

Re:New GitHub Terms of Service require removing many open-so... by connorshea on Wednesday March 01, 2017 @02:52PM (#13767597)
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.
Re:New GitHub Terms of Service require removing many open-so... by pluma on Wednesday March 01, 2017 @03:07PM (#13767749)
Also to be clear GitLab (apparently) didn't lose any data actually stored in git from that timeframe, "just" the data stored via GitLab itself (issues, wikis, etc).

It's of course still bad because GitLab makes a big deal of being about the "whole package" rather than just version control, but it's not the massive potential for intellectual property loss "six hours of data" implies for what most think of primarily as a git hosting service.

Re:New GitHub Terms of Service require removing many open-so... by dullroar on Wednesday March 01, 2017 @03:58PM (#13768246)
Not quite. I coincidentally signed up for a GitLab account that very day, at that very time period, to make a minor change to someone else's project. I (1) set up my account, (2) forked their project, (3) made the change, and (4) issued a pull request. Came back the next day and none of that was there, including my forked git repo. I had to do it all over again, and it was clear it was a clean wipeout of everything, because I was allowed to re-register with the exact same userid, etc. I know that is a rare-snowflake event, but the fact I had a repo and had even sent a pull request from it shows they did, in fact, lose some data in git itself.
Re:New GitHub Terms of Service require removing many open-so... by connorshea on Wednesday March 01, 2017 @04:54PM (#13768827)
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 for you.

If you don't want to do that in this thread, feel free to email me: connor at gitlab.com

Re:New GitHub Terms of Service require removing many open-so... by dullroar on Wednesday March 08, 2017 @08:43PM (#13826049)
It's all good. I just replicated all the work (setting up the account, my forked repo, the change, my pull request) the next day.
Re:New GitHub Terms of Service require removing many open-so... by majewsky on Wednesday March 01, 2017 @02:24PM (#13767278)
This story made me grab my Github username and org names on Gitlab. :)
Re:New GitHub Terms of Service require removing many open-so... by mcs_ on Wednesday March 01, 2017 @02:23PM (#13767268)
I partially agree.

gitlab is a very good alternative... but i think that porting of a working project (not just code) is still complicate to accomplish. Manually import items like:

- issues - projects - users

it is very expensive in terms of operation.

I know that there are products, libs and API to, let say, mirror your repository, but all those tools, after you dive into some READMEs, are just not enough.

BTW: if anybody knows how to do "1 to 1" porting from github to gitlab i will appreciate it

Re:New GitHub Terms of Service require removing many open-so... by Etzos on Wednesday March 01, 2017 @02:33PM (#13767394)
Migrating issues and projects is pretty trivial since GitLab has an import tool specifically to pull things out of GitHub: https://docs.gitlab.com/ce/workflow/importing/import_project...
Re:New GitHub Terms of Service require removing many open-so... by theptip on Wednesday March 01, 2017 @03:22PM (#13767918)
Also worth noting is that you can configure a recurring one-way sync to periodically bring the slave repo up to date; this is useful for giving Gitlab a try while not committing to leaving Github as your primary hosting service.
Re:New GitHub Terms of Service require removing many open-so... by wereHamster on Wednesday March 01, 2017 @02:22PM (#13767261)
Until gitlab decides to 'update' their ToS, at which point prepare to move to yet another hosting service. Right?
Re:New GitHub Terms of Service require removing many open-so... by gpm on Wednesday March 01, 2017 @02:25PM (#13767292)
At worst, self hosted gitlab will always work.
Re:New GitHub Terms of Service require removing many open-so... by astrodust on Wednesday March 01, 2017 @03:11PM (#13767804)
These legal issues are real and no amount of running away and ignoring them will resolve them.

This is an intractable part of open-source software development. We can piss all over GitHub for trying to figure it out and getting it wrong, but at least they're trying.

Re:New GitHub Terms of Service require removing many open-so... by mirabilos on Wednesday March 01, 2017 @03:06PM (#13767745)
just ssh, git and gitweb will do.

Or self-hosted FusionForge if you need more fancy stuff.

Re:New GitHub Terms of Service require removing many open-so... by compuguy on Wednesday March 01, 2017 @03:21PM (#13767909)
There's also Gogs as well.
Re:New GitHub Terms of Service require removing many open-so... by wyldfire on Wednesday March 01, 2017 @02:29PM (#13767354)
Only if their terms [1] are more favorable.

I did a quick skim and didn't see anything regarding waiving attribution rights.

[1] https://about.gitlab.com/terms/

Re:New GitHub Terms of Service require removing many open-so... by ergo14 on Wednesday March 01, 2017 @02:28PM (#13767342)
OR better yet - just install rhodecode, use Git/mercurial however you want + you get awesome code review.
[dead]
Re:New GitHub Terms of Service require removing many open-so... by sctb on Wednesday March 01, 2017 @03:12PM (#13767818)
Users are probably flagging this comment because it is unnecessarily inflammatory. That tends not to do good things to the discussion, and even evokes associations with trolling.
Re:New GitHub Terms of Service require removing many open-so... by catshirt on Wednesday March 01, 2017 @03:40PM (#13768063)
must we check any semblance of emotion at the door? i am simply trying to put into words the emotions invoked having used their product.

if we want to suggest I'm opening up a potential argument by being "unnecessarily inflammatory", id say that GitLab as a product is the unecessary inflammation that started the argument.

I didnt insult anyone- I have a ton of respect for the GitLab guys and I genuinely wish them the best of luck. which is why I'm not going to step on eggshells when I have the opportunity to describe my experience with their product.

edit: was downvoted again, on this post, before anyone could have feasibly had the time to read and put any reasonable thought into it.

thoughtful conviction, passion, and opinions won't be the downfall of HN. but overzealous censorship might. For such an intelligent community, we seem to have an awfully hard time reading between the lines.

all that aside- lets be honest- I've been here long enough to wager I'm being downvoted out of pure disagreement. a bigger offense, in my opinion (if I may be so brave as to share it....)

Re:New GitHub Terms of Service require removing many open-so... by blister on Wednesday March 01, 2017 @04:14PM (#13768439)
I think it's your third paragraph here. You claim not to have insulted anyone, but you literally claimed that GitLab employees are worse than Hitler.

That's:

A) Super inflammatory B) Extremely disrespectful C) Adds nothing of value to the discussion

You're absolutely allowed to have a difference of opinion. Even saying something like, "I really hate the GitLab interface and it feels super janky" would have probably gone through this unscathed.

But you definitely were rude and openly hostile.

Re:New GitHub Terms of Service require removing many open-so... by catshirt on Wednesday March 01, 2017 @04:24PM (#13768558)
bringing Hitler into the discussion was a (perhaps rude or disrespectful) attempt at tongue in cheek humor, for which Id be willing to apologize. But- if I was trying to be seriously critical or hostile or start an argument - I would have said Thiel or Trump instead. I wouldn't have made the least justifiable argument of all time.

so while I appreciate and generally agree with your response, i still can't believe the hostility of my post garnered the downvotes- considering my completely tame and submissive second response was downvoted even further :)

(Ps - I absolutely never compared any person to Hitler- as a joke or otherwise. interpreting it that way seems lazy. if anything, I said the product is worse than Hitler. which is slightly more defensible and slightly less hostile.)