On 23/09/2010 08:37, Grant Ingersoll wrote:
Are devs who work on or use open source happier in their day jobs?
Tricky. For me, I started working on open source as a hobby. I really
enjoyed my previous (non-OSS) job but it is hard to beat being paid to
do your hobby.
I can see this could be true
Bill Stoddard wrote:
Tetsuya Kitahata wrote:
ABOUT APACHECON ASIA
If China would be impossible, Tokyo would be also nice.
And Bali (near Jakarta) would be attractive. 10th anniversary
and Jakarta's 10th anniversary --- BACK to the FUTURE!
CN has proven easier than JP. Again,
Robert Burrell Donkin wrote:
the documentation revisions seem just about ready now.
http://www.apache.org/dev/release-signing.html has been substantially
revised and new pages add at http://www.apache.org/dev/openpgp.html and
http://www.apache.org/dev/key-transition.html. i think most of the
Henri Yandell wrote:
+1, but
what I'd really like to drum up the energy to do is a Come develop
with the developers corner. In so much as I spend a decent amount of
every ApacheCon now working on a Commons release and being able to
pull people in and distribute out some JIRA issues
-Original Message-
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
The process at .../security/ answers parts of that question, but I
find some steps like the suggestion to obscure the commit that fixes a
vulnerability a bit awkward. One idea I came up with is to have a
Noel J. Bergman wrote:
Mark Thomas wrote:
Noel J. Bergman wrote:
what thickness of skin should be required of participants on our lists?
Thick enough to take to criticism, whether it be right or wrong, and
to respond in a positive manner.
Personal attacks of any form or degree
Noel J. Bergman wrote:
We may disagree as his clueful:clueless ratio, but we can agree that he is
just snarky. But on a related note, what thickness of skin should be
required of participants on our lists?
Thick enough to take to criticism, whether it be right or wrong, and
to respond in a
Jean T. Anderson wrote:
I think ignoring is an excellent tactic for a developer's list. I worry
that isn't strong enough for a user's list, but I also wouldn't want to
embark on a path that could backfire.
Not exactly the same situation as yours but one of our users went off
on one a few
