From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Super Long Term ... Support or Maintenance?
Date: Tue, 8 Nov 2016 12:08:42 +0100 [thread overview]
Message-ID: <5821B23A.90007@codethink.co.uk> (raw)
Hi,
I am writing a description for the wiki and this topic came to my mind.
It is just a detail...
I would like to propose that we say "maintenance" instead of "support"
when referring to the activities we will do in the open within the CIP
group.
Support has a specific meaning in the commercial world. It is referred
to a "service". In order to gain traction in the industry, the confusion
between maintenance and support plays against us.
In the Open Source world, both words are used indistinctly so I do not
expect any issue by using only (mostly) maintenance.
So we would say Super Long Term Maintenance (SLTM).
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2016-11-08 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 11:08 Agustin Benito Bethencourt [this message]
2016-11-16 13:36 ` [cip-dev] Super Long Term ... Support or Maintenance? Agustin Benito Bethencourt
2016-11-17 0:48 ` Naoki MATSUMOTO
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5821B23A.90007@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox