On 12 February 2014 03:57, Sébastien Luttringer <[email protected]> wrote: > On 11/02/2014 14:39, Bartłomiej Piotrowski wrote: >> On 02/11/2014 02:37 AM, Sébastien Luttringer wrote: >>> - Send a message on [email protected] >>> - Write some lines in the AUR package comments >>> - Open a BR for inclusion >>> - Push his new package to community > > This is a short list of well known places where you can find hints that > someone is already working on moving your package. > I did *not* suggest that you should do one of the previous examples. > > I'm not telling you to open a BR before moving a package. I'm too lazy. > But if you move a package, it's a good idea to check if there is bug > report opened (or closed) about it. Like a feature request[1]. > >>> - Test his modification >>> - Start his communication with upstream >>> - Request some feedback. > > All these bullets was to justify, that sometimes, you need more time > than usual before pushing the binary package. That why we should check > the previous places before inclusion. > >> Address your issues to TU who modified your package. > Be sure that was the first thing I have done. > > However that's not the first time I see this happening during the > inclusion process, that motivated me to share this point on the list and > add this "obvious" recommendation in our guidelines.
Agree on all points, and have updated the wiki edit to make the suggestions clearer: https://wiki.archlinux.org/index.php?title=AUR_Trusted_User_Guidelines&diff=296958&oldid=296802 -- GPG/PGP ID: C0711BF1
