Closed 153957 closed 9 years ago
koenbok
commented
9 years ago I'm around and check once in a while but my priorities are with Framer. @krallin is also an admin but I'm not sure how his workload looks these days.
If someone good is interested to help out let me know.
krallin
commented
9 years ago I'm mostly familiar with the 3.x codebase (having worked almost exclusively on that branch), so it's difficult (i.e. very time-intensive) for me to support issues in 2.x (especially considering some of these have been fixed in 3.x).
If we were to merge 3.x into master (and release it on PyPi), I'll try and make time to go through issues affecting that version.
@koenbok, would that make sense?
koenbok
commented
9 years ago Yes making 3.x master is long overdue :-(
I'll try to make some time this week to do that and then we can take it from there ok?
krallin
commented
9 years ago Sure, that works for me ; )
@153957 — once we merge 3.x into master, I'll look at the various existing issues and either close them if they were fixed in 3.x, suggest a workaround (if they're feature requests), or look for a fix.
stefanooldeman
commented
9 years ago I've been following this repo now for a few days and I'd like to get involved. Some advice would be welcome: on when is a good time to step in (after the 3.x merge to master). And if there are any issues which might be high prio or simple bugs, features to get familiar with the project. I have prior experiences with python 3, but I see this is a nice opportunity to change that.
koenbok
commented
9 years ago After the 3 merge. This weekend :-)
koenbok
commented
9 years ago Ok. V3 is now master.
@krallin go for it and let me know if I can add you to the pypy owners too. @stefanooldeman now is a good time to step in. My personal request would be to make large projects generate faster. But maybe you should start a bit easier :-)
krallin
commented
9 years ago Thanks @koenbok. Being added as a maintainer on PyPi too would be awesome.
@stefanooldeman, I think Python 3 support would be a pretty high priority list item (I was going to try and do some work on this — starting with enabling tests for Python 3), which is now reachable considering that Boto has added support for Python 3.
Speeding up builds would be a great thing too. I think this would have to be done by tracking dependencies across the objects (pages, static files) we manage, and only re-building what needs to be rebuilt.
Unfortunately, tracking "what has changed" might be difficult, especially once you factor in the effectively unlimited surface area we expose to plugins. Any ideas?
krallin
commented
9 years ago Quick update on Py3. I have a branch here that passes the tests. I'll publish this in a PR shortly so we can work on it / test it.
Cheers,
krallin
commented
9 years ago Hey @koenbok,
Could you add Travis to this repo? The .travis.yml file is already here, you just need to register with them and add commit hooks for this repo.
This will run tests against any PR that is proposed.
krallin
commented
9 years ago Started working on a list of the items we want to work on in Cactus here: https://github.com/koenbok/Cactus/issues/117
Feel free to contribute ideas to the list, or even claim an item : )
On the Cactus Blog Jorn says:
I see a lot of open Issues/Pull Requests that have not had answers or follow ups in a while. Are there still some maintainers around to respond to and accept PRs?