From owner-freebsd-gnome@FreeBSD.ORG Mon Mar 8 05:44:40 2010 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDD41106566C; Mon, 8 Mar 2010 05:44:40 +0000 (UTC) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id 9F8438FC14; Mon, 8 Mar 2010 05:44:40 +0000 (UTC) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.4/8.14.4) with ESMTP id o285jFS4090476; Mon, 8 Mar 2010 00:45:15 -0500 (EST) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Michal Varga In-Reply-To: <3f1fd1ea1003071809i4ad35d6jf5e8cd500ac7ae02@mail.gmail.com> References: <3f1fd1ea1002250318o582bbd5ua5a695e3af5e3cb9@mail.gmail.com> <3f1fd1ea1002250713v29671732i57d89ad0f666d1b@mail.gmail.com> <1267112635.4439.27.camel@headache.rainbow-runner.nl> <3f1fd1ea1002250754i1b9f1096ma8d3b80b168f27f0@mail.gmail.com> <1267115639.4439.59.camel@headache.rainbow-runner.nl> <3f1fd1ea1002251321pddf7639g349b17f92db991ec@mail.gmail.com> <3f1fd1ea1003032019o59a92e3fhd3fdbd98b7479f0f@mail.gmail.com> <1267800450.91818.8.camel@headache.rainbow-runner.nl> <3f1fd1ea1003071706i6fde25fkc6a62632e19c9d9d@mail.gmail.com> <1268011089.96436.22.camel@shumai.marcuscom.com> <3f1fd1ea1003071809i4ad35d6jf5e8cd500ac7ae02@mail.gmail.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-7MQdGt80WyZpRsMdZ/y8" Organization: MarcusCom, Inc. Date: Mon, 08 Mar 2010 00:44:50 -0500 Message-ID: <1268027090.96436.31.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,HELO_NO_DOMAIN autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on creme-brulee.marcuscom.com Cc: gnome@freebsd.org, Koop Mast Subject: Re: marcuscom and www/epiphany-extensions X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 05:44:40 -0000 --=-7MQdGt80WyZpRsMdZ/y8 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable On Mon, 2010-03-08 at 03:09 +0100, Michal Varga wrote: > On Mon, Mar 8, 2010 at 02:18, Joe Marcus Clarke wr= ote: > > We are spread thin, and we can always use help. The major work, though= , > > is typically with the first-time port or first-time minor version bump > > update. After that, the micro revs are typically trivial. > > > > But there are a lot of components to GNOME, and even bumping versions > > and distinfos can get tiresome. GNOME 2.29.92 is imminent, so if you > > want to jump in, and help with the updates, you are more than welcome t= o > > do so. > > > > Joe > > > Yep, that's what I had in mind. >=20 > Are there any mechanisms in place to 'book' a particular set of > components that I'd plan to keep an eye on? To explain, there are two > particular issues that concern me. Not really. We hang out on IRC (on #freebsd-gnome on Freenode). Usually what happens is that someone will say, "hey, is anyone working on X?" If not, then that person will take the port. I typically monitor ftp-release-list on http://lists.gnome.org, and work my way down the list. >=20 > First - I have, for example, no accessibility users (incl. myself), or > the whole tomboy/mono hilarity, or say, packagekit. While I probably > could blindly port the next release in queue, see if it builds, run > some plist checks, etc., I wouldn't be able to see if it actually > works, as in the best case scanario, I wouldn't have a clue about the > proper function of that component (so let's say, while I'm aware what > Orca is generally supposed to achieve, I have no idea about particular > details of a common accessibility users's setup and how he uses it. So > I might pretty much port a version that has "well, it seems to be able > to start" as the only working feature). We operate in the same manner. While some of us can test certain ports, we can't test them all. We do basic sanity checks, and rely on our users who may be more familiar with how the ports should work to alert us to problems. >=20 > Second is the work duplication - obviously it doesn't to any good when > two people spent last few hours on a bunch of ports, then submit them > at about the same time, only to see that they both also duplicated > half of the work of each other (and I can only do that probably few > times a week, there are those usual "full time job / kids" issues). I > can imagine that especially first few days after a new Gnome release, > this would happen regularly without any "these ports are mine, don't > touch them" in place, so I presume there is something that deals with > it. IRC is probably the best. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-7MQdGt80WyZpRsMdZ/y8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkuUjtAACgkQb2iPiv4Uz4dXkQCbByyW0J69FWVfLEO1zEl5/OI9 OVQAoKwN36GFwgmiAGHE177icZMXYeWF =1r06 -----END PGP SIGNATURE----- --=-7MQdGt80WyZpRsMdZ/y8--