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

Archive old dcm2niix repository? #865

Closed
DimitriPapadopoulos opened this issue Sep 23, 2024 · 6 comments
Closed

Archive old dcm2niix repository? #865

DimitriPapadopoulos opened this issue Sep 23, 2024 · 6 comments

Comments

@DimitriPapadopoulos
Copy link
Collaborator

Describe the bug

How about archiving https://github.com/neurolabusc/dcm2niix, after adding a redirection to this repository? Unless you no longer have the identifiers associated with the neurolabusc organisation.

That would prevent confusion around the reference repositories.

neurolabusc added a commit to neurolabusc/dcm2niix that referenced this issue Sep 23, 2024
@DimitriPapadopoulos
Copy link
Collaborator Author

I don't think #864 (comment) addresses the issue at hand.

@DimitriPapadopoulos
Copy link
Collaborator Author

I thought repository neurolabusc/dcm2niix is obsolete and repository rordenlab/dcm2niix is the current one, with the policy by the BIDS maintainers being implemented as different branches development / master in the latter.

Are you saying that the policy by the BIDS maintainers is implemented as different repositories neurolabusc/dcm2niix / rordenlab/dcm2niix?

@neurolabusc
Copy link
Collaborator

I do not understand the question. The repository dcm2niix has 228 forks. While at your request I did archive the my own personal fork and include a message in the readme redirecting to the root repository, I do not understand the need for disambiguation. Each fork lists its root fork, I think there are many legitimate active forks to handle unique situations of specific users or explore experimental features. By design, we use a permissive license that encourages others to create their own custom forks. I do not control these forks nor does it seem appropriate to archive these forks that may be appropriate for specific use cases.

@DimitriPapadopoulos
Copy link
Collaborator Author

DimitriPapadopoulos commented Sep 24, 2024

I know that Git is not a centralised VCS. However, one repository usually plays a more central role than others, and that special repository needs to be identified.

At some point, I had cloned neurolabusc/dcm2niix as my upstream Git repository. Either it was indeed the primary repository at the time, where most of the development happens, or it was my mistake - at the time I think repositories were not as clearly identified as forks of another repository as today. Now, a few years later, I was tempted to keep using neurolabusc/dcm2niix because it was not identified as obsolete. I ended up finding rordenlab/dcm2niix, using the forking information exactly as you write. But it took me some time.

@neurolabusc
Copy link
Collaborator

OK, but I archived the neurolabusc repository and clearly redirected to the main repository before I closed this issue, and now you have re-opened this. I think this issue is closed as resolved. Unless you can provide a rationale I think this issue should be closed as resolved.

@DimitriPapadopoulos
Copy link
Collaborator Author

I did not repoen after you archived the neurolabusc repository and clearly redirected to the main repository, but before that.

But most importantly, thank you very much for this great piece of software!

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

2 participants