OK folks, I'm out for a bit as I have a personal trip and a spike at
work which will prevent me from arguing about try-with-resources for a
while. Two thoughts to part on.

 * I'm pretty sure jclouds wants folks like me to participate. Please
make that easier and less stressful, monotonous, or otherwise WTF.

When we create long-term branches before identifying any user-pleasing
features, and then don't backport anything, folks like me are
backporting MoreObjects to Objects, or hunting in git history vs
looking at how to fix real problems or realize real features. Please,
find a way to end the "I forked for try-with-resources" madness. Even
if you hate the idea of android, do it to keep your other devs
productive and to stop the bug port gap. Fork when you've found
something meaningfully incompatible.

 * When we started jclouds, it was all about the users. Find them again

As a project, we should never justify something by saying an account
with 200 followers tweeted it and no-one complained, or some email
that was mobbed by a dev pile-on only had one user say "meh". There's
a real, but solvable engagement problem. Please don't perpetuate this
disconnection. Engage and ask users what they are doing. Ask them to
reply to mail threads. Don't pile-on to user discussion.. allow folks
to reply, and actively nudge users who aren't replying to either reply
or send you text that they reply with.

Hope this helps, and see you around.
-A

Reply via email to