Re: [pylons-devel] Pylons 1.x maintenance

2016-02-07 Thread Jan Heylen
Hi, May I ask how this story ended, Does Andrew has release access to pylons and it's dependencies such as WebError? I'm wondering because of the WebError issue I mentioned before: https://groups.google.com/d/msg/pylons-devel/92Wl0ylZJGg/hdbSy9sZBQAJ br, Jan Heylen On Wednesday, July 22, 2015

Re: [pylons-devel] Pylons 1.x maintenance

2015-07-21 Thread Ben Bangert
I'd be happy to add you and another person as release maintainers for Pylons (we could setup a separate pylons-legacy team for you on github with access to appropriate repos as well, or I can just stream-line merging anything one of you r+, whichever works). I assume you will also need release acce

Re: [pylons-devel] Pylons 1.x maintenance

2015-07-20 Thread Andrew Shadura
Hi, On 20 July 2015 at 22:47, Steve Piercy wrote: > To proceed, please contact Ben Bangert directly, as he is the owner of > Pylons the web framework, and work out any details. I don't have any > say in the matter; I'm just facilitating. > https://github.com/bbangert Okay, maybe I should try (a

Re: [pylons-devel] Pylons 1.x maintenance

2015-07-20 Thread Steve Piercy
On 7/20/15 at 6:10 PM, and...@shadura.me (Andrew Shadura) pronounced: Hi, On Jul 20, 2015 5:11 PM, "Steve Piercy" wrote: "Take over" implies ownership. Is that what you mean? I mean being able to react promptly to security and compatibility issues, merge and review patches, tag and upload

Re: [pylons-devel] Pylons 1.x maintenance

2015-07-20 Thread Andrew Shadura
Hi, On Jul 20, 2015 5:11 PM, "Steve Piercy" wrote: > "Take over" implies ownership. Is that what you mean? I mean being able to react promptly to security and compatibility issues, merge and review patches, tag and upload releases. The core team of Kallithea has necessary skills and experience,

Re: [pylons-devel] Pylons 1.x maintenance

2015-07-19 Thread Bert JW Regeer
> On Jul 19, 2015, at 11:34 , Steve Piercy wrote: > > "Take over" implies ownership. Is that what you mean? > > You could be added as a Core Developer so that you can manage pull requests. > https://github.com/orgs/Pylons/teams/core-developers That’s a non-public team. > > You are more tha

Re: [pylons-devel] Pylons 1.x maintenance

2015-07-19 Thread Steve Piercy
"Take over" implies ownership. Is that what you mean? You could be added as a Core Developer so that you can manage pull requests. https://github.com/orgs/Pylons/teams/core-developers You are more than welcome to make contributions to the code, following the contribution guidelines. http://

[pylons-devel] Pylons 1.x maintenance

2015-07-19 Thread Andrew Shadura
Hello everyone, I'm one of the developers of Kallithea, a source code hosting and review system, which is currently based on Pylons 1.0. As we're busy polishing essential features of the software, we don't currently have time or manpower to migrate to some less obsolete framework, so we stick to P