Matt -
I would like to put in my two cents on this issue. I don't know
the complete background from your perspective, but I'd like you to
consider these points:
Open source is no different from other aspects of life where people
have to work together in voluntary service. People need to respect
each other, and tread gently on other peoples work.
The best person to fix a bug is the programmer that created it.
Control over code is not necessarily about posession. It should be
about responsibilty. If I write something, and someone else changes
it right away, then neither of us are really responsible for how it
works after that. Both can walk away.
Everyone will have their own preferences, and everyone needs to
respect the work of others. If a developer changes someone elses
code, it should be for a compelling reason.
It should never be because you would personally use a different
style. Every successful developer has a personal style. For
example, if you would prefer to use "echo" instead of "print", or
"||" instaed of "or", then do so, but don't try to change the work
of other people to suit your yourself.
Every programmer can learn to read a variety of styles, but no
programmer can make the world conform to his/her own personal
preferences.
Bob Treumann
On 25 Feb 2002 at 8:44, Matthew McNaney wrote:
> Good day,
>
> As phpWebSite continues to grow and we add more developers, it is import=
ant
> to remind people of how CVS currently operates.
>
> First, if you commit something, it should work. If it doesn=92t work, th=
en
> someone might fix it. When you commit you are releasing it to the world.=
If
> you have a problem with someone repairing your code, don=92t commit. If =
you
> want to commit and still do not want people to touch your code, then mak=
e
> sure it has absolutely no bugs. I understand bugs can get by you, but I =
am
> weary of the possessiveness people have of their code. If you disagree w=
ith
> this, then you shouldn=92t be in Open Source.
>
> Second, if you are changing someone else=92s code, you should not change=
the
> functionality of the code without consulting the developer. Bug fixes ar=
e
> open season.
>
> Third, before you commit, update. Roll back is a bitch.
>
> If you have any problems or questions about these standards or anything =
or
> anyone else, contact Brian (br...@tu...) or myself directly.
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
>
>
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
|
