If one outcome of the sprint were a list of packages that can be ported to Python 3, or a clear(er) dependency tree for the zope packages, I could use that here in recruiting contributors.
We anticipate between 5 and ten eager participants in the open source contribution initiative I've written about and I'd love to scoop em all into the Plone world Sent from my iPhone > On Jan 8, 2016, at 5:30 AM, Eric Steele <ericsteel...@gmail.com> wrote: > > (Resending since it got bounced by plone-framework) > > I still need to post my fork announcement. I'll get that pushed out today. > > I've also forked PluggableAuthService to start merging that and PlonePAS > together. > > Eric > > >> On 8 Jan 2016, at 2:00, Philip Bauer wrote: >> >> The upcoming alpine city sprint will focus on Zope and CMF. Are there >> specific plans as to what will be done? >> >> What is the current state regarding our relationship with Zope? Am I correct >> that so far we only forked CMFCore >> (https://github.com/plone/Products.CMFCore)? >> >> If there will be work done on Zope where should that happen? >> >> Should such a discussion take place on >> https://community.plone.org/c/core-development/framework-team? >> >> So many questions and so little coffee, >> Philip >> >> -- >> Starzel.de >> Philip Bauer >> Nymphenburger Straße 187 >> 80634 München >> Tel: 089 - 189 29 533 >> ba...@starzel.de >> www.starzel.de > _______________________________________________ > Framework-Team mailing list > framework-t...@lists.plone.org > https://lists.plone.org/mailman/listinfo/plone-framework-team _______________________________________________ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
