On Mon, 2002-09-30 at 16:30, Pierre van Rooden wrote: > > 1) This setting was there since: 2002/03/18 > And I have protested against that ever since - not that anyone listened. Well, i guess nobody cared, or you didnt protested strongly enough, this doesnt give you the right to change it in cvs
> > 2) This change was made at that point by the security project (correct > > or not correct, imho that doesnt matter) > The decision was not clear imo - and since this changes the default > config (i.e. how mmabase works), it is not a project decision imo. > Whether it is correct DOES matter, IMO. I think it is. The project make certain decisions, they can be correct/incorrect, if you want to have influence in a project, join the project. We are now at a later point in time, and we can decide, to change this settting. It still doesnt give you the right to change it in cvs. > > 3) Changing something in cvs since in you dont like it, is not the > > correct way. Please notifiy everyone by putting it on the developers > > list. > As I wrote, I was under the impression that this change was temporary - > the security project is finished, IIRC, so I changed it back. > Anyway, as there was no vote, the change was not valid, and therefor > could be rolled back. First are you saying this as a developer or as an mmc member? Second: it was done in the running time of the security project, by someone of the security project, and no comments were placed on the cvs not the development list. IRCC: The desision we made in the security project was to change this setting to cloud security, since easier to understand, so more developers would use security and when the release would be there (refering to 1.6) we could review if this was a correct descision, to change it to cloud security. Does this give you the right to change it -back- as you name it? (did you have a vote? and what is the expire time to get rolled back?) > > 4) If we want to change it to another implementation, it is possible, > > but there should try to start discussion on developers list FIRST(or > > post a hack, etc...) > Which should be started by the project - not by me. The project decided that it should be changed. > My view is that: > a) security systems shouldn't change every release > b) the cloud security is, imo, not really finished - it seems a rather > weak and slow system, though I may be mistaken of how it works. I > foresee that people will not be pleased with it and we will have to > replace it _again_. Which is why I don't want to replace the system _now_. > c) I don't want a system that installs builders I have difficulty > getting rid off when I don't want to use it, rather than placing an xml > file I can delete with no problems. > d) If the one problem is to tell a user where to change the admin > password, I think that - again - we are lacking documentation, NOT a > properly working security system. Above is your personal view, but it still doesnt give you the right to change it. If you want to change this, please post an email related to this to the developers list instead of changing it in cvs. Furthermore, please specify when something decided by the MMC or if something is your personal view. -- Eduard Witteveen Systeem Ontwikkelaar Publieke Omroep, Gateway C Kamer 101 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
