unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] Excorporate: Exchange integration package
Date: Mon, 09 Feb 2015 09:16:18 -0500	[thread overview]
Message-ID: <jwvtwyvuqct.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m31tlz2rxn.fsf@fitzsim.org> (Thomas Fitzsimmons's message of "Mon, 09 Feb 2015 07:24:52 -0500")

> OK, I'm definitely sympathetic to this view.  In this regard, my main
> concern is that it's currently impossible for other Emacs developers to
> test Excorporate using/against only Free Software.  One idea is if
> OpenChange could grow EWS support in tandem with the features that
> Excorporate actually uses, then there would be a Free Software option
> for full Excorporate testing at all times (note: I'm not necessarily
> signing up for this work).  Would that improve the appeal of Excorporate
> for ELPA?

Yes, if Excorporate can be used with OpenChange, then that'd be fine.

> The counter-argument here is that Exchange Web Services is essentially
> just providing a network service.  From following emacs-devel I was
> under the impression that Free Software that talks to a network service
> over a protocol was OK, regardless of what was implementing the protocol
> on the other end.

Hmm... that's a very good point.  Let me sleep on it.


        Stefan



  parent reply	other threads:[~2015-02-09 14:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 21:21 [elpa] Excorporate: Exchange integration package Thomas Fitzsimmons
2015-02-09  4:08 ` Stefan Monnier
2015-02-09  6:56   ` Achim Gratz
2015-02-09  8:05   ` Michael Albinus
2015-02-09  9:05     ` joakim
2015-02-09 11:00   ` Daniel Colascione
2015-02-09 12:24   ` Thomas Fitzsimmons
2015-02-09 12:40     ` David Kastrup
2015-02-09 14:16     ` Stefan Monnier [this message]
2015-02-10 20:23       ` Stefan Monnier
2015-02-11  1:24         ` Thomas Fitzsimmons
2015-02-11  6:55           ` Tassilo Horn
2015-02-11  9:42             ` David Kastrup
2015-02-11 12:59               ` Tassilo Horn
2015-02-11 13:07                 ` Dmitry Gutov
2015-02-11 13:53                   ` Michael Albinus
2015-02-11 15:01                   ` Tassilo Horn
2015-02-09 22:07   ` Richard Stallman
2015-02-09  8:14 ` Michael Albinus
2015-02-09 12:41   ` Thomas Fitzsimmons
2015-02-09 13:02     ` Michael Albinus
2015-02-09 13:21       ` Thomas Fitzsimmons
2015-02-09 13:34         ` Michael Albinus
2015-02-09 17:22           ` SOAP, WSDL Ivan Shmakov
2015-02-09 18:38             ` Michael Albinus
2015-02-09 18:50               ` Ivan Shmakov
2015-02-09 14:09     ` [elpa] Excorporate: Exchange integration package Stefan Monnier
2015-02-09 10:06 ` SAKURAI Masashi

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvtwyvuqct.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=fitzsim@fitzsim.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).