Hi Scott, thanks for that. fortunately I've already got the PDF version few years ago. but of course it would be great to have it back on line and updated. I just sent a request for a login ID on the Floss website. Honestly I've never edited anything on it. do you have any experience with it? cheers, Mario On 02/23/2018 12:17 AM, Scott Hewitt wrote:

Hi,

I would be happy to help out with this

Also you can get to the floss manual via

http://write.flossmanuals.net/chuck/events/

All the best

Scott

---------- visit me

http://www.scotthewitt.co.uk @scotthewitt

http://www.ablelemon.co.uk http://www.theaudiopodcast.co.uk

On 22 February 2018 at 23:55, mario buoninfante wrote:

...

Hi everybody,

I had a quick look at the FLOSS manual (http://write.flossmanuals.net/chuck/introduction/) and I noticed the link is broken. since I'm discovering a lot of hidden stuff in the source code (Teabox, CNoise, DelayP, etc.), stuff not documented anywhere, I thought it would be great to update the manual.

is there anyone interested in helping out?

cheers,

Mario

_______________________________________________ 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

how do I unsubscribe from responses to this mailing list On Fri, Feb 23, 2018 at 1:28 PM, Spencer Salazar

wrote:

Hey Mario and Scott,

Sounds great, improving documentation is a great place where the community can get involved with the project!

Spencer

On Thu, Feb 22, 2018 at 4:20 PM, mario buoninfante < mario.buoninfante@gmail.com> wrote:

...

Hi Scott,

thanks for that. fortunately I've already got the PDF version few years ago. but of course it would be great to have it back on line and updated.

I just sent a request for a login ID on the Floss website. Honestly I've never edited anything on it. do you have any experience with it?

cheers,

Mario

On 02/23/2018 12:17 AM, Scott Hewitt wrote:

...

Hi,

I would be happy to help out with this

Also you can get to the floss manual via

http://write.flossmanuals.net/chuck/events/

All the best

Scott

---------- visit me

http://www.scotthewitt.co.uk @scotthewitt

http://www.ablelemon.co.uk http://www.theaudiopodcast.co.uk

On 22 February 2018 at 23:55, mario buoninfante wrote:

...

Hi everybody,

I had a quick look at the FLOSS manual (http://write.flossmanuals.net/chuck/introduction/) and I noticed the link is broken. since I'm discovering a lot of hidden stuff in the source code (Teabox, CNoise, DelayP, etc.), stuff not documented anywhere, I thought it would be great to update the manual.

is there anyone interested in helping out?

cheers,

Mario

_______________________________________________ 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

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Spencer Salazar, PhD Special Faculty Music Technology: Interaction, Intelligence, and Design California Institute of the Arts

ssalazar@calarts.edu | +1 831.277.4654 <(831)%20277-4654> https://spencersalazar.com

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- musician + web developer michaelmansourati.com

Absolutely, translations are really important as well. Now I got an ID that allows me access the floss manual and this afternoon I'll have a look at it. I'll report here what is the current status. In this way we all can think about how to tackle it. Cheers, Mario On 24/02/18 14:12, tth wrote:

On 02/23/2018 07:28 PM, Spencer Salazar wrote:

...

Hey Mario and Scott,

Sounds great, improving documentation is a great place where the community can get involved with the project!

   Make me thinking about a french translation.