there is no point to scrutinize iriduim (or ungoogled or any other
derived browser) - their codebase is probably 99% similar to chromium;
so if any of these have licensing issues it would be most likely what
they derive from chromium - i would not begin to look at derivatives or
qtwebengine until
2017-11-15T13:12:23-0800 jc_gargma wrote:
> When you post the results of QtWebEngine, please cc
> qtwebeng...@qt-project.org
> so that they are not left out of the loop this time.
> Qt is a friend to the free software community. Please give them the chance to
> fix the issues.
>
>
> -jc
Could
That's marvelous, thanks again,
Josh
On 30/11/17 12:02, Adonay Felipe Nogueira wrote:
See the update in the related thread. I'm seeding the text file.
2017-11-15T20:08:35+ Josh Branning wrote:
Thank you for this.
Could I also request you upload the text file(s) somewhere? I can't
seem
See the update in the related thread. I'm seeding the text file.
2017-11-15T20:08:35+ Josh Branning wrote:
> Thank you for this.
>
> Could I also request you upload the text file(s) somewhere? I can't
> seem to download them from the lists.gnu.org archive, and that may be
> a problem for
Yes, on a wiki would be good/fine. :)
Unsure about any maintenance ...
Thanks again,
Josh
On 15/11/17 20:39, Adonay Felipe Nogueira wrote:
I'd prefer a wiki or a temporary repository. Pads are OK but hard to
keep track of changes without a browser with enough resources and speed
to run the
I'd prefer a wiki or a temporary repository. Pads are OK but hard to
keep track of changes without a browser with enough resources and speed
to run the JS and live updates. I'll see where I can put the list.
I just notice that the FSD is having some downtime, perhaps they're
doing maintainance.
> I'll try doing the same steps for Iridium and QtWebEngine.
When you post the results of QtWebEngine, please cc qtwebeng...@qt-project.org
so that they are not left out of the loop this time.
Qt is a friend to the free software community. Please give them the chance to
fix the issues.
-jc
Thank you for this.
Could I also request you upload the text file(s) somewhere? I can't seem
to download them from the lists.gnu.org archive, and that may be a
problem for people who wish to help try and clarify the licenses.
May also be worth creating a pad, and seeing if people are willing
See the response I gave ([1]) to the new thread in the directory-discuss
mailing list ([2]).
Apparently it didn't change much, also considering the ambiguities I
noted on [1]..
I'll try doing the same steps for Iridium and QtWebEngine.
[1]
On 15/11/17 16:42, Adonay Felipe Nogueira wrote:
I also have contributed to that thread on directory-discuss mailing
list.
I hope it helps somehow. ;)
bill-auger writes:
there is an open issue about this on the parabola bug tracker that you
can watch if you like
I also have contributed to that thread on directory-discuss mailing
list.
I hope it helps somehow. ;)
bill-auger writes:
> there is an open issue about this on the parabola bug tracker that you
> can watch if you like
>
> https://labs.parabola.nu/issues/1167
>
> i
On 11/10/2017 03:14 PM, happy gnu wrote:
> But what about iridium?
there is an open issue about this on the parabola bug tracker that you
can watch if you like
https://labs.parabola.nu/issues/1167
i asked donaldr about this last week and he asked that i post to the FSD
mailing list so
12 matches
Mail list logo