Clarify the state of this repository vs. the xspec/xspec repo #85
Description
Dear maintainers,
dear @fgeorges, @adamretter, et al.
can you please clarify the status of this repository vs. the xspec/xspec one?
@cirulls is writing in xspec#18 (comment):
Regarding your question about the official xspec repository, I originally forked the xspec repository from the xpath organisation and submitted several pull requests to the project as well as reviewed pull requests from other people. Unfortunately I don't have write access to that repository and pull requests have been sitting there for almost a year now. Recently I have been given admin access to the xspec organisation which was created when the code was moved from Google Code and I transferred my fork here.
When having a look at the network graph you can clearly see that the xspec/xspec repo has maturly evolved during the past years while development in this original repository has stopped.
However, people still open new XSpec issues in this repository and at least I was confused where to report or contribute...
@cirulls is willing to revive development in the new xspec/xspec repo:
I'm hoping to revive XSpec project and I would be very interested in knowing how you are using XSpec, which features/bug fixes you'd like to see in the next XSpec release, etc. Feel free to post other issues/requests.
... so if the xspec repository in the xspec organization namespace became the official repository now, I would suggest to add a note to this repository here stating that it isn't maintained anymore and people should use xspec/xspec instead.
Looking forward to hearing from you!
Cheers,
Tobias