>
> Heh.  You just said we have a very active community.
>
> While I do like Stack Overflow for many things, it's not a true way of
> building a community.  It's a way of asking questions.  (Yes, this is just
> my opinion - not meaning to start a flamewar).  We have a vibrant community
> here - I don't think the mailing list is limiting the community.
>
>
I think but it's just an opinion, that the need of subscribe to a mailing
list is a little barrier. Some people won't do the effort which means less
interactions.


> Plus, mailing lists are still THE way to communicate in open source.
>  Especially is this true with Apache projects.
>
>
> > Moreover, research on old messages are poorly referenced. I
> > have recently experienced it one more time  during the migration of my
> > project on Wicket 1.5. The solution to my problem has already been
> > discussed
> > and resolved but it took me a long time to find it. Why not drop this
> > mailing list and discuss all questions
> > onStackOverflow. The business community would be more visible.
> >
>
> How can we quantify such a statement?  If you can provide some kind of
> proof
> that it's easier to find an answer by searching SO rather than mailing list
> archives, we could look into alternatives.  But such a statement just isn't
> easily (if at all) quantifiable.
>
>
Difficult to quantify but the nable mailing list is flat. There no way for
google to know which question is more important. For the reader it's not
very obvious neither. In a system like StackOverflow, the votes on
questions, on answers, the use of comments rather than answer allow the
filtering of the noise. I think the links beetween questions take the votes
in count and as a result google
shows you rapidly the best question/answer. Moreover when you are reading a
question, you see the other questions in relation.
I don't exactly how SO works but I find it very very efficient for me (not
for wicket questions ;) )

> Source management and bugs are also outdated. The version on github is
> much
> > better.
> >
>
> Github is awesome.  I don't care about the issue management on it.  JIRA
> has
> a ton more features and support.  It works for us.  I think that we would
> like to move to git at some point - but it's not (yet) supported for all
> projects at the ASF.  There is a public beta running of git for one project
> at the ASF right now.  If it succeeds, I think we'll be one of the first
> projects to switch as soon as they make it available to all projects.
>
>
Good news.


>
> Thanks!  Hope to see you around this antiquated mailing list :)
>

:)

Of course!!!

Reply via email to