[License-discuss] Generic process for removing approved licenses. Re: REMOVE AAL from list of approved licenses

[Henrik Ingo]

I would add that deprecation often implies that you should stop using a
feature/api now, because it will be removed in some future version, maybe
years from now.

For this discussion I have used deprecate as synonymous to such
notification. It's possible someone else could use it synonymously to the
end state (license either removed or moved to a list of deprecated=removed
licenses).

henrik

On Wed, Apr 1, 2020 at 7:36 AM McCoy Smith <mccoy at lexpan.law> wrote:

> "Deprecation" is used here in the computer sciencey sense:
> https://www.techopedia.com/definition/28957/deprecation
>
> "Deprecation is the process of marking attributes or features that should
> be
> avoided by users, including Web developers. Deprecation may be applied for
> various reasons, including one of the most common, which is the
> availability
> of more practical and effective alternatives."
>
> > -----Original Message-----
> > From: License-discuss <license-discuss-bounces at lists.opensource.org> On
> > Behalf Of Pamela Chestek
> > Sent: Tuesday, March 31, 2020 6:42 PM
> > To: license-discuss at lists.opensource.org
> > Subject: Re: [License-discuss] Generic process for removing approved
> > licenses. Re: REMOVE AAL from list of approved licenses
> >
> > I understand the concept of decertifying or removing, but I am very
> confused
> > by the use of the term "deprecate." The current category of licenses are:
> >
> > Popular and widely-used or with strong communities International Special
> > purpose Other/Miscellaneous Redundant Non-reusable Superseded
> > Voluntarily retired Uncategorized
> >
> > Are y'all suggesting yet another category, "deprecated"? And how does
> that
> > differ from some other categories, "non-reusable" in particular?
> > Why can't problematic licenses just be reclassified as "non-reusable"?
> >
> > Pam
> >
> > Pamela S. Chestek
> > Chestek Legal
> > PO Box 2492
> > Raleigh, NC 27602
> > pamela at chesteklegal.com
> > 919-800-8033
> > www.chesteklegal.com
> >
> > _______________________________________________
> > The opinions expressed in this email are those of the sender and not
> > necessarily those of the Open Source Initiative. Official statements by
> the
> > Open Source Initiative will be sent from an opensource.org email
> address.
> >
> > License-discuss mailing list
> > License-discuss at lists.opensource.org
> > http://lists.opensource.org/mailman/listinfo/license-
> > discuss_lists.opensource.org
>
>
> _______________________________________________
> The opinions expressed in this email are those of the sender and not
> necessarily those of the Open Source Initiative. Official statements by the
> Open Source Initiative will be sent from an opensource.org email address.
>
> License-discuss mailing list
> License-discuss at lists.opensource.org
>
> http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
>


-- 
henrik.ingo at avoinelama.fi
+358-40-5697354        skype: henrik.ingo            irc: hingo
www.openlife.cc

My LinkedIn profile: http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20200401/482360fc/attachment-0001.html>