On 6/23/19, 11:51 AM, "Scott Matheson" <[email protected]> wrote:

    Alex
           I fully understand and wish you all the best, but as a small 
developer i need to look at what is best for my development, i will keep a eye 
on Royal 
    
For sure, you have to do what's best for you.  Another good thing about Apache 
projects is that you can be one of the 3 PMC members who keeps Royale or Flex 
going.  The members of an Apache project are all volunteers from Apache's 
perspective.  I may be an employee of Adobe, but neither I nor any other member 
of Royale or Flex had to be "hired" by Apache.  Instead, you or Blake or anyone 
can contribute patches in your spare time, earn committer rights, learn how to 
cut and review releases and earn PMC membership.  Then you have permanent stake 
in the project.  All you need to cut a future release is two others to help you 
review it.  You can commit bug fixes or new features as long as they don't 
conflict with someone else's commits.  There is no product manager or business 
people deciding what goes in the next release or when the next release is.  Try 
getting a bug fix accepted and released by some other large-ish non-Apache 
projects.  It can be a challenge.

Sometimes, the best way to control the future is to contribute to it.

My 2 cents,
-Alex


    > On 23 Jun 2019, at 06:26, Alex Harui <[email protected]> wrote:
    > 
    > One of the reasons Flex and Royale are at Apache is so no corporation can 
pull the plug.  Apache specifically does not allow corporations to have any say 
in their projects.  If Adobe decides to stop paying me to work on Flex and/or 
Royale, if I can find some other way to get paid to do it, I can.
    > 
    > As long as there are 3 PMC members who can get it together to approve 
releases, the projects can live on at the ASF.  The community only has to be 
large enough to keep 3 PMC members motivated to participate on the mailing 
lists and process releases.
    > 
    > -Alex
    > 
    > On 6/22/19, 1:35 PM, "Scott" <[email protected]> wrote:
    > 
    >    So I am an old program  60 so I would say I have seen it all many time 
over, we have tried/looked at royal a number of times 
    > 
    >    As for royal, sorry it is late, we needed royal to be in full 
production 2 years ago, when we tried royal we kept finding new issues or 
missing elements, yes I know this is community code and I wish the project all 
the success 
    > 
    >    Now for the real issue, community unless there is a big user community 
then the key developed will do something else, just look at what happened to 
flex when adobe pull the plug, this could happened again and who is to say it 
will not, then royal will be  a dead end 
    > 
    >    Sorry that’s just my view, over 40 years of development I have seen 
this happen many time    
    > 
    >    Sent from my iPad
    > 
    >> On 22 Jun 2019, at 16:48, Piotr Zarzycki <[email protected]> 
wrote:
    >> 
    >> Hi Scott,
    >> 
    >> I'm curious why are thinking that Royale is a dead end?
    >> 
    >> Thanks,
    >> Piotr
    >> 
    >>> On Sat, Jun 22, 2019, 4:42 PM Scott <[email protected]> wrote:
    >>> 
    >>> AIR is a good option but you have the update  install problems, the
    >>> solutions are out there and air will do auto update etc ...
    >>> 
    >>> Google web frame work well, you install a browser, that looks a desk top
    >>> app but run the flex app like today, I have tried this and it work well 
the
    >>> WebKit stuff is not difficult
    >>> 
    >>> With the new commercial owners of air etc you should be able to come to 
a
    >>> deal on the desk top install of flash, I have talked to Andrew about 
this
    >>> approach
    >>> 
    >>> In our case we had the skills and due to timing we went for a UX port to
    >>> HTML5 but keeps all the as3 code, we converted to TrueType in less that 
1
    >>> day
    >>> 
    >>> Royal is an option but to hard and IMHO a dead end, in a few years your 
be
    >>> porting again
    >>> 
    >>> 
    >>> 
    >>> Sent from my iPhone
    >>> 
    >>>> On 22 Jun 2019, at 16:25, Blake McBride <[email protected]> wrote:
    >>>> 
    >>>> Greetings,
    >>>> 
    >>>> I have a large Flex(3.5)/Flash app that (obviously) runs under a 
browser.
    >>>> Since the Flash player is going away, I am wondering if I should 
consider
    >>>> AIR.  What are my other options?  What's easiest?
    >>>> 
    >>>> Thanks.
    >>>> 
    >>>> Blake McBride
    >>> 
    >>> 
    > 
    > 
    > 
    
    

Reply via email to