Re: [gentoo-dev] Re: Gentoostats, SoC 2011
On 04/27/2012 06:34 PM, Nikos Chantziaras wrote: > On 23/08/11 00:20, Vikraman wrote: >> Hi all, >> >> Gentoostats[0] is a GSoC 2011 project to collect package statistics >> from gentoo >> machines. Please check it out. Bug reports and feature suggestions are >> welcome. >> >> To submit your stats, use the app-portage/gentoostats ebuild from >> betagarden >> overlay[1]. >> >> [0] https://soc.dev.gentoo.org/gentoostats/ >> [1] https://soc.dev.gentoo.org/gentoostats/about > > Is this project dead now? > > Hi, The project is not dead. As part of GSoC 2012 I will be working on improving gentoostats. I'll post an official announcement here in the very near future. If you have any questions and/or ideas about the project please don't hesitate to get in touch with me. Regards, G. Gaydarov
Re: [gentoo-dev] Re: Gentoostats, SoC 2011
On Fri, Apr 27, 2012 at 10:34 AM, Nikos Chantziaras wrote: > On 23/08/11 00:20, Vikraman wrote: >> >> Hi all, >> >> Gentoostats[0] is a GSoC 2011 project to collect package statistics from >> gentoo >> machines. Please check it out. Bug reports and feature suggestions are >> welcome. >> >> To submit your stats, use the app-portage/gentoostats ebuild from >> betagarden >> overlay[1]. >> >> [0] https://soc.dev.gentoo.org/gentoostats/ >> [1] https://soc.dev.gentoo.org/gentoostats/about > > > Is this project dead now? > > A trivial look at the git repo would indicate no it is not dead. -A
[gentoo-dev] Re: Gentoostats, SoC 2011
On 23/08/11 00:20, Vikraman wrote: Hi all, Gentoostats[0] is a GSoC 2011 project to collect package statistics from gentoo machines. Please check it out. Bug reports and feature suggestions are welcome. To submit your stats, use the app-portage/gentoostats ebuild from betagarden overlay[1]. [0] https://soc.dev.gentoo.org/gentoostats/ [1] https://soc.dev.gentoo.org/gentoostats/about Is this project dead now?
Re: [gentoo-dev] Re: Gentoostats, SoC 2011
On 25-08-2011 22:15:22 +0800, Patrick Nagel wrote: > The prompt should offer three options: > > [s]end the data directly > s[h]ow me the data* > s[k]ip > > You can disable this prompt by having either 'SEND_STATS="yes"' (to always > send) or 'SEND_STATS="no" (to never send) in your /etc/make.conf. > > *) And in the next step, after showing the data set(s): Send? [y/n] > > (why do all those words have to start with an 's'??) send display/view later :) -- Fabian Groffen Gentoo on a different level
Re: [gentoo-dev] Re: Gentoostats, SoC 2011
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 2011-08-25 20:43, Markos Chandras wrote:
> On 25/08/2011 11:42 ??, Nikos Chantziaras wrote:
>> On 08/24/2011 01:48 PM, Patrick Lauer wrote:
>>> [...] If you sneakily add something to cron.daily by default you can
>>> get pretty nice coverage. But I guess anyone trying that in
>>> Gentooland will meet some rather unpleasant resistance :)
>
>> emerge always asks me after a world update whether I want to "auto
>> clean packages" with a yes/no prompt. I wouldn't be bad if once a
>> month or whatever it would ask me whether I want to upload my stats.
>> Gentoostats should probably become a runtime dep of Portage itself by
>> default, but not used automatically.
>
> I like your idea and people seem to like making things complicated.
> Simple solution:
>
> opt-in
>
> How: Display a warning after an emerge -u{DNav} world. Let user disable
> this warning by using a special variable in make.conf
>
> STATS_ENABLE="no".
>
> By default, this variable will be "yes" on base/ profiles
That sounds perfect to me.
The prompt should offer three options:
[s]end the data directly
s[h]ow me the data*
s[k]ip
You can disable this prompt by having either 'SEND_STATS="yes"' (to always
send) or 'SEND_STATS="no" (to never send) in your /etc/make.conf.
*) And in the next step, after showing the data set(s): Send? [y/n]
(why do all those words have to start with an 's'??)
Cheers,
Patrick.
- --
Key ID: 0x86E346D4http://patrick-nagel.net/key.asc
Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk5WWPoACgkQyYHmhobjRtSwewCgyJzgsLLvjfZpX5vg8XcxkNMb
tg8AoIkHz1z6b9DxTrnJxe3YyTDMOYsr
=ZKYx
-END PGP SIGNATURE-
Re: [gentoo-dev] Re: Gentoostats, SoC 2011
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 25/08/2011 11:42 ??, Nikos Chantziaras wrote:
> On 08/24/2011 01:48 PM, Patrick Lauer wrote:
>> [...] If you sneakily add something to cron.daily by default you
>> can get pretty nice coverage. But I guess anyone trying that in
>> Gentooland will meet some rather unpleasant resistance :)
>
> emerge always asks me after a world update whether I want to "auto
> clean packages" with a yes/no prompt. I wouldn't be bad if once a
> month or whatever it would ask me whether I want to upload my
> stats. Gentoostats should probably become a runtime dep of Portage
> itself by default, but not used automatically.
>
>
I like your idea and people seem to like making things complicated.
Simple solution:
opt-in
How:
Display a warning after an emerge -u{DNav} world.
Let user disable this warning by using a special variable in make.conf
STATS_ENABLE="no".
By default, this variable will be "yes" on base/ profiles
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOVkNbAAoJEPqDWhW0r/LCWFEP+wSHLeGuqIGIV1OcHzlrgMJn
qBusQcvWb2SbP58G+3hndPUHWsnSIRDk2zws21wZH1DLaCr3Hyc5V9s8WM7HMWeX
WHgLVN71KDSmhREvz9fJWGA08rLJHa/Xs3XdNBUp5mMGsogPmwgEmNgSyfpKe6wC
nsBC6pk/R6kvAdlinyLp2uybBDI00GtiUSN3fyvvuoE3XMlVdyYLYTKTguVmJB4A
aR97bIR2otZlWTmSGMvr899vht35Mwoe0/UHDV2SJHtWk9zzIYzWHEW9mMUoWAAw
1/2bYAafE+rp0/MPTv0tJ8WtoB6NhpJBRZGa5MuQM0V8jQqbgweq1YBO4zO8VAO+
tn6/thWk+heSklzTR1Uom1F+pYMxJBY0nBQUQ6ppZLjOM43WTT5TmPkc/rYwEB3M
8FywLV+Mryax+nQesLkgMQLLKUSuQygy+4zxoCUHkY5DwB08C5dfYua/Y+nLbb0l
iCmCNpYSKUJF2cbHm6kDfOonsyfre//+JNvycxuz5J932XqFwkv7dM8ywSwP7Srw
FfWWspLfHxyoXSHlljwXj0UxfQcjNbg3MyUt8s0pSys9GlUzdSv1vx4xGgS8dtzA
zTSvTE1xO3fUzO1Au+KaSs0GC49BO7Gf1fWFdIhr8ZcJD82+jDaooompzPqFm0lB
XZQAVwslAMQbSaJAEfCY
=V+cS
-END PGP SIGNATURE-
[gentoo-dev] Re: Gentoostats, SoC 2011
On 08/24/2011 01:48 PM, Patrick Lauer wrote: [...] If you sneakily add something to cron.daily by default you can get pretty nice coverage. But I guess anyone trying that in Gentooland will meet some rather unpleasant resistance :) emerge always asks me after a world update whether I want to "auto clean packages" with a yes/no prompt. I wouldn't be bad if once a month or whatever it would ask me whether I want to upload my stats. Gentoostats should probably become a runtime dep of Portage itself by default, but not used automatically.
[gentoo-dev] Re: Gentoostats, SoC 2011
Rich Freeman posted on Wed, 24 Aug 2011 07:07:54 -0400 as excerpted: > On Wed, Aug 24, 2011 at 6:48 AM, Patrick Lauer > wrote: >> If you sneakily add something to cron.daily by default you can get >> pretty nice coverage. But I guess anyone trying that in Gentooland will >> meet some rather unpleasant resistance :) > > Well, we could always broadcast the news widely (lists, forums, > eselect news, and so on). > > I'd also make it controllable via use flag. Put the client and the > cron.daily file in a package, and then make that a use-dependency of > something everybody has (the profile if profiles support this (don't > think they do), and if not pick something that correlates well with > people who would benefit from this feature. > > Users can opt-out via use flag. > > You can also start out with it being opt-in (use flag off by default in > profiles), and then turn it on later (with notice/etc). > > The key is to not be sneaky about it. Agreed on the no-sneaky bit. The practical question is what to make it a USE flag of? Baselayout/ openrc? Portage? Personally, I'd start with a couple paragraphs in the handbook describing the package and why one really /does/ want it installed and setup but that Gentoo gives the user the option, as part of the installation section, presumably thrown in with choosing the cron and syslog daemons, etc. Then I'd do the PR thing as you mention, pointing out that it's in the handbook now, so new users will likely be installing it, and to avoid skewing the numbers toward the new installations, existing installations should consider it as well. Existing users aren't likely to want the focus to shift to packages only the noobs are likely to install, for instance. Setup a bit of a competition there, and I'd guess you're likely to get better buy-in from existing users. I'd leave the USE flag dependency out of it, at least initially. It could always be added later, if thought necessary. But I suspect that if it's presented well in the handbook, many new users will install it, and if that fact is pointed out to existing users in appropriate forum/list threads, etc, many existing users will as well, just to "keep up", statistically. Yet if it's a separate package that must be separately installed, there's no way people can say it wasn't their choice, as they might be able to if it's a USE flag they weren't paying attention to, particularly if that flag defaults on. Make it an active choice and people are far more likely to continue with it, too, than if they felt in any way that it was pushed on them, with little choice. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
