Bug 32322

This page is a good start to understand the different ways how to contribute to Mageia. It also explains the right ways to apply for the different roles. Unfortunately Bugzilla is not the right way for your request...
https://www.mageia.org/en/contribute/

Status: NEW => RESOLVED
Resolution: (none) => INVALID

You are mazing guys (some times not in a good sense)
The house is on fire, come some one to try to help to reduce the fire and all you can say is, you knock on wrong door check the map of the house, and slap the door instead of suggest the right door to knock.

At less on discuss list suggest me try on other list

Your help is for sure welcome. But as you didn't say in which way you want to contribute, the mentioned wiki page explains you the different fields where you can support the distribution. As each role uses other mailinglists and tools (as explained under each link for the roles), there are different ways how to go forward.

Nobody slapped a door or rejected your offer to help. You are highly welcome. But you need to understand that Bugzilla is for reporting bugs and the wiki pages explains how to get in contact to the different groups which own a role in the Mageia distribution.

It was too hard ask me give more information to make clear my request instead of directly closing the bug?

Lets see if i understand good enough how the updates is handled to make me clear, and maybe this time you send me to the right door because for me is also not clear enough.


1. Some one detect a fail in one package an make the report like in  https://bugs.mageia.org/show_bug.cgi?id=32230
1.1. Some packager push packages in a testing repository explain why y what is fixed, like in https://bugs.mageia.org/show_bug.cgi?id=32296 , some time if reporter and packager is the same the previous step is semi skipped
2. The reporter or packager or some of bugsquad ask to qa team to test and validate or reject the testing packages

If the packages are validated

3. The reporter or other nice guy make a Advisory describing what is fixed and what rpms and src.rpms need to go from testing to official updates

And where comes the part where i wish to help

4. Some one with access to server and/or special tool , run some scripts and/or pass to the tool the needed information: Advisory, list of rpms and src.rpms 
5. The scripts or the tool move the rpms and src.rpms from testing to official updates , publish the advisory, regenerate the urpmi and dnf metadata

Just in case, i want to be one of the persons that can make step 4.

Thank you

(In reply to katnatek from comment #4)
> It was too hard ask me give more information to make clear my request
> instead of directly closing the bug?

Please understand that Bugzilla is for reporting of bugs and not for user education. For basic questions the forums or mailing lists are more suitable. Using bugzilla for such questions binds the scarce ressources from bugsquad and other helpers.

Your step 4 doesn't exist in this kind of way but is part of a packagers job. If you want to become a packager the process is described in the wiki and linked from the page that was already posted. Here again the direct link:
https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

After reading this link you may understand why bugzilla is not the right communication channel to apply as packager as it is the wrong communication channel for such requests.

Thanks again for your offer to help Mageia. You are highly welcome!

I suspect that should be something like step 4 because if any packager can do it then i don't understand why the testing packages are still there and not already on official updates.

Sadly the two people that i suspect i could make the question leave.

Thank you

Well marja send my a reply and i know where to go and what to read.
I let part of the text

"Step 4 is more complicated than it seems, it isn't just uploading the
advisory and list of the (S)RPMs, corrections may need to be made and
that is best done by someone who has experience as QA member.
https://wiki.mageia.org/en/How_to_create_an_update_advisory#Creating_.28or_modifying.29_an_Advisory

Do you have experience as QA member? If not, you might want to become a
member and help testing updates. It is a really nice team and their work
is invaluable. A good overview of what is involved in QA testing can be
found here https://wiki.mageia.org/en/QA_process_for_validating_updates"

Thank you

[Ignoring that this was not the best place to ask - never mind, it is done]

(In reply to katnatek from comment #0)
> Due recent leaves on mageia we have some important number of updates 
> I will like to help to mitigate that
> I obviously need some to teach me the work flow and give me the necessary
> access
It looks as if joining QA might be the best option, The second link in the previous post is good. But first: https://wiki.mageia.org/en/QA_Team

> I have a few TI skills and i feel i can help on this theme
You are well known to us as a very competent & interested user whose contribution to bugs is already valuable. To actually clear outstanding bugs, becoming a packager would be more than appreciated. This has a longer apprenticeship. Start from https://wiki.mageia.org/en/Packagers_Team_portal

(In reply to katnatek from comment #4)
> And where comes the part where i wish to help
> 4. Some one with access to server and/or special tool , run some scripts
> and/or pass to the tool the needed information: Advisory, list of rpms and
> src.rpms 
> 5. The scripts or the tool move the rpms and src.rpms from testing to
> official updates , publish the advisory, regenerate the urpmi and dnf
> metadata
> Just in case, i want to be one of the persons that can make step 4.
The packager who pushes the update should write - in the bug - the advisory to go with it. You will have seen these. Once the update has been through QA and 'validated', the actual advisory needs transcribing & submitting to the Advisory system. This might pehrpas be automated (I wrote a script to help me when I did that, but it was still all manual transcription). Once that has happened, the process *is* then automated: the transfer of the update to the update media, its pushing to the mirrors etc.

CC'ing DaveH who know better about this. I suggest communicating directly with him to start with, rather than using this bug.

CC: (none) => davidwhodgins

(In reply to Lewis Smith from comment #8)
I still have some doubts about become a mageia packager, and feel do that and join qa is bite more that i can chew, but i can't be congruent with myself if i no try

I hope my actual skills packaging make the process a few more quick

@Lewis Smith, i can't found a soft way to say this, so here i go
David Hodgins is one of the the persons i say leave mageia , as you know the other is Thomas B.

Yes - I discovered this indirectly after I suggested him (DH)!
Do not contemplate QA *and* packager; just one would help.