Bob Finch wrote:
If I understand the question correctly, and I may not.....
The answer is that you are a "contributor" of a PKGBUILD (et al) unless you are a TU, in which case you are "maintaining" the *binary* package.
Or at least that was what it was in at first.
Very best regards;
Bob Finch
On Thu, Oct 9, 2008 at 7:08 AM, Callan Barrett <wizzomafizzo@gmail.com <mailto:wizzomafizzo@gmail.com>> wrote:
On Thu, Oct 9, 2008 at 6:13 PM, Henning Garus <henning.garus@googlemail.com <mailto:henning.garus@googlemail.com>> wrote: > It does make sense, at least to me, to have your name and email > address in a PKGBUILD you currently maintain in AUR, even if you > didn't create it. However, I don't think there is any policy about > this. I have seen some "custom" tags, which I can't remember exactly > and of course much misuse of the maintainer tag - I am guilty of that > one myself. > > What one could do to prevent further misuse of the Maintainer tag > would be introducing a new tag like AUR-Maintainer and put it in the > wiki. Notice that this is just an example, I wouldn't be against > calling this different. It wouldn't stop the "Maintainer Tag problem" > all at once, but it might help reducing it.
I've never understood this rule, especially when I was enforcing it. Why aren't AUR maintainers allowed to use the maintainer tag?
-- Callan Barrett
So, I guess we can all agree on the following two: 1) Someone who submits a *new* package puts himself as "Contributor". 2) The developers and TUs that maintain binary versions of packages (and only they) may list themselves as "Maintainers". The above is what's written in the wiki as well. An alternative would be to list all people who modify the original PKGBUILD (i.e. updating/patching/restructuring) as "Contributors". I'm not fond of this approach as, considering an extreme case where 10+ individuals are involved, having a lengthy list of "Contributor" tags would look pretty damn ugly. This could be bent a bit though, by allowing a person that heavily modifies a package to include himself/herself at his/her own discretion. PS: I don't mind not being mentioned in an orphan package I've adopted, I just wasn't aware that the "Maintainer" tag is applicable only to Devs/TUs. I think that this point should be made clear on the wiki, in a relevant to the AUR article [1]. ---------------- [1] Maybe here: http://wiki.archlinux.org/index.php/AUR_User_Guidelines#Maintaining_Packages...