Skip to content

Instantly share code, notes, and snippets.

@bgruening

bgruening/RBC_meeting_july.md Secret

Last active July 27, 2016 12:13
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save bgruening/a7851ac1a4748d85fca36ad5cf293aad to your computer and use it in GitHub Desktop.
Save bgruening/a7851ac1a4748d85fca36ad5cf293aad to your computer and use it in GitHub Desktop.
Download ZIP
Things to discuss during our RBC meeting in Freiburg
Raw
RBC_meeting_july.md

This will be a list of things we would like to discuss during the our meeting. Please feel encuraged to submit technical, but also general topics:

  1. did people already think about security in systems like Conda/Bioconda? Currently, it seems like some evil attacker could easily slip in some compromised software by "updating" a package (which could then be automatically installed on HPC systems with all possible consequences...). It would be cool to have some ring of trust like mechanism with signed packages. In principle most ingredients should be there already; this could be mostly about making a reasonable proposal to the bioconda people. (Sebastian)

  2. thinking more about our RNA-Seq QC SOPs, we got the impression that ideally we should --sooner than later-- get the community involved in extending and adapting such SOPs. This has at least two major aspects: how to initiate this and how to make this accessible to biologists (which calls for something less technical than documents on Github, whereas Wikis or Google docs etc may be too unstructured.) (Sebastian)

  3. Visibility and accessibility of training material. From Sebastian .... Still, IMO it would be worth to discuss how to e.g. optimize the visibility of the material (e.g. more prominent links from some official RBC site etc....) and ideally the accessibility for non-techies to make it easier for biologists to contribute.

@jfallmann
Copy link

Paper draft
https://www.overleaf.com/5768824tgyyqh
Feel free to contribute

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment