[SciPy-dev] Summer Doc Marathon status report and request for more writers
nicky van foreest
Sun Jul 6 12:29:19 CDT 2008
Yesterday I sent a mail to the scipy-dev mailing list as a volunteer
to review. However, I have not received any mail to show me that my
rights would change. Is this perhaps the standard procedure?
Thanks in advance, and even more for the initiative for taking up the
2008/7/6 Joe Harrington <email@example.com>:
> Thanks to all who have signed up since my update email, we've done
> another 5%! Woohoo! Let's all do it!
> We're putting together some sort of prize idea for the conference.
> Would folks prefer:
> colored conference badge ribbon
> dessert on me
> graphic for your personal website
> copy of the printed PDF autographed by Stefan van der Walt
> something else?
> You get a + for every 250 words you've written at the time you vote!
> You can total your score from the stats page:
> In order to allow people to buy as many votes as possible, we'll set
> the close of voting as midnight PDT Friday. Offer subject to
> logistical reality (i.e., a conversation with our accountant about
> legal uses of certain kinds of funds). I guess that makes this our
> MID-SUMMER DOCUMENTATION WIND SPRINT!
> Andrew Straw <firstname.lastname@example.org> says:
>> One thing I notice about the organization of the doc site that seems
>> sub-optimal is that functions are resolved to the module where they're
>> defined rather than their canonical namespace. In particular, clicking
>> on the page for array() from the main numpy page gives me a page with
>> the primary header saying "numpy.core.multiarray.array". I think that's
>> confusing, particularly to new users. All the more so since I believe
>> the "numpy.core" namespace is more-or-less for internal implementation
>> and it is discouraged to write external code referencing into numpy.core.
> Keep your EYES on the PRIZE: *write*! Woohoo! ;-)
> Scipy-dev mailing list
More information about the Scipy-dev