Difference between revisions of "Developer Meetings/OrganizerInstruction"
From Slicer Wiki
m (Text replacement - "slicerWiki/index.php" to "wiki") |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
| − | == | + | == Hangouts are held every week at 10am on Tuesday mornings == |
| − | The day | + | == Day before the hangout, edit Developer meetings page == |
| + | |||
| + | The day before the hangout, [{{fullurl:Developer_Meetings|action=edit§ion=1}} edit] the Developer Meeting page available on the wiki: | ||
* Uncomment the entry associated with the following week or create the corresponding page. | * Uncomment the entry associated with the following week or create the corresponding page. | ||
| − | == Around | + | == Around 9:55am, join the hangout == |
| + | |||
| + | We use the following hangout <i>room</i>: https://hangouts.google.com/hangouts/_/kitware.com/slicer | ||
| + | |||
| + | As people try to join, make sure to accept their requests. | ||
| + | |||
| + | <!-- | ||
| + | == Around 4pm, create an event in the "Slicer BarCamp" community and send a first email on the slicer-developer list == | ||
| Line 15: | Line 24: | ||
<gallery widths=550px heights=400px perrow=2> | <gallery widths=550px heights=400px perrow=2> | ||
File:SlicerBarCamp-CreateEvent-1.png|Create an event | File:SlicerBarCamp-CreateEvent-1.png|Create an event | ||
| − | File:SlicerBarCamp-CreateEvent-2.png|Set event properties<br>(1)Select theme<br>(2)Set hangout name to <code>Developer Hangout</code><br>(3)Set start time ( | + | File:SlicerBarCamp-CreateEvent-2.png|Set event properties<br>(1)Select theme<br>(2)Set hangout name to <code>Developer Hangout</code><br>(3)Set start time (10am)<br>(4)Set end time (11am)<br>(5)Choose "Google hangout" in advanced property<br>(6)Copy link to the wiki page<br>(7)Click on "Invite" |
</gallery> | </gallery> | ||
| − | + | --> | |
<!-- | <!-- | ||
| Line 25: | Line 34: | ||
Hi Slicers, | Hi Slicers, | ||
| − | We'll be having our Slicer4 developer hangout | + | We'll be having our Slicer4 developer hangout tomorrow at 10am EST. Since the Google hangout platform have been upgraded, you will RECEIVE THE LINK allowing to join the hangout FIVE MINUTES BEFORE IT STARTS. |
If you have specific point you want to discuss, consider updating the wiki: | If you have specific point you want to discuss, consider updating the wiki: | ||
| − | http://www.slicer.org/ | + | http://www.slicer.org/wiki/Developer_Meetings/HANGOUTDATE |
</pre> | </pre> | ||
| − | == Around | + | == Around 9:50am, start a hangout == |
See Google help: [https://support.google.com/plus/bin/answer.py?hl=en&answer=1215275 Start a hangout] for details | See Google help: [https://support.google.com/plus/bin/answer.py?hl=en&answer=1215275 Start a hangout] for details | ||
| Line 39: | Line 48: | ||
| − | == Around | + | == Around 9:55am, reply to your first email with hangout link == |
Email template: | Email template: | ||
| Line 53: | Line 62: | ||
--> | --> | ||
| − | == After or during the meeting, | + | == After or during the meeting, update 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/ | + | See [http://www.slicer.org/wiki/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. |
Latest revision as of 17:05, 21 November 2019
Home < Developer Meetings < OrganizerInstructionContents
Hangouts are held every week at 10am on Tuesday mornings
Day before the hangout, edit Developer meetings page
The day before 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 9:55am, join the hangout
We use the following hangout room: https://hangouts.google.com/hangouts/_/kitware.com/slicer
As people try to join, make sure to accept their requests.
After or during the meeting, update 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.
