You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
was added to the Freedesktop runtime by Tom Coldrick. The idea was
@@ -59,10 +59,12 @@ opened an <a href="https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/i
59
59
to include <a href="https://github.com/cisco/openh264"target="_blank" rel="noopener noreferrer">Cisco&rsquo;s OpenH264</a>
60
60
(commonly referred as <code>libopenh264</code> too) as an extension to the runtime.</p>
61
61
<p><code>libopenh264</code> code is open source but due to the H.264 patents, no
62
-
vendor is legally allowed to distribute their own binaries. The
63
-
solution to this was to distribute Cisco&rsquo;s unmodified binaries directly
64
-
to the user which would effectively be free of any royalties but the
65
-
catch is, the binaries have <a href="https://www.openh264.org/BINARY_LICENSE.txt"target="_blank" rel="noopener noreferrer">some license restrictions</a>
62
+
vendor is legally allowed to distribute their own binaries (some vendors
63
+
build it themselves and hand it to Cisco but no one made that arrangement
64
+
for us). The solution to this was to distribute Cisco&rsquo;s unmodified
65
+
binaries directly to the user which would effectively be free of any
<p>So Endless around that time, added <a href="https://docs.flatpak.org/en/latest/module-sources.html#extra-data"target="_blank" rel="noopener noreferrer">extra-data</a>
68
70
support to Flatpak. This meant that the Flatpak extension metadata
@@ -259,7 +261,13 @@ once again, now to Fedora and they are looking for ways to make their
259
261
own OpenH264 extension similar to how we did.</p>
260
262
<p>I hope the experience here helps anyone in the future wanting to maintain
261
263
such an extension and this will also serve as a reminder to how much
262
-
extra work patents like these causes.</p></description>
264
+
extra work patents like these causes.</p>
265
+
<p>Lastly I&rsquo;d like to thank Endless for giving us not only noopenh264 but
266
+
also extra-data support in Flatpak that made all this possible;
for maintaining this setup for a long time; <a href="https://gitlab.com/valentindavid"target="_blank" rel="noopener noreferrer">Valentin David</a>
269
+
for helping me in the last few days and everyone else who worked on this
was added to the Freedesktop runtime by Tom Coldrick. The idea was
@@ -60,10 +60,12 @@ opened an <a href="https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/i
60
60
to include <a href="https://github.com/cisco/openh264"target="_blank" rel="noopener noreferrer">Cisco&rsquo;s OpenH264</a>
61
61
(commonly referred as <code>libopenh264</code> too) as an extension to the runtime.</p>
62
62
<p><code>libopenh264</code> code is open source but due to the H.264 patents, no
63
-
vendor is legally allowed to distribute their own binaries. The
64
-
solution to this was to distribute Cisco&rsquo;s unmodified binaries directly
65
-
to the user which would effectively be free of any royalties but the
66
-
catch is, the binaries have <a href="https://www.openh264.org/BINARY_LICENSE.txt"target="_blank" rel="noopener noreferrer">some license restrictions</a>
63
+
vendor is legally allowed to distribute their own binaries (some vendors
64
+
build it themselves and hand it to Cisco but no one made that arrangement
65
+
for us). The solution to this was to distribute Cisco&rsquo;s unmodified
66
+
binaries directly to the user which would effectively be free of any
<p>So Endless around that time, added <a href="https://docs.flatpak.org/en/latest/module-sources.html#extra-data"target="_blank" rel="noopener noreferrer">extra-data</a>
69
71
support to Flatpak. This meant that the Flatpak extension metadata
@@ -260,7 +262,13 @@ once again, now to Fedora and they are looking for ways to make their
260
262
own OpenH264 extension similar to how we did.</p>
261
263
<p>I hope the experience here helps anyone in the future wanting to maintain
262
264
such an extension and this will also serve as a reminder to how much
263
-
extra work patents like these causes.</p></description>
265
+
extra work patents like these causes.</p>
266
+
<p>Lastly I&rsquo;d like to thank Endless for giving us not only noopenh264 but
267
+
also extra-data support in Flatpak that made all this possible;
for maintaining this setup for a long time; <a href="https://gitlab.com/valentindavid"target="_blank" rel="noopener noreferrer">Valentin David</a>
270
+
for helping me in the last few days and everyone else who worked on this
to include <ahref="https://github.com/cisco/openh264"target="_blank" rel="noopener noreferrer">Cisco’s OpenH264</a>
69
69
(commonly referred as <code>libopenh264</code> too) as an extension to the runtime.</p>
70
70
<p><code>libopenh264</code> code is open source but due to the H.264 patents, no
71
-
vendor is legally allowed to distribute their own binaries. The
72
-
solution to this was to distribute Cisco’s unmodified binaries directly
73
-
to the user which would effectively be free of any royalties but the
74
-
catch is, the binaries have <ahref="https://www.openh264.org/BINARY_LICENSE.txt"target="_blank" rel="noopener noreferrer">some license restrictions</a>
71
+
vendor is legally allowed to distribute their own binaries (some vendors
72
+
build it themselves and hand it to Cisco but no one made that arrangement
73
+
for us). The solution to this was to distribute Cisco’s unmodified
74
+
binaries directly to the user which would effectively be free of any
<p>So Endless around that time, added <ahref="https://docs.flatpak.org/en/latest/module-sources.html#extra-data"target="_blank" rel="noopener noreferrer">extra-data</a>
77
79
support to Flatpak. This meant that the Flatpak extension metadata
was added to the Freedesktop runtime by Tom Coldrick. The idea was
@@ -60,10 +60,12 @@ opened an <a href="https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/i
60
60
to include <a href="https://github.com/cisco/openh264"target="_blank" rel="noopener noreferrer">Cisco&rsquo;s OpenH264</a>
61
61
(commonly referred as <code>libopenh264</code> too) as an extension to the runtime.</p>
62
62
<p><code>libopenh264</code> code is open source but due to the H.264 patents, no
63
-
vendor is legally allowed to distribute their own binaries. The
64
-
solution to this was to distribute Cisco&rsquo;s unmodified binaries directly
65
-
to the user which would effectively be free of any royalties but the
66
-
catch is, the binaries have <a href="https://www.openh264.org/BINARY_LICENSE.txt"target="_blank" rel="noopener noreferrer">some license restrictions</a>
63
+
vendor is legally allowed to distribute their own binaries (some vendors
64
+
build it themselves and hand it to Cisco but no one made that arrangement
65
+
for us). The solution to this was to distribute Cisco&rsquo;s unmodified
66
+
binaries directly to the user which would effectively be free of any
<p>So Endless around that time, added <a href="https://docs.flatpak.org/en/latest/module-sources.html#extra-data"target="_blank" rel="noopener noreferrer">extra-data</a>
69
71
support to Flatpak. This meant that the Flatpak extension metadata
@@ -260,7 +262,13 @@ once again, now to Fedora and they are looking for ways to make their
260
262
own OpenH264 extension similar to how we did.</p>
261
263
<p>I hope the experience here helps anyone in the future wanting to maintain
262
264
such an extension and this will also serve as a reminder to how much
263
-
extra work patents like these causes.</p></description>
265
+
extra work patents like these causes.</p>
266
+
<p>Lastly I&rsquo;d like to thank Endless for giving us not only noopenh264 but
267
+
also extra-data support in Flatpak that made all this possible;
for maintaining this setup for a long time; <a href="https://gitlab.com/valentindavid"target="_blank" rel="noopener noreferrer">Valentin David</a>
270
+
for helping me in the last few days and everyone else who worked on this
was added to the Freedesktop runtime by Tom Coldrick. The idea was
@@ -59,10 +59,12 @@ opened an <a href="https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/i
59
59
to include <a href="https://github.com/cisco/openh264"target="_blank" rel="noopener noreferrer">Cisco&rsquo;s OpenH264</a>
60
60
(commonly referred as <code>libopenh264</code> too) as an extension to the runtime.</p>
61
61
<p><code>libopenh264</code> code is open source but due to the H.264 patents, no
62
-
vendor is legally allowed to distribute their own binaries. The
63
-
solution to this was to distribute Cisco&rsquo;s unmodified binaries directly
64
-
to the user which would effectively be free of any royalties but the
65
-
catch is, the binaries have <a href="https://www.openh264.org/BINARY_LICENSE.txt"target="_blank" rel="noopener noreferrer">some license restrictions</a>
62
+
vendor is legally allowed to distribute their own binaries (some vendors
63
+
build it themselves and hand it to Cisco but no one made that arrangement
64
+
for us). The solution to this was to distribute Cisco&rsquo;s unmodified
65
+
binaries directly to the user which would effectively be free of any
<p>So Endless around that time, added <a href="https://docs.flatpak.org/en/latest/module-sources.html#extra-data"target="_blank" rel="noopener noreferrer">extra-data</a>
68
70
support to Flatpak. This meant that the Flatpak extension metadata
@@ -259,7 +261,13 @@ once again, now to Fedora and they are looking for ways to make their
259
261
own OpenH264 extension similar to how we did.</p>
260
262
<p>I hope the experience here helps anyone in the future wanting to maintain
261
263
such an extension and this will also serve as a reminder to how much
262
-
extra work patents like these causes.</p></description>
264
+
extra work patents like these causes.</p>
265
+
<p>Lastly I&rsquo;d like to thank Endless for giving us not only noopenh264 but
266
+
also extra-data support in Flatpak that made all this possible;
for maintaining this setup for a long time; <a href="https://gitlab.com/valentindavid"target="_blank" rel="noopener noreferrer">Valentin David</a>
269
+
for helping me in the last few days and everyone else who worked on this
0 commit comments