[Numpy-discussion] Meta: help, devel and stackoverflow

srean srean.list at gmail.com
Thu Jun 28 22:50:18 EDT 2012

I like this solution and I think ask.scipy.org can be revived to take
over that role, but this will need some policing to send standard
questions there and also some hangout time at ask.scipy.org.

I love the stackoverflow model but it requires more active
participation of  those who want to answer questions as compared to
mailing lists. This because questions not only do not come to you by
default but they also  get knocked off the top page as more questions
come in. Something to watch out for though I believe it wont be as bad
as the main SO site.

Meta^2 I have been top posting with abandon here. Not sure what is
preferred here, top or bottom.


On Thu, Jun 28, 2012 at 8:52 PM, T J <tjhnson at gmail.com> wrote:
> On Thu, Jun 28, 2012 at 3:23 PM, Fernando Perez <fperez.net at gmail.com>
> wrote:

> I'm okay with having two lists as it does filtering for me, but this seems
> like a sub-optimal solution.
> Observation: Some people would like to apply labels to incoming messages.
> Reality: Email was not really designed for that.
> We can hack it by using two different email addresses, but why not just keep
> this list as is and make a concentrated effort to promote the use of 2.0
> technologies, like stackoverflow/askbot/etc?  There, people can put as many
> tags as desired on questions: matrix, C-API, iteration, etc. Potentially,
> these tags would streamline everyone's workflow.  The stackoverflow setup
> also makes it easier for users to search for solutions to common questions,
> and know that the top answer is still an accurate answer.  [No one likes
> finding old invalid solutions.]  The reputation system and up/down votes
> also help new users figure out which responses to trust.
> As others have explained, it does seem that there are distinct types of
> discussions that take place on this list.
> 1)  There are community discussiuons/debates.
> Examples are the NA discussion, the bug tracker, release schedule, ABI/API
> changes, matrix rank tolerance too low, lazy evaluation, etc.   These are
> clearly mailing-list topics.   If you look at all the messages for the last
> two(!) months, it seems like this type of message has been the dominate
> type.
> 2) There are also standard questions.
> Recent examples are "memory allocation at assignment",  "dot() function
> question", "not expected output of fill_diagonal", "silly isscalar
> question".  These messages seem much more suited to the stackoverflow
> environment.  In fact, I'd be happy if we redirected such questions to
> stackoverflow.  This has the added benefit that responses to such questions
> will stay on topic.  Note that if a stackoverflow question seeds a
> discussion, then someone can start a new thread on the mailing list which
> cite the stackoverflow question.
> tl;dr
> Keep this list the same, and push "user" questions to stackoverflow instead
> of pushing them to a user list.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion

More information about the NumPy-Discussion mailing list