Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-02-21 Thread Emil
I consent to relicensing any and all the contributions I have made to
the pmacct project - no matter how small these might be ^^

/ Emil

Den tors 20 feb. 2020 kl 10:27 skrev Nick Douma :

> Hi,
>
> On 08-01-2020 14:52, Job Snijders wrote:
> > We need explicit approval from all contributors, and carefully keep
> > track of those agreements. If a contributor doesn't agree or answer,
> > we'll have to re-implement the contributed functionality or remove the
> > contribution from the code base.
> >
> > REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> > ---
> >
> > If you have contributed to the pmacct project (your name may be listed
> > below), please consider a reply-all to this email expressing your
> > explicit consent (or disapproval) to change the license governing your
> > contributions to the pmacct project, to the following license:
> >
> > """
> > Permission to use, copy, modify, and distribute this software for
> > any purpose with or without fee is hereby granted, provided that the
> > above copyright notice and this permission notice appear in all
> > copies.
> >
> > THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
> > WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
> > WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
> > AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
> > DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
> > OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> > TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> > PERFORMANCE OF THIS SOFTWARE.
> > """
> >
> > ---
>
> I made a (small) contribution years ago, which was merged to the CVS/SVN
> repo by Paolo (if I remember correctly). I agree to the relicensing.
>
> 1.5.0rc3 -- 18-04-2014
>   + AMQP plugin: implemented persistent messaging via
> amqp_persistent_msg configuration directive so to protect against
> RabbitMQ restarts. Feature is courtesy by Nick Douma.
>
> Kind regards,
>
> Nick Douma
>
> ___
> pmacct-discussion mailing list
> http://www.pmacct.net/#mailinglists
>
___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-02-20 Thread Nick Douma
Hi,

On 08-01-2020 14:52, Job Snijders wrote:
> We need explicit approval from all contributors, and carefully keep
> track of those agreements. If a contributor doesn't agree or answer,
> we'll have to re-implement the contributed functionality or remove the
> contribution from the code base.
>
> REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> ---
>
> If you have contributed to the pmacct project (your name may be listed
> below), please consider a reply-all to this email expressing your
> explicit consent (or disapproval) to change the license governing your
> contributions to the pmacct project, to the following license:
>
> """
> Permission to use, copy, modify, and distribute this software for
> any purpose with or without fee is hereby granted, provided that the
> above copyright notice and this permission notice appear in all
> copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
> WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
> AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
> DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
> OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
> """
>
> ---

I made a (small) contribution years ago, which was merged to the CVS/SVN
repo by Paolo (if I remember correctly). I agree to the relicensing.

1.5.0rc3 -- 18-04-2014
  + AMQP plugin: implemented persistent messaging via
amqp_persistent_msg configuration directive so to protect against
RabbitMQ restarts. Feature is courtesy by Nick Douma.

Kind regards,

Nick Douma

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-12 Thread Stephen Clark

I am too.

On 1/11/20 3:38 PM, Mike Jager wrote:

On 9 Jan 2020, at 2:52, Job Snijders wrote:


We need explicit approval from all contributors, and carefully keep
track of those agreements. If a contributor doesn't agree or answer,
we'll have to re-implement the contributed functionality or remove the
contribution from the code base.

REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
---

If you have contributed to the pmacct project (your name may be listed
below), please consider a reply-all to this email expressing your
explicit consent (or disapproval) to change the license governing your
contributions to the pmacct project, to the following license:

 """
 Permission to use, copy, modify, and distribute this software for
 any purpose with or without fee is hereby granted, provided that the
 above copyright notice and this permission notice appear in all
 copies.

 THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
 WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
 WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
 AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
 DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
 OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
 TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 PERFORMANCE OF THIS SOFTWARE.
 """

---

I'm happy to change the license governing my contributions to the above.

Cheers
Mike

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists




--

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)

"Beer is proof God loves us and wants us to be happy!" (Ben Franklin)


___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-11 Thread Mike Jager
On 9 Jan 2020, at 2:52, Job Snijders wrote:

> We need explicit approval from all contributors, and carefully keep
> track of those agreements. If a contributor doesn't agree or answer,
> we'll have to re-implement the contributed functionality or remove the
> contribution from the code base.
>
> REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> ---
>
> If you have contributed to the pmacct project (your name may be listed
> below), please consider a reply-all to this email expressing your
> explicit consent (or disapproval) to change the license governing your
> contributions to the pmacct project, to the following license:
>
> """
> Permission to use, copy, modify, and distribute this software for
> any purpose with or without fee is hereby granted, provided that the
> above copyright notice and this permission notice appear in all
> copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
> WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
> AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
> DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
> OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
> """
>
> ---

I'm happy to change the license governing my contributions to the above.

Cheers
Mike

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-09 Thread Camilo Cardona
Hi all,

I agree to the relicensing of pmacct to the mentioned license, including all my 
contributions to it.

I think that moving to a more permissive license makes sense, understanding 
that the maintainers do not feel the need to  enforce any of the restrictions 
of the current one.

Cheers,
Camilo Cardona
___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-09 Thread Paolo Lucente


Hi Karl and Lennert, Community,

Thanks very much for your comments and for the opportunity you are
giving me to address them. 

I'd like to comment publicly - so that we can cast this in stone and
have it archvied for time to tell - that there are no hidden reasons,
secret plans or favouritism behind this initiative and the motivations
expressed. The reasons stated are the real reasons.

In the very early days of starting the project i picked a license semi
randomly, that is, after having been recommended so. Many years passed
and i focused solely on core develoment of pmacct. Am i a believer of
restrictive licenses? No, i've never been. I personally believe in
innovating and looking forward rather than making sure nobody is
'copying' (pass me the simplistic term) pmacct - i think by doing
open-source that is simply a given. So one day happened that we had
this kind of conversation with Job and decided to attempt to re-align
licensing.

Related to the above, I also believe that people so far have contributed
to pmacct not out of desire to comply with the license terms but because
they thought that sharing their code would benefit all parties involved.

The other point that Job raised, let's call it the mortality one, i
truly believe it's self-explanatory. I may perhaps add that over the
course of 17 years intellectual thinking of a person may evolve.

One more reason that perhaps did not emerge is - again on a pure
intelllectual level - the wish to maximize who uses pmacct, including
inside their products. Licensing has several time risen as a concern
for integrating pmacct in 3rd parties so I hope we can now put that to
rest.

Finally, I too consent relicense my pmacct work under the proposed
license. I'm excited to see this change happen! :-)

Paolo
 
On Wed, Jan 08, 2020 at 05:05:48PM +0200, Lennert Buytenhek wrote:
> On Wed, Jan 08, 2020 at 08:53:57AM -0600, Karl O. Pinc wrote:
> 
> > > Summary: The pmacct project is looking to relicense its code from the
> > > current GPL license to a more liberal BSD-style license.
> > > 
> > > 1) Faced with our own mortality, it became clear that succession
> > >planning is of paramount importance for this project's continued
> > >success. We contemplated what happens in context of intellectual
> > >property rights should one of pmacct's contributors pass away, and
> > >realized potential heirs won't necessarily desire involvement in this
> > >open source project, potentially hampering changes to intellectual
> > >property policies in the project's future. 
> > > 
> > > 2) We suspect there are entities who violate the terms of pmacct's
> > >current GPL license, but at the same time we don't wish to litigate.
> > >Instead of getting infringers to change their behavior, relicensing
> > >the project could be another way to resolve the potential for
> > >conflict: we see benefits to removing rules we don't plan on
> > >enforcing anyway.
> > 
> > On Wed, 8 Jan 2020 16:02:35 +0200
> > Lennert Buytenhek  wrote:
> > 
> > > Although the stated reasoning
> > > for the relicensing effort feels somewhat specious to me, 
> > 
> > I agree.  (Disclaimer: I'm not a contributor.)
> > 
> > 1) If we wanted to change the licensing, we couldn't, after we're
> > dead.
> > 
> > 2) People are violating our rights and we don't want to do
> > anything about it.
> > 
> > I don't want to argue one way or another but it would be nice
> > to have a real reason.  There are good reasons available,
> > all the way down to "I wrote most of it and I changed my mind."
> > 
> > Even if there's some commercial entity that wants to sell
> > pmacct in their product and won't because of the licensing,
> > it would be nice to know this.  Especially knowing who.
> > (E.g. We know that Amazon uses PostgreSQL as the basis
> > of their RDS database product, and does not contribute
> > back as far as I can tell.)  It'd be nice to know who 
> > the contributors are helping.
> 
> FWIW, I fully agree with this analysis.  I chose to agree with the
> relicensing anyway as I don't think this is an important enough
> battle to fight.   (If someone were to ask me to relicense my Linux
> kernel contributions under a closed-source-able license, I would be
> a lot more upset.)
> 
> ___
> pmacct-discussion mailing list
> http://www.pmacct.net/#mailinglists

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Aaron Finney
Hello,

I happily consent to the relicensing as proposed. Thank you for your
continued dedication to ensuring the long-term viability of the project.
What an amazing community.

Aaron

On Wed, Jan 8, 2020, 5:54 AM Job Snijders  wrote:

> Dear all,
>
> Summary: The pmacct project is looking to relicense its code from the
> current GPL license to a more liberal BSD-style license.
>
> A few weeks ago I had the pleasure to spend some face time with Paolo,
> which allowed for in-depth discussion about pmacct's current trajectory
> and bright future. We concluded it would be in the best interest of the
> pmacct project to attempt to relicense all code under a more permissive
> BSD-style license, for mainly two reasons:
>
> 1) Faced with our own mortality, it became clear that succession
>planning is of paramount importance for this project's continued
>success. We contemplated what happens in context of intellectual
>property rights should one of pmacct's contributors pass away, and
>realized potential heirs won't necessarily desire involvement in this
>open source project, potentially hampering changes to intellectual
>property policies in the project's future.
>
> 2) We suspect there are entities who violate the terms of pmacct's
>current GPL license, but at the same time we don't wish to litigate.
>Instead of getting infringers to change their behavior, relicensing
>the project could be another way to resolve the potential for
>conflict: we see benefits to removing rules we don't plan on
>enforcing anyway.
>
> Going forward, the preferred license under which we encourge people to
> contribute new work is a variant of the ISC license (also used by the
> OpenBSD project). The license template (to be used in file headers) can
> be found here:
>
> https://github.com/pmacct/pmacct/blob/master/LICENSE.template
>
> We need explicit approval from all contributors, and carefully keep
> track of those agreements. If a contributor doesn't agree or answer,
> we'll have to re-implement the contributed functionality or remove the
> contribution from the code base.
>
> REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> ---
>
> If you have contributed to the pmacct project (your name may be listed
> below), please consider a reply-all to this email expressing your
> explicit consent (or disapproval) to change the license governing your
> contributions to the pmacct project, to the following license:
>
> """
> Permission to use, copy, modify, and distribute this software for
> any purpose with or without fee is hereby granted, provided that the
> above copyright notice and this permission notice appear in all
> copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
> WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
> AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
> DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
> OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
> """
>
> ---
>
> The next action in this process will be to individually follow up with
> all contributors who didn't respond to the above request.
>
> Once the relicensing effort has been completed, we'll tag the resulting
> code base as pmacct version 2.0.0 and celebrate! Pmacct has many great
> years ahead of itself; Paolo's enthusiasm to do so is evident in this
> interview video :-) https://www.youtube.com/watch?v=QqmOcMAtGDM
>
> Please feel free to raise any questions you may have on the
> pmacct-discussion@pmacct.net list, or privately with me and/or Paolo.
>
> Kind regards,
>
> Job Snijders
>
>
> DRAFT LIST OF KNOWN PMACCT AUTHORS (based on 'git shortlog -sen')
> =
>
> Commits  Author 
>2921  Paolo Lucente 
>  52  Marc Sune 
>  20  Corentin Néau 
>  17  Vincent Bernat 
>  14  Job Snijders 
>  12  Matthias Arnold 
>   9  Raphaël P. Barazzutti 
>   9  Claudio Ortega 
>   8  Jonas Jensen 
>   8  Matthias Arnold 
>   8  Tim LaBerge 
>   7  Jared Mauch 
>   7  vittoriofoschi 
>   7  Camilo Cardona 
>   5  Aaron Finney 
>   5  Vittorio Foschi 
>   4  vphatarp 
>   3  Alexander Brusilov 
>   3  Emil Palm 
>   3  Dusan Migra 
>   3  Dan Berger 
>   3  Markus Weber 
>   2  Tim LaBerge 
>   2  Guy Lowe 
>   2  Hidde van der Heide 
>   2  Jim Westfall 
>   2  Lee Yongjae 
>   2  Lennert Buytenhek 
>   2  Matthieu Texier 
>   2  Miki Takata 
>   2  Pierre Dubouilh 
>   2  Tiago Gomes 
>   2  Vadim Tk 
>   3  Thomas Graf 
>   1  Junpei YOSHINO 

Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Hidde van der Heide

On Wed, Jan 08, 2020 at 02:52:42PM +0100, Job Snijders wrote:

REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
---

If you have contributed to the pmacct project (your name may be listed
below), please consider a reply-all to this email expressing your
explicit consent (or disapproval) to change the license governing your
contributions to the pmacct project, to the following license:

   """
   Permission to use, copy, modify, and distribute this software for
   any purpose with or without fee is hereby granted, provided that the
   above copyright notice and this permission notice appear in all
   copies.

   THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
   WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
   WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
   AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
   DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
   OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
   TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
   PERFORMANCE OF THIS SOFTWARE.
   """

---


I consent to the change of license for the project and in particular
my single line contribution.

- Hidde


signature.asc
Description: PGP signature
___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Karl O. Pinc
Hello,

I also consent to relicensing any and all the contributions I have made
to the pmacct project.  (I may have sent documentation patches in via email
at some point.  I forgot about those.)

Regards,

Karl 
Free Software:  "You don't pay back, you pay forward."
 -- Robert A. Heinlein

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Markus Weber
I consent to relicensing any and all the contributions I have made to 
the pmacct project - no matter how small these had been ;-)


Markus

Am 08.01.2020 um 14:52 schrieb Job Snijders:

Dear all,

Summary: The pmacct project is looking to relicense its code from the
current GPL license to a more liberal BSD-style license.

A few weeks ago I had the pleasure to spend some face time with Paolo,
which allowed for in-depth discussion about pmacct's current trajectory
and bright future. We concluded it would be in the best interest of the
pmacct project to attempt to relicense all code under a more permissive
BSD-style license, for mainly two reasons:

1) Faced with our own mortality, it became clear that succession
planning is of paramount importance for this project's continued
success. We contemplated what happens in context of intellectual
property rights should one of pmacct's contributors pass away, and
realized potential heirs won't necessarily desire involvement in this
open source project, potentially hampering changes to intellectual
property policies in the project's future.

2) We suspect there are entities who violate the terms of pmacct's
current GPL license, but at the same time we don't wish to litigate.
Instead of getting infringers to change their behavior, relicensing
the project could be another way to resolve the potential for
conflict: we see benefits to removing rules we don't plan on
enforcing anyway.

Going forward, the preferred license under which we encourge people to
contribute new work is a variant of the ISC license (also used by the
OpenBSD project). The license template (to be used in file headers) can
be found here:

 https://github.com/pmacct/pmacct/blob/master/LICENSE.template

We need explicit approval from all contributors, and carefully keep
track of those agreements. If a contributor doesn't agree or answer,
we'll have to re-implement the contributed functionality or remove the
contribution from the code base.

REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
---

If you have contributed to the pmacct project (your name may be listed
below), please consider a reply-all to this email expressing your
explicit consent (or disapproval) to change the license governing your
contributions to the pmacct project, to the following license:

 """
 Permission to use, copy, modify, and distribute this software for
 any purpose with or without fee is hereby granted, provided that the
 above copyright notice and this permission notice appear in all
 copies.

 THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
 WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
 WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
 AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
 DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
 OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
 TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 PERFORMANCE OF THIS SOFTWARE.
 """

---

The next action in this process will be to individually follow up with
all contributors who didn't respond to the above request.

Once the relicensing effort has been completed, we'll tag the resulting
code base as pmacct version 2.0.0 and celebrate! Pmacct has many great
years ahead of itself; Paolo's enthusiasm to do so is evident in this
interview video :-) https://www.youtube.com/watch?v=QqmOcMAtGDM

Please feel free to raise any questions you may have on the
pmacct-discussion@pmacct.net list, or privately with me and/or Paolo.

Kind regards,

Job Snijders


DRAFT LIST OF KNOWN PMACCT AUTHORS (based on 'git shortlog -sen')
=
  
Commits  Author 

2921  Paolo Lucente 
  52  Marc Sune 
  20  Corentin Néau 
  17  Vincent Bernat 
  14  Job Snijders 
  12  Matthias Arnold 
   9  Raphaël P. Barazzutti 
   9  Claudio Ortega 
   8  Jonas Jensen 
   8  Matthias Arnold 
   8  Tim LaBerge 
   7  Jared Mauch 
   7  vittoriofoschi 
   7  Camilo Cardona 
   5  Aaron Finney 
   5  Vittorio Foschi 
   4  vphatarp 
   3  Alexander Brusilov 
   3  Emil Palm 
   3  Dusan Migra 
   3  Dan Berger 
   3  Markus Weber 
   2  Tim LaBerge 
   2  Guy Lowe 
   2  Hidde van der Heide 
   2  Jim Westfall 
   2  Lee Yongjae 
   2  Lennert Buytenhek 
   2  Matthieu Texier 
   2  Miki Takata 
   2  Pierre Dubouilh 
   2  Tiago Gomes 
   2  Vadim Tk 
   3  Thomas Graf 
   1  Junpei YOSHINO 
   1  root 
   1  Mehul Prajapati 
   1  Mike Jager 
   1  rouba002 
   1  Nimrod 
   1  Jeroen Roovers 
   1  Paweł Małachowski 
   1  Pier Carlo Chiodi 
   1  

Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Lennert Buytenhek
On Wed, Jan 08, 2020 at 08:53:57AM -0600, Karl O. Pinc wrote:

> > Summary: The pmacct project is looking to relicense its code from the
> > current GPL license to a more liberal BSD-style license.
> > 
> > 1) Faced with our own mortality, it became clear that succession
> >planning is of paramount importance for this project's continued
> >success. We contemplated what happens in context of intellectual
> >property rights should one of pmacct's contributors pass away, and
> >realized potential heirs won't necessarily desire involvement in this
> >open source project, potentially hampering changes to intellectual
> >property policies in the project's future. 
> > 
> > 2) We suspect there are entities who violate the terms of pmacct's
> >current GPL license, but at the same time we don't wish to litigate.
> >Instead of getting infringers to change their behavior, relicensing
> >the project could be another way to resolve the potential for
> >conflict: we see benefits to removing rules we don't plan on
> >enforcing anyway.
> 
> On Wed, 8 Jan 2020 16:02:35 +0200
> Lennert Buytenhek  wrote:
> 
> > Although the stated reasoning
> > for the relicensing effort feels somewhat specious to me, 
> 
> I agree.  (Disclaimer: I'm not a contributor.)
> 
> 1) If we wanted to change the licensing, we couldn't, after we're
> dead.
> 
> 2) People are violating our rights and we don't want to do
> anything about it.
> 
> I don't want to argue one way or another but it would be nice
> to have a real reason.  There are good reasons available,
> all the way down to "I wrote most of it and I changed my mind."
> 
> Even if there's some commercial entity that wants to sell
> pmacct in their product and won't because of the licensing,
> it would be nice to know this.  Especially knowing who.
> (E.g. We know that Amazon uses PostgreSQL as the basis
> of their RDS database product, and does not contribute
> back as far as I can tell.)  It'd be nice to know who 
> the contributors are helping.

FWIW, I fully agree with this analysis.  I chose to agree with the
relicensing anyway as I don't think this is an important enough
battle to fight.   (If someone were to ask me to relicense my Linux
kernel contributions under a closed-source-able license, I would be
a lot more upset.)

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Karl O. Pinc
> Summary: The pmacct project is looking to relicense its code from the
> current GPL license to a more liberal BSD-style license.

> 1) Faced with our own mortality, it became clear that succession
>planning is of paramount importance for this project's continued
>success. We contemplated what happens in context of intellectual
>property rights should one of pmacct's contributors pass away, and
>realized potential heirs won't necessarily desire involvement in this
>open source project, potentially hampering changes to intellectual
>property policies in the project's future. 
> 
> 2) We suspect there are entities who violate the terms of pmacct's
>current GPL license, but at the same time we don't wish to litigate.
>Instead of getting infringers to change their behavior, relicensing
>the project could be another way to resolve the potential for
>conflict: we see benefits to removing rules we don't plan on
>enforcing anyway.

On Wed, 8 Jan 2020 16:02:35 +0200
Lennert Buytenhek  wrote:

> Although the stated reasoning
> for the relicensing effort feels somewhat specious to me, 

I agree.  (Disclaimer: I'm not a contributor.)

1) If we wanted to change the licensing, we couldn't, after we're
dead.

2) People are violating our rights and we don't want to do
anything about it.

I don't want to argue one way or another but it would be nice
to have a real reason.  There are good reasons available,
all the way down to "I wrote most of it and I changed my mind."

Even if there's some commercial entity that wants to sell
pmacct in their product and won't because of the licensing,
it would be nice to know this.  Especially knowing who.
(E.g. We know that Amazon uses PostgreSQL as the basis
of their RDS database product, and does not contribute
back as far as I can tell.)  It'd be nice to know who 
the contributors are helping.

Regards,

Karl 
Free Software:  "You don't pay back, you pay forward."
 -- Robert A. Heinlein

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists


Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Vincent Bernat
 ❦  8 janvier 2020 14:52 +01, Job Snijders :

> REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> ---
>
> If you have contributed to the pmacct project (your name may be listed
> below), please consider a reply-all to this email expressing your
> explicit consent (or disapproval) to change the license governing your
> contributions to the pmacct project, to the following license:
>
> """
> Permission to use, copy, modify, and distribute this software for
> any purpose with or without fee is hereby granted, provided that the
> above copyright notice and this permission notice appear in all
> copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
> WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
> AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
> DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
> OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
> """
>
> ---

I am OK with the change.
-- 
Keep it simple to make it faster.
- The Elements of Programming Style (Kernighan & Plauger)

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Will Dowling
> On 8 Jan 2020, at 9:52 pm, Job Snijders  wrote:
> 
> REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> ---
> 
> If you have contributed to the pmacct project (your name may be listed
> below), please consider a reply-all to this email expressing your
> explicit consent (or disapproval) to change the license governing your
> contributions to the pmacct project, to the following license:
> 
>"""
>Permission to use, copy, modify, and distribute this software for
>any purpose with or without fee is hereby granted, provided that the
>above copyright notice and this permission notice appear in all
>copies.
> 
>THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
>WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
>WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
>AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
>DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
>OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
>TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
>PERFORMANCE OF THIS SOFTWARE.
>"""
> 
> ---

I consent to relicensing any and all contributions I have made to the pmacct 
project.

I’m not identified in your original list, as my patches were submitted to the 
mailing list and merged in by Paolo (my foggy memory suggests GitHub used to be 
a mirror only). Might be worth a trawl through the mailing list history for 
additional patch contributors.

In any case this applies to the following patches made for the 1.5.2 release:

! fix, amqp_common.c: Content type was only specified for messages published
 when the amqp_persistent_msg configuration option is specified. This info
 should always be applied to describe the payload of the message. Patch is
 courtesy by Will Dowling.
! fix, amqp_plugin.c: generate an error on compile if --enable-rabbitmq is
 specified without --enable-jansson. It's clear in the documentation that
 both are required for AMQP support, but if built without jansson it will
 silently not publish messages to AMQP. Patch is courtesy by Will Dowling.
! fix, amqp_common.c: modified the content type to "application/json" in
 line with RFC4627. Patch is courtesy by Will Dowling.

Cheers :)


Will Dowling

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Re: [pmacct-discussion] effort to relicense pmacct from GPL to a BSD-style license

2020-01-08 Thread Lennert Buytenhek
Hello!


On Wed, Jan 08, 2020 at 02:52:42PM +0100, Job Snijders wrote:

> REQUEST TO THE PMACCT CONTRIBUTOR COMMUNITY
> ---
> 
> If you have contributed to the pmacct project (your name may be listed
> below), please consider a reply-all to this email expressing your
> explicit consent (or disapproval) to change the license governing your
> contributions to the pmacct project, to the following license:
> 
> """
> Permission to use, copy, modify, and distribute this software for
> any purpose with or without fee is hereby granted, provided that the
> above copyright notice and this permission notice appear in all
> copies.
> 
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
> WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
> AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
> DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
> OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
> """
> 
> ---

(My name is in the contributor list.)  Although the stated reasoning
for the relicensing effort feels somewhat specious to me, I consent
with relicensing of any and all contributions I have made to the
pmacct project to whatever open source license the project leadership
sees fit, as I am of the opinion that not fragmenting the pmacct
development community is the higher goal here.


Cheers,
Lennert

___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists