On the https://www.ohloh.net/p page please add the ability to sort projects by lines of code.

A git repository maintains two dates for each commit: The AuthorDate which is displayed in standard git log output The CommitDate which is displayed in git log --pretty=fuller output Here is an ... [More] example from the OpenAFS project: commit f199ac666195771a02e3ebb040c6e5fe47c58c58 Author: Andrew Deason AuthorDate: Wed Nov 2 16:55:49 2011 -0500 Commit: Derrick Brashear CommitDate: Sat Nov 12 06:55:52 2011 -0800 afs: Do not use separate array for srvAddrs This use of the AuthorDate instead of the CommitDate results in two problems: The commit list displayed by Ohloh is not ordered the same as git log output which results in confusion since the most recent commits will not always be displayed on the top of the list. Monthly totals, graphs, statistics, etc are incorrect. The AuthorDate is the date that the Author created the first version of the patchset in the her/his local repository. The CommitDate is the date that the patchset was accepted by the project and committed to the upstream repository. Can this please be fixed? Thank you. [Less]

The hourly cost of a developer varies based upon the skill set involved. Please permit projects to configure the default Cocomo hour wage that is used for computing the estimated cost of the project.

Cocomo analysis provides a point in time analysis of a code base which is intended to represent what it would take to reproduce the code base if coding was started from scratch. It does not provide ... [More] any indication of how much effort was spent over the history of a project. I think it would be helpful for ohloh to develop an estimated costing model which could be used to show to overall investment in project over its lifetime or on a monthly basis. [Less]

Large projects such as OpenAFS are often broken up into subcomponents (processes, libraries, packaging, documentation, etc.) These components often have very different attributes. They may be ... [More] developed with different languages or different licenses. They are often developed by different sub-groups of the project development team. It may also be true that while the project as a whole may be active specific subcomponents may be rotting. I believe it would be quite useful if the Code Analysis, Commits and Estimated Cost tools could be restricted to particular directories or subtrees. Thanks. [Less]