[IPython-dev] Scipy central & IPython notebook.

Kevin Dunn kgdunn@gmail....
Sun Sep 23 13:57:19 CDT 2012


On Sun, Sep 23, 2012 at 2:16 PM, Thomas Kluyver <takowl@gmail.com> wrote:
> On 23 September 2012 19:03, Brian Granger <ellisonbg@gmail.com> wrote:
>> * Marketing.  If it is part of the ipython universe, we can control
>> the messaging and marketing to promote the notebook and ipython.  As a
>> project, we tend to not be very outgoing with our marketing and I
>> think this is a mistake.
>
> As a counterpoint: I'm not thinking of this as a marketing tool for
> IPython notebooks. First and foremost it should be a useful repository
> for scientific Python users. I also want to be able to mix examples
> submitted as notebooks with examples from people who don't use the
> notebook, in which case it would work like scipy-central currently
> does.
>
> In short: I see the notebook as a tool for this kind of site, not the
> focus of it.
>
> Thomas


Hi there, thanks for these exciting ideas. However, I posted this to
the SciPy list on 26 Aug 2012. I'll simply cut and paste it here
again. I know this is the IPython list, but it is relevant to the
above discussion.

In short, I'm happy for the community to take on SciPy-Central and use
it however it could work best. However, I'm unable to contribute at
this time to make it work in the desired way.

Here's the original message. Thanks for reading. Kevin
----

Hi everyone, the scipy-central.org "maintainer" here; in inverted
commas, because I've been doing no maintenance over the past 12 to 18
months.

I'd like to offer all the scipy-central.org material over to the
community to keep going with it and improve it. I expected to have
time to do it myself, but new jobs and a different career path have
prevented me from implementing improvements that Pauli and several
others have proposed in the past.

This might be a good time to consider the issue, even just from a
branding perspective, to get it all looking coherent.

If anyone wants to get back to me on this, I can pass over the following:

1. Some/all of the domain names (those not transferred I will let
lapse on the next renewal in June 2013)

scipy-central.org(DNS)
scpyce.org(DNS)
scipy-central.com(MX)	Forward ( http://scipy-central.org )
scipy-central.net(MX)		Forward ( http://scipy-central.org )
scipycentral.com(MX)		Forward ( http://scipy-central.org )
scipycentral.net(MX)		Forward ( http://scipy-central.org )
scipycentral.org(MX)		Forward ( http://scipy-central.org )
scpyce.com(MX)		Forward ( http://scpyce.org )	
scpyce.net(MX)			Forward ( http://scpyce.org )	

2. all Django code, media files, templates, CSS and HTML, including
detailed instructions on how to install and use it are already at
https://github.com/kgdunn/SciPyCentral  Please take a look at this to
judge the complexity of the move.
3. backup scripts: local and off-site
4. the PostgreSQL database [23Mb]
5. monthly backup snapshots going back to July 2011, when the site
started [450Mb]
6. the Google Analytics account (not sure how to transfer this)
7. the original artwork files for the media

There are some interesting page hit and search analytics in raw data
(item 5) and from Google (item 6) that someone might want to look at.

I currently host the site on Webfaction. The new owner(s) will require
a similar unix-type server with:
* Python and Django,
* webserver (e.g. Apache, or nginx),
* ability to email for account creation, password resets and
submission confirmation
* rsync for remote backup,
* and other miscellaneous utilities: South, Pygments, Sphinx, Haystack
search with Xapian, PIL, etc

The new owner(s) will also inherit 2 pull requests and 45 issues on
the above-mentioned Github site. Other proposals made in the Scipy-Dev
mailing lists over the past year also exist.

I'm in no rush to hand it over; just putting it out there that someone
or some group more capable and with more time can definitely do a
better job of it than me.

Let me know how the community wants to proceed: please let's keep the
discussion public so everyone can contribute.


More information about the IPython-dev mailing list