I was thinking we could make those repos read only once Royale has a fork?
Did anyone have any other ideas, see any problems?
On 27 September 2017 17:16:43 BST, Alex Harui wrote:
>Hi Folks,
>
>Looks like the new Royale repos have been created, so I think we need
>to
>switch over to those repos
The new repos are available here:
https://github.com/apache/royale-compiler (was flex-falcon)
https://github.com/apache/royale-typedefs
https://github.com/apache/royale-asjs
https://github.com/apache/royale-tourjs
In addition, we will be building out our royale.apache.org website here:
https://g
The Royale PMC members ought to subscribe to Private right away. I'm not babble
dependent and will subscribe to all shortly.
Sent from my iPhone
> On Sep 27, 2017, at 9:37 AM, Alex Harui wrote:
>
> The mailing lists appear to be set up, but we may want to get Nabble
> hooked up to them before
The mailing lists appear to be set up, but we may want to get Nabble
hooked up to them before moving lots of conversations over there.
-Alex
On 9/27/17, 9:28 AM, "Erik de Bruin" wrote:
>How about the mailing lists?
>
>EdB
>
>
>
>On Wed, Sep 27, 2017 at 6:16 PM, Alex Harui
>wrote:
>
>> Hi Folks
How about the mailing lists?
EdB
On Wed, Sep 27, 2017 at 6:16 PM, Alex Harui
wrote:
> Hi Folks,
>
> Looks like the new Royale repos have been created, so I think we need to
> switch over to those repos and not make more commits to flex-asjs,
> flex-typedefs, and flex-falcon.
>
> Thanks,
> -Al
Hi Folks,
Looks like the new Royale repos have been created, so I think we need to
switch over to those repos and not make more commits to flex-asjs,
flex-typedefs, and flex-falcon.
Thanks,
-Alex
