Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code #106

Open
dotmilk opened this issue Jun 7, 2018 · 6 comments
Open

Code #106

dotmilk opened this issue Jun 7, 2018 · 6 comments

Comments

@dotmilk
Copy link

dotmilk commented Jun 7, 2018

I saw like most apologists, lots of 'no code here' arguments about being taken down as trending, are there some code snippets etc in other issues, like some bash stuff etc for migrating to a different place or fetching your issues, that we could compile into some .sh etc code to place in the repository.

TL/DR: Can we compile / combine github migration related code and place it into this repo?

@bakkerme
Copy link

bakkerme commented Jun 7, 2018

There's no requirement for code being in a repo, I mean look at danistefanovic/build-your-own-x, currently in the trending list. We were taken down purely because it's inconvenient.

@dotmilk
Copy link
Author

dotmilk commented Jun 7, 2018

I agree it was taken down as it was inconvenient to their image. And I'm aware of the fact that code is not needed, it's just another resource (which is what this repo is about):

'A space to learn or share escape routes — In the coming days we will collaboratively put together resources and guides on where best to move you and your projects and how.'

Has an added benefit of shutting down certain talking points.

I am also wondering if code related to migration is added, will it possibly trigger a larger (worse in the long run for their image) response from this soulless entity?

@bakkerme
Copy link

bakkerme commented Jun 7, 2018

I am also wondering if code related to migration is added, will it possibly trigger a larger (worse in the long run for their image) response from this soulless entity?

There's too much risk in damaging what little good will is left. Microsoft won't officially be in charge til later this year, and by more blatantly censoring inconvenient information, they risk an even greater backlash.
There's a great PR up with a solid guide and code to assist users to migrate to GitLab that should make for a good starting point and a template to work off for over platforms. Over the weekend I'm going to look at compiling some general resources about moving to other git hosting providers. This repo has too much attention to be wasted on bickering in the issues.

@dotmilk
Copy link
Author

dotmilk commented Jun 7, 2018

What bickering?

@bakkerme
Copy link

bakkerme commented Jun 7, 2018

Well, what I will say is that there's some less than productive conversation in a few of these issues.

I think the best way forward here is to focus on getting resources in the hands of the community. The high tensions of the acquisition will cool down in time and vassudanagunta can finally get some sleep 😜.

@vassudanagunta
Copy link
Contributor

Hey guys. Thanks so much for your work. I've decide on a way forward. See Issue 114.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants