Talk:Proprietary software

message: Hello fellow Wikipedians,
I have just added archive links to  on Proprietary software. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20081028213407/http://ec.europa.eu/comm/competition/antitrust/cases/decisions/37792/en.pdf to http://ec.europa.eu/comm/competition/antitrust/cases/decisions/37792/en.pdf
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers.—cyberbot IITalk to my owner:Online 22:54, 24 January 2016 (UTC)
replies: text: Got some SUN vs. MS PDF, okay. –Be..anyone 💩 18:03, 12 April 2016 (UTC)
thread_title:  External links modified 

message: There doesn't seem to be a reason to have both articles. I will do the merge within a year if there are no objections. Anyone can feel free to do it sooner if it seems like a good idea. ~Kvng (talk) 20:05, 3 June 2022 (UTC)
replies: text: Where would you put Licensed Internal Code (LIC) such as Coupling Facility Control Code (CFCC) and millicode? --Shmuel (Seymour J.) Metz Username:Chatul (talk) 13:25, 6 June 2022 (UTC)
replies: text: Actually, it isn't. Most firmware these days does not involve horizontal microcode. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 13:41, 2 September 2022 (UTC)
thread_title:  Merge from [[Proprietary firmware]] 

message: An editor has identified a potential problem with the redirect :Proprietary saftware and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 September 22#Proprietary saftware until a consensus is reached, and readers of this page are welcome to contribute to the discussion.   -- Tamzin[cetacean needed] (she|they|xe) 20:55, 22 September 2022 (UTC)
thread_title:  "Proprietary saftware" listed at [[Wikipedia:Redirects for discussion|Redirects for discussion]] 

message: This is not how "non-free" is defined: non-free means that you have failed the definition of free software in any way, such as by requiring non-commercial use (violates "freedom to use for any purpose" and analogous principles). For example, Aladdin Free Public License is classified non-free by all 4 organizations in the infobox. Non-free maps to the "Non-Open Licenses" part on the table.  
And proprietary also covers more than "closed-source". Source-available software can retain the intellectual monopoly (hence proprietary), but they let you look, so it's not closed. Artoria2e5 🌉 06:39, 12 August 2023 (UTC)
replies: text: I bet I can make this better somehow. Gotta be BOLD! Artoria2e5 🌉 06:42, 12 August 2023 (UTC)
thread_title:  Non-free isn't just proprietary 

message: The redirect Privative software has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at  until a consensus is reached.  Isla🏳️‍⚧ 11:05, 15 May 2024 (UTC)
thread_title:  "[[:Privative software]]" listed at [[Wikipedia:Redirects for discussion|Redirects for discussion]] 

message: The redirect Privative software has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at  until a consensus is reached.  Isla🏳️‍⚧ 11:07, 15 May 2024 (UTC)
thread_title:  "[[:Privative software]]" listed at [[Wikipedia:Redirects for discussion|Redirects for discussion]]