Boost logo

Boost :

Subject: Re: [boost] Wiki, website, and stuff..
From: Daniel Pfeifer (daniel_at_[hidden])
Date: 2015-01-29 04:11:10

On Wed, Jan 28, 2015 at 1:52 PM, Beman Dawes <bdawes_at_[hidden]> wrote:

> On Tue, Jan 27, 2015 at 10:42 PM, Rene Rivera <grafikrobot_at_[hidden]>
> wrote:
> > I was contemplating editing the release schedule documentation <
> >> and thinking if
> it
> > would be better to start moving such documentation away from the Trac
> wiki.
> > And I think it is a good idea to move that documentation elsewhere.
> > Especially if it's some place where it's easier to manager the editing
> > permissions and contributions. So I was thinking about what options we
> had.
> > What I'm aware of as choices are:
> >
> > * Another project in Github just for wiki like documentation.
> >
> > * Using the website project wiki for it.
> >
> > * Adding it directly to the website given how easy it is to edit online
> > now. Although not so easy to preview because of the way the web site
> works.
> >
> > * 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 version control.

> and we can also use gh-pages mechanism. The wiki approach is
> somewhat lighter weight and so may be better for casual documentation.
> * Other trac wiki pages: I don't think there is a single answer. Each
> subset of pages needs to be looked at since some should be abandoned,
> some moved to a boostorg or boostorg/project wiki, and some (like
> developer related docs) should probably go in either the super-project
> repo or a new developer repo.
> --Beman
> _______________________________________________
> Unsubscribe & other changes:

Boost list run by bdawes at, gregod at, cpdaniel at, john at