Move away from @cray.com email addresses

This PR removes @cray.com email addresses, using the following strategy:

* removes GOALS.md and STATUS.devel which seem like files that aren't
  of much importance anymore now that more of our documentation is
  online and at GitHub.  Updated README.devel and README.files to
  reflect this, as well as a few rules in Makefile.devel that haven't
  been used since the SVN days.

* removed references to [email protected] which is going away.
  Though we're replacing it with an equivalent, it seems poor form to
  mention it as plaintext in all these files (many of which used
  disguiseme in the .rst cases, but it seems unlikely to help when the
  sources themselves are public).  In most cases, referred people to
  the GitHub issues page instead, or figured they could figure out how
  to contact us.

* updated scripts that mailed to [email protected] to refer to
  [email protected], though more effort could/should eventually be put
  here to make these more organization-agnostic.

* removed some text files containing my email address which I can't
  recall why I would've intentionally put into the repository.

* some other stuff as well?

Makefile.devel

@@ -64,10 +64,3 @@ SPECTEST_DIR = ./test/release/examples/spec
 spectests: FORCE
 	rm -rf $(SPECTEST_DIR)
 	doc/util/extract-rst-tests.py  doc/rst/language/spec/ --output $(SPECTEST_DIR)
-
-FUTURES:
-	cd test && find . -wholename ".svn" -prune -o \( -name \*.future \) -exec head -n 1 {} + > FUTURES
-
-
-future_stats: FUTURES
-	./util/devel/test/future_stats STATUS.devel test/FUTURES

README.devel

@@ -18,7 +18,6 @@ description:
   CHANGES.md
   CONTRIBUTORS.md
   COPYRIGHT
-  GOALS.md
   LICENSE
   LICENSE.chapel
   QUICKSTART.rst

README.files

@@ -12,7 +12,6 @@ further information about the files and directories that they contain.
   CHANGES.md           : a list of changes in each release
   CONTRIBUTORS.md      : a list of contributors to the Chapel project
   COPYRIGHT            : copyright information
-  GOALS.md             : the goals of this release
   LICENSE              : license information for the Chapel release as a whole
   LICENSE.chapel       : license statement for the Chapel implementation itself
   README.files         : this file

doc/rst/platforms/cygwin.rst

@@ -36,7 +36,7 @@ hard-drive (``/cygdrive/c/``) to create ``/cygdrive/c/chapel`` tends to
 work well. Currently, our compiler-generated Makefiles break when the
 compiler or runtime use an absolute path that contains spaces. If any
 Cygwin experts have tips on addressing this issue in a portable way,
-please let us know at :disguise:`[email protected]`.
+please let us know.
 
 
 Required Packages

doc/rst/technotes/extern.rst

@@ -997,6 +997,6 @@ Future Directions
 =================
 
 We intend to continue improving these capabilities to provide richer
-and richer support for external types and functions over time.  If you
-have specific requests for improvement, please let us know at:
-:disguise:`[email protected]`.
+support for external types and functions over time.  If you
+have specific requests for improvement, please let us know on the
+Chapel GitHub issue page or community forums.

doc/rst/technotes/firstClassFns.rst

@@ -150,4 +150,5 @@ Future Directions
 
 Over time, we will be improving the support for first-class functions
 and their syntax.  If you have specific feature requests or
-suggestions, please let us know at: :disguise:`[email protected]`.
+suggestions, please let us know on the Chapel GitHub issues page or
+community forums.

doc/rst/usingchapel/bugs.rst

@@ -4,28 +4,6 @@
 Reporting Chapel Issues
 =======================
 
-Public Issues
--------------
-
 Chapel uses `GitHub Issues`_ to track public issues. If you have a bug report,
 feature request, or other issue to report, please use the "New Issue"
 button on that page to file it.
-
-Public issues that predate our issue tracker can be found in the
-(retired) `STATUS.devel file`_ and the (retired)
-`chapel-bugs mailing list archives`_.
-
-Private Issues
---------------
-
-Chapel accepts private issue reports :any:`by email <privatebugs>`.
-
-.. _GitHub Issues: https://github.com/chapel-lang/chapel/issues
-.. _chapel-bugs mailing list archives: https://sourceforge.net/p/chapel/mailman/chapel-bugs/
-.. _STATUS.devel file: https://github.com/chapel-lang/chapel/blob/master/STATUS.devel
-
-.. toctree::
-   :hidden:
-   :maxdepth: 1
-
-   privatebugs

doc/rst/usingchapel/building.rst

@@ -163,7 +163,7 @@ new build environment by creating ``Makefile.<compiler>`` and/or
 ``Makefile.<platform>`` files and setting your environment variables to
 refer to those files.  If you do develop new build environment support
 that you would like to contribute back to the community, we encourage
-you to send your changes back to us at: :disguise:`[email protected]`
+you to submit a pull request to the Chapel GitHub repository.
 
 .. _readme-installing:
 

doc/rst/usingchapel/chplenv.rst

@@ -116,8 +116,7 @@ CHPL_HOST_PLATFORM
    We are interested in making our code framework portable to other platforms --
    if you are using Chapel on a platform other than the ones listed above,
    please refer to :ref:`platform-specific-settings` for ways to set up a
-   Makefile for this platform and/or contact us at:
-   :disguise:`[email protected]`
+   Makefile for this platform.
 
 
 .. _readme-chplenv.CHPL_TARGET_PLATFORM:

doc/rst/usingchapel/tasks.rst

@@ -35,9 +35,6 @@ detail.  The rest of this document includes:
 * a list of tasking-related methods on the locale type
 * a brief description of future directions for the tasking layer
 
-If you have questions about tasks that are not covered in the following,
-please send them to :disguise:`[email protected]`.
-
 
 --------------------------
 Task Implementation Layers
@@ -273,9 +270,8 @@ The Chapel program will generate an error if the requested number of
 threads per locale is too large.  For example, when running multi-locale
 programs, the GASNet communication layer typically places an upper bound
 of 127 or 255 on the number of threads per locale (There are ways to
-work around this assumption on certain platforms -- please contact us at
-:disguise:`[email protected]` or peruse the GASNet documentation if you need
-to do so.)
+work around this assumption on certain platforms -- please contact us if
+you need to do so, or peruse the GASNet documentation).
 
 CHPL_TASKS == fifo
 ------------------
@@ -426,5 +422,5 @@ balancing at the other end of the spectrum (for programmers who would
 prefer not to manage threads or whose programs cannot trivially be
 load balanced manually).  Our hope is to leverage existing open source
 threading and task management software and to collaborate with others
-in these areas, so please contact us at :disguise:`[email protected]` if you'd
+in these areas, so please contact us if you'd
 like to work with us in this area.

highlight/emacs/chpl-mode.el

@@ -1,7 +1,7 @@
 ;;; chpl-mode.el --- Major mode for editing Chapel code
 
 ;; Author:     2007 Steven T Balensiefer
-;; Maintainer: Chapel group <[email protected]>
+;; Maintainer: Chapel group
 ;; Created:    December 2002
 ;; Version:    0.7
 ;; Keywords:   Chapel languages oop

test/release/examples/primers/sparse.chpl

@@ -282,9 +282,8 @@ writeSpsArr();
 // over time.
 //
 // Anyone reading this far who is interested in exploring more with
-// sparse domains and arrays in Chapel is encouraged to contact us at
-// [email protected].  We currently have a Compressed Sparse Row
-// (CSR) sparse domain/array layout within our modules and an
-// implementation of the NAS CG benchmark that makes use of it, and
-// would be happy to provide the curious with full explanations of
-// the features therein, and are open to new suggestions.
+// sparse domains and arrays in Chapel is encouraged to contact us.
+// We currently have a Compressed Sparse Row (CSR) sparse domain/array
+// layout within our modules and an implementation of the NAS CG benchmark
+// that makes use of it, and would be happy to provide the curious with
+// full explanations of the features therein, and are open to new suggestions.

test/sparse/bradc/CSR/sparse.chpl

@@ -260,9 +260,8 @@ writeSpsArr();
 // over time.
 //
 // Anyone reading this far who is interested in exploring more with
-// sparse domains and arrays in Chapel is encouraged to contact us at
-// [email protected].  We currently have a Compressed Sparse Row
-// (CSR) sparse domain/array implementation in the works and a
-// virtually complete implementation of the NAS CG benchmark that
-// makes use of it, and would be happy to share those examples with
-// users of the release.
+// sparse domains and arrays in Chapel is encouraged to contact us.
+// We currently have a Compressed Sparse Row (CSR) sparse domain/array
+// implementation in the works and a virtually complete implementation
+// of the NAS CG benchmark that makes use of it, and would be happy to
+// share those examples with users of the release.