<div dir="ltr"><br><div class="gmail_extra">Thomas,</div><div class="gmail_extra"><br></div><div class="gmail_extra" style>BTW, it might be helpful to think of the noVNC master repository as a "larger work". noVNC pulls together a bunch of other components plus the noVNC core code to create the noVNC project.</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>Here is an example of one of the chains:</div><div class="gmail_extra" style>- noVNC includes websockify (<a href="https://github.com/kanaka/websockify">https://github.com/kanaka/websockify</a>) which includes both server-side (websocket.py, websockify) and client side components (e.g. websock.js, ).</div>
<div class="gmail_extra" style>- websockify's client side includes web-socket-js (<a href="https://github.com/gimite/web-socket-js">https://github.com/gimite/web-socket-js</a>)</div><div class="gmail_extra" style>- web-socket-js includes SWFObject, the gsolo MD5 implementation, the hurlant crypto library, etc.</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>I've filed a pull request with gimite to include the original source for swfobject.js: <a href="https://github.com/gimite/web-socket-js/pull/135">https://github.com/gimite/web-socket-js/pull/135</a> Once he pulls that in I will update the noVNC tree to reflect that.</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>I've also added a git submodule to point to the original web-socket-js tree to both noVNC and websockify.</div><div class="gmail_extra"><br><div class="gmail_quote">
On Thu, Apr 11, 2013 at 12:35 PM, Thomas Goirand <span dir="ltr"><<a href="mailto:thomas@goirand.fr" target="_blank">thomas@goirand.fr</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">> I would<br>
> be surprised if there is such a clause since it would imply that a<br>
> Debian ISO build would not be free software in the same sense because<br>
> the source is not physically included (only provided externally).<br>
<br>
</div>We also build source ISO images. Though these days, almost everyone<br>
download from internet, so it is a less known feature, so it is<br>
understandable that you didn't know.</blockquote><div><br></div><div style>Certainly I knew about it. But that doesn't change the point that somebody could download an ISO build that doesn't include the source, but the build is still 100% free and open source because the source is just as easily available as the binaries even though it is separate. This is also true of noVNC (even before I added the submodule links).</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">
> Your very request is for me to change the way I maintain noVNC<br>
<br>
</div>No, my request is that you add the missing source code in your<br>
repository, so that your project can be said 100% free and open source.<br>
I wouldn't like to impose anything on anyone.<br></blockquote><div><br></div><div style>I've added the submodule link to the web-socket-js source. Other options would require me to change my workflow because I would need to do munging (and therefore extra testing) of upstream project trees that I don't control. noVNC is just a side project for me now. I would like to keep the limited time I do have to be able to actually enhance noVNC and websockify and not spend any of it complying with extra Debian process overhead.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
My understanding is that this .swf file is there only to add support for<br>
web sockets in older browser. With time, this is becoming a feature less<br>
and less important, as newer browser have the feature.<br></blockquote><div><br></div><div style>Absolutely. I will celebrate the day when I feel like I can remove this entirely (I am not a Flash fan). Unfortunately, we're not there yet. </div>
<div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Can't you, instead, just ship swobject.js unobfuscated (that's easy to<br>
do, right?), and provide a link to the .swf blob somewhere? Is this<br>
completely unacceptable for you? If so, then we must agree to not agree,<br>
and indeed, I will continue to ship websockify as <version>+dfsg,<br>
showing that I had to modify upstream code to make it follow the Debian<br>
Free Software Guidelines.<br></blockquote><div><br></div><div style>I've issued the pull request to gimite/web-socket-js to add the original swfobject.js source to his tree. When (if) he pulls that in then I will update to reflect that. I've also added the git submodule link to the version of his tree that the current swf file is built from. If that's not sufficient (my read of the DFSG is that it should be sufficient), then yes, you'll probably need to maintain the separate dfsg tree for Debian.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">P.S: Are you going to the OpenStack Summit? It would be nice to meet you<br>
there.<br>
</blockquote></div><br></div><div class="gmail_extra" style>I would love to, but unfortunately I am not. noVNC and websockify are no longer part of my paid job so I don't have a sponsor to pay my way.</div><div class="gmail_extra" style>
<br></div><div class="gmail_extra" style>Regards,</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Joel Martin (kanaka)</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>
P.S. I'm not sure if Debian work is part of what you are paid to do or not, but regardless, I wanted to say thank you for doing all the work to package up OpenStack packages for Debian. I've worked before as a release engineer creating a large custom Linux distro (Gentoo based) and it's pretty tedious and thankless work. So thanks!</div>
</div>