When I sent this I attached some top-level html files, but my mailer seems
to have eaten them.
The tarball made it through, however. If you look at the output dir
inside the tarball, you'll see the QIPs I mentioned in fully rendered
form.
The other stuff in the tarball is some code to convert QIPs from text
format to html and generate an index.
Justin
On Thu, 6 Jan 2011, Justin Ross wrote:
Hi, everyone.
I'd like to propose a new way to communicate about the major changes going
into our releases. The goal is to help us make decisions early in the
process, coordinate when a change in one place impacts another, and engender
a broader sense of direction. It should also help to document the work that
we do.
To do this, I've imitated an approach that's been used in other community
software projects. The Python project, for instance, uses Python Enhancement
Proposals (PEPs) to review important changes to the Python language [1].
I've attempted to produce something very similar here and tie it into our
release process. It's my hope that during the 0.10 cycle some contributors
will opt to describe their major changes using the QIP process. This is,
however, entirely optional.
The attached QIP 1 and QIP template should provide an overview of how this
might work. This is very much in an early and unrefined form, so I hope
you'll take a look and share your thoughts.
Thanks,
Justin
---
[1] http://www.python.org/dev/peps/pep-0001/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
