Document describing Grok development process

Registered by Martijn Faassen on 2007-03-20

We need a document describing to developers interested in extending the Grok core or writing Grok extensions what the process is. This is especially important for the core. What would someone need to do to add something to the Grok core? It doesn't need to be very formal (in fact shouldn't be), but it might include discussing it on the mailing list (or putting summaries of irc conversations there, to keep others in the loop), and posting new issues on launchpad.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.