Ethan, welcome back.
Aaron, I like your idea of a multi-pronged approach and am very willing
to focus on specific files or whatever portions that you or Ethan would
like me to.
Terri, I also like the idea of the "skin" approach and other UI systems
that I have developed for did use that appr
Aaron Crosman wrote:
> From my reading of the responses to my question I see two ways that
> people are thinking of proceeding, which I think might complement
> each other well.
I'm reading this thread with interest, as the problems of working with
the current templates are really why I'm on this
Let's see if python.org is ok with me now...
Barry Warsaw wrote:
> If there are folks who want to start working on a new web u/i, either
> to integrate a new templating system, or to prototype better content
> or usability, then in the short term the thing to do would be to
> branch Mailman
Developers and Admins,
It is understandable that some admins request a Mailman that works on
their RHEL3 or older. But please don't let that hold development back at
all. Admins really should appreciate that the developers look forward
and focus on creating a system that is state-of-the-art. Wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2007, at 1:04 PM, Aaron Crosman wrote:
>> From my reading of the responses to my question I see two ways that
> people are thinking of proceeding, which I think might complement each
> other well.
>
> First, there's the approach of fixing th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2007, at 11:47 AM, Ethan Fremen wrote:
> Having struggled mightily to find a way to improve templating while
> not
> moving to python 2.4 (at least), I have to confess I don't think
> there's
> a good way to get there.
That shouldn't be
Barry Warsaw wrote:
> If there are folks who want to start working on a new web u/i, either
> to integrate a new templating system, or to prototype better content
> or usability, then in the short term the thing to do would be to
> branch Mailman 2.1 and let you have at it. In order to get
>From my reading of the responses to my question I see two ways that
people are thinking of proceeding, which I think might complement each
other well.
First, there's the approach of fixing the current pages by moving the
style information out of the Python code and into a CSS file. Second,
there
On Sun, 2007-04-29 at 17:12 -0500, Jon Reese wrote:
> Unfortunately there are a number of package related versions that cannot
> be upgraded easily because the packagers have not brought the RPMs up to
> date with the current stable release of Mailman (2.1.9). They may have
> reasons for this,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 30, 2007, at 11:41 AM, Terri Oda wrote:
> Ideally, I think it should be possible to skin mailman just using
> CSS, so I'd say we should start there. And once that's done, maybe
> someone could sit down and try making a few different skins so p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 27, 2007, at 4:53 PM, Aaron Crosman wrote:
> That said, I'm not clear where this project stands. I've been
> reviewed
> the summary from last summer's SoC work, and while that's given me
> some
> idea of what was done, I don't have a good
11 matches
Mail list logo
