Joachim Draeger wrote:
I think there is something substantial going wrong. We are loosing our
main code comitter, and I guess many people are feeling insecure, like I
do at the moment. We have to prevent that!
I believe you're referring to me ;-)
To make it clear and hopefully make you and the community feel less
insecure you are not loosing me.
I am a James PMC member and I'm willing to accomplish my duties under
that hat. I will try to keep my PMC role and my contributor role separated.
As contributor I have my needs and my ideas/plans for James and I can
spend a bunch of hours per week working on that goals.
I think that my work as contributor/committer in the last year has been
useful for the community and has been the bigger step toward the 2.3.0
release.
As contributor and user I'm not directly interested in the 2.3.0
release, while I am interested in a release soon as PMC member.
Generally speaking if the James community grows I'm happy under my PMC
role, and if the community grows because James codebase become better
(to me this means: more modular, more understandable by the community) I
am happy as contributor too, because this increase the probability I
will get something useful back from the community.
As contributor I'm a bit pissed off that lately I receive
"alerts"/"complaints" every time I commit or I try to commit something.
I also have lost my faith in discussions because I think that the people
that have enough understanding of the whole James architecture and
details does not have enough time to sustain a good technical
conversation and the result is that we talk of non-concrete changes or
we never finish a concrete discussion. I thought that this didn't worked
and I started applying few of many changes I did in my local james,
starting from the easier, and reapplying them from scratch (the second
time you implement the same thing you always produce better code).
This worked for a while and I thought it worked fine when I've been
nominated PMC committer.
Now something has happened and people started hasking me for too much
discussions and I simply think I have lost too much time in discussions
that produced nothing useful to James. This is my spare time, I want to
do things I like, and producing code is one of them.
Even if I'm not interested in IMAP and never used file based
repositories I worked on the latter and I said I'm willing to help with
the IMAP roadmap because I understood I was probably the "missing block"
to create and coordinate a group working on that (in terms of: time +
james internal knowledge + repository rights).
Imho for IMAP, and even for POJOs we need to apply MAJOR refactorings
(if we want to avoid loads of workarounds).
In the long term planning there are things like JMS, repository "urls"
and other stuff that needs major changes under the hood.
I currently simply don't understand why "refactoring" has been
classified as "bad thing".
Everyone agreed that we need POJOs but everyone now say "if ain't
broken, don't fix it". Is Avalon broken? No, we have no Avalon related
bugs in our JIRA, so everyone is not so clear on the goals.
Everyone here fears that my work will delay the next release and I don't
get why. I would like to have concrete examples where my work in the
last year has delayed the release of the next release. Imho the current
trunk and the current v2.3 branch is already more stable than any James
stable release we have out there.
That said I will actively partecipate in the mailing list, and I will
actively cast my vote on any decision, but I will not commit new
features or refactorings until I will have solved my misunderstandings
with the "James goals". I will keep working on James and maybe
submitting JIRA issues and attaching my work while my local version and
james trunk will be similar.
If nothing happens before I will try to define some clear requirements
to a better collaboration and prepare few clear votes on that.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
