Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Matthew Summers <quantumsummers@g.o>
Subject: Re: Reviving webapp-config
Date: Fri, 10 Jun 2011 10:38:45 -0500
On Fri, Jun 10, 2011 at 6:49 AM, Sebastian Pipping <sping@g.o> wrote:
> Questions:
>
>  - What does reviving mean in detail?
>     A re-write?  A somewhat compatible re-write?

I am not necessarily interested in a complete re-write unless its
really warranted due to support for new features. First things first,
webapp-config needs to have the open bugs addressed and current
functionality should be supported.

>     Getting back to maintaining the current code?

There is some good code in there, so I think at minimum some of that
will be maintained moving forward. Regardless, the current codebase
should be audited, bugs fixed, and a new design spec incorporating the
new features desired needs to be written in collaboration with various
stake holders.


>     Why did you choose how you did?

I do not understand this sentence, but will try to explain the choices
a bit. Having used webapp-config for 7 years or so, I had grown fond
of it for managing things like drupal (back in the day) and for
handling static media for my company projects. As time progressed, it
seemed reasonable to extend the functionality of w-c to do fancier
things like change tracking or byte-compiling python modules outside
of site-packages for multi-instance and potentially multi-versioned
deployments of the various pythonic webapps I manage. It seems
reasonable to roll this sort of functionality into the existing tool.
I am not intending to make this something specific to python webapps,
just to be clear, but include tools to handle webapps written in
ruby/rails, perl, etc.

Additionally, Gentoo's infra team uses w-c for a few things and its a
nice tool that mostly integrates well into cfengine (afaik). Whatever
the case with automation, it does make management tasks easier
(perhaps IMO).

Further, there are substantial applications, like Moodle, that would
benefit from a more robust deployment toolkit within Gentoo.

So, in general, from both a distribution and a professional
perspective its quite clear (at least to me), that this tool has an
important role in Gentoo and therefore needs to be revived.

>
>  - Have you spoken to Andreas Nüsslein who worked on a
>   re-write in context of an earlier GSoC?

I have not. I was unaware of this project until it was mentioned in
replies to this thread. I have started reading the code. Perhaps there
are some elements of Andreas' code we can incorporate into the w-c
codebase. I need to dig into the code far more than my cursory glance.

>
> Best,
>
>
>
>
> Sebastian
>
>

Good questions Sebastian, thanks.

Matthew W. Summers
Gentoo Foundation Inc.


Replies:
Re: Reviving webapp-config
-- Sebastian Pipping
References:
Reviving webapp-config
-- Matthew Summers
Re: Reviving webapp-config
-- Sebastian Pipping
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Reviving webapp-config
Next by thread:
Re: Reviving webapp-config
Previous by date:
Re: Re: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa: index.xml
Next by date:
Re: Re: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa: index.xml


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.