I don't think it's a good idea to have an RSS feed with commits show up in download sections, definitely not by default. Most of the time these commit messages are of no help to regular users, and they do have the potential to confuse people. --Jeroen De Dauw (talk) 19:37, 5 December 2012 (UTC)
- Confuse how? Even if someone doesn't understand the meaning of the commits, they give some clue on development activity etc. It's just a couple lines and seemed nice (the only piece of information always up to date on documentation pages! ;-) ), that's it. --Nemo 21:16, 5 December 2012 (UTC)
Instructions may be hard to follow
The instructions for the download may be hard to understand:
- If the person does not know git, it is hard to get what all this stuff in the lists (code, "tag", "branches") is about (not to mention what you are looking at after clicking a link).
- People who know git may just use the suggested git clone
If the list is intended to allow people who know git to get a better impression of the repo we should possibly pull up the git clone section (since it seems to be the easiest way to obtain the files) and then write something like: "If you want to browse the repository, here is a overview of entry points". --Jan Dittrich (WMDE) (talk) 07:05, 27 June 2016 (UTC)