Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73FD6BE66 for ; Fri, 6 Jan 2012 07:38:16 +0000 (UTC) Received: (qmail 90679 invoked by uid 500); 6 Jan 2012 07:38:16 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 90463 invoked by uid 500); 6 Jan 2012 07:38:11 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 90412 invoked by uid 99); 6 Jan 2012 07:38:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 07:38:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sandy.pec@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-tul01m020-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 07:38:02 +0000 Received: by obcwn6 with SMTP id wn6so1620743obc.6 for ; Thu, 05 Jan 2012 23:37:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=V0Yxgsoh3Gpf+sCMqZhxcSlHNXyxH1167qrMwQdkNYQ=; b=a7GP2TMaNpAx3IsLvU/s6lCwbjMJHNLm3+f3uGJN/kQxFljoAaF97yVgRLudgvLSvN 5ZqT8uW73s9R5m+NpRtN7htqjOxkplmYJWkXbujn0u3tKabuVl9O/8Ojrd5wXBoDXNsL CD3e8QMgVTGSJH3y2h2+S2ZgPqUSZzgpyZ7gw= Received: by 10.182.76.134 with SMTP id k6mr4048925obw.10.1325835461651; Thu, 05 Jan 2012 23:37:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.12.132 with HTTP; Thu, 5 Jan 2012 23:37:20 -0800 (PST) In-Reply-To: References: From: Sandeep Gupta Date: Fri, 6 Jan 2012 13:07:20 +0530 Message-ID: Subject: Re: On splitting communities and non-code committers (was: Apache Flex community website) To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d044787a5b8eddb04b5d71fe5 --f46d044787a5b8eddb04b5d71fe5 Content-Type: text/plain; charset=UTF-8 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 wrote: > Hi Brent, > > On Fri, Jan 6, 2012 at 12:56 AM, Brent Arnold > 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 > --f46d044787a5b8eddb04b5d71fe5--