Return-Path: X-Original-To: apmail-aries-dev-archive@www.apache.org Delivered-To: apmail-aries-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B47E19541 for ; Thu, 27 Oct 2011 15:17:16 +0000 (UTC) Received: (qmail 45564 invoked by uid 500); 27 Oct 2011 15:17:16 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 45529 invoked by uid 500); 27 Oct 2011 15:17:16 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 45521 invoked by uid 99); 27 Oct 2011 15:17:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2011 15:17:16 +0000 X-ASF-Spam-Status: No, hits=0.4 required=5.0 tests=FREEMAIL_FROM,FRT_ADOBE2,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jpjhughes@gmail.com designates 209.85.161.178 as permitted sender) Received: from [209.85.161.178] (HELO mail-gx0-f178.google.com) (209.85.161.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2011 15:17:12 +0000 Received: by ggnh1 with SMTP id h1so3556778ggn.23 for ; Thu, 27 Oct 2011 08:16:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=FMfFiAw9L+KvcKvVdAEk3Mokhc7ldAKGeNmSO/I/5oU=; b=FE0V9JjDwX3si63XMQsr/Y3e9cFusgJq/q+WaupSPAooOx2Ftr796h5ZzEkvg1Lmzd pRl6hNhnXMtpyEIYRzH3/JokwkHaNo+HFogM4FzcXGJZIQ2LzWd2B970XzfwCbyXqDNm yez/o1lpafEmwy51pssRHaQVsKWmyX/BkiF6M= Received: by 10.236.124.97 with SMTP id w61mr52412070yhh.106.1319728611146; Thu, 27 Oct 2011 08:16:51 -0700 (PDT) MIME-Version: 1.0 Sender: jpjhughes@gmail.com Received: by 10.147.38.11 with HTTP; Thu, 27 Oct 2011 08:16:31 -0700 (PDT) In-Reply-To: <91C6FBF7-2E85-4C01-BBAD-1DF64BC6022B@adobe.com> References: <91C6FBF7-2E85-4C01-BBAD-1DF64BC6022B@adobe.com> From: Jeremy Hughes Date: Thu, 27 Oct 2011 16:16:31 +0100 X-Google-Sender-Auth: ySWpfm6n7bn03MNURHwmogiTbsI Message-ID: Subject: Re: board report To: dev@aries.apache.org Content-Type: text/plain; charset=ISO-8859-1 Yeah, thanks David :-) On 27 October 2011 16:10, Felix Meschberger wrote: > Hi, > > Thanks for reporting back from the IRC channel since not everybody sitting on this mailing list is also sitting on the IRC channel. That's why there is a saying in the ASF that if it wasn't on the mailing list, it didn't happen ;-) > > Regards > Felix > > Am 27.10.2011 um 17:00 schrieb David Bosschaert: > >> Just for the record, after some discussion on #apache-aries the >> decision was made that this work should be done on a copy of the jmx >> directory in trunk/sandbox/jmx-next >> >> Cheers, >> >> David >> >> On 24 October 2011 22:53, Jeremy Hughes wrote: >>> Well it's a good point that forking/branching on github is so easy but then >>> svn copy is also a oneliner. There was a discussion on one of the Apache >>> lists on use of github which I should catch up with to see what the general >>> view is. Personally I'd say if you want to collaborate use Apache SVN and >>> the Apache infra ... mailing lists etc. You can't accept patches as easily >>> out on github ... well accepting pull requests are easy but AFAIK there's no >>> ASL assignment checkbox that JIRA has. If/when you bring the code back into >>> Aries in SVN if you've accepted patches or pull requests in github you would >>> need to find those people and get them to license their patches under the >>> ASL. >>> >>> Cheers, >>> Jeremy >>> On 24 Oct 2011 19:42, "David Bosschaert" wrote: >>> >>>> Sure it could but then it should really happen on a branch. I thought >>>> https://github.com/apache/aries was the official Apache mirror of >>>> Aries. Branching on git is easier so that's why I started there. >>>> I can't really do it on trunk as it will take a couple of months >>>> before it's complete. >>>> >>>> Would you prefer it on an SVN branch? >>>> >>>> Cheers, >>>> >>>> David >>>> >>>> On 24 October 2011 17:50, Jeremy Hughes wrote: >>>>> Hi David, Thanks for that. I'm curious though - could this work go on >>>>> in Apache SVN rather than off on the side in GitHub? >>>>> >>>>> Cheers, >>>>> Jeremy >>>>> >>>>> On 24 October 2011 17:06, David Bosschaert >>>> wrote: >>>>>> Hi Jeremy, >>>>>> >>>>>> It might be worth mentioning that work has started on implementing the >>>>>> OSGI RFC 169 [1] enhancements to the OSGi-JMX spec in Aries/JMX. At >>>>>> this stage it looks like Aries will become the Reference >>>>>> Implementation of this spec. >>>>>> >>>>>> The current status can be found on the following branch on the github >>>>>> mirror of Aries: >>>>>> https://github.com/bosschaert/aries/tree/davidb/jmxv2_ri >>>>>> >>>>>> Cheers, >>>>>> >>>>>> David >>>>>> >>>>>> [1] http://www.osgi.org/download/osgi-early-draft-2011-09.pdf >>>>>> >>>>>> On 24 October 2011 16:45, Jeremy Hughes wrote: >>>>>>> Hi everyone, I've put together our board report [1]. Please add >>>>>>> anything significant I might have missed. I'll submit it to the board >>>>>>> at 6pm UK time / 10am Pacific. >>>>>>> >>>>>>> [1] http://aries.apache.org/overview/boardreports/october-2011.html >>>>>>> >>>>>>> Thanks, >>>>>>> Jeremy >>>>>>> >>>>>> >>>>> >>>> >>> > >