I recall several Fedora contributors mailed
different RH people repeatedly but didn't receive a reply.
This is one reason, why we wanted to have Fedora Project being able to
handle this without a Red Hat employee involved.
What kind of tool are you thinking about? IMO we need a work flow
not a tool. Of course everything should be documented in the wiki so it
is transparent to everybody.
That is why I asked for a process, describing the workflow.
> How can we make it fair for everyone?
We never can. :( Some people want more KDE, others Xfce or LDXE. Some
think i686 is important, others advocate x86_64. So we cannot order what
we want but what the users request.
The question from my side was not "Can we make it fair for everyone?".
It was "_HOW_ can we make it fair for everyone?".
If you suggest, to follow the statistical data and use it as a base
data for a media production, then I think it would be a great start.
As a starting point I suggest to look at the torrent statistics at
The page gives nice information about what our users prefer.
If we count in usage statistics, then we have to mind the
HTTP/FTP/RSYNC servers and mirrors usage as well.
So we have a real 100% overview of how many ISOs of which kind have
I suggest the following work flow:
1. One person is in charge of media production. While he is not
responsible for any decisions, he has to coordinate all the
different parties involved e.g. ambassadors, design team and the
media company. Let's call him the media wrangler for now.
Currently the wrangler would be you (sspreitzer), but we could
also have a new wrangler for each release if it turns out to be
too exhausting for a single person.
I think this would be a great start.
2. At time of the alpha release the ambassadors decide about the
general direction, e.g. do we want spins media. This should be
done in a regular IRC meeting. For the 13 release cycle this
means we are already late and have to hurry up.
Why must this be in the alpha state? The ISOs are released on the
release date. And the media wrangler can order the media company for
production on the date the ISOs are released.
3. Based on the decision of the ambassadors the media wrangler
works out a detailed plan. This includes things like i686 vs.
i86_64 or the quantity of the different spins (if the
ambassadors decided to do any).
I think the media wrangler must propose an order proposal to the
ambassadors. And the ambassadors vote on whether to use this as an
order or vote against and countersuggest a new order version.
4. At this point the wrangler already knows which media is going
be produced, so he can already file a ticket at the design team
5. In the next meeting the ambassadors ratify the suggestion
by the media wrangler. This should be done by the time of the
beta release latest.
See point 3.
6. The wrangler takes care that everything is produced as
by the ambassadors. He informs them about the progress or the
difficulties in the regular IRC meetings.
You think this will work? Is it to complicated? What do you guys think?
Complicated? It is just work. It is easy. But someone has to do it.
Mit freundlichen Grüßen / with kind regards,
Sascha Thomas Spreitzer
Warum mache ich überhaupt dieses ganze OpenSource Zeugs?
Lesen Sie hier, warum;