Gregory Casamento wrote:
Reasons to have developer.gnustep.org <http://developer.gnustep.org>:
3) Can provide documentation along with clear examples in a place that people can reach simply by typing the URL without having to wonder where to find it.
Most people (including Luke and me) are upset that gnustep.org doesn't redirect to www.gnustep.org would somebody really type out that domain? Most people just slap the name on google with perhaps a term on it and click on the link (also encouraged by current browser bar/searchbar design, but I digress).
Personally, If I need apple documentation, e.g., I just slap in the class name in a search engine and add perhaps "doc" "reference" "example" and hope something comes out. Other times, if I need an overview, I go to the website and browse around. Click on a link or a menu. In that case, it is of no difference if stuff resides in www.gnustep.org/developer or developer.gnustep.org
Most of the stuff you cite for developers is just GitHub. We don't need more. People will get code or release form there 99% of the time. I extra maintain duplicated information on the website or wiki, but that is convenient for people looking around and for the rare developer using it. I bet a beer that most other developer either use ready packages from their distro or just clone the git repo.
In the case we think subdomains are of use, I would rather gather a documentation site. E.g. docs.gnustep.org with different kind of manuals as well as reference documentation.
But this is all a matter of taste and opinions, I just wanted to make the value of a domain quite relative.
These again, were just my 2 cents. Cheers - Riccardo
