Agree with latest comments. I think we should work in docs and ease the start of new users to target 1.0 And in the process fix some few things (i.e: don't want to reach 1.0 with Jewel Table in its current state and API)
What do you think? If you all agree could you think on how to contribute to that effort? Can we have as a near goal to bring 1.0 planing ourselves to donate some hours to Apache Royale to make this happen? If some of us help in the current state I think we can get to it sooner. Thanks El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<[email protected]>) escribió: > I am completely agree with Olaf: start using a new platform where the > documentation is not complete, clean and updated it is a really bad > thing...and it would be a potential reason to increase the difficulty to > adopt the platform... > > Angelo > > El vie., 26 abr. 2019 8:54, Olaf Krueger <[email protected]> escribió: > > > Hi, > > > > Basically, I think it's important to provide a great developer > experience. > > IMO, that's more important than trying to implement missing features. > > > > One thing to achieve this is documentation of course. > > Thanks to all of you there already exist a lot of docs, but it feels a > bit > > messy because they are hosted at different places, e.g.: > > > > - royale-docs repo > > - royale-asjs wiki > > - royale-asjs Readme > > - https://royale.apache.org > > - ...? > > > > As a user, it's hard to get an overview of what is available... and > where. > > Maybe it's a good idea to consolidate the docs before releasing 1.0. > > > > Just my 2 cents, > > Olaf > > > > > > > > > > > > > > > > -- > > Sent from: http://apache-royale-development.20373.n8.nabble.com/ > > > -- Carlos Rovira http://about.me/carlosrovira
