[ZF] Re: Status update for documents

[Christian Theune]

Hi,

any comments? I'd like to proceed and get those things done too, but I
need feedback for this to proceed.

Additionally, I noticed that I'm still not understanding the actual
problem of the contributor vs committer member issue. I think we forgot
to revisit that during PyCon. Can someone point out the problem and the
general idea of a solution so I can make adjustments to the docs?

Christian

Am Donnerstag, den 19.04.2007, 19:16 +0200 schrieb Christian Theune:
> Hi,
> 
> sorry this took so long again, but loosing my changes in the last
> open-office struggle multiple times didn't motivate me very much. :(
> 
> However, I received a base-line version of the by laws as restructured
> text and replaced the open-office by laws.
> Then I went ahead and checked in my changes regarding the removal of the
> ZMO.
> 
> I have a few questions before I can finalize the draft version:
> 
> - We wanted to make the ZMO a committee instead.
>   I guess that it's a standing committee. 
> 
>   Is it going to be a committee of the board or of the
>   Membership-at-large, though?
> 
> - The original ZMO had quite a few responsibilities and
>   properties. I'd like to boil them down. 
>  
>   The original list was:
> 
>   - directed and established by the chairman? (rather not, better ...)
>   - leading the zope platform development and
>   - execution, definition and maintenance a development process
>   - produce a roadmap
>   - interact with standards organisations
>   - resolve conflicts, establish working groups
>   - provide development infrastructure
>   - ensure the use of open source rules of engagement
>   - enforce foundation policies and provisions (bylaws, membership agreement, ip policy and other policy documents)
>   - interact with membership at large by providing zope platform plans, status updates and by soliciting requirements and feedback
>   - (conducting academic and research community outreach)
>    ­ (conduct zope platform marketing)
>   - (assure the availability of enablement services, including education and training programs)
> 
>   As the development committee should work on making Zope (and Co)
> better, I don't think it should do:
> 
>   - do marketing
>   - do enablement services
>   - enforce foundation policies
>   
>  Maybe some of the other points can collapsed a bit to be less
>  verbose?
> 
> Christian
> 
> PS: If you think this should be discussed on the foundation list, not
> the board list, please tell me.
> 
-- 
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/foundation/attachments/20070422/80007698/attachment.bin