Hi Andrew, for me cwiki and other flex things was the "old way". In Royale we use GitHub tools. So the Github wiki is like the Apache cwiki Don't need to have the old tools, we even talked about that long time ago and decided to go Github way since is what all people are using today.
One thing you can do is migrate things from FlexJS already not migrated to Royale Docs, for example this page (to take one): https://cwiki.apache.org/confluence/display/FLEX/FlexJS+Layout That content should have an entry in Royale Docs in Features part (Royale Layouts). And other here should review if contents need some updating But as a starting point I think is ok, changing "FlexJS" for ·"Royale", and things like that. Thanks Carlos El mié., 11 dic. 2019 a las 18:49, Andrew Wetmore (<[email protected]>) escribió: > Hi: > > I gather from Infra that Royale does not have its own cwiki (and not its > own Confluence??) account. The person I was speaking with suggested we > should have our own, rather than piggybacking on the Flex cwiki, not least > because committers like me (a committer for Royale but not for Flex) can > run into problems, as when I could not edit the board report in Confluence > today. > > How do we get this organized? I would be happy to help migrate from the > Flex cwiki everything that is there that also or primarily applies to > Royale. > > Andrew > > -- > Andrew Wetmore > > http://cottage14.blogspot.com/ > -- Carlos Rovira http://about.me/carlosrovira
