Re: Ambassadors places in new Working Groups

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2013/10/27, Ankur Sinha <sanjay.ankur@xxxxxxxxx>:
> On Sun, 2013-10-27 at 12:27 +0100, Nobrakal wrote:
>> In my mind, Ambassadors are more near of users than developers or
>> marketing team. Ambassadors organize all the events, submit new
>> idea... It is really important to have at least an ambassador in WG
>
> I don't think Amabssdors must be part of the WGs, unless they also have
> a skill set relevant to the WG. For example, Tuan isn't just an
> ambassador. He works with servers and therefore brings certain knowledge
> that will be useful to the WG.

That great, for Tuan and Cwickert. But my problem is that neither
email was sent on the ambassadors list. And, as you say, they are
ambassadors "additional". We need real representant of Ambassadors (I
don't say Tuan ans Cwickert are bad ambassadors)
>
> Elected members of the WG are ones who will *lead* them. Ambassadors are
> more than welcome to keep tabs on these working groups and provide them
> with feedback when required, like the rest of the community.

Yes, but we need a mentor for this ambassador, to coordinate their
action in the WG.

> Ambassadors
> generally jump into action in the last stage of a release: when it's
> ready, and we need to spread information about it. We don't do much
> during rest of the release cycle, with tasks that *create* a release.
>
> As I understand it, this is the order of information flow:
>
> Development/WGs (Develop) -> Marketing/Docs team (Keep tabs + create
> collateral: flyers etc.) -> Ambassadors + and the community, in general
> (Spread the word) -> rest of the world.

It's for the first release. After, for your product, you need
feedback, and other suggestion, to best help them. The user is the
center of all contributors. So, your order become

Development/WGs (Develop) -> Marketing/Docs team (Keep tabs + create
>collateral: flyers etc.) -> Ambassadors + and the community, in general
 (Spread the word) -> rest of the world. -> User -> Development/WGs
(Develop)....

This last step require ambassadors.

>
> It's similar to what we have now, which is why I keep requesting folks
> that aren't developers to help out with marketing/docs, or at least to
> keep tabs on their tasks.

That very good. This is why you need ambassadors, for all steps in the
developpement.

> Users don't create software. They use it.
That the most important thing ! Softwares are make to users. If you
exclude user of your process, it's a big mistake

>Most users don't know or care
> at all about how software is created. In most cases, users are only
> involved during the first phase of software development, when
> requirements are being collected. The WGs already have their
> requirements figured out.

You forget the post-production. After a software, user have some other
idea of improvement.

> For example, what would you as a user contribute to the server (or
> another) working group?

For example, I'm a user. I want php on my server, but it isn't in the
"server" group on yum. I can tell developpers to add php in their
group.


2013/10/27, Frank Murphy <frankly3d@xxxxxxxxx>:
> On Sun, 27 Oct 2013 12:34:01 +0100
> Nobrakal <nobrakal@xxxxxxxxx> wrote:
>
>Then why do Ambassadors "not reply" to emails even from other
>Ambassadors, the perception I have been given is that Ambassadors
>should not be disturbed. Ankur (FranciscoD), could fill you in more
>on this *do not contact" aspect of *some* Ambassadors.

If some ambassadors do not their jobs, it's another problem. I speak
about the 'normal' ambassadors.
>
> It is also important to have them in freemedia,
> don't see that happening, too often.

Yes, you're right, but it's another problem. But, now, freemedia isn't
longer required. Live usb is very useful, on my mind.

Alexandre
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux