[boost] Development Practices (Proposal Progress)

Subject: [boost] Development Practices (Proposal Progress)
From: Dean Michael Berris (mikhailberis_at_[hidden])
Date: 2011-01-03 16:24:56

Hi Everyone,

I was looking around at the Trac wiki and saw that there's a page
called "ImprovingPractices". It's
https://svn.boost.org/trac/boost/wiki/ImprovingPractices if you want
to look.

The Objectives stated on the page are definitely the same ones I am
looking to address with a proposal I was thinking of writing from
scratch. A quick read through definitely seems to me that there is
significant overlap between what I had in mind and what's already in
this document.

One thing that doesn't seem to be in this document, is how to get new
libraries into a Boost distribution. I'm not sure if this part should
be in the same document either, but I really do think that somehow the
continuity between the development of a library for inclusion into
Boost and the release procedure should be in-tune.

The document also assumes that the development of a library happens in
the same repository -- mainly because it assumes that subversion is
going to be used exclusively. That's understandable, but in the case
of a proposal to support Git-based libraries as well I wonder whether
it's alright if I edit this document for the proposed enhancements.

So my question would be:

- What would be the best way for me to solicit feedback on a proposal
that tweaks the current process? Is editing this wiki page the way or
should I create a new one?
- Because there a number of parts of the proposal I'm going to write
that deal with things on the front-end of the process (the
interest-gathering, development (collaborative or otherwise), and
review/inclusion part) as well as the back-end of the process
(distribution maintenance, bug fixing / patching, and release
management / packaging) is it better if these areas are described in
different Wiki pages or should one page with different sections
suffice?
- Is the Wiki the best place to put this? Would others be more
comfortable in a different means of looking at and commenting on a
complete proposal?

Thanks in advance and I definitely look forward to feedback and guidance.

-- 
Dean Michael Berris
about.me/deanberris