Remove python packaging and code

README.rst

@@ -1,57 +1,29 @@
-Test and reference data for the specreduce package
---------------------------------------------------
+Reference and calibration data for the reducing optical/IR spectra
+------------------------------------------------------------------
 
 .. image:: http://img.shields.io/badge/powered%20by-AstroPy-orange.svg?style=flat
     :target: http://www.astropy.org
     :alt: Powered by Astropy Badge
 
-.. image:: https://github.com/astropy/specreduce-data/workflows/Python%20Tests/badge.svg
-    :target: https://github.com/astropy/specreduce-data/actions
-    :alt: Python Test Status on Github Actions
-
-This repository contains general reference data for spectroscopic data reduction
+This repository contains general reference and calibration data for spectroscopic data reduction
 (e.g. standard star spectra, atmospheric extinction curves, line lists for calibration
-lamps) and test data for the specreduce package.
+lamps).
 
 
 License
 -------
 
 This project is Copyright (c) Astropy Specreduce contributors and licensed under
-the terms of the BSD 3-Clause license. This package is based upon
-the `Astropy package template <https://github.com/astropy/package-template>`_
-which is licensed under the BSD 3-clause licence. See the licenses folder for
+the terms of the BSD 3-Clause license. See the licenses folder for
 more information.
 
 
 Contributing
 ------------
 
-We love contributions! specreduce-data is open source,
-built on open source, and we'd love to have you hang out in our community.
-
-**Imposter syndrome disclaimer**: We want your help. No, really.
-
-There may be a little voice inside your head that is telling you that you're not
-ready to be an open source contributor; that your skills aren't nearly good
-enough to contribute. What could you possibly offer a project like this one?
-
-We assure you - the little voice in your head is wrong. If you can write code at
-all, you can contribute code to open source. Contributing to open source
-projects is a fantastic way to advance one's coding skills. Writing perfect code
-isn't the measure of a good developer (that would disqualify all of us!); it's
-trying to create something, making mistakes, and learning from those
-mistakes. That's how we all improve, and we are happy to help others learn.
-
-Being an open source contributor doesn't just mean writing code, either. You can
-help out by writing documentation, tests, or even giving feedback about the
-project (and yes - that includes giving feedback about the contribution
-process). Some of these contributions may be the most valuable to the project as
-a whole, because you're coming to the project with fresh eyes, so you can see
-the errors and assumptions that seasoned contributors have glossed over.
-
-Note: This disclaimer was originally written by
-`Adrienne Lowe <https://github.com/adriennefriend>`_ for a
-`PyCon talk <https://www.youtube.com/watch?v=6Uj746j9Heo>`_, and was adapted by
-specreduce-data based on its use in the README file for the
-`MetPy project <https://github.com/Unidata/MetPy>`_.
+We love contributions! specreduce-data is open source and we would appreciate any
+new data or updates to existing data. Much of the data archived here comes from the
+calibration data that IRAF provides. This has been augmented with some more recent data that's
+freely available from other sources. A goal of this repository is to provide a single,
+curated collection to help save users the task of finding and downloading calibration
+reference data themselves.