Chatted with a lot of people, seen many, different development models, went
around, asked, talked, and I believe I have a pretty decent picture, and
maybe even a solution...
So the major topic of discussion is that I perceive a substantial difference
between being able to commit code to a CVS
+1.
Another example if I could. The job role of 'Java admin' is growing more
and more at companies. Developers shouldn't be adminning things, but would
you have your unix or oracle admin be the admin of the Java side with zero
Java knowledge?
Jakarta houses the 'Java' community at Apache but
-1
If someone doesn't want to be involved in the voting - he can do exaclty
that, abstain. If someone doesn't want to support a particular release -
he can abstain from the release vote( or vote +-0 ).
If you spend time and write code for a project and are willing to
maintain/support - and if
Henri Yandell [EMAIL PROTECTED] wrote:
+1.
Another example if I could. The job role of 'Java admin' is growing more
and more at companies. Developers shouldn't be adminning things, but would
you have your unix or oracle admin be the admin of the Java side with zero
Java knowledge?
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I do agree ( and I advocated for this a lot ) on lowering ( or
eliminating) the walls between projects, so jakarta commiters can commit
code in any jakarta project ( subject to the normal project rules ).
Some people didn't agree with that even for
On Sat, 25 May 2002, Pier Fumagalli wrote:
If you are a commiter - you have the same rights with all other commiters.
If you don't want to exercise some rights - it's your choice.
Hola, you tend to forget a part I'm stressing out quite hardly... It's not
only rights... It's also dues,
