On Mon, Oct 28, 2013 at 2:06 PM, Simo Sorce <simo(a)redhat.com> wrote:
On Mon, 2013-10-28 at 08:55 -0400, Stephen Gallagher wrote:
> * Platform for deploying web applications with high-value frameworks.
> * Ruby on Rails
> * Django
> * Turbogears
> * Node.js
Are we going to do this via Software Collections ?
The main issue I see with these is that various apps requires at times,
conflicting versions of the same base framework/language.
I think it would make sense for the Base Design and
Environments/Stacks WGs to define how to install, build and package
the runtimes and the applications that use them (including the
conflicting/multiple versions issue), without focusing on a specific
use (e.g. treating web applications, GUI applications and CLI
applications equally), and for the Server WG to handle deploying the
web applications within the web server and managing deployed web
I think the main issue is the amount of packages we try to cram in
Would it be radical to suggest that "packages" should be invisible to
an admin that doesn't want to see them? "Enable the DNS server",
configure what it is serving, *product's magic here*, the DNS server
>  Ideally, we want a mid-level Microsoft admin to be able to
> Fedora without much learning curve.
For this you need wizards and (web) UIs, I am not sure how much in our
charter there is for developing additional software, Fedora usually is
about packaging stuff, mostly.
I strongly think Fedora needs to more actively develop missing
functionality, or cause the missing functionality to be developed.
"The Open Source community hasn't written it yet" is an excuse but not
a reason for the users to put up with the resulting lack of