91–100 of 212 posts
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
Earlier quoted context omitted.
It's a fundamental problem of open source projects hosting on GitHub. I don't think the the Fossil colocation model is necessarily right, but some open protocol is needed so that issues can be easily migrated between these services.
Is it really that hard to write a little script to copy the issues over? Github has an exceptional API.
Now it's time for them to move to Node. They currently use the JS engine from Firefox 45 (over 2 years old) and are looking to move to 52 (almost 15 months old). Let's not forget that the update before that was from FF25 which was from 2013. It's past time to port your stuff to N-API and actually allow devs to have access to standard dev tools using standard dev practices. It would be a great change for Gnome devs to…
That'd mean even more of the world relying on a monopolist of ecosystem of V8/Blink. V8/Blink already runs 70% of browsers and a massive amount of software, don't you think at some point it's enough with giving Google control over everything?
Earlier quoted context omitted.
There's an unofficial issue import API: https://gist.github.com/jonmagic/5282384165e0f86ef105 But it doesn't let you change ownership of issues or comments; everything appears as created by the importing user.
That makes sense. You shouldn't normally be allowed to impersonate another username, which is exactly what a full import does.
Also, you can impersonate commits freely.
I don't think allowing full import would be a big deal, especially if the UI made it clear that the comments were imported.
Earlier quoted context omitted.
That'd mean even more of the world relying on a monopolist of ecosystem of V8/Blink. V8/Blink already runs 70% of browsers and a massive amount of software, don't you think at some point it's enough with giving Google control over everything?
Why does using V8 or Blink give Google control over your software?
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
It's not like gnome was utilizing bugzilla anyways. They had one bug that was 11 years old.
Earlier quoted context omitted.
Probably because Github is a closed-source company that can remove you, your repo, or your group at any time, for any reason. Committing to a hosted service is a bad idea (see: Sourceforge). That sort of thing isn't acceptable to a project like Gnome.
To be clear, despite this announcement being posted to gitlab.com (i.e. the "hosted GitLab", which can and will remove you/your/repo any group at any time), the GNOME project is self-hosting their own gitlab instance. So they are indeed insulated from such hypothetical damage.
Earlier quoted context omitted.
Probably because Github is a closed-source company that can remove you, your repo, or your group at any time, for any reason. Committing to a hosted service is a bad idea (see: Sourceforge). That sort of thing isn't acceptable to a project like Gnome.
Just curious, has this ever happened? Were there any cases where github removed someone's repo?
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
Don't worry, those'll be cleared up in the next rewrite.