Control: tags -1 + moreinfo On Wed, 2026-10-14 at 23:27 +0200, Luca Padovan wrote: > Fair enough. Thanks for the constructive feedback anyway. > Best regards, Luca > > Il Mer 14 Ott 2026, 23:20 Andrey Rakhmatullin <[email protected]> ha scritto: > > On Wed, Oct 14, 2026 at 11:18:04PM +0200, Luca Padovan wrote: > > > I understand your concerns, but I'd appreciate some more specific feedback > > > on why you wouldn't recommend sponsoring portop. > > > > This feedback won't be actionable for you.
It's because the project is young (only 3 months old), and upstream and downstream being the same is a red flag for many DDs. Though, having a quick (superficial) look at the project, it looks to be of great quality regardless. These are the questions that need to be answered before this package can be considered for sponsoring, at least in my opinion: Why are you packaging a development snapshot rather than the latest v0.4.0 release? If you want a specific feature, why not package v0.4.0 first and then upload v0.4.0+git... to experimental? Consider anything in unstable is going to migrate to testing and then later propagate to stable. Right now, in it's current state using the latest release, is portop mature enough and suitable to be included in a stable release of Debian, where it will sit unchanged for 2 years with nothing but security fixes and non-intrusive important bug fixes (i.e. no new features)? Are you willing to ensure it is looked after for the full lifetime of a stable release by backporting any such fixes (minimal patches)? Will direct users to continue using your external APT repository because Debian is outdated (as many upstreams do), and if yes then what is the point of packaging? New packages must stand up to scrutiny on why they are being introduced. What is the benefit of packaging portop when other implementations like top, htop, btop and many others are already in Debian? In other words, what makes portop unique? Is there a reason that the package is not being maintained on salsa.debian.org, under go-team/packages/? Even though you are upstream, it is better for the packaging to be separate so that all the other Debian contributors can also easily make changes, especially considering you want team maintenance. Many sponsors are looking for a git repo, and Go team packages should be created following git-buildpackage / DEP- 14[1] format, and follow team conventions[2]. It also makes the packaging easier to find and work on; I was unable to find any debian/ directory or Debian packaging files in the master or develop branches of your GitHub repo. Hope this is helpful. This is not meant to discourage you, just point out things people like myself are thinking about. -- Maytham [1] https://dep-team.pages.debian.net/deps/dep14/ [2] https://go-team.pages.debian.net/packaging.html
signature.asc
Description: This is a digitally signed message part

