Jessy,
Yes, there are plans (and activity) related to the presentation of list
archives within the django framework.
In fact, Aamir, one of our GSoC interns, is working on that very subject as his
project for the summer.
In keeping with the django philosophy of combining many special purpose
Are we making a design mistake?
The current design of the Postorius and Hyperkitty web interfaces to the
mailing list and its archives uses the fully qualified list submission email
address as a component of the URLs presented to the public.
Is this really a good idea? Just think of the
good to know, look forward to seeing it!
On Mon, Jun 11, 2012 at 6:21 AM, Richard Wackerbarth rich...@nfsnet.orgwrote:
Jessy,
Yes, there are plans (and activity) related to the presentation of list
archives within the django framework.
In fact, Aamir, one of our GSoC interns, is working on
On Mon, Jun 11, 2012 at 05:43:33AM -0500, Richard Wackerbarth wrote:
Are we making a design mistake?
The current design of the Postorius and Hyperkitty web interfaces to the
mailing list and its archives uses the fully qualified list submission email
address as a component of the URLs
Richard Wackerbarth writes:
The current design of the Postorius and Hyperkitty web interfaces
to the mailing list and its archives uses the fully qualified list
submission email address as a component of the URLs presented to
the public.
I fear that doing this will create an even
On Jun 11, 2012, at 05:43 AM, Richard Wackerbarth wrote:
I think that we should rethink this decision and follow a slug approach to
the identification of the mailing lists in URLs. Those who choose to do so
can use the fqdn as their slug. But others would be able to readily change
the mapping
Actually, the Django methodology would allow the website designer to choose any
URL that she wishes.
So, Postorius should be able to set a configuration parameter to any value that
the designer chooses and core would just be echoing it.
Richard
On Jun 11, 2012, at 11:28 AM, Barry Warsaw
