Re: WNPP Update Package source source of gjiten
On Tue, Oct 05, 2021 at 06:35:34PM +0900, notebook wrote:
>
> > > [Me]
> > > It looks like becoming a maintainer requires 40+ hours to go through all
> > > the "must read" articles and becoming accustomed to every procedure and
> > > guideline.
>
> > [Andrey]
> > Actually, even providing a source package for a one-time upload requires
> > that. Becoming a maintainer requires more, and is not a one-time action.
>
> And so my hopes of ever getting the new source in place drop away. 😅💦💦
Well, this is a 100% volunteer project, but the good thing is that everyone can
volunteer and contribute. Debian is a do-ocracy [1], so if you really want that
new version so hard that you need to use tear emojis, your best bet is to get
involved yourself. [2]
[1] https://www.debian.org/doc/manuals/debmake-doc/ch02.en.html#social
[2] or pay somone, eg a freelancer, to do the work for you.
> That sounds like a very lot of time for deploying. Is there a reason for
> having a system that time-consuming? It feels like the deploy takes away
> valuable that could be spend developing... Or are you talking about the time
> for "first-timers"?
For sure, the first package is the hardest, but the learning curve is steep.
My 2 cents:
And very likely you dont need to know everything by hearth at the beginning,
learning is continious experience and with an existing package, the QA tools
available in Debian (e.g lintian), the review process in mentors, you
need not be scared of the complexity, as you have an existing package you
could start off. It might be outdated, but the efforts are not from zero.
Debian is well known for its high quality packages, and the knowledge of
Debian packaging is one big part of ensuring the quality level. And with that
knowledge, packaging won't be too time consuming. So it is an investment.
Debians quality standards exceeds "[just] deploying", so the developement work
done for packaging is usually very well spent time. Development is not only
about features, as you know, but integrating it well into the system is very
important too.
--
tobi
>
>
> [Andrey]
> > I [...] you just want that the package in Debian uses your updated code, you don't need to (and can't) do anything in addition to [Filing the bug (#982343) on bugs.debian]
>
> Thank you for clearing things up! 🙂
>
> -- Chris
>
> On 2021/10/05 18:24, Andrey Rahmatullin wrote:
> > On Tue, Oct 05, 2021 at 06:20:11PM +0900, notebook wrote:
> > > > [Andrey Rahmatullin:]
> > > > If, on the other hand, you just want
> > > > that the package in Debian uses your updated code, you don't need to (and
> > > > can't) do anything in addition to what you already did.
> > >
> > > Just for future reference:
> > >
> > > "what you did" means
> > > (1) Writing here in debian-mentors and hoping for someone to do the job?
> > > or
> > > (2) Filing the bug (#982343) on bugs.debian?
> > (2)
> >
> > > > [Tobias Frost:]
> > > > Otherwise, we have the ITS procedure if you want to take over package maintainership:
> > > > https://wiki.debian.org/PackageSalvaging (from a very quick look at the package, it seems to be eligible for ITS)
> > > >
> > >
> > > It's not really clear to me what the result of package salvaging is. I
> > > guess it would make me a maintainer?
> > Yes.
> >
> > > Background:
> > > It looks like becoming a maintainer requires 40+ hours to go through all
> > > the "must read" articles and becoming accustomed to every procedure and
> > > guideline.
> > Actually, even providing a source package for a one-time upload requires
> > that. Becoming a maintainer requires more, and is not a one-time action.
> >
>
Reply to: