I just think... trying to persuade people like that is very needy.
Ralph (Goers) doesn't give me the impression like he's needy like that ;-).
It is clear that the new version is a bit out of tune with the goals
these other projects might have. The requirements for a logging package
should be a lowest common denominator thing. If the product is good, the
other projects should notice anyway and take notice themselves. I would
focus on documentation and clarity. You're a bit at odds with the times
I think. Do you have the interests of your users in mind, or of someone
else? That's what makes it hard to give a recommendation because it's
just impossible. I mean "to become more popular". If you feel the need
to advertize or say "hey, don't forget about us" so badly, that just
means....
Well anybody can figure that out for himself I guess. But I was looking
at a topic called Update trunk to Java 7 from last May and it didn't
seem like their was an urgent need to do so.
Well it means you are on the wrong tract or not feeling confident.
Maybe you really feel like you need a call for attention, but.... ... ..
. . . . .. .....
Everybody already knows you lol. Your name is well-known. It just seems
like everyone is stuck using 1.2. Stuckerdiestuckstuckstuck. You might
want to send out for an honest appraisal or feedback.
Ask the question of whether Log4J 2 meets their goals. Ask the question
of whether 2.3 meets or met their goals. Ask the question of whether 2.4
meets or will meet their goals. Ask what they want from a logging
package. Don't forget to mention the issues: Java 7. Public vs. Core --
do they like that? Are they impressed by a separation of public versus
implementation API? If they have experience with the product, do they
feel the need to use Core functionality that is not normally directly
accessible from Public?. Did they feel their needs were respected when
the move to 2 was made? Do they feel the EOL of v1 has been a necessary
or required or helpful thing?. What are their needs and interests? How
do they feel about having to use two jars? I would seriously consider
asking these questions, all of them.
So don't ask for uptake, ask for feedback. I think that is the best
suggestion or advice I can offer. Ask them whether you are on the right
path. Ask this of your fellow Apache projects. Do that and you will do
well, or better, in the future. If such a thing as 'better' would exist,
but you can always do better than what you were before.
And that's true of everyone everywhere. That's just true of life.
Regards, B.
Op 14-8-2015 om 23:34 schreef Gary Gregory:
Something to think about after we get 2.4 out the door...
Do you think it appropriate for us to do some kind of outreach to
other Apache projects and say "hey, about about use log4j 2?"
Gary
--
E-Mail: [email protected] <mailto:[email protected]> |
[email protected] <mailto:[email protected]>
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
<http://garygregory.wordpress.com/>
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
