On Wed, 15 Apr 2015 17:55:19 +0200, Robert Krüger <krue...@lesspain.de>
wrote:
Understandable. IMHO a certain "seriousness threshold" to reduce the
noise
makes sense.
I was thinking on a score system such as the one at StackOverflow, but I'm
not aware of any support of Atlassian.
What if you at least had a policy where someone in your team
can propose people they know from the mailing list for a while for
accounts? I don't think what's needed is to have a completely open system
with one-click self-registration but don't draw the line where you draw
it
now, which means you're missing qualified input from people who are ready
to invest qualified time (e.g. to build test cases and good descriptions
of
issues) but do not submit patches.
I would add that having a corporate collective account could probably
help. I'm thinking of a case in which there are a couple of dozen
developers from the same corporate that could share the same email alias.
Even in this case self-subscribing wouldn't be needed, actually it might
make sense to have a control process to be sure that the corporate account
is official, I mean the corporate is in charge for it.
--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - fabrizio.giud...@tidalwave.it
