X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Sun, 4 Nov 2012 14:39:59 -0500 Message-Id: <201211041939.qA4Jdx86026393@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (message from Britton Kerin on Sun, 4 Nov 2012 09:18:12 -0900) Subject: Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was: Pin hole size) References: <1511E63C-F435-44B1-9734-C7AF7AF49A92 AT sbcglobal DOT net> <20121030132922 DOT GY32696 AT fi DOT muni DOT cz> <201210312340 DOT q9VNe3VW012697 AT envy DOT delorie DOT com> Reply-To: geda-user AT delorie DOT com Deciding how much and where to document things is always tricky, especially for key pages like the home page. Whoever decides to work on such pages will find that "improves over time" is the way to go. Such things tend to evolve over time as people ask about how to do things in the mailing lists and forums - if you find people keep asking how to find something, you move pointers to that something to more obvious places. As for the git page, IMHO we need *something* that serves as (1) an intro to git for people who don't know it, (2) information specific to our projects (i.e. example git commands with geda-specific URLs), and (3) a summary of the git process we prefer users to use. A section at the bottom leading to "further readings" would be suitable as well, for people who want more and broader information not specific to geda.