I think a good code hygiene is important, and some suggestions here are relevant: 1) I also think there should be a directory for the source code (namely, src/), and the top level should act as a table of contents. As a newcomer myself who's trying to grasp Git, I can say an organized project makes people more inclined join. Therefore, directories should be named as clearly as possible: see item 2; 2) For item 1, t/ should be renamed to testsuite/. As Junio said, if we get a more organized project, people could just "cd t" and tab to autocomplete, or "cd tes" at the worst scenario, which is not such a big hassle. About people expecting the testsuite to be inside t/, once they type "cd t" and get an error, most people would look for an alternative and eventually find the correct folder, or tabbing would just suggest the name. 3) The top level should hold files that point people towards where they want to go, helpful files like README and even some Documentation/ files could get a promotion. 3) As 1.8.0 can be an inflexion for users, so could be for the developers as well. -- JoÃo Paulo Melo de Sampaio Computer Engineering Student @ UFSCar Website: http://www.jpmelos.com Twitter: twitter.com/jpmelos (@jpmelos) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html