Hi All, I would like to send my official resignation as a core member of the documentation team. I no longer use ChucK to the extent that I am an expert and I have not committed to the documentation in at least a year. I want to see the community flourish, as I see on the list, and as such I am serving as a gatekeeper to updating and improving the manual. Last year we tried a documentation push that had some interesting developments and I think was ultimately a failure because we did not push enough traffic there. Their export to PDF was ( and in my opinion still is) inadequate for generating a manual that can be shipped with ChucK. My suggestion moving forward is to move to Markdown or asciidoc for generating files that can be easily turned into html or pdf with appropriate style files for each. Github has proved to be an excellent place for collaborating on these types of projects and I would suggest that as a place to get the migrating going. I would be more than happy to help with the migration to a new platform or to help a new person get up to speed on how I generated the PDF manual so they can continue to update it with all of the great discoveries and suggestions on the list. I would also be happy to do some actual porting work of the documentation to a new system that can be more easily maintained if that is what is deemed necessary by the community or new point person. For history, the original manual was generated by me with help from Ge and Phil sometime in 2005 or so. I got into ChucK very seriously at that point and emailed the list or Ge personally to figure out how to do certain things in the language. For every email Ge sent me I created a tutorial or reference and compiled it into a document. Ge, Phil, and I spent many a night generating web references, then I would port that to LaTeX for the PDF manual. Since that time many other people have contributed references that have since been included in the manual and it has grown to the document we know today. It was a lot of fun and I think it had a significant impact on getting new users into ChucK. I want to thank the ChucK team and community, and I look forward to helping you get to the next place. Adam (--art)
Adam;
It was a lot of fun and I think it had a significant impact on getting new users into ChucK. I want to thank the ChucK team and community, and I look forward to helping you get to the next place.
Yes. We'll have to talk some more about all this, maybe with Tomasz who was very actively involved with the last "push", but first I'd like to thank you for your effort. I remember the Bad Old Days when the only docs were online, so not there when you'd be traveling with your laptop. I think I saved them a html page at a time back then... It's very easy to point out issues that the docs are lacking, but we shouldn't forget what a HUGE improvement your pdf was and how much more accessible it made ChucK. Fortunately we don't have the kind of community that tells people to "RTFM", but at least we could, if we wanted to. Thanks, Kas.
hi,
I too would like to acknowledge the great work you have done Adam as
the documentation and tutorials was the way that I learnt ChucK.
I would be interested in being involved in continuing the
documentation of ChucK onwards.
all the best
Scott
2011/6/2 Kassen
Adam;
> It was a lot of fun and I think it had a significant impact on getting new users into ChucK. I want to thank the ChucK team and community, and I look forward to helping you get to the next place.
Yes. We'll have to talk some more about all this, maybe with Tomasz who was very actively involved with the last "push", but first I'd like to thank you for your effort. I remember the Bad Old Days when the only docs were online, so not there when you'd be traveling with your laptop. I think I saved them a html page at a time back then...
It's very easy to point out issues that the docs are lacking, but we shouldn't forget what a HUGE improvement your pdf was and how much more accessible it made ChucK. Fortunately we don't have the kind of community that tells people to "RTFM", but at least we could, if we wanted to. Thanks, Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i'd like to say that the pdf file is good, i have to make it in to a plaintextfile, because that's easier to read with the synthesizer, ancient me, i just like plaintext better for some reason, (gets out cane and goes "you young whippersnappers and your new fangled reading formats.") I'm not sure why it did this, though the conversion process seemed to like to mess up words and phrases, and that's not a good thing when you are trying to learn how to write code. Still i'm a lot further along than if i had nothing at all to work with, so yay for that. On 6/2/2011 3:14 PM, Scott Hewitt wrote:
hi,
I too would like to acknowledge the great work you have done Adam as the documentation and tutorials was the way that I learnt ChucK.
I would be interested in being involved in continuing the documentation of ChucK onwards.
all the best
Scott
2011/6/2 Kassen
: Adam;
It was a lot of fun and I think it had a significant impact on getting new users into ChucK. I want to thank the ChucK team and community, and I look forward to helping you get to the next place.
Yes. We'll have to talk some more about all this, maybe with Tomasz who was very actively involved with the last "push", but first I'd like to thank you for your effort. I remember the Bad Old Days when the only docs were online, so not there when you'd be traveling with your laptop. I think I saved them a html page at a time back then...
It's very easy to point out issues that the docs are lacking, but we shouldn't forget what a HUGE improvement your pdf was and how much more accessible it made ChucK. Fortunately we don't have the kind of community that tells people to "RTFM", but at least we could, if we wanted to. Thanks, Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJN7GkCAAoJEIaKvi7tbzRH7AgH/3hbIeLjmIBUg5Y91WMDlYOU 02p5vHss01qciTcQRAmMmerbxaMeH2EKO/0gv8nzM8ot8srqu9hTQTwlMyjMRQs0 ih0qLvj/PIMAyPtR1edfiCiqiEtOCJGnj5B464LOgDYWmrF48B2+91OW8NS/CPjF Ewn8csQTt7axZRjzoHFIywf5q4yY41KefBXwiQkoB+yJDVmjodeZg+MlyvEU02Wm 1P4MogwsRoT+L3baO/+eiwfWOcESPdrZ3IZStmF7u3C4LZ7D/4GgIai27Kb0CJNy vrZyltM4iSmmJSQ/H+p4SwtHrs3unLqMiyzNnTSDJCe7DyLUkr6+gmFO9TstBhA= =9uin -----END PGP SIGNATURE-----
participants (4)
-
Adam Tindale
-
Kassen
-
Scott Hewitt
-
tempjayren@gmail.com