<div dir="auto">If the package is available under the GPL, it strikes me that requiring any non-trivial approval to obtain source under that license would not be allowed. If the form is just a check box verifying that you have received object code, maybe, but this sounds like it may be a license violation. Can we clarify what the approval process entails? How much information is required, and for what reasons might people be rejected?<div dir="auto"><br></div><div dir="auto">However, if some third party were to obtain this source, build from it, and make it available, that version of the code would be perfectly Free.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 10, 2020, 08:15 Andreas Tille <<a href="mailto:andreas@an3as.eu">andreas@an3as.eu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Jan 10, 2020 at 07:45:34AM -0500, Daniel Hakimi wrote:<br>
> Can you please clarify -- you said the license was the same, but you didn't<br>
> say what that license actually was. What license is your code available<br>
> under?<br>
<br>
GPL-3+ [1]<br>
<br>
BTW, I think if a Debian package is published the requirement to sign<br>
anything to get the source code is useless since interested parties can<br>
easily download the Debian source package.<br>
<br>
This is for instance true for the latest source in Git which just has a<br>
compile bug which we desperately try to fix to finalise the Qt4<br>
removal[2].<br>
<br>
Kind regards<br>
<br>
Andreas.<br>
<br>
[1] <a href="https://salsa.debian.org/med-team/freemedforms-project/blob/master/COPYING.txt" rel="noreferrer noreferrer" target="_blank">https://salsa.debian.org/med-team/freemedforms-project/blob/master/COPYING.txt</a><br>
[2] <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104" rel="noreferrer noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874880#104</a><br>
<br>
> On Fri, Jan 10, 2020, 07:18 Eric Maeker <<a href="mailto:eric.maeker@gmail.com" target="_blank" rel="noreferrer">eric.maeker@gmail.com</a>> wrote:<br>
> <br>
> > Hi,<br>
> ><br>
> > For now, our NPO is too poor to engage in consulting or to pay external<br>
> > developments and we awfully miss time to manage all aspects of a widely<br>
> > collaborative project.<br>
> > Sounds like we are travelling to "contrib" or "non-free" package ? Or may<br>
> > be "non-debian" ?<br>
> ><br>
> > Belle journée<br>
> > Cordialement<br>
> ><br>
> ><br>
> > <<a href="http://maeker.fr" rel="noreferrer noreferrer" target="_blank">http://maeker.fr</a>> *Dr Maeker Éric*<br>
> ><br>
> > *Gériatre, psychogériatre*<br>
> > <a href="mailto:eric.maeker@gmail.com" target="_blank" rel="noreferrer">eric.maeker@gmail.com</a><br>
> > Twitter @DrMaeker <<a href="https://www.twitter.com/drmaeker" rel="noreferrer noreferrer" target="_blank">https://www.twitter.com/drmaeker</a>><br>
> > RPPS 10002307964<br>
> ><br>
> > <a href="http://maeker.fr" rel="noreferrer noreferrer" target="_blank">maeker.fr</a> Site personnel<br>
> > <a href="http://empathies.fr" rel="noreferrer noreferrer" target="_blank">empathies.fr</a> Association Emp@thies<br>
> > <a href="http://freemedforms.com" rel="noreferrer noreferrer" target="_blank">freemedforms.com</a> Logiciel médical<br>
> ><br>
> > La gériatrie, c'est la médecine pour les pères et les mères Noël<br>
> ><br>
> ><br>
> > Le ven. 10 janv. 2020 à 03:03, Paul Wise <<a href="mailto:pabs@debian.org" target="_blank" rel="noreferrer">pabs@debian.org</a>> a écrit :<br>
> ><br>
> >> On Thu, Jan 9, 2020 at 8:00 PM Eric Maeker wrote:<br>
> >><br>
> >> > Free Source code is provided to any demander approved by the NPO, code<br>
> >> licence is still the same.<br>
> >><br>
> >> I don't like this, people seeking source code should not have to get<br>
> >> approval first. That said, I note that the source code is available<br>
> >> directly from the site without approval.<br>
> >><br>
> >> > But, the code documentation is only reserved to approved developers by<br>
> >> this NPO.<br>
> >><br>
> >> I definitely don't like this, it would be much better to publish the<br>
> >> code documentation to everyone under a free license.<br>
> >><br>
> >> > We do encourage new dev to apply to our NPO and to sign a CLA (which is<br>
> >> still a draft piece of text actually).<br>
> >><br>
> >> I don't like this either, it would be much better for devs to release<br>
> >> their contributions under the same license that you do, then you can<br>
> >> incorporate their changes, preserving their copyright over their<br>
> >> changes and passing on their license to you to downstream users. So<br>
> >> the whole of the software is then owned by a variety of copyright<br>
> >> holders, each of whom also have to abide by the license given to them<br>
> >> by the other contributors. The license on the software then cannot be<br>
> >> changed without contributor consensus, so it becomes a much more solid<br>
> >> project from a user perspective. Single-owner projects are much more<br>
> >> easy to turn proprietary.<br>
> >><br>
> >> <a href="http://ebb.org/bkuhn/blog/2014/06/09/do-not-need-cla.html" rel="noreferrer noreferrer" target="_blank">http://ebb.org/bkuhn/blog/2014/06/09/do-not-need-cla.html</a><br>
> >><br>
> >> > The problem is that FreeMedForms EHR needs access to private data<br>
> >><br>
> >> Could you explain why this data needs to be private? It would be much<br>
> >> better to release it publicly under a free license.<br>
> >><br>
> >> > The private data are only available to paying partners to the NPO.<br>
> >><br>
> >> Is this the only form of income that the NPO has available to it? It<br>
> >> sounds like the NPO is seeking what is called an "Open Core" business<br>
> >> model, where the core part of the project is public and freely<br>
> >> licensed but addons are proprietary. The incentives here can be quite<br>
> >> perverse, often companies seek to prevent outside contributions to the<br>
> >> core or even remove features from the core so that more people start<br>
> >> paying them for the proprietary addons. So I encourage you to consider<br>
> >> alternative income streams.<br>
> >><br>
> >> I think the best option for the would be to consult with as many of<br>
> >> the practices, clinics, hospitals and emergency departments that you<br>
> >> know about that use the software and find out the best way for the NPO<br>
> >> to have enough resources to continue development consistent with the<br>
> >> interests of the community of folks who use the software. Examples of<br>
> >> potential income models could include: large grants/sponsorships that<br>
> >> cover development and other costs, a membership subscriber base that<br>
> >> pays for all maintenance and development costs, or more of a<br>
> >> crowd-funding model where folks interested in specific features pay<br>
> >> for their development, or a community of consultants that do all work<br>
> >> on the project as requested by their customers or possibly a<br>
> >> combination of these and other options.<br>
> >><br>
> >> > Forks trie to access our private data using the open sourced server<br>
> >> protocol (query to a php script).<br>
> >><br>
> >> I would suggest to just make the data public and under a free license,<br>
> >> but if you don't want to do that, the way to go would be to setup an<br>
> >> e-commerce site where people have to pay before they can download the<br>
> >> private data and then have in the software a way to load the locally<br>
> >> saved data that has been downloaded from the site. I believe there are<br>
> >> some freely licensed e-commerce tools in Debian and the consultants<br>
> >> that offer support for Debian in your area might be able to help with<br>
> >> finding, installing and configuring them.<br>
> >><br>
> >> <a href="https://www.debian.org/consultants/" rel="noreferrer noreferrer" target="_blank">https://www.debian.org/consultants/</a><br>
> >> <a href="https://lists.debian.org/debian-consultants/" rel="noreferrer noreferrer" target="_blank">https://lists.debian.org/debian-consultants/</a><br>
> >><br>
> >> --<br>
> >> bye,<br>
> >> pabs<br>
> >><br>
> >> <a href="https://wiki.debian.org/PaulWise" rel="noreferrer noreferrer" target="_blank">https://wiki.debian.org/PaulWise</a><br>
> >><br>
> ><br>
<br>
-- <br>
<a href="http://fam-tille.de" rel="noreferrer noreferrer" target="_blank">http://fam-tille.de</a><br>
</blockquote></div>