Changes between Version 1 and Version 2 of member-admin/meetingnotes7-31-14


Ignore:
Timestamp:
Jul 31, 2014, 6:38:05 PM (5 years ago)
Author:
Stephen Mahood
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • member-admin/meetingnotes7-31-14

    v1 v2  
    22
    33'''Outreach'''
    4     mv: idea of creating a members email list, for us to ask members to join to create a community place to announce events, discuss topics in the community, discuss mayfirst policies
    5     HG: have a large a community how do we make sure it is moderators, concern of capacity
    6     mv: list about events, and about mayfirst things, but if we get to a point that to many posts are happening then I think that is a good thing as it is a sign of member engaging
    7     A: Can it connect with JG idea of identifying sectors and areas of interest, to bring kind of issue to the discussion
    8     HG: JG idea was to segment the membership, to target the interaction. Idea of part of the outreach, to ID specific targeted outreach. A contact list, to have a discussion, each LC member would need to have a work sheet for those discussions, so we can enter this stuff into the DB. We could target the outreach. Outreach and data collection at the same.
    9     mv: likes the idea but concerned with it just being a drive the membership meeting
    10     HG: since we are already going to be doing outreach and good to get some data, but discussion and getting to know is the priority, now that we have a database to update.
     4    mv: idea of creating a members email list, for us to ask members to join to create a community place to announce events, discuss topics in the community, discuss mayfirst policies[[BR]]
     5    HG: have a large a community how do we make sure it is moderators, concern of capacity[[BR]]
     6    mv: list about events, and about mayfirst things, but if we get to a point that to many posts are happening then I think that is a good thing as it is a sign of member engaging[[BR]]
     7    A: Can it connect with JG idea of identifying sectors and areas of interest, to bring kind of issue to the discussion[[BR]]
     8    HG: JG idea was to segment the membership, to target the interaction. Idea of part of the outreach, to ID specific targeted outreach. A contact list, to have a discussion, each LC member would need to have a work sheet for those discussions, so we can enter this stuff into the DB. We could target the outreach. Outreach and data collection at the same.[[BR]]
     9    mv: likes the idea but concerned with it just being a drive the membership meeting [[BR]]
     10    HG: since we are already going to be doing outreach and good to get some data, but discussion and getting to know is the priority, now that we have a database to update.[[BR]]
    1111
    1212'''Web Redesign
    1313'''
    14     HG: List of things we should have on the webpage
    15     keep a list of ideas
    16     HG: will send a list to the membership team for the ticket that discusses this
     14    HG: List of things we should have on the webpage[[BR]]
     15    keep a list of ideas[[BR]]
     16    HG: will send a list to the membership team for the ticket that discusses this[[BR]]
    1717
    1818'''People Links Podcast
    1919'''
    2020
    21 mv: started with explaining some of the experience of producing the cyberunions podcast, specifically about the structure. He suggests a flexible structure with some consistency of 2 segments, 1 on mayfirst include resources, or something that might be impacting and the 2nd segment to focus on a member and their movement work. The membermovement section would be an interview, which could take place before the actual podcast is recorded.
    22 HG/A: How long should it be?
    23 mv: mentioned the process that cyberunions went through in first focusing on short 15-20 minute piece but realized that shows can get rich in content and on average the show is about 45 minutes. He suggested to keep in flexible but 30-60 minutes is a good frame for one guest interview and maybe a 60-90 minutes for 2 guests, but depends on the content
    24 A: suggest a 30 minute show, but good to be flexible
    25 HG: 30 minute ideal, suggests resources and issues, tech development in the field or focusing on new tools. Invite folks to a training.
    26 A: Answering many questions, common issues people are having.
    27 HG: Take people through the process of things like reseting a password or things with service
    28 HG: thematic  discussions as an idea on future shows.
    29 mv: who would be the hosts, would it be the same hosts or rotation, he never had experience with rotation of hosts but likes the idea.
    30 HG: committee of hosts, rotate, a group and hosts and segments.
    31 A: people who volunteer do not have to commit, easer to rotate less pressure and gives a different set of voices for the show
    32 mv: suggest single language podcast one for english and one for spanish
    33 HG: transcript in bilingual, but likes the single language podcast
    34 HG: should we have a script or some sort to bring it back to floss
    35 mv: to maybe introduce resources to the member movement section i.e. mailchimp many people use it, could discuss mailman or civicrm
    36 HG: what do we need to make this happen?
     21    mv: started with explaining some of the experience of producing the cyberunions podcast, specifically about the structure. He suggests a flexible structure with some consistency of 2 segments, 1 on mayfirst include resources, or something that might be impacting and the 2nd segment to focus on a member and their movement work. The membermovement section would be an interview, which could take place before the actual podcast is recorded.[[BR]]
     22    HG/A: How long should it be?[[BR]]
     23    mv: mentioned the process that cyberunions went through in first focusing on short 15-20 minute piece but realized that shows can get rich in content and on average the show is about 45 minutes. He suggested to keep in flexible but 30-60 minutes is a good frame for one guest interview and maybe a 60-90 minutes for 2 guests, but depends on the content[[BR]]
     24    A: suggest a 30 minute show, but good to be flexible[[BR]]
     25    HG: 30 minute ideal, suggests resources and issues, tech development in the field or focusing on new tools. Invite folks to a training.[[BR]]
     26    A: Answering many questions, common issues people are having.[[BR]]
     27    HG: Take people through the process of things like reseting a password or things with service[[BR]]
     28    HG: thematic  discussions as an idea on future shows.[[BR]]
     29    mv: who would be the hosts, would it be the same hosts or rotation, he never had experience with rotation of hosts but likes the idea.[[BR]]
     30    HG: committee of hosts, rotate, a group and hosts and segments.[[BR]]
     31    A: people who volunteer do not have to commit, easer to rotate less pressure and gives a different set of voices for the show[[BR]]
     32    mv: suggest single language podcast one for english and one for spanish[[BR]]
     33    HG: transcript in bilingual, but likes the single language podcast [[BR]]
     34    HG: should we have a script or some sort to bring it back to floss[[BR]]
     35    mv: to maybe introduce resources to the member movement section i.e. mailchimp many people use it, could discuss mailman or civicrm[[BR]]
     36    HG: what do we need to make this happen?[[BR]]
    3737
    3838Technology: need a mixer  on the call for recording all voices
     
    4747Hosts: Need to decide to host
    4848
    49 HG: Good to shift the order around might lead with member movement or swap with mayfirst section
    50 First show Grainne & Abi to be part of both segments.
     49    HG: Good to shift the order around might lead with member movement or swap with mayfirst section[[BR]]
     50
     51'''First show''' Grainne & Abi to be part of both segments.
    5152Good to get a list of like 10 groups that we could talk to about a specific topic.
    5253