Tags:

    Re: contributing to jamoma

    Hi

    Given the many false starts I had with FTM, I can only second these
    news sound great, indeed. I hope being able to follow the dynamic,
    this time.

    Best,
    Julien




    Le 12 juil. 2010 à 23:33, Pascal Baltazar <pb@zkrx.org> a écrit :

    > Hi !
    >
    > That sounds great !
    >
    > I also wanted to mention that Diemo and Théo will spend a couple day
    > s at the end of the month (possibly 29th + 30th) working on Jamoma 0
    > .6 prototyping in relation to FTM...
    >
    > I will spend a couple days too (25-28th) working with Diemo on
    > CataRT, probably with some Jamoma integration
    >
    > So that all sounds like a great dynamics starting around these
    > subjects..
    >
    > Best,
    >
    > p
    >
    > On 12 Jul 2010, at 22:55, Trond Lossius wrote:
    >
    >> Hi Adrian,
    >>
    >> thanks for the fix, I have committed it to the master branch now. I
    >> have also set you up as developer for most of the Redmine projects,
    >> If you need additional permissions, please let me know.
    >>
    >> Your help will be much welcome in the project, as will
    >> contributions towards documentation. If you have additional patches
    >> to contribute, using Redmine as you did this time is a easy way of
    >> doing so. Alternatively, if you are aquatinted with GIT, you might
    >> want to download Jamoma from GIT and build, and we could give you
    >> permissions to work on the repositories that you would be
    >> interested in contributing towards.
    >>
    >> Regarding Jamoma and FTM, the project that am (or should be)
    >> working on, deals with how to use FTM for high level storing and
    >> controlling of Jamoma modules, by querying modules for their states
    >> or tracking changes over time, storing the information as FTM data
    >> structures, and then be able to operate on it. I am planning to
    >> keep working on that during this summer. I think that it might also
    >> be interesting to create an extended version of jcom.parameter that
    >> would be able to maintain FTM objects as parameters. That should
    >> probably go into a UserLib to avoid a general dependence of Jamoma
    >> on FTM. That might be a more ambitious project, but could be quite
    >> useful.
    >>
    >> Your input in the process will definitively be useful, and the
    >> module(s) you are working on sounds highly interesting. Tom Stoll
    >> have been porting parts of CataRT to Jamoma, so there might be some
    >> interesting possibilities in connecting the various initiatives at
    >> some point.
    >>
    >> Best,
    >> Trond
    >>
    >>
    >>
    >> On Jul 11, 2010, at 4:25 AM, Adrian Gierakowski wrote:
    >>
    >>> Hi Trond,
    >>>
    >>> Just wanted to let you know that I updated the Bug #532 on http://redmine.jamoma.org/issues
    >>>
    >>> It is the first time I am contributing something to jamoma and I
    >>> don't know exactly how things work. I submitted a corrected
    >>> version of a help patch that wasn't working properly but I didn't
    >>> close the case since I don't know when is a case considered to be
    >>> closed. Should the corrected file be submitted to the repository
    >>> somehow? I have a "report" status so I guess I wouldn't be able to
    >>> do it anyway.
    >>>
    >>> I do not have much experience with programming in C, C++ and so
    >>> on, but I do have with max so I am happy to contribute to thing
    >>> like the above case or maybe write some modules and contribute to
    >>> the documentation.
    >>>
    >>> Btw. I read somewhere on the web that you are involved with trying
    >>> to integrate ftm and jamoma. I am really into that since I am
    >>> currently working on a personal project (a generalized granulator)
    >>> using jamoma and ftm and I could contribute from a point of view
    >>> of an end user and patch/module designer. At what stage is the
    >>> whole project (or idea) anyway?
    >>>
    >>> Best wishes.
    >>>
    >>> --
    >>> Adrian Gierakowski
    >>>
    >>
    >