Hi Carlos and Olaf, To clarify: the offer extends to everyone: Alex, Carlos, everyone here.
Everyone can submit bids. The group will vote on who to pay. I have no idea if this will work to inspire / motivate / organize, but it is worth a shot. Everyone's time is valuable, and balancing unpaid work on open source projects with client driven (paid) work is naturally a challenge. The idea is to allow financially for more focus to be on getting Royale 1.0 completed within a month. People can submit bids from $1.00 to $2,500.00. As a group we can choose multiple bids or a single bid. We will do whatever the group votes on with the budget I presented. The Moonshine-IDE.com team would do more if we could. From a code contribution perspective, we are working diligently on releases every 2 weeks or so. I understand the Apache way is similar to a potluck dinner, and everyone brings what they can. We are bringing an IDE focused on fast on-boarding for new users for Royale. The next release will hopefully include Carlos' suggestion to have a non-sandbox Mac version, in addition to the one available in the Mac App Store / iTunes. This will help power users who want to make use of existing software they have downloaded instead of using our "get your environment setup in one click" helper app. There will be other features too, especially related to GitHub and making it easy to bring example Royale projects into the IDE which are posted to GitHub. I understand more documentation was the vote from the Twitter pole. We agree and have been working on the tutorial aspect. Specifically: two weeks ago Piotr recruited a video tutorial specialist. He is going to be working on some of the goals with Piotr. However, he does not know Royale, so he will be learning it. This is actually great, because it will help Piotr to explain it to someone, who in turn can explain it in a video to everyone. Also, we have given to Piotr a portion of one of our production Flex applications which includes a login sequence and a basic contact details management (edit your e-mail and phone number type app) to be used in a tutorial potentially. We can never have enough tutorials, though! I'd love to see a lot more people working on tutorials. ASDocs and finalizing the API of key things like the Jewel Data Grid, along with the build process automation, are all critical items. I fully agree. My hope, now that the group has reached consensus on what 1.0 will take, is that we can get very specific milestones defined in GitHub: https://github.com/apache/royale-asjs/milestones For example, exactly what do we need to have fixed with the build process automation? Which specific sections of the documentation need to be improved? Having specific issues for these items will make it crystal clear what the group must complete before 1.0 is considered done. If the group decides we need a build specialist from outside the Royale community group, then we can try to get help on UpWork. We would rather keep the funding in the direct community since so many of you have worked so hard unpaid on this project for so long. Still, whatever the group decides is needed, lets figure out how to get it pipe lined into existence in the next 30 days. Thank you, Justin Hill ----- Message from Olaf Krueger <[email protected]> on Sun, 28 Apr 2019 23:20:03 -0700 (MST) ----- To: [email protected] Subject: Re: Let's bump Royale version to 1.0 -- submit your bid for assistance to the group by Friday May 3 Hi Justin, thanks for your amazing offer! > ...what Alex and Carlos want to see happen... Before others will do this I would just like to mention that no individuals make decisions here at Apache. It's always the community! ;-) However, I am curious about the feedback! Thanks, Olaf ----- Message from Carlos Rovira <[email protected]> on Mon, 29 Apr 2019 19:44:32 +0200 ----- To: [email protected] Subject: Re: Let's bump Royale version to 1.0 -- submit your bid for assistance to the group by Friday May 3 Hi Justin, great initiative, but some thoughts: 1.- As Olaf said, Alex or I are just two more devs, so we can say what should we do. That's the apache way! :), only work towards the goal and giving advice to make things happen. We decisions are community managed 2.- I think is very generous offer so people can contribute and earn some money and a great plan, Some things you should take into account for the rewarding plan: * We just get results of the poll about releasing published few minutes ago. Seems people wants to focus docs first and release second (from 61 votes). * In the other hand, I see Alex is still fighting with the release process. He stated that probably this week he will have the process ready to be tested by someone. If he get to that point that will be awesome, and hope others could be the first one in try to "push the button". If that works ok, we'll have a 0.9.6 release (I think the one by Alex), and then a 0.9.7 (by that new release manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay 1.0. For me release should happen at least from month to month. have sense? Just my my thoughts, but hope other want to share here what they can do and work to earn some money too! :)
