Hey Apache-Training Team, today I joined the mailing list and during my long flights I have found time to think about the project.
Besides the discussion /creation of project internal processes we must have in mind, that corprate training is "Game about real money". My motivation is to help to make training in OS Software easier to deliver - this may spread the word about OSS too. Full curriculum development can be considered as a separate task. I think, Apache Software projects can help with prebuild training components. Trainers take such modules and focus on customer demand and a good path to teach or work and grow together. Taking away the technical burdon from a trainer can be so benefitial - trainers still need to be experts, but I don't want them to fix Software issues. This is a different topic. Is this understanding in line with the project? I propose not to limit the project to any tooling. ASCII doc is cool, Latex is widely used in Academia - and this is a huge resources to get contributors for this fresh flavored Apache Project. If we Pickup people on their place it will be much easier. I think this project will be a bit different - also less software focused geeks can join and bring energy in. I am convinced that OS is way more than Software and licenses - it drives Interactions, sharing and future. Here are some thoughts regarding contents: - collection of OS tutorials embedded/related to Apache Projects - collection of free Cheat-Sheets - Form to capture Life questions of Trainers --> learn about real demand - Repository with answers to such questions (incl. search capability) # I created a tool for this some time ago. Would love to refresh and contribute it If demand exists and If it is in line with project scope. The tool I mean makes sense especially If we plan to grow a trainer community. So, thats all for today. Cheers, and best wishes, Mirko Am Sa., 23. Feb. 2019, 13:50 hat Sharan Foga <[email protected]> geschrieben: > Hi > > I'd prefer Jira too especially if it's going to be easier for anyone to > contribute. > > Thanks > Sharan > > On 2019/02/23 04:21:44, Kenneth Knowles <[email protected]> wrote: > > > > One thing I've encountered on GitHub is that you can only assign a PR > > > > review to a member of the `apache` organization. Is that also true > for > > > > issues? > > > > > > Most likely but I don’t know. Because of GitHib's poor granularity of > it's > > > permission system INFRA have locked it down and a lot of things > projects > > > can do in the wild can’t be done at Apache. > > > > > > > If this is true, I prefer Jira so non-committers can take issues. What do > > you do on echarts? Do you know what they do on royale-asjs? > > > > Kenn > > >
