[pylons-devel] github pages for pylons project sites

2016-01-02 Thread Michael Merickel
Hey everyone, I'm starting the discussion (which I hope is very quick) about what to do with our public websites. Right now we have: - docs.pylonsproject.org (docs, hosted on rtd) - docs.pylonsproject.org/projects (hosted on rtd) - www.pylonsproject.org (ppo, hosted somewhere controlled by

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Steve Piercy
OK, so we need to set that expectation in a contributing.md document for the repo. We cannot assume that contributors know our process when it's not documented for a given repo. GitHub uses contributing.md: https://help.github.com/articles/setting-guidelines-for-repository-contributors/

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Michael Merickel
Okay, I was unaware of any on-going changes on the sites which is a little silly for someone with my level of involvement in the project. Blaise, could you please explain the setup you are currently working on - including a timeline, what websites it will affect, how team members will be able to

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Blaise Laflamme
Sure, the initial setup is pretty simple, Linode VPS running Ubuntu 14.04 with latest Nginx-stable. A pylons user, with public user keys for site publishing, responsible to publish via pushing master branch to prod deployment, and probably dev branch for dev deployment. The setup will be done

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Blaise Laflamme
You're right, we definitely need this. On Saturday, January 2, 2016 at 4:54:18 PM UTC-5, Steve Piercy wrote: > > OK, so we need to set that expectation in a contributing.md > document for the repo. We cannot assume that contributors know > our process when it's not documented for a given repo.

[pylons-devel] Re: github pages for pylons project sites

2016-01-02 Thread Blaise Laflamme
Those three sites are on a Rackspace VPS badly organized and using their Cloud DNS. I'm in the process of migrating them over a Linode (we got sponsorship) VPS + DNS configured to publish via a githook for people who'll have access to do it: for now me, steve and goodwill. Those sites are

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Steve Piercy
On 1/2/16 at 3:11 PM, mmeri...@gmail.com (Michael Merickel) pronounced: Hey everyone, I'm starting the discussion (which I hope is very quick) about what to do with our public websites. Right now we have: - docs.pylonsproject.org (docs, hosted on rtd) - docs.pylonsproject.org/projects (hosted

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Blaise Laflamme
-trypyramid.com -webob.org we'll have to redo a base for pylonsproject.org since it's a crappy pyramid app atm, but we could have something quick for the better. On Saturday, January 2, 2016 at 5:22:45 PM UTC-5, Michael Merickel wrote: > > Which websites are you planning to affect in the short

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Bert JW Regeer
Bert would indeed be happy. Cheers, Bert > On Jan 2, 2016, at 15:22, Michael Merickel wrote: > > Which websites are you planning to affect in the short term? Is it the 3 I > originally listed? I expect Bert will be happy if webob.org is on the list. > > On Sat, Jan 2,

Re: [pylons-devel] github pages for pylons project sites

2016-01-02 Thread Michael Merickel
Which websites are you planning to affect in the short term? Is it the 3 I originally listed? I expect Bert will be happy if webob.org is on the list. On Sat, Jan 2, 2016 at 4:03 PM, Blaise Laflamme wrote: > Sure, > > the initial setup is pretty simple, Linode VPS running