[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#799287: Packaging dependencies for mailman3-hyperkitty



Le 26 mars 2016 04:57:34 GMT+01:00, Paul Wise <pabs@debian.org> a écrit :
On Fri, 2016-03-25 at 19:35 +0100, Pierre-Elliott Bécue wrote:

That's in progress, the only goal of this detection is to deactivate
_javascript_ dynamic load of threads. We're thinking about alternative
solutions.

I don't understand why you would deactivate _javascript_ dynamic load for
bots? Typically they don't support _javascript_ (except Google) and you
should have a fallback for people who turn off _javascript_ anyway.

I hope mailman3/HyperKitty web interfaces use progressive enhancement:

http://en.wikipedia.org/wiki/Progressive_enhancement

I understand your point, and I'll think about it, but my goal is to make
upstream remove obsolete dependencies. django-libravatar seems to be the
only project that bundles support for that, and it's not maintained, whereas
django-gravatar2 is still maintained.

I guess you are talking about this project, it hasn't seen any issues
filed so probably just works as-is without needing any changes?

https://github.com/fnp/django-libravatar

So, for now, I think that I'd rather have a first mailman3 suite in debian,
and then, think about how to make things better. :)

I see.

Can't tell exactly regarding _javascript_ question. Sorry.

But I'll forward your comments, thanks for taking the time to make them. :)
--
PEB
Reply to: