-
Notifications
You must be signed in to change notification settings - Fork 54
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
Backup copy of all conversations (issues/PRs) of this repo #96
Comments
If they can remove the repo from trending list without any T&C violations, what will stop them from removing it from GitHub? Seriously, @nicholas-c try to answer this question. |
Because it's simply not in their interest to do so? What would they gain from doing so? It's a pretty simple precedent really. |
Exactly the same as they're gaining from removal this repo from trending. Prevent spreading information about GitHub issues and its alternatives. Fewer people will know about GitLab/BitBucket/whatnot => More people will stay here => Moar $$$ to M$. |
So, in your reality @nicholas-c, what is the reason for removing this repo from trending? Just a small bug in GitHub algorithms? Or somebody gives just a couple of craps because this repo is growing quickly? |
I imagine you're just not as trendy as you thought you were |
Come on, guys! I'm trying to be paranoid here, stop posting foil-cap jokes and making me laugh :D |
@limonte are you planning on removing your repos like sweetalert2 from github? |
@7twin I don't know yet. Probably no, at least not before M$ will start censorship. Anyways, the decision on moving out isn't just mine, there are multiple collaborators in that repository and we will vote before making any decisions. |
@dkfiresky I almost died laughing. |
@evyatarmeged great to hear that. |
@limonte Microsoft has no power over GitHub yet... Sigh... |
I really doubt that they'll delete this repo, but we could just make a discord group or a Slack. |
Guys, can you figure out the based/easiest way for users to export all the Issues and comments under them ASAP? We are going to need it. |
Sorry I have no tolerance for people who consider this an open forum when it isn't. But all of this won't matter very soon. I'll be making an announcement and a change to this repo so that everyone can have what they want (though they've always had that freedom). |
@vassudanagunta Like I said, it's probably a better idea to get all developers together in a discord or a slack instead of just trying to export the issues/comments. Issues by themselves have very little power -- but a group of developers do. If this repository were to be removed, we have no way of finding each others again. But I don't see why the repository would be removed anyways, it's not like we're being disrespectful or causing havoc. |
I'm a believer in self-organization and teams doing whatever works for them. That's what makes a team. What we have here is not a team and will not gel into one because of all the differences. So please, organize as you see fit! I will post a link to whatever you set up. |
@vassudanagunta Alright... Well to respond to your question, you can access all the issues on a repository by using GitHub's API: https://api.github.com/repos/upend/IF_MS_BUYS_GITHUB_IMMA_OUT/issues/events I uploaded them to an unlisted pastebin: https://pastebin.com/uJpB1n6z As for the comments in each issues, |
The comments are more important than the issue titles... they contain the work of people so far, their research, their ideas. |
It does not just contain the issues titles, it contains the issues description too. I'm just trying to contribute here, it's better than nothing. Quite frankly, you could also just save each issue one by one as 'html page' if you're really worried about it. If we keep using the GitHub API approach, then you could use https://api.github.com/repos/upend/IF_MS_BUYS_GITHUB_IMMA_OUT/issues/96/comments to get the comments of the #96 https://api.github.com/repos/upend/IF_MS_BUYS_GITHUB_IMMA_OUT/issues/94/comments to get the comments of the #94 etc. |
Here's why a way to export issues and comments is really important: #114. If you guys have a solution that everyone can use, that would be awesome. |
I disagree with @nicholas-c but I do respect his opinions. He spent his personal time to put his thoughts and numbers into very structured comments and you vanished all his effort. Good luck @vassudanagunta with what you're doing. I was with you and your initiative from the very beginning, but now IMMA OUT from here. |
Hello, The GitHub Evacuation Project has moved to GitLab (not an endorsement or even a final home). Your enthusiasm and contribution is still needed. Please check out the new project home, and read the project wiki for info to get restarted. Thank you! vas |
In case (when) they will delete this repo (#92), all our communication will be vanished.
As I see the solution, some service should periodically trigger GitHub API to fetch every issue and all issue comments and store them somewhere.
Does anyone have any idea how can we make a reserve copy of all conversations of this repo?
Whatwver the solution will be, it should be linked in the README, so all forks will have that information as well.
The text was updated successfully, but these errors were encountered: