All Groups

replace Paypal module

the e-commerce module is complex and not working well. there is an alternative Paypal-specific module. Stuff I found recently indicates it is a better option for a subscription-only payments system. It is not perfect either and i have offered US$100 towards a bounty being assembled for a guy doing some enhancements to it there is also a separate donations module to cover off that aspect. still leaves the issue of payment for advertising and other "products" but the numbers of those may be small enough to handle manually???
18/4/06 Gordon Heydon, the developer, is persuading me to stick with it.  If I do, it will be MUCH easier to write custom code to automate membership processing so I'm swaying that way now.....

copy nodes to issues

this function is disabled, lest we generate another 300 project issues

IP Protection and Copyleft

Options for distribution and protection of Core Practice:


allows modification

Creative Commons

range of different licences depending on modification etc

Waived copyright

Effectively just an informal version of either of the above licences
E.g. FITS http://www.becta.org.uk/tsas/docs/fits_fits.pdf  

RADIX Group Model

RADIX defines the Data Model, names that are common across groups (0.n.n…), the Maturity Model and the Optimising Model. A Group may define a different version of any of these specific to their model, but this should only be done where absolutely necessary. General policy is to use a common definition of these across models.
RADIX Framework does not define the process model, but there is a generic design that should be followed, and adapted to suit the needs of each specific Group.
In general, the Group Process Model will have both of the following Disciplines (or sets of related Processes):


A subclass of Document. Workbooks supplement Guidance. They can be a document of any size or format that refers to a specific object and provides detailed information about how to implement it. There needs to be a corresponding 3.….12.1 Guidance that they supplement. Workbooks are provided by anyone. They may be placed in the public domain or offered commercially. They may be registered for a 3.….12.n OID, in which case they will be referenced in the 3.….12.1 document.


A subclass of Document.   The master description of the practices, the processes they describe, and all parts of the CoPr model for a Group, along with any other reference information for that group as desired. 


A subclass of Document. A sample document, usually associated with a Practice Guidance e.g. a sample Service Catalog or Availability Plan


Defines a practice that is used in a number of places. It is documented in its associated guidance. The technique object allows that guidance to be written once and used in many places. For example a Post Implementation Review.


A role is the job a person performs while owning a Process or performing a Practice. A person can have multiple roles, but they perform only one role at any one time, and only one person owns a role.

Remembering the small number of staff in SMEs and especially in VSEs we try to keep the role model simple, even though multiple roles can be mapped to a person anyway. We don’t want someone reading Guidance for 12 Roles to work out what they do.
ARCI matrices are too complex for Core Practice?

A Role describes a job that someone needs to perform. A Role can own some Processes and perform some Practices. A person can have multiple roles, but they perform only one role at any one time, and only one person owns a role. The Practices they perform are not necessarily part of Processes they own.

Syndicate content