[Framework-Team] Plone-React Sprint in Bonn

Timo Stollenwerk tisto at plone.org
Tue Mar 6 16:42:40 UTC 2018


Awesome. Thank you!

Am 06.03.2018 um 17:38 schrieb Eric Bréhault:
> We already have 4 positive votes, plus yours I guess :) so that's 5,
> consider it officially approved.
> 
> On Tue, Mar 6, 2018 at 5:33 PM, Timo Stollenwerk <tisto at plone.org
> <mailto:tisto at plone.org>> wrote:
> 
>     The sprint will be from 11th to 14th. Would it be possible to get an
>     official vote from the FWT before that? Otherwise we can not use this in
>     announcements and stuff.
> 
>     Cheers,
>     Timo
> 
>     Am 05.03.2018 um 14:07 schrieb Eric Bréhault:
>     > Ok well, nevermind, let's go with next week anyway.
>     >
>     > On Mon, Mar 5, 2018 at 1:05 PM, Franco Pellegrini <frapell at gmail.com <mailto:frapell at gmail.com>
>     > <mailto:frapell at gmail.com <mailto:frapell at gmail.com>>> wrote:
>     >
>     >     Sorry Eric, I misread Jen's response... I am available tomorrow and
>     >     also the 13, so both dates work for me :)
>     >
>     >     Cheers
>     >
>     >
>     >     El lun., 5 de mar. de 2018 05:26, Eric Bréhault <ebrehault at gmail.com <mailto:ebrehault at gmail.com>
>     >     <mailto:ebrehault at gmail.com <mailto:ebrehault at gmail.com>>>
>     escribió:
>     >
>     >         Hi all,
>     >
>     >         +1 too for the Bonn sprint.
>     >
>     >         Regarding the FWT meeting, as Franco and Jens are not available
>     >         tomorrow, let's schedule the next meeting next week (March 13th).
>     >
>     >         Eric
>     >
>     >         On Mon, Mar 5, 2018 at 1:00 AM, Franco Pellegrini
>     >         <frapell at gmail.com <mailto:frapell at gmail.com>
>     <mailto:frapell at gmail.com <mailto:frapell at gmail.com>>> wrote:
>     >
>     >             Yes, I am able to attend next tuesday too, and also big +1
>     >             on this sprint being strategic
>     >
>     >             Regards,
>     >             Franco
>     >
>     >             On Sun, Mar 4, 2018 at 6:58 PM Jens Klein
>     >             <jk at kleinundpartner.at <mailto:jk at kleinundpartner.at>
>     <mailto:jk at kleinundpartner.at <mailto:jk at kleinundpartner.at>>> wrote:
>     >
>     >                 I am not available next Tuesday, but I am +1 to declare
>     >                 the Sprint strategic. -- Jens
>     >
>     >                 Am 4. März 2018 10:53:30 nachm. schrieb Alessandro Pisa
>     >                 <alessandro.pisa at gmail.com <mailto:alessandro.pisa at gmail.com>
>     >                 <mailto:alessandro.pisa at gmail.com
>     <mailto:alessandro.pisa at gmail.com>>>:
>     >
>     >>                 On 4 March 2018 at 14:35, Timo Stollenwerk
>     >>                 <tisto at plone.org <mailto:tisto at plone.org>
>     <mailto:tisto at plone.org <mailto:tisto at plone.org>>> wrote:
>     >>
>     >>                     Hi Framework Team,
>     >>
>     >>                     we are going to sprint on plone-react this month
>     >>                     in Bonn:
>     >>
>     >>                   
>      https://plone.org/events/sprints/plone-react-sprint-bonn-2018
>     <https://plone.org/events/sprints/plone-react-sprint-bonn-2018>
>     >>                   
>      <https://plone.org/events/sprints/plone-react-sprint-bonn-2018
>     <https://plone.org/events/sprints/plone-react-sprint-bonn-2018>>
>     >>
>     >>                     I'd like to ask the framework team to declare
>     this
>     >>                     sprint a strategic sprint.
>     >>
>     >>                     We think that plone-react is the most promising
>     >>                     candidate as a front-end for a new headless Plone
>     >>                     right now and we think that it is important to
>     >>                     further explore that option.
>     >>
>     >>                     The goals of the sprint are:
>     >>
>     >>                     - Contributing back our recent work in a client
>     >>                     project to plone-react
>     >>                     - Upgrade to React 16
>     >>                     - Improve error handling
>     >>                     - Continue to work on improving the Pastanga
>     >>                     toolbar and the Pastanaga editor
>     >>
>     >>                     We still have a few seats left, if anyone is
>     >>                     interested to help us. Though, some React
>     >>                     knowledge is mandatory, since this will be a very
>     >>                     focused sprint. Remote sprinting is also possible
>     >>                     (Asko will join us remotely).
>     >>
>     >>
>     >>                 Hi Timo and all.
>     >>                 It is quite some time the framework team meetings are
>     >>                 not happening and AFAIK no meeting is scheduled the
>     >>                 next week.
>     >>                 Anyway if somebody is available to discuss this and
>     >>                 other topics on the next Tuesday I should be
>     available.
>     >>
>     >>                 Ciao!
>     >>                 --
>     >>                 @ale_pisa - http://ale-rt.github.io -
>     >>                 http://alepisa.blogspot.com -
>     >>                 https://it.linkedin.com/in/apisa
>     <https://it.linkedin.com/in/apisa>
>     >>                 <https://it.linkedin.com/in/apisa
>     <https://it.linkedin.com/in/apisa>>
>     >>                 _______________________________________________
>     >>                 Framework-Team mailing list
>     >>                 Framework-Team at lists.plone.org
>     <mailto:Framework-Team at lists.plone.org>
>     >>                 <mailto:Framework-Team%40lists.plone.org
>     <mailto:Framework-Team%2540lists.plone.org>>
>     >>               
>      https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>
>     >>                 <https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>>
>     >>
>     >                 _______________________________________________
>     >                 Framework-Team mailing list
>     >                 Framework-Team at lists.plone.org <mailto:Framework-Team at lists.plone.org>
>     >                 <mailto:Framework-Team at lists.plone.org
>     <mailto:Framework-Team at lists.plone.org>>
>     >               
>      https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>
>     >                 <https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>>
>     >
>     >
>     >             _______________________________________________
>     >             Framework-Team mailing list
>     >             Framework-Team at lists.plone.org <mailto:Framework-Team at lists.plone.org>
>     >             <mailto:Framework-Team at lists.plone.org
>     <mailto:Framework-Team at lists.plone.org>>
>     >           
>      https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>>
>     >
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > Framework-Team mailing list
>     > Framework-Team at lists.plone.org <mailto:Framework-Team at lists.plone.org>
>     > https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>
>     >
>     _______________________________________________
>     Framework-Team mailing list
>     Framework-Team at lists.plone.org <mailto:Framework-Team at lists.plone.org>
>     https://lists.plone.org/mailman/listinfo/plone-framework-team
>     <https://lists.plone.org/mailman/listinfo/plone-framework-team>
> 
> 


More information about the Framework-Team mailing list