Difference between revisions of "Developer Meetings/OrganizerInstruction"

From Slicer Wiki
Jump to: navigation, search
m
Line 17: Line 17:
  
  
 +
<!--
 
Then send an email to the list using the following Email template:
 
Then send an email to the list using the following Email template:
  
Line 48: Line 49:
 
</pre>
 
</pre>
  
== After or duringthe meeting, udpate conclusion ==
+
-->
 +
 
 +
== After or during the meeting, udpate conclusion ==
  
 
After the meeting, update the conclusion and send an email to the slicer developer list.
 
After the meeting, update the conclusion and send an email to the slicer developer list.
  
 
See [http://www.slicer.org/slicerWiki/index.php/Developer_Meetings/20120522#Conclusion here] for an example of conclusion and [http://slicer-devel.65872.n3.nabble.com/Slicer-4-hangouts-TODAY-4pm-EDT-tp3971413p4007808.html here] for an example of email.
 
See [http://www.slicer.org/slicerWiki/index.php/Developer_Meetings/20120522#Conclusion here] for an example of conclusion and [http://slicer-devel.65872.n3.nabble.com/Slicer-4-hangouts-TODAY-4pm-EDT-tp3971413p4007808.html here] for an example of email.

Revision as of 21:51, 6 June 2013

Home < Developer Meetings < OrganizerInstruction

Day of the hangout, edit Developer meetings page

The day of the hangout, edit the Developer Meeting page available on the wiki:

  • Uncomment the entry associated with the following week or create the corresponding page.


Around 10am, create an event in the "Slicer BarCamp" community and send a first email on the slicer-developer list

After opening the Slicer BarCamp page, follow the step described below.


After or during the meeting, udpate conclusion

After the meeting, update the conclusion and send an email to the slicer developer list.

See here for an example of conclusion and here for an example of email.