Hi All,

I'm looking at the content on csound.sf.net and csounds.com and
there's a great deal of overlap.  I'm thinking, instead of creating a
separate site, we update csounds.com with any information missing from
csound.sf.net.  The problem with this is that none of us who would
probably be editing the content related to development have any
editorial permissions on csounds.com.

I think with the current scheme, having only one resource at Berklee
updating the site is too much for one person.  No offense and of
course much appreciation to John Clements for his hard work, but I
think merging the sites and getting more people involved is going to
pool our resources together and ultimately be more effective (one
place for information).

I also think we should add a new tracker to the sourceforge site to
track updates for csounds.com.  People could then file requests and
bugs (i.e. bad URL links, etc.) for the site itself.  That would
certainly help manage all the great recommendations people have that
are suggested but get lost over time.

Thoughts?

steven

I agree with Steven. In what way would we merge them however?

On 21 February 2012 14:43, Steven Yi  wrote:
> Hi All,
>
> I'm looking at the content on csound.sf.net and csounds.com and
> there's a great deal of overlap.  I'm thinking, instead of creating a
> separate site, we update csounds.com with any information missing from
> csound.sf.net.  The problem with this is that none of us who would
> probably be editing the content related to development have any
> editorial permissions on csounds.com.
>
> I think with the current scheme, having only one resource at Berklee
> updating the site is too much for one person.  No offense and of
> course much appreciation to John Clements for his hard work, but I
> think merging the sites and getting more people involved is going to
> pool our resources together and ultimately be more effective (one
> place for information).
>
> I also think we should add a new tracker to the sourceforge site to
> track updates for csounds.com.  People could then file requests and
> bugs (i.e. bad URL links, etc.) for the site itself.  That would
> certainly help manage all the great recommendations people have that
> are suggested but get lost over time.
>
> Thoughts?
>
> steven
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Well, we'd have to ensure the information that was done on the
csound.sf.net site is incorporated into the csounds.com site (such as
mentioning linuxaudio.org and sourceforge, making the links to
downloads be individual like they are on csound.sf.net per platform,
etc.).  From my glances, Csounds.com could certainly have some more
information filled in.  Also, we'd eventually make csound.sf.net just
redirect to csounds.com.

On Tue, Feb 21, 2012 at 2:57 PM, Rory Walsh  wrote:
> I agree with Steven. In what way would we merge them however?
>
> On 21 February 2012 14:43, Steven Yi  wrote:
>> Hi All,
>>
>> I'm looking at the content on csound.sf.net and csounds.com and
>> there's a great deal of overlap.  I'm thinking, instead of creating a
>> separate site, we update csounds.com with any information missing from
>> csound.sf.net.  The problem with this is that none of us who would
>> probably be editing the content related to development have any
>> editorial permissions on csounds.com.
>>
>> I think with the current scheme, having only one resource at Berklee
>> updating the site is too much for one person.  No offense and of
>> course much appreciation to John Clements for his hard work, but I
>> think merging the sites and getting more people involved is going to
>> pool our resources together and ultimately be more effective (one
>> place for information).
>>
>> I also think we should add a new tracker to the sourceforge site to
>> track updates for csounds.com.  People could then file requests and
>> bugs (i.e. bad URL links, etc.) for the site itself.  That would
>> certainly help manage all the great recommendations people have that
>> are suggested but get lost over time.
>>
>> Thoughts?
>>
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Steven, I like and agree with all your ideas, and I will await Dr. Boulanger's directive on how we can all help achieve this unity of message and information using Csounds.com as more of an active community hub for our work and ideas.

As I am currently in the final semesters of my work here at Berklee, I would welcome any help with keeping the site up to date.

John

richard -

this sounds excellent. i think we are on a very good way to improve the
site more and more. i have some thoughts / questions i'd like to discuss
(with you and everyone being engaged in this topic):

1) my personal preference for "the one and only" site/address would be
csound.net. i find the .net domain most appropriate, and for people
looking the first time for csound in the net, the first contact starts
with an oddity: why this extra "s"?

in this context i remember that

2) the web tool currently being used at csounds.com might not be the
most user-friendly one. it is easy to post news, but maybe it's not the
best tool to allow a number of maintainers to include new features in a
flexible way. you, steven and john will know; i remember some people
were reporting this.

so i am wondering whether

3) it might be good to set a new tool at csound.net, and move the
content of csounds.com to csound.net (or even csound.org if it is not
possible to set this up at csound.net)?

	joachim



Am 22.02.2012 06:16, schrieb Dr. Richard Boulanger:
> Dear Steven,
> 
> This is a great plan.  
> 
> I do love the idea of Csounds.com  being the central
> repository and having other sites redirect to here.
> 
> I also agree that it would be a huge project and that we would love to
> have some help.
> Help to do this and to realize more of the ideas that come as we merge
> and expand.
> 
> I think that Steven already has the highest level of access at
> Csounds.com .
> Do you need me to do more to open up the site more to you?
> Happy to have others join Steven, John and I to help expand Csounds.com
> .
> Steven.  Let me know what you need and I appreciate your advice and your
> help coordinating
> this new initiative and the transition.  It will be wonderful. 
> 
> Dr.B.
> *___________________________________*
> *
> *
> *Dr. Richard Boulanger, Ph.D.*
> *
> *
> Professor of Electronic Production and Design
> Professional Writing and Music Technology Division
> Berklee College of Music
> 1140 Boylston Street
> Boston, MA 02215-3693
> 
> 617-747-2485 (office)
> 774-488-9166 (cell)
> 
> rboulanger@berklee.edu 
> http://csounds.com/boulanger
> ____________________________________
> 
> http://csounds.com 
> http://csoundforlive.com 
> ____________________________________
> 
> http://csounds.com/mathews
> ____________________________________
> 
> On Feb 21, 2012, at 11:36 AM, J Clements wrote:
> 
>> Steven, I like and agree with all your ideas, and I will await Dr.
>> Boulanger's directive on how we can all help achieve this unity of
>> message and information using Csounds.com  as more
>> of an active community hub for our work and ideas.
>>
>> As I am currently in the final semesters of my work here at Berklee, I
>> would welcome any help with keeping the site up to date.
>>
>> John
>>
>> On Feb 21, 2012 10:09 AM, "Steven Yi" > > wrote:
>>
>>     Well, we'd have to ensure the information that was done on the
>>     csound.sf.net  site is incorporated into
>>     the csounds.com  site (such as
>>     mentioning linuxaudio.org  and
>>     sourceforge, making the links to
>>     downloads be individual like they are on csound.sf.net
>>      per platform,
>>     etc.).  From my glances, Csounds.com  could
>>     certainly have some more
>>     information filled in.  Also, we'd eventually make csound.sf.net
>>      just
>>     redirect to csounds.com .
>>
>>     On Tue, Feb 21, 2012 at 2:57 PM, Rory Walsh >     > wrote:
>>     > I agree with Steven. In what way would we merge them however?
>>     >
>>     > On 21 February 2012 14:43, Steven Yi >     > wrote:
>>     >> Hi All,
>>     >>
>>     >> I'm looking at the content on csound.sf.net
>>      and csounds.com  and
>>     >> there's a great deal of overlap.  I'm thinking, instead of
>>     creating a
>>     >> separate site, we update csounds.com  with
>>     any information missing from
>>     >> csound.sf.net .  The problem with this
>>     is that none of us who would
>>     >> probably be editing the content related to development have any
>>     >> editorial permissions on csounds.com .
>>     >>
>>     >> I think with the current scheme, having only one resource at
>>     Berklee
>>     >> updating the site is too much for one person.  No offense and of
>>     >> course much appreciation to John Clements for his hard work, but I
>>     >> think merging the sites and getting more people involved is
>>     going to
>>     >> pool our resources together and ultimately be more effective (one
>>     >> place for information).
>>     >>
>>     >> I also think we should add a new tracker to the sourceforge site to
>>     >> track updates for csounds.com .  People
>>     could then file requests and
>>     >> bugs (i.e. bad URL links, etc.) for the site itself.  That would
>>     >> certainly help manage all the great recommendations people have
>>     that
>>     >> are suggested but get lost over time.
>>     >>
>>     >> Thoughts?
>>     >>
>>     >> steven
>>     >>
>>     >>
>>     >> Send bugs reports to the Sourceforge bug tracker
>>     >>          
>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>     
>>     >> Discussions of bugs and features can be posted here
>>     >> To unsubscribe, send email sympa@lists.bath.ac.uk
>>      with body "unsubscribe csound"
>>     >>
>>     >
>>     >
>>     > Send bugs reports to the Sourceforge bug tracker
>>     >          
>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>     
>>     > Discussions of bugs and features can be posted here
>>     > To unsubscribe, send email sympa@lists.bath.ac.uk
>>      with body "unsubscribe csound"
>>     >
>>
>>
>>     Send bugs reports to the Sourceforge bug tracker
>>              
>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>     
>>     Discussions of bugs and features can be posted here
>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>      with body "unsubscribe csound"
>>
> 

Hi Dr. B,

I think I either need more privileges or need to learn Drupal more to
figure out how to modify the site.  I was trying to update the
documentation page but did not see any means to edit it (it has old
links to the 5.14 manual, for example).  I'll email you and John
Clements off list to work all that out.

Otherwise, I'll start looking into content migration and updating things.

For csound.net, I'd like to propose we rebrand csounds.com as
csound.net.  It should be easy to have both domain names direct to the
same location, with links on csounds.com to redirect to the
corresponding URL location on csound.net.  Having the redirect would
maintain old links to things on csounds.com to point to the right
place.  This also gives us an opportunity to freshen up things and
update all around, and give us a goal for a newer, fuller, richer
site.

For Iain, I'll email you offlist for some advice regarding drupal as
you have experience with it.  It'd be great to hear what you think,
especially in regards to updating the site.

As for the design, I think we'll need something a bit fresher.  Let's
worry about content and site structure for now, and perhaps we can get
the community to offer up some designs.  Personally, I think we need
to start engaging with using more videos and audio mp3 playlists that
will demonstrate works done with Csound as well as ways of using
Csound beyond the command-line.  The use of Csound as a sound engine
library really is something that needs to be highlighted and while
those in the community know and understand how that works, we should
setup a dedicated page online that will present that to a new user.

Thanks!
steven

On Wed, Feb 22, 2012 at 11:28 AM, joachim heintz  wrote:
> richard -
>
> this sounds excellent. i think we are on a very good way to improve the
> site more and more. i have some thoughts / questions i'd like to discuss
> (with you and everyone being engaged in this topic):
>
> 1) my personal preference for "the one and only" site/address would be
> csound.net. i find the .net domain most appropriate, and for people
> looking the first time for csound in the net, the first contact starts
> with an oddity: why this extra "s"?
>
> in this context i remember that
>
> 2) the web tool currently being used at csounds.com might not be the
> most user-friendly one. it is easy to post news, but maybe it's not the
> best tool to allow a number of maintainers to include new features in a
> flexible way. you, steven and john will know; i remember some people
> were reporting this.
>
> so i am wondering whether
>
> 3) it might be good to set a new tool at csound.net, and move the
> content of csounds.com to csound.net (or even csound.org if it is not
> possible to set this up at csound.net)?
>
>        joachim
>
>
>
> Am 22.02.2012 06:16, schrieb Dr. Richard Boulanger:
>> Dear Steven,
>>
>> This is a great plan.
>>
>> I do love the idea of Csounds.com  being the central
>> repository and having other sites redirect to here.
>>
>> I also agree that it would be a huge project and that we would love to
>> have some help.
>> Help to do this and to realize more of the ideas that come as we merge
>> and expand.
>>
>> I think that Steven already has the highest level of access at
>> Csounds.com .
>> Do you need me to do more to open up the site more to you?
>> Happy to have others join Steven, John and I to help expand Csounds.com
>> .
>> Steven.  Let me know what you need and I appreciate your advice and your
>> help coordinating
>> this new initiative and the transition.  It will be wonderful.
>>
>> Dr.B.
>> *___________________________________*
>> *
>> *
>> *Dr. Richard Boulanger, Ph.D.*
>> *
>> *
>> Professor of Electronic Production and Design
>> Professional Writing and Music Technology Division
>> Berklee College of Music
>> 1140 Boylston Street
>> Boston, MA 02215-3693
>>
>> 617-747-2485 (office)
>> 774-488-9166 (cell)
>>
>> rboulanger@berklee.edu 
>> http://csounds.com/boulanger
>> ____________________________________
>>
>> http://csounds.com 
>> http://csoundforlive.com 
>> ____________________________________
>>
>> http://csounds.com/mathews
>> ____________________________________
>>
>> On Feb 21, 2012, at 11:36 AM, J Clements wrote:
>>
>>> Steven, I like and agree with all your ideas, and I will await Dr.
>>> Boulanger's directive on how we can all help achieve this unity of
>>> message and information using Csounds.com  as more
>>> of an active community hub for our work and ideas.
>>>
>>> As I am currently in the final semesters of my work here at Berklee, I
>>> would welcome any help with keeping the site up to date.
>>>
>>> John
>>>
>>> On Feb 21, 2012 10:09 AM, "Steven Yi" >> > wrote:
>>>
>>>     Well, we'd have to ensure the information that was done on the
>>>     csound.sf.net  site is incorporated into
>>>     the csounds.com  site (such as
>>>     mentioning linuxaudio.org  and
>>>     sourceforge, making the links to
>>>     downloads be individual like they are on csound.sf.net
>>>      per platform,
>>>     etc.).  From my glances, Csounds.com  could
>>>     certainly have some more
>>>     information filled in.  Also, we'd eventually make csound.sf.net
>>>      just
>>>     redirect to csounds.com .
>>>
>>>     On Tue, Feb 21, 2012 at 2:57 PM, Rory Walsh >>     > wrote:
>>>     > I agree with Steven. In what way would we merge them however?
>>>     >
>>>     > On 21 February 2012 14:43, Steven Yi >>     > wrote:
>>>     >> Hi All,
>>>     >>
>>>     >> I'm looking at the content on csound.sf.net
>>>      and csounds.com  and
>>>     >> there's a great deal of overlap.  I'm thinking, instead of
>>>     creating a
>>>     >> separate site, we update csounds.com  with
>>>     any information missing from
>>>     >> csound.sf.net .  The problem with this
>>>     is that none of us who would
>>>     >> probably be editing the content related to development have any
>>>     >> editorial permissions on csounds.com .
>>>     >>
>>>     >> I think with the current scheme, having only one resource at
>>>     Berklee
>>>     >> updating the site is too much for one person.  No offense and of
>>>     >> course much appreciation to John Clements for his hard work, but I
>>>     >> think merging the sites and getting more people involved is
>>>     going to
>>>     >> pool our resources together and ultimately be more effective (one
>>>     >> place for information).
>>>     >>
>>>     >> I also think we should add a new tracker to the sourceforge site to
>>>     >> track updates for csounds.com .  People
>>>     could then file requests and
>>>     >> bugs (i.e. bad URL links, etc.) for the site itself.  That would
>>>     >> certainly help manage all the great recommendations people have
>>>     that
>>>     >> are suggested but get lost over time.
>>>     >>
>>>     >> Thoughts?
>>>     >>
>>>     >> steven
>>>     >>
>>>     >>
>>>     >> Send bugs reports to the Sourceforge bug tracker
>>>     >>
>>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>     
>>>     >> Discussions of bugs and features can be posted here
>>>     >> To unsubscribe, send email sympa@lists.bath.ac.uk
>>>      with body "unsubscribe csound"
>>>     >>
>>>     >
>>>     >
>>>     > Send bugs reports to the Sourceforge bug tracker
>>>     >
>>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>     
>>>     > Discussions of bugs and features can be posted here
>>>     > To unsubscribe, send email sympa@lists.bath.ac.uk
>>>      with body "unsubscribe csound"
>>>     >
>>>
>>>
>>>     Send bugs reports to the Sourceforge bug tracker
>>>
>>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>     
>>>     Discussions of bugs and features can be posted here
>>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>>      with body "unsubscribe csound"
>>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Is there any way we could start using an updated interface for the
mailing list? I would love the see the mailing-list integrated fully
into the website. It's the single greatest resource for all things
Csound yet it's kind of hidden away a little from new users. Most
software projects have fully searchable forums accessible through the
projects website:

http://www.renoise.com/board/
http://forum.cockos.com/forumdisplay.php?f=20
http://www.rawmaterialsoftware.com/index.php

etc...

Rory.





On 25 February 2012 07:16, Dr. Richard Boulanger  wrote:
> Thanks Iain for all your advice.
>
> We would love your help as we migrate, merge, evolve.
>
> I have asked John Clements to contact you and give you top-level clearance
> so that you can look around and advise and help us to upgrade.
>
> If you want to coordinate with John and Steven that would be great.
>
> Before we get to far into things, we need to upate to the newest Drupal that
> is offered by Westhost.  I think we are currently running
> a Drupal which is a few versions behind.
>
> Happy to hear about your suggestions for The Csound Instrument Collection
> (online).  It would be nice to have a resource like this
> to which users could download, upload, search, listen, rate, comment...
> about instruments, pieces, etc....  I have the content... ready
> to go. (26 years of collected instruments and pieces.)
>
> My plan is to move some of my "personal" things from Csounds.com to my new
> Boulanger Labs website and offer Csounds.com,
> Csound.org, and thanks to Jacob Joaquin, Csound.net to the community - to
> have them all point to the same place - and to take advantage of some of the
> expertise in the community (such as yours) and the generous donation of time
> and energy of you and others
> to make this resource even more current, vital, and comprehensive - to
> better serve the growing community of Csounders.
>
> Dr. B.
> ___________________________________
>
> Dr. Richard Boulanger, Ph.D.
>
> Professor of Electronic Production and Design
> Professional Writing and Music Technology Division
> Berklee College of Music
> 1140 Boylston Street
> Boston, MA 02215-3693
>
> 617-747-2485 (office)
> 774-488-9166 (cell)
>
> rboulanger@berklee.edu
> http://csounds.com/boulanger
> ____________________________________
>
> http://csounds.com
> http://csoundforlive.com
> ____________________________________
>
> http://csounds.com/mathews
> ____________________________________
>
> On Feb 25, 2012, at 1:59 AM, Iain Duncan wrote:
>
> On Wed, Feb 22, 2012 at 7:02 AM, Steven Yi  wrote:
>>
>> Hi Dr. B,
>>
>> I think I either need more privileges or need to learn Drupal more to
>> figure out how to modify the site.  I was trying to update the
>> documentation page but did not see any means to edit it (it has old
>> links to the 5.14 manual, for example).  I'll email you and John
>> Clements off list to work all that out.
>
>
> That sounds like your account doesn't have edit privileges for the content
> type of the page you're looking at. If you did, there should be a very
> obvious 'edit' tab there when you're logged in.
>
>>
>>
>> Otherwise, I'll start looking into content migration and updating things.
>>
>>
>> For csound.net, I'd like to propose we rebrand csounds.com as
>> csound.net.  It should be easy to have both domain names direct to the
>> same location, with links on csounds.com to redirect to the
>> corresponding URL location on csound.net.  Having the redirect would
>> maintain old links to things on csounds.com to point to the right
>> place.  This also gives us an opportunity to freshen up things and
>> update all around, and give us a goal for a newer, fuller, richer
>> site.
>>
>> For Iain, I'll email you offlist for some advice regarding drupal as
>> you have experience with it.  It'd be great to hear what you think,
>> especially in regards to updating the site.
>
>
> Hmm, one caveat I should mention is that Drupal has uh, not done a very good
> job with regards to the update processes that are 'supposed to work'. So I
> would *highly highly* advise making sure that the web team is happy with the
> version of Drupal you're using before anyone spends tons of time migrating
> content over, or you may have some hair-pulling if content has been entered
> in and Drupal is to be upgraded. It's supposed to be fine, but depending on
> the modules enabled, it can either be fine or a gong show. :-/
>
> If there are issues, please feel free to email me off list. Use iainctduncan
> @ that giant email provider that runs the world instead of iainduncanlists
> in order to make sure I notice it quickly, I don't always open all threads
> on here! =) I'm pretty well versed in drupal content migration headaches and
> sometimes it's just easier to do stuff with python and mysql directly.
>
> Dr B, or those in the know, what version of Drupal is being used right now
> and are there any plans to upgrade?
>
> One thing I would definitely recommend against is spending much time making
> any kind of database app in Drupal to act as an online instrument catalog.
> That is much better done in Pyramid/Django/Ruby-on-Rails, the Drupal db
> framework is really primitive. If you want it to appear on the drupal site,
> I have code for making drupal proxy modules so that content from third party
> sites works exactly like it's part of the drupal site. We've done that for a
> bunch of clients now, making the hard stuff in Python/Pyramid with it served
> as a third party app and leaving general purpose content management in
> Drupal with some kind of proxy setup.  This works really well for any kind
> of ReST published db service, say if one wanted to be able to make different
> public facing tools have access to instrument catalogs.
>
> If anyone wants to give me access, I can poke around in it over the weekend
> and let you know my thoughts. I would love help the situation improve for
> the new user experience!
>
> iain
>
>>
>> As for the design, I think we'll need something a bit fresher.  Let's
>> worry about content and site structure for now, and perhaps we can get
>> the community to offer up some designs.  Personally, I think we need
>> to start engaging with using more videos and audio mp3 playlists that
>> will demonstrate works done with Csound as well as ways of using
>> Csound beyond the command-line.  The use of Csound as a sound engine
>> library really is something that needs to be highlighted and while
>> those in the community know and understand how that works, we should
>> setup a dedicated page online that will present that to a new user.
>>
>> Thanks!
>> steven
>>
>> On Wed, Feb 22, 2012 at 11:28 AM, joachim heintz 
>> wrote:
>> > richard -
>> >
>> > this sounds excellent. i think we are on a very good way to improve the
>> > site more and more. i have some thoughts / questions i'd like to discuss
>> > (with you and everyone being engaged in this topic):
>> >
>> > 1) my personal preference for "the one and only" site/address would be
>> > csound.net. i find the .net domain most appropriate, and for people
>> > looking the first time for csound in the net, the first contact starts
>> > with an oddity: why this extra "s"?
>> >
>> > in this context i remember that
>> >
>> > 2) the web tool currently being used at csounds.com might not be the
>> > most user-friendly one. it is easy to post news, but maybe it's not the
>> > best tool to allow a number of maintainers to include new features in a
>> > flexible way. you, steven and john will know; i remember some people
>> > were reporting this.
>> >
>> > so i am wondering whether
>> >
>> > 3) it might be good to set a new tool at csound.net, and move the
>> > content of csounds.com to csound.net (or even csound.org if it is not
>> > possible to set this up at csound.net)?
>> >
>> >        joachim
>> >
>> >
>> >
>> > Am 22.02.2012 06:16, schrieb Dr. Richard Boulanger:
>> >> Dear Steven,
>> >>
>> >> This is a great plan.
>> >>
>> >> I do love the idea of Csounds.com  being the
>> >> central
>> >> repository and having other sites redirect to here.
>> >>
>> >> I also agree that it would be a huge project and that we would love to
>> >> have some help.
>> >> Help to do this and to realize more of the ideas that come as we merge
>> >> and expand.
>> >>
>> >> I think that Steven already has the highest level of access at
>> >> Csounds.com .
>> >> Do you need me to do more to open up the site more to you?
>> >> Happy to have others join Steven, John and I to help expand Csounds.com
>> >> .
>> >> Steven.  Let me know what you need and I appreciate your advice and
>> >> your
>> >> help coordinating
>> >> this new initiative and the transition.  It will be wonderful.
>> >>
>> >> Dr.B.
>> >> *___________________________________*
>> >> *
>> >> *
>> >> *Dr. Richard Boulanger, Ph.D.*
>> >> *
>> >> *
>> >> Professor of Electronic Production and Design
>> >> Professional Writing and Music Technology Division
>> >> Berklee College of Music
>> >> 1140 Boylston Street
>> >> Boston, MA 02215-3693
>> >>
>> >> 617-747-2485 (office)
>> >> 774-488-9166 (cell)
>> >>
>> >> rboulanger@berklee.edu 
>> >> http://csounds.com/boulanger
>> >> ____________________________________
>> >>
>> >> http://csounds.com 
>> >> http://csoundforlive.com 
>> >> ____________________________________
>> >>
>> >> http://csounds.com/mathews
>> >> ____________________________________
>> >>
>> >> On Feb 21, 2012, at 11:36 AM, J Clements wrote:
>> >>
>> >>> Steven, I like and agree with all your ideas, and I will await Dr.
>> >>> Boulanger's directive on how we can all help achieve this unity of
>> >>> message and information using Csounds.com  as more
>> >>> of an active community hub for our work and ideas.
>> >>>
>> >>> As I am currently in the final semesters of my work here at Berklee, I
>> >>> would welcome any help with keeping the site up to date.
>> >>>
>> >>> John
>> >>>
>> >>> On Feb 21, 2012 10:09 AM, "Steven Yi" > >>> > wrote:
>> >>>
>> >>>     Well, we'd have to ensure the information that was done on the
>> >>>     csound.sf.net  site is incorporated into
>> >>>     the csounds.com  site (such as
>> >>>     mentioning linuxaudio.org  and
>> >>>     sourceforge, making the links to
>> >>>     downloads be individual like they are on csound.sf.net
>> >>>      per platform,
>> >>>     etc.).  From my glances, Csounds.com  could
>> >>>     certainly have some more
>> >>>     information filled in.  Also, we'd eventually make csound.sf.net
>> >>>      just
>> >>>     redirect to csounds.com .
>> >>>
>> >>>     On Tue, Feb 21, 2012 at 2:57 PM, Rory Walsh > >>>     > wrote:
>> >>>     > I agree with Steven. In what way would we merge them however?
>> >>>     >
>> >>>     > On 21 February 2012 14:43, Steven Yi > >>>     > wrote:
>> >>>     >> Hi All,
>> >>>     >>
>> >>>     >> I'm looking at the content on csound.sf.net
>> >>>      and csounds.com  and
>> >>>     >> there's a great deal of overlap.  I'm thinking, instead of
>> >>>     creating a
>> >>>     >> separate site, we update csounds.com  with
>> >>>     any information missing from
>> >>>     >> csound.sf.net .  The problem with this
>> >>>     is that none of us who would
>> >>>     >> probably be editing the content related to development have any
>> >>>     >> editorial permissions on csounds.com .
>> >>>     >>
>> >>>     >> I think with the current scheme, having only one resource at
>> >>>     Berklee
>> >>>     >> updating the site is too much for one person.  No offense and
>> >>> of
>> >>>     >> course much appreciation to John Clements for his hard work,
>> >>> but I
>> >>>     >> think merging the sites and getting more people involved is
>> >>>     going to
>> >>>     >> pool our resources together and ultimately be more effective
>> >>> (one
>> >>>     >> place for information).
>> >>>     >>
>> >>>     >> I also think we should add a new tracker to the sourceforge
>> >>> site to
>> >>>     >> track updates for csounds.com .  People
>> >>>     could then file requests and
>> >>>     >> bugs (i.e. bad URL links, etc.) for the site itself.  That
>> >>> would
>> >>>     >> certainly help manage all the great recommendations people have
>> >>>     that
>> >>>     >> are suggested but get lost over time.
>> >>>     >>
>> >>>     >> Thoughts?
>> >>>     >>
>> >>>     >> steven
>> >>>     >>
>> >>>     >>
>> >>>     >> Send bugs reports to the Sourceforge bug tracker
>> >>>     >>
>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>>     
>> >>>     >> Discussions of bugs and features can be posted here
>> >>>     >> To unsubscribe, send email sympa@lists.bath.ac.uk
>> >>>      with body "unsubscribe csound"
>> >>>     >>
>> >>>     >
>> >>>     >
>> >>>     > Send bugs reports to the Sourceforge bug tracker
>> >>>     >
>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>>     
>> >>>     > Discussions of bugs and features can be posted here
>> >>>     > To unsubscribe, send email sympa@lists.bath.ac.uk
>> >>>      with body "unsubscribe csound"
>> >>>     >
>> >>>
>> >>>
>> >>>     Send bugs reports to the Sourceforge bug tracker
>> >>>
>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>>     
>> >>>     Discussions of bugs and features can be posted here
>> >>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>> >>>      with body "unsubscribe csound"
>> >>>
>> >>
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>

This would be great, as well as getting rid of the forums on
csounds.com.  We need *one* place for questions and answers, and
having multiple one only divides up the community.  Having a mailing
list interface that feels like a forum would be nice.

On Sat, Feb 25, 2012 at 2:45 PM, Rory Walsh  wrote:
> Is there any way we could start using an updated interface for the
> mailing list? I would love the see the mailing-list integrated fully
> into the website. It's the single greatest resource for all things
> Csound yet it's kind of hidden away a little from new users. Most
> software projects have fully searchable forums accessible through the
> projects website:
>
> http://www.renoise.com/board/
> http://forum.cockos.com/forumdisplay.php?f=20
> http://www.rawmaterialsoftware.com/index.php
>
> etc...
>
> Rory.
>
>
>
>
>
> On 25 February 2012 07:16, Dr. Richard Boulanger  wrote:
>> Thanks Iain for all your advice.
>>
>> We would love your help as we migrate, merge, evolve.
>>
>> I have asked John Clements to contact you and give you top-level clearance
>> so that you can look around and advise and help us to upgrade.
>>
>> If you want to coordinate with John and Steven that would be great.
>>
>> Before we get to far into things, we need to upate to the newest Drupal that
>> is offered by Westhost.  I think we are currently running
>> a Drupal which is a few versions behind.
>>
>> Happy to hear about your suggestions for The Csound Instrument Collection
>> (online).  It would be nice to have a resource like this
>> to which users could download, upload, search, listen, rate, comment...
>> about instruments, pieces, etc....  I have the content... ready
>> to go. (26 years of collected instruments and pieces.)
>>
>> My plan is to move some of my "personal" things from Csounds.com to my new
>> Boulanger Labs website and offer Csounds.com,
>> Csound.org, and thanks to Jacob Joaquin, Csound.net to the community - to
>> have them all point to the same place - and to take advantage of some of the
>> expertise in the community (such as yours) and the generous donation of time
>> and energy of you and others
>> to make this resource even more current, vital, and comprehensive - to
>> better serve the growing community of Csounders.
>>
>> Dr. B.
>> ___________________________________
>>
>> Dr. Richard Boulanger, Ph.D.
>>
>> Professor of Electronic Production and Design
>> Professional Writing and Music Technology Division
>> Berklee College of Music
>> 1140 Boylston Street
>> Boston, MA 02215-3693
>>
>> 617-747-2485 (office)
>> 774-488-9166 (cell)
>>
>> rboulanger@berklee.edu
>> http://csounds.com/boulanger
>> ____________________________________
>>
>> http://csounds.com
>> http://csoundforlive.com
>> ____________________________________
>>
>> http://csounds.com/mathews
>> ____________________________________
>>
>> On Feb 25, 2012, at 1:59 AM, Iain Duncan wrote:
>>
>> On Wed, Feb 22, 2012 at 7:02 AM, Steven Yi  wrote:
>>>
>>> Hi Dr. B,
>>>
>>> I think I either need more privileges or need to learn Drupal more to
>>> figure out how to modify the site.  I was trying to update the
>>> documentation page but did not see any means to edit it (it has old
>>> links to the 5.14 manual, for example).  I'll email you and John
>>> Clements off list to work all that out.
>>
>>
>> That sounds like your account doesn't have edit privileges for the content
>> type of the page you're looking at. If you did, there should be a very
>> obvious 'edit' tab there when you're logged in.
>>
>>>
>>>
>>> Otherwise, I'll start looking into content migration and updating things.
>>>
>>>
>>> For csound.net, I'd like to propose we rebrand csounds.com as
>>> csound.net.  It should be easy to have both domain names direct to the
>>> same location, with links on csounds.com to redirect to the
>>> corresponding URL location on csound.net.  Having the redirect would
>>> maintain old links to things on csounds.com to point to the right
>>> place.  This also gives us an opportunity to freshen up things and
>>> update all around, and give us a goal for a newer, fuller, richer
>>> site.
>>>
>>> For Iain, I'll email you offlist for some advice regarding drupal as
>>> you have experience with it.  It'd be great to hear what you think,
>>> especially in regards to updating the site.
>>
>>
>> Hmm, one caveat I should mention is that Drupal has uh, not done a very good
>> job with regards to the update processes that are 'supposed to work'. So I
>> would *highly highly* advise making sure that the web team is happy with the
>> version of Drupal you're using before anyone spends tons of time migrating
>> content over, or you may have some hair-pulling if content has been entered
>> in and Drupal is to be upgraded. It's supposed to be fine, but depending on
>> the modules enabled, it can either be fine or a gong show. :-/
>>
>> If there are issues, please feel free to email me off list. Use iainctduncan
>> @ that giant email provider that runs the world instead of iainduncanlists
>> in order to make sure I notice it quickly, I don't always open all threads
>> on here! =) I'm pretty well versed in drupal content migration headaches and
>> sometimes it's just easier to do stuff with python and mysql directly.
>>
>> Dr B, or those in the know, what version of Drupal is being used right now
>> and are there any plans to upgrade?
>>
>> One thing I would definitely recommend against is spending much time making
>> any kind of database app in Drupal to act as an online instrument catalog.
>> That is much better done in Pyramid/Django/Ruby-on-Rails, the Drupal db
>> framework is really primitive. If you want it to appear on the drupal site,
>> I have code for making drupal proxy modules so that content from third party
>> sites works exactly like it's part of the drupal site. We've done that for a
>> bunch of clients now, making the hard stuff in Python/Pyramid with it served
>> as a third party app and leaving general purpose content management in
>> Drupal with some kind of proxy setup.  This works really well for any kind
>> of ReST published db service, say if one wanted to be able to make different
>> public facing tools have access to instrument catalogs.
>>
>> If anyone wants to give me access, I can poke around in it over the weekend
>> and let you know my thoughts. I would love help the situation improve for
>> the new user experience!
>>
>> iain
>>
>>>
>>> As for the design, I think we'll need something a bit fresher.  Let's
>>> worry about content and site structure for now, and perhaps we can get
>>> the community to offer up some designs.  Personally, I think we need
>>> to start engaging with using more videos and audio mp3 playlists that
>>> will demonstrate works done with Csound as well as ways of using
>>> Csound beyond the command-line.  The use of Csound as a sound engine
>>> library really is something that needs to be highlighted and while
>>> those in the community know and understand how that works, we should
>>> setup a dedicated page online that will present that to a new user.
>>>
>>> Thanks!
>>> steven
>>>
>>> On Wed, Feb 22, 2012 at 11:28 AM, joachim heintz 
>>> wrote:
>>> > richard -
>>> >
>>> > this sounds excellent. i think we are on a very good way to improve the
>>> > site more and more. i have some thoughts / questions i'd like to discuss
>>> > (with you and everyone being engaged in this topic):
>>> >
>>> > 1) my personal preference for "the one and only" site/address would be
>>> > csound.net. i find the .net domain most appropriate, and for people
>>> > looking the first time for csound in the net, the first contact starts
>>> > with an oddity: why this extra "s"?
>>> >
>>> > in this context i remember that
>>> >
>>> > 2) the web tool currently being used at csounds.com might not be the
>>> > most user-friendly one. it is easy to post news, but maybe it's not the
>>> > best tool to allow a number of maintainers to include new features in a
>>> > flexible way. you, steven and john will know; i remember some people
>>> > were reporting this.
>>> >
>>> > so i am wondering whether
>>> >
>>> > 3) it might be good to set a new tool at csound.net, and move the
>>> > content of csounds.com to csound.net (or even csound.org if it is not
>>> > possible to set this up at csound.net)?
>>> >
>>> >        joachim
>>> >
>>> >
>>> >
>>> > Am 22.02.2012 06:16, schrieb Dr. Richard Boulanger:
>>> >> Dear Steven,
>>> >>
>>> >> This is a great plan.
>>> >>
>>> >> I do love the idea of Csounds.com  being the
>>> >> central
>>> >> repository and having other sites redirect to here.
>>> >>
>>> >> I also agree that it would be a huge project and that we would love to
>>> >> have some help.
>>> >> Help to do this and to realize more of the ideas that come as we merge
>>> >> and expand.
>>> >>
>>> >> I think that Steven already has the highest level of access at
>>> >> Csounds.com .
>>> >> Do you need me to do more to open up the site more to you?
>>> >> Happy to have others join Steven, John and I to help expand Csounds.com
>>> >> .
>>> >> Steven.  Let me know what you need and I appreciate your advice and
>>> >> your
>>> >> help coordinating
>>> >> this new initiative and the transition.  It will be wonderful.
>>> >>
>>> >> Dr.B.
>>> >> *___________________________________*
>>> >> *
>>> >> *
>>> >> *Dr. Richard Boulanger, Ph.D.*
>>> >> *
>>> >> *
>>> >> Professor of Electronic Production and Design
>>> >> Professional Writing and Music Technology Division
>>> >> Berklee College of Music
>>> >> 1140 Boylston Street
>>> >> Boston, MA 02215-3693
>>> >>
>>> >> 617-747-2485 (office)
>>> >> 774-488-9166 (cell)
>>> >>
>>> >> rboulanger@berklee.edu 
>>> >> http://csounds.com/boulanger
>>> >> ____________________________________
>>> >>
>>> >> http://csounds.com 
>>> >> http://csoundforlive.com 
>>> >> ____________________________________
>>> >>
>>> >> http://csounds.com/mathews
>>> >> ____________________________________
>>> >>
>>> >> On Feb 21, 2012, at 11:36 AM, J Clements wrote:
>>> >>
>>> >>> Steven, I like and agree with all your ideas, and I will await Dr.
>>> >>> Boulanger's directive on how we can all help achieve this unity of
>>> >>> message and information using Csounds.com  as more
>>> >>> of an active community hub for our work and ideas.
>>> >>>
>>> >>> As I am currently in the final semesters of my work here at Berklee, I
>>> >>> would welcome any help with keeping the site up to date.
>>> >>>
>>> >>> John
>>> >>>
>>> >>> On Feb 21, 2012 10:09 AM, "Steven Yi" >> >>> > wrote:
>>> >>>
>>> >>>     Well, we'd have to ensure the information that was done on the
>>> >>>     csound.sf.net  site is incorporated into
>>> >>>     the csounds.com  site (such as
>>> >>>     mentioning linuxaudio.org  and
>>> >>>     sourceforge, making the links to
>>> >>>     downloads be individual like they are on csound.sf.net
>>> >>>      per platform,
>>> >>>     etc.).  From my glances, Csounds.com  could
>>> >>>     certainly have some more
>>> >>>     information filled in.  Also, we'd eventually make csound.sf.net
>>> >>>      just
>>> >>>     redirect to csounds.com .
>>> >>>
>>> >>>     On Tue, Feb 21, 2012 at 2:57 PM, Rory Walsh >> >>>     > wrote:
>>> >>>     > I agree with Steven. In what way would we merge them however?
>>> >>>     >
>>> >>>     > On 21 February 2012 14:43, Steven Yi >> >>>     > wrote:
>>> >>>     >> Hi All,
>>> >>>     >>
>>> >>>     >> I'm looking at the content on csound.sf.net
>>> >>>      and csounds.com  and
>>> >>>     >> there's a great deal of overlap.  I'm thinking, instead of
>>> >>>     creating a
>>> >>>     >> separate site, we update csounds.com  with
>>> >>>     any information missing from
>>> >>>     >> csound.sf.net .  The problem with this
>>> >>>     is that none of us who would
>>> >>>     >> probably be editing the content related to development have any
>>> >>>     >> editorial permissions on csounds.com .
>>> >>>     >>
>>> >>>     >> I think with the current scheme, having only one resource at
>>> >>>     Berklee
>>> >>>     >> updating the site is too much for one person.  No offense and
>>> >>> of
>>> >>>     >> course much appreciation to John Clements for his hard work,
>>> >>> but I
>>> >>>     >> think merging the sites and getting more people involved is
>>> >>>     going to
>>> >>>     >> pool our resources together and ultimately be more effective
>>> >>> (one
>>> >>>     >> place for information).
>>> >>>     >>
>>> >>>     >> I also think we should add a new tracker to the sourceforge
>>> >>> site to
>>> >>>     >> track updates for csounds.com .  People
>>> >>>     could then file requests and
>>> >>>     >> bugs (i.e. bad URL links, etc.) for the site itself.  That
>>> >>> would
>>> >>>     >> certainly help manage all the great recommendations people have
>>> >>>     that
>>> >>>     >> are suggested but get lost over time.
>>> >>>     >>
>>> >>>     >> Thoughts?
>>> >>>     >>
>>> >>>     >> steven
>>> >>>     >>
>>> >>>     >>
>>> >>>     >> Send bugs reports to the Sourceforge bug tracker
>>> >>>     >>
>>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>>     
>>> >>>     >> Discussions of bugs and features can be posted here
>>> >>>     >> To unsubscribe, send email sympa@lists.bath.ac.uk
>>> >>>      with body "unsubscribe csound"
>>> >>>     >>
>>> >>>     >
>>> >>>     >
>>> >>>     > Send bugs reports to the Sourceforge bug tracker
>>> >>>     >
>>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>>     
>>> >>>     > Discussions of bugs and features can be posted here
>>> >>>     > To unsubscribe, send email sympa@lists.bath.ac.uk
>>> >>>      with body "unsubscribe csound"
>>> >>>     >
>>> >>>
>>> >>>
>>> >>>     Send bugs reports to the Sourceforge bug tracker
>>> >>>
>>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>>     
>>> >>>     Discussions of bugs and features can be posted here
>>> >>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>> >>>      with body "unsubscribe csound"
>>> >>>
>>> >>
>>> >
>>> >
>>> > Send bugs reports to the Sourceforge bug tracker
>>> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> > Discussions of bugs and features can be posted here
>>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> > csound"
>>> >
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Speaking of the forums, they have CAPTCHAs, and as I am blind I cannot
access them without asking another human to solve them for me. I think
I especially like the one provided by The ZoneBBS, which asks you a
question, and gives you checkboxes to check that would make it *very*
difficult for a computer to solve.

The problem with image CAPTCHAs, in addition to their visual nature,
is that someone could write a program that would filter out the
squiggly lines where the human sees them, making them easily defeated.
I propose that CAPTCHAs (not just on Csounds.com, but everywhere
they're implemented) test for speed and block suspiciously fast (or
even moderately fast) programs solving them from the same address or,
if they see a range of IP addresses solving them to register users or
comment, they should block the range. I also understand that people
will comment on forum posts multiple times in a day, so there should
also be a warning telling users if they comment a certain number of
times a minute, they will be blocked from the site.

On 2/25/12, Steven Yi  wrote:
> This would be great, as well as getting rid of the forums on
> csounds.com.  We need *one* place for questions and answers, and
> having multiple one only divides up the community.  Having a mailing
> list interface that feels like a forum would be nice.
>
> On Sat, Feb 25, 2012 at 2:45 PM, Rory Walsh  wrote:
>> Is there any way we could start using an updated interface for the
>> mailing list? I would love the see the mailing-list integrated fully
>> into the website. It's the single greatest resource for all things
>> Csound yet it's kind of hidden away a little from new users. Most
>> software projects have fully searchable forums accessible through the
>> projects website:
>>
>> http://www.renoise.com/board/
>> http://forum.cockos.com/forumdisplay.php?f=20
>> http://www.rawmaterialsoftware.com/index.php
>>
>> etc...
>>
>> Rory.
>>
>>
>>
>>
>>
>> On 25 February 2012 07:16, Dr. Richard Boulanger 
>> wrote:
>>> Thanks Iain for all your advice.
>>>
>>> We would love your help as we migrate, merge, evolve.
>>>
>>> I have asked John Clements to contact you and give you top-level
>>> clearance
>>> so that you can look around and advise and help us to upgrade.
>>>
>>> If you want to coordinate with John and Steven that would be great.
>>>
>>> Before we get to far into things, we need to upate to the newest Drupal
>>> that
>>> is offered by Westhost.  I think we are currently running
>>> a Drupal which is a few versions behind.
>>>
>>> Happy to hear about your suggestions for The Csound Instrument Collection
>>> (online).  It would be nice to have a resource like this
>>> to which users could download, upload, search, listen, rate, comment...
>>> about instruments, pieces, etc....  I have the content... ready
>>> to go. (26 years of collected instruments and pieces.)
>>>
>>> My plan is to move some of my "personal" things from Csounds.com to my
>>> new
>>> Boulanger Labs website and offer Csounds.com,
>>> Csound.org, and thanks to Jacob Joaquin, Csound.net to the community - to
>>> have them all point to the same place - and to take advantage of some of
>>> the
>>> expertise in the community (such as yours) and the generous donation of
>>> time
>>> and energy of you and others
>>> to make this resource even more current, vital, and comprehensive - to
>>> better serve the growing community of Csounders.
>>>
>>> Dr. B.
>>> ___________________________________
>>>
>>> Dr. Richard Boulanger, Ph.D.
>>>
>>> Professor of Electronic Production and Design
>>> Professional Writing and Music Technology Division
>>> Berklee College of Music
>>> 1140 Boylston Street
>>> Boston, MA 02215-3693
>>>
>>> 617-747-2485 (office)
>>> 774-488-9166 (cell)
>>>
>>> rboulanger@berklee.edu
>>> http://csounds.com/boulanger
>>> ____________________________________
>>>
>>> http://csounds.com
>>> http://csoundforlive.com
>>> ____________________________________
>>>
>>> http://csounds.com/mathews
>>> ____________________________________
>>>
>>> On Feb 25, 2012, at 1:59 AM, Iain Duncan wrote:
>>>
>>> On Wed, Feb 22, 2012 at 7:02 AM, Steven Yi  wrote:
>>>>
>>>> Hi Dr. B,
>>>>
>>>> I think I either need more privileges or need to learn Drupal more to
>>>> figure out how to modify the site.  I was trying to update the
>>>> documentation page but did not see any means to edit it (it has old
>>>> links to the 5.14 manual, for example).  I'll email you and John
>>>> Clements off list to work all that out.
>>>
>>>
>>> That sounds like your account doesn't have edit privileges for the
>>> content
>>> type of the page you're looking at. If you did, there should be a very
>>> obvious 'edit' tab there when you're logged in.
>>>
>>>>
>>>>
>>>> Otherwise, I'll start looking into content migration and updating
>>>> things.
>>>>
>>>>
>>>> For csound.net, I'd like to propose we rebrand csounds.com as
>>>> csound.net.  It should be easy to have both domain names direct to the
>>>> same location, with links on csounds.com to redirect to the
>>>> corresponding URL location on csound.net.  Having the redirect would
>>>> maintain old links to things on csounds.com to point to the right
>>>> place.  This also gives us an opportunity to freshen up things and
>>>> update all around, and give us a goal for a newer, fuller, richer
>>>> site.
>>>>
>>>> For Iain, I'll email you offlist for some advice regarding drupal as
>>>> you have experience with it.  It'd be great to hear what you think,
>>>> especially in regards to updating the site.
>>>
>>>
>>> Hmm, one caveat I should mention is that Drupal has uh, not done a very
>>> good
>>> job with regards to the update processes that are 'supposed to work'. So
>>> I
>>> would *highly highly* advise making sure that the web team is happy with
>>> the
>>> version of Drupal you're using before anyone spends tons of time
>>> migrating
>>> content over, or you may have some hair-pulling if content has been
>>> entered
>>> in and Drupal is to be upgraded. It's supposed to be fine, but depending
>>> on
>>> the modules enabled, it can either be fine or a gong show. :-/
>>>
>>> If there are issues, please feel free to email me off list. Use
>>> iainctduncan
>>> @ that giant email provider that runs the world instead of
>>> iainduncanlists
>>> in order to make sure I notice it quickly, I don't always open all
>>> threads
>>> on here! =) I'm pretty well versed in drupal content migration headaches
>>> and
>>> sometimes it's just easier to do stuff with python and mysql directly.
>>>
>>> Dr B, or those in the know, what version of Drupal is being used right
>>> now
>>> and are there any plans to upgrade?
>>>
>>> One thing I would definitely recommend against is spending much time
>>> making
>>> any kind of database app in Drupal to act as an online instrument
>>> catalog.
>>> That is much better done in Pyramid/Django/Ruby-on-Rails, the Drupal db
>>> framework is really primitive. If you want it to appear on the drupal
>>> site,
>>> I have code for making drupal proxy modules so that content from third
>>> party
>>> sites works exactly like it's part of the drupal site. We've done that
>>> for a
>>> bunch of clients now, making the hard stuff in Python/Pyramid with it
>>> served
>>> as a third party app and leaving general purpose content management in
>>> Drupal with some kind of proxy setup.  This works really well for any
>>> kind
>>> of ReST published db service, say if one wanted to be able to make
>>> different
>>> public facing tools have access to instrument catalogs.
>>>
>>> If anyone wants to give me access, I can poke around in it over the
>>> weekend
>>> and let you know my thoughts. I would love help the situation improve for
>>> the new user experience!
>>>
>>> iain
>>>
>>>>
>>>> As for the design, I think we'll need something a bit fresher.  Let's
>>>> worry about content and site structure for now, and perhaps we can get
>>>> the community to offer up some designs.  Personally, I think we need
>>>> to start engaging with using more videos and audio mp3 playlists that
>>>> will demonstrate works done with Csound as well as ways of using
>>>> Csound beyond the command-line.  The use of Csound as a sound engine
>>>> library really is something that needs to be highlighted and while
>>>> those in the community know and understand how that works, we should
>>>> setup a dedicated page online that will present that to a new user.
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> On Wed, Feb 22, 2012 at 11:28 AM, joachim heintz 
>>>> wrote:
>>>> > richard -
>>>> >
>>>> > this sounds excellent. i think we are on a very good way to improve
>>>> > the
>>>> > site more and more. i have some thoughts / questions i'd like to
>>>> > discuss
>>>> > (with you and everyone being engaged in this topic):
>>>> >
>>>> > 1) my personal preference for "the one and only" site/address would be
>>>> > csound.net. i find the .net domain most appropriate, and for people
>>>> > looking the first time for csound in the net, the first contact starts
>>>> > with an oddity: why this extra "s"?
>>>> >
>>>> > in this context i remember that
>>>> >
>>>> > 2) the web tool currently being used at csounds.com might not be the
>>>> > most user-friendly one. it is easy to post news, but maybe it's not
>>>> > the
>>>> > best tool to allow a number of maintainers to include new features in
>>>> > a
>>>> > flexible way. you, steven and john will know; i remember some people
>>>> > were reporting this.
>>>> >
>>>> > so i am wondering whether
>>>> >
>>>> > 3) it might be good to set a new tool at csound.net, and move the
>>>> > content of csounds.com to csound.net (or even csound.org if it is not
>>>> > possible to set this up at csound.net)?
>>>> >
>>>> >        joachim
>>>> >
>>>> >
>>>> >
>>>> > Am 22.02.2012 06:16, schrieb Dr. Richard Boulanger:
>>>> >> Dear Steven,
>>>> >>
>>>> >> This is a great plan.
>>>> >>
>>>> >> I do love the idea of Csounds.com  being the
>>>> >> central
>>>> >> repository and having other sites redirect to here.
>>>> >>
>>>> >> I also agree that it would be a huge project and that we would love
>>>> >> to
>>>> >> have some help.
>>>> >> Help to do this and to realize more of the ideas that come as we
>>>> >> merge
>>>> >> and expand.
>>>> >>
>>>> >> I think that Steven already has the highest level of access at
>>>> >> Csounds.com .
>>>> >> Do you need me to do more to open up the site more to you?
>>>> >> Happy to have others join Steven, John and I to help expand
>>>> >> Csounds.com
>>>> >> .
>>>> >> Steven.  Let me know what you need and I appreciate your advice and
>>>> >> your
>>>> >> help coordinating
>>>> >> this new initiative and the transition.  It will be wonderful.
>>>> >>
>>>> >> Dr.B.
>>>> >> *___________________________________*
>>>> >> *
>>>> >> *
>>>> >> *Dr. Richard Boulanger, Ph.D.*
>>>> >> *
>>>> >> *
>>>> >> Professor of Electronic Production and Design
>>>> >> Professional Writing and Music Technology Division
>>>> >> Berklee College of Music
>>>> >> 1140 Boylston Street
>>>> >> Boston, MA 02215-3693
>>>> >>
>>>> >> 617-747-2485 (office)
>>>> >> 774-488-9166 (cell)
>>>> >>
>>>> >> rboulanger@berklee.edu 
>>>> >> http://csounds.com/boulanger
>>>> >> ____________________________________
>>>> >>
>>>> >> http://csounds.com 
>>>> >> http://csoundforlive.com 
>>>> >> ____________________________________
>>>> >>
>>>> >> http://csounds.com/mathews
>>>> >> ____________________________________
>>>> >>
>>>> >> On Feb 21, 2012, at 11:36 AM, J Clements wrote:
>>>> >>
>>>> >>> Steven, I like and agree with all your ideas, and I will await Dr.
>>>> >>> Boulanger's directive on how we can all help achieve this unity of
>>>> >>> message and information using Csounds.com  as
>>>> >>> more
>>>> >>> of an active community hub for our work and ideas.
>>>> >>>
>>>> >>> As I am currently in the final semesters of my work here at Berklee,
>>>> >>> I
>>>> >>> would welcome any help with keeping the site up to date.
>>>> >>>
>>>> >>> John
>>>> >>>
>>>> >>> On Feb 21, 2012 10:09 AM, "Steven Yi" >>> >>> > wrote:
>>>> >>>
>>>> >>>     Well, we'd have to ensure the information that was done on the
>>>> >>>     csound.sf.net  site is incorporated into
>>>> >>>     the csounds.com  site (such as
>>>> >>>     mentioning linuxaudio.org  and
>>>> >>>     sourceforge, making the links to
>>>> >>>     downloads be individual like they are on csound.sf.net
>>>> >>>      per platform,
>>>> >>>     etc.).  From my glances, Csounds.com  could
>>>> >>>     certainly have some more
>>>> >>>     information filled in.  Also, we'd eventually make csound.sf.net
>>>> >>>      just
>>>> >>>     redirect to csounds.com .
>>>> >>>
>>>> >>>     On Tue, Feb 21, 2012 at 2:57 PM, Rory Walsh >>> >>>     > wrote:
>>>> >>>     > I agree with Steven. In what way would we merge them however?
>>>> >>>     >
>>>> >>>     > On 21 February 2012 14:43, Steven Yi >>> >>>     > wrote:
>>>> >>>     >> Hi All,
>>>> >>>     >>
>>>> >>>     >> I'm looking at the content on csound.sf.net
>>>> >>>      and csounds.com 
>>>> >>> and
>>>> >>>     >> there's a great deal of overlap.  I'm thinking, instead of
>>>> >>>     creating a
>>>> >>>     >> separate site, we update csounds.com 
>>>> >>> with
>>>> >>>     any information missing from
>>>> >>>     >> csound.sf.net .  The problem with this
>>>> >>>     is that none of us who would
>>>> >>>     >> probably be editing the content related to development have
>>>> >>> any
>>>> >>>     >> editorial permissions on csounds.com .
>>>> >>>     >>
>>>> >>>     >> I think with the current scheme, having only one resource at
>>>> >>>     Berklee
>>>> >>>     >> updating the site is too much for one person.  No offense and
>>>> >>> of
>>>> >>>     >> course much appreciation to John Clements for his hard work,
>>>> >>> but I
>>>> >>>     >> think merging the sites and getting more people involved is
>>>> >>>     going to
>>>> >>>     >> pool our resources together and ultimately be more effective
>>>> >>> (one
>>>> >>>     >> place for information).
>>>> >>>     >>
>>>> >>>     >> I also think we should add a new tracker to the sourceforge
>>>> >>> site to
>>>> >>>     >> track updates for csounds.com .  People
>>>> >>>     could then file requests and
>>>> >>>     >> bugs (i.e. bad URL links, etc.) for the site itself.  That
>>>> >>> would
>>>> >>>     >> certainly help manage all the great recommendations people
>>>> >>> have
>>>> >>>     that
>>>> >>>     >> are suggested but get lost over time.
>>>> >>>     >>
>>>> >>>     >> Thoughts?
>>>> >>>     >>
>>>> >>>     >> steven
>>>> >>>     >>
>>>> >>>     >>
>>>> >>>     >> Send bugs reports to the Sourceforge bug tracker
>>>> >>>     >>
>>>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> >>>     
>>>> >>>     >> Discussions of bugs and features can be posted here
>>>> >>>     >> To unsubscribe, send email sympa@lists.bath.ac.uk
>>>> >>>      with body "unsubscribe csound"
>>>> >>>     >>
>>>> >>>     >
>>>> >>>     >
>>>> >>>     > Send bugs reports to the Sourceforge bug tracker
>>>> >>>     >
>>>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> >>>     
>>>> >>>     > Discussions of bugs and features can be posted here
>>>> >>>     > To unsubscribe, send email sympa@lists.bath.ac.uk
>>>> >>>      with body "unsubscribe csound"
>>>> >>>     >
>>>> >>>
>>>> >>>
>>>> >>>     Send bugs reports to the Sourceforge bug tracker
>>>> >>>
>>>> >>>      https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> >>>     
>>>> >>>     Discussions of bugs and features can be posted here
>>>> >>>     To unsubscribe, send email sympa@lists.bath.ac.uk
>>>> >>>      with body "unsubscribe csound"
>>>> >>>
>>>> >>
>>>> >
>>>> >
>>>> > Send bugs reports to the Sourceforge bug tracker
>>>> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> > Discussions of bugs and features can be posted here
>>>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>> > "unsubscribe
>>>> > csound"
>>>> >
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>