Return-Path: Delivered-To: apmail-lucene-lucy-dev-archive@minotaur.apache.org Received: (qmail 36096 invoked from network); 25 Jul 2010 20:15:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Jul 2010 20:15:57 -0000 Received: (qmail 85119 invoked by uid 500); 25 Jul 2010 20:15:57 -0000 Delivered-To: apmail-lucene-lucy-dev-archive@lucene.apache.org Received: (qmail 85086 invoked by uid 500); 25 Jul 2010 20:15:57 -0000 Mailing-List: contact lucy-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: lucy-dev@lucene.apache.org Delivered-To: mailing list lucy-dev@lucene.apache.org Received: (qmail 85078 invoked by uid 99); 25 Jul 2010 20:15:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jul 2010 20:15:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.116.39.62] (HELO rectangular.com) (68.116.39.62) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Jul 2010 20:15:51 +0000 Received: from marvin by rectangular.com with local (Exim 4.63) (envelope-from ) id 1Od7be-0004bn-Od for lucy-dev@lucene.apache.org; Sun, 25 Jul 2010 13:15:30 -0700 Date: Sun, 25 Jul 2010 13:15:30 -0700 To: lucy-dev@lucene.apache.org Subject: Re: Lucy JIRA perms/Admin Message-ID: <20100725201530.GC5117@rectangular.com> References: <20100725182922.GA5117@rectangular.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) From: Marvin Humphrey On Sun, Jul 25, 2010 at 11:49:51AM -0700, Mattmann, Chris A (388J) wrote: > > It seems like using LUCY Jira might be more appropriate, since some of the > > tasks -- e.g. our mods to Lucy's Jira :) -- don't seem to require Infra > > involvement. > > Yep, but let's be specific. What do you think should be LUCY Jira issues > versus INFRA issues? I care about getting the individual sub-issues right, and I care about updating the checklist at . I don't have strong opinions about whether or where we perform additional omnibus tracking. If others do, though, I'm happy to dot a few extra i's and cross a few extra t's. > 1. mailing lists (creation of lucy-*@incubator.a.o lists and migration of > existing subscriptions to new lists). I'd imagine this also includes > decommissioning of the old Lucene M/Ls for Lucy as they shouldn't be needed > any longer and per the Incubator resolution for Lucy, the Lucene PMC is no > longer cognizant over. When Infra "migrates" mailing lists, it looks like they put forwards in place on the old lists. > 2. SVN (did Hoss take care of this already?) It's not done until we all have commit access and everything in the existing repository under lucene/lucy has moved over. IIUC, we're waiting for someone within the Incubator with sufficient karma to take certain actions. For now I'm relying on Hoss to keep that ball rolling. > 3. Wiki (needs to move to incubator space?) I don't think it will have to move, though we may need to insert the incubation disclaimer on the front page. My preference is that it stay where it is. I have to step out right now, but full rationale will follow in another mail. > 4. Lucy UNIX groups under Incubator karma, removal of Lucy Lucene karma > rules (I think Hoss took care of this already) I think orderly shutdown of the existing Lucy Lucene subproject website, svn, etc needs to wait until everything is set up under incubator. > > Having said that, where we file it is an implementation detail I don't have > > strong opinions about. Please go ahead and open a ticket wherever you see > > fit. > > So, to me it looks like we need INFRA help with #1 and maybe #3, right? If > so, I'll handle filing the issues. Maybe just #1, which I've already claimed -- let's not duplicate. :) Marvin Humphrey