You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@training.apache.org by Christofer Dutz <ch...@c-ware.de> on 2023/03/02 12:23:35 UTC
AW: [DISCUSS] How to proceed?
Ok … so It’s report time again … who’s up to the challenge?
Chris
Von: Christofer Dutz <ch...@c-ware.de>
Datum: Samstag, 18. Februar 2023 um 15:08
An: dev@training.apache.org <de...@training.apache.org>
Betreff: Re: [DISCUSS] How to proceed?
Hi all,
Was offline for a day or two because of email-issues … but catching up right now.
Well for me the goal was to provide the infrastructure so it’s easy to create training material in a collaborative fashion. But the goal of the project itself I always considered to become a resource to go to, if you need training material for Apache projects. That’s also why every Apache committer generally has commit rights. The idea was that this allows everyone to work on their material.
Chris
From: Mirko Kämpf <mi...@gmail.com>
Date: Friday, 17. February 2023 at 12:20
To: dev@training.apache.org <de...@training.apache.org>
Subject: Re: [DISCUSS] How to proceed?
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 <
christofer.dutz@c-ware.de>:
> 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
Re: [DISCUSS] How to proceed?
Posted by Lars Francke <la...@gmail.com>.
Hi Mirko,
thank you very much. Unfortunately, the attachment has been stripped.
Cheers,
Lars
On Fri, Mar 3, 2023 at 10:04 AM Mirko Kämpf <mi...@gmail.com> wrote:
>
> Hey Apache Training project team,
>
> here is a draft for the March '23 report.
>
> For fast access in directly in the mail, but also attached to this email as
> a MS-Word file.
> This way, I save some time, because I have to reactivate my ASF login.
>
>
> In green italic you find the my comments / thoughts. In yellow, the facts I
> can't answer.
> Please have a look and let me know what you think.
>
> Cheers,
> Mirko
>
>
> March 2023
>
> Training
> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#training>
>
> The Training project aims to develop *procedures and *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:
> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#three-most-important-unfinished-issues-to-address-before-graduating>*
>
> 1. Improve the participation from community for Apache Training Project
> 2. *Identify the short-, mid-, and long-term goals of the project.*
> 3. *Select an approach to handle non coding / non document related taske*
> 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. It
> also needs feedback from other Apache Projects on the presentations and
> trainings developed till now.
>
> *In order to improve this collaboration we suggest investigating 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 remained low since the last report. We have to work on
> strategies to increase the** participation and the visibility of the
> project and its goals. Besides q**ueries for contributions from individual
> contributors** from other Apache projects we want to show what the Apache
> Training project can offer 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. *
>
>
>
> *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>*
>
> *No n**ew training **material has been provided. *
>
> *PR activity** continues* *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*
> - Working towards first release: *What type of artifacts to release is
> not clear, due to unclear goals and strategy.*
> - Community building: *The community exists of a small number of people
> but is more or less invisible, as of today.*
> - 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>*
>
> *May 2021*
>
> *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: We may need more outreach to PMCs to ask them to add material.
> - (training) Christofer Dutz
> Comments:
> - (training) Justin Mclean
> Comments:
> - (training) Lars Francke
> Comments:
>
> *IPMC/Shepherd notes:
> <https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#ipmcshepherd-notes>*
>
>
>
> Am Do., 2. März 2023 um 21:48 Uhr schrieb Mirko Kämpf <
> mirko.kaempf@gmail.com>:
>
> > OK. I'll draft the report tomorrow.
> > Cheers,
> > Mirko
> >
> > Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
> > 18:16:
> >
> >> Hi Mirko,
> >>
> >> Well, the only content I could provide, would be that we did discuss the
> >> future of the project and that discussion is ongoing.
> >>
> >> Chris
> >>
> >>
> >> Von: Mirko Kämpf <mi...@gmail.com>
> >> Datum: Donnerstag, 2. März 2023 um 14:47
> >> An: dev@training.apache.org <de...@training.apache.org>
> >> Betreff: Re: [DISCUSS] How to proceed?
> >> Hey,
> >>
> >> I am ready to contribute / to report.
> >>
> >> But I need some content to take over the reporting task.
> >>
> >> Best,
> >> Mirko
> >>
> >> Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
> >> 13:23:
> >>
> >> > Ok … so It’s report time again … who’s up to the challenge?
> >> >
> >> > Chris
> >> >
> >> >
> >> > Von: Christofer Dutz <ch...@c-ware.de>
> >> > Datum: Samstag, 18. Februar 2023 um 15:08
> >> > An: dev@training.apache.org <de...@training.apache.org>
> >> > Betreff: Re: [DISCUSS] How to proceed?
> >> > Hi all,
> >> >
> >> > Was offline for a day or two because of email-issues … but catching up
> >> > right now.
> >> >
> >> > Well for me the goal was to provide the infrastructure so it’s easy to
> >> > create training material in a collaborative fashion. But the goal of the
> >> > project itself I always considered to become a resource to go to, if you
> >> > need training material for Apache projects. That’s also why every Apache
> >> > committer generally has commit rights. The idea was that this allows
> >> > everyone to work on their material.
> >> >
> >> > Chris
> >> >
> >> > From: Mirko Kämpf <mi...@gmail.com>
> >> > Date: Friday, 17. February 2023 at 12:20
> >> > To: dev@training.apache.org <de...@training.apache.org>
> >> > Subject: Re: [DISCUSS] How to proceed?
> >> > 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 <
> >> > christofer.dutz@c-ware.de>:
> >> >
> >> > > 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
Re: [DISCUSS] How to proceed?
Posted by Mirko Kämpf <mi...@gmail.com>.
Hey Apache Training project team,
here is a draft for the March '23 report.
For fast access in directly in the mail, but also attached to this email as
a MS-Word file.
This way, I save some time, because I have to reactivate my ASF login.
In green italic you find the my comments / thoughts. In yellow, the facts I
can't answer.
Please have a look and let me know what you think.
Cheers,
Mirko
March 2023
Training
<https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#training>
The Training project aims to develop *procedures and *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:
<https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#three-most-important-unfinished-issues-to-address-before-graduating>*
1. Improve the participation from community for Apache Training Project
2. *Identify the short-, mid-, and long-term goals of the project.*
3. *Select an approach to handle non coding / non document related taske*
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. It
also needs feedback from other Apache Projects on the presentations and
trainings developed till now.
*In order to improve this collaboration we suggest investigating 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 remained low since the last report. We have to work on
strategies to increase the** participation and the visibility of the
project and its goals. Besides q**ueries for contributions from individual
contributors** from other Apache projects we want to show what the Apache
Training project can offer 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. *
*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>*
*No n**ew training **material has been provided. *
*PR activity** continues* *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*
- Working towards first release: *What type of artifacts to release is
not clear, due to unclear goals and strategy.*
- Community building: *The community exists of a small number of people
but is more or less invisible, as of today.*
- 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>*
*May 2021*
*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: We may need more outreach to PMCs to ask them to add material.
- (training) Christofer Dutz
Comments:
- (training) Justin Mclean
Comments:
- (training) Lars Francke
Comments:
*IPMC/Shepherd notes:
<https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#ipmcshepherd-notes>*
Am Do., 2. März 2023 um 21:48 Uhr schrieb Mirko Kämpf <
mirko.kaempf@gmail.com>:
> OK. I'll draft the report tomorrow.
> Cheers,
> Mirko
>
> Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
> 18:16:
>
>> Hi Mirko,
>>
>> Well, the only content I could provide, would be that we did discuss the
>> future of the project and that discussion is ongoing.
>>
>> Chris
>>
>>
>> Von: Mirko Kämpf <mi...@gmail.com>
>> Datum: Donnerstag, 2. März 2023 um 14:47
>> An: dev@training.apache.org <de...@training.apache.org>
>> Betreff: Re: [DISCUSS] How to proceed?
>> Hey,
>>
>> I am ready to contribute / to report.
>>
>> But I need some content to take over the reporting task.
>>
>> Best,
>> Mirko
>>
>> Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
>> 13:23:
>>
>> > Ok … so It’s report time again … who’s up to the challenge?
>> >
>> > Chris
>> >
>> >
>> > Von: Christofer Dutz <ch...@c-ware.de>
>> > Datum: Samstag, 18. Februar 2023 um 15:08
>> > An: dev@training.apache.org <de...@training.apache.org>
>> > Betreff: Re: [DISCUSS] How to proceed?
>> > Hi all,
>> >
>> > Was offline for a day or two because of email-issues … but catching up
>> > right now.
>> >
>> > Well for me the goal was to provide the infrastructure so it’s easy to
>> > create training material in a collaborative fashion. But the goal of the
>> > project itself I always considered to become a resource to go to, if you
>> > need training material for Apache projects. That’s also why every Apache
>> > committer generally has commit rights. The idea was that this allows
>> > everyone to work on their material.
>> >
>> > Chris
>> >
>> > From: Mirko Kämpf <mi...@gmail.com>
>> > Date: Friday, 17. February 2023 at 12:20
>> > To: dev@training.apache.org <de...@training.apache.org>
>> > Subject: Re: [DISCUSS] How to proceed?
>> > 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 <
>> > christofer.dutz@c-ware.de>:
>> >
>> > > 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
Re: [DISCUSS] How to proceed?
Posted by Mirko Kämpf <mi...@gmail.com>.
OK. I'll draft the report tomorrow.
Cheers,
Mirko
Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
18:16:
> Hi Mirko,
>
> Well, the only content I could provide, would be that we did discuss the
> future of the project and that discussion is ongoing.
>
> Chris
>
>
> Von: Mirko Kämpf <mi...@gmail.com>
> Datum: Donnerstag, 2. März 2023 um 14:47
> An: dev@training.apache.org <de...@training.apache.org>
> Betreff: Re: [DISCUSS] How to proceed?
> Hey,
>
> I am ready to contribute / to report.
>
> But I need some content to take over the reporting task.
>
> Best,
> Mirko
>
> Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
> 13:23:
>
> > Ok … so It’s report time again … who’s up to the challenge?
> >
> > Chris
> >
> >
> > Von: Christofer Dutz <ch...@c-ware.de>
> > Datum: Samstag, 18. Februar 2023 um 15:08
> > An: dev@training.apache.org <de...@training.apache.org>
> > Betreff: Re: [DISCUSS] How to proceed?
> > Hi all,
> >
> > Was offline for a day or two because of email-issues … but catching up
> > right now.
> >
> > Well for me the goal was to provide the infrastructure so it’s easy to
> > create training material in a collaborative fashion. But the goal of the
> > project itself I always considered to become a resource to go to, if you
> > need training material for Apache projects. That’s also why every Apache
> > committer generally has commit rights. The idea was that this allows
> > everyone to work on their material.
> >
> > Chris
> >
> > From: Mirko Kämpf <mi...@gmail.com>
> > Date: Friday, 17. February 2023 at 12:20
> > To: dev@training.apache.org <de...@training.apache.org>
> > Subject: Re: [DISCUSS] How to proceed?
> > 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 <
> > christofer.dutz@c-ware.de>:
> >
> > > 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
> >
>
AW: [DISCUSS] How to proceed?
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Mirko,
Well, the only content I could provide, would be that we did discuss the future of the project and that discussion is ongoing.
Chris
Von: Mirko Kämpf <mi...@gmail.com>
Datum: Donnerstag, 2. März 2023 um 14:47
An: dev@training.apache.org <de...@training.apache.org>
Betreff: Re: [DISCUSS] How to proceed?
Hey,
I am ready to contribute / to report.
But I need some content to take over the reporting task.
Best,
Mirko
Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
13:23:
> Ok … so It’s report time again … who’s up to the challenge?
>
> Chris
>
>
> Von: Christofer Dutz <ch...@c-ware.de>
> Datum: Samstag, 18. Februar 2023 um 15:08
> An: dev@training.apache.org <de...@training.apache.org>
> Betreff: Re: [DISCUSS] How to proceed?
> Hi all,
>
> Was offline for a day or two because of email-issues … but catching up
> right now.
>
> Well for me the goal was to provide the infrastructure so it’s easy to
> create training material in a collaborative fashion. But the goal of the
> project itself I always considered to become a resource to go to, if you
> need training material for Apache projects. That’s also why every Apache
> committer generally has commit rights. The idea was that this allows
> everyone to work on their material.
>
> Chris
>
> From: Mirko Kämpf <mi...@gmail.com>
> Date: Friday, 17. February 2023 at 12:20
> To: dev@training.apache.org <de...@training.apache.org>
> Subject: Re: [DISCUSS] How to proceed?
> 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 <
> christofer.dutz@c-ware.de>:
>
> > 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
>
Re: [DISCUSS] How to proceed?
Posted by Mirko Kämpf <mi...@gmail.com>.
Hey,
I am ready to contribute / to report.
But I need some content to take over the reporting task.
Best,
Mirko
Christofer Dutz <ch...@c-ware.de> schrieb am Do., 2. März 2023,
13:23:
> Ok … so It’s report time again … who’s up to the challenge?
>
> Chris
>
>
> Von: Christofer Dutz <ch...@c-ware.de>
> Datum: Samstag, 18. Februar 2023 um 15:08
> An: dev@training.apache.org <de...@training.apache.org>
> Betreff: Re: [DISCUSS] How to proceed?
> Hi all,
>
> Was offline for a day or two because of email-issues … but catching up
> right now.
>
> Well for me the goal was to provide the infrastructure so it’s easy to
> create training material in a collaborative fashion. But the goal of the
> project itself I always considered to become a resource to go to, if you
> need training material for Apache projects. That’s also why every Apache
> committer generally has commit rights. The idea was that this allows
> everyone to work on their material.
>
> Chris
>
> From: Mirko Kämpf <mi...@gmail.com>
> Date: Friday, 17. February 2023 at 12:20
> To: dev@training.apache.org <de...@training.apache.org>
> Subject: Re: [DISCUSS] How to proceed?
> 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 <
> christofer.dutz@c-ware.de>:
>
> > 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
>