Recent Changes for "July 2007 Wiki Meeting" - Rochester Wikihttps://rocwiki.org/July_2007_Wiki_MeetingRecent Changes of the page "July 2007 Wiki Meeting" on Rochester Wiki.en-us https://rocwiki.org/July_2007_Wiki_Meetinghttps://rocwiki.org/July_2007_Wiki_Meeting?action=diff&version1=2&version2=3&ts=1188175345July 2007 Wiki Meeting2007-08-27T00:42:25ZrottenchesterRenamed to "Wiki Community/July 2007 Wiki Meeting" <div id="content" class="wikipage content"> Differences for July 2007 Wiki Meeting<p><strong></strong></p><table> <tr> <td> <span> Deletions are marked with - . </span> </td> <td> <span> Additions are marked with +. </span> </td> </tr> <tr> <td> Line 1: </td> <td> Line 1: </td> </tr> <tr> <td> <span>- A small but undaunted group of ["PeterBoulay" Peter], ["JoannaLicata" Joanna] and ["Rottenchester"] attended a RocWiki<br> - meeting today. Here are some of the topics we discussed, the decisions we made, and some food for thought:<br> - <br> - 1. We're going to try regular meetings and a Facebook group.<br> - <br> - Nobody can attend every meeting, so we might as well just start having them regularly in hopes that putting a time out there will help people plan. With that in mind, we arbitrarily picked the last Sunday of every month at 4 p.m. We'll rotate the meeting location, and picked the Old Toad for the next meeting, August 26.<br> - <br> - Since Facebook has a pretty good event management function, and since a lot of people on this list are on Facebook, Joanna has created a Facebook group which can be seen here:<br> - <br> - [http://www.facebook.com/group.php?gid=3378039402 RocWiki Group on Facebook]<br> - <br> - We'll try to use this group and the Facebook event function to manage our meetings. We'll still use this list for discussions as usual.<br> - If you're on Facebook, join up.<br> - <br> - 2. We're looking for people to fill the (informal) roles of those who have left.<br> - <br> - The good: Rocwiki continues to have a steady stream of edits and traffic averaging about 2,000 page views per day. The bad: We lost some key contributors and organizers this year.<br> - <br> - The people who left (["RobertPolyn" Rob], ["FarMcKon" Far], ["AdamDewitz" Adam] and others) filled a number of informal roles. One of those roles was meeting organizer. Another was publicist, which included printing up and distributing RocWiki stickers, sending out press releases, etc. A third role was technical staff, working on code and system administration for RocWiki. All of these are thankless but important tasks.<br> - <br> - We're going to try to use Facebook and regularly scheduled meetings to help fill in the meeting organization gap. Hopefully, the advance notice of a meeting will help us get a few more contributors out to meetings.<br> - <br> - We could really use a publicist - someone willing to write a few emails or make a few calls to local student newspapers, and maybe to distribute stickers or posters when school starts.<br> - <br> - As for technical staff, ["Rottenchester"] is doing that now, but it would be great to get someone else involved.<br> - <br> - 3. We've started preliminary discussions with RIT about helping out with RocWiki.<br> - <br> - We had a meeting on Friday with some cohorts of ex-Rochesterian Adam Dewitz. These meetings are in the early stages, but the goal is to get RocWiki on the map at RIT, and to have RIT students do projects that will help contribute to design and coding new features for RocWiki.<br> - <br> - So, mark your calendars for Sunday, August 26, 4 PM, The Old Toad. If you can't make it, we'll have another meeting in September.</span> </td> <td> <span>+ #redirect Wiki Community/July 2007 Wiki Meeting</span> </td> </tr> </table> </div> https://rocwiki.org/July_2007_Wiki_Meetinghttps://rocwiki.org/July_2007_Wiki_Meeting?action=diff&version1=1&version2=2&ts=1188175323July 2007 Wiki Meeting2007-08-27T00:42:03Zrottenchesterfixed formatting <div id="content" class="wikipage content"> Differences for July 2007 Wiki Meeting<p><strong></strong></p><table> <tr> <td> <span> Deletions are marked with - . </span> </td> <td> <span> Additions are marked with +. </span> </td> </tr> <tr> <td> Line 6: </td> <td> Line 6: </td> </tr> <tr> <td> <span>-</span> Nobody can attend every meeting, so we might as well just start having<span><br> -</span> them regularly in hopes that putting a time out there will help people<span><br> -</span> plan. With that in mind, we arbitrarily picked the last Sunday of<span><br> -</span> every month at 4 p.m. We'll rotate the meeting location, and picked<span><br> -</span> the Old Toad for the next meeting, August 26. </td> <td> <span>+</span> Nobody can attend every meeting, so we might as well just start having them regularly in hopes that putting a time out there will help people plan. With that in mind, we arbitrarily picked the last Sunday of every month at 4 p.m. We'll rotate the meeting location, and picked the Old Toad for the next meeting, August 26. </td> </tr> <tr> <td> Line 12: </td> <td> Line 8: </td> </tr> <tr> <td> <span>-</span> Since Facebook has a pretty good event management function, and since<span><br> -</span> a lot of people on this list are on Facebook, Joanna has created a<span><br> -</span> Facebook group which can be seen here: </td> <td> <span>+</span> Since Facebook has a pretty good event management function, and since a lot of people on this list are on Facebook, Joanna has created a Facebook group which can be seen here: </td> </tr> <tr> <td> Line 18: </td> <td> Line 12: </td> </tr> <tr> <td> <span>-</span> We'll try to use this group and the Facebook event function to manage<span><br> -</span> our meetings. We'll still use this list for discussions as usual. </td> <td> <span>+</span> We'll try to use this group and the Facebook event function to manage our meetings. We'll still use this list for discussions as usual. </td> </tr> <tr> <td> Line 22: </td> <td> Line 15: </td> </tr> <tr> <td> <span>-</span> 2. We're looking for people to fill the (informal) roles of those who<span><br> -</span> have left. </td> <td> <span>+</span> 2. We're looking for people to fill the (informal) roles of those who have left. </td> </tr> <tr> <td> Line 25: </td> <td> Line 17: </td> </tr> <tr> <td> <span>-</span> The good: Rocwiki continues to have a steady stream of edits and<span><br> -</span> traffic averaging about 2,000 page views per day. The bad: We lost<span><br> -</span> some key contributors and organizers this year. </td> <td> <span>+</span> The good: Rocwiki continues to have a steady stream of edits and traffic averaging about 2,000 page views per day. The bad: We lost some key contributors and organizers this year. </td> </tr> <tr> <td> Line 29: </td> <td> Line 19: </td> </tr> <tr> <td> <span>-</span> The people who left (["RobertPolyn" Rob], ["FarMcKon" Far], ["AdamDewitz" Adam] and others) filled a number of<span><br> -</span> informal roles. One of those roles was meeting organizer. Another<span><br> -</span> was publicist, which included printing up and distributing RocWiki<span><br> -</span> stickers, sending out press releases, etc. A third role was<span><br> -</span> technical staff, working on code and system administration for<span><br> -</span> RocWiki. All of these are thankless but important tasks. </td> <td> <span>+</span> The people who left (["RobertPolyn" Rob], ["FarMcKon" Far], ["AdamDewitz" Adam] and others) filled a number of informal roles. One of those roles was meeting organizer. Another was publicist, which included printing up and distributing RocWiki stickers, sending out press releases, etc. A third role was technical staff, working on code and system administration for RocWiki. All of these are thankless but important tasks. </td> </tr> <tr> <td> Line 36: </td> <td> Line 21: </td> </tr> <tr> <td> <span>-</span> We're going to try to use Facebook and regularly scheduled meetings to<span><br> -</span> help fill in the meeting organization gap. Hopefully, the advance<span><br> -</span> notice of a meeting will help us get a few more contributors out to<span><br> -</span> meetings. </td> <td> <span>+</span> We're going to try to use Facebook and regularly scheduled meetings to help fill in the meeting organization gap. Hopefully, the advance notice of a meeting will help us get a few more contributors out to meetings. </td> </tr> <tr> <td> Line 41: </td> <td> Line 23: </td> </tr> <tr> <td> <span>-</span> We could really use a publicist - someone willing to write a few<span><br> -</span> emails or make a few calls to local student newspapers, and maybe to<span><br> -</span> distribute stickers or posters when school starts. </td> <td> <span>+</span> We could really use a publicist - someone willing to write a few emails or make a few calls to local student newspapers, and maybe to distribute stickers or posters when school starts. </td> </tr> <tr> <td> Line 45: </td> <td> Line 25: </td> </tr> <tr> <td> <span>-</span> As for technical staff, ["Rottenchester"] is doing that now, but it would be great to<span><br> -</span> get someone else involved. </td> <td> <span>+</span> As for technical staff, ["Rottenchester"] is doing that now, but it would be great to get someone else involved. </td> </tr> <tr> <td> Line 48: </td> <td> Line 27: </td> </tr> <tr> <td> <span>-</span> 3. We've started preliminary discussions with RIT about helping out<span><br> -</span> with RocWiki. </td> <td> <span>+</span> 3. We've started preliminary discussions with RIT about helping out with RocWiki. </td> </tr> <tr> <td> Line 51: </td> <td> Line 29: </td> </tr> <tr> <td> <span>-</span> We had a meeting on Friday with some cohorts of ex-Rochesterian Adam<span><br> -</span> Dewitz. These meetings are in the early stages, but the goal is to<span><br> -</span> get RocWiki on the map at RIT, and to have RIT students do projects<span><br> -</span> that will help contribute to design and coding new features for<span><br> -</span> RocWiki. </td> <td> <span>+</span> We had a meeting on Friday with some cohorts of ex-Rochesterian Adam Dewitz. These meetings are in the early stages, but the goal is to get RocWiki on the map at RIT, and to have RIT students do projects that will help contribute to design and coding new features for RocWiki. </td> </tr> <tr> <td> Line 57: </td> <td> Line 31: </td> </tr> <tr> <td> <span>-</span> So, mark your calendars for Sunday, August 26, 4 PM, The Old Toad. If<span><br> -</span> you can't make it, we'll have another meeting in September. </td> <td> <span>+</span> So, mark your calendars for Sunday, August 26, 4 PM, The Old Toad. If you can't make it, we'll have another meeting in September. </td> </tr> </table> </div> https://rocwiki.org/July_2007_Wiki_Meetinghttps://rocwiki.org/July_2007_Wiki_Meeting?action=diff&version1=0&version2=1&ts=1188174087July 2007 Wiki Meeting2007-08-27T00:21:27ZrottenchesterBetter Late than Never <div id="content" class="wikipage content"> Differences for July 2007 Wiki Meeting<p><strong></strong></p><table> <tr> <td> <span> Deletions are marked with - . </span> </td> <td> <span> Additions are marked with +. </span> </td> </tr> <tr> <td> Line 1: </td> <td> Line 1: </td> </tr> <tr> <td> </td> <td> <span>+ A small but undaunted group of ["PeterBoulay" Peter], ["JoannaLicata" Joanna] and ["Rottenchester"] attended a RocWiki<br> + meeting today. Here are some of the topics we discussed, the decisions we made, and some food for thought:<br> + <br> + 1. We're going to try regular meetings and a Facebook group.<br> + <br> + Nobody can attend every meeting, so we might as well just start having<br> + them regularly in hopes that putting a time out there will help people<br> + plan. With that in mind, we arbitrarily picked the last Sunday of<br> + every month at 4 p.m. We'll rotate the meeting location, and picked<br> + the Old Toad for the next meeting, August 26.<br> + <br> + Since Facebook has a pretty good event management function, and since<br> + a lot of people on this list are on Facebook, Joanna has created a<br> + Facebook group which can be seen here:<br> + <br> + [http://www.facebook.com/group.php?gid=3378039402 RocWiki Group on Facebook]<br> + <br> + We'll try to use this group and the Facebook event function to manage<br> + our meetings. We'll still use this list for discussions as usual.<br> + If you're on Facebook, join up.<br> + <br> + 2. We're looking for people to fill the (informal) roles of those who<br> + have left.<br> + <br> + The good: Rocwiki continues to have a steady stream of edits and<br> + traffic averaging about 2,000 page views per day. The bad: We lost<br> + some key contributors and organizers this year.<br> + <br> + The people who left (["RobertPolyn" Rob], ["FarMcKon" Far], ["AdamDewitz" Adam] and others) filled a number of<br> + informal roles. One of those roles was meeting organizer. Another<br> + was publicist, which included printing up and distributing RocWiki<br> + stickers, sending out press releases, etc. A third role was<br> + technical staff, working on code and system administration for<br> + RocWiki. All of these are thankless but important tasks.<br> + <br> + We're going to try to use Facebook and regularly scheduled meetings to<br> + help fill in the meeting organization gap. Hopefully, the advance<br> + notice of a meeting will help us get a few more contributors out to<br> + meetings.<br> + <br> + We could really use a publicist - someone willing to write a few<br> + emails or make a few calls to local student newspapers, and maybe to<br> + distribute stickers or posters when school starts.<br> + <br> + As for technical staff, ["Rottenchester"] is doing that now, but it would be great to<br> + get someone else involved.<br> + <br> + 3. We've started preliminary discussions with RIT about helping out<br> + with RocWiki.<br> + <br> + We had a meeting on Friday with some cohorts of ex-Rochesterian Adam<br> + Dewitz. These meetings are in the early stages, but the goal is to<br> + get RocWiki on the map at RIT, and to have RIT students do projects<br> + that will help contribute to design and coding new features for<br> + RocWiki.<br> + <br> + So, mark your calendars for Sunday, August 26, 4 PM, The Old Toad. If<br> + you can't make it, we'll have another meeting in September.</span> </td> </tr> </table> </div>