[sakai-pmc] Facebook: Sakai Project Group

[Neal Caidin]

Good points. Thanks.

-- Neal


> Anthony Whyte <mailto:arwhyte at umich.edu>
> February 13, 2014 at 12:23 PM
>
>
> If a page, the news-wire approach needs to be something more than 
> infrequent release-related announcements or cross-posted Apereo news. 
>  The flow of info should resemble what Instructure makes available on 
> its page: pointers to interesting pedagogical discussions, ed tech 
> musings, alerts regarding upcoming webinars, adopter stories, etc. [1] 
>  If the content is something less than this then, in my view, it's not 
> worth maintaining a Facebook presence.  If it is worth doing then it's 
> going to take something more than a casual effort to keep the content 
> fresh, relevant and flowing.  And it might just make more sense to 
> direct what energies can be harnessed to enlivening the Apereo page 
> than attempt to maintain a sakaiproject page [2].
>
>
> Given competing responsibilities, it's unclear to me how local Sakai 
> stories will be surfaced and disseminated without crowd sourcing the 
> roles of journalist and reporter to community contributors.
>
>
> Me neither.  I'm no fan of Facebook and do not plan to contribute time 
> to maintaining either a group or a page.  That said, those who think a 
> Facebook presence important should not be deterred by my dislike of 
> the platform.
>
> Cheers,
>
> Anth
>
> [1] https://www.facebook.com/instructure  (4,394 likes)
> [2] https://www.facebook.com/apereo (89 likes)
>
>
>
> 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 11:19 AM
> 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
>
>
>

-- 
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/9503114d/attachment.html 
-------------- 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/9503114d/attachment.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/9503114d/attachment-0001.jpg 
-------------- 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/9503114d/attachment-0002.jpg