Chippy's thoughts on the AGM:
I think I'd better say out front that I have been thinking about how to
integrate Paneris and the PMS within a framework using libraries derrived
from the Iglu ones. Many of my technical thoughts are based on this. I
feel that this would make an ideal exercise for extending the libraries.
It would also give us a "Paneris Project" which might help in the discussion
of roles (or not).
We can do it quickly in the short-term, but to get a good job done we
need to get Paneris using the template library, much of the code should
be modularised and we need something like Database.pl which handles .ini
files. It all comes quite easily if we reproduce the site structure in
the template directory. This allows us to have multiple templates for the
same script as happens on Paneris at the moment (when a template is requested,
the scripts look in the current directory and then upwards
until it finds one, sometimes getting the default template in the root
of the template directory). I can go on more about this, fi you like :-)
The rest are some of my thoughts on the agenda points. I think we should
either get an answer to these questions (which will appear in the minutes)
or send the discussion to the web where we can experiment creating a voting
system.
Business Stuff - A Structured Discussion covering the following
topics
-
Structure
-
Structure of Paneris is a co-operative of web workers creating a virtual
corporation. Each person can have different roles depending on the situation
(e.g. within different projects or within Paneris).
-
Adhocracy
-
People come together around issues to provide input and vote on decisions.
Questions include
-
Who gets a vote?
-
How do we count the votes (who "wins")
-
Openness
-
I'm not convinced that all openness is good in all cases, but it is a good
default.
-
I think we should be open with information they supply us with until an
organisation or person asks us not to be. I think we need to respect people's
veto on their information being public. I think we can insist that the
Paneris Core or Paneris Members (see roles below) don't have such a veto.
BTW, anyone know if we need to register for the Data Protection Act?
-
We have some responsibility to educate our clients that transparancy (all
relevant information is available to the project team) can help the implementation.
-
We need to think carefully about letting anyone alter anything on Paneris
and the PMS. I think that this will come out from thinking about roles
-
Flexability
-
We should have core Paneris rules/procedures, and others which can vary
from project to project (with Paneris defaults)
-
We should recongnise which procedures can be encoded automatically, and
which of those should be implemented, the others generally becoming procedure
documents or rules. If in doubt, wait until you do something 3 times and
then implement what you ended up doing!
-
Ethics
-
Aims and Objectives
-
Create the ultimate web development system (librares and code)
-
Create a web based project management, communication and documentation
system (The Paneris site)
-
Create and nurture a group of members
-
Roles
-
Within projects
-
leader
-
developer
-
graphic artist
-
partner e.g. keyhaven
-
client e.g. skyguard
-
contacts (3rd parties)
-
Within Paneris
-
"Core" or "Contributers" - contributers to "The Paneris project": development
or graphic design of the site?
-
Members - people who have worked on a Paneris (managed) project
-
Partners - people who "make the sale" (hopefully with Paneris input) and
ask Paneris to manage a project.
-
Clients - end customer
-
The next 12 months
-
Integrate Paneris and PMS using our web development system
Technology Stuff
-
templates
-
Should contain all formatting work.
-
transparent database access
-
We should also have transparent INI file access (for integration of Paneris/PMS)
-
how to support navigation
-
generic administration (of)
-
Database
-
Filesystem
-
Templates
-
Scripts
-
pluggable modules (customer tracking, ...)
-
move over SAP;