Re: [Chicken-users] Save the Gazette!
On 02/28/11 14:36, Alaric Snell-Pym wrote: > So far, I've written my omelette recipe into SVN; and tools are > gathering in the gazette-tools egg and on the wiki page at > http://wiki.call-cc.org/gazette - hopefully this weekend I'll get a > chance to integrate and test what we have, and we may even get our first > gazette out of it! I've just taken a look at Felix's work in the gazette-tools egg, and added in Andy Bennett's script to parse mailing list archives. I've generalised the users.lst mechanism a little to make it easy to map from real names to wiki links, and modified Andy's script to do that for email author names - and the results are awesome! I'll look into Andy's shellery to parse the git logs next - in the meantime, I encourage interested parties to have a play: chicken-install -s gazette-tools generate-eggs-history generate-list-history ...and laud Andy and Felix for their good work so far! ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On 02/28/11 14:10, Christian Kellermann wrote: >> The Gazette is reaching that point, and I want to save it. > > After all the wonderful responses to this thread and the awesome > amount of work that it has triggered. I wondered who is working on > a new issue now? > > This feels like people that have gathered around a collapsing person > for help and then everyone goes back to work because someone said > he has called an ambulance... > > The gazette is still there, waiting... Hee hee, don't worry; I've just been a bit busy with business travel and the new babe. So far, I've written my omelette recipe into SVN; and tools are gathering in the gazette-tools egg and on the wiki page at http://wiki.call-cc.org/gazette - hopefully this weekend I'll get a chance to integrate and test what we have, and we may even get our first gazette out of it! > > P.S.: This is not a I-want-to-annoy-you but a > I-want-to-get-back-in-the-loop post... > I'm glad to hear it ;-) Watch that wiki page and that egg in SVN, they're the rallying points; anything good that comes to me in email, gets pushed in those directions when I get a chance. ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
* Alaric Snell-Pym [110216 10:41]: > > When a community agrees it'd be cool to do something on a regular basis, > to begin with, there's a lot of enthusiasm and volunteering, so things > go well. > > However, a crucial point comes at which producing that thing starts to > become a chore, no matter how popular the product is. At this point, if > measures are not put into place to make it continue, it dies out. > > The Gazette is reaching that point, and I want to save it. After all the wonderful responses to this thread and the awesome amount of work that it has triggered. I wondered who is working on a new issue now? This feels like people that have gathered around a collapsing person for help and then everyone goes back to work because someone said he has called an ambulance... The gazette is still there, waiting... Kind regards, Christian P.S.: This is not a I-want-to-annoy-you but a I-want-to-get-back-in-the-loop post... ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On Thu, 17 Feb 2011 21:16:43 +0100 (CET) Felix wrote: > From: Mario Domenech Goulart > Subject: Re: [Chicken-users] Save the Gazette! > Date: Thu, 17 Feb 2011 15:10:32 -0500 > >> On Thu, 17 Feb 2011 21:09:01 +0100 (CET) Felix >> wrote: >> >>> BTW, perhaps we should make some room in the egg repo for this >>> work. >> >> Maybe under the gazette dir? > > Why not make it an egg? For easy installation, which lowers > the barrier for new editors. Ah, of course! Somehow I haven't thought about that. Sorry. :-) Best wishes. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On 02/17/11 14:33, Alex Shinn wrote: > Or replace every use of sed and awk with perl, which > is consistent across all platforms and scales better. However, as I think most of the people likely to run this code will have chicken installed and know Scheme, why not do it in Chicken? I believe somebody even wrote a decent regex implementation for it ;-) ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
From: Mario Domenech Goulart Subject: Re: [Chicken-users] Save the Gazette! Date: Thu, 17 Feb 2011 15:10:32 -0500 > On Thu, 17 Feb 2011 21:09:01 +0100 (CET) Felix > wrote: > >> BTW, perhaps we should make some room in the egg repo for this >> work. > > Maybe under the gazette dir? > Why not make it an egg? For easy installation, which lowers the barrier for new editors. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On Thu, 17 Feb 2011 21:09:01 +0100 (CET) Felix wrote: > BTW, perhaps we should make some room in the egg repo for this > work. Maybe under the gazette dir? > If nobody objects, I can do the svn log parsing. Great! Best wishes. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
BTW, perhaps we should make some room in the egg repo for this work. If nobody objects, I can do the svn log parsing. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
From: Andy Bennett Subject: Re: [Chicken-users] Save the Gazette! Date: Thu, 17 Feb 2011 16:32:44 + Whoa. Thanks, Andy! cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
* Andy Bennett [110217 17:36]: > Hi, > > > Super special bonus point: > > > > 5) Write a script that, given a date range, parses the mailing list > > archive into wiki markup for a list of links to the posts in the > > archive, along with links to the user's pages as per (4), grouped by thread. > > The attached script will process the web-based list archives > (http://lists.nongnu.org/archive/html/chicken-users/ ) for the last 8 > days worth of messages. > > It will group them by thread, sort them with the most active threads at > the top and then provide links to the individual messages, grouped by > author. > > It does not link to the users' pages. Very nicely done! I love it! Christian ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
Hi, > Super special bonus point: > > 5) Write a script that, given a date range, parses the mailing list > archive into wiki markup for a list of links to the posts in the > archive, along with links to the user's pages as per (4), grouped by thread. The attached script will process the web-based list archives (http://lists.nongnu.org/archive/html/chicken-users/ ) for the last 8 days worth of messages. It will group them by thread, sort them with the most active threads at the top and then provide links to the individual messages, grouped by author. It does not link to the users' pages. A sample output is below: - * Using a macro definition within a explicit renaming macro.(4 messages) ** Peter Bex *** [[http://lists.nongnu.org/archive/html/chicken-users/2011-02/msg00042.html|2011/02/11]] ** Patrick Li *** [[http://lists.nongnu.org/archive/html/chicken-users/2011-02/msg00041.html|2011/02/11]] [[http://lists.nongnu.org/archive/html/chicken-users/2011-02/msg00049.html|2011/02/12]] ** Felix *** [[http://lists.nongnu.org/archive/html/chicken-users/2011-02/msg00047.html|2011/02/12]] - Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF (use http-client html-parser sxpath srfi-69 srfi-19) (define base-url "http://lists.nongnu.org/archive/html/chicken-users/";) ; Fetch the mail archive's index (define tree (with-input-from-request base-url #f html->sxml)) (define month-list ((sxpath `(// li)) tree)) ; The last week might span both this month and last month ;(define interesting-months `(,(car month-list) ,(cadr month-list))) (define interesting-months `(,(car month-list) ,(cadr month-list) )) ; Fetch the thread listings for the interesting-months (define (get-thread-path snippet) (cadadr ((sxpath `(// a @ href)) snippet))) ; Filter the HTML so that we only have the thread listings. Then convert it to SXML (define thread-trees (map (lambda (thread-path) (with-input-from-string (;apply string-intersperse (with-input-from-request (string-append base-url thread-path) #f (lambda () (let ((flag #f)) (map (lambda (line) (cond ((string-match "]*>" line) (begin (set! flag (not flag)) line)) (flag line) (else "")) ;(string-substitute "]*>" "" line) ;(string-substitute "(]*>)|()" "" line) ) (read-lines)) ) ))) html->sxml)) (map get-thread-path interesting-months))) ; Canonicalise the subject for each message and generate a list of (subject, author, date, link)s (define messages ((sxpath `(// li)) thread-trees)) (define message-list (map (lambda (message) (if (> (length message) 4) (let ((link (car ((sxpath `(// a @ href *text*)) (second message (subject (string-substitute "[ \t]+" " " (string-substitute (string-append "(Re: )?" (regexp-escape "[Chicken-users] ") "(Re: )?") "" (car ((sxpath `(// *text*)) (second message 'all )) (author (second (fourth message))) (date (second (sixth message `(,subject ,author ,date ,link) ) '() )) messages)) ; Filter out everything except messages from the last week (define (sent-this-week? date-string) (let ((date (scan-date date-string "~Y~m~d")) (last-week (date-subtract-duration (current-date) (make-duration #:days 8 (if (>= (date-compare date last-week) 0) #t #f))) (define filtered-message-list (map (lambda (message) (if (= (length message) 4) (if (sent-this-week? (third message)) message '()) '())) message-list)) ; Regroup the filtered-message-list by subject then author (define message-hash (fold (lambda (msg summary) (if (not (eq? msg '())) (begin (hash-table-update! (second summary) (first msg) (lambda (identity) (hash-table-update! identity (car (cdr msg)) (lambda (identity) (append identity `(,(cddr msg (lambda () '()) ) identity) (lambda () (make-hash-table)) ) (hash-table-update! (first summary) (first msg) (lambda (identity) (+ identity 1)) (lambda () 0)) )) summary ) `(,(make-hash-table) ,(make-hash-table)) filtered-message-list)) ; Render a wikified list of threads and links to messages (define url-regex (regexp "()/(..)/..")) (map (lambda (subj) ( (lambda (subj value) (format #t "* ~A(~A messages)" subj (hash-table-ref (first message-hash) subj)) (newline) (hash-table-walk value (lambda (key value) (format #t "** ~A" key ) (newline) (format #t "*** ") (map (lambda (value) (format #t "[[~A~A/~A|~A]] " base-url (string-substitute url-regex "\\1-\\2" (first value)) (second value) (first value))
Re: [Chicken-users] Save the Gazette!
On Thu, Feb 17, 2011 at 10:51 PM, John Cowan wrote: > Andy Bennett scripsit: > >> Strange! The first part of the first sed is supposed to remove the '*' >> that indicates the currently checked out branch. > > The meaning of the regex /^*/ is implementation-dependent: it can be > read as "remove any number of hats, including zero" or "remove a star at > the beginning of the line". It's safer to disambiguate these as /\^*/ > and /^\*/ respectively. Or replace every use of sed and awk with perl, which is consistent across all platforms and scales better. -- Alex ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
Andy Bennett scripsit: > Strange! The first part of the first sed is supposed to remove the '*' > that indicates the currently checked out branch. The meaning of the regex /^*/ is implementation-dependent: it can be read as "remove any number of hats, including zero" or "remove a star at the beginning of the line". It's safer to disambiguate these as /\^*/ and /^\*/ respectively. -- "Well, I'm back." --SamJohn Cowan ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
Alaric Snell-Pym wrote: > On 02/16/11 15:04, Andy Bennett wrote: > >> This bash command, executed inside a git repo, should do the trick: >> >> - >> for b in `git branch -a --no-color | sed -e 's/^*//' -e >> 's/^\s*\(\S*\).*/\1/'` ; do echo " * On `echo $b | sed -e >> 's#^remotes/##'`:"; git log --pretty=format:' * (%h): %s (%an, %ar)' >> --since="1 week ago" $b; echo ""; done; >> - >> >> It's a one-liner. >> > > That's a good start! Perfect! It doesn't seem to *do* anything for me > (the first sed seems to turn the output of git branch into just as many > blank lines) but, ah, we can work on such details ;-) Strange! The first part of the first sed is supposed to remove the '*' that indicates the currently checked out branch. Here's what my 'git branch' command does: - $ git branch -a --no-color * master old pp remotes/origin/HEAD -> origin/master - Here's a snippet from my ~/.gitconfig - [color] diff = auto status = auto branch = auto - The second part of the first sed is supposed to remove those '-> origin/master' bits from the remote branches. I have just tested with NetBSD's sed and the 2nd part seems to cause everything to turn blank... It seems to be having trouble with the \S character class and the match reference. Changing this argument to -e 's/-> .*//' produces a correct result. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF signature.asc Description: OpenPGP digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
>
> Agreed!
Excellent!
>
> I've outlined what I think would be good; of course, partial
> implementations ("I did X but Y is too hard") are a step in the right
> direction, and somebody else might do Y later, too :-) Every little helps!
Could you, once again, list the necessary parts and put this list into
the wiki?
cheers,
felix
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On 02/16/11 15:04, Andy Bennett wrote: > This bash command, executed inside a git repo, should do the trick: > > - > for b in `git branch -a --no-color | sed -e 's/^*//' -e > 's/^\s*\(\S*\).*/\1/'` ; do echo " * On `echo $b | sed -e > 's#^remotes/##'`:"; git log --pretty=format:' * (%h): %s (%an, %ar)' > --since="1 week ago" $b; echo ""; done; > - > > It's a one-liner. > That's a good start! Perfect! It doesn't seem to *do* anything for me (the first sed seems to turn the output of git branch into just as many blank lines) but, ah, we can work on such details ;-) > > You might get commits appearing in more than one place if the branches > overlap. > That's fine, the human can easily tidy up such niggles. ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On 02/16/11 14:20, Felix wrote:
> ... and I want a pony. :-)
What colour?
> It is never the question of whether some well-crafted, time-saving
> tool is useful or not, that's obvious. It's always the question of who
> does it and when. So instead of discussing the technical details, I
> propose to discuss when we will get together and fix this once and for
> all, or try to find someone who coordinates such an effort. I'm sure a
> bunch of chickenistas will be willing to write some part of the whole
> thing (I certainly am). It would be good to identify (in a concise and
> not too specific manner) the different tools (or parts of a more
> general tool) that are needed. Post them here, and I will pick out
> something that I'd like to do. Others will join, hopefully. And you
> will take care of project management. Agreed?
Agreed!
I've outlined what I think would be good; of course, partial
implementations ("I did X but Y is too hard") are a step in the right
direction, and somebody else might do Y later, too :-) Every little helps!
ABS
--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
Hi, > 3) A script that, when run in a local git checkout, or maybe by talking > direct to the core git repo, lists all the commits in a specified time > period, grouped by branch. > For bonus points, the output of scripts (2) and (3) could be actual > markup for putting straight into the gazette, say as a bulleted list, > just requiring editing to remove useless commits and to add editorial > insight. This bash command, executed inside a git repo, should do the trick: - for b in `git branch -a --no-color | sed -e 's/^*//' -e 's/^\s*\(\S*\).*/\1/'` ; do echo " * On `echo $b | sed -e 's#^remotes/##'`:"; git log --pretty=format:' * (%h): %s (%an, %ar)' --since="1 week ago" $b; echo ""; done; - It's a one-liner. You might get commits appearing in more than one place if the branches overlap. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF signature.asc Description: OpenPGP digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
From: Alaric Snell-Pym Subject: Re: [Chicken-users] Save the Gazette! Date: Wed, 16 Feb 2011 13:34:18 + > Sort of. I know there's RSS and so on available, but it currently needs > much manual work to turn it into content. I'd like a script that pulls > that RSS feed and spits out (to current-output-port is fine, I can tie > them all together into a top-level script) something that I can really > easily turn into gazette text. Eg, all the hyperlinks are already > generated and marked up. Let me make up some examples: ... and I want a pony. :-) It is never the question of whether some well-crafted, time-saving tool is useful or not, that's obvious. It's always the question of who does it and when. So instead of discussing the technical details, I propose to discuss when we will get together and fix this once and for all, or try to find someone who coordinates such an effort. I'm sure a bunch of chickenistas will be willing to write some part of the whole thing (I certainly am). It would be good to identify (in a concise and not too specific manner) the different tools (or parts of a more general tool) that are needed. Post them here, and I will pick out something that I'd like to do. Others will join, hopefully. And you will take care of project management. Agreed? cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
On 02/16/11 13:22, Alan Post wrote: > Ivan, > > I understood Alaric's message to be a request to take the commit > log, &c, regardless of the form they are in, and convert that > directly into a form useable by the gazette: Summarized, formatted, > and checked in to the repository. Sort of. I know there's RSS and so on available, but it currently needs much manual work to turn it into content. I'd like a script that pulls that RSS feed and spits out (to current-output-port is fine, I can tie them all together into a top-level script) something that I can really easily turn into gazette text. Eg, all the hyperlinks are already generated and marked up. Let me make up some examples: >>> 2) A script that, when run in a local svn checkout, or maybe by talking >>> direct to SVN, lists all the eggs that have seen commits in a specified >>> time period (with the option of "right up to now" as the end of the time >>> period); and then lists the commit messages and revision numbers (for >>> deeper investigation, if required) for each. For extra points, make sure >>> that tagging a version of an egg is clearly indicated somehow (eg, >>> "TAGGED 1.5"). This should all be a relatively simple matter of parsing >>> the svn logs. * [[egg:ugarit|ugarit]] * [r12345] Added more bugs [[users:alaric-snell-pym|Alaric Snell-Pym]] * [r56789] Tagged 0.9 [[users:alaric-snell-pym|Alaric Snell-Pym]] I'd then look up the revision numbers if I needed to check out the background of a meaningless commit message, but largely, I'd edit that down into a paragraph like: In the [[egg:ugarit|ugarit]] egg, [[users:alaric-snell-pym|Alaric Snell-Pym]] added more bugs in handling FIFOs then tagged version 0.9 (and be roughly confident all the links are correct :-) >>> 3) A script that, when run in a local git checkout, or maybe by talking >>> direct to the core git repo, lists all the commits in a specified time >>> period, grouped by branch. Similarly, I'd be hoping for something like: * experimental * [deadbeef] Implemented call/pc [[users:felix|Felix Winkelmann]] * master * [cafebabe] Tagged v4.9 [[users:felix|Felix Winkelmann]] ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
Ivan, I understood Alaric's message to be a request to take the commit log, &c, regardless of the form they are in, and convert that directly into a form useable by the gazette: Summarized, formatted, and checked in to the repository. -Alan On Wed, Feb 16, 2011 at 07:04:28PM +0900, Ivan Raikov wrote: > > Hi Alaric, > > >Thanks for volunteering to write editorial content. As for your > requests, I believe that you can already do 2) by using the Trac RSS > feed: > > http://bugs.call-cc.org/timeline?ticket=on&changeset=on&milestone=off&wiki=off&max=50&daysback=7&format=rss > > Obviously you can set the 'daysback' parameter to whatever you > wish. Reasonable RSS readers allow you to filter the feed by creator and > other criteria. I don't remember the URL to the git browser, but > perhaps there is an RSS option there as well. > > As for 4), one can probably replace the creator tag in the RSS XML > with the user's real name, rather than messing with the wiki or HTML. > > -Ivan > > Alaric Snell-Pym writes: > > > When a community agrees it'd be cool to do something on a regular basis, > > to begin with, there's a lot of enthusiasm and volunteering, so things > > go well. > > > > However, a crucial point comes at which producing that thing starts to > > become a chore, no matter how popular the product is. At this point, if > > measures are not put into place to make it continue, it dies out. > > > > The Gazette is reaching that point, and I want to save it. > > > > I am happy to write editorial content such as recipes and mailing-list > > summaries, as long as I have time (and it doesn't take me long, I'm > > notoriously verbose in even the simplest of emails ;-), but I can't > > (personally) stomach the tedious part: going through the svn and git > > commit logs to find out what's happened, and then mapping git/svn > > identities to real names and people's pages on the wiki. > > > > So, I propose that you lot should automate it for me. > > > > I want: > > > > 1) The users page on the wiki to, in parens or brackets or something, > > after each person's name, list their various identities used in IRC / > > svn usernames / etc. so they can be easily tallied together > > > > 2) A script that, when run in a local svn checkout, or maybe by talking > > direct to SVN, lists all the eggs that have seen commits in a specified > > time period (with the option of "right up to now" as the end of the time > > period); and then lists the commit messages and revision numbers (for > > deeper investigation, if required) for each. For extra points, make sure > > that tagging a version of an egg is clearly indicated somehow (eg, > > "TAGGED 1.5"). This should all be a relatively simple matter of parsing > > the svn logs. > > > > 3) A script that, when run in a local git checkout, or maybe by talking > > direct to the core git repo, lists all the commits in a specified time > > period, grouped by branch. > > > > 4) All scripts should map usernames found in svn/git to displayed names > > via a function that defaults to identity. Somebody else please write a > > function to replace this, that looks in the wiki page and parses it to > > map svn/git identities to Wiki markup for the user's user page with > > their full name as the anchor text, that can be inserted into the above > > scripts to make wonderful magic happen. > > > > For bonus points, the output of scripts (2) and (3) could be actual > > markup for putting straight into the gazette, say as a bulleted list, > > just requiring editing to remove useless commits and to add editorial > > insight. > > > > Super special bonus point: > > > > 5) Write a script that, given a date range, parses the mailing list > > archive into wiki markup for a list of links to the posts in the > > archive, along with links to the user's pages as per (4), grouped by thread. > > > > I think that the above are relatively bite-sized chunks that people who > > want to see the Gazette continue should be able to manage between them; > > if the above are done then, if needed, I'd be willing to pioneer alone > > with running them each week (or every other week at worst) and writing > > some content around them! > > > > So, volunteers please :-) > > > > ABS > > ___ > Chicken-users mailing list > Chicken-users@nongnu.org > http://lists.nongnu.org/mailman/listinfo/chicken-users -- .i ko djuno fi le do sevzi ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Save the Gazette!
Hi Alaric, Thanks for volunteering to write editorial content. As for your requests, I believe that you can already do 2) by using the Trac RSS feed: http://bugs.call-cc.org/timeline?ticket=on&changeset=on&milestone=off&wiki=off&max=50&daysback=7&format=rss Obviously you can set the 'daysback' parameter to whatever you wish. Reasonable RSS readers allow you to filter the feed by creator and other criteria. I don't remember the URL to the git browser, but perhaps there is an RSS option there as well. As for 4), one can probably replace the creator tag in the RSS XML with the user's real name, rather than messing with the wiki or HTML. -Ivan Alaric Snell-Pym writes: > When a community agrees it'd be cool to do something on a regular basis, > to begin with, there's a lot of enthusiasm and volunteering, so things > go well. > > However, a crucial point comes at which producing that thing starts to > become a chore, no matter how popular the product is. At this point, if > measures are not put into place to make it continue, it dies out. > > The Gazette is reaching that point, and I want to save it. > > I am happy to write editorial content such as recipes and mailing-list > summaries, as long as I have time (and it doesn't take me long, I'm > notoriously verbose in even the simplest of emails ;-), but I can't > (personally) stomach the tedious part: going through the svn and git > commit logs to find out what's happened, and then mapping git/svn > identities to real names and people's pages on the wiki. > > So, I propose that you lot should automate it for me. > > I want: > > 1) The users page on the wiki to, in parens or brackets or something, > after each person's name, list their various identities used in IRC / > svn usernames / etc. so they can be easily tallied together > > 2) A script that, when run in a local svn checkout, or maybe by talking > direct to SVN, lists all the eggs that have seen commits in a specified > time period (with the option of "right up to now" as the end of the time > period); and then lists the commit messages and revision numbers (for > deeper investigation, if required) for each. For extra points, make sure > that tagging a version of an egg is clearly indicated somehow (eg, > "TAGGED 1.5"). This should all be a relatively simple matter of parsing > the svn logs. > > 3) A script that, when run in a local git checkout, or maybe by talking > direct to the core git repo, lists all the commits in a specified time > period, grouped by branch. > > 4) All scripts should map usernames found in svn/git to displayed names > via a function that defaults to identity. Somebody else please write a > function to replace this, that looks in the wiki page and parses it to > map svn/git identities to Wiki markup for the user's user page with > their full name as the anchor text, that can be inserted into the above > scripts to make wonderful magic happen. > > For bonus points, the output of scripts (2) and (3) could be actual > markup for putting straight into the gazette, say as a bulleted list, > just requiring editing to remove useless commits and to add editorial > insight. > > Super special bonus point: > > 5) Write a script that, given a date range, parses the mailing list > archive into wiki markup for a list of links to the posts in the > archive, along with links to the user's pages as per (4), grouped by thread. > > I think that the above are relatively bite-sized chunks that people who > want to see the Gazette continue should be able to manage between them; > if the above are done then, if needed, I'd be willing to pioneer alone > with running them each week (or every other week at worst) and writing > some content around them! > > So, volunteers please :-) > > ABS ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Save the Gazette!
When a community agrees it'd be cool to do something on a regular basis, to begin with, there's a lot of enthusiasm and volunteering, so things go well. However, a crucial point comes at which producing that thing starts to become a chore, no matter how popular the product is. At this point, if measures are not put into place to make it continue, it dies out. The Gazette is reaching that point, and I want to save it. I am happy to write editorial content such as recipes and mailing-list summaries, as long as I have time (and it doesn't take me long, I'm notoriously verbose in even the simplest of emails ;-), but I can't (personally) stomach the tedious part: going through the svn and git commit logs to find out what's happened, and then mapping git/svn identities to real names and people's pages on the wiki. So, I propose that you lot should automate it for me. I want: 1) The users page on the wiki to, in parens or brackets or something, after each person's name, list their various identities used in IRC / svn usernames / etc. so they can be easily tallied together 2) A script that, when run in a local svn checkout, or maybe by talking direct to SVN, lists all the eggs that have seen commits in a specified time period (with the option of "right up to now" as the end of the time period); and then lists the commit messages and revision numbers (for deeper investigation, if required) for each. For extra points, make sure that tagging a version of an egg is clearly indicated somehow (eg, "TAGGED 1.5"). This should all be a relatively simple matter of parsing the svn logs. 3) A script that, when run in a local git checkout, or maybe by talking direct to the core git repo, lists all the commits in a specified time period, grouped by branch. 4) All scripts should map usernames found in svn/git to displayed names via a function that defaults to identity. Somebody else please write a function to replace this, that looks in the wiki page and parses it to map svn/git identities to Wiki markup for the user's user page with their full name as the anchor text, that can be inserted into the above scripts to make wonderful magic happen. For bonus points, the output of scripts (2) and (3) could be actual markup for putting straight into the gazette, say as a bulleted list, just requiring editing to remove useless commits and to add editorial insight. Super special bonus point: 5) Write a script that, given a date range, parses the mailing list archive into wiki markup for a list of links to the posts in the archive, along with links to the user's pages as per (4), grouped by thread. I think that the above are relatively bite-sized chunks that people who want to see the Gazette continue should be able to manage between them; if the above are done then, if needed, I'd be willing to pioneer alone with running them each week (or every other week at worst) and writing some content around them! So, volunteers please :-) ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
