Note that we can and have given out Apache Flex wiki edit access to non-committers.
If the plan is to move this content to Apache someday, it is prudent to make sure contributors have agreed to that before contributing. Having this work contributed directly to the Apache Flex wiki implies that agreement. So, I think folks have to decide whether there is some logistical or technical advantage to having this content created outside of Apache on a different wiki technology or not. It is important that good doc exists within the project. I think I've seen projects get in trouble for pointing folks outside of Apache for the "recommended" doc. But that does not mean that other folks cannot create better content outside of Apache and make money writing books and other learning content. My 2 cents, -Alex On 8/13/17, 12:15 PM, "Olaf Krueger" <p...@olafkrueger.net> wrote: > >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: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FFlexJS-Docs-Started-with-some-docs-u >sing-a-github-repo-tp63786p63849.html&data=02%7C01%7C%7Ce00c1eb5621a40a123 >7908d4e27fe696%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63638248633420 >9429&sdata=HFsLJjHR94EnZa%2FqKkT%2FJ6bYgh2PM847puWcjQjkLy4%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
