Doesn't project forking begin to solve this challenge in collaboration? Add another root CVS directory, assign new or existing host/maintainer( s ) to that node and move on!

A project fork doesn't have to be an exact dircopy of an old branch of code, but can contain extracts.

Nick

Ciaran McCreesh wrote:
On Sat, 26 Feb 2005 19:50:11 +0100 Simon Stelling <[EMAIL PROTECTED]>
wrote:
| > * the package is actively maintained and herded in metadata.xml
| | the bug is lying around for several months,
| | > * the package maintainer is easily contactable by irc or email
| | the package maintainer isn't on irc and did never comment the bug
| and your patch is only applyied on a specific arch which is CC'ed or | even in the AssignedTo field of the bug?


Didn't we decide that arch specific patches were a bad idea?

| Of course it's always better to ask first, but would it still be rude
| in  such a case? What if a revbump isn't needed?

Naah, if the maintainer has vanished and there's no herd backing them up
(or the entire herd has vanished) then it's a whole different story.


-- [email protected] mailing list



Reply via email to