Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of carlos.rovira@gmail.com
 designates 209.85.161.175 as permitted sender)
MIME-Version: 1.0
Sender: carlos.rovira@gmail.com
In-Reply-To: <CC5808DF.1E03%pent@adobe.com>
References: 
 <CAMFKFRi7XQXk9Ko7V-YqAnJ6b1Xe1OF+VD7chN5bfWExgj3i3Q@mail.gmail.com>
	<CC5808DF.1E03%pent@adobe.com>
Date: Mon, 20 Aug 2012 22:07:44 +0200
Message-ID: 
 <CAMFKFRizVNGoCceqH2t1DHn30HKeeWR0rwS-zy9oZ6Cgq9whiA@mail.gmail.com>
Subject: Re: Apache Flex in Github
From: Carlos Rovira <carlos.rovira@codeoscopic.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf305b13ea19df3704c7b810e5

--20cf305b13ea19df3704c7b810e5
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable

Right! We are looking for people with completly freedom since this would
make make things move forward in the project due to remove barriers and
allow contributions flow.

The fear that at sometime apache flex official project will be cloacked by
a more successful fork will always be possible. Right now is possible
forking the fork at github and evolving it in a radikal new way!. But for
that reason apache flex would grow better in contributors and play the king
role in an efficient way. People will always look to the better, and if a
fork is better will grab it instead of the official project. So we should
move the project in the right way and get people statisfied to work with
the official fork in order to create critical mass and have a compact and
joined community.

For that reason today open source, sharing and all around this is all about
git, github and the things we are talking about here


2012/8/20 Peter Ent <pent@adobe.com>

> This seems like a great way to manage changes to Flex while giving people
> complete freedom to fiddle with it. The danger can come, at some point in
> the future, from git repositories that contain features not compatible
> with Apache Flex. I would think this could be handled by making sure
> Apache Flex is known to be the true version and if you are not a
> developer, just be aware that if you are taking Flex from some other git
> repository you do so at your own risk.
>
> In other words, if there come to be a bunch of 3rd party IDEs that use
> Apache Flex and you go and snag a copy of Flex from someone's personal gi=
t
> repository, you run the risk of that Flex SDK not working with your IDE.
> But I think those things just work themselves out; a vibrant developer
> community will probably keep such a thing in check.
>
> From what I've been reading about git, this fits perfectly well with how
> git works and should make everyone's life easier once it gets underway,
> plus it lets Apache Flex work the "Apache Way".
>
>
--=20
Carlos Rovira
Director de Tecnolog=EDa
M: +34 607 22 60 05
F:  +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Per=F3n, 32
Planta 10, Puertas P-Q
28020 Madrid

--20cf305b13ea19df3704c7b810e5--