[pypy-svn] rev 1614 - pypy/trunk/doc/funding
hpk at codespeak.net
hpk at codespeak.net
Tue Oct 7 22:24:36 CEST 2003
Author: hpk
Date: Tue Oct 7 22:24:36 2003
New Revision: 1614
Modified:
pypy/trunk/doc/funding/B5.0_management.txt
Log:
a first go at the management section (where i had a FIXME tag).
please note that i put everything into the B5.0_management
part for the time beeing. I suggest to roll all B5.* sections
into one document as this makes it easier to move around stuff.
If this is somehow not applicable then the paragraphs need
to be moved to different files, i guess.
This is a checkin to gather more feedback.
Modified: pypy/trunk/doc/funding/B5.0_management.txt
==============================================================================
--- pypy/trunk/doc/funding/B5.0_management.txt (original)
+++ pypy/trunk/doc/funding/B5.0_management.txt Tue Oct 7 22:24:36 2003
@@ -2,35 +2,108 @@
B.5 Project management
-Describe the organisation, management and decision making structures
-of the project. Describe the plan for the management of knowledge, of
-intellectual property and of other innovation-related activities
-arising in the project.
+DESCRIBE THE ORGANISATION, MANAGEMENT AND DECISION MAKING STRUCTURES
+OF THE PROJECT. DESCRIBE THE PLAN FOR THE MANAGEMENT OF KNOWLEDGE, OF
+INTELLECTUAL PROPERTY AND OF OTHER INNOVATION-RELATED ACTIVITIES
+ARISING IN THE PROJECT.
(Recommended length three pages)
:DELETE:END
+
Project Management
=====================
-add text!
+FIXME probably some overview-preamble here, i can't write about the
+financial managment. holger.
+
+Technical development driven by discussion and feedback
+-------------------------------------------------------
-FIXME_LAURA FIXME_JACOB FIXME_HOLGER This is the section that needs the
-longest about Sprints... Also need to say that we have made a working
-prototype, have worked together before,
-
-B.5 Project management
-
-Describe the organisation, management and decision making structures
-of the project. Describe the plan for the management of knowledge, of
-intellectual property and of other innovation-related activities
-arising in the project. (Recommended length three pages)
-
-This section should describe how the proposed project will be managed,
-the decision making structures to be applied, the communication flow
-within the consortium and the quality assurance measures which will be
-implemented, and how legal and ethical obligations will be met.
+The technical development of PyPy is driven by open continous discussion.
+Many of the involved decisions are made and verified during one-week
+working meetings, so called "sprints". Members from the larger Python
+software community are publicly invited and have the chance to interact
+and work with the PyPy developers or become one themselves. Mailing lists,
+chat-sessions, Wikis and notification of program changes provide a constant
+flow of information between PyPy project members and the wider community.
+Therefore conflicts out of missing information or due to
+misunderstandings will be minimized.
+
+As the PyPy researchers and developers fully interact with a wider
+research and software audience, we expect to often present reports
+and scientific papers on major conferences.
+
+
+Technical decisions
+-------------------
+
+Major design or technical decisions are usually reached through consensus
+during the sprints. If a conflict cannot be resolved there then the technical
+board gets the final say. The members of the technical board are appointed by
+a vote of everyone who has commit rights to the source repository. However,
+it is expected that design and implementation choices will usually be
+determined by consensual agreement or by informal votes on the development
+mailing list. This is common practice within the Python and many others free
+softare communities. Also, the PyPy developers and researchers will construct
+few if any formal hierarchies between them. Constantly working together with
+agile methodologies and the visilibity of each individual contribution help
+enforce high-quality program code and good design decisions.
+
+
+Intellectual property
+---------------------
+
+The public availability of the source code at all times together with a
+very open and flexible license (the MIT-license) provide the basis to exchange
+ideas, contribute to the project or reuse all parts of it from the start.
+In return, this provides the developers with fast feedback
+and improvements with respect to their current developments. At the heart of a
+free software community lies open communication, the free flow of information
+and organizing shared interests. The PyPy project is already fully involved and
+based on these principles. Finally, every contributor is fully responsible for not
+introducing any program code which might infringe third party copyright or patents.
+
+
+The quality
+-----------
+
+The PyPy project will ensure quality by a variety of means. On the grand
+scale, the involvement of excellent researchers ensures that the general
+direction takes care of latest insights in language research. Moreover,
+we will publish our research results on conferences and to scientific
+and free software communities. This forms the basis to maintain a high-quality
+general technical direction.
+
+The developers deploy agile methodologies like unittest-driven development
+and pair-programming. By the end of the project we expect to have produced
+more than 3000 unittests testing every aspect of the runtime system. The
+presence of such tests also allows to rapidly change parts of the implementation
+without fear of breaking functionality elsewhere. We also plan to release
+our runtime system often and thus gather additional feedback from early
+adopters, developers and researchers.
+
+To support the open development we base all of our documents, source
+code and website information on a version control system. In combintation
+with a notification on all changes this ensures that all interested parties
+can review and react to developments.
+
+The PyPy developers have produced a working prototype within four one-week
+sprints and a little development in between. The code and design quality
+of the project is already widely accepted. There are now 400 unittests.
+As a consequence, Guido van Rossum, the inventor and maintainer of today's
+Python, listed is as the number one project he would like to succeed. He
+previously attended one of our sprints and got deeply involved with our
+architecture and source code which he immediately found intuitive to work with.
+
+Thus we believe that our choices for quality management are fit to meet
+highest standards.
+
+
+FIXME Jacob (holger) the financial and management interfacing with
+the EU needs to be described. Then the different parts need to
+be structured in a resonable way.
Quality of the management
More information about the Pypy-commit
mailing list