Flock media / communications plan proposal

[Máirín Duffy]

Hi,

While Flock is going on, with a little bit of work up front to set a
solid / standard direction, I think we could come out of it having some
nicely collated & organized posts about the event, photos, as well as
better chat experience.

We actually have some data, thanks to Suzanne Hillman, about how
Fedorans use social media around Fedora events. She surveyed 141 Fedora
contributors across all geos (52.5% EMEA, 28.4% NA, 12.1% APAC, and 7.1%
LATAM) and asked about their social media / photo sharing preferences.
(24% of respondents were ambassadors.) I'll summarize the findings at
the bottom of this email and I'll refer to it as I made suggestions here.

So as suggested earlier [1], we'regoing to give funded attendees blog,
video nanny, or photo assignments to cover different Flock sessions.
This is as it's been for all Fedora eventswith the trip report
requirement, with a minor tweak that we're assigning specifictalks for
coverage rather than leaving it open-ended.

Media Proposal:
==============

In order to fulfill the requirement of their assignment, funded
attendees should follow these instructions below.

For bloggers / note-takers:
-----------------------------------

For those who have been assigned to take notes / transcribe / blog a
particular session or sessions, we ask them to maketheir posts in the
Fedora community blog, following these instructions:

https://communityblog.fedoraproject.org/writing-community-blog-article/

TheFedora Design Team can provide a selection of banners for the
articles that can be used, based on whether the article is a
transcription / notes of a session or a fully-fleshed out blog post.
They can also pull photos from the instagram and Flickr tags below.

We will need editors for the community blog to vet the posts and push
them through each evening. It might be nice to have Fedora magazine
summary posts each evening as well.


For photographers:
--------------------------

Those who have agreed to take on a photo assignment should agree to
release their photos under a CC-BY or CC-BY-SA license.

They should post photos either to instagram or Flickr (most popular pure
photo sharing apps). On instagram, they will put the tag #flockcod
posts. On Flickr, they will join a group (we'll set it up asopen join)
and posttheir photos to that group, also tagging them with #flockcod.

(Note that Facebook was popular for sharing photos too, but I have
direct experience with trying to get photos out via their API and unless
a very specific and finnicky workflow is followed, they are
irretrievable. So I'm recommending avoiding that.)

For video nannies:
-------------------------

Those who have agreed to video nanny one or more sessions must, at the
end of the session:

1) Rename the recording file to reflect the title of the session.
2) Upload the video of that session to the Fedora Project YouTube channel.

Logistically, I'm not 100% sure of the best workflow here - we could
have the session laptops logged in to the account?

Also, some sessions (eg hackfests) won't make sense to record. Should we
ask on the CFP side if the session makes sense to record or not?

Communication Proposal
=====================

Chat
------

By far IRC is the most widely-used chat medium, so if there is one
official one, that should be it.

#fedora-flock - main channel

Room channels:

#fedora-flock-capecod
#fedora-flock-barnstable
#fedora-flock-grand-i
#fedora-flock-grand-ii
#fedora-flock-osterville
#fedora-flock-centerville
#fedora-flock-orleans

Signal was 2nd place; if we can set up a bridge between #fedora-flock on
IRC and a telegram channel that would be good.

Mailing Lists
-----------------
We need to set up:
- flock-attendees-2017(a)lists.fpo
- flock-speakers-2017(a)lists.fpo

And we need to subscribe all registrants to flock-attendees and all
speakers to flock-speakers. We might want to send out an announcement
email every morning for attendees and let them know it's coming so
they'll check. We could also post a link to the morning announcements on
the website?


Ok below is the research I mentioned.

Cheers,
~m

Research Findings Summary
=======================

- 78% of respondents use social media to read, post, or comment about
Fedora.

SOCIAL MEDIA PLATFORMS
-------------------------------------

To read about Fedora or Fedora events, the most popular socialmedia
platformswere:

1) Twitter (99 respondents) (this was also the most frequently-used by far)
2) Facebook (50 respondents)
3) Google Plus (45 respondents)
4) Reddit (37 respondents)


CHAT APPLICATIONS
-----------------------------

To read about Fedora or Fedora events, the most popular chat apps were:

1) IRC (84 respondents)
2) Telegram (44 respondents)
3) Google Hangouts (25 respondents)
4) Whatsapp (17 respondents)

PHOTO SHARING
-----------------------

77.3% of all respondents use photo sharing platforms for photos relating
to Fedora or Fedora events.

To *view* photos about Fedora or Fedora events, the most popular
applications / platforms were:

1) Facebook (21 respondents)
2) Twitter (19respondents)
3)  Google Plus (12respondents)
4) Flickr (10 respondents)
5) Instagram (10 respondents)


To *post* or *comment on* photos about Fedora or Fedora events, the most
popular applications / platforms were:

1) Twitter (19 respondents)
2) Facebook (18 respondents)
3)Google Plus (10 respondents)
4) Instagram (9 respondents)
5) Flickr (8 respondents)




[1]
https://lists.fedoraproject.org/archives/list/[e-mail]...

[Justin W. Flory]

On 04/27/2017 03:43 AM, Máirín Duffy wrote:
>  Hi,
>  
>  While Flock is going on, with a little bit of work up front to set a
>  solid / standard direction, I think we could come out of it having some
>  nicely collated & organized posts about the event, photos, as well as
>  better chat experience.
>  
>  We actually have some data, thanks to Suzanne Hillman, about how
>  Fedorans use social media around Fedora events. She surveyed 141 Fedora
>  contributors across all geos (52.5% EMEA, 28.4% NA, 12.1% APAC, and 7.1%
>  LATAM) and asked about their social media / photo sharing preferences.
>  (24% of respondents were ambassadors.) I'll summarize the findings at
>  the bottom of this email and I'll refer to it as I made suggestions here.
>  
>  So as suggested earlier [1], we'regoing to give funded attendees blog,
>  video nanny, or photo assignments to cover different Flock sessions.
>  This is as it's been for all Fedora eventswith the trip report
>  requirement, with a minor tweak that we're assigning specifictalks for
>  coverage rather than leaving it open-ended.
>  
>  Media Proposal:
>  ==============
>  
>  In order to fulfill the requirement of their assignment, funded
>  attendees should follow these instructions below.
>  
>  For bloggers / note-takers:
>  -----------------------------------
>  
>  For those who have been assigned to take notes / transcribe / blog a
>  particular session or sessions, we ask them to maketheir posts in the
>  Fedora community blog, following these instructions:
>  
>  https://communityblog.fedoraproject.org/writing-community-blog-article/
>  
>  TheFedora Design Team can provide a selection of banners for the
>  articles that can be used, based on whether the article is a
>  transcription / notes of a session or a fully-fleshed out blog post.
>  They can also pull photos from the instagram and Flickr tags below.
>  
>  We will need editors for the community blog to vet the posts and push
>  them through each evening. It might be nice to have Fedora magazine
>  summary posts each evening as well.
>   
This would be awesome. I'm planning on putting some guidelines together
for the Community Blog for editors, so it should be easy to streamline
blog posts covering individual sessions / talks onto the CommBlog. It
would definitely be awesome if the Design Team could collaborate on
creating a base set of featured images to use. As a reference, the
Community Blog featured images are here:

    https://pagure.io/communityblog-images

As far as the Fedora Magazine goes, it might be helpful for some of the
editors to find time to get together once a day and do an hour power
session to do a daily overview or something along these lines. We had
wanted to do that with the keynotes last year, but it didn't end up
panning out.

So from my perspective, big +1 to the above!

>  
>  For photographers:
>  --------------------------
>  
>  Those who have agreed to take on a photo assignment should agree to
>  release their photos under a CC-BY or CC-BY-SA license.
>  
>  They should post photos either to instagram or Flickr (most popular pure
>  photo sharing apps). On instagram, they will put the tag #flockcod
>  posts. On Flickr, they will join a group (we'll set it up asopen join)
>  and posttheir photos to that group, also tagging them with #flockcod.
>  
>  (Note that Facebook was popular for sharing photos too, but I have
>  direct experience with trying to get photos out via their API and unless
>  a very specific and finnicky workflow is followed, they are
>  irretrievable. So I'm recommending avoiding that.)
>   
As an extra incentive, we can also tie these guidelines into what
determines if this badge is awarded or not:

    https://badges.fedoraproject.org/badge/flock-paparazzi

>  For video nannies:
>  -------------------------
>  
>  Those who have agreed to video nanny one or more sessions must, at the
>  end of the session:
>  
>  1) Rename the recording file to reflect the title of the session.
>  2) Upload the video of that session to the Fedora Project YouTube channel.
>  
>  Logistically, I'm not 100% sure of the best workflow here - we could
>  have the session laptops logged in to the account?
>   
To have YouTube access, you have to have access to the Google+ account.
However, it is possible that we could add individuals who are video
nannying ahead of time as YouTube managers for the duration of Flock.
This would let them use their personal Google accounts to upload the videos.

Also, I'd like to try to put together some guidelines or a SOP for the
video uploads (like a common set of base tags, adding the right metadata
(e.g. location / date), etc. This is something I'll try to work on
closer to Flock, but I think it would be valuable to make sure we get
everything right in the first go.

>  Also, some sessions (eg hackfests) won't make sense to record.
> Should we
>  ask on the CFP side if the session makes sense to record or not?
>  
>  Communication Proposal
>  =====================
>  
>  Chat
>  ------
>  
>  By far IRC is the most widely-used chat medium, so if there is one
>  official one, that should be it.
>  
>  #fedora-flock - main channel
>  
>  Room channels:
>  
>  #fedora-flock-capecod
>  #fedora-flock-barnstable
>  #fedora-flock-grand-i
>  #fedora-flock-grand-ii
>  #fedora-flock-osterville
>  #fedora-flock-centerville
>  #fedora-flock-orleans
>  
>  Signal was 2nd place; if we can set up a bridge between #fedora-flock on
>  IRC and a telegram channel that would be good.
>   
For context, it is really easy to bridge a Telegram group to an IRC
channel. This is what the @fedora supergrouup is using for
#fedora-telegram and @fedoradiversity group is for #fedora-diversity.
We're using this as the bridge software right now:

    https://github.com/RITlug/teleirc

It's a simple NodeJS bot that isn't too difficult to set up. I'd be more
than willing to help with this once IRC channels are established, if needed.

>  Mailing Lists
>  -----------------
>  We need to set up:
>  - flock-attendees-2017(a)lists.fpo
>  - flock-speakers-2017(a)lists.fpo
>  
>  And we need to subscribe all registrants to flock-attendees and all
>  speakers to flock-speakers. We might want to send out an announcement
>  email every morning for attendees and let them know it's coming so
>  they'll check. We could also post a link to the morning announcements on
>  the website?
>  
>  
>  Ok below is the research I mentioned.
>  
>  Cheers,
>  ~m
>   
-- 
Cheers,
Justin W. Flory
jflory7(a)gmail.com

[Brian Exelbierd]

On Thu, Apr 27, 2017, at 08:45 AM, Justin W. Flory wrote:
>  On 04/27/2017 03:43 AM, Máirín Duffy wrote:
>  > Hi,
>  > 
>  > While Flock is going on, with a little bit of work up front to set a
>  > solid / standard direction, I think we could come out of it having some
>  > nicely collated & organized posts about the event, photos, as well as
>  > better chat experience.
>  > 
>  > We actually have some data, thanks to Suzanne Hillman, about how
>  > Fedorans use social media around Fedora events. She surveyed 141 Fedora
>  > contributors across all geos (52.5% EMEA, 28.4% NA, 12.1% APAC, and 7.1%
>  > LATAM) and asked about their social media / photo sharing preferences.
>  > (24% of respondents were ambassadors.) I'll summarize the findings at
>  > the bottom of this email and I'll refer to it as I made suggestions here.
>  > 
>  > So as suggested earlier [1], we'regoing to give funded attendees blog,
>  > video nanny, or photo assignments to cover different Flock sessions.
>  > This is as it's been for all Fedora eventswith the trip report
>  > requirement, with a minor tweak that we're assigning specifictalks for
>  > coverage rather than leaving it open-ended.
>  > 
>  > Media Proposal:
>  > ==============
>  > 
>  > In order to fulfill the requirement of their assignment, funded
>  > attendees should follow these instructions below.
>  > 
>  > For bloggers / note-takers:
>  > -----------------------------------
>  > 
>  > For those who have been assigned to take notes / transcribe / blog a
>  > particular session or sessions, we ask them to maketheir posts in the
>  > Fedora community blog, following these instructions:
>  > 
>  > https://communityblog.fedoraproject.org/writing-community-blog-article/
>  > 
>  > TheFedora Design Team can provide a selection of banners for the
>  > articles that can be used, based on whether the article is a
>  > transcription / notes of a session or a fully-fleshed out blog post.
>  > They can also pull photos from the instagram and Flickr tags below.
>  > 
>  > We will need editors for the community blog to vet the posts and push
>  > them through each evening. It might be nice to have Fedora magazine
>  > summary posts each evening as well.
>  > 
>  
>  This would be awesome. I'm planning on putting some guidelines together
>  for the Community Blog for editors, so it should be easy to streamline
>  blog posts covering individual sessions / talks onto the CommBlog. It
>  would definitely be awesome if the Design Team could collaborate on
>  creating a base set of featured images to use. As a reference, the
>  Community Blog featured images are here:
>  
>      https://pagure.io/communityblog-images
>  
>  As far as the Fedora Magazine goes, it might be helpful for some of the
>  editors to find time to get together once a day and do an hour power
>  session to do a daily overview or something along these lines. We had
>  wanted to do that with the keynotes last year, but it didn't end up
>  panning out.
>  
>  So from my perspective, big +1 to the above!
>  
>  > 
>  > For photographers:
>  > --------------------------
>  > 
>  > Those who have agreed to take on a photo assignment should agree to
>  > release their photos under a CC-BY or CC-BY-SA license.
>  > 
>  > They should post photos either to instagram or Flickr (most popular pure
>  > photo sharing apps). On instagram, they will put the tag #flockcod
>  > posts. On Flickr, they will join a group (we'll set it up asopen join)
>  > and posttheir photos to that group, also tagging them with #flockcod.
>  > 
>  > (Note that Facebook was popular for sharing photos too, but I have
>  > direct experience with trying to get photos out via their API and unless
>  > a very specific and finnicky workflow is followed, they are
>  > irretrievable. So I'm recommending avoiding that.)
>  > 
>  
>  As an extra incentive, we can also tie these guidelines into what
>  determines if this badge is awarded or not:
>  
>      https://badges.fedoraproject.org/badge/flock-paparazzi
>  
>  > For video nannies:
>  > -------------------------
>  > 
>  > Those who have agreed to video nanny one or more sessions must, at the
>  > end of the session:
>  > 
>  > 1) Rename the recording file to reflect the title of the session.
>  > 2) Upload the video of that session to the Fedora Project YouTube channel.
>  > 
>  > Logistically, I'm not 100% sure of the best workflow here - we could
>  > have the session laptops logged in to the account?
>
>  To have YouTube access, you have to have access to the Google+ account.
>  However, it is possible that we could add individuals who are video
>  nannying ahead of time as YouTube managers for the duration of Flock.
>  This would let them use their personal Google accounts to upload the
>  videos.
>  
>  Also, I'd like to try to put together some guidelines or a SOP for the
>  video uploads (like a common set of base tags, adding the right metadata
>  (e.g. location / date), etc. This is something I'll try to work on
>  closer to Flock, but I think it would be valuable to make sure we get
>  everything right in the first go. 
We need to make sure the videos wind up manageable by our Youtube folks
after the event.  Would it make more sense (and be easier to those who
don't know how to do the upload) to have them put the videos in a known
location for one person to do the uploads?  Otherwise I feel like we are
going to spend a lot of effort to train a lot of people to do a process
a small numer of times.

>  > Also, some sessions (eg hackfests) won't make sense to
> record. Should we
>  > ask on the CFP side if the session makes sense to record or not? 
I don't think we need to.  I think we should work with talks always
being recorded.  We can leave recording instructions next to the laptop
if someone feels their hacksession warrants recording.

I wish we could get away from laptop recordings ... the quality is
terrible.  Last year's audio was mostly unusuable.

>  > Communication Proposal
>  > =====================
>  > 
>  > Chat
>  > ------
>  > 
>  > By far IRC is the most widely-used chat medium, so if there is one
>  > official one, that should be it.
>  > 
>  > #fedora-flock - main channel
>  > 
>  > Room channels:
>  > 
>  > #fedora-flock-capecod
>  > #fedora-flock-barnstable
>  > #fedora-flock-grand-i
>  > #fedora-flock-grand-ii
>  > #fedora-flock-osterville
>  > #fedora-flock-centerville
>  > #fedora-flock-orleans 
I'd like to make it clear that we don't expect people to be hanging out
on the room channels.  My understanding is that we want to use them for
meetbox to pull in transcriptions.

>  > 
>  > Signal was 2nd place; if we can set up a bridge between #fedora-flock on
>  > IRC and a telegram channel that would be good.
>  > 
>  
>  For context, it is really easy to bridge a Telegram group to an IRC
>  channel. This is what the @fedora supergrouup is using for
>  #fedora-telegram and @fedoradiversity group is for #fedora-diversity.
>  We're using this as the bridge software right now:
>  
>      https://github.com/RITlug/teleirc
>  
>  It's a simple NodeJS bot that isn't too difficult to set up. I'd be more
>  than willing to help with this once IRC channels are established, if
>  needed.
>  
>  > Mailing Lists
>  > -----------------
>  > We need to set up:
>  > - flock-attendees-2017(a)lists.fpo
>  > - flock-speakers-2017(a)lists.fpo
>  > 
>  > And we need to subscribe all registrants to flock-attendees and all
>  > speakers to flock-speakers. We might want to send out an announcement
>  > email every morning for attendees and let them know it's coming so
>  > they'll check. We could also post a link to the morning announcements on
>  > the website? 
What are you thinking will be in the announcement email?  We should try
to get those drafted in advance if possible.

regards,

bex


> > 
> > 
> > Ok below is the research I mentioned.
> > 
> > Cheers,
> > ~m
> > 
> 
> -- 
> Cheers,
> Justin W. Flory
> jflory7(a)gmail.com
> 
> _______________________________________________
> flock-planning mailing list -- flock-planning(a)lists.fedoraproject.org
> To unsubscribe send an email to
> flock-planning-leave(a)lists.fedoraproject.org
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

[Máirín Duffy]

> > Also, I'd like to try to put together some guidelines or a
> SOP for
> the
> > video uploads (like a common set of base tags, adding the right
> metadata
> > (e.g. location / date), etc. This is something I'll try to work on
> > closer to Flock, but I think it would be valuable to make sure we get
> > everything right in the first go.
>
> We need to make sure the videos wind up manageable by our Youtube folks
> after the event.  Would it make more sense (and be easier to those who
> don't know how to do the upload) to have them put the videos in a known
> location for one person to do the uploads?  Otherwise I feel like we
> are
> going to spend a lot of effort to train a lot of people to do a process
> a small numer of times. 
If we had space on fedorapeople somewhere we could use nautilus on the laptops to set up a
gvfs / ssh mount and set ip a symlink so the vids automagically get uploaded as they
record?

> > > Also, some sessions (eg hackfests) won't make sense to record.
> Should we
> > > ask on the CFP side if the session makes sense to record or not?
>
> I don't think we need to.  I think we should work with talks always
> being recorded.  We can leave recording instructions next to the laptop
> if someone feels their hacksession warrants recording. 
This is incompatible with the approach of assigning sessions to funded attendees to video
nanny ahead of time, though.
 
> I wish we could get away from laptop recordings ... the quality is
> terrible.  Last year's audio was mostly unusuable. 
We can rent mics if you think its important? We priced that out.
> > > Communication Proposal
> > > =====================
> > > 
> > > Chat
> > > ------
> > > 
> > > By far IRC is the most widely-used chat medium, so if there is one
> > > official one, that should be it.
> > > 
> > > #fedora-flock - main channel
> > > 
> > > Room channels:
> > > 
> > > #fedora-flock-capecod
> > > #fedora-flock-barnstable
> > > #fedora-flock-grand-i
> > > #fedora-flock-grand-ii
> > > #fedora-flock-osterville
> > > #fedora-flock-centerville
> > > #fedora-flock-orleans
>
> I'd like to make it clear that we don't expect people to be hanging out
> on the room channels.  My understanding is that we want to use them for
> meetbox to pull in transcriptions. 
Yep agreed, they exist mostly for the people doing transcription work.
> > > 
> > > Signal was 2nd place; if we can set up a bridge between
> #fedora-flock on
> > > IRC and a telegram channel that would be good.
> > > 
> > 
> > For context, it is really easy to bridge a Telegram group to an IRC
> > channel. This is what the @fedora supergrouup is using for
> > #fedora-telegram and @fedoradiversity group is for #fedora-diversity.
> > We're using this as the bridge software right now:
> > 
> >     https://github.com/RITlug/teleirc
> > 
> > It's a simple NodeJS bot that isn't too difficult to set up. I'd be
> more
> > than willing to help with this once IRC channels are established, if
> > needed.
> > 
> > > Mailing Lists
> > > -----------------
> > > We need to set up:
> > > - flock-attendees-2017(a)lists.fpo
> > > - flock-speakers-2017(a)lists.fpo
> > > 
> > > And we need to subscribe all registrants to flock-attendees and all
> > > speakers to flock-speakers. We might want to send out an
> announcement
> > > email every morning for attendees and let them know it's coming so
> > > they'll check. We could also post a link to the morning
> announcements on
> > > the website?
>
> What are you thinking will be in the announcement email?  We should try
> to get those drafted in advance if possible. 
Good idea. For predrafted content we could have a summary of upcoming sessions that day.
Maybe reminders about policies / wifi password / how to get help / how to do yourvolunteer
tasks. Info about how to get the party bus the morning of that day. Maybe some
advertisement of fedora badges that could be earned and how to get them. We might also
want to do announcements day of based on how things go. Eg if people end up being confused
about where the pool is or where the closest pharmacy is or whatever.
> regards,
>
> bex
>
>
> > > 
> > > 
> > > Ok below is the research I mentioned.
> > > 
> > > Cheers,
> > > ~m
> > > 
> > 
> > -- 
> > Cheers,
> > Justin W. Flory
> > jflory7(a)gmail.com
> > 
> > _______________________________________________
> > flock-planning mailing list -- flock-planning(a)lists.fedoraproject.org
> > To unsubscribe send an email to
> > flock-planning-leave(a)lists.fedoraproject.org
> > Email had 1 attachment:
> > + signature.asc
> >   1k (application/pgp-signature)
> _______________________________________________
> flock-planning mailing list -- flock-planning(a)lists.fedoraproject.org
> To unsubscribe send an email to
> flock-planning-leave(a)lists.fedoraproject.org 
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Stephen John Smoogen]

On 27 April 2017 at 09:28, Máirín Duffy <fedora(a)linuxgrrl.com&gt; wrote:
> >> Also, I'd like to try to put together some guidelines or a SOP for
> >the
> >> video uploads (like a common set of base tags, adding the right
> >metadata
> >> (e.g. location / date), etc. This is something I'll try to work on
> >> closer to Flock, but I think it would be valuable to make sure we get
> >> everything right in the first go.
> >
> >We need to make sure the videos wind up manageable by our Youtube folks
> >after the event.  Would it make more sense (and be easier to those who
> >don't know how to do the upload) to have them put the videos in a known
> >location for one person to do the uploads?  Otherwise I feel like we
> >are
> >going to spend a lot of effort to train a lot of people to do a process
> >a small numer of times.
>
>  If we had space on fedorapeople somewhere we could use nautilus on the laptops to set up
> a gvfs / ssh mount and set ip a symlink so the vids automagically get uploaded as they
> record? 
Sadly I don't think that will work. The conference internet is going
to be maxed out with people and the connection upstream is usually
1/8th -> 1/16th of what is available downstream. This means that
pushing data up continuously is going to die a lot (either killing
everyone elses connection or stuttering) This may kill the video
recording or just leave a mess of dead data.

I would expect that any data will need to be uploaded 'after-hours' in
order to make sure that the video is uncorrupted.



-- 
Stephen J Smoogen.

[Máirín Duffy]

On 04/27/2017 09:58 AM, Stephen John Smoogen wrote:
>  Sadly I don't think that will work. The conference internet is
> going
>  to be maxed out with people and the connection upstream is usually
>  1/8th -> 1/16th of what is available downstream. This means that
>  pushing data up continuously is going to die a lot (either killing
>  everyone elses connection or stuttering) This may kill the video
>  recording or just leave a mess of dead data.
>
>  I would expect that any data will need to be uploaded 'after-hours' in
>  order to make sure that the video is uncorrupted. 
Could we set up chron to rsync all files in /home/$WHATEVER/Videos every 
30 minutes? And if the network fails, well it's an rsync?

~m

[Brian Exelbierd]

On Thu, Apr 27, 2017, at 03:28 PM, Máirín Duffy wrote:
>  
>  
>  
>  >> Also, I'd like to try to put together some guidelines or a SOP for
>  >the
>  >> video uploads (like a common set of base tags, adding the right
>  >metadata
>  >> (e.g. location / date), etc. This is something I'll try to work on
>  >> closer to Flock, but I think it would be valuable to make sure we get
>  >> everything right in the first go.
>  >
>  >We need to make sure the videos wind up manageable by our Youtube folks
>  >after the event.  Would it make more sense (and be easier to those who
>  >don't know how to do the upload) to have them put the videos in a known
>  >location for one person to do the uploads?  Otherwise I feel like we
>  >are
>  >going to spend a lot of effort to train a lot of people to do a process
>  >a small numer of times.
>  
>  If we had space on fedorapeople somewhere we could use nautilus on the
>  laptops to set up a gvfs / ssh mount and set ip a symlink so the vids
>  automagically get uploaded as they record?
>  
>  >
>  >> > Also, some sessions (eg hackfests) won't make sense to record.
>  >Should we
>  >> > ask on the CFP side if the session makes sense to record or not?
>  >
>  >I don't think we need to.  I think we should work with talks always
>  >being recorded.  We can leave recording instructions next to the laptop
>  >if someone feels their hacksession warrants recording.
>  
>  This is incompatible with the approach of assigning sessions to funded
>  attendees to video nanny ahead of time, though. 
No it isn't.  We can ask funded people to do the video management for
talks.  We can just not assign someone to the hack sessions.

>   
>  >
>  >I wish we could get away from laptop recordings ... the quality is
>  >terrible.  Last year's audio was mostly unusuable.
>  
>  We can rent mics if you think its important? We priced that out. 
Let's price that out for sure.  I'll also see if I can find out if we
can borrow some video kits.

>  >
>  >> > Communication Proposal
>  >> > =====================
>  >> > 
>  >> > Chat
>  >> > ------
>  >> > 
>  >> > By far IRC is the most widely-used chat medium, so if there is one
>  >> > official one, that should be it.
>  >> > 
>  >> > #fedora-flock - main channel
>  >> > 
>  >> > Room channels:
>  >> > 
>  >> > #fedora-flock-capecod
>  >> > #fedora-flock-barnstable
>  >> > #fedora-flock-grand-i
>  >> > #fedora-flock-grand-ii
>  >> > #fedora-flock-osterville
>  >> > #fedora-flock-centerville
>  >> > #fedora-flock-orleans
>  >
>  >I'd like to make it clear that we don't expect people to be hanging out
>  >on the room channels.  My understanding is that we want to use them for
>  >meetbox to pull in transcriptions.
>  
>  Yep agreed, they exist mostly for the people doing transcription work.
>  >
>  >> > 
>  >> > Signal was 2nd place; if we can set up a bridge between
>  >#fedora-flock on
>  >> > IRC and a telegram channel that would be good.
>  >> > 
>  >> 
>  >> For context, it is really easy to bridge a Telegram group to an IRC
>  >> channel. This is what the @fedora supergrouup is using for
>  >> #fedora-telegram and @fedoradiversity group is for #fedora-diversity.
>  >> We're using this as the bridge software right now:
>  >> 
>  >>     https://github.com/RITlug/teleirc
>  >> 
>  >> It's a simple NodeJS bot that isn't too difficult to set up. I'd be
>  >more
>  >> than willing to help with this once IRC channels are established, if
>  >> needed.
>  >> 
>  >> > Mailing Lists
>  >> > -----------------
>  >> > We need to set up:
>  >> > - flock-attendees-2017(a)lists.fpo
>  >> > - flock-speakers-2017(a)lists.fpo
>  >> > 
>  >> > And we need to subscribe all registrants to flock-attendees and all
>  >> > speakers to flock-speakers. We might want to send out an
>  >announcement
>  >> > email every morning for attendees and let them know it's coming so
>  >> > they'll check. We could also post a link to the morning
>  >announcements on
>  >> > the website?
>  >
>  >What are you thinking will be in the announcement email?  We should try
>  >to get those drafted in advance if possible.
>  
>  Good idea. For predrafted content we could have a summary of upcoming
>  sessions that day. Maybe reminders about policies / wifi password / how
>  to get help / how to do yourvolunteer tasks. Info about how to get the
>  party bus the morning of that day. Maybe some advertisement of fedora
>  badges that could be earned and how to get them. We might also want to do
>  announcements day of based on how things go. Eg if people end up being
>  confused about where the pool is or where the closest pharmacy is or
>  whatever. 
Can you get someone on the local team to take point on starting these
templates?

Also, let's start thinking about the badge.  I'd love to see the badge
issued at the event not an evening activity, even if the theme is based
in part on the activity.  I suggest this, echoing some others, because
we want people to realize we didn't just throw a big party.  The badge
is pretty obvious to folks who aren't there.

regards,

bex

[Stephen John Smoogen]

On 27 April 2017 at 10:04, Máirín Duffy <duffy(a)redhat.com&gt; wrote:
>  On 04/27/2017 09:58 AM, Stephen John Smoogen wrote:
> >
> > Sadly I don't think that will work. The conference internet is going
> > to be maxed out with people and the connection upstream is usually
> > 1/8th -> 1/16th of what is available downstream. This means that
> > pushing data up continuously is going to die a lot (either killing
> > everyone elses connection or stuttering) This may kill the video
> > recording or just leave a mess of dead data.
> >
> > I would expect that any data will need to be uploaded 'after-hours' in
> > order to make sure that the video is uncorrupted.
>
>
>  Could we set up chron to rsync all files in /home/$WHATEVER/Videos every 30
>  minutes? And if the network fails, well it's an rsync? 
It will depend on whether you have a dedicated network or not. If it
is not a dedicated network you can into run failing everyone's network
as the router or wireless access points try to unblock themselves.
This is one of the reasons why computer conference wireless is usually
so bad even when you have put in a bunch of extra APs to deal with it.
A lot of computer people like to push stuff more than "normal" people
and all those pushes are competing for usually a 1->80mbit uplink. The
routers go into a "ok buffers full, drop and if they really needed it
they will start over" which every rsync/scp/git push/etc will do.

https://arstechnica.com/information-technology/2017/03/802-eleventy-what-...

[I believe cable modems use a similar CB radio type technology of
listen/send so it explains why a lot of cable modems make for an
unhappy programmer.]

>  ~m
>
>  _______________________________________________
>  flock-planning mailing list -- flock-planning(a)lists.fedoraproject.org
>  To unsubscribe send an email to flock-planning-leave(a)lists.fedoraproject.org 


-- 
Stephen J Smoogen.

[Máirín Duffy]

Hi Smooge,

On 04/27/2017 10:23 AM, Stephen John Smoogen wrote:
>  It will depend on whether you have a dedicated network or not. If it
>  is not a dedicated network you can into run failing everyone's network
>  as the router or wireless access points try to unblock themselves.
>  This is one of the reasons why computer conference wireless is usually
>  so bad even when you have put in a bunch of extra APs to deal with it.
>  A lot of computer people like to push stuff more than "normal" people
>  and all those pushes are competing for usually a 1->80mbit uplink. The
>  routers go into a "ok buffers full, drop and if they really needed it
>  they will start over" which every rsync/scp/git push/etc will do. 
Should we look into specing out / pricing out a separate wireless 
network just for presentation computers to facilitate this? Would that help?

~m

[charles profitt]

On Wed, 2017-04-26 at 21:43 -0400, Máirín Duffy wrote:
>  Hi,
>  
>  So as suggested earlier [1], we'regoing to give funded attendees
>  blog, video nanny, or photo assignments to cover different Flock
>  sessions. This is as it's been for all Fedora eventswith the trip
>  report requirement, with a minor tweak that we're assigning specific
>  talks for coverage rather than leaving it open-ended. 
Ubuntu did something similar at UDS. They had 'crew' positions that
were assigned. The fantastic thing they did as a bonus was that crew
got a special t-shirt for the event as well. This did two things:

1) Identified the crew to other attendees

2) Gave the people performing crew duties a sense of pride that they
had a 'special' t-shirt. The crew t-shirts were a different color and
had the word 'crew' on the back.

In the Fedora world that could potentially be accompanied by a badge as
well.

>  
>  Media Proposal:
>  ============== 
>  We will need editors for the community blog to vet the posts and
> push
>  them through each evening. It might be nice to have Fedora magazine
>  summary posts each evening as well. 
I work at a K-12 so the dates for this years Flock conflict with
getting all the IT stuff ready for the opening of school and I likely
can not attend. I should be able to assist with the editing tasks each
evening.

>  
>  For photographers:
>  --------------------------
>  
>  Those who have agreed to take on a photo assignment should agree to
>  release their photos under a CC-BY or CC-BY-SA license.
>  
>  They should post photos either to instagram or Flickr (most popular
>  pure photo sharing apps). On instagram, they will put the tag
>  #flockcod posts. On Flickr, they will join a group (we'll set it up
>  asopen join) and posttheir photos to that group, also tagging them
>  with #flockcod.
>  
>  (Note that Facebook was popular for sharing photos too, but I have
>  direct experience with trying to get photos out via their API and
>  unless a very specific and finnicky workflow is followed, they are
>  irretrievable. So I'm recommending avoiding that.) 
I agree using Flickr as the place to host photos. Then Facebook can
link to the Flickr photos to get more coverage.

>  
>  Communication Proposal
>  =====================
>  
>  Chat
>  ------
>  
>  By far IRC is the most widely-used chat medium, so if there is one
>  official one, that should be it.
>  
>  #fedora-flock - main channel
>  
>  Room channels:
>  
>  #fedora-flock-capecod
>  #fedora-flock-barnstable
>  #fedora-flock-grand-i
>  #fedora-flock-grand-ii
>  #fedora-flock-osterville
>  #fedora-flock-centerville
>  #fedora-flock-orleans
>   
At UDS we had a 'crew' member that was assigned to ask questions of the
in-person people from IRC to assist in remote participation. Though
with UDS we were live streaming the in-person conversation both with
video and audio. It would be fantastic to have the ability for remote
participants to contribute, but I understand that is often difficult.


Solid proposals Máirín!

Charles

[charles profitt]

On Thu, 2017-04-27 at 10:23 -0400, Stephen John Smoogen wrote:
>  On 27 April 2017 at 10:04, Máirín Duffy <duffy(a)redhat.com&gt;
> wrote:
>  > 
>  
>  It will depend on whether you have a dedicated network or not. If it
>  is not a dedicated network you can into run failing everyone's
>  network as the router or wireless access points try to unblock
>  themselves. This is one of the reasons why computer conference
>  wireless is usually so bad even when you have put in a bunch of extra
>  APs to deal with it. A lot of computer people like to push stuff more
>  than "normal" people and all those pushes are competing for usually a
>  1->80mbit uplink. The routers go into a "ok buffers full, drop and if
>  they really needed it they will start over" which every rsync/scp/git
>  push/etc will do. 
With UDS the video / audio feed was always over a wired connection.
Though I believe Canonical paid to have additional bandwidth brought in
just for the conference and isolated it on their own networking gear.

The information security conference I assist with every year does the
same thing. In that case the hotel has a connection that they turn on
for the two days of conference and they handle all the wireless as
well.

Charles