[PD] Cyclone future

[Alexandre Torres Porres]

2016-02-21 16:35 GMT-03:00 Fred Jan Kraan <fjkraan at xs4all.nl>:

> I decided to stop working on it.


well, I have to say I'm actually deeply sorry for that cause I think you've
been doing a great job working on fixes and all


> There is no benefit for the community in having two diverging versions of
> cyclone.
>

Agreed, but I thought we could all work in just one, too bad if that can't
happen.

Anyway, this year I had plans to start coding and building externals. A
close friend of mine here in Brazil - who's active in the Pd community as a
developer - was willing to help me/teach me. I just talked to him (Flávio
Schiavoni - he's on this list but also copied here on this message) and
he's also available to help us in the maintenance of cyclone regarding the
more technical issues like building the library and keeping it for download
via deken.

I can continue to be involved doing things like

- work on the documentation/help files
- test, find and report bugs and issues in the current objects
- list missing functionalities to be added on current and existing objects
according to newer versions of Max (5+)
- test and help in the implementation of new objects
- keep track of a "To Do List"

As my coding skills improve, I can also work on bug fixes and implementing
new objects, but for now I need help from Schiavoni, who's onboard with me
on this.

I know there are others willing to contribute coding new objects and all,
of course anyone who's willing to help is welcome.

Now, leaving aside issues of future maintenance, and regarding the very
purpose and *Future of* the *Cyclone* project, I don't believe anything
should differ from the original project description, which says its a *set
of objects cloned from Max/MSP* (..) *bringing some level of compatibility
between Max/MSP and Pd environments *(..) *mainly for people using both Max
and Pd*

There's nothing in the original project description about the following
goals of future development, but maybe we could discuss it and make it
explicit.

A)- Ideally, objects should be kept updated to the functionalities existent
in the most to date Max/MSP versions
B)- Ideally, we should have all possible objects cloned

We know in practice that's a crazy amount of work, so collaborators are
free to work on what they consider more relevant and important.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160221/08763e50/attachment.html>