I would have to agree here.
Geeklog has allot to offer, when you simply compare it to e.g. Wordpress then Geeklog comes with allot more out of the box. And if you indeed keep the focus on security then it has a pretty firm statement which sets it apart from all the other Blog / CMS tools out there.
I wouldn't know what kind of teams there should be, I guess this could be an example:
- Head: Person overseeing the entire project.
- Members. Maybe split it up in several parts, e.g. certain members being responsible for specific plugins etc.
(I have no idea how this is right now, so I don't know how structured you can make this at this very moment)
- Head: Person overseeing everything related to communication.
- Marketing department: People that simply get people to make reviews on Geeklog, get it into the news, persuade potential users that Geeklog is tha shit, etc.
- News department: People that post all the news on the Geeklog site based on what the developers are working on, what positive news there is from Markting, etc.
- Forum watch: Moderator task force. (answering questions, keeping the forums in shape, poking developers that there's a tricky question, etc. ^_~)
- Head: Person overseeing the entire documentation proces. (not sure to what extend though, maybe at first documentation for the regular users and more advanced users but not yet developers?)
- Members: People responsible for pieces of documentation, they contribute to the wiki or find documentation elsewhere and contribute it that way.
(not sure how to fill this one in yet either.)
MT (Management Team)
- The big boss. (assuming he's at the head of everything and oversees the departments via the department heads)
- All department heads.
I would like to help but not sure in what area.
"The Linux philosophy is 'Laugh in the face of danger'. Oops. Wrong One. 'Do it yourself'. Yes, that's it." - Linus Torvalds