Hi Carlos, so far we have one binding vote and one non-binding vote ... I started a vote and I would feel uncomfortable with not having at least 3 binding votes in favor of the new repo.
Chris Am 22.09.20, 12:09 schrieb "Carlos Rovira" <[email protected]>: Great Chris, I saw the flex thread, and I think it's ok we go ahead. So please let's go and request the repo :) thanks! El mar., 22 sept. 2020 a las 11:43, Christofer Dutz (< [email protected]>) escribió: > So I took it to the Flex list and heard some in favor mails, but not a > single negative one .... so I think it would be safe to continue. > > Chris > > > > > Am 16.09.20, 20:23 schrieb "Christofer Dutz" <[email protected]>: > > Hi Piotr, > > sure I can ... will do right away. > > Chris > > Am 16.09.20, 20:08 schrieb "Piotr Zarzycki" <[email protected] > >: > > Chris, > > Could you please open [Discuss] thread on Flex list apart of VOTE, > maybe > someone will have some thoughts on that. > > Thanks, > Piotr > > śr., 16 wrz 2020 o 17:06 Carlos Rovira <[email protected]> > napisał(a): > > > Hi Chris > > I'm ok with that. > > Could you start the vote on Flex list ? > > I can do equally here in Royale in parallel and reference yours > > > > > > El mié., 16 sept. 2020 a las 16:31, Christofer Dutz (< > > [email protected]>) escribió: > > > > > Hi Carlos, > > > > > > I think it's not required for a new repo to be an act of the > PMC, but I > > > think it would be nice to do it. > > > > > > Also I think it would be good to vote on the willingness to > fork BlazeDS > > > and a vote on the Flex list that the PMC is ok with this > > > (I know in this particular case it's sort of silly, but this > would be the > > > way I would personally do it) > > > > > > But I'd say it's up to the Royale PMC to decide how you want > to do it. > > > > > > Chris > > > > > > > > > > > > > > > Am 16.09.20, 16:20 schrieb "Carlos Rovira" < > [email protected]>: > > > > > > Hi Chris, > > > it seems people are ok with doing this. > > > If we need to do some voting, we could do it. > > > If not we could request the "royaleds" repo. > > > Since you have more knowledge on this flow, better you > handle it so > > we > > > do > > > in the apache way. > > > > > > thanks! > > > > > > El mar., 15 sept. 2020 a las 9:23, Piotr Zarzycki (< > > > [email protected]>) escribió: > > > > > > > Definitely Chris! Enjoy your meal ! ;) > > > > > > > > wt., 15 wrz 2020 o 09:17 Christofer Dutz < > > [email protected]> > > > > napisał(a): > > > > > > > > > Lol ... good catch .. stupid phone __ > > > > > > > > > > Note to myself: Don't write emails on your phone > during breakfast > > > ... > > > > > > > > > > That should have been "RoyaleDS" __ > > > > > > > > > > Chris > > > > > > > > > > Am 15.09.20, 08:59 schrieb "Piotr Zarzycki" < > > > [email protected] > > > > >: > > > > > > > > > > Chris, > > > > > > > > > > Why Royales ? Do you suggest to have more than one > project > > > there ? > > > > > > > > > > wt., 15 wrz 2020 o 08:52 Christofer Dutz < > > > [email protected]> > > > > > napisał(a): > > > > > > > > > > > Hi all, > > > > > > > > > > > > Well if we want to do this, I would suggest a > new git > > > repository. > > > > > For that > > > > > > we should pick a name. I would suggest Royales. > But that's > > > > something > > > > > that > > > > > > has to be an act of the PMC (I think). > > > > > > > > > > > > Chris > > > > > > > > > > > > ________________________________ > > > > > > Von: Greg Dove <[email protected]> > > > > > > Gesendet: Montag, 14. September 2020 22:18 > > > > > > An: Apache Royale Development < > [email protected]> > > > > > > Betreff: Re: [DISCUSS] fork/move Apache Flex > BlazeDS to > > > Royale? > > > > > > > > > > > > I am not really familiar with any detail of > BlazeDS, but > > > this does > > > > > sound > > > > > > like a great idea to me, Chris. > > > > > > If you can 'modernize' a version of BlazeDS that > is > > > increasingly > > > > more > > > > > > suitable for Royale, sounds like a really good > fit for your > > > > > knowledge and > > > > > > experience. I'm not sure we have anyone else who > > would/could > > > do > > > > that. > > > > > > I say 'go for it'! > > > > > > +1 (if it's needed). > > > > > > > > > > > > > > > > > > On Mon, Sep 14, 2020 at 9:04 PM Raúl Núñez < > > > [email protected]> > > > > > wrote: > > > > > > > > > > > > > Hi: > > > > > > > > > > > > > > I totally agree with this update. So +1 :) :) > > > > > > > > > > > > > > Regards!! > > > > > > > > > > > > > > El lun., 14 sept. 2020 a las 10:58, Carlos > Rovira (< > > > > > > > [email protected]>) > > > > > > > escribió: > > > > > > > > > > > > > > > Hi Chris, > > > > > > > > > > > > > > > > I'm all for it. We really need BladeDS in > Royale, so we > > > should > > > > > keep it > > > > > > > with > > > > > > > > the flow and also improve it for the actual > needs. > > > Spring Flex > > > > > > > integration > > > > > > > > is now dead, so bringing that too to keep it > alive > > would > > > be > > > > very > > > > > good. > > > > > > > > > > > > > > > > So it's ok for me to leave BladeDS in Flex > in its > > > current name > > > > > and > > > > > > > > versioning (and if there's any need in flex > in > > > forthcoming > > > > years > > > > > let > > > > > > > others > > > > > > > > do the patches they could need), and bring > BlazeDS in > > its > > > > > current state > > > > > > > as > > > > > > > > "RoyaleDS" here and start releasing new > improvements > > for > > > Royale > > > > > with > > > > > > the > > > > > > > > new name. > > > > > > > > > > > > > > > > I think that also will make Royale stronger > since we > > > already > > > > > support > > > > > > the > > > > > > > > main AMF implementation in this project. > > > > > > > > > > > > > > > > So +1 > > > > > > > > > > > > > > > > > > > > > > > > El lun., 14 sept. 2020 a las 10:44, > Christofer Dutz (< > > > > > > > > [email protected]>) escribió: > > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > currently I’m using Apache Flex BlazeDS as > backend > > for > > > my > > > > > Royale > > > > > > > > > applications. > > > > > > > > > > > > > > > > > > This has somewhat become a little old and > I do need > > to > > > do > > > > > quite some > > > > > > > > > tweaking to get it working with Royale and > especially > > > with > > > > new > > > > > > Spring, > > > > > > > > > Spring-Boot and Spring-Security. > > > > > > > > > So I guess doing some update of that and > re-releasing > > > does > > > > > sound > > > > > > like a > > > > > > > > > good idea. > > > > > > > > > > > > > > > > > > But I think it would be better to do a > clean cut and > > > optimize > > > > > it for > > > > > > > > usage > > > > > > > > > with Royale. > > > > > > > > > > > > > > > > > > I’d even like to call it something > “RoyaleDS” to make > > > the > > > > link > > > > > > Rolyale > > > > > > > + > > > > > > > > > RoyaleDS a little more obvious than the > old Flex + > > > BlazeDS > > > > > pair. > > > > > > > > > > > > > > > > > > What do you think? > > > > > > > > > > > > > > > > > > Right now the Flex project seems like > we’re keeping > > the > > > > lights > > > > > on in > > > > > > an > > > > > > > > > empty building and I doubt things will > improve soon. > > > Starting > > > > > to move > > > > > > > the > > > > > > > > > things we want to keep on maintaining to > Royale > > sounds > > > like a > > > > > good > > > > > > > thing > > > > > > > > to > > > > > > > > > to. > > > > > > > > > Perhaps even a stripped down version of the > > mavenizer. > > > > > > > > > > > > > > > > > > Chris > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Carlos Rovira > > > > > > > > http://about.me/carlosrovira > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Piotr Zarzycki > > > > > > > > > > > > > > > > > > -- > > > > > > > > Piotr Zarzycki > > > > > > > > > > > > > -- > > > Carlos Rovira > > > http://about.me/carlosrovira > > > > > > > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > -- > > Piotr Zarzycki > > > -- Carlos Rovira http://about.me/carlosrovira
