Subject: Re: [boost] Wiki, website, and stuff..
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-01-29 05:30:45
> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Daniel Pfeifer
> Sent: 29 January 2015 09:11
> To: Boost Developers List
> Subject: Re: [boost] Wiki, website, and stuff..
> On Wed, Jan 28, 2015 at 1:52 PM, Beman Dawes <bdawes_at_[hidden]> wrote:
> > > would be better to start moving such documentation away from the Trac wiki.
> > > * A github pages site of some sort.
> > >
> > > Are there other options? Any opinions on the above options?
> > There are really two issues IMO:
> > * Docs primarily for release managers. We already have the
> > boostorg/release repo, so we can either add release manager docs to
> > its directory tree or use its wiki. The wiki approach encourages all
> > release managers to help keep the docs up-to-date. Docs in the
> > directory tree brings all the advantages of git distributed version control,
> One quick comment I would like to throw in here:
> Wikis on GitHub are stored in Git repositories and come with all advantages of git distributed
I think that
1 Documentation that is correct, updated and understandable is Really, really, really important -
and we could do better.
2 Wiki documentation has the big advantage that anyone (with a login - not anon) can update - so
updates and correction are more likely to be done.
3 GIT allows us to easily back up to previous versions if a change proves unhelpful.
So I support Wikis on GitHub are stored in Git repositories.
(How we deal with the bug reporting aspect of Trac, I am not so sure.)
--- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk