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
Hi,
On Jul 20, 2015 5:11 PM, Steve Piercy steve.piercy@gmail.com 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
Hi,
On 20 July 2015 at 22:47, Steve Piercy steve.piercy@gmail.com 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
On Jul 19, 2015, at 11:34 , Steve Piercy steve.piercy@gmail.com 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.
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.
