[Pydotorg-redesign] python.org - Time for a Technolgy Update?

[Steve Holden]

I am writing to this list, which appears to be largely dormant since
"The Great Reorganization" over two years ago now, because I have
mentioned the prospect of migrating some of the site's functionality to
Django a couple of times on the pydotorg list and had no takers. So I
wondered if anyone at all besides Fredrik Lund and me think it would be
a good idea.

I can understand that nobody might relish the task, but I would hope
that it could be done incrementally in such as way that the transition
would not need to be managed in the same "all or nothing" way that the
last one was.

Thoughts?

regards
Steve

[Jeff Rush]

Post by Steve Holden
I am writing to this list, which appears to be largely dormant since
"The Great Reorganization" over two years ago now, because I have
mentioned the prospect of migrating some of the site's functionality to
Django a couple of times on the pydotorg list and had no takers. So I
wondered if anyone at all besides Fredrik Lund and me think it would be
a good idea.
I can understand that nobody might relish the task, but I would hope
that it could be done incrementally in such as way that the transition
would not need to be managed in the same "all or nothing" way that the
last one was.

If it were Zope 3 I would be interested in helping, but I'm not a Django
developer, and I've developed the impression that Zope doesn't have a good
perception with many pydotorg folk, unfortunately.

In general, dynamic websites don't seem desirable by many on pydotorg, and
although I've heard the arguments of non-endorsement (of a single framework),
stability and complexity, (a) there are still things dynamic engines can do
that static content cannot, and (b) it would strengthen Python's standing as a
serious web development language if it were showcased with python.org, IMHO.

-Jeff

[martin]

Post by Jeff Rush

Post by Steve Holden
I am writing to this list, which appears to be largely dormant
since "The Great Reorganization" over two years ago now, because I
have mentioned the prospect of migrating some of the site's
functionality to Django a couple of times on the pydotorg list and
had no takers. So I wondered if anyone at all besides Fredrik Lund
and me think it would be a good idea.

+1 for a good idea. +0 for Django.
I think different pieces will have different requirements that may not
all be met by Django though using a single framework is probably
better than using multiple frameworks.
Which parts of the site could benefit? Jobs, news, releases, maybe.

Post by Jeff Rush

Post by Steve Holden
I can understand that nobody might relish the task, but I would
hope that it could be done incrementally in such as way that the
transition would not need to be managed in the same "all or
nothing" way that the last one was.

If it were Zope 3 I would be interested in helping, but I'm not a
Django developer, and I've developed the impression that Zope doesn't
have a good perception with many pydotorg folk, unfortunately.
In general, dynamic websites don't seem desirable by many on pydotorg,
and although I've heard the arguments of non-endorsement (of a single
framework), stability and complexity, (a) there are still things
dynamic engines can do that static content cannot, and (b) it would
strengthen Python's standing as a serious web development language if
it were showcased with python.org, IMHO.

+1 for a Python showcase.

//M

[Aahz]

Post by Steve Holden
I am writing to this list, which appears to be largely dormant since
"The Great Reorganization" over two years ago now, because I have
mentioned the prospect of migrating some of the site's functionality to
Django a couple of times on the pydotorg list and had no takers. So I
wondered if anyone at all besides Fredrik Lund and me think it would be
a good idea.
I can understand that nobody might relish the task, but I would hope
that it could be done incrementally in such as way that the transition
would not need to be managed in the same "all or nothing" way that the
last one was.
Thoughts?

Right now, the active discussion in this area is moving the jobs page to
a tracker so that the page itself can be auto-generated. My thought is
that we should finish that first before any other discussion of website
technology to avoid distractions.

I'm not intrinsically objecting to your proposal, but I do think that
because python.org is not a particularly dynamic site, we do want to
make sure that we can generate a static site for efficient serving. (We
already have regular problems with the machine bogging down with the
existing dynamic code in PyPI.)

[Richard Jones]

Post by Aahz
I'm not intrinsically objecting to your proposal, but I do think that
because python.org is not a particularly dynamic site

I believe Fredrik's implementation produced a static site, but allowed
management of the contents through-the-web.

I'm +1 on this.


Richard

[Richard Jones]

Post by Steve Holden
I am writing to this list, which appears to be largely dormant since
"The Great Reorganization" over two years ago now, because I have
mentioned the prospect of migrating some of the site's functionality to
Django a couple of times on the pydotorg list and had no takers. So I
wondered if anyone at all besides Fredrik Lund and me think it would be
a good idea.

Just so we're clear, here's Fredrik's ideas on this:

http://www.google.com/search?q=pydotorg+django

:)


Richard