flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandeep Gupta <sandy....@gmail.com>
Subject Re: On splitting communities and non-code committers (was: Apache Flex community website)
Date Fri, 06 Jan 2012 07:37:20 GMT
Hi Brent,

You mentioned that we may commit by evangelizing, writing docs and
tutorials etc... which I kind of agree with.

However, being a non-commiter I do not have access to Wiki to write - I do
not have access to code to write method documentation and else. How do I
contribute in such ways - Am I missing something here?

Is there some other way to submit our contributions to Apache when we are
not amongst one of a commiter - in the hope that one day we will be :)

Apologies if this has been answered before or is put up at some place as a
doc. My ignorance counts for now!

Keep Walking,
~ Sandeep

On Fri, Jan 6, 2012 at 12:21 PM, Bertrand Delacretaz <bdelacretaz@apache.org
> wrote:

> Hi Brent,
> On Fri, Jan 6, 2012 at 12:56 AM, Brent Arnold <brent@brentarnold.com>
> wrote:
> > ...As a member of the Flex community I wanted to contribute in some way,
> and
> > since I'm not an initial committer or anything, I figured I could at
> least
> > do something like setup and host a website --> apacheflex.org.
> >
> > I realize that the core of the project will remain with apache.org, but
> I
> > felt that we could use a resource for the non-technical aspects of the
> > project, i.e. a wiki, forums...
> IMO, based on my experience with many Apache projects, it would be
> much better if this could happen *within* Apache Flex, as opposed to
> potentially creating a split community.
> Many Apache projects have some committers who do not commit a single
> line of code, but are still "committed" to the project by evangelizing
> it, writing docs and tutorials, acting as user's advocates etc.
> So, It is totally possible for people involved in community activities
> but not in code to become committers, and managing a community website
> is IMO totally within scope of Apache Flex.
> In summary, if your community-related contributions could happen
> *within* Apache Flex as opposed to *besides* it I think that would be
> much more powerful. Contrary to what some might think, an Apache
> project has a lot of freedom in how it organizes itself, and this
> podling's mentors [1] are here to help make things happen as far as
> the foundation is concerned, once a project's needs are clearly
> identified.
> -Bertrand
> [1] http://incubator.apache.org/flex/team.html

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