Different docs url
Closed this issue · 9 comments
Could this move to a different docs URL? Hopefully there's somewhere this can go easily?
Sure, I'll put it on the agenda for our next meeting :) Unless you want it changed sooner than that?
During our last meeting (2023-05-11) we changed the domain on which the current docs site is hosted. Originally I had changed it to https://anndataR.dynverse.org because I wanted to try out how easy it was to change the domain for just one repo, but I later changed it to https://anndata.data-intuitive.com because the dynverse organisation doesn't really have anything to do with this codebase.
During the meeting, it became evident to me that we need to reach a consensus regarding anndataR's place within the scverse ecosystem. If the scverse core team does not perceive anndataR to be part of the scverse ecosystem, and if anndataR can't host its documentation site at https://anndataR.scverse.org or https://scverse.org/anndataR, then we should reconsider the current repository location at github.com/scverse/anndataR.
@ivirshup @gtca Was there anything discussed during the last community meeting?
I appreciate your thoughts on the matter.
When you say that data intuitive is 'your' company, do you mean that you are an employee, or 'the boss'? I guess I worry that putting it under data-intuitive implies ownership (and being subjected to the whims of corporate overlords) in a way that anndataR/anndataR does not.
Hey Martin! I appreciate you bringing up any concerns that you may have.
I'm a co-founder of Data Intuitive, but I don't think that this is necessarily relevant.
I'd like to assure you that regardless of which repository anndataR it is in, it should retain it's current licensing unless all of us agree it should be changed (that is, an MIT license with us as the copyright owners).
In addition, despite the fact that Data Intuitive is mostly a consultancy company, I'd say about 90% of our work is open source. You wouldn't be able to tell by our GitHub organisation itself, since our contributions reside mostly in other source code repositories. Despite being only a small company, we're involved in quite a few open source repositories which we actively maintain:
- viash-io/viash, GPL3, 2429 commits
- openpipelines-bio/openpipeline, MIT, 1293 commits
- openproblems-bio/openproblems-v2, MIT, 1013 commits
- dynverse/anndata, MIT, 146 commits
- czbiohub/utilities, MIT, 420 commits
- funkyheatmap/funkyheatmap, MIT, 73 commits
What I'm trying to say is, at DI we try contribute to and maintain open source projects as best as possible. We're fans of open communication, and we'd be delighted to host anndataR.
Having said that, I'm also more than happy to just create a new organisation for anndataR :)
@rcannood and all,
Thanks for the discussions we had on the topic! For the repo, we're happy to keep it under the scverse org. And as we'll be trying to get better at highlighting community-maintained projects, it will also be a great start for creating and adding a corresponding badge and a line in the README as something really well suited for anndataR as it has been a joint effort from the very start.
And seems like the respective developers and maintainers should have all the necessary repository-specific rights to admin and maintain anndataR repo here (if something is missing, we should look into that).
Maybe @mtmorgan, @lazappi and @LouiseDck can also chime in to add their perspective as to where they feel this repo would be best living.
That sounds great to me!
That's great news!
How about we add something to the readme / index page of the documentation about how this is a community maintained package and list who the authors are.
What about the documentation url. Would we be able to host it at https://anndataR.scverse.org ? Note that this page will also have the aforementioned disclaimer about it being community maintained.
This sounds like a great step to me!
@gtca: WDYT?
What about the documentation url. Would we be able to host it at https://anndatar.scverse.org/ ? Note that this page will also have the aforementioned disclaimer about it being community maintained.