Re: [Boost-docs] svn.boost.org wiki

Subject: Re: [Boost-docs] svn.boost.org wiki
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2015-07-15 18:15:30

On Wed, Jul 15, 2015 at 10:47 AM, Stefan Seefeld <stefan_at_[hidden]>
wrote:

> On 15/07/15 12:39 PM, Rene Rivera wrote:
> > On Wed, Jul 15, 2015 at 10:14 AM, Stefan Seefeld <stefan_at_[hidden]
> > <mailto:stefan_at_[hidden]>> wrote:
> >
> > Regarding that.. One thing I thought about is that we could rename the
> > python trac component to something like "python USE GITHUB".
>
> Hah. Yes, that may work, but I'd still want to advertise the github
> issue tracker properly, somewhere. And the question remains: where ?
>

Since I'm partly in your shoes also (in wanting to avoid trac and just use
github). What I would do is:

a) Rename the trac component as above.
b) Avoid editing the trac wiki.
c) Suggest some edits to <http://www.boost.org/development/bugs.html> to
mention github issues in general and to point out the trac "name USE
GITHUB" thing.
d) Possibly edit your library metadata description <
https://github.com/boostorg/python/blob/develop/meta/libraries.json>  to
note the use of github so that ti shows up here <
http://www.boost.org/doc/libs/1_58_0/>.
e) Suggest additional fields for the metadata to include links to the
library specific resources (like web site, issues site, additional testing,
etc.).

I was thinking of setting up a Boost.Python website on github, with
> mostly the same content as on Boost.org (i.e., generated form the same
> sources), plus some additional bits that I can't easily integrate into
> Boost.org, such as Boost.Python-specific development docs.
> I see that some Boost libraries also have their own website outside
> Boost.org (http://boost-spirit.com, say :-) ), so this wouldn't be a
> first...
>

I highly recommend you to do that :-)

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail