Re: [aur-general] TU Application - Seblu
On Fri 21 Jan 2011 21:38 +0200, Ionuț Bîru wrote: On 01/21/2011 09:10 PM, Grigorios Bouzakis wrote: Seblu wrote: It looks like a trick question! But if I want to be a good maintainer, I do understand the reasons. and **The trust does not exclude the audit.** Excuse me for asking but is there anything preventing you from moving cairo-xcb to community if you become a TU? Yes, us. As far as i know if you become a TU you can maintain anything you want that has more than 10 votes in the AUR. Becoming a TU means that you become a member in the developement team, a team in which we trust each other, respect each other decisions, use the same packaging standards, the same tools as developers etc. I think if the package meets the guidelines then you shouldn't bully someone into not maintaining it. As long as he's providing the support that should suffice. Sometimes we may need to adjust the guidelines, and we decide this as a group through a formal vote. If you are just going to ignore and say, screw Jan decisions, I'm going to upload it just because I can, you are not welcomed in the team. The TUs are a separate group in the Arch community who can make different decisions on what or what not to maintain. In the past theres been many patched beyond recongnition packages in community eg. many packages with lcd patches from ubuntu, urxvt with 256 colour support and many other patches included etc. Do a list with the current packages that doesn't follow the arch way and i will take care of them. AFAIK the reason awesome was removed from community was that JGC removed the cairo backend from the package in extra AND the awesome maintainer didnt want to maintain a cairo-xcb package himself. If he did awesome would still be in community... He respected the decision and trusted Jan because we are a team and we have to work together to accomplish a goal. I would encourage him to not be bullied out of maintaining things that he would like to maintain in community. As long as they are not really creating more work for anyone than himself, they should be fine.
Re: [aur-general] TU Application - Seblu
On Sat, Jan 22, 2011 at 12:13 PM, Loui Chang louipc@gmail.com wrote: On Fri 21 Jan 2011 21:38 +0200, Ionuț Bîru wrote: On 01/21/2011 09:10 PM, Grigorios Bouzakis wrote: Seblu wrote: It looks like a trick question! But if I want to be a good maintainer, I do understand the reasons. and **The trust does not exclude the audit.** Excuse me for asking but is there anything preventing you from moving cairo-xcb to community if you become a TU? Yes, us. As far as i know if you become a TU you can maintain anything you want that has more than 10 votes in the AUR. Becoming a TU means that you become a member in the developement team, a team in which we trust each other, respect each other decisions, use the same packaging standards, the same tools as developers etc. I think if the package meets the guidelines then you shouldn't bully someone into not maintaining it. As long as he's providing the support that should suffice. Sometimes we may need to adjust the guidelines, and we decide this as a group through a formal vote. Seriously? Since when is adding a package that is already in the repos with a different configure flag a good idea? We don't even allow this in the AUR... Ronald
Re: [aur-general] TU Application - Seblu
On Sat 22 Jan 2011 19:03 +0100, Ronald van Haren wrote: On Sat, Jan 22, 2011 at 12:13 PM, Loui Chang louipc@gmail.com wrote: On Fri 21 Jan 2011 21:38 +0200, Ionuț Bîru wrote: On 01/21/2011 09:10 PM, Grigorios Bouzakis wrote: Seblu wrote: It looks like a trick question! But if I want to be a good maintainer, I do understand the reasons. and **The trust does not exclude the audit.** Excuse me for asking but is there anything preventing you from moving cairo-xcb to community if you become a TU? Yes, us. As far as i know if you become a TU you can maintain anything you want that has more than 10 votes in the AUR. Becoming a TU means that you become a member in the developement team, a team in which we trust each other, respect each other decisions, use the same packaging standards, the same tools as developers etc. I think if the package meets the guidelines then you shouldn't bully someone into not maintaining it. As long as he's providing the support that should suffice. Sometimes we may need to adjust the guidelines, and we decide this as a group through a formal vote. Seriously? Since when is adding a package that is already in the repos with a different configure flag a good idea? We don't even allow this in the AUR... Seriously. While it's not ideal, it has been done. I would consider it the same as including bin/lib32 packages just to include things like wine or whatever. The [community] repo is intended for this kind of experimentation and freedom. I think awesomewm has enough of a user base to justify such measures if a TU is willing to maintain it. I'm starting to get a bit peeved with people confusing [community] and [unsupported] with the [core] and [extra] bits.
Re: [aur-general] TU Application - Seblu
that means that you don't trust the arch maintainer judgment? /snip But if I want to be a good maintainer, I do understand the reasons. and **The trust does not exclude the audit.** +1 Everyone can make mistakes, even Arch packagers. Ffs, Allan's a core dev :P More shocking news at 11. Excuse me for asking but is there anything preventing you from moving cairo-xcb to community if you become a TU? Yes, us. Who's us? As far as i know if you become a TU you can maintain anything you want that has more than 10 votes in the AUR. Becoming a TU means that you become a member in the developement team, a team in which we trust each other, respect each other decisions, use the same packaging standards, the same tools as developers etc. I think if the package meets the guidelines then you shouldn't bully someone into not maintaining it. As long as he's providing the support that should suffice. Sometimes we may need to adjust the guidelines, and we decide this as a group through a formal vote. +1 for discussion and voting, -1 for because I said so, noob. Seriously? Since when is adding a package that is already in the repos with a different configure flag a good idea? We don't even allow this in the AUR... I think there's been a misunderstanding. The package would have a different name via the suffix to indicate the option, which is permissible in both [community] and the AUR. Seriously. While it's not ideal, it has been done. I would consider it the same as including bin/lib32 packages just to include things like wine or whatever. The [community] repo is intended for this kind of experimentation and freedom. I think awesomewm has enough of a user base to justify such measures if a TU is willing to maintain it. I mostly agree. The Arch ideal is to include the most vanilla package possible and let users compile their own custom packages if they need or want them, but if there is a considerable demand for non-vanilla build options then I see no reason not to either change the vanilla package or include a clearly labelled alternative package. As already stated, this has been done before and it isn't a big deal at all. I'm starting to get a bit peeved with people confusing [community] and [unsupported] with the [core] and [extra] bits. Well, now that [community] is official, the line between it and [extra] is slowly being blurred, maybe even erased, so there's not much reason to be peeved about the confusion. I really don't see much difference in the types of packages included in either. I suspect that some devs treat [extra] as though it were [community] and that there is no strict policy in place to determine what belongs there and what belongs in [community].
[aur-general] deletion request ffmpeg-svn
Hi :) I would like ffmpeg-svn to be deleted because it's out-of-date and the ffmpeg svn repository won't receive any more updates by reason of the ffmpeg project switching to git. So it would be kind of misleading to have two development packages in aur and one of them frozen. thanks raubkopierer
Re: [aur-general] deletion request ffmpeg-svn
On 22.01.2011 22:39, Christian Scharkus wrote: Hi :) I would like ffmpeg-svn to be deleted because it's out-of-date and the ffmpeg svn repository won't receive any more updates by reason of the ffmpeg project switching to git. So it would be kind of misleading to have two development packages in aur and one of them frozen. thanks raubkopierer Done. thx Next time please include a link -- Florian Pritz -- {flo,bluewind}@server-speed.net signature.asc Description: OpenPGP digital signature
[aur-general] Please orphan python-wtforms
Dear TUs, can someone please orphan python-wtforms [1]? The PKGBUILD is heavily outdated, it hasn't been modified for over a year and doesn't even build anymore. Another user (FSX) said in the comments that he has emailed the current package maintainer (welterde) a while back but never got a reply. Thank you very much! Felix [1] http://aur.archlinux.org/packages.php?ID=26120
Re: [aur-general] Please orphan python-wtforms
done On Sat, Jan 22, 2011 at 6:04 PM, Felix Kaiser felix.kai...@fxkr.net wrote: Dear TUs, can someone please orphan python-wtforms [1]? The PKGBUILD is heavily outdated, it hasn't been modified for over a year and doesn't even build anymore. Another user (FSX) said in the comments that he has emailed the current package maintainer (welterde) a while back but never got a reply. Thank you very much! Felix [1] http://aur.archlinux.org/packages.php?ID=26120