Hi all, I have absolutely no objections to not retiring, if there is activity. It just fealt as if all this project was doing, was causing me to invest time to keep everything up to date, someone to waste time publishing incubator reports, ipmc members to waste time reading and approving them and the board for doing the same.
If there’s activity and interest, I’m happy to continue …. Just picking my fights a bit right now and trying to rid myself of commitments that only consume time and benefit no one. Chris Von: Rich Bowen <[email protected]> Datum: Mittwoch, 11. September 2024 um 16:21 An: [email protected] <[email protected]> Betreff: Re: Preparation for next release On Feb 6, 2024, at 4:49 PM, Mirko Kämpf <[email protected]> wrote: > > Hey, Apache Training community, > > ... > Last year, there was the one question: Should the project be retired? > I personally said: No. This is not the right time to do this. But even > after one year, > I do not feel that we clearly know what direction we want to steer this > project. Hi, Mirko and everyone. My biggest challenge with the Training project has always been that I have never before successfully built one of the presentations. I’m a writer, not a programmer. I know nothing about Maven, and found the failure messages completely unhelpful. BUT - with some help from Mirko and Chris, and with the new release, everything is building, and I’m excited to use Training.a.o to create my own conference presentations, but, more importantly, to write presentations that anyone can pick up and present. This is something I’ve wanted to do for AGES. So, no, please don’t retire the project. With your blessing, I’ll be creating a bunch of presentations, first under the Apache/ and Apache/ComDev trees, about how the ASF works, how ComDev works, and also onboarding content for committers, members, directors, and contributors in general. As for other things that were proposed in this thread - yes, I think that getting TLPs using these tools helps everyone - it provides a standard presentation format, and it creates content that anyone with basic knowledge can pick up and present at a meetup, to their coworkers, at a conference, or really anywhere. This is a HUGE power-up for projects. Once we have some strong sample content, we can, and should, approach people at conferences (Hey! Come to Community Over Code in Denver next month!!) who have given talks, and suggest that they donate that presentation to the training project for conversion into the standard format. Once a project has a sample presentation, we can approach that project’s user/dev lists, point to the resource, and encourage improvements, enhancements, and more presentations. Again, this is work that I have wanted to do for *years*, but have been hindered by being unable to get any of the tools to work. I’m excited to finally be able to jump in and get stuff done. (Psst: Two PRs out there for your consideration!) — Rich Bowen [email protected]
