flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Kwiatkowski <nicho...@spoon.as>
Subject Re: Proposal: Code Example / Application Development Procedure (was: Re: Non-core code, contrib and samples (was: Goal for Flex: Strengthening large-scale Flex applications...))
Date Thu, 19 Jan 2012 22:11:27 GMT
I think where the contrib discussion ended was when people wanted to commit
code that wasn't theirs (frameworks).  From what I remember, the discussion
switched over to having a wiki post with links to existing frameworks, and
not putting them in the contrib trunk.

Code samples using a framework is ok, but not just the framework itself.


On Thu, Jan 19, 2012 at 5:07 PM, Peter Elst <peter.elst@gmail.com> wrote:

> > The flex-dev list should be responsible for building
> > the "car parts" (Flex SDK). But they should not take
> > care which type of "car" (Flex app) we build, and,
> > how we'd drive that thing.
> >
> > The flex-users list should take care which type of "car"
> > (Flex app) we build, and, how we'd drive that thing.
> My personal take on this is not to turn the flex-user list into a
> discussion back channel, but something for users of Apache Flex releases to
> ask questions about specific issues related to those releases - i.e. users
> of software
> If your more involved in the development and feel the urge to discuss best
> practices you can talk to fellow developers active in the project rather
> than end users on the flex-dev list.
> The idea about a contrib / samples area sounds perfect IMHO. There would be
> actual code people can delve into rather than a back and forth on personal
> coding style preferences and architectural choices.
> - Peter

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