So … might be a juicy topic for some feedback here on the list (Atlas list preferred, but an it harm none, do as thou wilt) or at the conference.Add a clause to the Trainer's agreement (is there a Coach's agreement too?) that says what is allowed under a waiver. We would expect that a material violation of those guidelines would but one's CST/CSC status in jeopardy.Allow such materials to be used as part of Scrum-related commercial endeavors such as courses and coaching gigs.Require submission of all such materials to the Scrum Alliance for their (potential) review. Applicant agrees to keep this submitted material up to date (so you can't submit something good and then convert it to something evil). Not that anyone would.
--
You are in this forum as a guest. Please govern yourself accordingly.
---
You received this message because you are subscribed to the Google Groups "AgileAtlas" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agileatlas+...@googlegroups.com.
Visit this group at http://groups.google.com/group/agileatlas?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
I see two ways we could to this. Either we print out the German pdf (Germans seem to like German course material), and hand them out separately. However, then we would still have so much material floating around in class, that the second option would help more, I think: Include the text from the Scrum Core into the handbook together with that other stuff I mentioned before. The latter seems to conflict with the ND part of the license, I think.
All,
Carol copied for info as this relates to rights to Scrum Alliance material.
Atlas material is currently CC BY-NC-ND. Non-commercial, no derived works. That seems mostly reasonable. We can of course offer waivers, but in general I'd think the Scrum Alliance would want to protect this material.
However, via Markus G�rtner, we think about things like these:
- Materials to be handed out to a class, or as part of a coaching effort. If these activities were done for money, would that violate the NC?
- Take the Core page, and, using that text, interpolate examples, which some people want. Does that violate ND?
We might want to talk about this during the Retreat or separately. Chet and I had this idea:
Add a clause to the Trainer's agreement (is there a Coach's agreement too?) that says what is allowed under a waiver. We would expect that a material violation of those guidelines would but one's CST/CSC status in jeopardy.
Allow such materials to be used as part of Scrum-related commercial endeavors such as courses and coaching gigs.
Require submission of all such materials to the Scrum Alliance for their (potential) review. Applicant agrees to keep this submitted material up to date (so you can't submit something good and then convert it to something evil). Not that anyone would.
So � might be a juicy topic for some feedback here on the list (Atlas list preferred, but an it harm none, do as thou wilt) or at the conference.
Regards,
Ron Jeffries
I try to Zen through it and keep my voice very mellow and low.Inside I am screaming and have a machine gun.Yin and Yang I figure.
--� -- Tom Jeffries
You received this message because you are subscribed to the Google Groups "Scrum Training and Coaching Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ScrumTCC+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
�
�
I would quite happily settle for attribution. Derivative works are fine by me and I really can't see a problem with commercial gain.
If that works for the other authors we're good.
Cheers
Mark
work are free to make other agreements with selected users. Assuming the Scrum Alliance is the owner of the work, the Alliance could authorize exceptions to the trainers.
Having said that, I am not sure that the NC-ND is the most appropriate. We want to transform the world of work, so the distribution and integration of this core document should be easy, not hard...
I would quite happily settle for attribution. Derivative works are fine by me and I really can't see a problem with commercial gain.
If that works for the other authors we're good.