Also on the topic of releases, I think this will be a complex topic in our case due to the additional dimension of "version of the subject of the training". If for example we release a version 0.1 of the Kafka training, does this have a 1:1 relationship with Kafka versions - meaning 0.1 covers Kafka 2.0? This would make it tougher to backport generic changes like rewording use cases or something similar that are valid for all Kafka versions.
A follow up question would be whether a release covers just one specific target version, or if we recreate "older versions" as well, as these may have been affected by generic changes. I am in favor of having all material within one repo, as one of the main goals of the project was to enable creating custom agendas by picking and matching sections from the available material. This will be facilitated by having it all in the same place. One potential exception could be if we create any tooling around this to "compile" material. I think it might make sense to keep source for such a project in its own repository. Potentially this tooling might be useable for people who use it to create and manage their own content, so having it as a separate project would make that much easier. Best regards, Sönke Am So., 24. Feb. 2019, 01:44 hat Lars Francke <lars.fran...@gmail.com> geschrieben: > On Sat, Feb 23, 2019 at 9:57 PM Christofer Dutz <christofer.d...@c-ware.de > > > wrote: > > > Regarding "Releases" ... > > > > Thinking of having multiple slide decks and trainings in one git repo > > sounds problematic. In contrast to svn git doesn't support releasing a > > subdirectory. It would require us to have all trimmings in areleasable > > state at the same time. > > > > I agree that this is a bit weird but Hive for example does release > subprojects (storage-api) from their main git repository. They set a tag > but only release the part that they mean to release as a source archive. > > > > We could use branches for each training/presentation and release them bcz > > merging to develop and then regularly officially release the entire > package. > > > > I'm against anything that deviates from what most people are used to and > (I'm making assumptions) most people expect a master branch/trunk and won't > necessarily look into other branches. So I'm very much in favor of either > one big content-repo or multiple smaller ones. I'm leaning towards one big > monorepo which makes it easier to mix & match / compose things from smaller > parts. > > So would opt for not really doing typical releases at all, or to create > > tons of git repos for each training and do ordinary releases for these > > (would prefer the later option) > > > > Yeah, I agree on the former one but I'm not sure how this would work "rule > wise". > > Lars > > > > > > Chris > > > > Outlook f?r Android<https://aka.ms/ghei36> herunterladen > > > > ________________________________ > > From: Furkan KAMACI <furkankam...@gmail.com> > > Sent: Saturday, February 23, 2019 9:24:59 PM > > To: dev@training.apache.org > > Subject: Re: Open questions // Misc stuff > > > > Hi, > > > > Thanks for such an e-mail Lars! > > > > As far as I see, you have created different e-mail threads for some of > the > > listed topics at your e-mail. Since there is not a dedicated discussion > for > > it, I want to mention that we can send daily/weekly Slack digest into > > e-mail list as like Apache Pulsar project does in order to archive such > > information via mail-list. > > > > Kind Regards, > > Furkan KAMACI > > > > On Sat, Feb 23, 2019 at 9:45 PM Sharan Foga <sha...@apache.org> wrote: > > > > > Hi Lars > > > > > > This isn't noise :-) this is enthusiasm and it's great. It's all about > > > finding out where we want to go, what we want to do and how to do it, > > ..... > > > all of that takes discussion. > > > > > > Thanks > > > Sharan > > > > > > On 2019/02/22 23:14:41, Lars Francke <lars.fran...@gmail.com> wrote: > > > > I think I'm done for the day. > > > > > > > > Sorry for all the noise. > > > > > > > > These are just meant as discussion starters but if you feel that I go > > off > > > > in an entirely different direction than you thought, please don't > > > hesitate > > > > to let me know. > > > > We've obviously had an idea in mind when we proposed this project but > > > that > > > > doesn't mean that's the best way to go about it. > > > > > > > > And especially about all the Apache rules and politics I still get a > > > bunch > > > > to learn. So if I say something that sounds wrong to you then...it > > > probably > > > > is ;-) > > > > > > > > On Fri, Feb 22, 2019 at 11:01 PM Lars Francke < > lars.fran...@gmail.com> > > > > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > I've got a bunch of open questions that we could/should discuss. I > > > think > > > > > it makes sense to have separate threads for each but I wanted to > > start > > > a > > > > > "global" one first. This is lots of dull stuff to get sorted out > I'm > > > > > afraid. Existing projects usually have it a bit easier because they > > > already > > > > > come with a website or issue tracker etc. > > > > > > > > > > I'll start new threads for some of these topics: > > > > > > > > > > - Name search: I believe we need to start a PODLINGNAMESEARCH to > see > > > > > whether "Training" is a suitable name(e.g. [1]) > > > > > > > > > > - Jira: Do we want to use Jira? Might sound a bit premature as we > > don't > > > > > have any "product" yet but I'm sure we will and I believe it makes > > > sense to > > > > > have it > > > > > > > > > > - Confluence: Do we need a Wiki? Not sure yet... > > > > > > > > > > - Bylaws: Some/most/all (?) projects have bylaws, rules governing > how > > > they > > > > > work[2] > > > > > > > > > > - Git/Github usage > > > > > > > > > > - Releases: This is a bit more concrete already. What will > > constitute a > > > > > release? Assuming we produce a slidepack (in whichever format), > does > > it > > > > > even need releases? Is each content update not a release on its own > > > etc.? > > > > > > > > > > - Legal/Trademark: It'd be good to discuss with Legal/Trademark > folks > > > so > > > > > we can give guidance on how companies (ours included) can refer to > > > these > > > > > trainings in their material (e.g. "OpenCore Hadoop Training based > on > > > Apache > > > > > Training (incubating) - Hadoop" or something like that > > > > > > > > > > - Website: We need a website.... > > > > > > > > > > - Twitter: apachetraining is already taken but I've registered > > > > > apache_training (not done anything yet) > > > > > > > > > > - Slack: We have a #training channel in the-asf Slack. For those > new > > to > > > > > the ASF you can register at https://the-asf.slack.com/ with your @ > > > > > apache.org address > > > > > > > > > > - Report: We need to prepare a report for the board/Incubator PMC > > every > > > > > month for three months and then every quarter after that, I've > never > > > done > > > > > that but we have people in here with lots of experience so I hope > it > > > won't > > > > > be a problem :) > > > > > > > > > > And then there's the more interesting bits: > > > > > > > > > > - What content are you interested in producing? > > > > > - Which "formats"? (e.g. PowerPoint, RevealJS, Videos etc.) > > > > > - > > > > > > > > > > I'm looking forward to this! > > > > > > > > > > Cheers, > > > > > Lars > > > > > > > > > > > > > > > [1] <https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-27> > > > > > [2] e.g. <https://cwiki.apache.org/confluence/display/Hive/Bylaws > >, > > < > > > > > https://gump.apache.org/bylaws.html> > > > > > > > > > > > > > > > > > > > >
