Decide on plan for the Beacon repository about ga4gh-schemas HOT 12 CLOSED

@skeenan Do you think these docs should move to the website?

I know you were contemplating some cleanup - the docs might be a good fit as part of some overall reorganization.

from ga4gh-schemas.

@skeenan now that we have your beacon site should we delete the beacon repo?

from ga4gh-schemas.

I would be reluctant to completely delete the repo given the complex name of the beacon site. How about leaving a ReadMe to that repo with a URL pointer to the beacon site?

from ga4gh-schemas.

I think the plan is for the beacon site url to get a lot shorter/more memorable. Right now its just a dev s3 instance - it should graduate to something real and mesh well with ga4gh.com shortly.

from ga4gh-schemas.

Yes, this morning I've received a permanent home to host our site @massie will be able to update the DNS entry for ga4gh.org once it's up on the new host. re: deleting the Beacon repo, I can see the sense in not duplicating the info in different places, but I'd like Steve Sherry to comment as he is the author of the material in that repo., I've pinged him.

from ga4gh-schemas.

Please don't delete the repo -- people have starred it, are watching it, have forked it, etc. Bread-crumbs are useful, and going out of your way to enforce a potential form of link rot seems counter-intuitive.

There's no harm in leaving something up, right?

from ga4gh-schemas.

Well we've got a balance here - you know?

There will be many users who visit http://github.com/ga4gh for the first time. For those users, we want to make sure the first experience is a good one, and that they know how to find the things they need.

The Beacon schema files are actually over here: https://github.com/ga4gh/schemas/blob/master/src/main/resources/avro/beacon.avdl

Which you would miss entirely by going to the beacon repo - so its pretty confusing as is.

As for link rot - we can handle that with just a deprecation plan. First we can delete the files, and fix this repo to link to the right place - then we can decide if we want to ping all the star-owners or whatever with the new link. There aren't any real forks, and an issue of the form "this repo is going away" would take care of the watchers, so its not untenable.

from ga4gh-schemas.

My $.02:

• the only actual content in the repo is two text files (BeaconProjectRationale.md and currentBeaconfile.md). Having two copies of that content is a Bad Idea -- as soon as @skeenan and Steve Sherry confirm that the new official home is live, we should delete it from GitHub
• once the content is gone, I agree there's some charm in leaving a forwarding pointer for old people, but as @cassiedoll points out, that's offset by the potential confusion for new people.
• given that there are only 6 stars and no active forks, I'd suggest leaving a "deprecated -- follow this link" comment in the repo description for a few weeks, and then deleting the repo entirely

from ga4gh-schemas.

Less is more :)

from ga4gh-schemas.

+1 to @dglazer solution

Steve Sherry has informed me he is happy to let ga4gh.org/#/beacon become the main site for beacon once it is live.

from ga4gh-schemas.

The live url is fully up: http://ga4gh.org/#/beacon
I'm going to change the Beacon repo to point to the new site as @dglazer suggested above.

from ga4gh-schemas.

The repo was fully deprecated awhile ago. At some point in the future it will be deleted - so this issue is now resolved.

from ga4gh-schemas.