Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2020.1 Edition #17

Merged
merged 33 commits into from
Jul 20, 2020
Merged
Show file tree
Hide file tree
Changes from 9 commits
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
9efc03c
a lot of typo
Mte90 Feb 10, 2020
3d58cf3
another typo
Mte90 Feb 10, 2020
17e917b
fix #7
Mte90 Mar 7, 2020
3cb4087
transcript new notes in the book? let's start
Mte90 Mar 7, 2020
208b296
transcriptiotion in progress with new stuff
Mte90 Mar 8, 2020
504bed9
other notes added to the book
Mte90 Mar 9, 2020
8a5be0a
adding @ryuno-ki in the thanks section
Mte90 Mar 10, 2020
16b0b9b
how many notes do you have?
Mte90 Mar 10, 2020
8d962e1
just another new section
Mte90 Mar 11, 2020
7fcd248
some few links and notes
Mte90 Mar 19, 2020
f2cb9b7
other notes
Mte90 Mar 26, 2020
64c66d9
finished my notes and resources
Mte90 Mar 29, 2020
fc29d51
first bunch of revisions
Mte90 Mar 31, 2020
3a58d79
second bunch of revisions
Mte90 Mar 31, 2020
14808ea
finish review
Mte90 Mar 31, 2020
0ebe7fe
rewriting of delegating section
Mte90 Apr 26, 2020
7229103
adding more information about arguing
Mte90 Apr 27, 2020
45f655b
new thoughts
Mte90 May 2, 2020
f556ec7
more resources
Mte90 May 2, 2020
6a2176f
new tiny chapter
Mte90 May 5, 2020
acc1c3a
a lot of notes... written!
Mte90 May 29, 2020
6ef688b
resize a bit the cover
Mte90 Jun 5, 2020
d947ec9
first 3 chapters review
Mte90 Jun 5, 2020
8409ed4
reviewed another chapter
Mte90 Jun 6, 2020
c3be940
reviewed various chapters
Mte90 Jun 6, 2020
79d0a43
reviewed also the appendixes
Mte90 Jun 6, 2020
5224c2c
first round of review by Andrè
Mte90 Jul 2, 2020
8d8f13e
first round of review by Andrè
Mte90 Jul 2, 2020
9b76f58
first round of review by Andrè
Mte90 Jul 2, 2020
ceb167c
review of chapter 3
Mte90 Jul 18, 2020
b9108e1
finished another review round!
Mte90 Jul 18, 2020
fd210cc
finished another review round!
Mte90 Jul 18, 2020
ad4517b
last revision
Mte90 Jul 20, 2020
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
46 changes: 41 additions & 5 deletions manuscript/appendix.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,47 @@
-# Appendix 1 for Community Managers

## Divide your community members to various levels

As we saw in this book a project can have different areas of involvements or activities and this based on the volunteers availability.
It is important to organize at the best what you want to do as community manager divide (just for you) the volunteers in various levels so based on your needs you know what kind of people to reach.
We can define as example in this ways:

* Author/Owner - The creator of a project or the is the leader
* Maintainer - A different role then the above that is doing the hard work of keeping everything work and also checking for issues or new opportunities
* Contributors - People that can work based on their time on specific activities
* Community members - the whole group of people that is moving on the project

This groups of people can have as example different communications or different knowledge of what is the project is doing. Keeping an eye on those will help you to find people "to promote" on different tasks that can require more accountability as example.

## How to do productive discussions

One of the problem in a community that is easy to change the focus or the point of the discussion, in other words to go off-topic. This isn't a specific problem of the meetings but with any discussion from emails to chat.
My experience taught me that in a chat if you sent 2 messages (not 2 questions in the same message) people will reply to just one, maybe the first one or the last one.

There are 2 kind of discussions productive or useless and as maintainer or community manager is important to get the maximum to save your time, because communication is a time-consuming task.
How you can recognize Useless discussions? Check this list:
Mte90 marked this conversation as resolved.
Show resolved Hide resolved

* When are used a lot of hyperbole
* There is a lot of repetition
* There are tons of new ideas without any clear proposal
* Noise detection
* Comments from inactive people can be very dangerous:
* They are not aligned with the project status
* They are just lurking so don't have any experience of the community life of the project
* Can act as troll because you [just changed their workflow](https://xkcd.com/1172/)
* Doers are usually silent and is important to reach them

This are basic rules but you need to give a different weight to the your evaluation based also on the previous section. Every volunteer is important but some can have more relevance on the decisions just because they are alive and participating in what you are doing.
Mte90 marked this conversation as resolved.
Show resolved Hide resolved

## How to manage a meeting

Meetings can be boring so it’s important to have an agenda with strict times to be sure not to forget something or keep at pace with the plan itself.
During the meeting take few minutes to talk about the purpose of the meeting (also on the invitation card) and the workflow of the meeting.
Preparing the attendees it’s important to improve the quality of the meeting and to be proud of what was done during this time, so it is not going to be a boring meeting.
The agenda of the meeting is important, and also the titles of the various moments that help to remember the topics.
During the meeting take few minutes to talk about the purpose of the meeting (also on the invitation email/communication) and the workflow of the meeting.
Preparing the attendees it’s important to improve the quality of the meeting itself and to be proud of what was done during this time, so it is not going to be a boring meeting.
The agenda of the meeting is important, and also the titles of the various moments that help to remember the topics (a nice tip can be to add a prefix on your communication like "Website localization - First steps" or "Event organization 2020 - Venue").
The order too, put on top the topics with more priority, avoid jargon during the meeting and don’t forget to leave time to reply to questions and also the last words to the attendees.
Don’t forget that someone needs to get notes of the meetings for the people that missed it and to write a report.
Don’t forget that someone needs to get notes of the meetings for the people that missed it and to write a report, also define a specific amount of time to avoid off topic discussions and be on track.
At the same time can be important to have a moment during the meeting for open floor questions but just define in it on your agenda so everyone can plan what to ask in that slot.

### When

Expand Down Expand Up @@ -87,6 +121,8 @@ In every communication it’s better to follow the rule of 7 communications.
When you have no idea where to start with a communication the simple way is writing a list with every point, prioritize and only then writing your message.
Because you are part of an open project, you need to do open questions to the people too. These open questions are not for better clarification but let the others explain what they mean, because a lot of things are not specifically communicated with words for example.

There are different tasks about communication and for a community managers is important to keep a public communication on high quality standards, to save time but also to be more transparent, create an history, create a workflow and improve the reputation of your project. There are 2 ways for that: gather the common questions of newcomers of the community and create some sort of documentation or keep a period report of what is happening/ed in a project. Those are simple ways to improve the quality of communication in your project that on long term can have a lot of benefits.

## How to talk with people

* Don’t criticize, condemn, nor recriminate
Expand Down Expand Up @@ -158,7 +194,7 @@ Every culture has differences but there are few rules that apply for everyone.
* Telegram: is the best choice because has bots, link previews, moderation tools, links/media recap, client desktop/mobile and is open source (there are open source addicts that don’t want to use proprietary software)
* Hangouts/Hangouts Meet: it’s useful online for video meetings but remember it allows a maximum of 10 people on the free plan
* IRC: it’s the classic solution on open source to chat but for the new generation and for the mobile world it’s too difficult to configure and understand
* Slack-like: it is a IRC 2.0 that may improve the organization in groups of people and usually a bridge between IRC and Telegram can improve the migration. Slack have problems on onboarding new people because the free plan is very limited to 10000 messages (also on private groups and is very easy to reach that). It is not open source and there are many alternatives without that problem. This tools, like telegram have integrations such as bots.
* Matrix/Slack-like: it is a IRC 2.0 that may improve the organization in groups of people and usually a bridge between IRC and Telegram can improve the migration. Slack have problems on onboarding new people because the free plan is very limited to 10000 messages (also on private groups and is very easy to reach that). It is not open source and there are many alternatives without that problem. This tools, like telegram have integrations such as bots.
* Mailing list: like irc they can be annoying but used for the marketing part they work very well
* Discourse or forum: with a modern interface they work very well with notification and other stuff
* Collaborative Documents: they are important to work together on a plan. Etherpad in the open source world are the best, but they are very poor in features like: comments or suggest changes, notification and classic features of a text editor. Usually Google Docs are used, covering all those features but the urls are very complicated and some people don’t like that because they are not open source.
37 changes: 20 additions & 17 deletions manuscript/chapter1-bio.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ So to explain what I am doing or what I am learning to others, because what's us

For me internet was the first way to meet people like me (I still love forums) to work on my projects or discuss.
In 2009 after the school I had to choose what to do with my life. A question that all the young people often face, my choice was very simple: work with computers (without math).
Something clearly impossible at that time, it was a like an elitarian job, because there was this idea that to be good at computer you needed to be good at math remembering formulas or calculating glogarithms.
Something clearly impossible at that time, it was a like an elitarian job, because there was this idea that to be good at computer you needed to be good at math remembering formulas or calculating algorithms.

I chose to go to L'Aquila and take a university course at the Academy of Fine Arts on Web Design. After all I liked to work with websites, so I was easily getting the piece of paper (my parents were longing for).
For non-italians, 2009 was the year of the big earthquake with 309 dead and that course never started, so I took a sabbatical year working at the family's shop in the morning and doing a work stage in an IT company in the afternoon for 6 months.
Expand All @@ -62,7 +62,7 @@ After 4 years we are still doing stuff but we are only two people now. With a lo
I was developing in PHP because when I moved to Linux this was my home, with the discovery of Python and I made my first UI projects with the Qt framework. I was experimenting with doing the same things on Linux as I was doing with Windows, even with custom software.
It's basically what people do when migrating from the first to the latter, in my case I felt like Indiana Jones, without boundaries, and it was intriguing.

At 18 years (2008) I bought my domain `mte90.net`, after some time I opted for using a CMS, and since data bases were overrated I decided to build my site with a flat CMS.
At 18 years (2008) I bought my domain `mte90.net`, after some time I opted for using a CMS, and since databases were overrated I decided to build my site with a flat CMS.
So I started using an Italian Open Source CMS and extending it creating plugins and also doing a fork to the project to add more stuff.
I built a tiny community around it, a mini build system and at the time I didn't know about git or other version control systems.
In 2012 I opted to use a real CMS that was following real coding standards (compared to the spaghetti code) to do more and better without starting from scratch.
Expand Down Expand Up @@ -103,19 +103,19 @@ I had an idea of how the browser and software work, their development cycle and
I also discovered what doesn't work at a higher level within IT companies, the distance they have to their users' needs (because they follow market needs instead).
I strengthened my language skills in the process.
Mozilla assigned funds to volunteers to organize or participate in events, when I joined I was one of the few experts of Firefox OS in Italy.
In short, I traveled all around Italy, visiting new places and meeting people, having the chance to better understand the needs and questions of the users of Mozilla products and of the Open Source ecosystem as a whole in general.
This traveling allowed me to build a group of friends that started to do the same, hosting demonstrations of Firefox OS, explaining how to develop for it, recruiting new people and finding new ways to engage them. Also we have improved and expanded Firefox OS Italian manual together.
In short, I travelled all around Italy, visiting new places and meeting people, having the chance to better understand the needs and questions of the users of Mozilla products and of the Open Source ecosystem as a whole in general.
This travelling allowed me to build a group of friends that started to do the same, hosting demonstrations of Firefox OS, explaining how to develop for it, recruiting new people and finding new ways to engage them. Also we have improved and expanded Firefox OS Italian manual together.

![The hard work of months for the Italian version of the Firefox OS development book](images/1/ffos-libro.jpg)

With the [death of Firefox OS](https://daniele.tech/2015/05/the-firefox-os-1-x2-x-problems/) I got a lot of experience in community building, mentoring, development and so on, and I kept traveling in the country also even if a little less than before.
With the [death of Firefox OS](https://daniele.tech/2015/05/the-firefox-os-1-x2-x-problems/) I got a lot of experience in community building, mentoring, development and so on, and I kept travelling in the country also even if a little less than before.
I was giving speeches about other technologies, like addons development, Firefox web tools for developers, how to join the community, privacy and why Mozilla was important.

These travels created an "aura" around me, I was (and still I am) called many nicknames like Mozilla-Man, Mr. Firefox, Mozilla and so on. People aren't creative with nicknames after all...
At the same time I started improving my English,and in 2015 I joined Mozilla Reps program, participating in activities and discussions online at international level.

I> Mozilla Reps program is an international program free for everyone meant to empower ones local Mozilla community (not only about Firefox but Mozilla per se or other projects like A-Frame as example).
I> It is a program with 280~ people from a lot of countries now (when I joined it was double that number), empowering volunteers to become better community managers, better project managers, join Mozilla discussions as NDA group, get funding for events and swag.
I> Mozilla Reps program is an international program free for everyone meant to empower local Mozilla communities (not only about Firefox but Mozilla per se or other projects like A-Frame as example).
I> It is a program with ~280 people from a lot of countries now (when I joined it was double that number), empowering volunteers to become better community managers, better project managers, join Mozilla discussions as NDA (Non-Disclosure Agreement) group, get funding for events and swag.

In the same period I attended my first international event the [FOSDEM 2015](https://daniele.tech/2015/02/fosdem-2015-the-report/), even with my messy English I was able to organize it with the help of 3 Italian friends.
Participating allowed me to meet new volunteers in person (also from Mozilla) and this helped me to meet new people (or recognize them from the nickname), slowly I understood that the Reps program was a way to help the community to do more and better.
Expand All @@ -138,15 +138,16 @@ An important lesson is in the working environment and human, there are reasons b

I want to close this section with links from my blog about a lot of experiences in Mozilla, I had always the habit to write a report after events or topics, and know they are a very valuable resource to understand the period and what was happening years after:

* [https://daniele.tech/2014/10/september-mozilla-marketplace-contributor-of-the-month-daniele-scasciafratte/](https://daniele.tech/2014/10/september-mozilla-marketplace-contributor-of-the-month-daniele-scasciafratte/)
* [https://daniele.tech/2015/05/the-firefox-os-1-x2-x-problems/](https://daniele.tech/2015/05/the-firefox-os-1-x2-x-problems/)
* [https://daniele.tech/2016/06/mozilla-all-hands-london-was-there/](https://daniele.tech/2016/06/mozilla-all-hands-london-was-there/)
* [https://daniele.tech/2016/06/confsl-2016-was-there/](https://daniele.tech/2016/06/confsl-2016-was-there/)
* [https://daniele.tech/2016/09/mozilla-tech-speaker-meetup-european-gathering-in-berlin/](https://daniele.tech/2016/09/mozilla-tech-speaker-meetup-european-gathering-in-berlin/)
* [https://daniele.tech/2016/09/clsxitaly-roma-2016-was-there/](https://daniele.tech/2016/09/clsxitaly-roma-2016-was-there/)
* [https://daniele.tech/2017/01/get-stats-of-your-browser-extension/](https://daniele.tech/2017/01/get-stats-of-your-browser-extension/)
* [https://daniele.tech/2017/09/why-developing-browser-extensions/](https://daniele.tech/2017/09/why-developing-browser-extensions/)
* [https://daniele.tech/2017/11/analisi-del-sondaggio-mozilla-su-iot/](https://daniele.tech/2017/11/analisi-del-sondaggio-mozilla-su-iot/) - Italian
* [September Mozilla Marketplace Contributor of the Month: Daniele Scasciafratte](https://daniele.tech/2014/10/september-mozilla-marketplace-contributor-of-the-month-daniele-scasciafratte/)
* [The Firefox OS 1.x/2.x Problems](https://daniele.tech/2015/05/the-firefox-os-1-x2-x-problems/)
* [Mozilla All Hands London – I was there](https://daniele.tech/2016/06/mozilla-all-hands-london-was-there/)
* [ConfSL 2016 – I was there](https://daniele.tech/2016/06/confsl-2016-was-there/)
* [Mozilla Tech Speaker Meetup & European Gathering in Berlin](https://daniele.tech/2016/09/mozilla-tech-speaker-meetup-european-gathering-in-berlin/)
* [CLSxItaly Roma 2016 – I was there](https://daniele.tech/2016/09/clsxitaly-roma-2016-was-there/)
* [ExtStoreStats – Get stats of your browser extension](https://daniele.tech/2017/01/get-stats-of-your-browser-extension/)
* [Why I am developing Browser Extensions](https://daniele.tech/2017/09/why-developing-browser-extensions/)
* [Analisi del sondaggio Mozilla su IoT per l’Italia](https://daniele.tech/2017/11/analisi-del-sondaggio-mozilla-su-iot/) - Italian
* [Firefox lost the browser war and what we can do?](https://daniele.tech/2020/02/firefox-lost-the-browser-war-and-what-we-can-do/)

![The monument with the names of 5000 Mozillians in front of the Mozilla's office in San Francisco](images/1/monumento.jpg)

Expand Down Expand Up @@ -190,7 +191,7 @@ A great idea that today has failed to explode as we thought, also because we are
I say it because in 2018 I became the president of the association and after a few years I can see the issues in a world that transform itself too much quickly.
Let's think a moment together, in 2019 the open source world is not as strange and dark as 5 or 10 years before.
The world is paying more and more attention to the opportunities of these technologies (except the Italian government in the various cities) but I see the big problem: to contribute.
This book was written because I see a lot of young people and newcomers that ask how to do something, how to start or how works. how it works. Because it is more important to be able to participate and contribute than to be mere users of the product for them.
This book was written because I see a lot of young people and newcomers that ask how to do something, how to start or how it works. Because it is more important to be able to participate and contribute than to be mere users of the product for them.

# Conclusion

Expand Down Expand Up @@ -231,3 +232,5 @@ X> * Where you see yourself in this story
X> * What is your biggest target (also non-realistic)
X> * What is the first step you want to do
X> * What you want to learn

There are also other FOSS story around with less photos but more clear learnings (maybe) like [this one](https://blog.burntsushi.net/foss/).