(10-11-2016, 11:36 AM)enlivenapp Wrote: Sorry, I didn't subscribe to the thread.... 
There were a bunch of people talking on the old PyroCMS forums, and I've been very interested in keeping PyroCMS going in CI. I've talked to Ryan (the new owner of PyroCMS) and he's keen on letting the CI versions die off. The good thing about it is most of the code is publicly available to use (under MIT?) so it could be used and ported.
At this point the CI PyroCMS needs some serious updating (especially the admin areas) if not a complete rewrite but if we can find a core group of committed folks that really want to keep PyroCMS going (under a different name) and keep it open source, I'd be game in helping or even heading up the dev team...
Also, now subbed to the thread.
Until last year I followed the community channels everywhere (forum, irc, facebook page / group) and there wasn't any serious attempt to save PyroCMS as a CI based CMS. I don't know where do you saw that.
About the licensing: Honestly I am not a lawyer so I'm not sure how it's possible to continue. In Pyro there were a bunch of libraries with different licences (MIT, Apache, OSL etc.) some things not licensed at all, some things have copyrighted by Pyro LLC or Phil Sturgeon with a made up license (dbad). Even CI 3.0 dev had a different license then now...
In conclusion, I don't think anybody should continue Pyro now despite of I was a huge fan of it too. The code is very old, the licensing issue is a serious problem too, it would require a complete rewrite in all areas. And the most important thing, we are near to CI4, which is 100% incompatible with PyroCMS 2.2 what was based on CI 3 dev from ~2013... CI 4 release will be a great oportunity to start with a blank slate and we should wait till then.
Also I see another huge problem: every popular CMS was backed by a company, without that support there is not enough dev hours to create something remarkable. Currently the most popular CMS based on CI (Fuel CMS) is also created by a company.
