I originally started using Github for Pd mainly because it would make it far easier for people to contribute to the project, ie. PR instead of .patch files. It's definitely delivered on that aspect.
I also agree on not jumping ship on a whim. It would be better to leverage one of the university connections and find a stable, more long term location. Its git, after all, so it's easy to just push to a new location. It becomes harder to carry the unfinished work, like open PRs with us, so that would need to be managed/mirrored for a while.
I also set up a Gitlab some of us are using internally at ZKM and it's pretty useful so far. As always, someone needs to maintain and backup the server and it would be great if a university IT department could handle that. :)
On Jun 5, 2018, at 6:00 AM, pd-dev-request@lists.iem.at wrote:
Date: Mon, 4 Jun 2018 17:27:48 +0200 From: "Christof Ressi" <christof.ressi@gmx.at mailto:christof.ressi@gmx.at> To: pd-dev <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at> Subject: Re: [PD-dev] Github being bought by MS Message-ID: trinity-0f991093-5c4f-42e2-acdd-08e4881ec7f3-1528126068418@3c-app-gmx-bs20
Content-Type: text/plain; charset=UTF-8
Actually, Sourceforge has been pretty evil in the past (like injecting installers with adware) and the new owners are still trying to recover from it. I guess Microsoft will be very careful not to mess up things with GitHub :-)
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
As seen at the month long outrage of the linuxaudio.org server with mailinglist, a university hosted server isn't the golden failsafe solution either.
m.
On 05.06.2018 16:05, Dan Wilcox wrote:
I originally started using Github for Pd mainly because it would make it far easier for people to contribute to the project, ie. PR instead of .patch files. It's definitely delivered on that aspect.
I also agree on not jumping ship on a whim. It would be better to leverage one of the university connections and find a stable, more long term location. Its git, after all, so it's easy to just push to a new location. It becomes harder to carry the unfinished work, like open PRs with us, so that would need to be managed/mirrored for a while.
I also set up a Gitlab some of us are using internally at ZKM and it's pretty useful so far. As always, someone needs to maintain and backup the server and it would be great if a university IT department could handle that. :)
On Jun 5, 2018, at 6:00 AM, pd-dev-request@lists.iem.at mailto:pd-dev-request@lists.iem.at wrote:
Date: Mon, 4 Jun 2018 17:27:48 +0200 From: "Christof Ressi" <christof.ressi@gmx.at mailto:christof.ressi@gmx.at> To: pd-dev <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at> Subject: Re: [PD-dev] Github being bought by MS Message-ID: trinity-0f991093-5c4f-42e2-acdd-08e4881ec7f3-1528126068418@3c-app-gmx-bs20
Content-Type: text/plain; charset=UTF-8
Actually, Sourceforge has been pretty evil in the past (like injecting installers with adware) and the new owners are still trying to recover from it. I guess Microsoft will be very careful not to mess up things with GitHub :-)
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
2018-06-05 11:05 GMT-03:00 Dan Wilcox danomatika@gmail.com:
I originally started using Github for Pd mainly because it would make it far easier for people to contribute to the project, ie. PR instead of .patch files. It's definitely delivered on that aspect.
not being an actual programmer, I can say I was only able to do minor contributions to Pd and work on external libraries because I found the interface of github (and github desktop, specially) to be reasonably easy to deal with.
I guess I can manage to adapt to other scenarios, but with IOhannes' remarks, I don't think I'll ditch github for my own projects unless something really fishy comes up from this MS merging. But most of all, I'm just worry they screw things up dramatically, like they did it with Skype :)
cheers
Hi Dan,
On 05/06/18 22:05, Dan Wilcox wrote:
I also agree on not jumping ship on a whim. It would be better to leverage one of the university connections and find a stable, more long term location. Its git, after all, so it's easy to just push to a new location.
I also set up a Gitlab some of us are using internally at ZKM and it's pretty useful so far. As always, someone needs to maintain and backup the server and it would be great if a university IT department could handle that. :)
If I recall correctly Jonathan Wilkes previously offered the use of the GitLab instance where he is hosting Purrr Data.
It becomes harder to carry the unfinished work, like open PRs with us, so that would need to be managed/mirrored for a while.
It's possible to fetch all GitHub PRs to your local:
https://gist.github.com/piscisaureus/3342247
Cheers,
Chris.
On 2018-06-07 03:00, Chris McCormick wrote:
If I recall correctly Jonathan Wilkes previously offered the use of the GitLab instance where he is hosting Purrr Data.
iirc think this was the OSUOSL (Oregon State University Open Source Labs), i mentioned in my reply.
It becomes harder to carry the unfinished work, like open PRs with us, so that would need to be managed/mirrored for a while.
It's possible to fetch all GitHub PRs to your local:
jeez, i didn't know that. this looks great.
fgmasdr IOhannes
On 07/06/18 15:05, IOhannes m zmoelnig wrote:
On 2018-06-07 03:00, Chris McCormick wrote:
It's possible to fetch all GitHub PRs to your local:
jeez, i didn't know that. this looks great.
I found this other hack too for fetching single PRs without adding a bunch of remotes:
$ cat ~/bin/git-fetch-github-pr #!/bin/sh
if [ "$1" = "" ] then echo "Usage: `basename $0` PR-ISSUE-ID [BRANCH]" else branch=${2-master} git fetch origin pull/$1/head:$branch fi
Cheers,
Chris.
-
Alexandre Torres Porres -
Chris McCormick -
Dan Wilcox -
IOhannes m zmoelnig -
Max