Complaints concerning github issue removal
Hi I noticed last week that issues on github were disabled. There are now 2 complaints in a pull request concerning this.
https://github.com/inkscape/inkscape/pull/20#issuecomment-251752290
Anyone able to answer them with some explanation? I assume code will eventually move to git/github/gitlab but we are not there yet...but I'm not sure what to answer "waldyrious" and "shakaran" on Github at the moment.
Best regards
On Fri, 2016-10-07 at 22:26 +0200, Christoffer Holmstedt wrote:
Hi I noticed last week that issues on github were disabled. There are now 2 complaints in a pull request concerning this.
https://github.com/inkscape/inkscape/pull/20#issuecomment-251752290
Anyone able to answer them with some explanation? I assume code will eventually move to git/github/gitlab but we are not there yet...but I'm not sure what to answer "waldyrious" and "shakaran" on Github at the moment.
I emailed both people privately explaining why the issues tracker was closed. Although it was closed for a while before, I re-opened it to close all the issues and point people to the real tracker then closed it again.
One of the two has responded by email and understands.
The main reason seems to be that the user was unwilling to join the mailing list and wanted emails from github. I'm going to note that for future because we shouldn't really divide up our community into different platform communication if possible.
Any way you can close the pull requests?
Best Regards, Martin Owens
2016-10-08 3:02 GMT+02:00 Martin Owens <doctormo@...400...>:
On Fri, 2016-10-07 at 22:26 +0200, Christoffer Holmstedt wrote:
Hi I noticed last week that issues on github were disabled. There are now 2 complaints in a pull request concerning this.
https://github.com/inkscape/inkscape/pull/20#issuecomment-251752290
Anyone able to answer them with some explanation? I assume code will eventually move to git/github/gitlab but we are not there yet...but I'm not sure what to answer "waldyrious" and "shakaran" on Github at the moment.
I emailed both people privately explaining why the issues tracker was closed. Although it was closed for a while before, I re-opened it to close all the issues and point people to the real tracker then closed it again.
One of the two has responded by email and understands.
The main reason seems to be that the user was unwilling to join the mailing list and wanted emails from github. I'm going to note that for future because we shouldn't really divide up our community into different platform communication if possible.
Any way you can close the pull requests?
Best Regards, Martin Owens
Actually, I'm not sure if we should close the pull requests at all because it is not possible to disable pull requests on github. With Bryce's reply to the pull request it might be easier for the future to keep it open and just link to that reply in future pull requests. More pull request will eventually come that way no matter if we close or leave it open, but it will be more visible if we leave it open.
On Sun, Oct 09, 2016 at 07:29:08AM +0200, Christoffer Holmstedt wrote:
2016-10-08 3:02 GMT+02:00 Martin Owens <doctormo@...400...>:
On Fri, 2016-10-07 at 22:26 +0200, Christoffer Holmstedt wrote:
Hi I noticed last week that issues on github were disabled. There are now 2 complaints in a pull request concerning this.
https://github.com/inkscape/inkscape/pull/20#issuecomment-251752290
Anyone able to answer them with some explanation? I assume code will eventually move to git/github/gitlab but we are not there yet...but I'm not sure what to answer "waldyrious" and "shakaran" on Github at the moment.
I emailed both people privately explaining why the issues tracker was closed. Although it was closed for a while before, I re-opened it to close all the issues and point people to the real tracker then closed it again.
One of the two has responded by email and understands.
The main reason seems to be that the user was unwilling to join the mailing list and wanted emails from github. I'm going to note that for future because we shouldn't really divide up our community into different platform communication if possible.
Any way you can close the pull requests?
Best Regards, Martin Owens
Actually, I'm not sure if we should close the pull requests at all because it is not possible to disable pull requests on github. With Bryce's reply to the pull request it might be easier for the future to keep it open and just link to that reply in future pull requests. More pull request will eventually come that way no matter if we close or leave it open, but it will be more visible if we leave it open.
Yes, those are some good points. You're right, we do plan to move off of Launchpad at some point, at least for code hosting and reviews. The main hitch presently (apart from needing to focus on the release in the near term) is reaching a consensus on a decision between gitlab and github.
Meanwhile, I don't see too much problem to experimenting with allowing pull requests off-Launchpad, if there are volunteers such as yourself to keep an eye on things (and review/forward/land salient bits). However, I think it would save us some trouble down the road if we could finalize our decision on gitlab vs. github, so we have a clear direction forward, even if the official transition is going to wait for a while.
Bryce
All & bryce,
I have some updated information with regard to GitLab. Matt Lee who used to work for the FSF has just gotten a job at GitLab and as good friend here in Boston, I was able to talk to him casually about our situation.
He recommends talking to him and GitLab about our CI requirements, they'll be willing to give us more support and assistance than a typical registrant project.
He also recommended keeping a clone of the project on Github, quoting "you know where GitLab keeps a copy of it's code, GitHub"
I'd be willing to talk more with Matt about the issue if others are interested. I also talked about some of the Free Software issues regarding GitLab and he says they're moving in the right direction and he is committed to Free Software while there.
Best Regards, Martin Owens Inkscape Boston ;-)
On Tue, 2016-10-11 at 11:35 -0700, Bryce Harrington wrote:
Yes, those are some good points. You're right, we do plan to move off of Launchpad at some point, at least for code hosting and reviews. The main hitch presently (apart from needing to focus on the release in the near term) is reaching a consensus on a decision between gitlab and github.
Meanwhile, I don't see too much problem to experimenting with allowing pull requests off-Launchpad, if there are volunteers such as yourself to keep an eye on things (and review/forward/land salient bits). However, I think it would save us some trouble down the road if we could finalize our decision on gitlab vs. github, so we have a clear direction forward, even if the official transition is going to wait for a while.
Bryce
On Tue, Oct 11, 2016 at 03:32:00PM -0400, Martin Owens wrote:
All & bryce,
I have some updated information with regard to GitLab. Matt Lee who used to work for the FSF has just gotten a job at GitLab and as good friend here in Boston, I was able to talk to him casually about our situation.
He recommends talking to him and GitLab about our CI requirements, they'll be willing to give us more support and assistance than a typical registrant project.
He also recommended keeping a clone of the project on Github, quoting "you know where GitLab keeps a copy of it's code, GitHub"
I'd be willing to talk more with Matt about the issue if others are interested. I also talked about some of the Free Software issues regarding GitLab and he says they're moving in the right direction and he is committed to Free Software while there.
Wow, that's great, and definitely +1 for a followup discussion with him.
I think it would be especially useful if you could connect Krzysztof and him up, as he'd done the most detailed comparison of github and gitlab for us so far, and probably would have some good questions.
Thanks, Bryce
Best Regards, Martin Owens Inkscape Boston ;-)
On Tue, 2016-10-11 at 11:35 -0700, Bryce Harrington wrote:
Yes, those are some good points. You're right, we do plan to move off of Launchpad at some point, at least for code hosting and reviews. The main hitch presently (apart from needing to focus on the release in the near term) is reaching a consensus on a decision between gitlab and github.
Meanwhile, I don't see too much problem to experimenting with allowing pull requests off-Launchpad, if there are volunteers such as yourself to keep an eye on things (and review/forward/land salient bits). However, I think it would save us some trouble down the road if we could finalize our decision on gitlab vs. github, so we have a clear direction forward, even if the official transition is going to wait for a while.
Bryce
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAABCAAGBQJX/T4wAAoJEOVbsiwf4qcg1RkP/03HogDgQLV8xPoVVD4yWZ+f vJvtKJgpBXDj28iDEW1qFdtOXONk7/bIrgK9oKYCRBYTyKjzY59meXKMjz2EnCLu QwMEjMVvh3iCx1Kia2Snjpr5GsPZh19XxZrIMm09VPyd91Wr64qmdhGX1HlYIiBa alx+ehvjEXgPFQyN0EIeAWS8/Iv/lAl7obV8kgBmy8GcgjLBmv7cmSOBg4ykjOhu Ux0t50BbLST1eKZJ8UxP38S+LlOP4AgEO0GHS6emPbCOIOjDTz6/bX2nTbzmgQc5 ZsSVpeb09QkxiTY5Xvs4UXURZ7l45q0MTjGnqvRmtiQBNN9jpLd9kMgobzxbe2Hi qC8XDDudOpOEBc5f7uEE6v/uZq9fVlcukJaW5sSyN7kiW0xjeT/QXLtT1RZGgSbf tAaaMFB2OLTctPvOL7UPIcFYvtp+wqfAzqKRg1qpLmaozt7kRaTa6a4qDu7Wx8dz m1w+LuUrLFfr25an+MjhHTFZgzl88CFdTlAaNiGQ/lPfFr9JTbfC4kvkUmQDKT8I TA4M8od2DvvOhVAM9rAV3jP0q7YTGn4n/NLVPeyaxjLnf7RpFRo7reQxjff7cYSh OZ6M4EdfDh7mlVqrMzyoWBUvUM033fJSb+qInaiBY0yQsU0VX5i2rpsiY4/MZyYz l6JERZorUdxugsNliZT+ =SJFm -----END PGP SIGNATURE-----
participants (3)
-
Bryce Harrington -
Christoffer Holmstedt -
Martin Owens