Bug#1051250: ITP: hyfetch -- A system info script built off of Neofetch, continuing development of the original project and adding new functionality

[Bailey Kasin]

Package: wnpp
Severity: wishlist
Owner: Bailey Kasin <baile...@gmail.com>
X-Debbugs-Cc: debian...@lists.debian.org

* Package name : hyfetch
Version : 1.4.10
Upstream Contact: Azalea Gui <m...@hydev.org>
* URL : https://github.com/hykilpikonna/hyfetch
* License : MIT
Programming Lang: Python
Description : A system info script built off of Neofetch, continuing development of the original project and adding new functionality

HyFetch started as a fork of Neofetch to add pride flag
colorations, and now also maintains Neofetch as that
project seems to be abandoned. The standard, updated
Neofetch script gets installed as Neowofetch to avoid
name collisions.

It can also integrate with tools such as Fastfetch and
qwqfetch, to act as a frontend for them adding the same
features it adds for Neofetch.

- This package is relevant because it is useful on it's
own, and also replaces an abandoned project.

- I contribute to the project and can handling packaging
on my own, though I believe this package falls under
the Debian Python Team umbrella and I have applied to
that team to maintain it there. (I am rather unfamiliar
with this process as this is the first package I have
tried to submit). I believe that also means that I do
need a sponsor.

[Marvin Renich]

Your short description is way too long and only three words in it are
useful: "system info script". Those three words by themselves do not
really give a good idea what the package does.

The neofetch package description (short and long) is much better; you
should model yours from it, adding the bits about being a fork of
Neofetch and integration with other tools in the long description.
Describe _what_ your package does first, then if room allows, add where
it came from.

It is definitely useful, in the long description, to describe how it
differs from the project that it forked. I wouldn't take that out, just
reorder things a bit, possibly rewording it as necessary. Write your
description as if the reader may not know what Neofetch does. Something
like:

HyFetch is a command line script to display information about your
Linux system, such as.... It is a fork of Neofetch, and adds pride
flag coloration.

It can also integrate....

It is also not clear (and possibly not relevant?) what the difference is
between "started as a fork" and "now also maintains". Did upstream for
hyfetch take over the neofetch github repo? You might want to just
leave out the second part, or at least reword it to be more clear.
Normally, a fork of a now-defunct project is just called a fork, unless
there was some official transfer of the old project's assets to the new
project upstream.

...Marvin

* Bailey Kasin <baile...@gmail.com> [230905 02:09]:

[Bailey Kasin]

Thank you for the feedback.

How are these for updated package descriptions?

Short description:

Customizable Linux System Information Script

Long description:

HyFetch is a command line script to display information about your

Linux system, such as amount of installed packages, OS and kernel

version, active GTK theme, CPU info, and used/available memory.

It is a fork of Neofetch, and adds pride flag coloration to the OS logo.

Upstream hyfetch has not taken over the repo, they remain separate. So

I think you are correct the difference is not relevant and just added

confusion to the original description.