[sakai-pmc] Facebook: Sakai Project Group

[Neal Caidin]

We could have both, wrt Facebook, but right now we have effectively 
neither. Since discussions and decisions happen on lists, adding another 
discussion channel might add confusion. So I guess I am leaning towards 
the newswire idea. Probably a short communications plan and checklist 
would be appropriate as well, since we already have the www.apereo.org 
newswire. I think Facebook has the potential to get a lot more attention 
than the apereo.org website. Especially because, my understanding, is 
that the information on the Apereo site is not subscribable , which adds 
another obstacle. We have the Announcements newsletter (collab), which 
is pretty good and widely read.

Essence of what I'm thinking:

* Yes, newswire over group discussion
* Multiple channels for newswire: Apereo newsletter, Apereo site, 
Facebook page (not group) ... maybe Twitter
* small group because it is official, and to concentrate responsibility

Just my opinion at the moment. I like the crowdsourcing concept in a lot 
of ways. Not sure it is best for dissemination of news.

For the discussion aspect, I wish we had something better than our 
Collab server, but I don't have any ideas. Collab server is great in a 
lot of ways, including traction, but it has deficiencies as well. For 
example, if I'm in Teaching and Learning and I want to loop in the dev 
group, I have to join the dev group for my post to go through. That 
seems silly to me. And one has to get comfortable with list archives and 
search tools like nabble or gmane to find and follow threads. Coursera 
style discussion groups are much easier.

2 cents, plus some other random coins.

-- Neal


> Noah Botimer <mailto:botimer at umich.edu>
> February 13, 2014 at 10:38 AM
> I guess I was keying in on Neal's suggestion that there be a Page. To 
> me, a Page should be newswire-style and a Group should be more of a 
> community (per Chuck's example).
>
> But I admit my Facebook-fu is rough. Really, any configuration works 
> for me because I'm not the ultimate producer or consumer in this scenario.
>
> Thanks,
> -Noah
>
>
>
> Anthony Whyte <mailto:arwhyte at umich.edu>
> February 13, 2014 at 10:32 AM
> Are you suggesting that a Facebook group should serve as a verified 
> newswire?
>
> anthony whyte | its and mlibrary | university of michigan | 
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
>
>
> Noah Botimer <mailto:botimer at umich.edu>
> February 13, 2014 at 10:19 AM
> I figure that we risk the dissolution of responsibility if there are 
> too many people enlisted, cf. Confluence.
>
> I am not suggesting any special eligibility or specific limits, but I 
> think the "verified newswire" channel has been lacking. If a few 
> people have this responsibility, I think we are likely to have better 
> results. Time and again we hear from the community that there is no 
> clear project mouthpiece, despite our many information outlets -- this 
> signals a need for unification of voice to me, not a lack of democracy.
>
> Thanks,
> -Noah
>
>
>
> Anthony Whyte <mailto:arwhyte at umich.edu>
> February 13, 2014 at 9:34 AM
>
>
> Crowd source the administration by granting admin rights to every 
> known contributor who joins the group.
>
>
> -1.   Create for yourself dozens, if not hundreds of backup admins, by 
> leveraging the community.
>
> Anth
>
> anthony whyte | its and mlibrary | university of michigan | 
> arwhyte at umich.edu <mailto:arwhyte at umich.edu> | 517-980-0228
>
>
>
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> February 13, 2014 at 9:17 AM
> I just did some research and what we really need is a Facebook page 
> which represents an official group and that makes it easy for anyone 
> to follow and receive announcements directly on their timeline. What 
> we have is a Facebook group, which currently has 8 people. Facebook 
> groups are intended for a group with a common interest to communicate 
> among themselves.
>
> I think anyone on the PMC should be an administrator on the Facebook 
> page in addition to myself. I should have at least one backup (maybe 
> this would be a good PMC Vice Chair role?) to post significant events 
> and milestones for the Sakai community.
>
> There will need to be a marketing push to get folks to "Like" the 
> Sakai Project page, which I'm thinking we can do through the Apereo 
> Newsletter, at the Open Apereo conference and maybe a couple of more ways.
>
> I'm going to notify the Foundation before I create the page since it 
> will represent official communications for the Sakai Project, and they 
> should be informed.
>
> Cheers,
> Neal
>
>
>

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140213/0067db55/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1253 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140213/0067db55/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 992 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140213/0067db55/attachment-0001.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140213/0067db55/attachment-0002.jpg