From: Dmitry Alexandrov <321942@gmail.com>
To: Ramon Delacruz <rdelacru@sdac.harvard.edu>
Cc: "'help-gnu-emacs@gnu.org'" <help-gnu-emacs@gnu.org>
Subject: Re: Emacs Consultanting Oportunity
Date: Wed, 08 Jun 2016 18:09:23 +0300 [thread overview]
Message-ID: <874m93k998.fsf@quux> (raw)
In-Reply-To: <600F9E0BA7530C4781A0B518B62752D015FFEEBF@max2> (Ramon Delacruz's message of "Mon, 6 Jun 2016 20:33:24 +0000")
Ramon Delacruz <rdelacru@sdac.harvard.edu> writes:
> We are going to be installing Emacs in new servers and have ran into
> some issues. Unfortunately we don't have anybody with enough knowledge
> of Emacs to help us get the desired behavior.
>
> I would like to know if you guys can recommend a company or individual
> that could potentially do paid consulting work and assists us during
> the configuration on the servers and user configuration.
For what it’s worth, a page titled ‘Service Directory’ [0] on FSF
web-site lists several people who are willing to provide paid
consultations on and support of GNU Emacs.
[0] https://www.fsf.org/resources/service/
next prev parent reply other threads:[~2016-06-08 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 20:33 Emacs Consultanting Oportunity Ramon Delacruz
2016-06-08 15:09 ` Dmitry Alexandrov [this message]
2016-06-08 17:46 ` Emanuel Berg
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=874m93k998.fsf@quux \
--to=321942@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rdelacru@sdac.harvard.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).