gmane.linux.debian.devel.legal archive

372 archived articles, newest first (page 2 of 4). Latest articles →

Re: On the need for a censorship API for legal compliance reasons in some countries and U.S. states
Tue, 17 Mar 2026 16:00:54 -0500
Adenix NPSP <[email protected]> • #38856
Re: License conditions for a specific file in praat
Tue, 17 Mar 2026 11:48:15 -0700
Soren Stoutner <[email protected]> • #38855
Re: License conditions for a specific file in praat
Tue, 17 Mar 2026 19:37:03 +0100
Michael Stehmann <[email protected]> • #38854
Re: License conditions for a specific file in praat
Tue, 17 Mar 2026 12:19:02 -0600
Gunnar Wolf <[email protected]> • #38853
Re: On the need for a censorship API for legal compliance reasons in some countries and U.S. states
Tue, 17 Mar 2026 18:30:03 +0100
Marco Trevisan via ubuntu-devel <[email protected]> • #38852
Re: On the need for a censorship API for legal compliance reasons in some countries and U.S. states
Tue, 17 Mar 2026 18:20:08 +0100
Marco Trevisan via ubuntu-devel <[email protected]> • #38851
Re: License conditions for a specific file in praat
Tue, 17 Mar 2026 17:56:19 +0100
Michael Stehmann <[email protected]> • #38850
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Tue, 17 Mar 2026 17:30:54 +0100
Michael Stehmann <[email protected]> • #38849
License conditions for a specific file in praat
Tue, 17 Mar 2026 15:36:58 +0100
Rafael Laboissière <[email protected]> • #38848
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Tue, 17 Mar 2026 10:16:28 +0000
Simon McVittie <[email protected]> • #38847
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Tue, 17 Mar 2026 07:41:41 +0100
Mechtilde Stehmann <[email protected]> • #38846
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 16 Mar 2026 18:42:34 -0500
Adenix NPSP <[email protected]> • #38845
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 16 Mar 2026 19:31:18 -0400
Aaron Rainbolt <[email protected]> • #38844
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Mon, 16 Mar 2026 15:22:25 -0700
Soren Stoutner <[email protected]> • #38843
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Mon, 16 Mar 2026 14:40:03 -0700
Luke Faraone <[email protected]> • #38842
Re: ansible-runner: guidance requested on possible Apache-2.0/GPL-3.0 incompatibility
Mon, 16 Mar 2026 20:45:38 +0100
Sakirnth Nagarasa <[email protected]> • #38841
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Mon, 16 Mar 2026 20:47:16 +0100
Mechtilde Stehmann <[email protected]> • #38840
Re: GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Mon, 16 Mar 2026 12:15:35 -0700
Soren Stoutner <[email protected]> • #38839
GPL-3+ licensed test fixture (SVG/metadata) in BSD-3 project
Sun, 15 Mar 2026 11:06:12 +0100
"Carl Keinath" <[email protected]> • #38838
Re: ansible-runner: guidance requested on possible Apache-2.0/GPL-3.0 incompatibility
Sat, 14 Mar 2026 11:05:24 -0700
Soren Stoutner <[email protected]> • #38837
ansible-runner: guidance requested on possible Apache-2.0/GPL-3.0 incompatibility
Sat, 14 Mar 2026 11:15:46 +0100
Sakirnth Nagarasa <[email protected]> • #38836
ansible-runner: guidance requested on possible Apache-2.0/GPL-3.0 incompatibility
Sat, 14 Mar 2026 11:15:31 +0100
Sakirnth Nagarasa <[email protected]> • #38835
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Fri, 13 Mar 2026 11:26:50 -0600
Gunnar Wolf <[email protected]> • #38834
Re: Age Verification
Thu, 12 Mar 2026 23:09:31 +0100
Joerg Jaspert <[email protected]> • #38833
Re: Age Verification
Wed, 11 Mar 2026 19:12:40 -0500
Adenix NPSP <[email protected]> • #38832
Re: Age Verification
Wed, 11 Mar 2026 16:59:52 -0700
Jamie Null <[email protected]> • #38831
Re: Age Verification
Wed, 11 Mar 2026 17:07:00 -0500
Adenix NPSP <[email protected]> • #38830
Re: Age Verification
Wed, 11 Mar 2026 17:56:05 -0400
"Vincent F. Heuser Jr." <[email protected]> • #38829
Age Verification
Wed, 11 Mar 2026 17:18:44 -0400
Shaugn Nell <[email protected]> • #38828
Re: Age Verification
Wed, 11 Mar 2026 16:26:07 -0500
Adenix NPSP <[email protected]> • #38827
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 10 Mar 2026 23:09:24 -0500
Adenix NPSP <[email protected]> • #38826
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 10 Mar 2026 20:59:05 -0700
Jamie Null <[email protected]> • #38825
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 10 Mar 2026 16:04:08 -0500
Adenix NPSP <[email protected]> • #38824
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 10 Mar 2026 13:58:20 -0600
"Jeremy Soller" <[email protected]> • #38823
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 10 Mar 2026 03:33:56 +0000
Artur Manuel <[email protected]> • #38822
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 9 Mar 2026 22:11:57 -0400
Aaron Rainbolt <[email protected]> • #38821
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 9 Mar 2026 22:02:28 -0400
Lucas Holt <[email protected]> • #38820
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 09 Mar 2026 19:39:52 -0600
"Jeremy Soller" <[email protected]> • #38819
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Thu, 5 Mar 2026 20:46:46 -0500
Aaron Rainbolt <[email protected]> • #38818
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Wed, 04 Mar 2026 15:39:57 -0700
Soren Stoutner <[email protected]> • #38817
Re: Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Wed, 4 Mar 2026 15:30:58 -0600
Adenix NPSP <[email protected]> • #38816
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Wed, 4 Mar 2026 14:43:45 -0500
"Vincent F. Heuser Jr." <[email protected]> • #38815
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Wed, 4 Mar 2026 09:52:54 -0600
Adenix NPSP <[email protected]> • #38814
Re: On the need for a censorship API for legal compliance reasons in some countries and U.S. states
Wed, 4 Mar 2026 12:38:23 +0000
"Personal (disroot.org)" <[email protected]> • #38813
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Wed, 4 Mar 2026 11:51:24 +0100
Jean-Baptiste Lallement <[email protected]> • #38812
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Wed, 04 Mar 2026 09:08:48 +0100
Moritz Schlarb <[email protected]> • #38811
On the need for a censorship API for legal compliance reasons in some countries and U.S. states
Tue, 3 Mar 2026 20:38:08 -0800
FloofyWolf <[email protected]> • #38810
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 3 Mar 2026 19:39:16 -0500
Aaron Rainbolt <[email protected]> • #38809
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 3 Mar 2026 19:32:00 -0500
Aaron Rainbolt <[email protected]> • #38808
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 3 Mar 2026 16:48:19 +0100
Heinrich Schuchardt via ubuntu-devel <[email protected]> • #38807
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Tue, 3 Mar 2026 15:56:03 +0100
Aigars Mahinovs <[email protected]> • #38806
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 2 Mar 2026 10:36:52 -0800
Danielle Foré <[email protected]> • #38805
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Mon, 02 Mar 2026 07:08:19 +0000
Stephan Verbücheln <[email protected]> • #38804
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 17:10:40 -0500
Aaron Rainbolt <[email protected]> • #38803
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 14:02:56 -0800
Jamie Null <[email protected]> • #38802
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 01 Mar 2026 16:46:20 -0500
Christopher Warner <[email protected]> • #38801
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 16:26:30 -0500
"Vincent F. Heuser Jr." <[email protected]> • #38800
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 16:21:34 -0500
Aaron Rainbolt <[email protected]> • #38799
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 16:08:37 -0500
Aaron Rainbolt <[email protected]> • #38798
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 21:51:15 +0100
Tomáš Zíma <[email protected]> • #38797
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 15:53:23 -0500
Aaron Rainbolt <[email protected]> • #38796
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 15:42:56 -0500
Aaron Rainbolt <[email protected]> • #38795
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 20:23:05 +0000
David Edmundson <[email protected]> • #38794
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 12:21:17 -0800
Danielle Foré <[email protected]> • #38793
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 15:12:09 -0500
"Vincent F. Heuser Jr." <[email protected]> • #38792
Re: On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 15:13:13 -0500
Aaron Rainbolt <[email protected]> • #38791
On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states
Sun, 1 Mar 2026 14:48:00 -0500
Aaron Rainbolt <[email protected]> • #38790
Re: Distribution of CDDL binaries in contrib
Sat, 28 Feb 2026 19:55:43 +0100
Bastian Blank <[email protected]> • #38789
Distribution of CDDL binaries in contrib
Sat, 28 Feb 2026 17:43:17 +0000
Jarl Gullberg <[email protected]> • #38788
Re: Updating the PHP license
Fri, 27 Feb 2026 23:48:13 +0100
Francesco Poli <[email protected]> • #38787
Re: Updating the PHP license
Thu, 26 Feb 2026 23:13:23 -0600
Ben Ramsey <[email protected]> • #38786
Re: Software implementing patented techniques
Sun, 15 Feb 2026 16:30:33 +0100
Simon Josefsson <[email protected]> • #38785
Re: Software implementing patented techniques
Sat, 14 Feb 2026 13:47:30 -0800
Don Armstrong <[email protected]> • #38784
Re: Software implementing patented techniques
Sat, 14 Feb 2026 21:40:02 +0100
Simon Josefsson <[email protected]> • #38783
Re: Software implementing patented techniques
Sat, 14 Feb 2026 11:38:25 -0800
Don Armstrong <[email protected]> • #38782
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Sun, 15 Feb 2026 03:44:01 +0900
Changwoo Ryu <[email protected]> • #38781
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Fri, 13 Feb 2026 21:42:46 +0100
Gioele Barabucci <[email protected]> • #38780
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Fri, 13 Feb 2026 13:37:25 -0700
Soren Stoutner <[email protected]> • #38779
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Fri, 13 Feb 2026 20:57:38 +0100
Gioele Barabucci <[email protected]> • #38778
Re: Software implementing patented techniques
Tue, 10 Feb 2026 17:23:42 +0100
Simon Josefsson <[email protected]> • #38777
Re: Software implementing patented techniques
Tue, 10 Feb 2026 13:31:58 +0200
Andrius Merkys <[email protected]> • #38776
Re: Software implementing patented techniques
Tue, 10 Feb 2026 11:18:37 +0000
Simon McVittie <[email protected]> • #38775
Software implementing patented techniques
Tue, 10 Feb 2026 12:39:55 +0200
Andrius Merkys <[email protected]> • #38774
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Fri, 30 Jan 2026 10:27:50 -0800
Dave Crossland <[email protected]> • #38773
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Thu, 29 Jan 2026 16:17:47 -0700
Soren Stoutner <[email protected]> • #38772
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Thu, 29 Jan 2026 07:38:10 -0500
Daniel Hakimi <[email protected]> • #38771
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Thu, 29 Jan 2026 09:41:19 -0000 (UTC)
Sune Vuorela <[email protected]> • #38770
Re: SIL OFL 1.1 plus "reserved font name" is DFSG?
Thu, 29 Jan 2026 14:50:38 +0900
Charles Plessy <[email protected]> • #38769
SIL OFL 1.1 plus "reserved font name" is DFSG?
Wed, 28 Jan 2026 22:14:39 -0500
Nicholas D Steeves <[email protected]> • #38768
Re: BSD-4-clause with different development organizations
Mon, 12 Jan 2026 09:20:50 +0100
Simon Josefsson <[email protected]> • #38767
Re: BSD-4-clause with different development organizations
Sat, 10 Jan 2026 15:26:47 -0700
Soren Stoutner <[email protected]> • #38766
BSD-4-clause with different development organizations
Sat, 10 Jan 2026 23:20:44 +0100
Peter Wienemann <[email protected]> • #38765
RE
Wed, 31 Dec 2025 07:51:38 +0000
Kristalina Georgieva <[email protected]> • #38764
Re: Question about icons related to a trademark in a package
Tue, 23 Dec 2025 14:25:07 -0700
Soren Stoutner <[email protected]> • #38763
Re: Question about icons related to a trademark in a package
Tue, 23 Dec 2025 22:22:00 +0100
Fabio Fantoni <[email protected]> • #38762
Re: Question about icons related to a trademark in a package
Tue, 23 Dec 2025 13:23:32 -0700
Soren Stoutner <[email protected]> • #38761
Re: Question about icons related to a trademark in a package
Tue, 23 Dec 2025 20:31:29 +0100
Fabio Fantoni <[email protected]> • #38760
Re: Question about icons related to a trademark in a package
Tue, 23 Dec 2025 19:38:15 +0100
Francesco Poli <[email protected]> • #38759
Re: Question about icons related to a trademark in a package
Tue, 23 Dec 2025 11:04:31 -0700
Soren Stoutner <[email protected]> • #38758
Question about icons related to a trademark in a package
Tue, 23 Dec 2025 15:47:10 +0100
Fabio Fantoni <[email protected]> • #38757
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.