Create repo for BioC2019

[lwaldron]

Not sure if we should go to something more generic like AnnualConference and use branches for each year? @mtmorgan

[mtmorgan]

Not sure how that works with github pages (one page one repo? does the old site need to persist?) and also the magic that allows bioc2018.bioconductor.org (versus bioconductor.github.io/AnnualConference). @vobencha might be able to help with the second

[vobencha]

It is possible to specify the same custom domain in multiple GitHub repos so we could have all these pages live at the same time -

https://bioc2018.bioconductor.org/ https://bioc2019.bioconductor.org/ https://bioc2020.bioconductor.org/ etc.

All material for a conference should be in the same repo if possible. The issue we ran into last time was that the workshop book was in a separate repo so we couldn't host it from https://bioc2018.bioconductor.org/. If material is in a separate repo we can link to it from the main conference page but the url that resolves does not have the same structure, e.g., it resolved to

https://bioconductor.github.io/BiocWorkshops

instead of

https://bioc2018.bioconductor.org/BiocWorkshops

The GitHub pages site is built from a specific branch so AFAIK you can't have material in multiple branches of a repo visible at the same time.

You could try creating an AnnualConference repo, host it out of docs/ and create directories for each year, 2019, 2020 etc. You might be able to control what year is visible via the index or other .md files at that level. I haven't tried this. If it doesn't work, creating a repo by year is cheap and a clean separation.

[omsai]

For Bioc2019 we've gone the "cheap and clean separation" route with a new repo: https://github.com/Bioconductor/BioC2019 to archive Bioc2018.

@lwaldron feel free to close this issue.