Re: [gentoo-dev] List of User projects

[Alistair Bush]

>
> diffball (the basis of y'alls delta compression for tarball
> snapshots, progenitor of tarsync used by emerge-*webrsync, etc).
>

Thank you Brian for that pkg, its appreciated.  My apologies if the rest is a 
little less kind.

> > ps.  I would like the packages to be specifically for gentoo,  but there
> > are exceptions to this.  as an example openrc (and even paludis to a
> > degree).  If you think that there is a package not specifically
> > targetting gentoo that deserves a mention please make it clear why.
>
> I'm a bit torn by this proposal; on the one hand, a shout out is nice-
> from a career angle it certainly would've been useful for getting
> some attention/exposure when I first was starting out.
>

Not really my aim.  Im not planning on listing ppl,  just there work.  Might 
not even put a url pointing to it.

> That said, it has some issues with it:
>
> * it'll wind up being a fairly subjective list leading to some
> debates nobody really wants to be involved in (nice euphemism for
> flamewars).

Well I suppose it would be my project,  therefore I would make the call.  ppl 
can flame all they like really.  Personally I don't find them a very good way to 
communicate,  would probably miss what they were flaming about anyway.

> *) the criteria seems to be external projects that are gentoo
> specific, aparently by non-devs/ex-devs.  This raises some questions
> as to what happens for when it's created by a dev externally (pkgcore
> went external a long while before I became an exdev), and what
> happens when the author becomes a dev (I'll be getting my gentoo-x86
> +w back soon enough).

Firstly that is very good news.

Currently I am taking this from Mon, 29 March 19:42 NZ DST.   So pkgcore is 
external,  and you are a community member so your in the list.   I don't want 
to bring a whole pile of history into it.   Will pkgcore have its own gentoo 
project,  or be considered as part of a gentoo project?  Im guessing not 
anyway.

I'm quite happy to consider the corner cases,  and will probably include a 
vast majority of them.  Initially I don't even believe I will have a fully 
complete list of all the projects the fit nicely into my criteria.  Thats why 
you have one of those nice statements that says.

"While we have attempted to list all package/projects etc we are sure we have 
missed some,  please contact ......  if you believe we have missed something 
blah de blah blah"

> *) PMS was started outside of gentoo, and maintained outside gentoo
> for a long while.  Now it's a gentoo project.  A shout out there
> would've been warranted (spec work isn't exactly sexy, regardless of
> any extra baggage that came w/ PMS), but at what point does it
> suddenly fall off this list?

Isn't this a bit too bikesheddy.  If someone, from now, were to create a 
project and then have it added to the list before they become a dev then good 
on them.  The project would not be removed.  Even if it died.  In fact the 
list would never be cleaned.  It may be updated to represent the state of the 
project,  but that project would be there for as long as the page was. (and 
probably longer the way ppl index the interwebs).

> *) kind of the packagekit connundrum- at least for pkgcore/paludis,
> they were written to support multiple distros/formats internally.  Yes
> they've got traction w/in gentoo, but at what point is it no longer a
> gentoo specific thing, and more of a "it gained it's first traction in
> gentoo" ?  Openrc I'd argue is in the same boat- yes it can be used
> elsewhere, but right now we're the owns extracting the most benefit
> from it.

Well I would suggest that a major part of the functionality of both those 
pkg's are directed towards supporting gentoo.   Even if both supported 5-10 
completely different distro's that did not resemble gentoo in the slightest I 
would still put them on the list.  Compare this with kmyfirewall that had a 
single dialog that allowed to be set "gentoo specfic" executable paths which 
would not be on the list.

> *) it slights the tools that started w/in gentoo's vcs; consider
> scanelf .  Very useful tool deserving some credit, but it would be
> exempted under these rules.

Life ain't always perfect.   And that goes both ways.   This isn't a list to 
thank developers for their effort,  make another thread if you want that.

It also doesn't slight that project in the slightest.

>
> Instead, if the purpose is a "thanks", why not every once in a while
> put up a news item discussing the tools in question?  Such an
> approach allows folk to focus in on whatever is useful/interesting
> (regardless of origination) and give the same 'thanks' angle and
> public exposure for the author in question.

Well I was considering this as well.   But first before we do this we would 
need to actually know what packages there are.  Therefore this thread.  Unless 
we do all packages from aaaaa to zzzzz.


- Alistair

ps. I must say that its a little sad that so far there has been much more 
effort put into nitpicking than actually populating the list (working towards 
the goal).  Which sums up gentoo pretty much.  So lets highlight this part a 
little more

> > If you think that there is a package not specifically
> > targetting gentoo that deserves a mention please make it clear why.

And lets add on "If you think a package should be mentioned for other reasons 
please make it clear why, as well"