[gentoo-dev] Re: [RFD] Adopt-a-package, proxy-maintenance, and other musings

2016-01-24 Thread Michael Palimaka
On 01/25/2016 02:50 AM, Göktürk Yüksek wrote:
> Ian Delaney:
> 
>> 5. At the risk of sounding like Patrick, gentoo lacks some forms
>> of documentation pertaining to established proxy maintainers and to
>> forms of stats analysis. In discussions, points were raised
>> regarding the gathering of stats data re packages' tally of
>> downloads and instances of emerging into a gentoo system. Most of
>> the desired stats appear to lack any form of tools available to
>> gather and report data that would prove helpful in evaluating
>> packages of either the m-w or m-n lists.
> 
>> The topic of recruitment and recruiting are tied, but imo, quite 
>> disparate.
> 
> 
> I don't want to go off-topic here too much but this is more than a
> missing tools issue. There are privacy concerns regarding the
> collection of such information. I recall this proposed idea from
> Google Summer of Code:
> 
> https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2012/Ideas#Package_statistics_reporting_tool
> 

This was implemented but never deployed. Data collection would always be
optional and off by default. There was even a nice configuration file to
select exactly which information is and is not sent.





Re: [gentoo-dev] Re: [RFD] Adopt-a-package, proxy-maintenance, and other musings

2016-01-23 Thread Ian Delaney
On Tue, 19 Jan 2016 22:02:21 -0500
Göktürk Yüksek  wrote:

> Duncan:
> > NP-Hardass posted on Tue, 19 Jan 2016 00:44:49 -0500 as excerpted:
> >   
>  [...]  
> > 
> > That gave me the idea of a maintainer-needed eclass.  When packages
> > are set to maintainer-needed, they can simply inherit this eclass
> > and add whatever function to the pkg_postinst, that will add a
> > message that will in effect say "adopt-me please", probably
> > printing a proxy-maintainer invitation URL to go to for more
> > information.
> > 
> > Talking about pkg_postinst messages, unless I missed it there's no
> > simple way to add a one ATM, without coding up the whole function,
> > making it problematic for eclasses, etc.  For EAPI-7, what about
> > either a helper function that can be called, or an array variable
> > that can be simply added to, that simply adds the supplied message
> > to a list of messages printed at pkg_postinst time, and of course
> > an appropriate default_pkg_postinst to go along with it?  Then
> > ebuilds and eclasses can call this helper or set this var in
> > whatever phase they need to, and the message will be printed at
> > pkg_postinst time without having to worry about setting up your own
> > pkg_postinst or stepping on anything pkg_postinst related setup
> > elsewhere. 
> See:
> sys-apps/portage: show an elog message when merged package is
> maintained by maintainer-needed
> https://bugs.gentoo.org/show_bug.cgi?id=398633
> 
> Can we reconsider implementing this idea perhaps?
> 

Given the thrust of this whole discussion this is a good idea. It
naturally advertises packages of this unmaintained status to users as
they emerge.

> --
> gokturk
> 
> 



-- 
kind regards

Ian Delaney



Re: [gentoo-dev] Re: [RFD] Adopt-a-package, proxy-maintenance, and other musings

2016-01-23 Thread Andrew Savchenko
On Sat, 23 Jan 2016 21:04:56 +0800 Ian Delaney wrote:
> On Tue, 19 Jan 2016 22:02:21 -0500
> Göktürk Yüksek  wrote:
> 
> > Duncan:
> > > NP-Hardass posted on Tue, 19 Jan 2016 00:44:49 -0500 as excerpted:
> > >   
> >  [...]  
> > > 
> > > That gave me the idea of a maintainer-needed eclass.  When packages
> > > are set to maintainer-needed, they can simply inherit this eclass
> > > and add whatever function to the pkg_postinst, that will add a
> > > message that will in effect say "adopt-me please", probably
> > > printing a proxy-maintainer invitation URL to go to for more
> > > information.
> > > 
> > > Talking about pkg_postinst messages, unless I missed it there's no
> > > simple way to add a one ATM, without coding up the whole function,
> > > making it problematic for eclasses, etc.  For EAPI-7, what about
> > > either a helper function that can be called, or an array variable
> > > that can be simply added to, that simply adds the supplied message
> > > to a list of messages printed at pkg_postinst time, and of course
> > > an appropriate default_pkg_postinst to go along with it?  Then
> > > ebuilds and eclasses can call this helper or set this var in
> > > whatever phase they need to, and the message will be printed at
> > > pkg_postinst time without having to worry about setting up your own
> > > pkg_postinst or stepping on anything pkg_postinst related setup
> > > elsewhere. 
> > See:
> > sys-apps/portage: show an elog message when merged package is
> > maintained by maintainer-needed
> > https://bugs.gentoo.org/show_bug.cgi?id=398633
> > 
> > Can we reconsider implementing this idea perhaps?
> > 
> 
> Given the thrust of this whole discussion this is a good idea. It
> naturally advertises packages of this unmaintained status to users as
> they emerge.
 
Please make this optional. Elog already contains too much
information and it is already hard to read logs after world update
or other massive change. It literally takes hours sometimes.

Best regards,
Andrew Savchenko


pgp4AnWCoIzR_.pgp
Description: PGP signature


Re: [gentoo-dev] Re: [RFD] Adopt-a-package, proxy-maintenance, and other musings

2016-01-23 Thread waltdnes
On Sat, Jan 23, 2016 at 10:54:01PM +0300, Andrew Savchenko wrote

> Please make this optional. Elog already contains too much information
> and it is already hard to read logs after world update or other
> massive change. It literally takes hours sometimes.

  Agreed 100%.  I filed a successfull bug request last month to remove
the "ewarn" about English word lists being dropped from default vim
install 2 years ago https://bugs.gentoo.org/show_bug.cgi?id=569056  The
last thing I want is more ewarns.

  A better policy may be to keyword them, e.g. ~amd64 ~x86, etc.  This
would be reasonable, because there is actually a valid reason to do so.
I.e. users would be using unmaintained software.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications



Re: [gentoo-dev] Re: [RFD] Adopt-a-package, proxy-maintenance, and other musings

2016-01-19 Thread Göktürk Yüksek
Duncan:
> NP-Hardass posted on Tue, 19 Jan 2016 00:44:49 -0500 as excerpted:
> 
>> "adopt-a-package" type program.  In functionality, this is no different
>> than proxy-maintenance, however, this codifies it into an explicit
>> policy whereby users are encouraged to step and take over a package. 
>> This obviously requires a greater developer presence in the proxy-maint
>> project (or something similar),
>> but, personally, I think that a stronger dev presence in proxy-maint
>> would be better for Gentoo as a whole.
> 
> That gave me the idea of a maintainer-needed eclass.  When packages are 
> set to maintainer-needed, they can simply inherit this eclass and add 
> whatever function to the pkg_postinst, that will add a message that will 
> in effect say "adopt-me please", probably printing a proxy-maintainer 
> invitation URL to go to for more information.
> 
> Talking about pkg_postinst messages, unless I missed it there's no simple 
> way to add a one ATM, without coding up the whole function, making it 
> problematic for eclasses, etc.  For EAPI-7, what about either a helper 
> function that can be called, or an array variable that can be simply 
> added to, that simply adds the supplied message to a list of messages 
> printed at pkg_postinst time, and of course an appropriate 
> default_pkg_postinst to go along with it?  Then ebuilds and eclasses can 
> call this helper or set this var in whatever phase they need to, and the 
> message will be printed at pkg_postinst time without having to worry 
> about setting up your own pkg_postinst or stepping on anything 
> pkg_postinst related setup elsewhere.
> 
See:
sys-apps/portage: show an elog message when merged package is maintained
by maintainer-needed
https://bugs.gentoo.org/show_bug.cgi?id=398633

Can we reconsider implementing this idea perhaps?

--
gokturk




[gentoo-dev] Re: [RFD] Adopt-a-package, proxy-maintenance, and other musings

2016-01-18 Thread Duncan
NP-Hardass posted on Tue, 19 Jan 2016 00:44:49 -0500 as excerpted:

> "adopt-a-package" type program.  In functionality, this is no different
> than proxy-maintenance, however, this codifies it into an explicit
> policy whereby users are encouraged to step and take over a package. 
> This obviously requires a greater developer presence in the proxy-maint
> project (or something similar),
> but, personally, I think that a stronger dev presence in proxy-maint
> would be better for Gentoo as a whole.

That gave me the idea of a maintainer-needed eclass.  When packages are 
set to maintainer-needed, they can simply inherit this eclass and add 
whatever function to the pkg_postinst, that will add a message that will 
in effect say "adopt-me please", probably printing a proxy-maintainer 
invitation URL to go to for more information.

Talking about pkg_postinst messages, unless I missed it there's no simple 
way to add a one ATM, without coding up the whole function, making it 
problematic for eclasses, etc.  For EAPI-7, what about either a helper 
function that can be called, or an array variable that can be simply 
added to, that simply adds the supplied message to a list of messages 
printed at pkg_postinst time, and of course an appropriate 
default_pkg_postinst to go along with it?  Then ebuilds and eclasses can 
call this helper or set this var in whatever phase they need to, and the 
message will be printed at pkg_postinst time without having to worry 
about setting up your own pkg_postinst or stepping on anything 
pkg_postinst related setup elsewhere.

-- 
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