Re: [Gimp-print-devel] 5.3.5 status?

[Solomon P. <pi...@sh...>]

On Wed, Dec 11, 2024 at 07:07:24PM -0500, Erik Beck of Tahoma wrote:
> Solomon, how can I and others help?

It's those big ticket items.  

1) Testing on actual printers

 Other than my dyesub fleet I have no idea if anything else still works 
 on real hardware.  Not that there have been a lot (if any?) changes 
 elsewhere...

2) Regression testing vs older versions

 There is the src/testpattern/Checksums directory in the tree; I need to 
 figure out how to generate a new batch and compare it to the previous 
 release's run.  Then go through the ones that differ and make sure they
 were intentionally changed.

3) Update web site and other public documentation

 * Extract current printer lists for the www site and update accordingly
 * Make it clear everywhere that MacOS is no longer supported
   (at least outside of MacPorts or Fink or whatever)
 * (Really, the entire web site should probably be replaced..)

Longer-term things:

4) Port gimp plugin to GEGL and GIMP3

 Earlier tonight I started getting the basic plumbing in place to make a 
 gimp-3 plugin possible. While I don't expect the actual gimp-interacing 
 bits will be terribly complicated (beyond handing >8bpp image data 
 formats) the real uplift is porting the gutenprintui library from gtk2 
 to gtk3.

5) Picking up the Standalone gutenprint printer application

 The GSoC project completed the initial phase, but a lot of work remains 
 -- general integration and cleanup, the inevitable testing, and 
 (particularly important for me) getting the dyesub backend in, which is 
 likely to take some serious restructuring of how it is put together.

 This matters because it's realistically going to be the only usable 
 path forward for gutenprint in the medium term.
 
6) Getting off of sourceforge

 I'm personally partial to sourcehut, if only because they consider 
 mailing lists (and email in general) to be first-class tools.

 The only things on sourceforge that matter are the mailing list 
 archives and the old release archive.  Both are extractable, though 
 sourceforge now "helpfully" strips out email address.  I don't know if 
 that will prevent re-importing elsewhere.

That's off the top of my head...

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)