Re: [gentoo-dev] Suggestion: remove app-office/borg from portage.

2008-08-18 Thread John Brooks
I agree that packages shouldn't be removed or moved because they have no
active developer maintaining them - that is going to take the value of
portage down quite a lot. Outdated packages do too, but not in quite the
same way.

I like the idea of a list or mailing list of developers willing to help
update unmaintained packages, and if community submitted ebuilds were
encouraged a bit more, the job would be pretty simple. Most of the times
i've done version bumps myself have just involved changing the name and
fixing up patches. I definitely like the idea of encouraging proxy
maintainers, as I said before. Becoming a full developer is (from what i've
seen externally) quite difficult and requires a lot of dedicated time, but
the user community is much larger - and 100 people doing one ebuild each is
going to work better than one person doing 100 ebuilds.

As another interesting idea for encouraging proxy maintainence, once an
easier/more developed system exists for that (such as the mailing list
mentioned before), perhaps a notice should be added to unmaintained ebuilds
mentioning that it has no active maintainer, to warn users that a newer
version may be available (in which case they can file a bug, etc) and
encourage those with the time and skills to take up some of the work on
those ebuilds. I would be very willing to work on some ebuilds if it didn't
involve chasing a trail of vaguely relevant developers down until one pays
attention. :P

I would think that masking them due to a lack of maintainence should be used
only as a last resort - if a package is blocking other updates or is
extremely out of date (unsupported by upstream / everything else). But in
those situations, deleting might be a better idea anyway, because what
purpose does it really serve?

- John Brooks

On Mon, Aug 18, 2008 at 5:35 PM, Joe Peterson [EMAIL PROTECTED] wrote:

 Jeremy Olexa wrote:
  Also, devs willing to maintain
  packages but then later retiring and leaving the packages in limbo.
  Maybe there should be some policy such as, when devs retire if no one
  else steps up to maintain the package, then it automatically gets
  moved to sunrise overlay and only maintained packages stay in the
  portage tree.

 My opinion is that packages should not be removed from the tree just
 because
 there is no assigned maintainer.  Even moving a package to sunrise
 effectively
 makes it invisible to many users, and a great strength of Gentoo is that it
 has such a variety of packages in the tree.

 I do see that there are potential problems with unmaintained packages, so
 it
 is a good goal to try to solve that.  Perhaps developers who have the time
 and
 choose to make themselves available to do simple version bumps on
 unmaintained
 packages could put themselves on a mailing list to receive such bug
 reports.
 Encouraging users to be proxy maintainers is a great idea too (as others
 have
 suggested).  As a last resort, otherwise working packages could be masked
 as
 unmaintained, which is probably better than total removal (after all,
 they
 could still be useful to some users.

-Joe




Re: [gentoo-dev] Suggestion: remove app-office/borg from portage.

2008-08-16 Thread John Brooks
It can be somewhat difficult to find someone to look over and commit an
ebuild on an unmaintained package though - the several times i've done that
have involved tracking down developers with previous commits to the package
or who are active in the category and trying to find one who isn't retired
(I have good taste in packages, apparently - high turnover :P). On one, I
had to talk to 7 different developers before I found someone willing and
able to help. Just adding to the bug probably won't help unless it's
assigned to someone - take a look at it's changelog
(/usr/portage/category/package/Changelog) and try to get in touch with
specific people if nobody responds to the tracker.

Random idea: How about a different bug assignee for maintainer-needed
packages with provided ebuilds/patches? Either something generic, or try to
go for something more category/package specific (herds, etc). Lots of work
for bugwranglers, though. There is a huge difference to developers between
an unmaintained package with no progress and just looking over an ebuild
that has been used successfully by several people.

- John Brooks

On Sat, Aug 16, 2008 at 2:18 PM, Robert Bridge [EMAIL PROTECTED] wrote:

 On Sat, 16 Aug 2008 18:42:35 +0200
 Aniruddha [EMAIL PROTECTED] wrote:

  I've filed the bugreport (version bump) a year ago. It looks like borg
  has no maintainer.

 So maintain it. You don't need to be a dev to write an ebuild, and
 there are enough devs who are happy to throw an eye over user donated
 ebuilds and commit them to the tree...

 Removing a package from portage simply because no one has commited the
 up-to-date version you want is silly. If the only problem is
 no version bumping, provide the ebuild. Someone will commit it. I've
 done that for a few packages, it's not hard.

 I don't know anything about borg specifically, but as a user, I would
 not want to see packages being removed from portage just because the
 devs are too busy to write version bump ebuilds.

 Rob.