[IPython-dev] Migrating wiki again

Brian Granger ellisonbg@gmail....
Thu Jan 10 01:13:02 CST 2013


Yes, the new task list on GiuHub is simple awesome.

On Wed, Jan 9, 2013 at 11:11 PM, MinRK <benjaminrk@gmail.com> wrote:
> We can even open an Issue with the new task list, to mark off which pages
> have had a manual clean/check pass.
>
>
> On Wed, Jan 9, 2013 at 10:41 PM, Brian Granger <ellisonbg@gmail.com> wrote:
>>
>> Great, thanks for doing this, it shouldn't be too bad to clean everything
>> up.
>>
>> On Wed, Jan 9, 2013 at 10:13 PM, MinRK <benjaminrk@gmail.com> wrote:
>> >
>> >
>> > On Wed, Jan 9, 2013 at 10:10 PM, Bradley M. Froehle
>> > <brad.froehle@gmail.com>
>> > wrote:
>> >>
>> >> Min: Thanks for the XML file. I had just built a script to scrape
>> >> http://wiki.ipython.org/Special:AllPages so I could use
>> >> http://wiki.ipython.org/Special:Export.
>> >> (https://gist.github.com/4499750#file-ipython_all_pages-py).
>> >>
>> >> Anyway, this mw-to-gollum.rb script
>> >> (https://gist.github.com/4499750#file-mw-to-gollum-rb) seems to work
>> >> okay.
>> >>
>> >> I've run it and pushed the results to
>> >> https://github.com/bfroehle/ipython/wiki/Main-Page
>> >>
>> >> There are a few issues:
>> >> 1. Some pages need to be manually cleaned up: e.g.,
>> >> https://github.com/bfroehle/ipython/wiki/Extensions-Index
>> >> 2. Github uses gollum which does not use directories --- everything is
>> >> in
>> >> a flat namespace. I've worked around this by replacing all
>> >> subdirectories
>> >> with dashes. (See the tr('/', '-') in the script). This seems to keep
>> >> most
>> >> of the links working, but some are still broken (see
>> >> https://github.com/bfroehle/ipython/wiki/Cookbook, for example).
>> >
>> >
>> > Pretty good!  There aren't too many pages, so I think we can probably
>> > start
>> > with that, and do a bit of cleanup and be set.
>> >
>> >>
>> >>
>> >>
>> >> -Brad
>> >>
>> >>
>> >> On Wednesday, January 9, 2013 at 8:55 PM, Bradley M. Froehle wrote:
>> >>
>> >> > Yes, I think this is a good idea too.
>> >> >
>> >> > I can attempt the migration if I can get a dump of the wiki contents
>> >> > in
>> >> > some usable fashion.
>> >> >
>> >> > -Brad
>> >> >
>> >> >
>> >> > On Wed, Jan 9, 2013 at 5:28 PM, MinRK <benjaminrk@gmail.com
>> >> > (mailto:benjaminrk@gmail.com)> wrote:
>> >> > > plus a million. I know Thomas did the moin->mediawiki migration,
>> >> > > and I don't want to make him do it all over again.
>> >> > > I can look into this migration next week.
>> >> > >
>> >> > > For now, can we 'lock' the current wiki, so there can't be any more
>> >> > > edits?
>> >> > >
>> >> > > -MinRK
>> >> > >
>> >> > >
>> >> > > On Wed, Jan 9, 2013 at 4:47 PM, Brian Granger <ellisonbg@gmail.com
>> >> > > (mailto:ellisonbg@gmail.com)> wrote:
>> >> > > > I am +1 on this plan.
>> >> > > >
>> >> > > > On Wed, Jan 9, 2013 at 4:46 PM, Thomas Kluyver <takowl@gmail.com
>> >> > > > (mailto:takowl@gmail.com)> wrote:
>> >> > > > > A few days ago, @dttocs on Github tipped us off that our Wiki
>> >> > > > > was
>> >> > > > > serving
>> >> > > > > spam about prescription drugs. I cleaned it up and upgraded
>> >> > > > > Mediawiki, but
>> >> > > > > it's already reappeared, so evidently the loophole that was
>> >> > > > > used
>> >> > > > > before is
>> >> > > > > still open. This isn't just the regular spam pages, which are
>> >> > > > > mostly under
>> >> > > > > control; something is able to modify .htaccess .
>> >> > > > >
>> >> > > > > I'm not a sysadmin, and we've got better uses for our time than
>> >> > > > > battling
>> >> > > > > malware. Unless someone feels confident they can maintain it
>> >> > > > > securely, I
>> >> > > > > suggest that we abandon our experiment with Mediawiki, and
>> >> > > > > start
>> >> > > > > moving the
>> >> > > > > content to a Github wiki.
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > Thomas
>> >> > > > >
>> >> > > > > _______________________________________________
>> >> > > > > IPython-dev mailing list
>> >> > > > > IPython-dev@scipy.org (mailto:IPython-dev@scipy.org)
>> >> > > > > http://mail.scipy.org/mailman/listinfo/ipython-dev
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > > --
>> >> > > > Brian E. Granger
>> >> > > > Cal Poly State University, San Luis Obispo
>> >> > > > bgranger@calpoly.edu (mailto:bgranger@calpoly.edu) and
>> >> > > > ellisonbg@gmail.com (mailto:ellisonbg@gmail.com)
>> >> > > > _______________________________________________
>> >> > > > IPython-dev mailing list
>> >> > > > IPython-dev@scipy.org (mailto:IPython-dev@scipy.org)
>> >> > > > http://mail.scipy.org/mailman/listinfo/ipython-dev
>> >> > >
>> >> > >
>> >> > >
>> >> > > _______________________________________________
>> >> > > IPython-dev mailing list
>> >> > > IPython-dev@scipy.org (mailto:IPython-dev@scipy.org)
>> >> > > http://mail.scipy.org/mailman/listinfo/ipython-dev
>> >> >
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> IPython-dev mailing list
>> >> IPython-dev@scipy.org
>> >> http://mail.scipy.org/mailman/listinfo/ipython-dev
>> >
>> >
>> >
>> > _______________________________________________
>> > IPython-dev mailing list
>> > IPython-dev@scipy.org
>> > http://mail.scipy.org/mailman/listinfo/ipython-dev
>> >
>>
>>
>>
>> --
>> Brian E. Granger
>> Cal Poly State University, San Luis Obispo
>> bgranger@calpoly.edu and ellisonbg@gmail.com
>> _______________________________________________
>> IPython-dev mailing list
>> IPython-dev@scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev@scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>



-- 
Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com


More information about the IPython-dev mailing list