Hello,
I'm working on the "Gjiten" package* ([1]). It was kind of abandoned and used Gtk2.As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
I upgraded it to Gtk3 and did some further development on it (see [2]).
I'd like to get the new codebase into the debian repos. If I understand correctly, I need a sponsor for that(?) Is there anyone willing to sponsor the package?
Hello Andrey:
Thank you for your reply!
As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
I contacted the current maintainers. They are too busy to do any work in this regard.
As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
On Tue, Oct 05, 2021 at 03:58:16PM +0900, notebook wrote:
Hello,As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
I'm working on the "Gjiten" package* ([1]). It was kind of abandoned and used Gtk2.
I upgraded it to Gtk3 and did some further development on it (see [2]).
I'd like to get the new codebase into the debian repos. If I understand correctly, I need a sponsor for that(?) Is there anyone willing to sponsor the package?
Hello Andrey:If you want to become a co-maintainer of the package in Debian you should
Thank you for your reply!
As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
I contacted the current maintainers. They are too busy to do any work in this regard.
So I guess whatever is in place must be replaced.
(2)[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?
[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. IYes.
guess it would make me a maintainer?
Background:Actually, even providing a source package for a one-time upload requires
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.
[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.
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]
On Tue, Oct 05, 2021 at 06:20:11PM +0900, notebook wrote:
(2)[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?
Yes.[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?
Background: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.
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.
Many of them.[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. 😅💦💦
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...Maintainers are usually not developers of the same project so this is irrelevant.
Or are you talking about the time for "first-timers"?Mostly.
Hi Chris,
On Tue, Oct 05, 2021 at 04:25:44PM +0900, notebook wrote:
Hello Andrey:
Thank you for your reply!
As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
I contacted the current maintainers. They are too busy to do any work in this regard.
Did you get any response?
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)
[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. 😅💦💦
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"?
[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(2)
(1) Writing here in debian-mentors and hoping for someone to do the job? or
(2) Filing the bug (#982343) on bugs.debian?
[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: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.
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.
As the package is already in Debian, you need to contact its current
maintainer(s) (though I see you already filed #982343).
I contacted the current maintainers. They are too busy to do any work in this regard.
Did you get any response?
Better question:
How were those contact attempts done?
On Oct 5, 2021, at 03:27, Tobias Frost <tobi@debian.org> wrote:
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.
As the package is already in Debian, you need to contact its current maintainer(s) (though I see you already filed #982343).
I contacted the current maintainers. They are too busy to do any work in this regard.
Did you get any response?
Better question:
How were those contact attempts done?
I contacted them via their mails stated on debian.
One mail was already dead (or I never received a reply).
And one stated he's too busy too work on it.
[Geert Stappers]
Willing to sponsor gjiten
[Matthew Fernandez]
the review process [...] surfaced many packaging issues [, ...] portability issues and build system issues
On Tue, Oct 05, 2021 at 08:27:37PM +0900, notebook wrote:
As the package is already in Debian, you need to contact its current >>>>>> maintainer(s) (though I see you already filed #982343).
I contacted the current maintainers. They are too busy to do any work in this regard.
Did you get any response?
Better question:
How were those contact attempts done?
I contacted them via their mails stated on debian.
One mail was already dead (or I never received a reply).
I hope we see why it is a good thing to have Debian BTS in the loop.
And one stated he's too busy too work on it.
Great opportunity to join forces.
Groeten
Geert Stappers
DD
Willing to sponsor gjiten
P.S.
Hi Felix
I'm back from vacantion and slowly catching up.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 243:27:40 |
Calls: | 6,625 |
Calls today: | 1 |
Files: | 12,175 |
Messages: | 5,320,257 |