royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlosrov...@apache.org>
Subject Re: Container change
Date Thu, 10 May 2018 09:56:31 GMT
Hi Piotr,

If you want that I move on from this project I can do that. And maybe that
will means that this project has something wrong or strange at its Core.
Since I'll be the fourth or five contributor that will move on from this
project due to discrepancies with some PMC members. So maybe those
contributors wasn't the problem.

What I see really discouraging is that Harbs will revert the change since
is breaking his app.

A true team will say "hey! something is wrong lets fix it", since is more
easy to fix from the actual point, than revert to that commit.

But you were clear with your proposal of me to fork Royale in other
project...Just let me know and I'll move on.



2018-05-10 10:49 GMT+02:00 Piotr Zarzycki <piotrzarzycki21@gmail.com>:

> +1.
>
> In my opinion it should be done in the following way.
> 1) Refactoring in separate branch
> 2) Announce on dev list
> 3) Wait until someone look into that - if it passed 48h gentle reminder. -
> The time in this project is rather longer in case of changes.
>
> Btw. I know couple of projects which forked Flex SDK and guys change it for
> the project purpose. If you really wanted to have it totally separated you
> can have your own SDK. - It's a pain, but you can move forward faster
> instead of waiting or discuss with others on something.
>
> I really wanted to use Jewel for the new project as part of
> Transpiledactionscript and this what is happening do not help. I'm not
> talking about code changes, but rather time spent on that after those
> changes.
>
> Piotr
>
> On Thu, May 10, 2018, 10:35 AM Harbs <harbs.lists@gmail.com> wrote:
>
> > Let me just say that I’m *very* frustrated right now.
> >
> > I’m busy chasing down all kinds of odd issues caused by a refactoring
> that
> > we didn’t agree on.
> >
> > I really don’t have the time to be doing so right now… :-(
> >
> > Carlos, you REALLY should have:
> > a) properly discussed this all *before* you made these changes.
> > b) done this on a feature branch.
> >
> > At this point, I’d like to just revert all the refactoring changes.
> >
> > Harbs
> >
> > > On May 10, 2018, at 9:08 AM, Piotr Zarzycki <piotrzarzycki21@gmail.com
> >
> > wrote:
> > >
> > > In that point I'm feeling that Even if couple of PMC members or
> > committers
> > > have some resistance, changes are being done no matter what.
> >
> >
>



-- 
Carlos Rovira
http://about.me/carlosrovira

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message