Hello Nicolas, I'll check the documentation to do that as soon as possible. Thanks for your review and the tip. If I understand correctly the diff command would be "diff -u old new" or you need some more switches in general to the diff command (for example: diff -Naur)? I have to check that too! I'm not a regular user of IRC, so see you on #fedora-devel-fr when all this will be ready. Thanks for your response and your help! -- Nicolas

Hello Kevin, Thanks for this precision! I'll use your advises in the futur. -- Nicolas Viéville

Hello Hankur, Thanks for your proposition for help. I would not miss to ping you if needed! I'll try to make the spec file these next days. -- Nicolas Viéville

2011/10/24 Nicolas Viéville <nicolas.vieville(a)univ-valenciennes.fr&gt;: No, you don't need to be in approved state to submit a spec file for review. Once your modification will be approved and the reviewer considers you are capable to maintain a package, you will be approved into RPM Fusion cvsextras group of contributors. Then an ACL request need to be done for you to commit your changes into a given module yourself. Once that said, gaining ACL rights on a package may be optional. If you only want to provide a quick update once, you may only request the primary maintainer to apply your changes. The problem with the wl-kmod package is about to know who is the actual primary maintainer, and if none feels responsible maintaining the package (such as answering bug reports and fixing bugs that prevent continuation of service), then the package will be removed because of lack of primary maintainer. Nicolas (kwizart)

On 25/10/11 02:30, Nicolas Viéville wrote: Further to kwizart's response: For a new or retired package, we review both the package and the proposed maintainer via an RPM Fusion bug Review Request. An example is here: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1992 and the process to follow is part of the page: http://rpmfusion.org/Contributors http://rpmfusion.org/Contributors#head-0df093adde5a77a5e0569b2460ff49d078... So I would suggest the same method, even though this is an "almost" existing package, ie post the .spec and srpm, and show that you have built it in mock. (Note that RPM Fusion's package maintenance process matches Fedora's old process from quite a few years ago).

Salut Nicolas ! Welcome ! ++ ----- Mail original ----- De: "Nicolas Viéville" <nicolas.vieville(a)univ-valenciennes.fr&gt; À: "RPMFusion Devlopers" <rpmfusion-developers(a)lists.rpmfusion.org&gt; Envoyé: Dimanche 16 Octobre 2011 17:59:12 Objet: Newcomer Hello List, I'm a newcomer to this list. My native language is french, so forgive me if my English is not correct at all. I'm also a newcomer to the packaging activity by becoming the co-maintainer of Sinha Ankur on broadcom-wl and wl-kmod packages for Fedora 15. As suggested on the contributors page of the RPMFusion site, here's the thread containing the package change request: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1907) As a newcomer, I need someone to sponsor me to this new activity. Maybe my co-maintainer could accept to do so. Thanks in advance for sponsoring me. I will certainly have a few naive questions to ask after reading the documentation on setting-up my environment to begin to contribute, most probably on the ssh/cvs-connection part. Thanks in advance for your advice. All questions or comments on this subject are welcome. Cordially, -- Nicolas Viéville