From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C02C71389E2 for ; Mon, 8 Dec 2014 23:46:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C9EFE09F5; Mon, 8 Dec 2014 23:46:38 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9B71EE09B0 for ; Mon, 8 Dec 2014 23:46:37 +0000 (UTC) Received: from pomiot.lan (mgorny-1-pt.tunnel.tserv28.waw1.ipv6.he.net [IPv6:2001:470:70:353::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id E020834049E; Mon, 8 Dec 2014 23:46:35 +0000 (UTC) Date: Tue, 9 Dec 2014 00:46:28 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Subject: [gentoo-dev] metadata.xml un-ization, v2 Message-ID: <20141209004628.4de52564@pomiot.lan> Organization: Gentoo X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Wfxq2X/Me.JhnWJ8Ugdh_BU"; protocol="application/pgp-signature" X-Archives-Salt: 17bb97e3-29c8-48ac-9067-d301725f80c5 X-Archives-Hash: 52b7857d7e9870347b92104acc891998 --Sig_/Wfxq2X/Me.JhnWJ8Ugdh_BU Content-Type: multipart/mixed; boundary="MP_/C.S.S+8i/_B9OBB3LI+9qZs" --MP_/C.S.S+8i/_B9OBB3LI+9qZs Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, all. So considering the previous thread, the Council and QA discussions, I have prepared a new version of the metadata.xml update. To hopefully make everyone happy, I come with this three-step process: 1. Add type=3D"" attribute to tag (see attached patch), 2. Convert to , 3. Eventually drop from DTD. If you like the idea, I'll prepare a smart conversion script soon. As for the exact details, I've pretty much decided to go for featurism here, IOW making everyone happy. It also proves how absurd typing maintainers is but if you really feel like having it, sure. The default is 'developer', tags would be converted into 'herd' and there are other options including 'proxy-maintainer', 'project', 'team' meant to fit all our wannabies. The diff explains the particular options. The main benefit of this project over other ideas is that it preserves backwards compatibility. We're adding a new attribute which should simply be ignored by old tools. Since we still require to be something valid, the output will change a bit but will still be meaningful (or even more meaningful in some cases). And since I removed no-herd some time ago, we can drop tags without worrying. Note: this is just about metadata.xml, I'm not touching herds.xml. What do you think? --=20 Best regards, Micha=C5=82 G=C3=B3rny --MP_/C.S.S+8i/_B9OBB3LI+9qZs Content-Type: text/plain Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=metadata-maint-type.patch PyAuZ2l0DQpJbmRleDogbWV0YWRhdGEuZHRkDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpSQ1MgZmlsZTogL3Zhci9j dnNyb290L2dlbnRvby94bWwvaHRkb2NzL2R0ZC9tZXRhZGF0YS5kdGQsdg0KcmV0cmlldmluZyBy ZXZpc2lvbiAxLjEzDQpkaWZmIC11IC1CIC1yMS4xMyBtZXRhZGF0YS5kdGQNCi0tLSBtZXRhZGF0 YS5kdGQJOSBNYXkgMjAxMyAwNjo1ODo1NSAtMDAwMAkxLjEzDQorKysgbWV0YWRhdGEuZHRkCTgg RGVjIDIwMTQgMjM6Mzg6MDkgLTAwMDANCkBAIC0xMyw2ICsxMywxNCBAQA0KIA0KICAgPCEtLSBP bmUgdGFnIGZvciBlYWNoIG1haW50YWluZXIgb2YgYSBwYWNrYWdlLCBtdWx0aXBsZSBhbGxvd2Vk LS0+DQogICA8IUVMRU1FTlQgbWFpbnRhaW5lciAoIGVtYWlsLCAoZGVzY3JpcHRpb258IG5hbWUp KiApPg0KKyAgICA8IS0tIG1haW50YWluZXIgb3JnYW5pemF0aW9uYWwgdHlwZSAtLT4NCisgICAg PCEtLSBkZXZlbG9wZXI6IHJlZ3VsYXIgR2VudG9vIGRldmVsb3BlciAoZGlyZWN0IGUtbWFpbCkg LS0+DQorICAgIDwhLS0gaGVyZDogaGVyZCAoZGVmaW5lZCBpbiBoZXJkcy54bWwpIC0tPg0KKyAg ICA8IS0tIHByb2plY3Q6IHByb2plY3QgKGhhdmluZyBXaWtpL2cubyBwcm9qZWN0IHBhZ2UpIC0t Pg0KKyAgICA8IS0tIHByb3h5LW1haW50YWluZXI6IG1haW50YWluZXIgdGhhdCBpcyBub3QgYSBH ZW50b28gZGV2ZWxvcGVyDQorICAgICAgYW5kIGNvbW1pdHMgdmlhIGEgcHJveHkgLS0+DQorICAg IDwhLS0gdGVhbTogdGVhbSBvZiBwZW9wbGUgdGhhdCBpcyBub3QgYSBoZXJkIG5vciBhIHByb2pl Y3QgLS0+DQorICAgIDwhQVRUTElTVCBtYWludGFpbmVyIHR5cGUgKGRldmVsb3BlcnxoZXJkfHBy b2plY3R8cHJveHktbWFpbnRhaW5lcnx0ZWFtKSAiZGV2ZWxvcGVyIiA+DQogDQogICA8IS0tIE5h dHVyYWwgbmFtZSBmb3IgcGFja2FnZSwgZXhhbXBsZTogTGlicmVPZmZpY2UgKGZvciBhcHAtb2Zm aWNlL2xpYnJlb2ZmaWNlKSAtLT4NCiAgIDwhRUxFTUVOVCBuYXR1cmFsLW5hbWUgKCNQQ0RBVEEp ID4NCg== --MP_/C.S.S+8i/_B9OBB3LI+9qZs-- --Sig_/Wfxq2X/Me.JhnWJ8Ugdh_BU Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUhjhUXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOhN8QANgE6sIXM+QTnogzHm3BHlAY jNjDpohlsMHDdiWD3Z1DbqJa/hlHWxw1rqkftRT6nm6GoCSYucoLZCLc5i0MxV/3 0l8zTme3fUKLnQtUe33kTMi/3uGZPRMgD6gFJyGq+6cG36Qq3ReFs/K/hgvj7Q7f KZ2oDlYc/l+3VRHvcPunYnbmmEOAPIghRcBt0A7c4Fp6/0EKWW/SP/HudTLI1LiZ dYHLctVSFM1wo5phWNIKspee2jqiqTPMC6gi8JgDvOPHZ2lxdu/jBHOFWSYc++j0 VwnQlpWEATS1DA4X9cbMu7bLgeSuSAbp0UTWYvdrdlYHpYcBXA4kXUorVXaKVyn2 Khwx5UEIXNzFDn7cQZTxEqP0TeG2kAiv6mxA4h3ZX0khwGlZAvpG+RTNHA+GNlZb gl5h/pL+NmVpQqjkDcIqc/NpD/sZweummSvXM/Dc8ZyopnL/fZiUrj/VmqC5UDzs 3GfZq79qGv8d+UjbsCwqs4+W9UoL02jUBbMUxWNu4rq4Q4l1t9aEmpjeeoWVuQW4 AbTdOYNWatz8sdAM28vioHPDqFsKrFPwTA4sl0MfFCKMAgNqKKFSZgzlkQvNRuT5 ZaLDGl9tRlT58e1ur3SWWdAOZmA6zABzCDrMyT/wiF2qqC03CtdNYY/GNTvzm9hF YMOkgtlKujUQ3o8Jsw4p =Rt5Y -----END PGP SIGNATURE----- --Sig_/Wfxq2X/Me.JhnWJ8Ugdh_BU--