[Mageia-marketing] It's time to think about Mageia 2

[Romain d'Alverny]

Hi Marcello,

On Mon, Jun 13, 2011 at 15:24, Marcello Anni <marcello.anni at alice.it> wrote:
> so what are the goals of the brainstorming session if no one is forced to work
> on them?

First, let's make sure we agree on what brainstorming is about:
http://en.wikipedia.org/wiki/Brainstorming#Osborn.27s_method

>From that can emerge good, actionable things, to discuss/spec further
and that enough people can commit to and produce. Unless this last
condition is met, a track/idea won't result in anything; that's part
of the game.

> can we have at least a sort of promise of developers who want to
> listen to the marketing key points we chose to improve the distro?

If you can't convince them of the relevance and benefits of your idea,
you will either have nothing at all, or something that is not properly
done (and don't expect things to be done in one single row).

> if we chose as a target "newbies" and we think they do need a short guide shortly
> after the installation, but no one will implement (as it was for mandriva),

Why don't you start to build it and advocate it in a small circle to
build it further and submit it then?

> what is our role other than giving proposals to others and preparing release notes?

Already answered in my previous mail, but apparently, you don't
understand that in a volunteer project, what gets done are things that
drive enough people to commit their time to it. Getting an
idea/concept approved/supported by the Council is a minimal step to go
through, but is not even mandatory. Getting supported/executed by
people that understand and want this thing done is an obviously
required step: that's kind of a first reality check.

> this is not a marketing team, you're wrong. this is a "comunication team",
> that is completely different

Communicating/discussing ideas is a good thing to master before
thinking/designing through new ones, no?

So, both are closely working together (hence the mar'comm' team). As
for marketing per se, it should grow through the whole project, and
the most important task of the marketing team is maybe to
advocate/educate this through all other teams (as is the role of every
other team to spread its own particular bits around).

> my ideas are on dev specs since years but they've never been implemented.
> so, why have i to lost my time proposing stuff that no one will listen to it?

Ideas and proposals are nothing without action (which presupose
agreement and understanding). It's good to have ideas. But don't blame
others for not succeeding (yet) in transforming them into reality
(don't blame you either, just try different or harder).

> there should be a respective trust among marketing- team /dev-team
> unless the project future can be summarize in a word:
> ABANDONED.

If you don't take the time to know people, their motivations, to work
with them, to advocate, discuss, contradict, deconstruct, re-build
your views, to say no sometimes, to experiment, you won't cross the
bridge going from your wishes to reality.

Trusting you is not enough a reason to do what you say, or dismiss my
own priorities regarding a limited resource (time); that's as valid in
a volunteer context as in a corporate one (only, few people will admit
it before it's too late).

So the best you can do is: take your time, focus on one thing you want
to do, build it - and if you need someone to help you, take the time
to find this person and explain why it's important to build it.

Just don't expect anyone to follow what you say just because you are
this or that (age, position, title, achievements, whatever).

Cheers!

Romain