I used to monitor the commits using http://cia.vc/

Since this service is not running anymore, is there any alternative?

Luiz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20121004/a17df9bb/attachment.html>

2012/10/4 luiz americo pereira camara :

I used to monitor the commits using http://cia.vc/ Since this service is not running anymore, is there any alternative?

There is http://svn.freepascal.org/feeds/lazarussvn.rss

Vincent

luiz americo pereira camara wrote

Since this service is not running anymore, is there any alternative?

The GitHub mirror I manage also has a built-in RSS feed for repository activity.

RSS feed of 'upstream' branch (that's Lazarus Trunk):

https://github.com/graemeg/lazarus/commits/upstream.atom

The original URL showing the commits in a web browser, and with a link to the above RSS feed.:

https://github.com/graemeg/lazarus/commits/upstream

Graeme.

Graeme Geldenhuys wrote

The GitHub mirror I manage also has a built-in RSS feed for repository activity.

I've also updated the 'Git Mirrors' wiki page with RSS feed information for Lazarus and FPC repositories.

http://wiki.freepascal.org/git_mirrors#RSS_feeds_of_commit_activity

Graeme.

Thanks for Vincent and Graeme

Luiz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20121004/8cee2887/attachment.html>

Hi,

I made a small script excactly for this use...
... but as it is used only be me, there could be some problems with it

Anyway, maybe it is useful:
http://www.downloadit.pf-control.de/feed.php

To see the actual changes click on a file or hover over it (sometimes a bit tricky)

Regards,
d.l.i.w

2012/10/4 dliw

Interresting

Thanks

Luiz

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20121004/ec96ccd8/attachment-0001.html>

My findings about the recommended feeds:

1) Native http://svn.freepascal.org/feeds/lazarussvn.rss

Good:
- direct from repository
- familiar (to me) file listing and revision compare page Bad
- Title not informative: Revision XXX
- Redundant info in content. Repeats title (Revision XXX), "Log:" not necessary

2) GitHub https://github.com/graemeg/lazarus/commits/master.atom

Good:
- Title informative
- Reliable service (GitHub)
Bad
- Unfamiliar (to me) file listing and revision compare page
- Revision number not easily visible

@Vincent
The generated svn feed from freepascal server can be customized? If yes, can you point me the script so i can take a look to improve it?

Luiz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20121004/2658ee76/attachment.html>

luiz americo pereira camara wrote

My findings about the recommended feeds:

Good comparison. Now you need to ask yourself as well, what is the most important information from commit logs. RSS feeds should tell you... "hey, this is the changes that has occurred". In such a case, is the revision number really import. The number doesn't actually tell you anything about what has happening in the project.

My prioritized list of information I find important in a repository RSS feed is as follows:

1) The title of the commit. A summary line of what that patch does. This allows me to quickly see what I find interesting.
2) More detailed commit message - though SVN users tend to love single line commit logs. Just my general observation.
3) The files that were modified.
4) How easily I can view the actual patch / diff.
5) The actual revision or sha1 of that commit, it case I wanted to report an issue or something.

With this order of what is important, I find that the GitHub RSS output hit the nail on the head. Not to mention the other extra features GitHub adds, like allowing you add notes to lines of code. You can then send tell others to view that patch on GitHub, and they will see your notes - great for pointing out bugs or possible improvements to patches.

1).... - Redundant info in content. Repeats title (Revision XXX), "Log:" not necessary

+1

2) GitHub https://github.com/graemeg/lazarus/commits/master.atom Bad - Unfamiliar (to me) file listing and revision compare page

Uh? It displays the standard de-faco patch format - just color coded. A minus-line for what was old, and a plus-line for what is new. 'svn diff' and 'git diff' generates such a patch format by default.

Graeme.

2012/10/4 Graeme Geldenhuys

I mean i'm familiar with
http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=rev&root=lazarus&revision=38966 and not with
https://github.com/graemeg/freepascal/commit/70deeaff71322b4b5af760c4fb757247ce93d565

In fact, Github is more complete giving the changes directly

All in all It's just personal taste. And this is not debatable

Luiz

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20121004/12323748/attachment.html>

2012/10/4 Graeme Geldenhuys

Agree

That's the main drawback of original svn feed, in my opinion.

Luiz

2012/10/5 luiz americo pereira camara :

@Vincent The generated svn feed from freepascal server can be customized? If yes, can you point me the script so i can take a look to improve it?

It uses the attached svn2feed.py, a rather old version from 2007 with a fix from 2009. Maybe the current version at
http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/svn2feed.py is an improvement.

Vincent
-------------- next part --------------
A non-text attachment was scrubbed...
Name: svn2feed.py
Type: application/octet-stream
Size: 16472 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20121005/65e54820/attachment-0001.obj>

This won't help you with any feed as long as the developers don't add "summary lines" to the commit messages as otherwise only an abbreviation of the commit message could be used as the title. Sometimes I'm already adding lines like "fixes bug #1234" to the top, but otherwise I'm already putting enough energy into the commit message itself so I don't intend to add an additonal line if I don't see a need for it (and I don't see RSS feeds as a reason).

Regards,
Sven

luiz americo pereira camara wrote

and not with https://github.com/graemeg/freepascal/commit/70deeaff71322b4b5af760c4fb757247ce93d565

If you want the list of files that have changed in a commit/patch, simply click the "Show Diff Stats" button on the right of the screen.

All in all It's just personal taste.

Yes, I understood that.

Graeme.