Hey Lars, For me it is important to understand the project's goals crystal clear. So that we can bring in some energy in a well aligned mode even if intensity is limited. One of my favorite topics is still teaching and education in general and see a huge potential in the Apache training project, if we could align it with the training demand of the community.
Let me comment on the current goals (from webpage): To sum up, the main goals for this project: - Develop shared material that can be used for training Provide a documentation framework for Apache projects to create and release training artefacts via Apache Training. Apache Training as a project is the host for offering artefacts in a central place and also it is the goto place for other projects so that the training material aspect (as in aspect oriented programming) is covered by additional people. => Think of a set of artefacts, starting from a quickstart guide, developer guide, pitch deck, intro video, etc. where experts from other domains come in and help producing such content, or just collecting links to existing. => Existing content can now be linked to certain skill levels so that learning paths emerge. - Cross-project This is by nature a fundament of the Apache Training project. - Focused on Apache but also 3rd party projects where it makes sense Maybe we should focus on Apache projects for active collaboration, but promote generic usage by other communities. - Develop “labs” or “hands-on” exercises Provide guidelines and templates and also a "test driver community" for such tutorials and exercises. Provide links to repositories with relevant tutorials and "bring those artefacts" into the scope of Apache Training, rather than creating new material from scratch. Fokus on reusing and pointing to existing content. - Develop or document an infrastructure that can be used for those labs Let's focus on the procedure of content creation, and curation. Running IT infrastructure for training modules looks a bit too heavy, also from an economical perspective. - Potentially develop tools to manage the material (e.g. a “slide” repository that contains “modules” that can be easily reused and combined) Defining the modules, scope, skills, prerequisites and also pointers to material is key to any training material creation project. Instead of maintaining the artifacts of a particular Apache project, here we should just structure the results of the experts contributions, and by letting them know that material is needed we can initiate the collaboration, eventually. Example: If I find it cool to create a tutorial for Apache XYZ, I would go to AXYZ and create material within that project, but using the Apache Training templates. Next, I'd provide the material for review, in Apache Training people would find this material and help improving it, even it they never had looked into AXYZ alone. What I need in this moment is not the AXYZ expert, but one with an Apache Training mindset. Hence I keep the content in the AXYZ project but using cross-project collaboration brings all projects forward, and it gives training artefacts a home everybody finds easily. Does this make sense? Cheers, Mirko Am Mi., 15. Feb. 2023 um 17:51 Uhr schrieb Lars Francke < [email protected]>: > Hi Chris, Mirko, > > I am now reading my mails again (as promised last time), so at least that > works better but unfortunately that didn't translate into any action on my > end. > There has also not been a lot of interest from the "outside" (Mirko and a > few others being exceptions but it's certainly not been overwhelming). > > As such I'd be happy to wind this project down, unless anyone else wants to > step up and "take over". > Mirko, your ideas about outreach to the projects sounds great and if you're > interested in getting something done please do so. > I promise that I'll do my best in supporting you! > > Cheers, > Lars > > > > On Wed, Feb 15, 2023 at 1:33 PM Mirko Kämpf <[email protected]> > wrote: > > > Hi Christofer, > > > > I am not sure if the goals of the project are clear to the contributors > and > > potential new contributors. > > > > From time to time I look into this project but I found it hard to > > understand a pattern. Because all training material > > about other Apache projects requires active knowledge about that project > - > > but maybe the experts in those projects > > are not always keen on writing training content. Hence, I think it is > > important to get linked to all those active Apache projects, > > and focus here in this particular project on "the Apache way of doing > > trainings and materials" --- maybe I am a bit late to the party > > and this has been discussed in the past. > > > > I think, opening towards non coders and linking people from multiple > > projects could bring Apache Training to the next level. > > Has this been done already in the past? > > > > Cheers, > > Mirko > > > > > > Am Mi., 15. Feb. 2023 um 13:21 Uhr schrieb Christofer Dutz < > > [email protected]>: > > > > > Hi all, > > > > > > So, we’ve missed another report. I’m not really happy with this state. > > > So, I would like to discuss with you, if we should give up Training or > > > what you folks think we should do? > > > > > > I personally am not happy with the way it’s currently running and would > > be > > > in favor for giving it up. > > > > > > Chris > > > > > > > > > > -- > > > > Dr. rer. nat. Mirko Kämpf > > Müchelner Str. 23 > > 06259 Frankleben > > > -- Dr. rer. nat. Mirko Kämpf Müchelner Str. 23 06259 Frankleben
