[Scons-dev] New SCons doc toolchain...

[Gary Oberbrunner]

On Thu, May 9, 2013 at 4:53 PM, Gour <gour at atmarama.net> wrote:


>

> When SCons project moved from SVN to Mercurial (personally I tried/used

> everything from darcs, bzr, hg, mtn, fossil and now settled on Git,

> although I

> prefer Bitbucekt over Github), I believe that one of the rationale is hope

> to

> increase contributors by using DVCS.

>

> In the same light I also propose(d) using reST/Sphinx which is much easier

> for

> content authors, has lot of support within Python community and its usage

> is

> simply exploding in recent years. (see http://sphinx-doc.org/examples.html

> )

>


I see this as an iterative process.  The first thing was to rationalize the
tool chain and use one tool for everything.  Formerly we had a hodgepodge
of stuff.  Now that it's decently organized, there's of course more work to
be done to make the doc better, more beautiful and readable, and so on --
and we can consider switching to alternative tools too; at least everything
parses and validates now!  So it's conceivable to convert it if that makes
sense.

(By the way, I use git at work and for some other open source projects, and
I have to say, even though it's more complicated and the doc is poor and
the commands args are inconsistent, I like it a lot more than mercurial.
Having the right core architecture and philosophy makes all the difference.)

-- 
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20130509/1c19301a/attachment.html>