Re: [License-discuss] OSI definition

2021-01-19 Thread Rick Moen
ng parties in their respective and figuratively-collective pedal extremities. -- Cheers, This limerick goes in reverse. If you start from the bottom-most verse Rick Moen Unless I’m remiss, This limerick’s not any worse. rick@linu The neat thing is this:-- Za

Re: [License-discuss] Feedback about fair-code model

2020-07-29 Thread Rick Moen
It might meet your needs, or maybe not. It does not reserve the monopoly over commercial use you mentioned in your four points. -- Cheers,There's no theorem like Bayes's Theorem, like no theorem we know. Rick Moen Everything about it is appealing, everything about it is a

Re: [License-discuss] How can we as a community help empower authors outside license agreements?

2020-03-18 Thread Rick Moen
lios-booth [2] https://en.wikipedia.org/wiki/Helios_Voting -- Cheers, "You can't do anything about the length of your life, Rick Moen but you can do something about its width and depth." r...@linuxmafia.com

Re: [License-discuss] How can we as a community help empower authors outside license agreements?

2020-03-18 Thread Rick Moen
r its Board elections. (Not urgent; I'm mostly just curious.) -- Cheers, "It's funny that pirates were always going around searching Rick Moen for treasure, and they never realized that the real r...@linuxmafia.com treasure was the fond memories they were cr

Re: [License-discuss] How can we as a community help empower authors outside license agreements?

2020-03-17 Thread Rick Moen
"Heedless of grammar, they all cried 'It's him!'" Rick Moen -- R.H. Barham, _Misadventure at Margate_ r...@linuxmafia.com McQ! (4x80) ___ License-discuss mailing list License-discuss@lists.opensourc

Re: [License-discuss] How can we as a community help empower authors outside license agreements?

2020-03-17 Thread Rick Moen
tails about how OSI votes for Board elections, e.g., FPtP vs. some flavour of ranked-choice, and so on, it would warm the heart of this voting-algorithm geek. (Again, I apologise if this has already been covered.) -- Cheers, "The crows seemed to be calling his name, thought Caw.&

Re: [License-discuss] How can we as a community help empower authors outside license agreements?

2020-03-17 Thread Rick Moen
6 + 82) / (224 + 198 + 137 + 92 + 82 + 67 + 60 + 56 + 39 + 36 + 36 + 13 + 7 + 7 + 7) .11 quit Liten-Datamaskin:~ rick$ (What can I say? I remain an incurable empiricist.) -- Cheers, "Why doesn't anyone invite copyeditors to parties, Rick Moen when

Re: [License-discuss] Thoughts on the subject of ethical licenses

2020-03-12 Thread Rick Moen
em short of writing a from-scratch replacement (which is what happened in April 2005; see: http://linuxmafia.com/faq/Apps/vcs.html#git ). -- Cheers, 299792458 meters per second. Not Rick Moenjust a good idea. It's the

Re: [License-discuss] Thoughts on the subject of ethical licenses

2020-03-12 Thread Rick Moen
s and being ignored, I don't see why it > is wrong to wonder if there is something different going on here than is > being publicly claimed. Fair points, well articulated. -- Rick Moen"Avoid dangling participles unless referring to James Bond, r...@linuxmafia.com in

Re: [License-discuss] Thoughts on the subject of ethical licenses

2020-03-11 Thread Rick Moen
about twenty hours later the same day, without any response to my critique, or yours, or a number of others'. I'm not rushing, here, to any conclusions (let alone uncharitable ones) as to the reason why: I merely note the sequence of events. -- Rick Moen "The

Re: [License-discuss] Thoughts on the subject of ethical licenses

2020-03-11 Thread Rick Moen
just as good, for public purposes -- feigned.) -- Cheers, Simple systems are not feasible because Rick Moen they require infinite testing. r...@linuxmafia.com -- Augustine's Law Number XLII McQ! (4x80) ___

Re: [License-discuss] What should fit in a FOSS license?

2020-03-11 Thread Rick Moen
'rejected licenses page') is here: https://wiki.opensource.org/bin/Archived+Discussions+on+Not+Approved+Licenses/ -- Cheers, « Le doute n'est pas une état bien agréable, mais Rick Moen l'assurance est un état ridicule. » ("Doubt is not r...@lin

Re: [License-discuss] Thoughts on the subject of ethical licenses

2020-03-08 Thread Rick Moen
ny of those groups had lost its bearings if it suddenly started trying to peremptorally short 'evil people' on rights and privileges (or responsibilities, either). But obviously Views Differ[tm]. -- Cheers, "Maybe the law ain't perfect, but it&

Re: [License-discuss] Thoughts on the subject of ethical licenses

2020-03-08 Thread Rick Moen
down OSD#6 ('No Discrimination Against Fields of Endeavor') if elected to OSI's Board in service of ideological goals seems to have drawn most of the attention, but my point is that that's the smallest part of the matter. -- Cheers, "Maybe the law a

Re: [License-discuss] Ethical open source licensing - Dual Licensing for Justice

2020-03-07 Thread Rick Moen
a project's Code of Conduct or a similar place, not in a licence text. IMO, he should have listened then. -- Cheers, "A recursive .sig Rick Moen Can impart wisdom and truth. r...@linuxmafia.com

[License-discuss] Backfilling Mailman archive gaps (was: Columbia S&T Law Review analysis of the OSI license-discuss mailing list)

2020-02-29 Thread Rick Moen
rovider's technical staff, but, with some luck, they would not refuse. (Mindful of Pam's request to please be nice, I'll not elaborate on what rightfully should be done concerning hosting providers who refuse. ;-> ) -- Cheers,There's no theorem like Bayes's

Re: [License-discuss] Ethical open source licensing - Persona non Grata Preamble

2020-02-29 Thread Rick Moen
codebase under your/my supervision, anyone objecting to your/my policy is free to ignore that policy and act differently concerning that person's own code instance and develop it differently. -- Cheers, "Maybe the law ain't perfect, but i

[License-discuss] Early uses of the term open source (was: "Fairness" vs. mission objectives)

2020-02-28 Thread Rick Moen
I belatedly noticed this subthread from a few days back, which happily helps angle back to software licensing and OSI: Quoting Eric S. Raymond (e...@thyrsus.com): > No, it wasn't. Believe me, I did a *very* through audit on existing > usage at the time I proposed the term for general use in 1998

Re: [License-discuss] Language, appropriateness, and ideas

2020-02-27 Thread Rick Moen
ing on the differences here because that sort of geeky metadiscussion wouldn't help the noise problem even a bit. -- Cheers, "Why doesn't anyone invite copyeditors to parties, Rick Moen when we're such cool people out with whom to hang?" r...@linuxmafia

Re: [License-discuss] Ethical open source licensing - Persona non Grata Preamble

2020-02-23 Thread Rick Moen
ectly by mailing list regulars.) -- Cheers, "Why doesn't anyone invite copyeditors to parties, Rick Moen when we're such cool people out with whom to hang?" r...@linuxmafia.com--

Re: [License-discuss] Ethical open source licensing - Persona non Grata Preamble

2020-02-22 Thread Rick Moen
anagement speaks for a codebase. Which is exactly what open source avoids. -- Cheers, "I am not a vegetarian because I love animals; Rick MoenI am a vegetarian because I hate plants." r...@linuxmafia.com

Re: [License-discuss] Ethical open source licensing - Persona non Grata Preamble

2020-02-22 Thread Rick Moen
[1] If interested in this history, see my coverage for _Linux Gazette_: http://linuxmafia.com/~rick/exhibit-b.html http://linuxmafia.com/~rick/exhibit-b-more.html -- Cheers, "Maybe the law ain't perfect, but it's the only Rick Moenone we got, and wi

Re: [License-discuss] Ethical open source licensing - Persona non Grata Preamble

2020-02-21 Thread Rick Moen
tps://wwahammy.com/on-safety-at-libreplanet/ -- Cheers, "Why doesn't anyone invite copyeditors to parties, Rick Moen when we're such cool people out with whom to hang?" r...@linuxmafia.com

Re: [License-discuss] MIT-Clone: Copyright notice

2020-02-14 Thread Rick Moen
the merits of MIT Licence exactly the way it is, and not seek to create a semi-clone with unwise modifications made for unwise reasons. -- Cheers, "Why doesn't anyone invite copyeditors to parties, Rick Moen when we'

Re: [License-discuss] [License-review] For approval: The Cryptographic Autonomy License (Beta 4)

2020-01-06 Thread Rick Moen
f via an OSCON keynote), the third one (Microsoft Reference License, Ms-RL) omitting rights of modification and redistribution, intended e.g., for reference copies of software libs -- obviously not open source. -- Cheers, "Maybe the law ain’t perfect, but it’s the only Rick

Re: [License-discuss] Why will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)?

2019-11-15 Thread Rick Moen
Quoting gameonli...@redchan.it (gameonli...@redchan.it): > I am a lawyer. [...] > And yes IAAL. Well, hello again, MikeeUSA! -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom anger. Study how awful our ancestors ha

[License-discuss] [OT] Noise filter (was: The CAL is NOT unilateral because...)

2019-07-30 Thread Rick Moen
Quoting Lawrence Rosen (lro...@rosenlaw.com): > Please no longer answer him here. 17 years ago on this very mailing list, a remarkably similar thread inspired contributor Tobia Conforto to post a very useful procmail filter, usable by individual subscribers to filter both postings from specific

Re: [License-discuss] code hosting (was Re: Evolving the License Review process for OSI)

2019-06-11 Thread Rick Moen
Quoting Pamela Chestek (pam...@chesteklegal.com): > Not sure what any of this has to do with software licensing Point taken, and course corrected. ___ License-discuss mailing list License-discuss@lists.opensource.org http://lists.opensource.org/ma

Re: [License-discuss] code hosting (was Re: Evolving the License Review process for OSI)

2019-06-11 Thread Rick Moen
Quoting Bruce Perens via License-discuss (license-discuss@lists.opensource.org): > You're a bit over the top, regarding Ruby on Rails. And if you are bothered > by the performance or resource use, consider converting the code to Crystal. Oh, I don't know about over the top. There's not a single

Re: [License-discuss] code hosting (was Re: Evolving the License Review process for OSI)

2019-06-10 Thread Rick Moen
Quoting Thorsten Glaser (t...@mirbsd.de): > I will not use the Debian-provided Gitlab even for Debian packages > if I can avoid it, both because I’m > by their badly coordinated move and because of its proprietaryness. Anyone's GitLab is also (IMVAO) grossly overengineered. From my own Operatio

Re: [License-discuss] Evolving the License Review process for OSI

2019-06-10 Thread Rick Moen
I'll follow Christopher's good example, and also try to cut to the chase. Quoting Christopher Sean Morrison via License-discuss (license-discuss@lists.opensource.org): > Except that we don’t need a representative number. If use cannot be > found, that would not imply there isn’t any. I certain

Re: [License-discuss] code hosting (was Re: Evolving the License Review process for OSI)

2019-06-10 Thread Rick Moen
Quoting John Cowan (co...@ccil.org): > A basically volunteer agency like OSI "self-hosts" when someone volunteers > to host for them. When that volunteer loses interest, the "self-hosting" > goes away. Failover is a thing, isn't it? Let me tell you a story. I'm a longtime volunteer with a loca

Re: [License-discuss] Discourse email

2019-06-10 Thread Rick Moen
Quoting Lawrence Rosen (lro...@rosenlaw.com): > Somehow a decision will be made eventually here despite accusations of > "strange personal rhetoric" in Rick's 2019 email that he formatted as "plain > text." Even HTML is still suspicious to some people, but I changed Rick's > message to HTML format

Re: [License-discuss] Evolving the License Review process for OSI

2019-06-10 Thread Rick Moen
Quoting Christopher Sean Morrison via License-discuss (license-discuss@lists.opensource.org): > I didn’t say he did. He commented on a potential lack of public > hosting as grounds for “absolutely not even [coming] close to checking > whether a license is in use”. I commented on the general not

Re: [License-discuss] Evolving the License Review process for OSI

2019-06-10 Thread Rick Moen
Quoting Christopher Sean Morrison via License-discuss (license-discuss@lists.opensource.org): > Code under an Open Source license that is not publicly available might > as well not be. Objection: Thorsten didn't speak of code that lacks public availability. > If it’s not publicly available a

Re: [License-discuss] popularity, usage, re-review of old licenses [was Re: Evolving the License Review process for OSI

2019-06-09 Thread Rick Moen
Quoting Luis Villa (l...@lu.is): > [1] who did not notice my "basic internet 101" subject change ;) What I _actually_ said was that just editing the Subject header (and preferably also deleting In-Reply-To so that mailers doing real threading pick up the change) is 'Internet 101' as a method to..

Re: [License-discuss] [License-review] Evolving the License Review process for OSI

2019-06-04 Thread Rick Moen
osted software, so if that's the criterion OSI wants to apply, then outsourcing will automatically win, every time. -- Cheers, Rick Moen "History is a nightmare from which I am trying to awake." r...@linuxmafia.com -- Ste

Re: [License-discuss] [License-review] Evolving the License Review process for OSI

2019-06-04 Thread Rick Moen
t. Speaking for myself, if I were to outsource, especially to a third-party-hosted Ember.js, Javascript, and Ruby on Rails application so complex that I couldn't administer it anyway, I'd feel I had weakened the open source message quite a bit. -- Cheers, "

Re: [License-discuss] Evolving the License Review process for OSI

2019-06-04 Thread Rick Moen
Quoting Henrik Ingo (henrik.i...@avoinelama.fi): > I can of course only speak for myself, but I don't think the above is > the right conclusion at all. Recent mailing list discussion seems to > have made the point that adhering to precedent is hard, when in most > cases the process does not produc

Re: [License-discuss] Evolving the License Review process for OSI

2019-06-03 Thread Rick Moen
Quoting McCoy Smith (mccoy.sm...@intel.com): > The problem with "grandfathering" such licenses is that they can be > used as precedent for new license submitters as to why their non-OSD > compliant licenses must also be approved. Several recent posters to this thread (including now you) have decr

Re: [License-discuss] [License-review] Evolving the License Review process for OSI

2019-06-02 Thread Rick Moen
umentation about the withdrawal including the present one in the OSI FAQ (https://opensource.org/faq#cc-zero) ought to cross-link to that exact URL for the full context. -- Cheers, A programmer had a problem. He thought to himself, "I know, Rick Moen I'll solve it

Re: [License-discuss] [License-review] Evolving the License Review process for OSI

2019-06-02 Thread Rick Moen
ttle and installing PaleMoon or ungoogled-chromium. -- Cheers,There's no theorem like Bayes's Theorem, like no theorem we know. Rick Moen Everything about it is appealing, everything about it is a wow. rick@linux Let out all that a-priori feeling, you've been concea

Re: [License-discuss] Threading and topic drift (was: License licenses)

2019-05-31 Thread Rick Moen
Ah, the perfidious typo. > So, you don't actually agree with what I said, but you're arguing anyway. ^ disagree Darn, stepped on my own line. ___ License-discuss mailing list License-discuss@lists.opensource.org http://lis

Re: [License-discuss] Threading and topic drift (was: License licenses)

2019-05-31 Thread Rick Moen
folks are trying to reach users where they actually > read and write. So, you don't actually agree with what I said, but you're arguing anyway. It's almost like you're one of my lawyer friends. ;-> -- Cheers, "I am a member of a civilization (IAAMOAC).

[License-discuss] Threading and topic drift (was: License licenses)

2019-05-31 Thread Rick Moen
Quoting Kevin P. Fleming (kevin+...@km6g.us): > As a regular Discourse user, I can say that this is one *huge* benefit > of that tool over regular mailing lists: threads can be split off into > separate topics, so that readers and others can follow the topics they > care about and don't have to wa

[License-discuss] Crossposting Considered Harmful (was: [License-review] Evolving the License Review process for OSI)

2019-05-27 Thread Rick Moen
¡Hola! Please note: > To: "Tzeng, Nigel H." > Cc: Bruce Perens , > License submissions for OSI review > , > "license-discuss@lists.opensource.org" > To paraphrase the illustrious Jamie Zawinski's famous jibe about awk, 'A man once had a problem with a contentiou

Re: [License-discuss] Evolving the License Review process for OSI

2019-05-26 Thread Rick Moen
Quoting Russell McOrmond (russellmcorm...@gmail.com): > The OSI as an organisation is free to determine its own objectives. > Whether they are in-line with what other people consider to be the > real-world objectives of software freedom can and does change over time. [scratches head] I'm honestl

Re: [License-discuss] Evolving the License Review process for OSI

2019-05-26 Thread Rick Moen
Tom's evergreen guideline: '1) Thou shalt not excessively annoy others. 2) Thou shalt not be too easily annoyed.') Truer words, and all that. -- Rick Moen emeritus sysop/owner/builder, 1:125/27@FidoNet, The Skeptic's Board BBS (1988-1994) (which ran a

Re: [License-discuss] Evolving the License Review process for OSI

2019-05-25 Thread Rick Moen
Quoting Russell McOrmond (russellmcorm...@gmail.com): [some well-thought-out observations, ending with:] > While I have been very active in the Free Software movement since the > early 1990's, I'm not an active participant in the OSI lists partly > because this list gives me the impression the sh

Re: [License-discuss] [License-review] Evolving the License Review process for OSI

2019-05-25 Thread Rick Moen
ouncement, thus sending me a direct offlist copy plus one (inappropriately) onlist that lands in the admin queue, I won't inattentively reply-all and accidentally commit noise on-list, not noticing the svlug-announce target. -- Cheers, "I am a

Re: [License-discuss] comprehensiveness (or not) of the OSI-approved list

2019-05-23 Thread Rick Moen
exactly what I said does, as to use in those circumstances. (Horses for courses, though. As Flanders and Swann put it, IIRC, everyone gets his own gout.) [1] § 1-201(b)(10), https://www.law.cornell.edu/ucc/1/1-201 § 2-316(2), https://www.law.cornell.edu/ucc/2/2-316 -- Cheers,

Re: [License-discuss] comprehensiveness (or not) of the OSI-approved list

2019-05-23 Thread Rick Moen
r use in current implementations. I respectfully differ. (However, on further examination, I see that the remark concerns other parts of son-of-RFC 1036 that are more-evidently obsolete and problematic.) -- Cheers, "I am a member of a civilization (IAAMOAC). Step back

Re: [License-discuss] comprehensiveness (or not) of the OSI-approved list

2019-05-23 Thread Rick Moen
ah! Yes, quite so. > My confusion is rapidly waxing > For XML Schema's too taxing: > I'd use DTDs / If they had local trees -- > I think I best switch to RELAX NG. You're about to get another entry in http://linuxmafia.com/pub/humour/sigs-rickmoen.html, I'll ha

Re: [License-discuss] comprehensiveness (or not) of the OSI-approved list

2019-05-22 Thread Rick Moen
Quoting Lawrence Rosen (lro...@rosenlaw.com): > > Today, I declare that a codebase is 2-clause BSD licensed. > > As you have the obvious right to do. > > But as someone recently reminded me, and I remind this list, the OSI charter > includes the obligation to "educate the public about open sour

Re: [License-discuss] comprehensiveness (or not) of the OSI-approved list

2019-05-22 Thread Rick Moen
uding as to blind spots and errors). Thanks. (On the other hand, if I'm only belabouring the obvious, apologies for that.) -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom anger. Study how awful our ancestors had it, yet r...@linu

Re: [License-discuss] Discourse hosting

2019-03-21 Thread Rick Moen
Quoting Michael Downey (mich...@downey.net): [about whether a CDCK contract is entailed for public use of a CDCK-hosted Discourse instance:] > No, they are not. Only subject to whatever terms of service the > application operator, e.g., OSI, wants to place. > > Just like no one is entering int

Re: [License-discuss] Discourse hosting

2019-03-19 Thread Rick Moen
Quoting Thorsten Glaser (t...@mirbsd.de): [GPLv2 Discourse codebase:] > I’ve not looked at it, but many “open core” are not Free Software: > they often reject patches that add features because they would > reduce the “added value” of the commercial version, and some even > strip comments or, wors

Re: [License-discuss] Discourse hosting

2019-03-19 Thread Rick Moen
Quoting Thorsten Glaser (t...@mirbsd.de): > Rick Moen dixit: > > >I appreciate your speaking, Kevin. I continue to be curious about > >whether users would be expected to enter a contractual relationship with > [ any third party ] > >in order to participate. > &g

Re: [License-discuss] Discourse hosting

2019-03-19 Thread Rick Moen
e corporation in NYC; we just wanted to participate with LDP. So, I am curious: To participate with OSI on a hope-for CDCK-hosted, outsourced Discourse instance, would contributors need to enter into a contractual relationship with for-profit corporation CDCK? (I cannot help notice Luis replied

Re: [License-discuss] Fwd: discussion of L-R process [was Re: [License-review] Approval: Server Side Public License, Version 2 (SSPL v2)]

2019-03-19 Thread Rick Moen
ed Discourse instance, rather than OSI outsourcing that initiative, and implicitly requiring contributors to enter into a contractual relationsihip with a for-profit El Cerrito, California corporation. -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moen

Re: [License-discuss] discussion of L-R process [was Re: [License-review] Approval: Server Side Public License, Version 2 (SSPL v2)]

2019-03-15 Thread Rick Moen
-aggressive gamesmanship -- but said that _if_ there is a perceived problem of lack of clarity as to who is entitled to speak, collectively, for OSI, then the obvious remedy is identification.) -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom a

Re: [License-discuss] discussion of L-R process [was Re: [License-review] Approval: Server Side Public License, Version 2 (SSPL v2)]

2019-03-15 Thread Rick Moen
not easily distinguished from that interpretation. (Oh: Wiews expressed are mine and in no way speak for OSI, with whom I have no institutional connection.) -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom anger. Study how a

Re: [License-discuss] Intimacy in open source (SSPL and AGPL)

2019-01-22 Thread Rick Moen
Quoting Johnny A. Solbu (joh...@solbu.net): > On Tuesday 22 January 2019 21:31, Nicholas Matthew Neft Weinstock wrote: > > My e-mail isn’t adding reply bars. I’m going to put my responses in blue, > > I apologize that this will likely impact readability for some members of > > the list. > > Th

Re: [License-discuss] Intimacy in open source (SSPL and AGPL)

2019-01-22 Thread Rick Moen
y distinctive to open source (let alone (A)GPL3 workds): Any copyright-covered use of material under third-party copyright title raises it. -- Cheers, "I never quarrel with a man who buys ink by the barrel." Rick Moen

Re: [License-discuss] [License-review] Support for SSPL v2

2018-12-18 Thread Rick Moen
now it but restricts service wrapping,... ...then OSI will have declined to declare existence of a noonday midnight, or a squared circle. -- Cheers, "I never quarrel with a man who buys ink by the barrel." Rick Moen-- Rep

Re: [License-discuss] Proposed license decision process

2018-12-13 Thread Rick Moen
that OSI Certified licences that really shouldn't have been approved aren't a lingering problem, but I'd call it a small one. -- Cheers,"I never quarrel with a man who buys ink by the barrel." Rick Moen

Re: [License-discuss] Mixed 5yr non-open then fully open license

2018-07-31 Thread Rick Moen
Quoting Thorsten Glaser (t...@mirbsd.de): > The MIT licence itself requires others who distribute the work to > include a copy of the licence, so, to easen their job, you really > should include the full licence body with the work. Copyright owner may explitly waive any requirement. E.g., this c

Re: [License-discuss] Mixed 5yr non-open then fully open license

2018-07-30 Thread Rick Moen
Damn that copy'n'paste for its excessive accuracy. I meant: > So, just state as copyright holder that the work is available under the > terms of licence A starting $DATE1, and also state as copyright holder > that the work is available under the terms of licence A starting $DATE2.

Re: [License-discuss] Mixed 5yr non-open then fully open license

2018-07-30 Thread Rick Moen
-- Cheers, Romana: "I don't think we should interfere." Rick Moen The Doctor: "Interfere?" Of course we should interfere. r...@linuxmafia.com Always do what you're best at, that's what I say." McQ! (4x80)

Re: [License-discuss] Mixed 5yr non-open then fully open license

2018-07-30 Thread Rick Moen
Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom anger. Study how awful our ancestors had it, yet r...@linuxmafia.com they struggled to get you here. Repay them by appreciating McQ! (4x80) the civiliz

Re: [License-discuss] Pritunl "open source"

2018-06-21 Thread Rick Moen
Quoting B Galliart (bgal...@gmail.com): > A couple months ago, I evaluated Pritunl, the "Open Source Enterprise > Distributed OpenVPN and IPsec Server" [...] > (1) What advocacy information does the Open Source Initiative provide which > indicates it is possible to protect the commercial viabilit