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 91F96B746 for ; Fri, 6 Jan 2012 08:34:39 +0000 (UTC) Received: (qmail 46981 invoked by uid 500); 6 Jan 2012 08:34:39 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 46788 invoked by uid 500); 6 Jan 2012 08:34:20 -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 46773 invoked by uid 99); 6 Jan 2012 08:34:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 08:34:11 +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 (nike.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 08:34:03 +0000 Received: by obcwn6 with SMTP id wn6so1662745obc.6 for ; Fri, 06 Jan 2012 00:33:42 -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=TiaM9j+a0oksWoYGu3SasZrGM9GGSAwtMvYxR+BNeIg=; b=ca9CDVsW1fomd5KAME8yJRzntx8NslVCzXcEe+hERLza3GwTwCrwNvGx79tKFJrsKu +EYiQXYhbNGf3rfqZwjEhqQbbPgQmxM5ncO/CEocwiY3fqxpdm/GDyHsDN3FsLah02CW kvYnXomkwgbuRloyq1guR0i7ToJ+iows4q57o= Received: by 10.182.78.165 with SMTP id c5mr4128554obx.60.1325838822246; Fri, 06 Jan 2012 00:33:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.12.132 with HTTP; Fri, 6 Jan 2012 00:33:21 -0800 (PST) In-Reply-To: References: From: Sandeep Gupta Date: Fri, 6 Jan 2012 14:03:21 +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=f46d0444ef1f078a0c04b5d7e84e X-Virus-Checked: Checked by ClamAV on apache.org --f46d0444ef1f078a0c04b5d7e84e Content-Type: text/plain; charset=UTF-8 Thanks Bertrand. That explains things well. Well, I know of pieces where code documentation can surely be improved - I can start from that piece. Just out of curiosity - will we have GIT support for Flex? If yes, we can get it mirrored to GitHub (as with many other Apache projects). It would then be very easy to create pull requests on our own fork. Keep Walking, ~ Sandeep On Fri, Jan 6, 2012 at 1:40 PM, Bertrand Delacretaz wrote: > Hi Sandeep, > > On Fri, Jan 6, 2012 at 8:37 AM, Sandeep Gupta wrote: > > ...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?... > > We don't have a wiki for Apache Flex yet - we can request one, the > Flex PPMC members [1] only need to decide if they want a MoinMoin or > Confluence one as it's what the ASF currently offers. > > If Flex absolutely needs another tool, it's possible to get a virtual > machine to run pretty much anything we want on it, as long as this > PPMC agrees to take responsibility for that. > > > > > 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 :)... > > Anyone can submit svn patches against the Flex codebase, once that's > imported under http://svn.apache.org/repos/asf/incubator/flex/ which > should happen in the next few days. > > The usual process is for people to create a JIRA issue and attach > their patch to it, we'll need to explain this at > http://incubator.apache.org/flex/get-involved.html > > -Bertrand > > [1] http://incubator.apache.org/flex/team.html > --f46d0444ef1f078a0c04b5d7e84e--