Hello,
Thank you for the explanation, it was brief and good. I hope you hear something good from me next days ;) !.
--
On Fri, Oct 28, 2011 at 4:41 PM, Toshio Kuratomi <a.badger@xxxxxxxxx> wrote:
On Fri, Oct 28, 2011 at 02:44:23PM +0000, Bousselham EL HADDAOUI wrote:A mixture :-). Tasks are open to everyone. Not everyone has permission to
> Thank you. Now I must learn first Python and I will see if I can do this task.
> I have a question : what is the procedure of resolving task or tickets ( for
> example: the task is open to every one ? or it's assigned to a specified member
> and he must do it! ).
perform a fix or not everyone has permission to commit a fix. In the latter
case, adding the fix as an attachment to the ticket and/or pinging someone
on IRC to review and commit it is what happens (and as you start doing that,
your name becomes well known and you become a candidate for getting more
permission).
Usually, people assign tickets to themselves when they take on the task.
That way other people know that you are working on it. Once in a while, if
we don't hear back from you, we may ping to see if you're still working on
it or if we should open it up for someone else to take a crack at.
(Speaking of which, go ahead and assign that ticket to yourself :-)
-Toshio
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Bousselham EL HADDAOUI
Élève ingénieur en 3ème année
École Nationale Supérieure d'Informatique et d'Analyse des Systèmes
Tél : 06 48 80 86 04
Élève ingénieur en 3ème année
École Nationale Supérieure d'Informatique et d'Analyse des Systèmes
Tél : 06 48 80 86 04
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
