> Quite honestly, I don't know 100% what Costin seeks. I thought my #1
:-)
Mea culpa, I should stick with writing java, it's easier than english :-)
> What I *believe* is that what Costin seeks is different from what I
> seek, simply from the direction the result is approached, and with the
> difference that I don't think that Costin values the 'productization'
> initiative, as his driving interest is different.
I do value "productization", but it's not my itch. I'm not saying your
proposal or itch are wrong - I was trying to find if this project can
solve both itches.
I would be happy to see what you propose, and I'll probably contribute (
if I find time ) in some areas, but I think there are multiple problems
and for me the most important is the lack of cooperation between projects,
not the lack of code.
It's apple and oranges - we don't have to argue about that but to accept
that both are good fruits.
> I want to ensure that we can bring things out useful things, make them
> easy to use, install, understand, and find for both the Order(10^2)
> people that are Jakarta developers, as well as the Order(10^whateveR)
> developers that are making server/servlet software/solutions with Java.
I would be happy to see something around 3 developers reviewing and voting
for each component, and 2-3 developers from various projects using the
component monitoring from time to time and making sure it works for their
need.
Getting 10^1 developers for a component is beyond my most optimistic view.
( tomcat as a full project has 6-7 active commiters - and I haven't seen
more then 3 focusing on the same sub-component. 2 is lucky in most cases )
> Fundamentally, what I am trying to ensure is that the productization /
> projectization doesn't get lost in this scuffle.
+1 on that.
What't I'm trying to ensure is that the product doesn't become more
important than the community, and enough people feel "part" of each
component community.
Costin
