Hi all, first of all, I'd say we are off to a great start with all this content that people are willing to donate. Thank you very very much to everybody!!
I agree with Mirko that a default process makes sense and at a first glance the proposed process and checklist items all look great! I just wanted to briefly point out, that the ASF also has a standardized way for IP donations [1] [2] that we might have to incorporate into our process. Most of the documentation refers to a "codebase" being brought in, so I am not 100% sure that this applies to our content, but my thinking is: it should. I noticed that license agreements and grants need to be mailed to secretary@apache, so potentially Craig can offer some additional insight into the actual process when we have determined if it is relevant to us. Logically it would probably go between items 4 and 5 on Mirko's proposed list. I have no idea how many contributions we will realistically have in-flight at any given time once we get off the ground, but in case this becomes a significant amount we might want to consider creating an extra issue type with a separate workflow for this in jira. That would allow us to track donations through the process stages. Best regards, Sönke [1] http://incubator.apache.org/ip-clearance/ [2] http://incubator.apache.org/ip-clearance/ip-clearance-template.html On Thu, Mar 21, 2019 at 6:41 AM Mirko Kämpf <[email protected]> wrote: > Hey everybody, > > I want to follow up on Justin's email with thoughts regarding "content > on-boarding". > > What do you think about a specific on-boarding workflow like this: > > (1) Content location (typically an URL) is provided (public git repo, > webserver, Slideshare, etc. ) > (2) Contributor fills out a content registration form, which contains > Justin's questions and others. > (3) Apache-Training community is informed via Email and verification of > content / licenses is done > (4) Apache-Training community votes for onboarding or rejects > (5.a) accepted content is stored in the Apache-Training content stage and > community is notified, JIRA-xyz: transform and index content > (5.b) rejected proposal is stored in the Apache-Training content stage and > submitters is notified > (6) content item is in state: accepted > (7) after JIRA-xyz has been processed, using the previously JIRA workflow, > the content is "ready for release" > > > > TBD: > - how to package multiple content items in one release > - finalize the onboarding checklist (proposal be Justin) > - provide a list of compatible licenses > - describe the "process of relicensing" > - describe a "cleanup process" to reduce "incompatible content" > > > > > *Initial set of question for checklist:*- Who created the content? > - In case of multiple authors: Did all give permission for this to be > licensed under it’s license? > - Some potential IP/license issues: > - Where did the following come from and how are they licensed? > - The content itself > - Slide theme, fonts and illustrations > - Icons used in the slides > - Are recordings of the slides being presented? > > > > Best wishes, > Mirko > > > > > > Am Do., 21. März 2019 um 02:24 Uhr schrieb Justin Mclean < > [email protected]>: > > > Hi, > > > > > I also have a slide deck on 'The Apache Way' > > > https://s.apache.org/apache-way-for-everyone > > > > Great content and would be good to have it here so it can be used and > > updated by all. > > > > For it to be used here I have some questions. > > - Is google docs the right format? > > - Who created the content? Did all give permission for this to be > licensed > > under it’s license? > > - Some potential IP/license issues. Where did the following come from > and > > how are they licensed? > > - The content itself (seems to be CC-BY) > > - Slide theme > > - Icons used in the slides > > - Do you have any recordings of the slides being presented? > > > > It’s seem to be currently licensed under: > > https://creativecommons.org/licenses/by/4.0/ > > > > Which probably means we cannot us it [1] unless it was re-licensed, even > > if it changed to CC-SA there are issues [2]. > > > > I’m more thinking out-loud here and perhaps some of the above could > > become a check list for incoming content? > > > > Thanks, > > Justin > > > > 1. https://apache.org/legal/resolved.html#cc-by > > 2. https://apache.org/legal/resolved.html#cc-sa > > > > -- > > Dr. rer. nat. Mirko Kämpf > Müchelner Str. 23 > 06259 Frankleben > -- Sönke Liebau Partner Tel. +49 179 7940878 OpenCore GmbH & Co. KG - Thomas-Mann-Straße 8 - 22880 Wedel - Germany
