Thu 22 Aug 2013 5:15PM

Gathering Artwork, Communication, Websites and Marketing in one team

RJ Raphaël Jadot Public Seen by 266

Decision coming from a topic initiated in council mailing list

This proposal because the frontier between all these roles is thin and variable, and we're a small team now :) IMHO splitting in dedicated teams should be more spontaneous and flexible.

This vision doesn't mean there is no specific role or responsibility, nor that there will never be no subteam. Just that, as for QA, subteams will imho be created by need, when there will be enough people to make them :)


Poll Created Thu 22 Aug 2013 5:16PM

Gathering Closed Sun 25 Aug 2013 4:23PM

by Raphaël Jadot Tue 16 May 2017 5:38PM

OK for gathering, we need to find a name now

  • Defining roles that need to be filled (doc, translation, social media…).
  • Gather artwork, website (including moderation, webdev, doc, translation, publishing but not sysadmin), com, and marketing teams in a single team (or circle to use the naming of holacracy) with one mailing list. I'd name this team Synergya or workshop, or operatorium, but my fave name is oficina :)
  • Append two coordinators to this team.


Results Option % of points Voters
Agree 100.0% 5 RJ WS AB BR JAP
Abstain 0.0% 0  
Disagree 0.0% 0  
Block 0.0% 0  
Undecided 0% 7 J KL AK CC R TPG AV

5 of 12 people have voted (41%)


Raphaël Jadot
Thu 22 Aug 2013 5:17PM

I agree


João Azevedo Patrício
Fri 23 Aug 2013 9:14AM

I agree but with lot's of ????. So I vote on the general idea of building a "oficina"


Anurag Bhandari
Sat 24 Aug 2013 2:46AM

Yes, we can do better with a combined team, for now, than having small-small teams with little or no communication. And I like the idea of "roles" :)


Wayne Sallee
Sat 24 Aug 2013 5:32PM

I still think that the mailing list is a better place to discuss. :-)

Deduct went over defense without defeat. :-)

Wayne Sallee


Kate Lebedeff Thu 22 Aug 2013 5:57PM

So, we unite communications, artwork, translations and documentation teams, with for now 1 leader - Joao, more to join. Is this correct?


Raphaël Jadot Thu 22 Aug 2013 7:19PM

yes :) at least a deputy because this team is quite big


Raphaël Jadot Thu 22 Aug 2013 11:07PM

@joaoazevedopatricio1 I like the oficina word, but does it sound good in portuguese?


Anurag Bhandari Fri 23 Aug 2013 12:31AM

I thought it was about merging all MLs into one, and not about merging all teams into one.


Raphaël Jadot Fri 23 Aug 2013 8:30AM

@anuragbhandari In fact, i prefer to use the term "role", we need people dedicated such as, for example, cristina is dedicated to artwork. Subteams can exist, and are free to exist if many people start to feed the same role, and need coordination. Like I said in the global description, they should created in a more spontaneous and flexible way. (Like QA inside cooker)

We need some roles (communication, social media, marketing etc) but can't create teams where there is not people :)


Raphaël Jadot Fri 23 Aug 2013 8:31AM

Mageia also did the same: https://wiki.mageia.org/en/Atelier_team


João Azevedo Patrício Fri 23 Aug 2013 9:14AM

I agree with this. Already discuss this with @raphaeljadot. I have some issues with the namings. this is a kind of semi-autonomous teams concept applied from industrial works. For this we need to have a clear view of all, first the way it works, bottom top, horizontal, top bottom, etc.. The strategy for each area how is defined and by who, and finally how the roles are assigned. the fact is that we all are a kind of factotum, and we should be more organic, so this merge for me is obvious but we cannot call it teams. I guess we can find a good name (i don't like circles), and we can use the old artisan production model as theme (whiteout masters and apprentices :-)).


João Azevedo Patrício Fri 23 Aug 2013 9:15AM

@raphaeljadot for me Oficina sounds good, Oficina is the Portuguese word for workshop. It also makes sense. I don't know how it sound for a russian or english speaker.


João Azevedo Patrício Fri 23 Aug 2013 9:17AM

for me the natural organization will be as a big large "team", on that team should be defined roles first based on needs, then look at skills and see if there is any gap on the relation skills > needs. After that people naturally position themselves and council acts as a "manager" trying to fill the gaps.


João Azevedo Patrício Fri 23 Aug 2013 9:21AM

Regarding leadership. There should not be that kind of mentality in this, I prefer someone coordinating each team of needs. I'm actually responsible for this area in council, that means I have to draw and make the best effort to achieve and design the strategy for the area. I haven't done it yet, or I've been quite week doing it. So I suggest, that during this merge a brainstorming of the "oficina" takes place to identify the strategy flaws, etc... I would call those brainstorming not meetings but "tertúlias" and would keep it in PT for my monstrous EGO feeding. :-)


Raphaël Jadot Fri 23 Aug 2013 12:38PM

@joaoazevedopatricio1 yes this is the spirit i try to have, not a leadership but coordination


Anurag Bhandari Sat 24 Aug 2013 2:49AM

But I'm unsure on whether we can use the word "oficina." I don't even know how to pronounce it. For such a diverse and global community, we may want to come up with an easy to spell / pronounce Latin or English name (could be an invented name as well, using the rules of etymology). I will think about such a name. Until then, Wingardium Leviosa.


Kate Lebedeff Sat 24 Aug 2013 7:31PM

@anuragbhandari I agree about the name thing, probably something easier would be better. Also, which would give a clear a straight idea of what is it about:)


João Azevedo Patrício Sat 24 Aug 2013 8:30PM

@anuragbhandari @katelebedeff The translation of Oficina is workshop. Related to latim, Oficina comes from the latin word "officina" (another f added) :-).
It's a word that is similar and recognizable in lot's of languages. But like I said in a non "latin" world I don't know how people will accept it or it will sound.
The way to pronounce is dependes on the language hehehe :-)


Kate Lebedeff Sun 25 Aug 2013 5:34PM

@joaoazevedopatricio1 yeees, I understand, imo it would be good to have the subject of the workshop more clear - straight in the name. Just my 2 cents:)


João Azevedo Patrício Mon 26 Aug 2013 11:08AM

@katelebedeff For mu is quite of indifferent. It has to have a name that has the chance to build a identity. The fact is that the description and the documentation available is more important than the name at the beginning. In the end I'm in favor that the people that belong to the teams that are being merger in a bigger picture should suggest and choose.