> From: Loren Wilton [mailto:[EMAIL PROTECTED]
> I expect (and this is personal opinion, I'm not an SA dev) > that the rules subproject will sooner or later consist of > annointed developers that have been granted checkin ability > on the source base, and the project will also accept > contributions from people that aren't developers. These > contributions may be accepted as they are, or perhaps > partially or completely reworked. Or may be rejected or ignored. > > Which is really no different than any open source project. > People start contributing to the project. At some point the > developers say "hey, this guy is doing lots of good stuff. I don't really need check in or such now -- I really just want to make sure that to be included in the loop and able to read the messages and see the rules in development so that a place to help will be found. Or as ideas occure to me, I will have the background information to make them relevant to what else is happening. > Maybe we should just make him a developer and save ourselves > the effort of having to check in his patches!" So they ask > the person if they want to be a developer, and if they do, > they are in. Right but as the discussion thread was proceeding there is one stark difference with other projects: the need for secrecy that was explained. Normally in an open source project anyone who wishes to listen, lurk, and read or even use the bleeding edge code is free to do so to learn and get into the frame of the project. That cannot be true (to the same extent) if there are security layers that make such gradual involvement difficult. -- Herb
