Return-Path: X-Original-To: apmail-incubator-deltaspike-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-deltaspike-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 7BBB898D9 for ; Mon, 2 Jan 2012 00:10:41 +0000 (UTC) Received: (qmail 22087 invoked by uid 500); 2 Jan 2012 00:10:41 -0000 Delivered-To: apmail-incubator-deltaspike-dev-archive@incubator.apache.org Received: (qmail 22063 invoked by uid 500); 2 Jan 2012 00:10:41 -0000 Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: deltaspike-dev@incubator.apache.org Delivered-To: mailing list deltaspike-dev@incubator.apache.org Received: (qmail 22055 invoked by uid 99); 2 Jan 2012 00:10:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 00:10:41 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of john.d.ament@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vx0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 00:10:33 +0000 Received: by vcbf1 with SMTP id f1so11268947vcb.6 for ; Sun, 01 Jan 2012 16:10:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=JRwvNGLjLBSAlauIm1FFqTXNtvhWHLCxoz8vSEe8XRg=; b=LtaP2NjHOIy4UiJFw4SCMuyR7R/fvS/TR8dTWHFaa5Q4mh/hSpryJAoPMYiP3PBsFh IzBMOeGiIaqW654tJURfcdRqhdjefVAUU4B6FMl8wil4/tbfm42QP9IRbPtDwX+vEHTb OvuI37H+Xe9k1XOc/UKoPm044Di+t4M2idypc= MIME-Version: 1.0 Received: by 10.52.32.163 with SMTP id k3mr14796213vdi.35.1325463012267; Sun, 01 Jan 2012 16:10:12 -0800 (PST) Received: by 10.52.28.167 with HTTP; Sun, 1 Jan 2012 16:10:12 -0800 (PST) In-Reply-To: References: Date: Sun, 1 Jan 2012 19:10:12 -0500 Message-ID: Subject: Re: Project Planning From: "John D. Ament" To: deltaspike-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec51d27660255d104b58068f1 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51d27660255d104b58068f1 Content-Type: text/plain; charset=ISO-8859-1 So (and this is going to sound extremely cliche) What can I do to help? Cuz right now I see lots of commits from you and strub, Lots of discusses. John On Sun, Jan 1, 2012 at 6:47 PM, Gerhard Petracek wrote: > hi john, > > jason did that already for solder. > > in general: > we added all parts to [1] and created tasks [2] to discuss them on the > mailing list (see the "[DISCUSS] ..." mails). > we started to discuss the features with the highest ranking. as soon as we > agree on a feature, we create a "feature"-ticket (e.g. [3]) and it gets > committed to deltaspike. > afterwards we continue with the next feature/s > > regards, > gerhard > > [1] > https://cwiki.apache.org/confluence/display/DeltaSpike/SE+Feature+Ranking > [2] https://issues.apache.org/jira/browse/DELTASPIKE-2 > [3] https://issues.apache.org/jira/browse/DELTASPIKE-21 > > > > 2012/1/2 John D. Ament > > > Hi All > > > > Was wondering, since I'm new at this and completely lost, how do we go > > about putting features into deltaspike? Let's say I love something in > > Solder and figure that would be great for deltaspike, do I just create a > > JIRA, email the group saying I want XXXX and here's why? Maybe I missed > an > > on boarding seminar somewhere .. :-) > > > > Thanks, > > > > John > > > --bcaec51d27660255d104b58068f1--