Why is there a separate pyramid_chameleon repository?

[Tshepang Lekhonkhobe]

When I saw https://github.com/Pylons/pyramid_chameleon, I thought it's a dependency of Pyramid, only to find that it's been integrated into Pyramid itself. Why is it there?

[Chris McDonough]

It was created at a sprint with the idea that we were going to
eventually move Chameleon support out of the core but we never pulled
the trigger. Unclear whether we ever will.

- C

[Blaise Laflamme]

THe same was done for mako, and I think it'll be a good thing to do. This could be a pycon sprint topic.

[Tshepang Lekhonkhobe]

To avoid this sort of confusion, and to represent reality, do you mind simply removing it?

[Blaise Laflamme]

You mean removing the repo? I don't think... Github repos are not only reflecting the current working state but also work in progress. Stable documentation reflects the current working state, I consider people visiting github repos as more advanced user looking at more than just stable stuff. If we decide to drop those projects from happening then yes we can remove them, not before.

[Wichert Akkerman]

On Jan 20, 2013, at 19:06, Blaise Laflamme <bla...@laflamme.org> wrote:

> You mean removing the repo? I don't think... Github repos are not only reflecting the current working state but also work in progress. Stable documentation reflects the current working state, I consider people visiting github repos as more advanced user looking at more than just stable stuff. If we decide to drop those projects from happening then yes we can remove them, not before.

Even then I would archive them in some way to preserve history.

Wichert.

[Tshepang Lekhonkhobe]

Ok, kool. Maybe a note on the README on the status?