Hi Alex, there is no attachment and no file in your email.
Cheers, Mirko Am Mi., 12. Apr. 2023 um 15:29 Uhr schrieb Alexis TADIFO < [email protected]>: > There's the file. > > Cheers. > > *Alexis C. TADIFO* > > 📞 (+237) 697 991 590 📞(+1) 418 569 8877 > > > Le mer. 12 avr. 2023 à 02:59, Mirko Kämpf <[email protected]> a > écrit : > >> Hi Alexis, >> >> the image you shared is not visible in my mail client. >> >> This is how it looks like: >> [image: image.png] >> Would you please try again? >> >> Thanks. >> >> Cheers, >> Mirko >> >> >> >> Am Di., 11. Apr. 2023 um 19:10 Uhr schrieb Alexis TADIFO < >> [email protected]>: >> >>> Hello Mirko, >>> I am Very delighted by your introduction of OKRs. >>> There it's a visual transcription of your contribution. >>> [image: ApacheTraining — Mirko.png] >>> Cheers. >>> >>> *Alexis C. TADIFO* >>> >>> 📞 (+237) 697 991 590 📞(+1) 418 569 8877 >>> >>> >>> Le mar. 11 avr. 2023 à 12:42, Christofer Dutz <[email protected]> >>> a écrit : >>> >>>> Hi Mirko, >>>> >>>> Well, I remember that when we started training, we had quite some >>>> momentum, but when we put up too many rules, that killed the buzz. >>>> So, we moved to the total opposite (giving anyone with Apache commit >>>> rights in any project, to also have commit rights here). Unfortuantely we >>>> never managed to get the drive back. So not 100% sure, if we concentrated >>>> on OKRs, still someone would have to do the work. So not quite sure how >>>> OKRs would help here? >>>> >>>> Thing is, we need to get the community engaged again ... but community >>>> building is hard work (harder than coding) ... guess we’d need people >>>> willing to put in the effort. >>>> >>>> Chris >>>> >>>> >>>> Von: Mirko Kämpf <[email protected]> >>>> Datum: Dienstag, 11. April 2023 um 16:58 >>>> An: [email protected] <[email protected]> >>>> Betreff: OKRs for Apache Training - Proposal >>>> Hey, >>>> >>>> In order to bring some more energy and focus into the project I suggest >>>> to >>>> start using OKRs. >>>> >>>> Since I am not sure if this is a way how ASF projects typically work I >>>> decided to give it a try. At least on my personal level it makes things >>>> easier, so I thought, for others it could work as well. >>>> >>>> I added my first OKR draft to this email. >>>> >>>> Please let me know what you think. >>>> >>>> Cheers, >>>> Mirko >>>> >>>> O1 We improve community participation to get ready for continuous >>>> colaboration on training material. >>>> KR1 We conducted a monthly session (30 min, recorded) to clarify issues >>>> and >>>> prep next steps. >>>> KR2 We have selected an approach to manage community related events. >>>> KR3 We have documented and used a slim process for content contribution. >>>> O2 We work continuously on our strategy. >>>> KR1 Each contributor has shared its own vision document which describes >>>> how >>>> he envisions the future of Apache Training and his personal >>>> contributions. >>>> KR2 We have conducted a brain-storming session using MIRO to create a >>>> project vision board. >>>> KR3 We have integrated all contributions regarding the project's vision >>>> and >>>> its future strategy and updated the webpage accordingly. >>>> O3 We actively integrate our activities with other Apache projects. >>>> KR1 We have a standardized interview sheet for collecting information >>>> about >>>> other projects and how they see Apache Training. >>>> KR2 We have interviewed members of 5 ASF projects. >>>> KR3 We extracted our learnings about next collaboration steps from >>>> interview results. >>>> KR4 We have published our findings in a blog. >>>> O4 We provide a standardized approach for training artefact creation. >>>> KR1 We have a template for presentations. >>>> KR2 We have a template for tutorials / workshop sessions >>>> >>> >> >> -- >> >> Dr. rer. nat. Mirko Kämpf >> Müchelner Str. 23 >> 06259 Frankleben >> >> -- Dr. rer. nat. Mirko Kämpf Müchelner Str. 23 06259 Frankleben
