Looking at the area51.stackexchange.com website, it looks like they consider a healthy stack exchange site to generate 15 questions and have roughly 1500 visitors a day. I don't know how big the PyCUDA community is, but I would guess it's too small to generate this amount of traffic.
My two cents: I think that stack overflow is the right place to ask programming questions about PyCUDA (eg. How do I use this or that? Why am I seeing this error? etc.) You can add a "pycuda" tag, and then these are easily found/indexed/searched. You can even get these questions through an rss feed: http://stackoverflow.com/feeds/tag/pycuda. I think the mailing list is more useful for the development of PyCUDA and any sort of general discussion that doesn't have a definite answer (like this thread itself!). On Fri, Mar 16, 2012 at 2:45 PM, Ely Spears <[email protected]> wrote: > My thinking was that it's a bit more cumbersome to look up archived PyCUDA > mailing list items, whether online or in my gmail search, to re-read them > for their applicability to my problem, and to parse the code discussed in > them. With a stackexchange, it's usually much easier to locate items that > are relevant from the past if I encounter them later, and since the code is > formatted with coloring and certain syntax niceties, just a lot easier to > read. Multiplied across dozens of mailing list entries that become relevant > to me, these extras go a long way. None of them are strictly necessary of > course, but why not have them when it's as easy as responding on > stackexchange instead of via email? > > It is true that we can always just use stackoverflow. But the main point > was trying to get the very talented folks who answer things in this email > format to instead make cleaner, easier to read/find/index/search answers on > a stackexchange (which could just be stackoverflow). The way I see it is > there are two disparate answer communities, this mailing list vs. gpu > related tags on stackoverflow. I feel like it would be so much more useful > going forward if they were all just in one place, and stackoverflow seems > like the better place. > > Since it doesn't seem like most folks care very much and that some people > actually prefer the email interface, perhaps I'll just make my own bookmark > website or something that attempts to index the pycuda mail digests by > their specific contents rather than just their titles or something. > > --Ely > > > > > On Thu, Mar 15, 2012 at 3:17 PM, Eli Stevens (Gmail) <[email protected] > > wrote: > >> Slightly off-topic: what's the benefit of having a dedicated stack >> exchange, vs. using Stack Overflow? I can only think of downsides >> related to fracturing the existing set of answers and responders, esp. >> for ones that aren't directly related to PyCUDA. >> >> On topic: I don't see a reason to not just use Stack Overflow. >> >> Eli >> >> On Thu, Mar 15, 2012 at 11:31 AM, David Mertens >> <[email protected]> wrote: >> > Being a Perl guy that mostly follows this list. You can probably count >> the >> > number of Perl programmers that use CUDA or OpenCL in their scripts on >> one >> > hand, but I happen to be one of them, and I would prefer a non-Python >> > centric topic, like plain CUDA, or CUDA/OpenCL. On such an exchange, >> > questions about PyCUDA would be fine, but keeping the forum open for >> > PerlCUDA, RubyCUDA, etc, would be appreciated, at least by me. :-) >> > >> > On Wed, Mar 14, 2012 at 9:03 AM, Ely Spears <[email protected]> >> wrote: >> >> >> >> I don't know if this has been brought up or discussed before; my >> apologies >> >> if it has. It seems like a natural thing to do as more and more people >> are >> >> developing with PyCUDA. It seems like it would be an easier place to >> manage >> >> questions, rather than reading the back-and-forths in email digests. >> >> Potentially it could even be a GPU stackexchange to open up questions >> about >> >> regular CUDA and other paradigms. Thoughts? Immediate strong >> objections? >> >> >> >> If we want to do this, the right place to inquire is >> >> < http://area51.stackexchange.com/ >. >> >> >> >> >> >> -- >> >> Ely M. Spears >> >> --------------------- >> >> http://people.seas.harvard.edu/~ely/ >> >> >> >> Harvard GVI Group: >> >> http://gvi.seas.harvard.edu/ >> >> [email protected] >> >> >> >> Mailing list: >> >> https://lists.seas.harvard.edu/mailman/listinfo/gv >> >> >> >> >> >> _______________________________________________ >> >> PyCUDA mailing list >> >> [email protected] >> >> http://lists.tiker.net/listinfo/pycuda >> >> >> > >> > >> > >> > -- >> > "Debugging is twice as hard as writing the code in the first place. >> > Therefore, if you write the code as cleverly as possible, you are, >> > by definition, not smart enough to debug it." -- Brian Kernighan >> > >> > >> > _______________________________________________ >> > PyCUDA mailing list >> > [email protected] >> > http://lists.tiker.net/listinfo/pycuda >> > >> > > > > -- > Ely M. Spears > --------------------- > http://people.seas.harvard.edu/~ely/ > > Harvard GVI Group: > http://gvi.seas.harvard.edu/ > [email protected] > > Mailing list: > https://lists.seas.harvard.edu/mailman/listinfo/gv > > > _______________________________________________ > PyCUDA mailing list > [email protected] > http://lists.tiker.net/listinfo/pycuda > >
_______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
