SoundSoftware Code Site

h1. 20101109actions

h2. Evaluation of the workshop

* programming background very different

* many different research areas (was this good or bad?)

* some "attitude" problems??

* networking was good… but it would be more important if everybody's research topic "presentations" should have been done in the first day

* all the energy and "side" stories compensated for a lack of technical expertise

h2. one day workshops? is it possible?

h2. Version Control

* the most important ideia coming out of the course

* main topic for 1 day workshop

* Are the user interfaces is more important than the tools itself?

* should we develop our own tool? (based on hgexplorer)

** study needs and workflows

** tailor for new students, presentations, workshops

h2. Building the "network"/SoundSoftware Community

* organize a workshop every year

** focused on the software used, not in the research itself

** share code, practices

* could also be done internally (C4DM)

** need of bug tracking software

** wiki to have discussions 

* Advantages of this community

** "Safer space", more confortable to researchers in the area, easier to ask questions than in specialized forums

* Online seminar:

** weekly? probably too much…

** Adobe Connect?? 

* the target community for this project is wider that this workshop's attendees

* FaceBook group has been active

** is it "open"/public? - it _should_ be public

* SoundSoftware could be an aggregator for audio/music software content (fetch info from blogs, etc)

** watch certain blogs feeds for tags

h2. Repositories 

* should we host? Probably not:

** maybe the people that attended the workshop should talk to their universities systems team

** talk to the supervisors/ people that attended in order that they act on this

h2. Future of the project

* need for sorting out software, needs, etc—in the community

* after that, choose tools, etc