Hi Martin,
On Fri, 10 Apr 2020, Martin Dosch wrote:
Dear Tomas,
thanks for your reply (I was already scared my message got stuck somewhere).
Debian is very much "scratch" your own itch, meaning here that the person
(or organisation) that needs something will do it.
Yeah, I also often hear it is a "Doacrazy" where people who do decide.
It might be that some Debian developper will need and pick up and maintain
your work, however if you care and want the package to be in Debian then I
suggest that you become an official member of Debian and maintain the
package within Debian. That would be awesome :-)
I'd love to maintain my program in Debian but I don't see myself capable of
doing so as debian packaging seems to be black magic to me.
If I read up something about debian packaging it usually opens a bunch of new
questions when answering one.
So I don't feel like it is a good idea to maintain a package as long as I
don't understand all those mechanisms.
Don't be offput by not understanding everything. Packaging is not a
complex task. Understanding everything is. When you do package stuff then
you use those pieces of the packaging universe that are useful for your
packaging to get done. Just get started and you'll see.
There are tools such as [lintian](https://lintian.debian.org/) that can
help you, by checking your packaging and telling you whether there are
things you need to fix.
Also fellow Debianers that can help you if you ask or will provide
feedback. You might get feedback that is rougher than you'd have liked,
but you take it sportsmanlike and grow.
Being a Debian Developer (thus part of the Debian project?) is even more
beyond my scope. I really like Debian and use it where possible (beside to
Android devices Debian is the only operating system in my home) but I don't
have enough time to be part of the Debian project. I don't see myself getting
involved to that degree which would mean to participate in project decisions
and politics.
It's not necessary to be taking part in discussions and politics. It's
your decision to do that or not to do that as in all participative
organisations.
I was (probably wrongly) thinking that I prepare the packaging and if it
seems sane the go-pkg-team takes over and brings the package to Debian.
If this is not going to happen I'm fine, maybe I'll take an approach to
maintain the package myself once I understand all the Debian packaging
mechanisms. Otherwise I can just compile it on all of my machines instead of
getting it out of the Debian repos without much hassle.
Preparing a package by yourself would be a first good, helpful step!
*t
