[prev in list] [next in list] [prev in thread] [next in thread]
List: gtk-devel
Subject: Re: First deprecate APIs and then remove them in the next major version
From: Daniel Kasak <d.j.kasak.dk () gmail ! com>
Date: 2017-12-18 2:13:22
Message-ID: CAF73Y=Q8r2a9mTO72zJtV_fzPJ8kHQLintu4MAy=v_v=zyb46A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Yeah, I poked originally. See:
https://bugzilla.gnome.org/show_bug.cgi?id=156017#c3
https://bugzilla.gnome.org/show_bug.cgi?id=156017#c5
https://bugzilla.gnome.org/show_bug.cgi?id=156017#c6
Other people commented and submitted further patches after that. After
that, I just gave up. If you're looking for more volunteers, have a good
think about this.
Just recently another bug has been marked as a duplicate of this one. I get
the feeling if I just continue to ping the bug, or the list, people would
tell me to pull my head in because it's not scratching their itch or
whatever. I only brought it up in the context of someone else saying there
are issues getting patches reviewed and applied.
Regarding IRC - I've never used it because it doesn't save history, so I
have to keep an IRC client open 24/7 just to see people's responses - and
the people I'm waiting on are invariably in a different timezone. If you
have a viable product, submitting a bug to their bug tracking systems and
pinging a couple of times should be sufficient - and I note what's been
said above regarding there only being 1 full-time developer on the product.
Redirecting people to IRC doesn't make less work for anyone - it makes
more. Anyway, I did email the gtk-devel-list - from memory - though
admittedly it was 13 years ago, as you mentioned.
> Otherwise, you get exactly what you paid for.
Oh, I had that one coming. Thankyou.
Dan
On Mon, Dec 18, 2017 at 11:16 AM, Emmanuele Bassi <ebassi@gmail.com> wrote:
> On 17 December 2017 at 23:14, Daniel Kasak <d.j.kasak.dk@gmail.com> wrote:
>
> >> Just one example, gtk3 (yes 3, not even 4) is currently completely
> >> unusable on
> >> Mac, so I sent a patch to fix this:
> >>
> >> https://bugzilla.gnome.org/show_bug.cgi?id=791174
> >>
> >> I know my patch is suboptimal, but to make this clear: it does not
> address
> >> a
> >> minor bug, this bug is a real show stopper on Mac, and this change is
> >> purely
> >> gtk internal. Of course it is not a clean solution, but there is no
> reason
> >> to
> >> simply apply this patch (at a bare minimum at least to the gtk3/stable
> >> branch)
> >> with a FIXME comment for now so that people on Mac can finally start
> using
> >> gtk3
> >> at all.
> >
> >
> > I really have to agree. One of my bugs I raised in 2004 - which involves
> > data loss - is still open. I submitted a patch ( which was difficult at
> the
> > time - I only dabble in C when I absolutely have to ) which received very
> > little feedback, and the bug has rotted since.
>
> Yes, everyone has their own pet bug where they submitted a patch and
> waited for feedback, as if GTK doesn't have ~3000 issues open at any
> given time, and a constant stream of bugmail.
>
> It would be *great* if we could review all incoming patches; sadly, we
> either do that, or we spend time actually developing the toolkit.
>
> Plus, if you have a patch lying in bugzilla for *13* years and you
> never bothered to actually poke people about it, then I don't think
> it'll ever get bumped up in terms of priority on the list of things to
> do.
>
> > "Send a patch" only goes so far. If patches don't get reviewed, or don't
> get
> > sufficient feedback, and never get accepted, what's the point in sending
> > patches?
>
> Your role doesn't terminate at sending a patch.
>
> It's your bug, your patch, and your responsibility for bringing it up
> to the people *volunteering* to work on GTK. If you have a patch that
> is languishing in Bugzilla, join the #gtk+ IRC channel on
> irc.gnome.org, or send an email to gtk-devel-list.
>
> Otherwise, you get exactly what you paid for.
>
> Ciao,
> Emmanuele.
>
> --
> https://www.bassi.io
> [@] ebassi [@gmail.com]
>
[Attachment #5 (text/html)]
<div dir="ltr">Yeah, I poked originally. See:<div> <a \
href="https://bugzilla.gnome.org/show_bug.cgi?id=156017#c3">https://bugzilla.gnome.org/show_bug.cgi?id=156017#c3</a><br> \
<a href="https://bugzilla.gnome.org/show_bug.cgi?id=156017#c5">https://bugzilla.gnome.org/show_bug.cgi?id=156017#c5</a><br> \
<a href="https://bugzilla.gnome.org/show_bug.cgi?id=156017#c6">https://bugzilla.gnome.org/show_bug.cgi?id=156017#c6</a><br><br>Other \
people commented and submitted further patches after that. After that, I just gave \
up. If you're looking for more volunteers, have a good think about \
this.</div><div><br></div><div>Just recently another bug has been marked as a \
duplicate of this one. I get the feeling if I just continue to ping the bug, or the \
list, people would tell me to pull my head in because it's not scratching their \
itch or whatever. I only brought it up in the context of someone else saying there \
are issues getting patches reviewed and applied.</div><div><br></div><div>Regarding \
IRC - I've never used it because it doesn't save history, so I have to keep \
an IRC client open 24/7 just to see people's responses - and the people I'm \
waiting on are invariably in a different timezone. If you have a viable product, \
submitting a bug to their bug tracking systems and pinging a couple of times should \
be sufficient - and I note what's been said above regarding there only being 1 \
full-time developer on the product. Redirecting people to IRC doesn't make less \
work for anyone - it makes more. Anyway, I did email the gtk-devel-list - from memory \
- though admittedly it was 13 years ago, as you \
mentioned.</div><div><br></div><div>> <span style="font-size:12.8px">Otherwise, \
you get exactly what you paid for.</span></div><div><span \
style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Oh, I \
had that one coming. Thankyou.</span></div><div><span \
style="font-size:12.8px"><br>Dan</span></div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Dec 18, 2017 at 11:16 AM, Emmanuele Bassi <span \
dir="ltr"><<a href="mailto:ebassi@gmail.com" \
target="_blank">ebassi@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 17 December 2017 at 23:14, Daniel Kasak \
<<a href="mailto:d.j.kasak.dk@gmail.com">d.j.kasak.dk@gmail.com</a>> wrote:<br> \
<br> >> Just one example, gtk3 (yes 3, not even 4) is currently completely<br>
>> unusable on<br>
>> Mac, so I sent a patch to fix this:<br>
>><br>
>> <a href="https://bugzilla.gnome.org/show_bug.cgi?id=791174" \
rel="noreferrer" target="_blank">https://bugzilla.gnome.org/<wbr>show_bug.cgi?id=791174</a><br>
>><br>
>> I know my patch is suboptimal, but to make this clear: it does not \
address<br> >> a<br>
>> minor bug, this bug is a real show stopper on Mac, and this change is<br>
>> purely<br>
>> gtk internal. Of course it is not a clean solution, but there is no \
reason<br> >> to<br>
>> simply apply this patch (at a bare minimum at least to the gtk3/stable<br>
>> branch)<br>
>> with a FIXME comment for now so that people on Mac can finally start \
using<br> >> gtk3<br>
>> at all.<br>
><br>
><br>
> I really have to agree. One of my bugs I raised in 2004 - which involves<br>
> data loss - is still open. I submitted a patch ( which was difficult at the<br>
> time - I only dabble in C when I absolutely have to ) which received very<br>
> little feedback, and the bug has rotted since.<br>
<br>
</span>Yes, everyone has their own pet bug where they submitted a patch and<br>
waited for feedback, as if GTK doesn't have ~3000 issues open at any<br>
given time, and a constant stream of bugmail.<br>
<br>
It would be *great* if we could review all incoming patches; sadly, we<br>
either do that, or we spend time actually developing the toolkit.<br>
<br>
Plus, if you have a patch lying in bugzilla for *13* years and you<br>
never bothered to actually poke people about it, then I don't think<br>
it'll ever get bumped up in terms of priority on the list of things to<br>
do.<br>
<span class=""><br>
> "Send a patch" only goes so far. If patches don't get reviewed, or \
don't get<br> > sufficient feedback, and never get accepted, what's the \
point in sending<br> > patches?<br>
<br>
</span>Your role doesn't terminate at sending a patch.<br>
<br>
It's your bug, your patch, and your responsibility for bringing it up<br>
to the people *volunteering* to work on GTK. If you have a patch that<br>
is languishing in Bugzilla, join the #gtk+ IRC channel on<br>
<a href="http://irc.gnome.org" rel="noreferrer" target="_blank">irc.gnome.org</a>, or \
send an email to gtk-devel-list.<br> <br>
Otherwise, you get exactly what you paid for.<br>
<div class="HOEnZb"><div class="h5"><br>
Ciao,<br>
Emmanuele.<br>
<br>
--<br>
<a href="https://www.bassi.io" rel="noreferrer" \
target="_blank">https://www.bassi.io</a><br> [@] ebassi [@<a href="http://gmail.com" \
rel="noreferrer" target="_blank">gmail.com</a>]<br> \
</div></div></blockquote></div><br></div>
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic