mNo edit summary
mNo edit summary
Line 8: Line 8:


# In week 1, students choose a format for communication in both asynchronous  and synchronous situations in private. You enable your advisors to see what is going on....(e.g. Emails are cc'd, blogs passwords are provided).
# In week 1, students choose a format for communication in both asynchronous  and synchronous situations in private. You enable your advisors to see what is going on....(e.g. Emails are cc'd, blogs passwords are provided).
# In week 1, create a Gantt chart of tasks and the individuals that will be responsible for them  
# In week 1, create a Gantt chart of tasks and the individuals that will be responsible for them  
# Use a logged weekly full team meetings(voice)(private).
# Use a logged weekly full team meetings(voice)(private).
# Use a design journal/idea blog/chat room/wall, which is logged?(private).
# Use a design journal/idea blog/chat room/wall, which is logged?(private).
# Share design iterations shared on Appropedia [project] and Thingiverse [designs] (public) – history file will track contributions.
# Share design iterations shared on Appropedia [project] and Thingiverse [designs] (public) – history file will track contributions.
# Building and testing the devices, with publishing full instructions/protocols.
# Building and testing the devices, with publishing full instructions/protocols.
# Develop method of sharing data access between universities and the public. See for example [[Pachube]] or consider ftp protocol – whatever is going to work.
# Develop method of sharing data access between universities and the public. See for example [[Pachube]] or consider ftp protocol – whatever is going to work.


[[category:Queens Applied Sustainability Group]]
[[category:Queens Applied Sustainability Group]]

Revision as of 02:30, 14 July 2011

This page discusses how to run an international collaboration on scientific and engineering research in applied sustainability.

It includes links to software and services and provides an example project: Open source solar spectrum project

Teams are responsible for:

  1. In week 1, students choose a format for communication in both asynchronous and synchronous situations in private. You enable your advisors to see what is going on....(e.g. Emails are cc'd, blogs passwords are provided).
  2. In week 1, create a Gantt chart of tasks and the individuals that will be responsible for them
  3. Use a logged weekly full team meetings(voice)(private).
  4. Use a design journal/idea blog/chat room/wall, which is logged?(private).
  5. Share design iterations shared on Appropedia [project] and Thingiverse [designs] (public) – history file will track contributions.
  6. Building and testing the devices, with publishing full instructions/protocols.
  7. Develop method of sharing data access between universities and the public. See for example Pachube or consider ftp protocol – whatever is going to work.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.