Pierre van Rooden wrote: > [EMAIL PROTECTED] wrote: > >> Changed it back, decision was made in march by security project to use >> this security in the cvs. > > > Were is that decision? I don't see it on the security project page. >
Sorry my mistake.....I have to update the page with recent information. > Anyway I don't think this had a vote - and changing behavior (such as > changing the default security) needs a vote. Hmmmm....I thought decisions made in a project didn't need a vote.....only to be documented (I know.... :( ). If somebody has a problem with it it can be discussed and voted about if necessary? > As I said before (in march, too), I don't feel like changing the > security system every release, especially since it seems to me that the > cloud security does not fulfill that role well. > > I changed the security back because I was under the assumption that the > security change was for test purposes - a temporary change. Since we > want to start on the 1.6 release I changed it back to context. > Gerard (project leader) corrected my comments but didn't reverse the > change - so I guess the action was justified. > > I would like to have the security system changed back to context - as I > said, it would be nice if the configuation stayed stable between > releases for a change. > What do others think? Which security-implementation must be made default in the next release? Gerard
