Hi Oli, I'm not sure about non-technical training, because the initial target of the proposal was an introduction to open source projects (not limited by Apache). But your email triggered one more idea for me, what if we will prepare some training materials related to Java Concurrency. It is time-to-time needed in a complex (open and closed-source) projects, so why don't prepare a couple of examples to allow more people to know Java internals.
I agree about prototyping, and I'm going to create some stuff related to Apache Ignite. Unfortunately, the donation of existing content was not approved by the company, so I need now to create some stuff from scratch. As for the separation of content/build: there is a vote related to the contribution process. This process separate review steps for engine and content. Sincerely Dmitriy Pavlov вт, 2 апр. 2019 г. в 18:59, Kuebel, Oliver <[email protected]>: > Hi everyone > > > > my name is Oli and I would be happy if I could support you with your > project. > > Currently I do not have specific training documents or any other kind of > content, but what I could offer you are my ideas and sometimes even an > opinion ;) > > > > After an initial discussion with Sönke and a review of the previous mail > discussions, I have the following comments / suggestions: > > > > > > # Prototyping: > > At the moment the discussed topics are all still quite abstract and less > tangible. > > I think that it would be helpful to try out the discussed issues on a > living example. > > What do you think about a kind of prototyping area where you could try > things out and discuss about a more concrete object? In addition, a > visualized working status could possibly gather more contributors. > > > > > > # Separate sections for content and engine > > As far as I understood, there should be a kind of engine (Maven Build) in > the target vision, which generates presentations or training documents > based on Asciidoc and the input of some parameters. > > What about two different subprojects here - one for the engine and one for > the actual content? > > The advantage would be that you could make the Approval/Review processes > different. The one for the engine is stricter (e.g. review by a committer > is mandatory) while the content area is more informal (e.g. changes allowed > by anyone followed by lazy consensus). > > > > > > # Non-technical training documents: > > So far, most of the planned training courses deal with technical topics. > The focus is currently mostly on Apache projects and their environment. I > think that especially at the beginning the target group of the project will > be here. That's why this focus makes sense now. > > As far as I understood should the initial structure of content be based on > technical products (at least that is one option :) ) > > However, should we plan with other non-IT topics right at the beginning? > Perhaps there will be some training documents for planting tomatoes or > meteorology in future? Or should we start with the content we have and make > a restructuring of the content storage in the future? > > > > > > I'm looking forward to your feedback > > > > Best regards > > Oli > > >
