aw snap
Arto Pekkanen
isoa at kapsi.fi
Tue Jul 19 11:55:47 UTC 2016
clutton kirjoitti 18.07.2016 12:54:
> Hi list.
>
> I'd like to fix an error and take the bounty.
> https://www.bountysource.com/issues/28271221-bounty-for-fixing-aw-snap-
> pages-on-freebsd-10-2
>
> I used to be interested in the issue but only now when exams is over I
> have some time/enough time.
>
> Is anyone working on this? Could I fix this, send patches, and take the
> bounty? Does anyone mind me doing this?
The related PR has been open for a long time now (almost a year):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204454
Just a moment ago another PR was filed regarding this issue:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211202
There is one indirectly related PR, kickstarter.com crashes browser:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207298
These official PRs for www/chromium are idle, with nobody working on
them. Mostly my comments there, providing some amateur insights, but
nothing useful to work on.
The more "active" issue tracker for FreeBSD chromium is here:
https://github.com/gliaskos/freebsd-chromium/issues
And as you can see, there is very little activity in regards to these
issues in any of these sources.
So yes sir, please do fix the bug if you can. There seems to be nobody
else working on this specific issue.
I would recommend checking in at
https://github.com/gliaskos/freebsd-chromium/issues/40 since this is
where the bounty originated from. With the github page you can also get
in touch with the official maintainers of the FreeBSD Chromium port.
There's a lot of technical background related to this issue, and I think
the official maintainers can elaborate on that a lot better than we
casual users can.
--
Arto Pekkanen
More information about the freebsd-chromium
mailing list