You can subscribe to this list here.
2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|
From: Brian S. J. <br...@ab...> - 2005-01-31 05:56:00
|
Hello folks, My normally nonexistant personal life interfered for the last few days, so I apologize for neglecting the mailing list. Right now there are a couple people here I likely haven't met, and some people who should be subscribed by now are not, so I'll work on nagging them about that to drum up a good crowd for discussing the project. Someone who hinted they might want to do publicity for this project is now nowhere to be found, so that needs work -- Other than the freshmeat entry and a little plugging at DU and in a /. thread, nothing has been done to spread word of this project to the community at large. I guess the next step there is basically posting notices to related projects like pdfinfo, word2x, wget, gocr, etc seeking more developers. We did get one more SourceForge developer yesterday off the USCountVotes programmer's list. I'll be happy to answer any general questions you guys have. In the meantime, as a reward for signing up to the list, you get some inside info... News as of yesterday was that USCountVotes decided that they would like to opensource not only bits of supporting code for their project, but the entire component which watches BOE websites and logs any changes found. I'd welcome suggestions if anyone knows of any programs based on libcurl or wget or LibWWW-Perl which were built with "audit mirroring," to coin a phrase, in mind. That is, aggressively keeping a mirror, ensuring thorough mirroring (e.g. occasionally ignoring robots rules), and timestamping and keeping old revisions of files. Some of the BOE websites are going to be tricky to mirror because they use .asp forms and don't have real hyperlinks to tie them together, plus we have to deal with dynamic pages that don't obey if-modified-since HTTP rules. Also, a staff change at USCountVotes has sort of left us out in the cold for a while as far as defining a standard for output of the parsers. Or we could view the situation as a "power vaccuum" and define a standard ourselves and the new USCountVotes hire will have to live with whatever we come up with. For other news keep an eye on our SourceForge news section: http://sourceforge.net/news/?group_id=129082 -- Brian |