CALL FOR:
Choosing a default security implementation for the next major release of
MMBase (1.6). There are 2 (3, but the 3rd one isn't going to be default,
because it only simulates the old security) different security
implementations, context and cloud security (for more information see
links section below).
Context security was the default implementation in the previous major
MMBase release. The securityproject has changed this default
implementation because it was needed by the distroproject to get a war
which can be installed without configuration that needs to be changed.
This was done without a vote, but becuase it changes the default
behaviour of MMBase a vote was needed.
In the mean time some discussion about the two different implementation
has accured in the devlist, so I'm not proposing the cloud security but
I'd like to ask you which one of the two must be made default in the
next release (and also in CVS-HEAD).
This is majority call, with a margin of 3 votes.
Please pay attention: two votes must be made: 1 for context security and
1 for cloud security.
LINKS:
Context security
<http://design.mmbase.org/testing/common/lastbuild/mmdocs/security/context-security.html>
Cloud security
<http://design.mmbase.org/testing/common/lastbuild/mmdocs/security/cloud-security.html>
START OF CALL: 2002-10-22 0:30
END OF CALL: 2002-10-25 0:30
Context security being default:
[_] +1 (YEA)
[_] +0 (ABSTAIN )
[_] -1 (NAY), because :
[_] VETO, because:
Cloud security being default:
[_] +1 (YEA)
[_] +0 (ABSTAIN )
[_] -1 (NAY), because :
[_] VETO, because:
Gerard
- Re: CALL: default security implementation Gerard van Enk
- Re: CALL: default security implementation Pierre van Rooden
- Re: CALL: default security implementation Michiel Meeuwissen
- Re: default security implementation Pierre van Rooden
- Re: default security implementation Rob van Maris
- Re: default security implementation Pierre van Rooden
- Re: default security implementation Eduard Witteveen
- Re: CALL: default security implementation Rico Jansen
- Re: CALL: default security implementation Wilbert Hengst
- Re: CALL: default security implementation Johannes Verelst
- Re: CALL: default security implementation Rob Vermeulen
