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

Re: Fedora Magazine RFR

On Tue, 2007-06-19 at 22:53 -0500, Mike McGrath wrote:
> Anand Capur wrote:
> >> So it sounds like the software you'd like to use have changed quite a
> >> bit in the progress of this thread.  Please update your RFR with a full
> >> list of exactly what packages you need to do this.
> >>
> >>     -Mike
> > eGroupware (which I will package for Fedora if needed).

What is eGroupware used for in the magazine?

> You'll need to get it into Fedora.
> >    * Web Server: Apache 2.2.4
> >    * PHP 5.2.2

We don't need Joomla or any other PHP CMS.  We are using Plone for CMS,
it can handle all of what the other ones can.  Bonus -- you benefit from
the Fedora knowledge and hacking on Plone, versus doing it all yourself.

> I don't mean to rain on your parade but this is a very lofty goal, I'd 
> recommend working with the docs team and see if you can get some more 
> support, http://fedoraproject.org/wiki/DocsProject/Magazine. 

Anand has general support for his idea, via f-marketing-l, but he is
definitely going a bit in his own direction.  This is not necessarily a
bad thing -- if he has the energy to grow the contributors and sustain
the momentum, we'll all learn a few things.

My recommendation is for Fedora Magazine to be a SIG operating within
the Fedora News Project.  Right now, FWN is the sole output of Fedora
News, but that doesn't have to be.  So, Fedora Magazine would be a peer
output effort.

IMHO, an effort needs at least SIG status before it should get precious
Infrastructure resources.  If we get to the point where Xen instances
can be handed out like Halloween candy, then that changes.  Right?

- Karsten
   Karsten Wade, 108 Editor       ^     Fedora Documentation Project 
 Sr. Developer Relations Mgr.     |  fedoraproject.org/wiki/DocsProject
   quaid.108.redhat.com           |          gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Attachment: signature.asc
Description: This is a digitally signed message part

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