search

ga4gh / ga4gh-schemas

Models and APIs for Genomic data. RETIRED 2018-01-24
http://ga4gh.org
Apache License 2.0
214 stars 110 forks source link

Deprecation notice added #884

Closed rishidev closed 2 years ago

rishidev commented 7 years ago

It was decided at a GA4GH meeting to deprecate future work in this repository, and make it clear to users that this is the case.

heuermh commented 7 years ago

More explanation needed, please.

mcourtot commented 7 years ago

Hi @heuermh; following the GA4GH plenary meeting in Orlando the project has been reorganised into work streams and driver projects, which supersede & replace the task teams. Being part of the 'old' metadata task team I know that we will still produce a data model, but I don't think the reference implementation will be maintained for example. Also as you can see above the current build in this repository is failing. The new GA4GH website is at https://www.ga4gh.org and hopefully provides more info.

akmorrow13 commented 7 years ago

I find it interesting the htsget also implements its own schemas based on BAM fields, when it seems this project would have been a great example for the use of ga4gh-schemas. Any thoughts on why they developed new schemas? This is proof that there is still a need for these.

lh3 commented 7 years ago

Github has recently implemented a new feature to archive a repo and make it read-only. Perhaps it is time to use the new feature here?

heuermh commented 7 years ago

Perhaps it is time to use the new feature here?

No, I don't believe that would be appropriate. Even though GA4GH the organization has deprecated future work in this repository, that should not prevent the greater community from doing so (Github reports 117 forks currently).

lh3 commented 7 years ago

Archiving only makes this repo read-only, not the forks. In addition, you can still fork archived repos.

heuermh commented 7 years ago

I don't see anything wrong with adding a deprecation notice and referencing new projects or efforts.

Archiving the repository however is an act of aggression against the community -- what is wrong with continuing to allow issues to be created and discussed? pull requests to be considered and merged?

If the current build is in a sorry state, perhaps GA4GH members who did not attend the plenary meeting and weren't part of the deprecation conversation or even non-GA4GH contributors might be willing to help make it right?

https://www.youtube.com/watch?v=OT5mqWKirhI

mbaudis commented 7 years ago

@heuermh I'm neutral on locking vs. plastering deprecation notes all over the repo.

However, regarding the "pick up & make it work": The problem wasn't the ability/willingness of people to contribute, but rather the existence of independent fiefdoms with different levels of activity (i.e. ~0 for variants after first definitions...), but then interdependencies. I cannot easily convey my frustrating experiences, seeing code after-monthlong-discussions-and-acceptance getting reverted later, due to nobody moving "essential" server code forward.

I had made it explicit that I see the schema fulfilling the role of "glue" keeping different projects/parts of GA4GH together. However, without an actively guiding hand managing code advancements, I have learned to appreciate the modular approach, where different areas of the schema are managed quasi independently, but with cross-participation. So if there are time stamps in Un*x time somewhere - whatever.

Therefore: I wish for a consistent GA4GH schema in spirit, but see the current "disassemble but talk to each other" approach as a way forward. And sure, with some, limited, effort, one can easily build a coherent + working + better schema than the remnants you see; but it is about uptake through participation (which makes this option a no-go).

Just IMO...