[GEM-dev] commit access for help files
Hans-Christoph Steiner
hans at eds.org
Fri Mar 31 05:24:27 CEST 2006
I am working on the 5 part intro to Pd workshop outlined here:
http://puredata.org/dev/pddp/IntroWorkshopSeries
As I am doing that, I am going to be going thru the Gem docs a lot.
A lot of the Gem help patches are quite nice, like cube-help.pd with
the [pd gemwin] subpatch, and the clear format. I'd like to fix some
of the others, like gemwin-help.pd, which are still quite raw.
Should I just send updated versions to y'all, or commit them directly
(in which case I would need commit access)? A lot of the time, it'll
be minor changes, like typos, small changes in working, etc.
Also, I was thinking that [pd gemwin] should be an object rather than
a subpatch. Its handy for normal Gem use.
.hc
________________________________________________________________________
____
If you are not part of the solution, you are part of the problem.
-
Eldridge Cleaver
More information about the GEM-dev
mailing list