training-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig L Russell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TRAINING-5) Donation: Github challenges
Date Thu, 02 May 2019 18:01:00 GMT

    [ https://issues.apache.org/jira/browse/TRAINING-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831828#comment-16831828
] 

Craig L Russell commented on TRAINING-5:
----------------------------------------

I think that this kind of material, even if not expected, is in line with the goals of the
project. 

I guess we need to figure out how to rationalize the content here. I don't see distributing
.svg content as source material.

Third-party contributions need to be licensed to Apache so that Apache can in turn license
the content under the ALv2 just like code. This implies that we need SGA or CCLA covering
the contribution. [To me, keeping the original license for these kinds of things doesn't make
sense.]

It looks like the Octocat image is just fine as it refers to specifically the GitHub service.
Even without explicit permission, one can argue that this is nominal usage.

> Donation: Github challenges
> ---------------------------
>
>                 Key: TRAINING-5
>                 URL: https://issues.apache.org/jira/browse/TRAINING-5
>             Project: Apache Training
>          Issue Type: New Feature
>            Reporter: Isabel Drost-Fromm
>            Priority: Major
>         Attachments: 01_workflow.svg
>
>
> For context - this is following Lars' idea there: [https://lists.apache.org/thread.html/66636f8402426143a81b5bf5070a5b6957d2b5e63284f9ee06dabc82@%3Cdev.training.apache.org%3E]
to simply open a Jira issue for to-be-donated-content. I'm happy to have the process created,
refined and refactored while we go through it. I think it makes sense to do so with a guinea
pig to try things out, happy to be that guinea pig myself.
> Actual donation context: At my dayjob we are currently in the process of lifting company
knowledge about development processes with Git and GitHub. As for several projects Inner Source
best practices were adopted ([http://innersourcecommons.org)|http://innersourcecommons.org)/]
we aren't that far from the Apache Way internally.
> One way we are currently trying is to raise awareness of the various Git/Github features
through challenges/ riddles posted close to the coffee machine.
> Essentially those challenges are simply svg files that you can print and fill in. As
such I think they might make for a good sandbox to develop our content donation processes
in a test first way.
> Currently all challenges are employer-branded. Happy to drop that/ have that white-labeled.
> Kudos to [https://davidrehman.de/] for helping me out with his design skills - he helped
arrange the sheets in a way that looked much less clumsy than my own first try and still kept
space for a Monalisa Octocat.
> Caveat: Graph was inspired by Gitlab's Git cheat-sheet.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message