Hi Matthew & everybody,
On 04/01/2014 06:06 PM, Matthew Garrett wrote:
Rather than saying that Fedora-the-product should represent all of our
independent subcommunities, we could allow individual subcommunities to
define their own product definitions, driven by their own branding. For
example, KDE could define separate desktop (Plasma) and mobile (Plasma
Active) products without having to worry about them conflicting with any
other products.
I think that maybe the new model for the website that some of us have
been working on might support this. E.g., we were thinking of an
ultra-slim Fedora 'brochure' site where you could download Fedora and
then a separate site as a 'community hub' for contributors, where
everyone works together regardless of what product(s) or teams they
might be involved with.
The ultra-slim 'brochure' site could be one brochure per Fedora.next
'official' product and one per subcommunity product, or it could be one
brochure with the three 'official' products and one per subcommunity
product. The point here being, it's going to be a simple design and
implementation so maybe as part of developing it we could provide
templates so that any subcommunities wanting to spin off a product can
snag the template, open up some tickets to have the design team create
them custom artwork for it, and fill out the details pretty easily.
This is the recent blog post I did outlining the basic idea we had for
the new website:
http://blog.linuxgrrl.com/2014/04/01/a-proposal-for-fedoras-website-considering-fedora-next/
Does this make sense? Does it seem a workable model to support
subcommunities better? Are there specifics about how we'd go about
developing brochure site templates that would better support subcommunities?
~m
_______________________________________________
advisory-board mailing list
advisory-board@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/advisory-board
