On Tue, Sep 4, 2012 at 5:01 PM, Barry Warsaw ba...@list.org wrote:
On Sep 02, 2012, at 02:23 PM, Ethan Fremen wrote:
I don't have rights to edit/comment on the 5-minute-guide page
I want to improve the wiki docs. Can I -
http://wiki.list.org/display/~mindlace - have permission to edit
http
, having a bunch of
lists/users/etc would be helpful in developing the UI further.
(for what its worth, I did search the mailman devs archive and look through
the docs before asking this)
Thanks,
~ethan fremen
___
Mailman-Developers mailing list
Mailman
On Tuesday, August 21, 2012, Terri Oda wrote:
Yeay! In addition to what Barry said (join Postorious!) I just want to
say I'm really excited to see you back. :)
Thanks, Terri! I hope I'll be more useful this time around.
More specifically, though, I think a good first step with Postorious
+Interface+Status page says that a
basic UI is being set up.
Is there a way I can jump in and help?
Thanks,
~ethan fremen
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman
A.M. Kuchling wrote:
I have an idea for a proposed conservative approach for 2.1:
* Add two mm_cfg settings: CSS_FILES and JS_FILES, while are lists
(alternatively, whitespace-separated strings):
CSS_FILES = ['/css/mailman.css', '/css/custom.css']
JS_FILES =
Ethan Fremen wrote:
For pages that are generated rather than hand-edited, I propose we use
this doctype as of 2.2:
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;
And with 3.0 I would like to see the following:
* All pages served
Barry Warsaw wrote:
Genshi has been mentioned a few times. My impression was that it
insists
on producing valid XML output, which is nice, but doesn't necessarily
play well with ideas like factorisable head/foot portions.
It doesn't; it has an HTML output mode. Yes, you should have a
A.M. Kuchling wrote:
On Sat, May 05, 2007 at 11:24:27AM -0400, Terri Oda wrote:
Have the CSS generated by a CGI (which could then use these variables
if they're available).
- extra processing for each web request
+ could lay groundwork to make it possible to change settings on a
per-list
Barry Warsaw wrote:
Of course, I think it /will/ make our lives harder in some ways. As
we've seen, folks like cPanel have their own forks that they modify,
and then their users come looking to us for support, which we can't
give them. Having more public branches out there will
Hi! I'm a spoiled young brat who used to have ambitions to be a graphic
designer, did a couple of underground 'zines right around when this
whole web thing started.
Anyway, so I got dragged kicking and screaming into the programming side
of things- astute googling would find some posts of me
A.M. Kuchling wrote:
Patch #1415956 from Bryan Carbonnell adds CSS for styling purposes and
changes the HTML to be valid XHTML1.0. It still needs some tidying
up, and it still uses tables for layout, but that patch takes us
halfway there.
For the moment, I can make at least IE7/firefox
Barry Warsaw wrote:
\
Related to the different levels of customizability, I'd say that it
should be easy for folks to change some color schemes and basic look
with just a passing understanding of CSS.
I agree with this, and think that a vast swath of customization needs
could be met with
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
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
14 matches
Mail list logo
