Adding functionality to the core

[Theron Luhn]

Engaging with https://github.com/Pylons/pyramid/issues/3452 got me thinking about functionality I’ve wished was shipped with Pyramid.  CORS for example, or a base traversal resource.

So I was wondering what’s the bar to add additional stuff to the project?  Not an official policy or anything, just the general feeling of the community.

— Theron

[Steve Piercy]

I think it depends on the additional thing. I'd need specifics.

In general, I have no opposition to additions, except for what
we have as general policy and guidelines for Pylons Project
projects, including Pyramid add-ons.

--steve


On 9/19/19 at 10:38 AM, the...@luhn.com (Theron Luhn) pronounced:

>Engaging with https://github.com/Pylons/pyramid/issues/3452

------------------------
Steve Piercy, Eugene, OR

[Michael Merickel]

My personal feeling is most things that can be done out of core should be done out of core, but if new hooks or functionality is needed in core to accomplish that then we should consider adding it. The only exceptions are things that seem clear to affect a large percentage of the community or things that are implementing standards.

CORS is a great example of something that I *think* view derivers and a custom module should be able to do completely outside of core, but in the vein of CSRF are something that might benefit from being shipped with Pyramid if the implementation was deemed useful for a large percentage of use cases.

- Michael

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/AD1DB163-D691-4EF6-B8CA-A19F3D76E245%40luhn.com.

--

Michael