Re: GR proposal: mandating VcsGit and VcsBrowser for all packages, using the "gbp patches unapplied" layout, and maybe also mandating hosted on Salsa
Hi all It seams to me reading this thread that there are those who would like to mandate the use of a given VCS on a particular host. The primary advantages being that it makes CI so much simpler, and having a uniform workflow makes it easier for those not maintaining a given package to view and make changes (occasionally distribution wide). On the other hand there is also those who would rather not see this become mandatory. Various reasons have been given, but if I have understood correctly they boil down to a few classes namely; doesn't fit our model, a lot or work to change for few if any perceived benefit, principled belief that maintainer is free to maintain however they see fit. Personally I see no reason to mandate such a change, with policy only recommending / preferring the proposed changes. Furthermore I accept that the policy should strongly recommend (i.e. require an explanation why not) for NEW packages. Clearly, maintained packages that do not match the proposed new VCS & Layout will be harder &/OR require additional effort from people that only understand this new work flow to to work on. However these packages are being maintained by people that DO understand the existing workflows etc. Sure such packages may not 'benefit' from some of the CI testing that *may* get produced or some project wide automated changes - these tasks *may* still need to be done by the existing maintainers - that is a 'cost' of choosing not to standardise on on the proposed new system. Of cause should the package in question no longer be maintained by the exiting maintainer/team then whoever picks up the package afterwards would be free to move to the new setup as they see fit - potentially understanding better the reason that the previous maintainer chose not to adopt the new setup along the way :-) /Andy
Re: GR proposal: mandating VcsGit and VcsBrowser for all packages, using the "gbp patches unapplied" layout, and maybe also mandating hosted on Salsa
On Fri, Jul 26, 2019 at 11:40:31AM -0300, Andy Simpkins wrote: > Hi all (...) > /Andy Thanks Andy for putting that into words, I completly agree with you. -- tobi
on using the wrong mailinglists (Re: Upstream metadata to help our users contribute back to projects we redistribute.)
On Thu, Jul 25, 2019 at 05:27:51PM +0900, Charles Plessy wrote: > (posted on -project because of the context, but answers probably > belong to -devel, where I am not subscribed...) I understand we live in strange times, but pleaaase, if your content belongs on -devel, but you are neither subscribed to -devel nor -project then a.) please *dont* post to -private instead b.) either subscribe to -devel and post there or c.) dont subscribe to -devel and post there and ask to be cc:ed. Technical discussions about the development of Debian belong to debian-devel@. Thank you very much, HTH, HAND. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: GR proposal: mandating VcsGit and VcsBrowser for all packages, using the "gbp patches unapplied" layout, and maybe also mandating hosted on Salsa
On Thursday, July 25, 2019 11:02:14 PM EDT gregor herrmann wrote: > On Wed, 24 Jul 2019 12:23:42 +, Scott Kitterman wrote: > > We are > > perfectly capable of phasing out obsolete workflows without a > > hammer like a GR (remember dpatch). > > Unrelated to the general topic but since you mention it: Yes I > remember dpatch -- it's not phased out, I just encountered it a few > days ago. It's true it's not extinct, but it's close. It's only used by several dozen packages now. If someone wanted to push to get dpatch completely out of the archive this cycle, I think it would be perfectly reasonable. The project has voted with their feet. Scott K
Debian Maintainers Keyring changes
The following changes to the debian-maintainers keyring have just been activated: 1o5g4...@gmail.com Removed key: 5BD067A29DFCA64B19CC7AD9D4330926497D44FE eugen.d...@pu-pm.univ-fcomte.fr Removed key: 11DD7D0BBA65B6AE507DD59200AB067AE47B79A4 jared_doming...@dell.com Removed key: B1811955D22D331B4BBD2990D97B2BA886A10CC0 abart...@samba.org Removed key: 81609BF85375BA5E510CCEA1FE001D44C8021865 christ...@amsuess.com Removed key: 08CD6D1255FA3A875C1FB096398D1112D3A4BDE1 clo...@igalia.com Removed key: B5D2B50BC48EC7F1EE90D9AB965089CE6B95F882 d.fil...@ubuntu.com Removed key: 126064058E7A80FE7D0672298F342172F407DB73 el...@heebs.ch Removed key: 71B8F031E648BCD95EAC18FA47712171F2ED62FB giuliop...@gmail.com Removed key: 00FC3F400DC16182193B659DCEC9942DB7ADB86F guillaume.tu...@gmail.com Removed key: 0ADA061F36B34833EA75DEF6C6079EAD0F1F7C52 ha...@rostlab.org Removed key: 85BA68475220E66963B122E8B488E3AA46FC0C03 i...@zmailbox.ru Removed key: 8196843E50756F72F99114B293899384DC2C77F4 james.h...@ubuntu.com Removed key: 80887BA0E28203ADC125E0049D50E144E6357327 j...@beathovn.de Removed key: 730CCA1EF04C3289457DC622C0215925C6D815D8 janpas...@vanbest.org Removed key: 566A0E6BF957F44032BF2DBAF8307A6ED690AC06 joehe...@gmail.com Removed key: 102E2FE7D5141DBD12B260FCB09E40B0F2AE6AB9 jst...@mehercule.net Removed key: CACE80AE01512F9AE8AB80D61C01F443C9C93C5A l...@ubuntu.com Removed key: F1096C5F1261014E0584EAB4332B94FED282FC25 michele.c...@gmail.com Removed key: D003326F93F33345EF9ADC4BD61360421C9B1AE5 nick.m.d...@gmail.com Removed key: D95C32042EE54FFDB25EC3489F2733F40928D23A pgqui...@elpauer.org Removed key: CD6612E87145C5B11EE63402936A835B678B9796 russell@gmail.com Removed key: A91E230C30A67BA1329C276822B1092ADDDC47DD schol...@fnb.tu-darmstadt.de Removed key: DE0837244DAFAE6C5DF33AD57EAE264181E773D5 sgmo...@kde.org Full name: Scarlett Moore Added key: 7C35920F1CE2899E8EA9AAD02E7C0367B9BFA089 simro...@gmail.com Removed key: 50713992E9A91E77240128915675ADD39CF02226 tiago.my...@gmail.com Removed key: 356CD3A1C2CE3CC155D2281E06C285ACEF93257A tshep...@gmail.com Removed key: CC7A536FE267C679439BE8C429572B2F500BF4A2 yauh...@kaliuta.org Removed key: FBF3EEAFA7807802B56B27A970A8FEE074B3ED3A Debian distribution maintenance software, on behalf of the Keyring maintainers
