Hey Hans,
I want to start pushing PdDroidParty src into Pd's SVN. Is that ok? Where should I put it in the tree?
Cheers,
Chris.
Its fine by me. But perhaps there is a better place for it. If I
remember correctly, you were using bazaar. Sourceforge supports
bazaar, so you could use that.
I think it would make the most sense to have it in its own repo,
whether on Sourceforge or elsewhere, whether on SVN or bzr. Then it
is easy to manage the list of committers.
.hc
On Oct 5, 2011, at 10:54 PM, Chris McCormick wrote:
Hey Hans,
I want to start pushing PdDroidParty src into Pd's SVN. Is that ok?
Where should I put it in the tree?Cheers,
Chris.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Programs should be written for people to read, and only incidentally
for machines to execute.
- from Structure and Interpretation of Computer Programs
Hi Hans,
Yep, I am using bazaar, which can use SVN sub-trees as a storage back-end. I am currently hosting it on the PdDroidParty site on my server, but I thought it might be good to have the code also in the SVN as it is part of the Pd ecosystem (and for redundancy too). I am happy to continue maintaining it in my own repo though. Because bzr is a DVCS I can still merge stuff from other contributors and retain their information in the commit log.
Oh well, sorry for the noise!
Cheers,
Chris.
Its fine by me. But perhaps there is a better place for it. If I remember correctly, you were using bazaar. Sourceforge supports bazaar, so you could use that.
I think it would make the most sense to have it in its own repo, whether on Sourceforge or elsewhere, whether on SVN or bzr. Then it is easy to manage the list of committers.
.hc
On Oct 5, 2011, at 10:54 PM, Chris McCormick wrote:
Hey Hans,
I want to start pushing PdDroidParty src into Pd's SVN. Is that ok? Where should I put it in the tree?
Cheers,
Chris.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
-
Chris McCormick -
Hans-Christoph Steiner