Le jeudi 09 juin 2011 10:41:24, James Page a écrit : > That approach might work; I'll review my current list of variants for > patchsets that could be applied (and document it somewhere so it can > easily be reviewed). > Most changes either seem to be adding new distinct features or fixing > minor bugs that where impacting Jenkins. Ok, fine for me. > Is there any specific policy on taking this approach? In effect Debian > would be branching from the original upstream - this is in principle the > same as what jenkins are doing upstream although it would reduce the > code duplication in the distro. AFAIK, generic policy regarding patches in Debian package is linked to Debian "Social Contract", section 2 "We will give back to the free software community". Main goal is to submit most patches upstream to also improve FOSS ecosystem in general. But it's a bit complicated to apply to inactive upstream, so we can just include patches inside Debian and send them to upstream bugtracker (so at least other Linux dist can benefit from it. Cheers, -- Damien
Attachment:
signature.asc
Description: This is a digitally signed message part.