Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 681938 - graphics project: disband or reduce?
Summary: graphics project: disband or reduce?
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Council
Classification: Unclassified
Component: unspecified (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Graphics Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-28 17:51 UTC by Michał Górny
Modified: 2020-06-09 06:09 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
graphics-pkgs.txt (graphics-pkgs.txt,13.87 KB, text/plain)
2019-09-27 09:07 UTC, Michał Górny
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-03-28 17:51:09 UTC
I'd like to discuss the possibilities of restructuring or disbanding the graphics project.  No offense to the project members intended but I feel like the way things work today is suboptimal, and not all packages under graphics@ maintenance are actually maintained.

I don't believe 'graphics-related' is a good scope for a project.  More specifically, I don't believe we can expect M developers to work on N (≫ M) unrelated graphics packages, especially that they cover many different areas, including libraries, converters, photo viewers, photo editors, vector graphics software, blender...

My proposal would be to either:

a. disband graphics project entirely, let project members take the packages they're personally interested in and move everything else to m-needed.

b. limit graphics project to 'core' packages (e.g. common libraries such as libjpeg, libpng...), and move everything else to individual maintainers/m-needed.

What do you think?  FWICS graphics project maintains almost 150 packages right now.  If you're not ready for big steps yet, it may be a good idea to let others grab at least some of them.
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-09-27 08:33:29 UTC
Ping.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-09-27 09:07:37 UTC
Created attachment 591154 [details]
graphics-pkgs.txt

Here's a list of packages maintained by graphics@, sorted by last commit date.

If I receive no reply, I'm going to start at the bottom and either start moving them to maintainer-needed or lastriting them.
Comment 3 Markus Meier gentoo-dev 2019-09-28 06:31:52 UTC
Michał: I still take care of a few packages I use and maintain (darktable, hugin and a few deps). Should I assign myself as maintainer there?

And I'm not really sure what's best to do with the graphics project, since nobody is really active in there...
Comment 4 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-09-28 06:34:14 UTC
(In reply to Markus Meier from comment #3)
> Michał: I still take care of a few packages I use and maintain (darktable,
> hugin and a few deps). Should I assign myself as maintainer there?

Yes, having dedicated maintainers on at least some of the packages would certainly be helpful to identify them as really maintained.

> And I'm not really sure what's best to do with the graphics project, since
> nobody is really active in there...

Indeed.  I was thinking keeping it for the sake of basic libs like libjpeg, libpng etc. may make sense.  Maybe I'll start by dropping leaf packages to m-needed (like programs that don't look like very generic tools).
Comment 5 Arfrever Frehtes Taifersar Arahesis 2020-06-09 06:09:08 UTC
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aefcfab833320af67edd6f8f4d620999f3fadbc3

commit aefcfab833320af67edd6f8f4d620999f3fadbc3
Author:     Aaron Bauman <bman@gentoo.org>
AuthorDate: 2020-06-06 18:19:41 +0000
Commit:     Aaron Bauman <bman@gentoo.org>aefcfab833320af67edd6f8f4d620999f3fadbc3
CommitDate: 2020-06-06 18:50:17 +0000

    */*: re-assign graphics project ebuilds to m-n