|
Size: 6352
Comment:
|
Size: 10766
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from Migrated/MeetingHowTo #language en <<TableOfContents>> |
|
| Line 3: | Line 7: |
| * You should not restrict participation of your meetings to Fellows. Give interested people the possibility to participate. A lot of people join the Fellowship after they participated in the group. * Be careful that your meetings do not become just babbling. Try to actually do things. It is not about who has the best idea, but who _does_ the coolest things. Also moderate the meeting if necessary. * Do not concentrate on technical issues. Concentrate on political and social issues. * At the beginning it might help to co-locate your meeting with already existing ones. For example in some cities there are already parallel Free Software, Security, etc. meetings. Especially for the social "non-working" part it is good to have different groups. Then they will also see what you do. |
== Who can attend an FSFE / Fellowship meeting? == * You should not restrict participation of your meetings to Fellows. Give interested people the possibility to participate. A lot of people join the Fellowship and get active in FSFE activities after they took part in a local group meeting. == What to do during an FSFE / Fellowship meeting? == * If there's a talk at the meeting or something specific to do, more people show up. See the announcement section for more information about how to advertise your event * What else can you do instead of a talk? Here's an incomplete list of what Fellowship groups have already done and/or could do: * watch a movie and discuss afterwards (e.g.: [[http://patentabsurdity.com/|Patent absurdity]], [[http://en.wikipedia.org/wiki/The_Yes_Men_Fix_the_World|Yes Men Fix The World]], ...) * Info-booth in pedestrian areas on special occasions like [[http://documentfreedom.org/|DFD]] or [[http://softwarefreedomday.org/|SFD]] * invite local politicians to discuss * phone or video conferences with other Fellowship groups * web sptrints to close issues on https://trac.fsfe.org/fsfe-web * draft (open) letters to politicians or public institutions (http://fsfe.org/news/2010/news-20100802-01.en.html initialized by Fellowship Group Bonn IIRC) * visit public institutions for advocacy work as this group in Norway did: https://joinup.ec.europa.eu/community/osor/news/touring-norways-municipalities-kindles-open-source-interest * start a new campaign! E.g: [[https://fscons.org/2012/schedule/session/fixing-public-procurement-how-well-stop-european-g/|monitoring all IT related public procurement notices in Finland]], [[http://pdfreaders.org/|pdfreaders.org]] (Fellowship group Berlin) * participate or organize your own [[https://www.cryptoparty.in/|cryptoparties]] * provide info events in schools * have a booth at "non-nerdy" events, like the [[http://blogs.fsfe.org/franz.gratzer/2013/06/12/booth-at-veganmania-in-vienna-2013/|Fellowship group Vienna did in 2013]] * Depending on the people attending your meetings, try not to focus too much on technical issues. Political and social issues are FSFE's speciality and talking about it helps reaching wider audiences. Note that technical discussions can be very excluding for non-technical people * It is advisable to "embed" the Fellowship group in other local groups (hackerspaces, LUGs, etc) and network with them, gain forces and resources for events, talks and the like. Don't try to "compete" with existing groups, rather integrate and connect. Being well connected also helps in getting slots for talks to reach a broader audience for our message. |
| Line 8: | Line 32: |
| * It is helpful to create a mailinglist before your first meeting, so you can just announce it. Please contact <<MailTo(fellowship-hackers AT fsfeurope DOT org)>> if you need a mailinglist. | == Support == * if there were problems or you have any suggestions please sent an email to <<MailTo(fellowship AT fsfeurope DOT org)>>. |
| Line 12: | Line 40: |
| * You should send an e-mail to all Fellows in a certain ZIP code area. Include a planned agenda so people can imagine what will happen. Please send an e-mail to <<MailTo(fellowship AT fsfeurope DOT org)>> with a range of postal (zip) codes, subject and the text. Then we will send an e-mail to the Fellows in that area. This should be send out at latest than 10 days before the event as it will also take a while until we can send it out. | == To FSFE's network == * You can send an e-mail to all Fellows in a certain ZIP code area. Include a planned agenda so people can imagine what will happen. Please send an e-mail to <<MailTo(fellowship AT fsfeurope DOT org)>> with a range of postal (zip) codes, subject and the text. Then we will send an e-mail to the Fellows in that area. |
| Line 14: | Line 43: |
| * Announce your meetings at mailing lists from local user-groups, [[https://lists.fsfe.org/mailman/listinfo | the Mailman list for your Fellowship group]], [[http://www.fsfe.org/contact/local.html | your country team]] At least in the beginning you should also announce it on the [[http://www.fsfe.org/contact/community.html | public discussion list]] for your region (if there is any). | /!\ This should be send out at latest than 10 days before the event as it will also take a while until we can send it out. |
| Line 16: | Line 45: |
| * Write about your meetings on planet.fsfe.org (send your RSS feed to fellowship-hackers@fsfeurope.org so we can add your weblog to the planet), and if you had a working meeting write a result protocol. | * Blog about your activities, if possible also in English to allow others to see what's going on and that something _is_ going on. |
| Line 18: | Line 47: |
| * Add the event on [[FellowshipEvents]] and if possible also on [[http://www.fsfe.org/events/events.html | FSFE's event page]]: See FSFE's [[http://www.fsfe.org/contribute/web/web.html | information page for webmasters]] to find out how to edit the web pages. Alternatively, you can send an email to <<MailTo(web AT fsfeurope DOT org)>> and ask our volunteers to put the event entry online for you. It might be a good idea to follow the style of existing entries on that list. | * Feel free to make extensive use of this Wiki as well. All fellows have an account on the wiki, and non-fellows can request an account ([[https://wiki.fsfe.org/UserGuide#Guest_accounts|Follow this guide]]). * You can create a wiki page for your group http://wiki.fsfe.org/groups/GroupName |
| Line 20: | Line 50: |
| * Add a wiki page for your group http://wiki.fsfe.org/groups/GroupName | * You can have your posts added to [[ planet.fsfe.org | planet.fsfe.org ]]. Send your RSS feeds to <<MailTo(fellowship-hackers@fsfeurope.org)>> so we can add your blog to the planets. It inspires other people! * Note: We try to make the planets language-dependant. Please try to make use of categories or tags which are language-specific so that we can generate language-specific feeds and add English posts to the English planet and other languages to each language's planet. |
| Line 22: | Line 53: |
| = Activities = | * You can add the event on [[FellowshipEvents]] and if possible also on [[http://www.fsfe.org/events/events.html | FSFE's event page]]: See FSFE's [[http://www.fsfe.org/contribute/web/web.html | information page for webmasters]] to find out how to edit the web pages. Alternatively, you can send an email to <<MailTo(web AT fsfeurope DOT org)>> and ask our volunteers to put the event entry online for you. It might be a good idea to follow the style of existing entries on that list. |
| Line 24: | Line 55: |
| Of course you are free to just meet, drink beer and discuss about Free Software related issues. Here some tipps when you want to do activities. | |
| Line 26: | Line 56: |
| * Do not try to make too complex activities. It is better to start with small tasks which you really can implement. When you have doubts it is a sign that it is too much for volunteers. You can also discuss planned activities with <<MailTo(coordinators AT list DOT fsfe DOT org)>> and see what other experiences group coordinators think about it. * Document planned and done activities in the wiki so you can point others to it, and others can comment on it. * Agenda proposals: Activities for DFD, SFD, a local booth at an event (see BoothCountdown and [[BoothFAQ]]), have evening topics about a certain topic, small workshops, or a release party. Beside taking a look at the recent [[http://mailman.fsfeurope.org/pipermail/discussion/ | archives of the discussion@ mailing list]] and the [[http://planet.fsfe.org/ | planet ]] to see if there are any current topics that might be of interest it is also a good idea to try to answer questions like: * Does anyone know of Free Software being used by government bodies? * ...or in schools? * Does the government have a policy on Free Software / Open Standards? * Can anyone help with [[http://www.fsfe.org/contribute/translators/translators.en.html | webpage translations]], [[http://www.fsfe.org/contribute/designers/designers.en.html|design stuff]], [[http://www.fsfe.org/contribute/contribute.en.html|or other things]]? * Is anyone involved with related project such as !OpenStreetMap or !OpenMoko * What other groups and meetings exist in this region? * Is today's meeting format good, or what's the best way to meet next time? |
== To your local network == |
| Line 37: | Line 58: |
| * Moderation: * During the working session, Q&As, etc. you should moderate. If people start telling stories about their life and do not stick to the topic it is absolutely fine to stop them. The other participants will thank you for it. * In general it is better explain a chatterbox your meeting rules than loosing more and more people who would actually like to do things because they are pissed about this behavoir. * If you have a presentation it is good to have a timer and give a notice to the speaker before the time is over (e.g. 10 minutes left, 5 minutes left, game over). |
* You can announce your meetings on the mailing lists of local user-groups, [[https://lists.fsfe.org/mailman/listinfo | the Mailman list for your Fellowship group]], [[http://www.fsfe.org/contact/local.html | your country team]]. At least in the beginning it is also useful to announce it on the [[http://www.fsfe.org/contact/community.html | public discussion list]] for your region (if there is any). |
| Line 42: | Line 60: |
| = Time and venue = | /!\ Personal contacts are important! Check who in your network could be interested by Free Software, and make your event attractive to those people! If you are part of other organisations, promote your event on their usual channels, highlighting their link with Free Software |
| Line 44: | Line 62: |
| Choosing a good time and venue really depends on what audience you expect. If you just want to attract people from one city, then you could organise a formal meeting with short presentations, or you could just pick a pub/cafe and have a meeting there. | * It is helpful to create a mailinglist before your first meeting, so you can just announce it. Please contact <<MailTo(system-hackers AT fsfeurope DOT org)>> if you need a mailinglist. |
| Line 46: | Line 64: |
| * A city centre venue might be difficult for people who need to park a car. * For people coming from other cities by train, a venue that is not near the train station might be hard for them to find. * If you hold the meeting on a weeknight, then people who have a travel time of more than 1 hour will probably not come. |
== Design your announcement notice == |
| Line 50: | Line 66: |
| = Other ideas what you can do = | * If your announce your meeting via other means than email, have a look at the [[https://fsfe.org/contribute/designers/styleguide.en.html#id-fellowship-guide|designer section]] of the website, you can find the official Fellowship colours and other designer guidelines. = Tips for your activities = Of course you are free to just meet, drink beer and other beverages, discuss about Free Software related issues. Here some tips gathered from experienced event organisers: * Do not try to make too complex activities. It is better to start with small tasks which you really can implement. When you have doubts it is a sign that it is too much for volunteers. You can discuss planned activities on <<MailTo(coordinators AT list DOT fsfe DOT org)>> and see what other group coordinators think about it. * Document planned and done activities in the wiki or on your blog so you can point others to it, and they can comment on it. == Activities ideas == * Activities for DFD ([[ documentfreedom.org | Document Freedom Day]]), SFD (Software Freedom Day)... (!) Issuing DFD awards is a lot of fun and rewarding. Every coordinator who participated in such an event described it as one of the most positive experiences with the Fellowship group. Which confirms that positive campaigning is a good thing to do. * Preparing a local booth at an event (see BoothCountdown and [[BoothFAQ]]), * Small workshops * Release party (!) You can have a look at the recent [[http://mailman.fsfeurope.org/pipermail/discussion/ | archives of the discussion@ mailing list]] and the [[http://planet.fsfe.org/ | planet ]] to see if there are any current topics that might be of interest (!) Bug sprints are fun! pdfreaders, trac.fsfe.org, maybe others... They don't take much time to prepare and are an easy way to get something accomplished as a group. == Know your group members == * People who don't get our message need to have it explained. Don't be mad at them. That's our audience. Tell them where to go and how to get help. Distribute Free Software CDs/DVDs if possible (e.g. Valo-CD or FramaKey for Windows users). * To plan activities that are interesting the meeting organisers need to know their group members: * You may use the [[https://vote.fsfe.org/ | Limesurvey instance ]] to check on what other fellows in your group want. * Some questions you might want to ask: * Does anyone know of Free Software being used by local government bodies? Do we want to support them? If not, do we want to lobby them? * ...or in schools? * Does the government have a policy on Free Software / Open Standards? * Can anyone help with [[http://www.fsfe.org/contribute/translators/translators.en.html | webpage translations]], [[http://www.fsfe.org/contribute/designers/designers.en.html|design work]], [[http://www.fsfe.org/contribute/contribute.en.html|or other things]]? * Is anyone involved with related project such as !OpenStreetMap or !OpenMoko * What other groups and meetings exist in this region? * Is today's meeting format good, or what's the best way to meet next time? == Inclusive groups == Here are a few tips to make your group meetings / mailing list attractive and welcoming to new people especially if they are not technical: * highlight the link between Free Software and other topics * be very clear that newcomers are welcome to ask any kind of questions. Sometimes checking with them if they are lost can be a good idea. * beware of super technical discussions, it can be very excluding * careful with inside jokes - at least try to include newcomers by explaining your jokes and sharing your group's culture. Sexist, racist of homophobic jokes are not funny == How to get more women involved == There is no magical solution. Being '''excellent to each other''' and welcoming in general is clearly the first step. {*} 2 cents from a female fellow on this: try to avoid women specific behaviours, even if it's to be especially nice. What makes a group inclusive is a global atmosphere. == Moderation: == * During the working session, Q&As, etc. you can ease things for everyone by [[ http://blogs.fsfe.org/lucile.falg/2013/10/14/tips-for-afk-meeting-moderation/ | moderating the discussions ]] == Group coordination == /!\ Coordinators, if you don't have a backup coordinator yet, get one! Spread the load on more shoulders. = Other ideas = |
| Line 53: | Line 140: |
= Postprocessing = * if possible write a little text about the meeting and post it on your fsfe.org blog and/or to your regional mailing list * if there were problems or you have any suggestions please sent an email to <<MailTo(fellowship AT fsfeurope DOT org)>>. |
General
Who can attend an FSFE / Fellowship meeting?
- You should not restrict participation of your meetings to Fellows. Give interested people the possibility to participate. A lot of people join the Fellowship and get active in FSFE activities after they took part in a local group meeting.
What to do during an FSFE / Fellowship meeting?
- If there's a talk at the meeting or something specific to do, more people show up. See the announcement section for more information about how to advertise your event
- What else can you do instead of a talk? Here's an incomplete list of what Fellowship groups have already done and/or could do:
watch a movie and discuss afterwards (e.g.: Patent absurdity, Yes Men Fix The World, ...)
Info-booth in pedestrian areas on special occasions like DFD or SFD
- invite local politicians to discuss
- phone or video conferences with other Fellowship groups
web sptrints to close issues on https://trac.fsfe.org/fsfe-web
draft (open) letters to politicians or public institutions (http://fsfe.org/news/2010/news-20100802-01.en.html initialized by Fellowship Group Bonn IIRC)
visit public institutions for advocacy work as this group in Norway did: https://joinup.ec.europa.eu/community/osor/news/touring-norways-municipalities-kindles-open-source-interest
start a new campaign! E.g: monitoring all IT related public procurement notices in Finland, pdfreaders.org (Fellowship group Berlin)
participate or organize your own cryptoparties
- provide info events in schools
have a booth at "non-nerdy" events, like the Fellowship group Vienna did in 2013
- What else can you do instead of a talk? Here's an incomplete list of what Fellowship groups have already done and/or could do:
- Depending on the people attending your meetings, try not to focus too much on technical issues. Political and social issues are FSFE's speciality and talking about it helps reaching wider audiences. Note that technical discussions can be very excluding for non-technical people
- It is advisable to "embed" the Fellowship group in other local groups (hackerspaces, LUGs, etc) and network with them, gain forces and resources for events, talks and the like. Don't try to "compete" with existing groups, rather integrate and connect. Being well connected also helps in getting slots for talks to reach a broader audience for our message.
For the first meeting it may be a good idea to give a short introduction to the Fellowship and the FSFE. This presentation can be used as a starting point.
Support
if there were problems or you have any suggestions please sent an email to <fellowship AT fsfeurope DOT org>.
Announcements
To FSFE's network
You can send an e-mail to all Fellows in a certain ZIP code area. Include a planned agenda so people can imagine what will happen. Please send an e-mail to <fellowship AT fsfeurope DOT org> with a range of postal (zip) codes, subject and the text. Then we will send an e-mail to the Fellows in that area.
![/!\](/moin_static198/fsfe/img/alert.png "/!\"){kind=small}
This should be send out at latest than 10 days before the event as it will also take a while until we can send it out.
- Blog about your activities, if possible also in English to allow others to see what's going on and that something _is_ going on.
Feel free to make extensive use of this Wiki as well. All fellows have an account on the wiki, and non-fellows can request an account (Follow this guide).
You can create a wiki page for your group http://wiki.fsfe.org/groups/GroupName
You can have your posts added to planet.fsfe.org. Send your RSS feeds to <fellowship-hackers@fsfeurope.org> so we can add your blog to the planets. It inspires other people!
- Note: We try to make the planets language-dependant. Please try to make use of categories or tags which are language-specific so that we can generate language-specific feeds and add English posts to the English planet and other languages to each language's planet.
You can add the event on FellowshipEvents and if possible also on FSFE's event page: See FSFE's information page for webmasters to find out how to edit the web pages. Alternatively, you can send an email to <web AT fsfeurope DOT org> and ask our volunteers to put the event entry online for you. It might be a good idea to follow the style of existing entries on that list.
To your local network
You can announce your meetings on the mailing lists of local user-groups, the Mailman list for your Fellowship group, your country team. At least in the beginning it is also useful to announce it on the public discussion list for your region (if there is any).
Personal contacts are important! Check who in your network could be interested by Free Software, and make your event attractive to those people! If you are part of other organisations, promote your event on their usual channels, highlighting their link with Free Software
It is helpful to create a mailinglist before your first meeting, so you can just announce it. Please contact <system-hackers AT fsfeurope DOT org> if you need a mailinglist.
Design your announcement notice
If your announce your meeting via other means than email, have a look at the designer section of the website, you can find the official Fellowship colours and other designer guidelines.
Tips for your activities
Of course you are free to just meet, drink beer and other beverages, discuss about Free Software related issues. Here some tips gathered from experienced event organisers:
Do not try to make too complex activities. It is better to start with small tasks which you really can implement. When you have doubts it is a sign that it is too much for volunteers. You can discuss planned activities on <coordinators AT list DOT fsfe DOT org> and see what other group coordinators think about it.
- Document planned and done activities in the wiki or on your blog so you can point others to it, and they can comment on it.
Activities ideas
Activities for DFD (Document Freedom Day), SFD (Software Freedom Day)...
Issuing DFD awards is a lot of fun and rewarding. Every coordinator who participated in such an event described it as one of the most positive experiences with the Fellowship group. Which confirms that positive campaigning is a good thing to do.
Preparing a local booth at an event (see BoothCountdown and BoothFAQ),
- Small workshops
- Release party
You can have a look at the recent archives of the discussion@ mailing list and the planet to see if there are any current topics that might be of interest
Bug sprints are fun! pdfreaders, trac.fsfe.org, maybe others... They don't take much time to prepare and are an easy way to get something accomplished as a group.
Know your group members
People who don't get our message need to have it explained. Don't be mad at them. That's our audience. Tell them where to go and how to get help. Distribute Free Software CDs/DVDs if possible (e.g. Valo-CD or FramaKey for Windows users).
- To plan activities that are interesting the meeting organisers need to know their group members:
You may use the Limesurvey instance to check on what other fellows in your group want.
- Some questions you might want to ask:
- Does anyone know of Free Software being used by local government bodies? Do we want to support them? If not, do we want to lobby them?
- ...or in schools?
- Does the government have a policy on Free Software / Open Standards?
Can anyone help with webpage translations, design work, or other things?
Is anyone involved with related project such as OpenStreetMap or OpenMoko
- What other groups and meetings exist in this region?
- Is today's meeting format good, or what's the best way to meet next time?
Inclusive groups
Here are a few tips to make your group meetings / mailing list attractive and welcoming to new people especially if they are not technical:
- highlight the link between Free Software and other topics
- be very clear that newcomers are welcome to ask any kind of questions. Sometimes checking with them if they are lost can be a good idea.
- beware of super technical discussions, it can be very excluding
- careful with inside jokes - at least try to include newcomers by explaining your jokes and sharing your group's culture. Sexist, racist of homophobic jokes are not funny
How to get more women involved
There is no magical solution.
Being excellent to each other and welcoming in general is clearly the first step.
2 cents from a female fellow on this: try to avoid women specific behaviours, even if it's to be especially nice. What makes a group inclusive is a global atmosphere.
Moderation:
During the working session, Q&As, etc. you can ease things for everyone by moderating the discussions
Group coordination
Coordinators, if you don't have a backup coordinator yet, get one! Spread the load on more shoulders.
Other ideas
The coordinator of the meetings can take orders for FSFE merchandise, send an omnibus order to be delivered to him/her, and distribute the items at the next meeting. This way, people can save shipping costs.