[arch-dev-public] Moving packages into community

[Sébastien Luttringer]

Hi,

Most of the time, when a TU is working on adding a new package to
community, he could:
- Send a message on aur-general at al.org
- Write some lines in the AUR package comments
- Open a BR for inclusion
- Push his new package to community.

This let him time to carefully:
- Test his modification
- Start his communication with upstream
- Warn the former AUR maintainers
- Request some feedback.

So, fellow TU, could you verify, before moving a package from AUR to
community, that it is not already in *and* not already in process of
being included.

I added some lines about that in our Guidelines[1].

Cheers,

[1] https://wiki.archlinux.org/index.php?title=AUR_Trusted_User_Guidelines

-- 
Sébastien "Seblu" Luttringer
https://seblu.net | Twitter: @seblu42
GPG: 0x2072D77A

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-dev-public/attachments/20140211/eb504230/attachment.asc>