How about something like the Ubuntu "popularity contest"? With that,
you can opt-in to share the packages you've got on your system
presumably to let the package maintainers know where to focus their
energy.
To me, the ideal setup would be a config option which had tiered options:
[ ] Check for updates
[ ] Submit OS info when checking for updates
An additional nice-ity would be setting the frequency of checking - on
open, weekly, monthly...
I've got a menu item on the Live CD which allows users to pull the
latest from SVN - but its on demand so call it opt-in. I think its a
nice bonus for users who care to have the latest, greatest version.
I've been contemplating adding another option to revert one version back
just in case an update adds a bug you can't live with. Maybe that's
something else to consider.
-- Matt Tesauro
OWASP Live CD Project Lead
http://www.owasp.org/index.php/Category:OWASP_Live_CD_Project
http://mtesauro.com/livecd/ - Documentation Wiki
Robert McCurdy wrote:
> Meh... really if you run somebodies code its really all bets off...
>
> '
> Forward responsibly please use BCC ! (Blind Carbon Copy) and check to see if
> your fwd: is a hoax before you send it !
> http://www.hoax-slayer.com/forward-responsibly.html
> '
>
> PLEASE DO NOT ADD THIS MAIL TO ANY AUTOMATED OR FORUM MAIL
> NO ECARDS OR INVITES PLEASE
>
> =================
> Robert McCurdy
> Network / Systems Consultant
> http://rmccurdy.com
> [email protected]
> 770.540.6402
> =================
>
>
> --- On Mon, 1/12/09, John Doesnot <[email protected]> wrote:
>
>> From: John Doesnot <[email protected]>
>> Subject: Re: [W3af-users] Check if a new version is available
>> To: "Andres Riancho" <[email protected]>
>> Cc: "[email protected]" <[email protected]>
>> Date: Monday, January 12, 2009, 9:41 PM
>>> Because I know some of you are a little paranoid
>> about me logging
>>> your IP addresses, I'll also create a --no-ckeck
>> flag that you could
>>> use to disable this check.
>> It should be opt-in if anything... disabled by default, or
>> at least
>> have a GIANT warning.
>> Disabling it should be controlled by a user file to avoid
>> it being
>> enabled again on update.
>>
>>> With this information, I'll be able to focus on
>> the most important
>>> platform (which I suspect is linux, but sometimes
>> guessing is not
>>> enough), and I could delegate the ports to other
>> platforms to other
>>> developers. The question is... would this bother you?
>> Yes, and I think I speak for all of those too paranoid to
>> join the list as well.
>>
>> --
>> http://www.nukeit.org
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> W3af-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/w3af-users
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> W3af-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/w3af-users
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
W3af-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/w3af-users
