Olaf, I think you should do what you feel comfortable given that you are putting most of the work 😊
That said, if you plan to migrate it to the Apache Flex project at a future point, it will be easier if you add an Apache V2 license to your repo right away. Thanks, Om On Aug 13, 2017 12:17 PM, "Olaf Krueger" <p...@olafkrueger.net> wrote: >By GitHub pages you mean as part of Apache ? No. Github pages use Jekyll as static site generator under the hood and Jekyll supports Markdown to generate the pages. So the migration should not so much effort. At the end, each particular article is represented by its particular file then which could probably be tracked easier. I think the benefit of using GitHub is that anybody is able to contribute, even non-comitters. And that it's not so bad to have some more FlexJS resources on the web. However, it could still move to Apache at any time. Thanks, Olaf -- View this message in context: http://apache-flex- development.2333347.n4.nabble.com/FlexJS-Docs-Started-with- some-docs-using-a-github-repo-tp63786p63849.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
