This is an excellent idea. I'd most likely move Vancouver.pm to this -
hopefully it would foster participation from the Vancouver Perl
community.

-chris

On 7/11/07, Bill Odom <billodom@gmail.com> wrote:
> Hi all.
>
> Here's part of the proposal I put together a few weeks back, when I
> (re)proposed Andy's original wikis-for-PMs idea to the Socialtext
> Powers-That-Be. I wanted to share it with everyone, so you could get
> an idea of what I was asking ST to provide, and to get feedback or
> questions before we move forward and make a broader announcement.
> Please let me know what you think.
>
> Thanks!
>
> Bill
>
> P.S. - Sorry for the wikitext; it's copied from a posting on an
> internal ST workspace.
>
> -----
>
> ^ Proposal
>
> Provide free wiki hosting for PerlMongers groups.
>
> ^ Specifics
>
> Provide a workspace for every PerlMongers group, upon request.
>
> Only create workspaces upon request, since:
>
> * Some PMs already have their own wikis, and won't need or want a new one.
> * Some PMs won't want to use a hosted wiki (for whatever reason).
> * We don't want want to create a large number of workspaces that may
> never get used.
> * We don't want to offend community members by creating something in
> their name without permission.
> * We need to know the admin of the workspace.
>
> Group leaders are allowed to request a PM workspace.
>
> * List of groups, with contact info, available at
> http://www.pm.org/groups/index.html
> * May need to work with/through José Castro (TPF Community Relations)
> and Jay Hannah (PM Admin)
>
> What information do we need from requesters to create a workspace?
>
> * Group name
> * Admin email address(es)
>
> Consider providing a general PerlMongers workspace in addition to the
> PM-specific workspaces.
>
> > Although PM-specific workspaces provide a sense of control and ownership that one large workspace doesn't, there's still value in having a general workspace that any PM member can use. Shared content could go there, and be linked/transcluded as necessary within PM-group workspaces. Any individual PM member could also be a member of this general workspace.
>
> Establish a pattern before starting; we don't want to make this up as
> we go. Specifically, we should know the:
>
> * Naming convention
> * Content template
> * Default features
> * Limitations, if any
>
> ^^ Trust
>
> Allay fears up front. Convey to PM leaders and members that:
>
> * You can always leave, and take your data with you.
> * Your content belongs to you.
> * Source is always freely available.
> * We won't spam you or try to sell you anything.
>
> Specifically, we need to provide an easy way for people to export
> their data, so there's never any doubt that this isn't about holding
> people hostage.
>
> ^^ Hosting
>
> The existing ST community server has more than enough capacity to
> handle this, so there's no need for new infrastructure.
>
> ^^ Access and Visibility
>
> Content should be publicly visible, but editable only by workspace members.
>
> ^^ Workspace names and URLs
>
> This is probably the best form:
>
> * http://wiki.pm.org/stlouis-pm/
>
> Another possibility:
>
> * http://wiki.pm.org/stlouis-perlmongers/
>
> Both of these require only a single DNS entry (for wiki.pm.org) and
> provide a natural grouping for all the sites. The suffixes (-pm /
> -perlmongers) decrease the likelihood of name collisions with other
> workspaces already hosted on the box.
>
> Of the two, I slightly prefer the first one. It's shorter, and matches
> the way many PM members refer to their groups.
>
> ^^ Content Template
>
> Consider providing a template appropriate for user-group-style content:
>
> * Member list (may just be workspace members, to encourage people to
> join the wiki)
> * Meeting location and map (a good way to demo Google maps plugin)
> * Meeting schedule (calendar plugin)
> * Archived meeting notes
> * Member presentations (attachments)
> * Member blogs
> * Member photos
> * Code samples (as both attachments and .pre blocks)
> * Content of interest to Perl developers (REST API docs, alternative
> editing tools, etc.)
>
> ^^ Support
>
> Support for these workspaces will be the same as for other community
> workspaces. PM members and workspace admins will have access to
> http://www.socialtext.net/open/ and /exchange, the mailing lists, and
> to #socialtext on IRC. Also, many ST employees are well-known within
> the Perl community; we're pretty easy to find if someone needs help.
>
> -----
> --
> Request pm.org Technical Support via support@pm.org
>
> pm_groups mailing list
> pm_groups@pm.org
> http://mail.pm.org/mailman/listinfo/pm_groups
>
-- 
Request pm.org Technical Support via support@pm.org

pm_groups mailing list
pm_groups@pm.org
http://mail.pm.org/mailman/listinfo/pm_groups