SVN Commits, mailing List Improvements

[AF]

I have a few ideas to improve this, as well as save poor email clients on PDAs and phones from dieing a lonely death when uber commit arrives.

Basically currently when svn commit occurs, it gets sent off to berliOS where its distributed on a mailing list.

Instead, what would happen is it gets sent to an email account which is used by a word press blog to publish posts. the svn commits would show up in the blog in a nice pretty html interface complete with a slew of typography and code syntax highlighting plugins. Blogposts would then be sent out via feedburner or another subscription mechanism in pretty html emails that show summaries but link to the blogpost at the end rather than showing 100 pages of diffs.

This would allow us to view all the commits in a nice web interface for which we would have full search and control over the theme, aswell as the ability to comment on svn commits in the blog, and use the extensive wordpress development community. we could also subscribe via email as the mailing list currently does, or we could use RSS feeds, which opens up a whole new world, such as integration into other sites, google homepage, desktops/screensavers, etc etc etc.

In the end we can subscribe to the feedburner using the old berliOS mailing list so those already subscribed do not loose their svn commits while taking advantage of the new emails.

This would also allow buildbot results to be posted to the blog using the xmlrpc functions in wordpress etc

[Auswaschbar]

I have a few ideas to improve this, as well as save poor email clients on PDAs and phones from dieing a lonely death when uber commit arrives.

Basically currently when svn commit occurs, it gets sent off to berliOS where its distributed on a mailing list.

Instead, what would happen is it gets sent to an email account which is used by a word press blog to publish posts. the svn commits would show up in the blog in a nice pretty html interface complete with a slew of typography and code syntax highlighting plugins. Blogposts would then be sent out via feedburner or another subscription mechanism in pretty html emails that show summaries but link to the blogpost at the end rather than showing 100 pages of diffs.

This would allow us to view all the commits in a nice web interface for which we would have full search and control over the theme, aswell as the ability to comment on svn commits in the blog, and use the extensive wordpress development community. we could also subscribe via email as the mailing list currently does, or we could use RSS feeds, which opens up a whole new world, such as integration into other sites, google homepage, desktops/screensavers, etc etc etc.

In the end we can subscribe to the feedburner using the old berliOS mailing list so those already subscribed do not loose their svn commits while taking advantage of the new emails.

This would also allow buildbot results to be posted to the blog using the xmlrpc functions in wordpress etc

We had this once, it was called fisheye. It have had newsfeeds, on a per-directory basis and othere usefull stuff. I miss it

[AF]

Isnt fisheye a commercial java application? I liked it but it was a little slow

[Tobi]

Feel free to create such a blog and subscribe an e-mail address which the blog can read to the commit mailing list.

Or poke Fnordia about fisheye