Forum OpenACS Q&A: CVS Commit forum notifications and separate forums for separate tags

Greetings,

Is email notification working for the CVS Commits forum for anybody?  It's not for me, I've tried toggling it several times.

Also, would there be value in creating different Commits forums for different tags?  We're tracking the 4.6 release pretty closely, but I have to look closely in the forum to see what patches got committed to which branch.

--cro

the messages go in directly and I think circumvent the notifications calls. I think something to better track what is going on on the various branches is a good idea. I am not that happy with the "thread per day" format but I am not sure what we should replace it with. I should add some branch info into my cvs log browser (and I have been thinking of adding batched notifications as well). If I get to it I will let you know.
Hmm, I didn't realize one had to explicitely call notifications so they got sent (at the time, notifications and forums were _brand new_) when I wrote the cvs-to-forums log script. I will fix that.

I'll think about a way to log to different tags, but how about this: We the tag to the subject or to an extra header so you can quickly filter it with procmail or another mail processing tool?

If people are not happy the "thread per day" model, then please suggest another model and we can see about making it happen.

-Roberto

We the tag to the subject or to an extra header so you can quickly filter it with procmail or another mail processing tool?

Will this be difficult when the patches apply to more than one tag? Or will that never happen? Sorry if I am exposing my CVS ignorance.

I think a thread per module makes sense.  You can get chronoligical listings at https://openacs.org/forums/user-history?user%5fid=46412&view=forum
That way people could subscribe to notifies on just the modules they care about (as well as all of them, of course). Of course, since I am not going to do the work I will now quit nitpicking your cool logging tool :)