Hi Mirko, I'm afraid I can't remember the procedure to get access to that Wiki but I will read it now and move it there!
Thank you very much. Cheers, Lars On Wed, Jul 5, 2023 at 2:25 PM Mirko Kämpf <mirko.kae...@gmail.com> wrote: > > Hello, > > I intend to submit the draft of the podling report to this page: > *https://cwiki.apache.org/confluence/display/incubator/July2023#training > <https://cwiki.apache.org/confluence/display/incubator/July2023#training>* > > But unfortunately, I still have no write permission to this wiki. > My username is: mirko.kae...@gmail.com > > > Here is the draft in the *Apache Training Wiki:* > https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#PodlingReports-July2023 > <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#PodlingReports-June2023> > > And at the end of this mail is the full text of the draft. > > It has been shared on the project's developer list. > No comments so far. > > Cheers, > Mirko > > > > > > 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 have been started. > > *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> > > > > *Activity has started to grow since the last report. We again failed to > provide the report on time, but this will change soon.Two persons joined > our conversation on the dev-list (Eric and Rich).* > > > *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> > > An pro-active request for a content / tool donation has been placed - but > it was rejected. The person I asked has no longer access to the tool I had > in mind. > > Creation of a ASF onboarding training module has been announced. > > A tool for inspecting documentation in Github repositories (ASF projects) > which will lead towards automatic training related content extraction has > been started. > > PR activity continuous on a low level since the last report. > > > *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 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
