On Tue, Jan 10, 2017, at 04:27 PM, Zoltan Hoppar wrote:
What I see here is a huge pile of informations - and we don't
handle
it the right way. We have a bunch of services that already providing
useful informations, and works well for particular part of our needs,
but altogether still missing the point. I think the ring concept what
our FPL has told, can be made if we integrate all the current critical
pieces, services into an two-way communication chain. IMHO endpoints
are our users, then groups, after it regions, and the biggest one is
the whole community - and to this chain need to build an strong infra
contribution/communication chain. Without all this - it's gonna be a
trouble. Right now, one of the blockers is that the smallest piece in
the chain can't find an entry point from it's desktop, and therefore
need to hop to page to page to get support, informations, and more if
you are an ambassador. If you are in other role, it's very similar,
just with other path. That is why we have outdated informations, and
we hunt each other to fill here and there.
The best way would be to create and handle events, is Fedocal, as
centerpiece, was a good idea for start, but won't help to generate
event pages, stats and informations to the participants, and to upper
infra levels (mktg, ambassadors, support, swag). I think, I believe
that here Pagure can help us, if the event can have linked
informations from other services - and this appears in a Pagure stored
static generated wiki/html page. If we know how can we extract
informations from Trac, Budget (
https://budget.fedoraproject.org/),
and from others - and dynamically generate/refresh content, I assume
we can kill a huge chunk of (outdated) wiki pages.
Otherwise, IMHO we still miss as comm platform the Hubs (it's coming),
and also similar option as FAS in (gnome) online accounts what is
would be able to link and manage from your desktop the user interests,
services, and mailinglists.
However, I think we are on a very, very promising road, that will
give
us a killer flexible infra, and contributors path.
So, given the tools we have in our toolbox today. Can we start to build
20% of this? Then we can add more as we go and learn what is working?
Even having something that is partially hand assembled could show how
the data flows together.
regards,
bex
Zoltan
2017-01-10 15:06 GMT+01:00 Gabriele Trombini
<g.trombini(a)gmail.com>:
> IMO is not really useful having event pages if we don't have
any idea
> on how to getting informations from them.
> Of course I agree with Bex in making them multitasking and usable for
> more than only one specific target.
> At the moment the benefit of having them is to work on historical
> events for planning people needed, budget expenses and report to get
> refund.
> I'd like to throw on the table more elements in a marketing
> perspective:
> 1) getting infos from events about how to route strategies (e.g.
> gather requests of swag and other gadgets)
> 2) getting infos about the release itself (which improvements people
> are asking)
> 3) getting infos about different target of people (e.g. developer,
> newbies, advanced users etc.)
> and so on.
> I think this kind of feedback is strictly on the shoulders of
our
> first lines 'cause they have the skills for doing that.
> At last, in this perspective I think we should improve the pages in
> the wiki (or elsewhere). The goal is that in the future we shall have
> a big database from which analyze data, checking information we need
> in several community tasks and strategies.
> My 2 cents.
> Thanks.
> Gabri
>
> --
> Gabri
>
> _______________________________________________
> ambassadors mailing list -- ambassadors(a)lists.fedoraproject.org
>> To unsubscribe send an email to ambassadors-
>> leave(a)lists.fedoraproject.org
>
--
PGP: 06853DF7
_________________________________________________
ambassadors mailing list -- ambassadors(a)lists.fedoraproject.org
To unsubscribe send an email to ambassadors-
leave(a)lists.fedoraproject.org