Hi folks, I was just pointing a colleague to the 'official download page' for numpy so he could find how to grab current sources: http://new.scipy.org/download.html but I was quite surprised to find that it still points to SVN for both numpy and scipy. It would probably not be a bad idea to update those and point them to github... Cheers, f
On 18 January 2012 11:22, Fernando Perez <fperez.net@gmail.com> wrote:
I was just pointing a colleague to the 'official download page' for numpy so he could find how to grab current sources:
http://new.scipy.org/download.html
but I was quite surprised to find that it still points to SVN for both numpy and scipy. It would probably not be a bad idea to update those and point them to github...
It's rather confusing having two websites. The "official" page at http://www.scipy.org/Download points to github. There hasn't been much maintenance effort for new.scipy.org, and there was some recent discussion about taking it offline. I'm not sure if a firm conclusion was reached. Cheers, Scott
On Wed, Jan 18, 2012 at 2:18 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
It's rather confusing having two websites. The "official" page at http://www.scipy.org/Download points to github.
The problem is that this page, which looks pretty official to just about anyone: http://numpy.scipy.org/ takes you to the one at new.scipy... So as far as traps for the unwary go, this one was pretty cleverly laid out ;) Best, f
On 19 January 2012 00:44, Fernando Perez <fperez.net@gmail.com> wrote:
On Wed, Jan 18, 2012 at 2:18 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
It's rather confusing having two websites. The "official" page at http://www.scipy.org/Download points to github.
The problem is that this page, which looks pretty official to just about anyone:
takes you to the one at new.scipy... So as far as traps for the unwary go, this one was pretty cleverly laid out ;)
It certainly is. I think (as usual), the problem is that fixing the situation lies on the shoulders of people who are already heavily overburdened.. There is a pull request updating the offending page at https://github.com/scipy/scipy.orgnew/pull/1 if any overburdened types feel like merging, building and uploading the revised html. Cheers, Scott
On Wed, Jan 18, 2012 at 10:19 PM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
I think (as usual), the problem is that fixing the situation lies on the shoulders of people who are already heavily overburdened..
I certainly understand that problem, as I'm eternally behind on a million things regarding ipython. But the only solution to these problems is delegation, not asking the already overburdened few to work even harder than they already do. I wonder if we could distribute the process of managing the websites a little more for numpy/scipy, so this didn't bottleneck as much. Furthermore, managing those is the kind of task that can be accomplished by someone who may not feel comfortable touching the numpy C core, and yet it's a *great* way to help the project out. In ipython, we've moved to githubpages hosting for everything, which means that now having a web team is as easy as clicking on the github interface a couple of times, and that's one more task we can get help on from others. In fairness, right now the ipythonweb team is the same people as the core, but at least things are in place to accept new hands helping should they become available, without any conflict with core development. Just a thought. Cheers, f
I think the problem here is one of delegation and information. I'm not even sure how the webpages get updated at this point. Does anyone on this list know? I think it would be a great idea to move to github pages for the NumPy project at least. Travis On Jan 19, 2012, at 12:39 AM, Fernando Perez wrote:
On Wed, Jan 18, 2012 at 10:19 PM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
I think (as usual), the problem is that fixing the situation lies on the shoulders of people who are already heavily overburdened..
I certainly understand that problem, as I'm eternally behind on a million things regarding ipython.
But the only solution to these problems is delegation, not asking the already overburdened few to work even harder than they already do. I wonder if we could distribute the process of managing the websites a little more for numpy/scipy, so this didn't bottleneck as much.
Furthermore, managing those is the kind of task that can be accomplished by someone who may not feel comfortable touching the numpy C core, and yet it's a *great* way to help the project out.
In ipython, we've moved to githubpages hosting for everything, which means that now having a web team is as easy as clicking on the github interface a couple of times, and that's one more task we can get help on from others. In fairness, right now the ipythonweb team is the same people as the core, but at least things are in place to accept new hands helping should they become available, without any conflict with core development.
Just a thought.
Cheers,
f _______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpydiscussion
19.01.2012 18:21, Travis Oliphant kirjoitti:
I think the problem here is one of delegation and information.
I'm not even sure how the webpages get updated at this point. Does anyone on this list know? I think it would be a great idea to move to github pages for the NumPy project at least.
The main scipy.org web page is the wiki. I'm not sure who apart from Enthought's IT staff has access to the machine running it. The pages at numpy.scipy.org and new.scipy.org are hosted on new.scipy.org as static files  they're just generated by sphinx and uploaded manually. In addition to that, the machine also runs the Trac, the doc editor, and the conference.scipy.org and docs.scipy.org websites. A couple of people (including at least me and Jarrod + Enthought IT staff) have access to that machine. Moving the stuff at numpy.scipy.org to Github pages would make sense, as those are only static files. IMO, the stuff at new.scipy.org should be taken down  the idea was to revise the scipy.org front page during Scipy '09 conference, and make it rely less on the wiki, but the work was not finished. I think I don't have the necessary unix permissions to put the site down or edit it, though. Pauli
On Thu, Jan 19, 2012 at 11:57 AM, Pauli Virtanen <pav@iki.fi> wrote:
19.01.2012 18:21, Travis Oliphant kirjoitti:
I think the problem here is one of delegation and information.
I'm not even sure how the webpages get updated at this point. Does anyone on this list know? I think it would be a great idea to move to github pages for the NumPy project at least.
The main scipy.org web page is the wiki. I'm not sure who apart from Enthought's IT staff has access to the machine running it.
This machine is slated to move to Amazon EC2 no later than end of March. I am doing it myself. The problem I ran into is one of accumulated crust (for lack of better expression). There are a zillion apache .conf files and virtual www sites hosted off that box, just deciding what it still live and what is not is a big task (I don't want to shut something off by accident). I would personally be in favour of moving as much as we can to github or whatever other place you may think of. The current scipy.org machine bogs down randomly and apache needs a kick almost daily. Whenever I log into the box to restart it  the load is in the 1720 range. The scipy.org machine is actually an OpenVZ container living on an underpowered (imho) linux box. Hence, I decided to get a large Amazon instance with plenty of memory. At the same time, this is the perfect opportunity for cleanup. If someone is willing to assist me, I have no problems getting more involved into moving things and reorganizing them. Ognen
On Thu, Jan 19, 2012 at 9:21 AM, Travis Oliphant <travis@continuum.io> wrote:
I'm not even sure how the webpages get updated at this point. Does anyone on this list know? I think it would be a great idea to move to github pages for the NumPy project at least.
We've moved to the following setup with ipython, which works very well for us so far: 1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com). 2. wiki.ipython.org: a mediawiki instance we run on a server I personally pay for. 3. archive.ipython.org: static hosting of content such as downloads of release candidates, same server as #2. We also keep main releases here as an alternative, but I think most people get the releases from pypi these days. With this setup, the only thing that requires actual ssh access is #3, and I simply uploaded the keys of a few developers to that server. But having to upload content there is fairly rare, and the large majority of content that needs update lives in #1 and #2, both of which have access control mechanisms that make job delegation extremely easy. At this point, our only real bottleneck is that I'm still the sole release manager so far. But now that we're hitting a more regular release pace I plan to change that soon, and start rotating this job too, so it doesn't depend on my time. We used to release so infrequently that this wasn't really an issue, and the 0.11 release was so big that I wouldn't foist it on anyone else (it took ~2 weeks just to do the release work), but moving forward this job should also be easy to delegate and we'll do so soon. I'm happy to share any other details that may help smooth out the workflow for numpy and scipy. I certainly think that the current setup with a very outdated wiki as the main site and a newbutsemiinvalid rst one needs fixing; it's kind of a shame to have the crown jewels of the scientific python ecosystem with such a poor web presence. But fortunately the problem isn't too hard to fix these days (the github machinery really plays a key part in helping here). Cheers, f
On Thu, Jan 19, 2012 at 1:48 PM, Fernando Perez <fperez.net@gmail.com> wrote:
On Thu, Jan 19, 2012 at 9:21 AM, Travis Oliphant <travis@continuum.io> wrote:
I'm not even sure how the webpages get updated at this point. Does anyone on this list know? I think it would be a great idea to move to github pages for the NumPy project at least.
We've moved to the following setup with ipython, which works very well for us so far:
1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com).
2. wiki.ipython.org: a mediawiki instance we run on a server I personally pay for.
3. archive.ipython.org: static hosting of content such as downloads of release candidates, same server as #2. We also keep main releases here as an alternative, but I think most people get the releases from pypi these days.
With this setup, the only thing that requires actual ssh access is #3, and I simply uploaded the keys of a few developers to that server. But having to upload content there is fairly rare, and the large majority of content that needs update lives in #1 and #2, both of which have access control mechanisms that make job delegation extremely easy.
At this point, our only real bottleneck is that I'm still the sole release manager so far. But now that we're hitting a more regular release pace I plan to change that soon, and start rotating this job too, so it doesn't depend on my time. We used to release so infrequently that this wasn't really an issue, and the 0.11 release was so big that I wouldn't foist it on anyone else (it took ~2 weeks just to do the release work), but moving forward this job should also be easy to delegate and we'll do so soon.
I'm happy to share any other details that may help smooth out the workflow for numpy and scipy. I certainly think that the current setup with a very outdated wiki as the main site and a newbutsemiinvalid rst one needs fixing; it's kind of a shame to have the crown jewels of the scientific python ecosystem with such a poor web presence. But fortunately the problem isn't too hard to fix these days (the github machinery really plays a key part in helping here).
ipython.org used to live on scipy.org machine  as far as I can tell the only thing still on the scipy.org machine related to ipython are the dev and user mailing lists (via mailman) hosted at projects.scipy.org. Ognen
On Thu, Jan 19, 2012 at 12:14 PM, Ognen Duzlevski <ognen@enthought.com> wrote:
ipython.org used to live on scipy.org machine  as far as I can tell the only thing still on the scipy.org machine related to ipython are the dev and user mailing lists (via mailman) hosted at projects.scipy.org.
Yup, we've now moved everything but the mailing lists (as you point out next, the load on that box was so awful all the time that trying to use it for anything was nothing but pain). Technically, when we were on scipy our domain was ipython.scipy.org, the ipython.org domain has been from the start hosted outside of the Enthought infrastructure; but that's just a nitpick :) Thanks for tackling the problem of cleaning up all that accumulated cruft, and for the always responsive support you gave us in the past. Cheers, f
On 19 January 2012 21:48, Fernando Perez <fperez.net@gmail.com> wrote:
We've moved to the following setup with ipython, which works very well for us so far:
1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com).
I like this idea, and to get the ball rolling I've stripped out the www directory of the scipy.orgnew repo into it's own repository using git filterbranch (posted here: https://github.com/scottza/scipy_website) and created https://github.com/scottza/scottza.github.com. This puts a copy of the new scipy website at http://scottza.github.com as a proof of concept. Since there seems to be some agreement on rehosting numpy's website on github, I'd be happy to do as much of the legwork as I can in getting the numpy.scipy.org content hosted at numpy.github.com. I don't have permission to create new repos for the Numpy organization, so someone would have to create an empty https://github.com/numpy/numpy.github.com and give me push permission on that repo. It would be great to see scipy go the same way and make updating the site easier. I know that David WardeFarley, Pauli and others put in a lot of work scraping content off the wiki to produce the new website, it would be fantastic to see the fruits of that effort. Issues with scipy "Trac, the doc editor, and the conference.scipy.org and docs.scipy.org" as mentioned by Pauli. There is also the cookbook on the wiki to consider (perhaps http://scipycentral.org/ could play a role there). Cheers, Scott
I would like to assist on the website. Although I have not made any code contributions to Numpy/SciPy (yet), I do follow the mailing lists and try to keep up to date on the scientific python scene. However, I need to hold my breath until the end of my wind tunnel test campaign mid February. And I do like the sound of the gihub workflow as currently done by the ipython team. Regards, David On 20/01/12 08:49, Scott Sinclair wrote:
On 19 January 2012 21:48, Fernando Perez<fperez.net@gmail.com> wrote:
We've moved to the following setup with ipython, which works very well for us so far:
1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com). I like this idea, and to get the ball rolling I've stripped out the www directory of the scipy.orgnew repo into it's own repository using git filterbranch (posted here: https://github.com/scottza/scipy_website) and created https://github.com/scottza/scottza.github.com. This puts a copy of the new scipy website at http://scottza.github.com as a proof of concept.
Since there seems to be some agreement on rehosting numpy's website on github, I'd be happy to do as much of the legwork as I can in getting the numpy.scipy.org content hosted at numpy.github.com. I don't have permission to create new repos for the Numpy organization, so someone would have to create an empty https://github.com/numpy/numpy.github.com and give me push permission on that repo.
It would be great to see scipy go the same way and make updating the site easier. I know that David WardeFarley, Pauli and others put in a lot of work scraping content off the wiki to produce the new website, it would be fantastic to see the fruits of that effort.
Issues with scipy "Trac, the doc editor, and the conference.scipy.org and docs.scipy.org" as mentioned by Pauli. There is also the cookbook on the wiki to consider (perhaps http://scipycentral.org/ could play a role there).
Cheers, Scott _______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpydiscussion
On Fri, Jan 20, 2012 at 3:53 AM, David Verelst <david.verelst@gmail.com> wrote:
I would like to assist on the website. Although I have not made any code contributions to Numpy/SciPy (yet), I do follow the mailing lists and try to keep up to date on the scientific python scene. However, I need to hold my breath until the end of my wind tunnel test campaign mid February.
Fantastic, thanks. I think the ideal setup would be to create a web team in the numpy org. so that this team can have permissions over the website repos (source and build). I don't belong to the org so I can't do it myself.
And I do like the sound of the gihub workflow as currently done by the ipython team.
Don't hesitate to ask us if you have any questions. In particular, it's important *not* to use ghpages like they originally suggest, but instead like we do it in ipython: the build should be a separate repo altogether, not just a branch in the official source repo. Ours has the makefile targets and scripts already for that, let me know if any of it doesn't make sense. Cheers, f
On Fri, Jan 20, 2012 at 12:53 PM, David Verelst <david.verelst@gmail.com>wrote:
I would like to assist on the website. Although I have not made any code contributions to Numpy/SciPy (yet), I do follow the mailing lists and try to keep up to date on the scientific python scene. However, I need to hold my breath until the end of my wind tunnel test campaign mid February.
And I do like the sound of the gihub workflow as currently done by the ipython team.
Regards, David
On 20/01/12 08:49, Scott Sinclair wrote:
On 19 January 2012 21:48, Fernando Perez<fperez.net@gmail.com> wrote:
We've moved to the following setup with ipython, which works very well for us so far:
1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com). I like this idea, and to get the ball rolling I've stripped out the www directory of the scipy.orgnew repo into it's own repository using git filterbranch (posted here: https://github.com/scottza/scipy_website) and created https://github.com/scottza/scottza.github.com. This puts a copy of the new scipy website at http://scottza.github.com as a proof of concept.
Nice!
Since there seems to be some agreement on rehosting numpy's website on github, I'd be happy to do as much of the legwork as I can in getting the numpy.scipy.org content hosted at numpy.github.com. I don't have permission to create new repos for the Numpy organization, so someone would have to create an empty https://github.com/numpy/numpy.github.com and give me push permission on that repo.
Does it need to be a new repo, or would permissions on https://github.com/numpy/numpy.scipy.org work as well?
It would be great to see scipy go the same way and make updating the site easier. I know that David WardeFarley, Pauli and others put in a lot of work scraping content off the wiki to produce the new website, it would be fantastic to see the fruits of that effort.
Yes it would. I've taken Fernando's suggestion and created a github team "Scipy web team" and given you pushpull permissions for https://github.com/scipy/scipy.orgnew Scott. David, once you make a few pull requests please ping us, and we can give you permissions too. Ralf
Issues with scipy "Trac, the doc editor, and the conference.scipy.org and docs.scipy.org" as mentioned by Pauli. There is also the cookbook on the wiki to consider (perhaps http://scipycentral.org/ could play a role there).
On 5 February 2012 13:07, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On 20/01/12 08:49, Scott Sinclair wrote:
On 19 January 2012 21:48, Fernando Perez<fperez.net@gmail.com> wrote:
We've moved to the following setup with ipython, which works very well for us so far:
1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com). I like this idea, and to get the ball rolling I've stripped out the www directory of the scipy.orgnew repo into it's own repository using git filterbranch (posted here: https://github.com/scottza/scipy_website) and created https://github.com/scottza/scottza.github.com. This puts a copy of the new scipy website at http://scottza.github.com as a proof of concept.
Nice!
Since there seems to be some agreement on rehosting numpy's website on github, I'd be happy to do as much of the legwork as I can in getting the numpy.scipy.org content hosted at numpy.github.com. I don't have permission to create new repos for the Numpy organization, so someone would have to create an empty https://github.com/numpy/numpy.github.com and give me push permission on that repo.
Does it need to be a new repo, or would permissions on https://github.com/numpy/numpy.scipy.org work as well?
Yes a new repo is required. Github will render html checked into a repo called https://github.com/numpy/numpy.github.com at http://numpy.github.com. Since the html is built from reST sources using Sphinx, we'd need a repo for the website source (https://github.com/numpy/numpy.github.com) and a repo to check the built html into (https://github.com/numpy/numpy.github.com). To update the website will require push permissions to both repos. The IPython team have scripts to automate the update, build and commit process for their website, which we could borrow from. Cheers, Scott
On 5 February 2012 13:07, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On 20/01/12 08:49, Scott Sinclair wrote:
On 19 January 2012 21:48, Fernando Perez<fperez.net@gmail.com>
We've moved to the following setup with ipython, which works very well for us so far:
1. ipython.org: Main website with only static content, manged as a repo in github (https://github.com/ipython/ipythonwebsite) and updated with a ghpages build (https://github.com/ipython/ipython.github.com). I like this idea, and to get the ball rolling I've stripped out the www directory of the scipy.orgnew repo into it's own repository using git filterbranch (posted here: https://github.com/scottza/scipy_website) and created https://github.com/scottza/scottza.github.com. This puts a copy of
wrote: the
new scipy website at http://scottza.github.com as a proof of concept.
Nice!
Since there seems to be some agreement on rehosting numpy's website on github, I'd be happy to do as much of the legwork as I can in getting the numpy.scipy.org content hosted at numpy.github.com. I don't have permission to create new repos for the Numpy organization, so someone would have to create an empty https://github.com/numpy/numpy.github.com and give me push permission on that repo.
Does it need to be a new repo, or would permissions on https://github.com/numpy/numpy.scipy.org work as well?
Yes a new repo is required. Github will render html checked into a repo called https://github.com/numpy/numpy.github.com at http://numpy.github.com. Since the html is built from reST sources using Sphinx, we'd need a repo for the website source (https://github.com/numpy/numpy.github.com) and a repo to check the built html into (https://github.com/numpy/numpy.github.com). To update the website will require push permissions to both repos.
I've created https://github.com/scipy/scipy.github.com and gave you
On Mon, Feb 6, 2012 at 8:17 AM, Scott Sinclair <scott.sinclair.za@gmail.com>wrote: permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it. On the numpy org I don't have the right permissions to do the same. Ralf
On 6 February 2012 21:41, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Mon, Feb 6, 2012 at 8:17 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
On 5 February 2012 13:07, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
Does it need to be a new repo, or would permissions on https://github.com/numpy/numpy.scipy.org work as well?
Yes a new repo is required. Github will render html checked into a repo called https://github.com/numpy/numpy.github.com at http://numpy.github.com. Since the html is built from reST sources using Sphinx, we'd need a repo for the website source (https://github.com/numpy/numpy.github.com) and a repo to check the built html into (https://github.com/numpy/numpy.github.com). To update the website will require push permissions to both repos.
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
The updated version of the 'old' new.scipy.org is now at http://scipy.github.com/. There are still a few things that I think need to get cleaned up. I'll ping the scipy mailing list in the next week or two to start the discussion on redirecting scipy.org and www.scipy.org, as well as solicit comments on the website content. Cheers, Scott
Hi, 06.02.2012 20:41, Ralf Gommers kirjoitti: [clip]
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
Ditto for numpy.github.com, now. Pauli
On Feb 7, 2012, at 4:02 AM, Pauli Virtanen wrote:
Hi,
06.02.2012 20:41, Ralf Gommers kirjoitti: [clip]
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
Ditto for numpy.github.com, now.
This is really nice. It will really help us make changes to the website quickly and synchronously with code changes. John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com Travis
Pauli
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpydiscussion
On Tue, Feb 7, 2012 at 2:03 PM, Travis Oliphant <travis@continuum.io> wrote:
John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com
Remember to also put a CNAME file in the root of the repository: http://pages.github.com/ Stéfan
2012/2/8 Stéfan van der Walt <stefan@sun.ac.za>:
On Tue, Feb 7, 2012 at 2:03 PM, Travis Oliphant <travis@continuum.io> wrote:
John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com
Remember to also put a CNAME file in the root of the repository:
Hi Pauli, I see that you've added the CNAME file. Now numpy.github.com is being redirected to numpy.scipy.org (the old site). As I understand it, whoever controls the scipy.org DNS settings needs point numpy.scipy.org at numpy.github.com so that people get the updated site when they browse to numpy.scipy.org.. Cheers, Scott
Hi, 08.02.2012 11:22, Scott Sinclair kirjoitti: [clip]
I see that you've added the CNAME file. Now numpy.github.com is being redirected to numpy.scipy.org (the old site).
As I understand it, whoever controls the scipy.org DNS settings needs point numpy.scipy.org at numpy.github.com so that people get the updated site when they browse to numpy.scipy.org..
Oops, so it seems. I read the Github pages docs and thought that the CNAME file just adds a virtual host, but apparently I misunderstood. I'll revert... Pauli
On 8 February 2012 00:03, Travis Oliphant <travis@continuum.io> wrote:
On Feb 7, 2012, at 4:02 AM, Pauli Virtanen wrote:
Hi,
06.02.2012 20:41, Ralf Gommers kirjoitti: [clip]
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
Ditto for numpy.github.com, now.
This is really nice. It will really help us make changes to the website quickly and synchronously with code changes.
John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing" Cheers, Scott
On Wed, Feb 15, 2012 at 5:13 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
On 8 February 2012 00:03, Travis Oliphant <travis@continuum.io> wrote:
On Feb 7, 2012, at 4:02 AM, Pauli Virtanen wrote:
Hi,
06.02.2012 20:41, Ralf Gommers kirjoitti: [clip]
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
Ditto for numpy.github.com, now.
This is really nice. It will really help us make changes to the website quickly and synchronously with code changes.
John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing"
I can do this  can I assume there is consensus that majority wants this done? Thank you, Ognen
On Wed, Feb 15, 2012 at 5:18 AM, Ognen Duzlevski <ognen@enthought.com> wrote:
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing"
I can do this  can I assume there is consensus that majority wants this done?
+1, and thanks to Scott for pushing on this front! Cheers, f
On 15 February 2012 15:30, Fernando Perez <fperez.net@gmail.com> wrote:
On Wed, Feb 15, 2012 at 5:18 AM, Ognen Duzlevski <ognen@enthought.com> wrote:
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing"
I can do this  can I assume there is consensus that majority wants this done?
+1, and thanks to Scott for pushing on this front!
Thanks Ognen. I think you can assume that there's consensus after a few +1's from core developers... Cheers, Scott
On Wed, Feb 15, 2012 at 7:42 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
On 15 February 2012 15:30, Fernando Perez <fperez.net@gmail.com> wrote:
On Wed, Feb 15, 2012 at 5:18 AM, Ognen Duzlevski <ognen@enthought.com> wrote:
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing"
I can do this  can I assume there is consensus that majority wants this done?
+1, and thanks to Scott for pushing on this front!
Thanks Ognen. I think you can assume that there's consensus after a few +1's from core developers...
Alright, it will happen sometime today and I will post a message announcing so. Ognen
Hi, 15.02.2012 14:59, Ognen Duzlevski kirjoitti: [clip]
Alright, it will happen sometime today and I will post a message announcing so. Ognen
Great! Once you have changed the records, we can adjust [1] the numpy.github.com page [1] to deal with the new virtual host name. Thanks, Pauli [1] http://pages.github.com/#custom_domains
It certainly would help people keep the NumPy website up to date. Thanks Ognen. Travis On Feb 15, 2012, at 7:18 AM, Ognen Duzlevski wrote:
On Wed, Feb 15, 2012 at 5:13 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
On 8 February 2012 00:03, Travis Oliphant <travis@continuum.io> wrote:
On Feb 7, 2012, at 4:02 AM, Pauli Virtanen wrote:
Hi,
06.02.2012 20:41, Ralf Gommers kirjoitti: [clip]
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
Ditto for numpy.github.com, now.
This is really nice. It will really help us make changes to the website quickly and synchronously with code changes.
John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing"
I can do this  can I assume there is consensus that majority wants this done?
Thank you, Ognen _______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpydiscussion
OK, the deed has been done :) Ognen On Wed, Feb 15, 2012 at 11:29 AM, Travis Oliphant <travis@continuum.io> wrote:
It certainly would help people keep the NumPy website up to date. Thanks Ognen.
Travis
On Feb 15, 2012, at 7:18 AM, Ognen Duzlevski wrote:
On Wed, Feb 15, 2012 at 5:13 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
On 8 February 2012 00:03, Travis Oliphant <travis@continuum.io> wrote:
On Feb 7, 2012, at 4:02 AM, Pauli Virtanen wrote:
Hi,
06.02.2012 20:41, Ralf Gommers kirjoitti: [clip]
I've created https://github.com/scipy/scipy.github.com and gave you permissions on that. So with that for the built html and https://github.com/scipy/scipy.orgnew for the sources, that should do it.
On the numpy org I don't have the right permissions to do the same.
Ditto for numpy.github.com, now.
This is really nice. It will really help us make changes to the website quickly and synchronously with code changes.
John Turner at ORNL has the numpy.org domain and perhaps we could get him to point it to numpy.github.com
It looks like numpy.org already redirects to numpy.scipy.org. So I think redirecting numpy.scipy.org to github should "do the right thing"
I can do this  can I assume there is consensus that majority wants this done?
Thank you, Ognen _______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpydiscussion
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpydiscussion
On Fri, Jan 20, 2012 at 8:49 AM, Scott Sinclair <scott.sinclair.za@gmail.com
wrote:
Issues with scipy "Trac, the doc editor, and the conference.scipy.org and docs.scipy.org" as mentioned by Pauli. There is also the cookbook on the wiki to consider (perhaps http://scipycentral.org/ could play a role there).
Cleaning up the Cookbook and putting it on scipycentral.org would be
useful. I'd like to understand though where the content of that site resides. Is there a public repo somewhere? Ralf
On 19 January 2012 00:44, Fernando Perez <fperez.net@gmail.com> wrote:
On Wed, Jan 18, 2012 at 2:18 AM, Scott Sinclair <scott.sinclair.za@gmail.com> wrote:
It's rather confusing having two websites. The "official" page at http://www.scipy.org/Download points to github.
The problem is that this page, which looks pretty official to just about anyone:
takes you to the one at new.scipy... So as far as traps for the unwary go, this one was pretty cleverly laid out ;)
The version of the numpy website now at http://numpy.github.com no longer points to the misleading and outdated new.scipy.org (an updated version of that site is at http://scipy.github.com). I think that numpy.scipy.org should be redirected to numpy.github.com as outlined at pages.github.com (see section on Custom Domains), and that it should happen sooner rather than later. Unfortunately I have no idea who has access to the DNS records (Ognen Duzlevski @ Enthought?). This change would remove one of the ways that people are currently directed to new.scipy.org. Cheers, Scott
participants (8)

David Verelst

Fernando Perez

Ognen Duzlevski

Pauli Virtanen

Ralf Gommers

Scott Sinclair

Stéfan van der Walt

Travis Oliphant