[sakai-pmc] Meta-thoughts about Proposals

[Noah Botimer]

There are so many push and pull communications channels now. I hesitate to
CC a bunch of lists. We have a web presence, there are blogs/RSS, things
like Twitter, and emails. List emails have the worst authority,
persistence, and general browseability.

If I were "managing the brand", I would recommend a regular blog post with
interesting updates (coordinated with the newsletter so it's not confusing
about what wins). I would one-time notify a bunch of the lists that our
community coordinator is sharing/summarizing the things he thinks the
community should know there. And I would use the @sakaiproject Twitter
account to announce the updates when they are posted. This combination
gives a known place with a clear channel and archive of information,
supported by good search and multiple user-controlled
notification/aggregation methods.

If there is someone who wants the list traffic, sakai-dev is the place. If
someone just wants to be able to check in on "what's happening", just one
more email in the bin is a low percentage shot. Get it on the web and to
places where people aggregate/share.

Thanks,
-Noah

On Nov 8, 2013, at 6:39 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

Thanks for the feedback Megan and Sam.

So I guess what I did was okay, it sounds like. I do get occasional
feedback from community members that they do not want to subscribe to the
sakai-dev list because it is a lot of information not relevant to them, but
they do want to stay connected to the community. I've never formally polled
the community on this, fyi, just anecdotal.

Cheers,
Neal



On Wed, Nov 6, 2013 at 8:59 PM, May, Megan Marie <mmmay at iu.edu> wrote:

>  I think that once a proposal matures into a decision that it should be
> widely shared.     If the next release is going to be Sakai 10, that is
> something the entire community should know!      It’s more about ensuring
> there is an *informed* community rather than creating transparency.
>
>
>
> The entire community shouldn’t need to monitor the dev list; rather the CC
> should be surfacing key topics.
>
>
>
> Megan
>
>
>
> *From:* sakai-pmc-bounces at collab.sakaiproject.org [mailto:
> sakai-pmc-bounces at collab.sakaiproject.org] *On Behalf Of *Sam Ottenhoff
> *Sent:* Wednesday, November 06, 2013 2:02 PM
> *To:* Neal Caidin
> *Cc:* sakai-pmc at collab.sakaiproject.org
> *Subject:* Re: [sakai-pmc] Meta-thoughts about Proposals
>
>
>
> Sakai-dev is wide open, has been our most active list for a decade, and is
> where dev changes have traditionally been discussed.  If you want to
> encourage people that are not members of sakai-dev to get involved, by all
> means, do it.  But I don't see how requiring cross-posting will achieve
> improved transparency.  I would instead suggest that you post to these
> various lists that being a member of sakai-dev is encouraged if people want
> to stay up to date on Sakai development and changes. If someone is only
> subscribed to the pedagogy list but really wanted to know about upcoming
> dev, then they are lost and need your help.
>
>
>
> --Sam
>
>
>
> On Wed, Nov 6, 2013 at 1:47 PM, Neal Caidin <neal.caidin at apereo.org>
> wrote:
>
> Hi PMC,
>
> There have been two important proposals in the last week. I think the
> selection of which lists to which to post in both cases is reasonable, to
> hit the intended audiences most likely to want a say and provide valuable
> input to the process.
>
> However, I believe we should be even more transparent and essentially
> notify just about everybody (except probably for the Announcements list).
> For these two proposals: Sakai 10 and Sakai online help, I just sent links
> to the archive discussions to several more lists to inform them.
>
> Does anyone agree with me on the transparency concept? I wonder what the
> best way to achieve this would be?
>
> Best,
> Neal
>
>
>
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
>
>
>
>
>
>
>
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
>

_______________________________________________
sakai-pmc mailing list
sakai-pmc at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131108/a7befd62/attachment.html