Hello, my apologies for the delay!  I've updated the report at:
https://cwiki.apache.org/confluence/display/INCUBATOR/May2022#training
but copied it here for reference.

It's a wiki, so we can probably make any changes or updates if anybody
needs or wants them!

All my best, and talk to you soon, Ryan

--------------------
## 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.

### Three most important unfinished issues to address before graduating:

1. Restart the Community
2. Start doing releases
3. Make Apache Training more well known

### Are there any issues that the IPMC or ASF Board need to be aware of?

As mentioned in the previous reports, activity in the Training project has
been very low. There was nearly no mailing list activity in the first
quarter, and virtually no commits.

### How has the community developed since the last report?

In April, one of the mentors (cdutz) launched a discussion on the mailing
list to see what the community wanted to do with the project. Together, we
brought up some ideas why the initial enthusiasm for Training materials
has sputtered out.

Some of the ideas to make the project more relevant and build community
include:

- maintaining presence and visiblity as in-person conferences return,
- encourage conversation and brainstorming about effective presentation
resources on the dev website,
- changing our focus to include self-learning resources for Apache
projects, and
- building and publishing Training web artifacts on the project website.

Even if it seems that we haven't yet found a clear and compelling niche,
the existing community is willing to continue work to see where we can
improve.

### How has the project developed since the last report?

Specific work on showcasing web artifacts on the Training project website
has started, as a quick win to demonstrate the project value.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:

### Date of last release:

2020-07-03 Presentation on NavigatingASFIncubation

### When were the last committers or PPMC members elected?

2020-11-23 Gautam Gupta (Comitter)

### Have your mentors been helpful and responsive?

Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

It was a project mentor that relaunched the discussion after our long
period of inactivity.

### Is the PPMC managing the podling's brand / trademarks?

Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

No issues.

### Signed-off-by:

- [ ] (training) Craig Russell
Comments:
- [ ] (training) Christofer Dutz
Comments:
- [ ] (training) Justin Mclean
Comments:
- [ ] (training) Lars Francke
Comments:

### IPMC/Shepherd notes:

On Mon, May 2, 2022 at 4:55 PM Christofer Dutz
<[email protected]> wrote:
>
> Any update on this?
>
> -----Original Message-----
> From: Christofer Dutz <[email protected]>
> Sent: Donnerstag, 28. April 2022 10:49
> To: [email protected]
> Subject: RE: Podling Training Report Reminder - May 2022
>
> Hi all,
>
> So, Ryan, I think it would be great if you could get started on this :-) The 
> link to the wiki page is in the mail.
> If you need any permissions, just let me know and I'll take care of 
> everything.
>
> With the current activity, I think it doesn't really matter if you write it 
> now or later.
> The earlier it's in the better I would probably feel.
>
> Would highly appreciate it :-)
>
> Chris
>
>
>
> -----Original Message-----
> From: [email protected] <[email protected]>
> Sent: Donnerstag, 28. April 2022 02:50
> To: [email protected]
> Subject: Podling Training Report Reminder - May 2022
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache Incubator 
> PMC. It is an initial reminder to give you plenty of time to prepare your 
> quarterly board report.
>
> The board meeting is scheduled for Wed, 18 May 2022.
> The report for your podling will form a part of the Incubator PMC report. The 
> Incubator PMC requires your report to be submitted 2 weeks before the board 
> meeting, to allow sufficient time for review and submission (Wed, May 04).
>
> Please submit your report with sufficient time to allow the Incubator PMC, 
> and subsequently board members to review and digest. Again, the very latest 
> you should submit your report is 2 weeks prior to the board meeting.
>
> Candidate names should not be made public before people are actually elected, 
> so please do not include the names of potential committers or PPMC members in 
> your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> ----------------------
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>     the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>     towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>     aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2022
>
> Note: This is manually populated. You may need to wait a little before this 
> page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> -------
>
> Mentors should review reports for their project(s) and sign them off on the 
> Incubator wiki page. Signing off reports shows that you are following the 
> project - projects that are not signed may raise alarms for the Incubator PMC.
>
> Incubator PMC

Reply via email to