Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the state of this repository vs. the xspec/xspec repo #85

Open
tofi86 opened this issue Dec 3, 2016 · 0 comments
Open

Clarify the state of this repository vs. the xspec/xspec repo #85

tofi86 opened this issue Dec 3, 2016 · 0 comments

Comments

@tofi86
Copy link

tofi86 commented Dec 3, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant