Hi, > I used google docs because personally for me it is easy to work with. But I > can change the format to anything the community agrees on.
I really don’t know the right format but some plain text format that could be exported to google docs, power point, keynote, pdf etc etc would seem to be best way to go. I have no idea what that might be right now. Chris has done some work in this area and used AsciiDoc right? Perhaps this might help? [2] > I created the content based on the information provided in various parts of > apache.org and gave the references where appropriate. Is there anything i > need to do? In code it generally obvious who created or worked on something as you can see version control or it has a header with a copyright notice. So this would need to be recorded somewhere, probably LICENSE? > I really wasn't sure which license to use, as I thought Apache and MIT > licenses refer mostly to the code. Yep that the issue. but you can still use ALv2 for things that are not code or you could use CC0 if you want to keep it as a creative commons license. > Diagrams used were designed from scratch by Amardip Raol and I have his > permission to use. So there was more than one creator :-) Also needs to be mentioned in LICENSE? > The theme I believe is good too. So where did it come from and who created that and what license is it under? > I have originally used couple from flaticon, but changed them to google > material design icons <https://github.com/google/material-design-icons> that > have Apache license. Should that be good? Yep another addition to LICENSE. Now I’ve suggested add ALv2 content to license (which is optional) but given it’s not obvious that this content is under ALv2 that’s been the suggested way of dealing with it in the past. > happy to relicense it. I used CC-BY because I believed it was the most > permissive out of all CC licenses Actually I think CC0 [1] is. [1] > +1. Also +1 on Mirko's points, especially on: > - provide a list of compatible licenses > - describe the "process of relicensing" > - describe a "cleanup process" to reduce "incompatible content" All good ideas. Thanks, Justin 1. https://creativecommons.org/share-your-work/public-domain/cc0/ 2. https://github.com/Mogztter/asciidoc-googledocs-addon
