all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Richard Stallman <rms@gnu.org>
Cc: jean.christophe.helary@traduction-libre.org,
	Alexander Adolf <alexander.adolf@condition-alpha.com>,
	emacs-devel@gnu.org
Subject: Re: [Proposal] New EUDC backend for macOS address book
Date: Tue, 14 Jul 2020 10:46:54 -0400	[thread overview]
Message-ID: <m3blkii275.fsf@fitzsim.org> (raw)
In-Reply-To: <E1jtk6N-0005j0-GL@fencepost.gnu.org> (Richard Stallman's message of "Thu, 09 Jul 2020 23:53:31 -0400")

Hi Richard,

Richard Stallman <rms@gnu.org> writes:

[...]

> Which document is this patch for?

doc/misc/eudc.texi

> It seems to say positive things about various MacOS applications.

OK, if you read something as positive there, then we can change or
remove it.  There was an earlier draft that was positive, but then I had
Alexander make it factual.

> Are those applications free software?

No.

> If not, we should not suggesting that people use them.
>
> Please see the node References in the GNU Coding Standards for our
> general policy about references to nonfree programs.  Basically, it is
> ok to mention them only if the reader surely already knows about them,
> but don't encourage people to use them.

Yes, I thought the committed patch satisfied these requirements.

> For example, it is ok to mention MacOS because the reader surely has
> already heard of it, and ok to say how to make Emacs work with MacOS
> (for the sake of users who are already using MacOS and want to use
> Emacs).  But don't say anything that might encourage people to try
> MacOS if they don't already use it.  In particular, don't describe its
> functionalities or advantages.

OK, from my re-reading, the only sentence that is questionable is:

"macOS Contacts is the rolodex-like application that ships with the
macOS operating system."

How about we remove that sentence, and change that whole section to
just:

"EUDC considers macOS Contacts as a directory server back end just like
LDAP, though the macOS Contacts application always resides locally on
your machine.  macOS used to be called Mac OS X, and the Contacts
application was previously called Address Book; the EUDC macOS Contacts
backend also works on those older versions."

That provides compatibility and other information about how existing
macOS Contacts users can switch to using it via EUDC.

If there's something else you consider positive, are you able to quote
it from the current (master tip) version of doc/misc/eudc.texi?

> The same questions apply to any nonfree program that runs on MacOS,
> but the anwers will be different.  Will Mac users who try EUDC
> generally already know about macOS Contacts?  I don't know.

Generally speaking, I don't know, and I don't feel qualified to comment
since I don't use Apple products.

However, I know of one specific example, the user who submitted the new
EUDC backend.  Alexander, a macOS user, was already using macOS Contacts
for his address book.  He wanted to use EUDC, so he extended EUDC to
interface with macOS Contacts.

One possibility this opens up for him and other EUDC/macOS Contacts
users is a workflow whereby one uses EUDC to complete email addresses
from macOS Contacts, then bbdb-snarf's them into BBDB, and so gradually
migrates to a Free Software address book solution.

> If so, you can talk about how to make EUDC work with macOS Contacts --
> but please don't say anything about how to use macOS Contacts itself,
> or what it can do.

Makes sense; that's what we attempted to do with the committed eudc.texi
changes.

Thomas



  reply	other threads:[~2020-07-14 14:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 15:09 [Proposal] New EUDC backend for macOS address book Alexander Adolf
2020-04-27 16:10 ` Thomas Fitzsimmons
2020-04-27 16:41   ` Jean-Christophe Helary
2020-05-02 16:20     ` Thomas Fitzsimmons
2020-05-06 15:14       ` Alexander Adolf
2020-05-06 17:41         ` Thomas Fitzsimmons
2020-05-07 16:03           ` Alexander Adolf
2020-05-07 18:29             ` Thomas Fitzsimmons
2020-05-08 12:17               ` Alexander Adolf
2020-05-08 13:44                 ` Thomas Fitzsimmons
2020-06-08 20:41                   ` Alexander Adolf
2020-06-10  5:03                     ` Thomas Fitzsimmons
2020-06-29 13:38                     ` Alexander Adolf
2020-07-09 15:12                     ` Alexander Adolf
2020-07-09 20:29                       ` Thomas Fitzsimmons
2020-07-10 13:36                         ` Alexander Adolf
2020-07-10  3:53                       ` Richard Stallman
2020-07-14 14:46                         ` Thomas Fitzsimmons [this message]
2020-07-15  3:49                           ` Jean-Christophe Helary
2020-07-17  0:56                             ` Richard Stallman
2020-08-09  1:57                           ` Richard Stallman
2020-09-06  3:00                             ` Thomas Fitzsimmons
2020-05-05 14:47   ` Alexander Adolf
2020-04-27 20:00 ` chad
2020-05-05 13:30   ` Alexander Adolf

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=m3blkii275.fsf@fitzsim.org \
    --to=fitzsim@fitzsim.org \
    --cc=alexander.adolf@condition-alpha.com \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@traduction-libre.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.