Hi all, I for my part have tried to keep clear of the inner workings of the project, as my main goal was to keep the core framework running, as this was how I got involved in it when the project was incepted after ApacheCon Las Vegas.
I’m happy to continue maintaining it. I did notice that we have 3 repos from other project that seem to aim at training material: https://github.com/apache/flink-training (Seems to contain exercises to some training material which I can’t say where it is) https://github.com/apache/tomcat-training/blob/main/presentations/tomcat-11-preview.html (Seems to be some tomcat related training material) https://github.com/apache/incubator-liminal (Some incubating ML framework) Maybe another approach would be to contact these projects and help them migrate to Apache Training? Chris Von: Mirko Kämpf <mirko.kae...@gmail.com> Datum: Sonntag, 14. April 2024 um 08:38 An: dev@training.apache.org <dev@training.apache.org> Betreff: Fwd: Podling Report - February 2023 (delyed to March) Hello, Apache Training people, our last podling report didn't make it to the Incubator wiki for review. *Reason was:* - I had no permissions to write to that wiki. Today I checked again, and it worked, I could edit April's page with the reports to verify it. Problem solved. Next report is on track. *Observation:*We still have zero to no community activity, besides the attempt to release the Training Tools (Nexus access is another blocker!). A discussion regarding our future goals couldn't be done yet because it had to be postponed. But we don't give up ... *Our talk at the ASF conference allows us to bring our topic a bit closer to other projects. *We have the opportunity to speak together with Apache Wayang (Glaucia) on stage about our projects. We both plan the outline of our presentation next week. *Here is my ask to the Apache Training people:*Could we please find a consensus regarding one problem we want to solve? *And here is the proposal: * I start with looking at our purpose: The purpose of the Training project is to create high-quality training material for various projects in an open source form. Up until now everyone who wants to offer a Training course for one of the Apache projects needs to create her or his own slides/labs and keep them up-to-date. This is a significant investment of time and money. This project aims to spread that burden and help all Apache projects as we can create shared resources and we can also create cross-project trainings. In order to contribute to those valuable objectives, we should drive some actions towards measurable goals. One path could be: We "start active training collaboration" with a single ASF Project - Apache Wayang - in this case, and find out what support from ASF Training "they" could think of. What I expect from that question is: We in ASF-T should get an understanding of the real demand. We assume from experience that there is demand for collaboration on training materials but we have not validated what that really means. We have to find out how others think about delivery of training and collaboration on that topic. Hence my key result #1 would be the following. *Expected result:*We, as the ASF-Training community, have a list of "training material" related wishes from 10 ASF projects (5 well established, 5 incubating). >From this list we can derive our future contributions to ASF. *Insights we want to gain:* We know what training means for them. How they typically handle training topics. What training material exists in which form for which audience. If they would participate in a broader training initiative, and how they could imagine this. What their dream about training activities related to their own project is. I prepare a survey using Google Forms and share it with a number x of ASF projects. Which projects I have asked will also be listed in a Google Spreadsheet. All GD-links will be shared on this channel for transparency. For this I will send another email, specifically for that activity. You are invited to participate. *Here is the plan:*Step 1 : Drafting the Survey and letter to the projects (deadline 17-th of April) Step 2 : Sending the survey to the projects (until 19-th of April) Step 3 : Send second round (until 25-th of April) Step 4 : Review responses and draw conclusions 10-th of may Step 5 : Compile the results into our presentation. For now I would be happy to hear your thoughts, regarding this attempt to fill the ASF Training mission with a bit of life. The Conference in Bratislave is a great opportunity for doing so. Who else of you will be there? Have a great weekend, Cheers Mirko ---------- Forwarded message --------- Von: Mirko Kämpf <mirko.kae...@gmail.com> Date: Sa., 2. März 2024 um 17:40 Uhr Subject: Podling Report - February 2023 (delyed to March) To: <dev@training.apache.org> Hello Apache Training people, here is the draft for our FEB-2024 podling report. Please add your contributions to it and let me know if you have any questions. I am still not able to edit the report submission page in the wiki. Request has been renewed right now. Best regards Mirko # February 2024 ## 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. The attempt started in June 2023, for reviewing and adjusting the project goals, has not yet been finalized. 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 teaching new participants the following procedures: * New committer onboarding * inter-project collaboration * New PMC member onboarding * New PMC Chair onboarding * New board member onboarding * You've just graduated to a TLP. What are the challenges you will now face? (2) Creation of some general recommendations/guidelines for: * managing/validation of training material contributions of arbitrary ASF projects has been proposed. We expand our focus now on the following aspects: * We work on strategies to increase the participation and the visibility of the Apache Training 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: * Improve the community participation (other Apache projects should actively be linked to this project, since they "have the content") (Re)define the short-, mid-, and long-term goals of the project. * Select an approach to handle non coding / non document related tasks (e.g., community related activities on events) * Create a strategy how this projects contributes to or is supported by other Apache projects * Create a tutorial on how the tools provided by this project can be used to create own content * Review and simplify 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? The Apache 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 tools, workflow, resulting 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? Initial connection to Apache Wayang has been established. The proposed presentation for the Community over Code conference in Bratislava has been accepted. This will be a collaboration between the Apache Training and Apache Wayang project. We discussed the idea of supporting presenters at the Apache Conference in 2024 in Bratislava with the Apache Training tools (Presentation template). # How has the project developed since the last report? A release for the provided tools has been done. A in person video conference has been planed. # How would you assess the podling's 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 a refinement and a re-alignment. Community building: The community exists of a very small number of people but is more or less invisible. Nearing graduation: Currently, we are far away from graduation. # When were the last committers or PPMC members elected? August 2023 # 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? 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: (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 -- Dr. rer. nat. Mirko Kämpf Müchelner Str. 23 06259 Frankleben
