From owner-freebsd-eclipse@FreeBSD.ORG Tue Apr 22 09:15:57 2014 Return-Path: Delivered-To: eclipse@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E4597FF; Tue, 22 Apr 2014 09:15:57 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D03C1A0C; Tue, 22 Apr 2014 09:15:56 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1WcWnv-0005PY-GO; Tue, 22 Apr 2014 11:15:53 +0200 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "ports-committers@freebsd.org" , eclipse@freebsd.org, "John Marino" , marino@freebsd.org Subject: Re: Time to dissolve eclipse@ team? Others want to maintain / team concept in general References: <53537775.5080607@marino.st> Date: Tue, 22 Apr 2014 11:15:50 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <53537775.5080607@marino.st> User-Agent: Opera Mail/12.16 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.1 X-Scan-Signature: 1f72ff50073f138f9668c095d6f579a1 Cc: FreeBSD Ports Management Team X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 09:15:57 -0000 On Sun, 20 Apr 2014 09:29:57 +0200, John Marino wrote: > For several months while scanning our numerous PRs, I've noticed people > complaining Eclipse was woefully out of 9 month ago. There have been > several PRs and they aren't even getting answered. > > I see a new one on 15 April, requesting maintainership also with > offering patches to update to the latest version. > > As I understand it, the eclipse@ team is down to a single person, and I > don't think the team concept should be used with less than 3 people. > > What's I'd like to see happen: > > 1) Portmgr establish minimum requirements for a "team". Nobody is going > to touch a PR owned by a team, even if it has timed out for months. I > recommend that a team must consist of at least 3 people, and if this > requirement cannot be maintained then the team must be dissolved. > > 2) the eclipse team should be dissolved unless more people join it > immediately. The ports owned by eclipse should be reassigned to either > the current member of eclipse or ports@ > > 3) seriously consider given eclipse maintainership to Jimmy Kelly if the > current maintainers don't have enough time anymore. > > Eclipse is an important set of ports and having such an old version > doesn't look for ports, so it could be a Public Relations issue as well. > > All that said, maybe the eclipse@ team has plans, but they certainly > haven't been communicated. None of the last 5 PRs going back July 2013 > have been responded to. > > Thanks, > John At least reward people who make a PR with a patch for a new version of Eclipse with a port. People who actually do the work are the ones who make open source work. Just make an eclipse43 port. I understand there is a eclipse-plugin-framework which must work with the eclipse port, but more exposure to new ports besides a patch on the mailinglist would be great. Regards, Ronald.