On 2005.02.09, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote: > I have the CVS write-commit privs, as about 58 other project members. > I'm also convinced that some RFE's sitting in the queue are of quality > to be included in the current dev branch. Yet, I'm not commiting them. > Why? Am I lazy? > Well, I'm not. I'm just *afraid* that this will/might/could collide > with the global project direction and doing this will result in my > additions being backed-out out of the repository, leaving me out in > the rain with lost time and shattered self-confidence. > And guess what? I do not know the direction! Isn't that absurd? > Am I being too paranoic?
I don't know what I can say that'll make you believe me, but I am totally hoping you and others will commit changes. If there's problems with the changes, we'll discuss them. We'll work together to form a strategy to correct any real deficiencies either caused by the change, or illuminated elsewhere by the change. We'll continue to work together to improve the codebase. If a change-in-progress is holding up the release, we'll conservatively estimate what it'll really take to make things right, and if it's going to block the release, consider backing out the change to keep things moving forward. When I wrote the CVS Commit Guidelines on the wiki, it was serious. Everyone who has been given the authority to commit to CVS by being granted rights also has the responsibility that comes with it. If people start committing code that pulls the direction of the server in opposing ways, then we'll pause for a bit and discuss the problem. Lets get to the point where we've got enough committing going on to see if this problem ever arises. This has no dependency on knowing what "the" direction is -- suppose there is no one direction. What then? As long as everyone's individual directions can peacefully co-exist with all the other developers, who should care? Only when there's a conflict will we need to resolve the problem, and I don't think that's best done by pointing to someone's arbitrary "vision" and declaring "I'm right, you're wrong: the vision says so." However, I do understand the importance of having a general direction or vision for the project so I'll be working on one, but it's for guidance and not law. The direction of this project is all about where we ALL want to take it. The vision is only a statement or capturing of that collective sentiment at one point in time in the past. ... If you don't believe that I truly feel this way, then put me to the test. Start making changes. Start committing code. We'll deal with the real problems as, when, and if they ever come up. And we'll be mature about it and find the best solutions that we can at the time. And, in the end, if we discover this isn't the best way for the project to exist, we'll discuss it again and come up with a new approach. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
