Thank you!
On Wed, Aug 2, 2023 at 1:08 PM Christofer Dutz <[email protected]> wrote: > > And done :) > > Von: Christofer Dutz <[email protected]> > Datum: Mittwoch, 2. August 2023 um 13:01 > An: [email protected] <[email protected]> > Betreff: AW: Podling-Report July 2023 > I’ll take care of it. > > Thanks for writing the report, Mirko :-) > > Chris > > > Von: Lars Francke <[email protected]> > Datum: Mittwoch, 2. August 2023 um 12:06 > An: [email protected] <[email protected]> > Betreff: Re: Podling-Report July 2023 > Hi Mirko, > > thank you. Unfortunately "one of us" has to submit the report. > I'm on holiday without much time for laptop work until Friday. > Chris, do you have time to move the report over? > > Cheers, > Lars > > On Wed, Aug 2, 2023 at 11:33 AM Mirko Kämpf <[email protected]> wrote: > > > > Hi, > > > > I am back and the August report is covered. > > > > Just added the report to the project Wiki page: > > https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#PodlingReports-August2023 > > > > I also requested write permission to the wiki in which the report has to be > > submitted. > > The attached MD file has also been sent to: [email protected] , > > where I asked for the right permissions, according to the docu in the top > > of the report page. > > > > Let's hope that this permission issue gets solved soon. > > > > Now I think we have a routine regarding the reporting procedure and also > > some > > small steps done, steps which lead us towards a more active future. > > > > Cheers, > > Mirko > > > > > > > > > > Am Mi., 2. Aug. 2023 um 10:42 Uhr schrieb Christofer Dutz > > <[email protected]>: > >> > >> Hi all, > >> > >> So, what’s the progress on this? Is this base still covered? > >> > >> Chris > >> > >> Von: Christofer Dutz <[email protected]> > >> Datum: Mittwoch, 26. Juli 2023 um 08:49 > >> An: [email protected] <[email protected]> > >> Betreff: AW: Podling-Report July 2023 > >> Hi Eric, > >> > >> thanks for picking up on this … but I guess if you write one now, it’s > >> going to be the August report ;-) > >> > >> Yeah … if we have that one, we’re back on track with our reporting > >> schedule and can go back to one report ever 3 months. > >> Our official schedule is: February, May, August, November > >> > >> Thanks again for this. > >> Chris > >> > >> > >> > >> Von: Eric Tessenow <[email protected]> > >> Datum: Mittwoch, 26. Juli 2023 um 06:52 > >> An: [email protected] <[email protected]> > >> Betreff: Podling-Report July 2023 > >> Dear all, > >> > >> as Mirko is currently not available, he asked me to initiate the podling > >> report for July, the last publication actually being addressed to June. > >> > >> I would like to ask for your contributions by end of Friday. > >> > >> As I do not have the permissions to manage the confluence-pages > >> (apache-training wiki and incubator wiki) yet, please someone with the > >> credentials, I assume > >> > >> Craig, Christopher, Justin, or Lars, you might be able to, please assist if > >> possible to hold the deadline. > >> > >> Hope your all otherwise alright. > >> > >> Best wishes, > >> > >> Eric > >> Adjusted copy of Podling Report July:July 2023 > >> > >> *Training > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#training>* > >> > >> The Training project aims to develop resources which can be used for > >> training purposes in various media formats, languages and for various > >> Apache and non-Apache target projects. > >> > >> Training has been incubating since 2019-02-21. > >> > >> In June, we started adjusting the project goals. Besides a pure focus on > >> content creation tools we have identified the need for two additional > >> aspects: > >> (1) For ASF processes some documentation exists, e.g. > >> https://community.apache.org/contributor-ladder, but the ASF member journey > >> is still a challenge for many new members, especially those with less > >> coding experience. > >> As a solution it has been suggested to provide training material for the > >> following problems: > >> * You've just graduated to a TLP. What are the challenges you will now > >> face? > >> * New committer onboarding > >> * New PMC member onboarding > >> * New PMC Chair onboarding > >> * New board member onboarding > >> > >> (2) Creation of some general recommendations/guidelines for: > >> * managing/validation of training material contributions of arbitrary ASF > >> projects > >> has been propsed. > >> > >> Initial discussion of the topics are ongoing. > >> > >> *We expand our focus now on the following aspects:* > >> > >> *We have to work on strategies to increase the** participation and the > >> visibility of the project and its goals.* > >> > >> *Besides requests** for contributions from individual contributors** from > >> other Apache projects we want to show what the Apache Training project can > >> offer to those projects**.* > >> > >> *We should build on the assumption that synergy and network effects can > >> help us to increase the community around training and skill management > >> topics.* > >> > >> > >> *Three most important unfinished issues to address before graduating:* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#three-most-important-unfinished-issues-to-address-before-graduating> > >> > >> 1. Improve the community participation (other Apache projects should > >> actively be linked to this project, since they "have the content") > >> 2. *(Re)define the short-, mid-, and long-term goals of the project.* > >> 3. *Select an approach to handle non coding / non document related tasks > >> (e.g., community related activities on events)* > >> 4. *Create a strategy how this projects contributes to or is supported > >> by other Apache projects* > >> 5. Create a tutorial on how the tools provided by this project can be > >> used to create own content > >> 6. Review current policies around contribution review and releases to > >> find a pragmatic compromise > >> > >> *Are there any issues that the IPMC or ASF Board need to be aware of?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of> > >> > >> The Training Project needs more contribution from other Apache projects, > >> hence a clear communication strategy for interlinking existing projects > >> with the Apache Training project is needed. > >> > >> We need feedback from other Apache projects on the presentations and > >> trainings developed till now. > >> > >> > >> > >> *In order to improve this collaboration we suggest to investigate the > >> status of other project’s documentation in a systematic approach, > >> especially with an eye on available training related material.* > >> > >> *How has the community developed since the last report?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#how-has-the-community-developed-since-the-last-report> > >> > >> *no changes* > >> > >> > >> *How has the project developed since the last report?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#how-has-the-project-developed-since-the-last-report> > >> > >> *no changes* > >> > >> > >> *How would you assess the podling's maturity?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#how-would-you-assess-the-podlings-maturity> > >> > >> There are currently some issues with this podling that we are working to > >> address, we believe that the issues are not yet critical and can be turned > >> around from within the community but want to make the board aware of this > >> early on. > >> > >> - Initial setup oft he project’s structure: *Goals and strategy needs > >> refinement.* > >> - Working towards first release: *What type of artefacts to release is > >> not clear, due to unclear goals and strategy.* > >> - Community building: *The community exists of a very small number of > >> people but is more or less invisible, as of today (April 2023).* > >> - Nearing graduation: *Currently, we are far away from graduation.* > >> > >> > >> *When were the last committers or PPMC members elected?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#when-were-the-last-committers-or-ppmc-members-elected> > >> > >> November 2020 > >> > >> > >> *Have your mentors been helpful and responsive?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#have-your-mentors-been-helpful-and-responsive> > >> > >> Mentors have been responsive and helpful when reached out to. > >> > >> > >> *Is the PPMC managing the podling's brand / trademarks?* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#is-the-ppmc-managing-the-podlings-brand--trademarks> > >> > >> The name search process has not yet been started, as there is still time to > >> do that if and when graduation draws nearer. > >> > >> The PPMC is actively monitoring usage of the Podlings current name on other > >> sites. > >> > >> The Podling is not directly affiliating with any sponsors donating content > >> and presenting an independent image on the webpage. > >> > >> > >> *Signed-off-by:* > >> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#signed-off-by> > >> > >> - (training) Craig Russell > >> Comments: > >> > >> - (training) Christofer Dutz > >> Comments: > >> > >> - (training) Justin Mclean > >> Comments: > >> > >> - (training) Lars Francke > >> Comments: > > > > > > > > -- > > > > Dr. rer. nat. Mirko Kämpf > > Müchelner Str. 23 > > 06259 Frankleben > >
