Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1968D1093E for ; Wed, 11 Feb 2015 04:04:45 +0000 (UTC) Received: (qmail 29266 invoked by uid 500); 11 Feb 2015 04:04:44 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 29079 invoked by uid 500); 11 Feb 2015 04:04:43 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 29068 invoked by uid 99); 11 Feb 2015 04:04:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 04:04:43 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 04:04:16 +0000 Received: by labpn19 with SMTP id pn19so984709lab.4 for ; Tue, 10 Feb 2015 20:03:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=uJqns3pdHk2wYcpS4T1QQ1G0DgohiwDlQGBrS8E4eFY=; b=M5h97hJMZX88MaSnTrPxQWonnrWnJ5jJ+DnN3wfwADCoX7CTccPlpwCuNfzpKhmTOJ cLE3qTDWSY34Ji5P6mUO7VX0JfCoyORpv5CN2sow131wFI7P68T0Bck4WWu6spGeBE62 kB1jNQNEXez4h3jr+xh3jG9JeCGuTBVIRA4yyJXX0mOeMtUikvLyhf3yA4CCNaQ+Nhqx IxXSLBZ/jbWwdJ1s6a3YBGvzXYQW3OaNCZhuTHezMGK08BZggZH9EWEHvjietxoOb32B UYBzcWzlP1RNEXURRQWFXTdCwNxutncECBeaMtFne4KN27NNyiSRmm35hRk13JoUa8S3 ASyQ== X-Gm-Message-State: ALoCoQkUbZ6xWfU/9pv1rvEsEfhkPQgprznXB1h3mTIom49f2uK4VcGU34I/sOUg7EgO7sXt0C/L MIME-Version: 1.0 X-Received: by 10.112.77.137 with SMTP id s9mr20985161lbw.55.1423627389510; Tue, 10 Feb 2015 20:03:09 -0800 (PST) Received: by 10.112.131.98 with HTTP; Tue, 10 Feb 2015 20:03:09 -0800 (PST) X-Originating-IP: [206.190.64.2] In-Reply-To: References: <54D3207D.3070404@salzburgresearch.at> <54D9DA3D.6080803@salzburgresearch.at> Date: Tue, 10 Feb 2015 20:03:09 -0800 Message-ID: Subject: Re: [DISCUSS] Commons RDF to join the Apache Incubator From: Marvin Humphrey To: "general@incubator.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org ATTENTION IPMC! If anybody is out there wants a low-stress Mentoring gig, this is it. And if you're an "RDF neutral" outsider, you'll be helping this project to achieve its goals, just by showing up. On Tue, Feb 10, 2015 at 3:14 PM, Stian Soiland-Reyes wrote: > Right - I think it would be good to leave as a decision to be made by > the PPMC when we get closer to graduation. One problem with TLP is that > we would likely need a different name ;-) So it would be advantageous in some ways to sort this out now. How good a fit is this project for Commons? Is it similar in scope and size to other Commons components? Any comments from current members of the Commons community? Should we be concerned about potential "umbrella project" issues, such as degrading signal-to-noise ratio on the Commons lists? Anybody else care to weigh in on the prospect of graduating a TLP which is anticipated to have low but sustainable activity? > Agree, Commons RDF is a slightly different proposal - in a way we need > the incubator mainly to mature the API (e.g. fight over method names) > and grow the community, rather than to be a "podling" to learn the > Apache Way and battle with NOTICE files. Given who's involved, this is going to be as easy as Mentoring gig as ever comes around. It's worth contemplating whether this project should be submitted as a TLP. Perhaps the initial group is not quite large enough and there aren't quite enough Apache Members, and long-term sustainability won't be established until the API negotiations succeed and the user community grows -- but still... >> The Champion's main work is to help formulate the proposal. That work >> is essentially done -- so it doesn't matter too much who takes that >> role, now. Are Andy and Reto opting out out as a gesture of openness >> to Sesame? > > Sergio has effectively been the Champion for this proposal, but I guess > he's not technically admissible as the Champion needs to be a Member or > Director. It's not uncommon for someone other than the Champion to do most of the hard work of drawing up the proposal, honestly. (I coordinated the drafting of the Lucy Incubator proposal long before I got the Member merit badge which qualifies me to serve as a Champion. It was the most educational activity I've ever undertaken at Apache.) Peter, who I see is active in Sesame, indicates that either Reto or Andy would be acceptable. If it would suit the community to have an outsider Champion, though, I'm willing to serve. To be honest there are other tasks around Apache that I need to attend to and I would rather be the one who hooked you up than take on a formal role -- so if another outsider is willing I'll stand aside. But I can't ignore the cost/benefit ratio here. > We were hoping to also get some "RDF neutral" mentors. See above. :) Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org