Stephen commented on my proposal that instead of storing all downloads on
the server, we should only cache recent ones and build the others on
request, because many archives are only downloaded once when they are
ported to a different archiver. Since this is in contradiction to the
suggestion
In my proposal I suggested using any of several asynchronous job queue
libraries, such as Celery or Huey. These all use redis as a back-end.
Because I have no experience with asynchronous job queues, I'm not sure if
this is too much baggage for our purposes. Maybe we just don't want the
extra
I'm already using the jobs infrastructure provided by the
django-extensions package:
http://django-extensions.readthedocs.org/en/latest/jobs_scheduling.html
Cool. I didn't know about this extension, but it looks like it does what we
need. So the background process would be its own file in the
Hey David, here are my thoughs on the challenges:
1) Determine which messages to include in the mbox.
An entire list archive is clearly one choice, but is there also
interest in generating mbox files for specific threads, list archieves
between specific dates, etc.?
Hmm, depending on the
Thanks for your feedback Aurelien.
we'll need something like a task queue and a daemon process or a cron job
In my proposal I suggested using any of several asynchronous job queue
libraries, such as Celery or Huey. These all use redis as a back-end.
Because I have no experience with
David Udelson writes:
Thanks for your feedback Aurelien.
we'll need something like a task queue and a daemon process or a cron job
In my proposal I suggested using any of several asynchronous job queue
libraries, such as Celery or Huey. [...]
So far, this is good discussion for
My proposal has been updated. I apologize if I breached mailing-list
ediquette, I'll get the hang of this eventually :)
On Wed, Mar 25, 2015 at 10:14 PM, Stephen J. Turnbull
turnb...@sk.tsukuba.ac.jp wrote:
David Udelson writes:
Thanks for your feedback Aurelien.
we'll need
David Udelson writes:
My proposal has been updated. I apologize if I breached mailing-list
ediquette, I'll get the hang of this eventually :)
No etiquette problem. Those are my personal views about effective use
of the mailing list and Melange, respectively. I suspect from past
experience
I'm interested in contributing to the Hyperkitty archiver. Specifically,
it looks like some requested features for Hyperkitty include rss syndication
for entire mailing lists/specific users/specific threads, and the ability
to view entire threads as plaintext and download that plaintext.
We
I have submitted a proposal on Google Melange. Any feedback I could get
about my project constraints would be great!
Thanks,
David
On Tue, Mar 24, 2015 at 8:23 AM, Aurelien Bompard aurel...@bompard.org
wrote:
I'm interested in contributing to the Hyperkitty archiver. Specifically,
it looks
Sent this email to Aurélien's personal email by mistake the first time
(sorry Aurélien!). I'll get used to the mailing list evenually
There's always been demand for a way to download a list archive as an
mbox file
This is a feature I am interested in pursuing. From a very (very) high
level,
On 2015-03-22 10:23 PM, David Udelson wrote:
I'm interested in contributing to the Hyperkitty archiver. Specifically, it
looks like some requested features for Hyperkitty include rss syndication
for entire mailing lists/specific users/specific threads, and the ability
to view entire threads as
Hello,
My name is David Udelson. I am a freshman Computer Science
undergraduate at Cornell University. I have 3 years of experience with
python under my belt, but I've never contributed to an open source project
because I've never known where to begin. I'm hoping GSoC will provide me
with
13 matches
Mail list logo
