php fundamentals bbq notes

[philipnorton42]

Hi all,

These are the notes I took during the discussion of php fundamentals
yesterday. There are some points missing, but I think the core details
are present.

I think we still need to decide on the nomenclature of the system. I
think that if we are pulling a lot from nvq then we can use that sort
of naming for levels, modules, performance criteria, tasks etc.

Action points are at the bottom :)

Great seeing everyone yesterday, lots of interesting things talked
about and I think we have a clearer picture of the sorts of things
that we want to achieve from this.

Speak soon.

Phil,

-----------------------

Need some sort of motto or easy description to let people know what it
is an why it is important.

Core set of materials that help professional development in the
digital/php industry.

Ultimate aim is to be an nvq course that can be of benefit to the
person and interest to the employer looking for people to employ. Can
also act as an nvq qualification by getting students to provide
evidence and using accessors to access that evidence.

Buddy scheme like php women, essentially called apprenticeships.

This can go towards a portfolo of evidence for what has been learnt
throughout the process of the persons career.

The nvq should have 3 levels.
beginner - level 1 == nvq level 2
day to day php dev
able to do the work
intermediate - level 2 == nvq level 3
senior dev
more aware of the surrounding technologies
advanced - level 3 == nvq level 4
software team leads
management orientated
interact with clients a lot more than previous levels
planning - ie proactive rather than reactive

To progress into level 3 you have to mentor a level one and level two
people
and also to contribute to the site in some way - wirting articles
and stuff

Theory and implementation as different parts of modules

Points system
- Number of modules in each level with a number of points
- To pass a level the person must pass a number of points

Checklist format for people to see how they are progressing through
the course/modules.
Methodology continues on from this checklist

Moodle
- for the core material
- further reading or outside links to anything relevant - ie google
videos or whatever
- external material is reveiwed to make sure it is still valid

wiki
- Stores all of the reference material related to each module.
- allows references and further reading for each article

All material needs to be reviewed every once in a while
Once the content is "good" it can be moved into the moodle cms
Original copy stays in the wiki - robots.txt to stop it being
indexed?

Content (ie practical articles)
Stored in a non-editable format.
Authors who contribue must agree to certain things
permalink
copyright licence
At the bottom of each article page we will put contribute or
suggest extra information - this will link through to the wiki
Working groups should be set up for each section

Use openID or facebook connect for one user sign in.

Area of the site that will publish a public profile so that the person
can link to it in order to show what they have done to the world

Community - how to be a part of it, why it's important


Actions:
rob - install moodle
stewart - Convert the mind map into a bulleted list of items.
all - find out about moodle and what it can do.
public facing content - article pages
design courses
Area of the site that will publish a public profile so that
the person can link to it in order to show what they have done to the
world
openID / facebook connect for login