diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110414/003974.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110414/003974.html | 96 |
1 files changed, 96 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110414/003974.html b/zarb-ml/mageia-dev/20110414/003974.html new file mode 100644 index 000000000..a3a5ccaaf --- /dev/null +++ b/zarb-ml/mageia-dev/20110414/003974.html @@ -0,0 +1,96 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Maintainers policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Maintainers%20policy&In-Reply-To=%3C201104141109.46884.anaselli%40linux.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003973.html"> + <LINK REL="Next" HREF="003976.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Maintainers policy</H1> + <B>Angelo Naselli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Maintainers%20policy&In-Reply-To=%3C201104141109.46884.anaselli%40linux.it%3E" + TITLE="[Mageia-dev] Maintainers policy">anaselli at linux.it + </A><BR> + <I>Thu Apr 14 11:09:43 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003973.html">[Mageia-dev] RFT: xen support +</A></li> + <LI>Next message: <A HREF="003976.html">[Mageia-dev] Maintainers policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3974">[ date ]</a> + <a href="thread.html#3974">[ thread ]</a> + <a href="subject.html#3974">[ subject ]</a> + <a href="author.html#3974">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>mercoledì 13 aprile 2011 alle 23:33, Anne nicolas ha scritto: +><i> - what about having co-maintenership or teams? How shall we manage this? +</I>I'm not against of that. I believe it could be a good way out +when people leave or can't/stop to work on their packages. Missing +all members of a team is a little bit harder :D + +I know some people prefer being the only owner, we could decide +case by case but finding packages that can be part of a group and +a team that can manage it could help either in bug management. + +Easy groups could be for instance: +kde +gnome +developer libraries +toolchain & co. + +But the real problem is that some packages could lay +on more than a group. For insntace, game and kde games +or educational and some games... and so on. + +I thought that a first try could be to have mentor and their +padawans seen as a team to maintain packages they've released +togheter. From that it should be easy to move maintainership +from one team member to another. But as ennael said that +could be more work for mentors. + +So i don't have a real solution :) but something to discuss on... + +Cheers, + Angelo +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 198 bytes +Desc: This is a digitally signed message part. +URL: </pipermail/mageia-dev/attachments/20110414/8fc9946b/attachment.asc> +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003973.html">[Mageia-dev] RFT: xen support +</A></li> + <LI>Next message: <A HREF="003976.html">[Mageia-dev] Maintainers policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3974">[ date ]</a> + <a href="thread.html#3974">[ thread ]</a> + <a href="subject.html#3974">[ subject ]</a> + <a href="author.html#3974">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |