Thanks all for re-starting the conversation! In terms of "how Apache
projects work"; it's really up to each project to decide how to roadmap
or do planning. So whoever can attract energy gets to decide on the way
you do it!
But I think the real issue is the larger split between likely
contributors here:
1- People interested in building whatever technology / deployment
methods that enable some sort of neat new way to deliver training(s). I
sense we have a few of those people; however I am not one of them.
2- People interested in writing slide decks in a solid framework. This
is what I'd be interested in. I waffle between Keynote and using
remark.js for my decks. But I'd love an ASF-hosted solution for
managing various slide decks in an organized way, where it's easy to use
source control on the source content directly.
3- People interested in training standards; that is, making it easy for
a training class to implement grading or other standards/academic
features. Long-term, this would be a nice-to-have, but the PPMC needs
to get the rest of the project moving before doing this work IMO.
So the big issue is find enough people to work on 1 (tooling) so that
the people interested in 2 (content) can simply show up, read a simple
how-to of "checkin this markdown file here and that config file there"
and actually work on training modules.
Does that make sense? I love the idea of this project, but personally
won't have energy to participate if it requires me to use the `mvn`
command. My technical energy is already overbooked; I'm looking for a
place to just work on content, and I bet there are a few other folks
like that too.
--
- Shane
ASF Member
The Apache Software Foundation
