Re: [aur-general] AUR - 'kernel26' search results

[Peter Lewis]

On Tuesday 21 September 2010 at 01:50 Ng Oon-Ee wrote:
> On Tue, 2010-09-21 at 02:22 +0200, Ulf Winkelvos wrote:
> 
> 
> > all requests are send to the mailing list. So TUs still have full
> > control, but ist pretty handy for users that are not on the ml.
> 
> If they're not on the ML, a mechanism should be added for reporters to
> give reasons why packages should be disowned or removed. For some cases
> discussion will also be done here on the ML, would the reporter than not
> be part of the discussion?

I agree with this too am working towards implementing it.

Since there are only certain given reasons for the deletion of a package (no 
sources available, no longer builds on current systems, duplicated elsewhere, 
source control system changed etc.) these could be check boxes to prompt the 
person proposing the deletion to think about these issues before clicking the 
button. There should also be a text field with which to elaborate.

If all this is then sent to the mailing list automatically in a standard 
email, then it makes it very clear why the deleltion is being requested, by 
whom, the name of the package and a link to it. This can also alert the 
current maintainer (say in a cc). A discussion can then follow on the list in 
the usual way before a TU makes the final decision.

I think this is likely to actually increase the signal to noise ratio in 
deletion request emails, since it will make the proposer think and be more 
likely to provide the needed information straight away.

Cheers,

Pete.

PS. I agree with Heiko though that these issues (including orphaning and 
duplicate flagging are not democratic issues, they're just about establishing 
fact. Voting isn't needed.)

Re: [aur-general] AUR - 'kernel26' search results

[Xyne]

/snip

I've always thought that there should be a TU dashboard for the AUR. It would
collect all requests in a single area with regular formatting. Nothing would
ever get lost in the list and users wouldn't need to sign up to it. Each
request could have it's own comments page (using the existing comments backend)
for discussion if necessary.

Building on this idea, the package page could include a button named "notify
maintainer". This would link to a form that allows a user to send a message to
the maintainer, e.g. "please add x86_64" to the PKGBUILD. If the package isn't
updated in e.g. 2 weeks, the "notify maintainer" button would be replaced by a
"request adoption" button.

Clicking on it would send a message to the dashboard, along with the previous
message sent to the maintainer (including dates etc). Any TU could then review
the message, the time that it was sent, and who sent it before deciding to
orphan the package, with the bonus of the package being automatically adopted
by whoever requested it.

Deletion requests would go directly to the dashboard. This could be a simple
form with a text field for the reason, e.g. "duplicate of foo", "no longer
builds", "project moved to git", etc.


Of course, in the absence of a dashboard, sending formatted messages to this
list automatically would work too. In that case, maybe the submitter could be
automatically signed up to the list (after a confirmation prompt while
submitting).



> > Another thing: Multiple maintainers would be realy nice... although
> > anybody should put more thought into that, as it could easily become
> > pretty messy.
> Can be nice. But a second maintainer may only be added by the first
> maintainer. Otherwise this can easily be abused by those impatient
> people. See above. In case of packages on which are working to people
> together who are in contact with each other regarding this package this
> could make it a bit easier. But in such a case only the maintainer of
> the package may add the second maintainer.

Maintainer groups would be really useful. Arch-Haskell would benefit from this.
Currently the "arch-haskell" account is just Don and when he's busy none of the
thousand+ Haskell packages can be updated. This has come up on the arch-haskell
mailing list and he was working on a solution, but I haven't heard anything
more about it.

I have a few ideas of how that could be implemented on the backend, but it
would just be another bikeshed discussion detracting from the one above. :P

Re: [aur-general] AUR - 'kernel26' search results

[Jonathan Conder]

 On 22/09/10 00:23, Xyne wrote:

Building on this idea, the package page could include a button named "notify
maintainer". This would link to a form that allows a user to send a message to
the maintainer, e.g. "please add x86_64" to the PKGBUILD. If the package isn't
updated in e.g. 2 weeks, the "notify maintainer" button would be replaced by a
"request adoption" button.

It would be nice to have something like this, like what we have on the 
forums, rather than having a plaintext email address exposed on the 
account.php page. If the user really wants to email the maintainer 
directly they could just look at a PKGBUILD.


On an unrelated note, does anyone else have problems with the MIME types 
on the AUR server? This is the header I get when downloading a tarball:


HTTP/1.1 200 OK
Content-Type: application/x-tgz
Accept-Ranges: bytes
ETag: "2582334637"
Last-Modified: Sat, 31 Oct 2009 01:58:19 GMT
Content-Length: 425
Date: Fri, 10 Sep 2010 10:52:28 GMT
Server: lighttpd/1.4.28

The MIME type for gzipped tarballs on my system is 
application/x-compressed-tar. It's kinda annoying because Firefox gets 
confused and decides it can't open the tarball. I might try to fix it 
myself at some later stage, but I'm really snowed under at the moment.


Jonathan

Re: [aur-general] Move network-ups-tools to AUR

[Thorsten Töpper]

Moved the package to AUR: http://aur.archlinux.org/packages.php?ID=5379

-- 
Jabber: atsut...@freethoughts.de Blog: http://atsutane.freethoughts.de/
Key: 295AFBF4 FP: 39F8 80E5 0E49 A4D1 1341 E8F9 39E4 F17F 295A FBF4


signature.asc
Description: PGP signature

[aur-general] everyone welcome our newest TU: Peter Lewis!

[Christopher Brannon]

Votes:
yes 19
no 1
abstain 1
Quorum was reached, and the application was accepted.

Peter, please read the following document:
.
It contains a list of tasks which every new TU must complete.
If you have not already done so, familiarize yourself with our bylaws:
.
Also, I have changed the status of your account on the AUR.

Welcome to the team!

-- Chris


pgpbzAexvUFoT.pgp
Description: PGP signature

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Ángel Velásquez]

2010/9/21 Christopher Brannon 

> Votes:
> yes 19
> no 1
> abstain 1
> Quorum was reached, and the application was accepted.
>
> Peter, please read the following document:
> .
> It contains a list of tasks which every new TU must complete.
> If you have not already done so, familiarize yourself with our bylaws:
> .
> Also, I have changed the status of your account on the AUR.
>
> Welcome to the team!
>
> -- Chris
>


Congratulations peter!


-- 
Angel Velásquez
angvp @ irc.freenode.net
Arch Linux Developer / Trusted User
Linux Counter: #359909
http://www.angvp.com

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Thorsten Töpper]

On Tue, 21 Sep 2010 16:34:22 -0300
Ángel Velásquez  wrote:
> 2010/9/21 Christopher Brannon 
- snip -
> > Welcome to the team!
> >
> > -- Chris
>
> Congratulations peter! 

Congratulations :-)

-- 
Jabber: atsut...@freethoughts.de Blog: http://atsutane.freethoughts.de/
Key: 295AFBF4 FP: 39F8 80E5 0E49 A4D1 1341 E8F9 39E4 F17F 295A FBF4


signature.asc
Description: PGP signature

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Sven-Hendrik Haase]

 On 21.09.2010 21:49, Thorsten Töpper wrote:
> On Tue, 21 Sep 2010 16:34:22 -0300
> Ángel Velásquez  wrote:
>> 2010/9/21 Christopher Brannon 
> - snip -
>>> Welcome to the team!
>>>
>>> -- Chris
>> Congratulations peter! 
> Congratulations :-)
>
Welcome to the world of tomorrow! Behold! Your destiny awaits!

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Brad Fanella]

On Sep 21, 2010, at 2:35 PM, Christopher Brannon  
 wrote:



Votes:
yes 19
no 1
abstain 1
Quorum was reached, and the application was accepted.

Peter, please read the following document:
.
It contains a list of tasks which every new TU must complete.
If you have not already done so, familiarize yourself with our bylaws:
.
Also, I have changed the status of your account on the AUR.

Welcome to the team!

-- Chris


Congratulations and welcome to the team! :-)

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Peter Lewis]

On Tuesday 21 September 2010 at 22:01 Sven-Hendrik Haase wrote:
> Thorsten Töpper wrote:
> > Ángel Velásquez  wrote:
> > > Christopher Brannon 
> > >
> > > Welcome to the team!
> > > 
> >> Congratulations peter!
> > 
> > Congratulations :-)
> 
> Welcome to the world of tomorrow! Behold! Your destiny awaits!

Woo hoo! Thanks everyone!

Pete.

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Florian Pritz]

On 21.09.2010 21:35, Christopher Brannon wrote:
> Welcome to the team!

Congratulations :)

-- 
Florian Pritz -- {flo,bluewi...@server-speed.net



signature.asc
Description: OpenPGP digital signature

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Laurent Carlier]

Le mardi 21 septembre 2010 21:35:01, Christopher Brannon a écrit :
> Votes:
> yes 19
> no 1
> abstain 1
> Quorum was reached, and the application was accepted.
> 
> Peter, please read the following document:
> .
> It contains a list of tasks which every new TU must complete.
> If you have not already done so, familiarize yourself with our bylaws:
> .
> Also, I have changed the status of your account on the AUR.
> 
> Welcome to the team!
> 
> -- Chris

Welcome! \o/

Laurent Carlier

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Thomas Dziedzic]

On Tue, Sep 21, 2010 at 4:38 PM, Laurent Carlier  wrote:
> Le mardi 21 septembre 2010 21:35:01, Christopher Brannon a écrit :
>> Votes:
>> yes 19
>> no 1
>> abstain 1
>> Quorum was reached, and the application was accepted.
>>
>> Peter, please read the following document:
>> .
>> It contains a list of tasks which every new TU must complete.
>> If you have not already done so, familiarize yourself with our bylaws:
>> .
>> Also, I have changed the status of your account on the AUR.
>>
>> Welcome to the team!
>>
>> -- Chris
>
> Welcome! \o/
>
> Laurent Carlier
>

Welcome!

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Jan Steffens]

On Tue, Sep 21, 2010 at 11:07 PM, Peter Lewis  wrote:
> Woo hoo! Thanks everyone!

Welcome! :-)

Re: [aur-general] everyone welcome our newest TU: Peter Lewis!

[Jonathan Conder]

 On 22/09/10 07:35, Christopher Brannon wrote:

Votes:
yes 19
no 1
abstain 1
Quorum was reached, and the application was accepted.

Peter, please read the following document:
.
It contains a list of tasks which every new TU must complete.
If you have not already done so, familiarize yourself with our bylaws:
.
Also, I have changed the status of your account on the AUR.

Welcome to the team!

-- Chris

Well done and welcome!

Re: [aur-general] Mime Types

[Loui Chang]

On Wed 22 Sep 2010 01:20 +1200, Jonathan Conder wrote:
>  On 22/09/10 00:23, Xyne wrote:
> >Building on this idea, the package page could include a button named
> >"notify maintainer". This would link to a form that allows a user to
> >send a message to the maintainer, e.g. "please add x86_64" to the
> >PKGBUILD. If the package isn't updated in e.g. 2 weeks, the "notify
> >maintainer" button would be replaced by a "request adoption" button.
> >
> It would be nice to have something like this, like what we have on
> the forums, rather than having a plaintext email address exposed on
> the account.php page. If the user really wants to email the
> maintainer directly they could just look at a PKGBUILD.
> 
> On an unrelated note, does anyone else have problems with the MIME
> types on the AUR server? This is the header I get when downloading a
> tarball:
> 
> HTTP/1.1 200 OK
> Content-Type: application/x-tgz
> Accept-Ranges: bytes
> ETag: "2582334637"
> Last-Modified: Sat, 31 Oct 2009 01:58:19 GMT
> Content-Length: 425
> Date: Fri, 10 Sep 2010 10:52:28 GMT
> Server: lighttpd/1.4.28
> 
> The MIME type for gzipped tarballs on my system is
> application/x-compressed-tar. It's kinda annoying because Firefox
> gets confused and decides it can't open the tarball. I might try to
> fix it myself at some later stage, but I'm really snowed under at
> the moment.

Interesting. Where is that set on your system?

This whole mime type thing is a bit of a mess eh?
I guess it's kind of hard to rely on non-standard mime types.
Is there some kind of auxiliary non IETF standard?

You can find the mime types that Firefox uses in:
/home//.mozilla/firefox//mimeTypes.rdf

Cheers.