From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-January/010850.html | 94 +++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/010850.html (limited to 'zarb-ml/mageia-dev/2012-January/010850.html') diff --git a/zarb-ml/mageia-dev/2012-January/010850.html b/zarb-ml/mageia-dev/2012-January/010850.html new file mode 100644 index 000000000..7ee499261 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/010850.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] packaging savoir-vivre + + + + + + + + + +

[Mageia-dev] packaging savoir-vivre

+ Maarten Vanraes + alien at rmail.be +
+ Sun Jan 1 03:29:07 CET 2012 +

+
+ +
Op zaterdag 31 december 2011 18:42:22 schreef nicolas vigier:
+> On Wed, 28 Dec 2011, Maarten Vanraes wrote:
+> > imho the best solution is that everyone checks if there's a maintainer
+> > for it and asks maintainer first...
+> > 
+> > i mean, it's all nice that it's in the spec file, but i think people who
+> > bump, rarely look inside spec file... (not saying any names)
+> 
+> So you think people who don't take the time to look at spec file before
+> submiting something will want to take the time to ask maintainer ?
+> 
+> It's a good idea to ask maintainer before making important or possibly
+> controversial changes, but for simple or obvious changes it's not really
+> needed. In that case, if for some reason a package should not be
+> submited, it's a good idea to add a comment in the spec file. It's also
+> a good idea to check the diff between current and pristine before
+> submiting a package.
+
+and also a good idea to check if a package has a maintainer and at the very 
+least notify him/her.
+
+- if (s)he makes mistakes, that's already useful
+- but what's more, you could indeed be making some changes, which could be 
+ignored.
+
+i don't know about you, but if there's a problem i have the fix for for a 
+package that's maintained by others, i think it's good form to notify them 
+with the patch so that they can do it; if they don't, you still can.
+
+unless it's really urgent that you fix this now... i don't see the need/reason 
+to just bypass the maintainer completely. (unless you have an understanding 
+with said maintainer; then, it's a different thing)
+
+the changes you make to his/her package, (s)he has to maintain and get bugfixes 
+for...
+
+imho this is no more than just common politeness...
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1