http://localhost:8080/trac/ticket/220 <p> please do a time quote for: </p> <p> (a) addition of a *private* forum facility to transitionnewtork.org - only invited members can see/add posts </p> <p> (b) addition of a forum to workspaces.transitionnetwork.org features - essentially including a forum in the workspace features </p> <p> There is a growing interest in enabling all the national hubs to have a place to share/discuss etc. </p> en-us /trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg http://localhost:8080/trac/ticket/220 Trac 0.12.5 jim Fri, 14 Jan 2011 15:49:01 GMT http://localhost:8080/trac/ticket/220#comment:1 http://localhost:8080/trac/ticket/220#comment:1 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> Much faff will be needed to to a) on TN.org. </p> <p> BUT!!! a+b can happen on workspaces very simply... </p> <p> See: <a class="ext-link" href="http://drupal.org/project/og_forum"><span class="icon">​</span>http://drupal.org/project/og_forum</a> </p> <p> Therefore, (b) would be a case of adding the module, allowing groups to use these. While (a) would be a case of adding a new private group in Workspaces with members controlled as needed, then simply using the forum that is auto-set up. </p> <p> This is the simple case, needs a release to LIVE and means .5-1.5 hours to set it up. </p> <p> If you want (a) on TN.org, well that's probably 20 minutes of research just to find an answer, then all the danger/problems we had before we moved workspaces out - namely content type permissions + user roles + OG + bespoke stuff = pain. </p> Ticket ed Mon, 17 Jan 2011 10:41:32 GMT http://localhost:8080/trac/ticket/220#comment:2 http://localhost:8080/trac/ticket/220#comment:2 <p> ta - duly informed Ben and encouraging him to chose route a </p> Ticket