It sounds like to most people the priority ( as it should be ) is
cleaning up the docs for the main API. I'm thinking I'll just start
plonking away at my own user guide to the csound python api, and if I
can make enough time to make it worthwhile, it can be used if people
want. Of course the source will be open. ;-)

I'll use svn, sphinx, and trac. If anyone wants to submit links to
material that I can incorporate or use as a reference, that would be
cool. It's been so long since I csounded that I'm a bit lost on the doc
front. I intend to write for someone with minimal python experience.

Thanks
Iain


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

You might want to take a look at "A Csound Tutorial" and "A Csound
Algorithmic Composition Tutorial", which both try to get beginners
started with the Csound Python API. If you like we can talk about your
contributing to these documents, which are open source, but of course
it's fine with me if you want to just do your own thing.

Regards,
Mike

On 10/21/09, Iain Duncan  wrote:
> It sounds like to most people the priority ( as it should be ) is
> cleaning up the docs for the main API. I'm thinking I'll just start
> plonking away at my own user guide to the csound python api, and if I
> can make enough time to make it worthwhile, it can be used if people
> want. Of course the source will be open. ;-)
>
> I'll use svn, sphinx, and trac. If anyone wants to submit links to
> material that I can incorporate or use as a reference, that would be
> cool. It's been so long since I csounded that I'm a bit lost on the doc
> front. I intend to write for someone with minimal python experience.
>
> Thanks
> Iain
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Wed, 2009-10-21 at 12:56 -0700, Iain Duncan wrote:
> It sounds like to most people the priority ( as it should be ) is
> cleaning up the docs for the main API. I'm thinking I'll just start
> plonking away at my own user guide to the csound python api, and if I
> can make enough time to make it worthwhile, it can be used if people
> want. Of course the source will be open. ;-)
> 
> I'll use svn, sphinx, and trac. If anyone wants to submit links to
> material that I can incorporate or use as a reference, that would be
> cool. It's been so long since I csounded that I'm a bit lost on the doc
> front. I intend to write for someone with minimal python experience.
> 

Victor and Michael and Rory, do you have any issues with your writing
and examples being used for this?

thanks
Iain



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Wed, 2009-10-21 at 16:01 -0400, Michael Gogins wrote:
> You might want to take a look at "A Csound Tutorial" and "A Csound
> Algorithmic Composition Tutorial", which both try to get beginners
> started with the Csound Python API. If you like we can talk about your
> contributing to these documents, which are open source, but of course
> it's fine with me if you want to just do your own thing.

Well part of it is that writing docs actually means I learn it well. ;-)
And it can be quite a bit easier to make something new-user-friendly by
starting with a green-field. I would like to use material from other
sources, but one of my goals is to keep this thing up to date.

thanks
Iain

> 
> Regards,
> Mike
> 
> On 10/21/09, Iain Duncan  wrote:
> > It sounds like to most people the priority ( as it should be ) is
> > cleaning up the docs for the main API. I'm thinking I'll just start
> > plonking away at my own user guide to the csound python api, and if I
> > can make enough time to make it worthwhile, it can be used if people
> > want. Of course the source will be open. ;-)
> >
> > I'll use svn, sphinx, and trac. If anyone wants to submit links to
> > material that I can incorporate or use as a reference, that would be
> > cool. It's been so long since I csounded that I'm a bit lost on the doc
> > front. I intend to write for someone with minimal python experience.
> >
> > Thanks
> > Iain
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> 
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I have no issues, everything I do is open source. I would appreciate credit.

Regards,
Mike

On 10/21/09, Iain Duncan  wrote:
> On Wed, 2009-10-21 at 12:56 -0700, Iain Duncan wrote:
>> It sounds like to most people the priority ( as it should be ) is
>> cleaning up the docs for the main API. I'm thinking I'll just start
>> plonking away at my own user guide to the csound python api, and if I
>> can make enough time to make it worthwhile, it can be used if people
>> want. Of course the source will be open. ;-)
>>
>> I'll use svn, sphinx, and trac. If anyone wants to submit links to
>> material that I can incorporate or use as a reference, that would be
>> cool. It's been so long since I csounded that I'm a bit lost on the doc
>> front. I intend to write for someone with minimal python experience.
>>
>
> Victor and Michael and Rory, do you have any issues with your writing
> and examples being used for this?
>
> thanks
> Iain
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Wed, 2009-10-21 at 16:04 -0400, Michael Gogins wrote:
> I have no issues, everything I do is open source. I would appreciate credit.

Of course. Is there a license I should use to be csound compatible?

Iain

> 
> Regards,
> Mike
> 
> On 10/21/09, Iain Duncan  wrote:
> > On Wed, 2009-10-21 at 12:56 -0700, Iain Duncan wrote:
> >> It sounds like to most people the priority ( as it should be ) is
> >> cleaning up the docs for the main API. I'm thinking I'll just start
> >> plonking away at my own user guide to the csound python api, and if I
> >> can make enough time to make it worthwhile, it can be used if people
> >> want. Of course the source will be open. ;-)
> >>
> >> I'll use svn, sphinx, and trac. If anyone wants to submit links to
> >> material that I can incorporate or use as a reference, that would be
> >> cool. It's been so long since I csounded that I'm a bit lost on the doc
> >> front. I intend to write for someone with minimal python experience.
> >>
> >
> > Victor and Michael and Rory, do you have any issues with your writing
> > and examples being used for this?
> >
> > thanks
> > Iain
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> 
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

None.
On 21 Oct 2009, at 21:02, Iain Duncan wrote:

> On Wed, 2009-10-21 at 12:56 -0700, Iain Duncan wrote:
>> It sounds like to most people the priority ( as it should be ) is
>> cleaning up the docs for the main API. I'm thinking I'll just start
>> plonking away at my own user guide to the csound python api, and if I
>> can make enough time to make it worthwhile, it can be used if people
>> want. Of course the source will be open. ;-)
>>
>> I'll use svn, sphinx, and trac. If anyone wants to submit links to
>> material that I can incorporate or use as a reference, that would be
>> cool. It's been so long since I csounded that I'm a bit lost on the  
>> doc
>> front. I intend to write for someone with minimal python experience.
>>
>
> Victor and Michael and Rory, do you have any issues with your writing
> and examples being used for this?
>
> thanks
> Iain
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Anything "open source" would be compatible. You could use the LGPL,
which is what Csound uses. The plain GPL is not "open source" it is
"free software" and it is NOT compatible. If you're not clear on the
difference between "open source" and "free software," look at

    http://www.opensource.org


Regards,
Mike

On 10/21/09, Victor Lazzarini  wrote:
> None.
> On 21 Oct 2009, at 21:02, Iain Duncan wrote:
>
>> On Wed, 2009-10-21 at 12:56 -0700, Iain Duncan wrote:
>>> It sounds like to most people the priority ( as it should be ) is
>>> cleaning up the docs for the main API. I'm thinking I'll just start
>>> plonking away at my own user guide to the csound python api, and if I
>>> can make enough time to make it worthwhile, it can be used if people
>>> want. Of course the source will be open. ;-)
>>>
>>> I'll use svn, sphinx, and trac. If anyone wants to submit links to
>>> material that I can incorporate or use as a reference, that would be
>>> cool. It's been so long since I csounded that I'm a bit lost on the
>>> doc
>>> front. I intend to write for someone with minimal python experience.
>>>
>>
>> Victor and Michael and Rory, do you have any issues with your writing
>> and examples being used for this?
>>
>> thanks
>> Iain
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Wed, 2009-10-21 at 16:10 -0400, Michael Gogins wrote:
> Anything "open source" would be compatible. You could use the LGPL,
> which is what Csound uses. The plain GPL is not "open source" it is
> "free software" and it is NOT compatible. If you're not clear on the
> difference between "open source" and "free software," look at
> 
>     http://www.opensource.org

It depends on who you ask about the definition of opensource. In fact,
the above link says GPL is an opensource license. I think what you mean
is that any non(-strong/viral)-copyleft license is suitable.

http://www.gnu.org/copyleft/

-- 
Saludos,
Felipe Sateler

Yes, that is what I mean, non-viral-copyleft.

Regards,
Mike

On 10/21/09, Felipe Sateler  wrote:
> On Wed, 2009-10-21 at 16:10 -0400, Michael Gogins wrote:
>> Anything "open source" would be compatible. You could use the LGPL,
>> which is what Csound uses. The plain GPL is not "open source" it is
>> "free software" and it is NOT compatible. If you're not clear on the
>> difference between "open source" and "free software," look at
>>
>>     http://www.opensource.org
>
> It depends on who you ask about the definition of opensource. In fact,
> the above link says GPL is an opensource license. I think what you mean
> is that any non(-strong/viral)-copyleft license is suitable.
>
> http://www.gnu.org/copyleft/
>
> --
> Saludos,
> Felipe Sateler
>


-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

You can use anything you can find from me out there.

Rory.


2009/10/21 Michael Gogins :
> Yes, that is what I mean, non-viral-copyleft.
>
> Regards,
> Mike
>
> On 10/21/09, Felipe Sateler  wrote:
>> On Wed, 2009-10-21 at 16:10 -0400, Michael Gogins wrote:
>>> Anything "open source" would be compatible. You could use the LGPL,
>>> which is what Csound uses. The plain GPL is not "open source" it is
>>> "free software" and it is NOT compatible. If you're not clear on the
>>> difference between "open source" and "free software," look at
>>>
>>>     http://www.opensource.org
>>
>> It depends on who you ask about the definition of opensource. In fact,
>> the above link says GPL is an opensource license. I think what you mean
>> is that any non(-strong/viral)-copyleft license is suitable.
>>
>> http://www.gnu.org/copyleft/
>>
>> --
>> Saludos,
>> Felipe Sateler
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net