[pypy-svn] rev 1726 - pypy/trunk/doc/funding
lac at codespeak.net
lac at codespeak.net
Sat Oct 11 18:03:08 CEST 2003
Author: lac
Date: Sat Oct 11 18:03:07 2003
New Revision: 1726
Modified:
pypy/trunk/doc/funding/B5.0_manage_bea.txt
Log:
removed MIT license to put in section 3. Deleted boilerplate.
Modified: pypy/trunk/doc/funding/B5.0_manage_bea.txt
==============================================================================
--- pypy/trunk/doc/funding/B5.0_manage_bea.txt (original)
+++ pypy/trunk/doc/funding/B5.0_manage_bea.txt Sat Oct 11 18:03:07 2003
@@ -1,11 +1,5 @@
-:DELETE:BEGIN
-
- B 5.0 Project Management
-
-:DELETE:END
-
Project Management
-======================
+==================
PyPy as a project will be implementing an agile development
lifecycle.This choice of development method will have effects on the
@@ -84,12 +78,6 @@
On the following pages we will describe in more detail how this choice
of method will influence the way this project will be managed.
-:DELETE:BEGIN
-
-B 5.1 Project manager
-
-:DELETE:END
-
Project Manager
------------------
@@ -250,14 +238,8 @@
management, communication, conflictresolving) for Learning Tree
International since 2000 in both Sweden and USA.
-:DELETE:BEGIN
-
-B 5.2 Management structure
-
-:DELETE:END
-
Management structure
--------------------------
+--------------------
The management structure will be as follows:
@@ -312,21 +294,15 @@
Since the PyPy project is implementing agile/Open Source methods
-("sprints") the goal is to have a proactive team of developers and project
+("Sprints") the goal is to have a proactive team of developers and project
managers.
This means that the project will be ruled by one primary management
strategy - to delegate as much responsibility to the developer team and
the persons responsible for each individual workpackage. This rule _will_
guide all planning and decisionmaking in the two boards.
-:DELETE:BEGIN
-
-B 5.3 Coordinator
-
-:DELETE:END
-
Coordinator
------------------
+-----------
The project coordinator in the PyPy project is:
@@ -348,14 +324,8 @@
The project coordinator will be able to use the project management team
for support in the tasks mentioned above.
-:DELETE:BEGIN
-
-B 5.4 Project meetings
-
-:DELETE:END
-
Project Meetings
------------------------
+----------------
Management Board will meet at the start of the project and two times
per year or on an ad hoc basis as requested. The meetings will
@@ -369,7 +339,7 @@
in the internal project web.
Team Meetings
-+++++++++++++++++++
++++++++++++++
The project team will meet at the "sprints" which take place on a six
week cycle ( se below). During the sprints, there will be time
@@ -398,17 +368,17 @@
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Key to PyPy's technical development and research are so called
-"sprints". These publically announced one-week meetings serve as an
+"Sprints". These publically announced one-week meetings serve as an
intense working forum to rapidly discuss and implement key PyPy ideas
with agile methodologies and take place on a six week cycle.
-The goals for each "sprint" will be decided by the development team
+The goals for each "Sprint" will be decided by the development team
in cooperation with the project management team. The project manager
is responsible for the handling of logistics before, during and after
the sprints (invite, location, preparation etc). Agenda and
discussions/decisions on these sprints will be documented and put up
in the internal project web.
-During the "sprints", developers usually pair up and write
+During the "Sprints", developers usually pair up and write
unit-tests to test the to-be-implemented features before actually
adding them. The unittest-first approach helps to understand the
planned feature. Additionally, the discussion in a pair makes sure
@@ -464,14 +434,8 @@
individual contribution help enforce high-quality program code and
good design decisions.
-:DELETE:BEGIN
-
-B 5.5 Quality control of technical development
-
-:DELETE:END
-
Quality control of technical development
-----------------------------------------------
+----------------------------------------
The PyPy project will ensure quality by a variety of means. On the
grand scale, the involvement of excellent researchers ensures that the
@@ -507,7 +471,7 @@
standards.
Additional Quality procedures
-++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
The project manager will circulate a draft Quality Management plan for
the project prior to first Project Meeting and and then present it for
@@ -528,14 +492,8 @@
- Evaluation routines
- Specific responsibilities within the project
-:DELETE:BEGIN
-
-B 5.6 Communication and reporting
-
-:DELETE:END
-
Communication and reporting
----------------------------------
+---------------------------
The project process will be reported as follows:
@@ -586,7 +544,8 @@
We will present multiple reports and scientific papers on major
conferences such as EuroPython (Python's european community
-conference), OSCON (Open Source Convention), PyCon (python developer
+conference), FOSDEM (Free and Open Source Developer European Meeting),
+OSCON (Open Source Convention), PyCon (python developer
conference) and to domain specific audiences such as embedded device
developers.In a later phase of the project the PEP (Python Enhancement
Proposals) procedures may be implemented. This is the standard
@@ -595,15 +554,9 @@
proposed Enhancement and provides an rationale. However, such a formal
method will only by required when the project reaches the point where
users begin to rely on aspects of our implementation.
-
-:DELETE:BEGIN
-
-B 5.7 Consortium
-
-:DELETE:END
Consortium
-----------------
+----------
The consortium consists of the following members:
@@ -620,46 +573,18 @@
(FIXME: Alastair - something we should mention here about the agreement?)
-:DELETE:BEGIN
-
-B 5.8 Ip
-
-:DELETE:END
-
Management of Knowledge and Intellectual Property
--------------------------------------------------
Every contributor is fully responsible for not introducing program code
which might infringe third party copyright or patents for that matter.
Every contributor agrees to license his contributions under a MIT-style
-license (approved by the Open Source Initiative)::
-
- The MIT License
-
- Copyright (c) <year> <copyright holders>
-
- Permission is hereby granted, free of charge, to any person
- obtaining a copy of this software and associated documentation
- files (the "Software"), to deal in the Software without
- restriction, including without limitation the rights to use,
- copy, modify, merge, publish, distribute, sublicense, and/or
- sell copies of the Software, and to permit persons to whom the
- Software is furnished to do so, subject to the following conditions:
-
- The above copyright notice and this permission notice shall be included
- in all copies or substantial portions of the Software.
-
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
- OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
- THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
- DEALINGS IN THE SOFTWARE.
+license approved by the Open Source Initiative and the Free Software
+Foundation. See section 3.
The public availability of PyPy's source code at all times on the basis
on such an open and commercially exploitable license stipulates exchange
-of ideas, contribution to the project and reusing all parts of PyPy from
+of ideas, contribution to the project and reusability all parts of PyPy from
the start.
In return, this provides the developers with fast feedback and
More information about the Pypy-commit
mailing list