News: 0000816280

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Debian @ COVID-19 Biohackathon (April 5-11, 2020)

([Distributions] Mar 30, 2020 15:40 UTC (Mon) (corbet))


The Debian community has announced a one-week, online "biohackathon" as a focused effort to improve the available free biomedical tools. " Most tasks do not require any knowledge of biology or medicine, and all types of contributions are welcome: bug triage, testing, documentation, CI, translations, packaging, and code contributions. "

From :

Andreas Tille <andreas-AT-an3as.eu>

To :

debian-devel-announce-AT-lists.debian.org

Subject :

Debian @ COVID-19 Biohackathon (April 5-11, 2020)

Date :

Fri, 27 Mar 2020 20:59:50 +0100

Message-ID :

<20200327195950.GF32306@an3as.eu>

Cc :

Debian Med Project List <debian-med-AT-lists.debian.org>

Archive-link :

[1]Article

Dear Debian Community,

There will be an virtual (online) COVID-19 Biohackathon from April 5-11,

2020 and the Debian Med team invite you help us improve biomedical FOSS

and the tools/libraries that support those projects.

Most tasks do not require any knowledge of biology or medicine, and all

types of contributions are welcome: bug triage, testing, documentation,

CI, translations, packaging, and code contributions.

1. Debian related bugs are viewable at [covid19-bugs]

2. Software awaiting packaging is listed at [covid-19-packages], please

respond to the RFP with your intent so we don't duplicate work

3. You can also contribute directly to the upstream packages, linked

from the Debian Med COVID-19 task page at [covid-19-packages]. Note:

many biomedical software packages are quite resource limited, even

compared to a typical FOSS project. Please be kind to the upstream

author/maintainers and realize that they may have limited resources to

review your contribution. Triaging open issues and opening pull requests

to fix problems is likely to be more useful than nitpicking their coding

style.

4. Architectures/porting: Please focus on amd64, as it is the primary

architecture for biomedical software. A secondary tier would be arm64 /

ppc64el / s390x (but beware the endian-related issues on s390x). From a

free/open hardware perspective it would be great to see more riscv64

support, but that is not a priority right now

5. The Debian Med team is also trying to improve the availability of

automated biomedical pipelines/workflows [robust-workflows] using the

Common Workflow Language open standard. The reference implementation of

CWL is written in Python and there are many open issues ready for work

that don't require any biomedical background [cwltool-issues]

6. It is very easy to contribute to Debian Med team. We have a lowNMU

policy for all our packages. Merge requests on Salsa are usually

processed quickly (but please ping some of the latest Uploaders of the

package to make sure it will be noticed). Even better if you ask for

membership to the team and push directly to the salsa repository.

7. The [debian-med-team-policy] should answer all questions how to

contribute.

The main COVID-19 biohackathon is being organized at [covid-19-bh20] and

for Debian's participation we are using [salsa-covid-19-bh20]

[covid-19-bugs] https://blends.debian.org/med/bugs/covid-19.html

[covid-19-packages] https://blends.debian.org/med/tasks/covid-19

[covid-19-bh20] https://github.com/virtual-biohackathons/covid-19-bh20

[salsa-covid-19-bh20]

https://salsa.debian.org/med-team/community/2020-covid19-...

[robust-workflows] https://doi.org/10.1007/s41019-017-0050-4

[cwltool-issues] https://github.com/common-workflow-language/cwltool/issues

[COVID-19-advice]

https://www.who.int/emergencies/diseases/novel-coronaviru...

[debian-med-team-policy] https://med-team.pages.debian.net/policy/

Sincerely,

Michael R. Crusoe on behalf of the Debian-Med team

(and Andreas Tille on behalf of Michael R. Crusoe ;-) )

--

Michael R. Crusoe

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl56BmsACgkQPCZ2P2xn

5uJzYBAAuo7koTEkxqRexkdg4T/xSO1s7AwW+NGRFPwQnT2NoIwBcXCDkU7xYGF2

ACbswiDJNwSevrP4oV89E0OLpncJbnPP9bRwFO+Sppuo6AhgAhJsxn8N6tN4DDki

50E+riYUqNfBakRKOzHVFTHy2H5BaOsDxJGMFoYW0twZCbWEoLJr9jMbcPHoDpyn

M+cMEQ6yUYwgLA08p67P2Ts9GsnYt30czZSmXYG88fjadhd2hQ/TvhykrRBGnL2d

QjcdPivoo+Er8h7LRrRzWAS1j5lPJOsQ9EJvMu3bns86Jk4yS0uX5Rcen+TNPEQ9

/ui+MtNY29XPwNTOfE564X4K6GMlPmQ+NnAghkzYOsKhlXuo54sRQhmfPR88fSBx

+hWddj3SNfb3NJlOrUbXDz4HKmq8jwPj7U5o13ajfMS+ylTER8j+rHNIdqjlIZPo

xs7vw5sn3hBNObfq8OKScOBbFe6GVi9Pl8sGKZSW7GebumeHRtrSKVMQvgBxEdup

a70kuG+c+BiBvX6IJEtMlDe4nZ418fI61sf7TM3lrSWFJ/FfRvfwUzmbm3ripf+T

tKTkqi0fBG2MhIaiCSz2jsZXzaoQX5huVYZbeaaskJaa/IP+T/Rc5N2kD+wPQZyC

dYi45DboGN37suTmiziDgvKZHKs5cPqzEAivElWivoPvuD/J65s=

=pqDm

-----END PGP SIGNATURE-----

----- End forwarded message -----

--

http://fam-tille.de



[1] https://lwn.net/ml/debian-devel-announce/20200327195950.GF32306@an3as.eu/

A sheet of paper crossed my desk the other day and as I read it,
realization of a basic truth came over me. So simple! So obvious we couldn't
see it. John Knivlen, Chairman of Polamar Repeater Club, an amateur radio
group, had discovered how IC circuits work. He says that smoke is the thing
that makes ICs work because every time you let the smoke out of an IC circuit,
it stops working. He claims to have verified this with thorough testing.
I was flabbergasted! Of course! Smoke makes all things electrical
work. Remember the last time smoke escaped from your Lucas voltage regulator
Didn't it quit working? I sat and smiled like an idiot as more of the truth
dawned. It's the wiring harness that carries the smoke from one device to
another in your Mini, MG or Jag. And when the harness springs a leak, it lets
the smoke out of everything at once, and then nothing works. The starter
motor requires large quantities of smoke to operate properly, and that's why
the wire going to it is so large.
Feeling very smug, I continued to expand my hypothesis. Why are Lucas
electronics more likely to leak than say Bosch? Hmmm... Aha!!! Lucas is
British, and all things British leak! British convertible tops leak water,
British engines leak oil, British displacer units leak hydrostatic fluid, and
I might add Brititsh tires leak air, and the British defense unit leaks
secrets... so naturally British electronics leak smoke.
-- Jack Banton, PCC Automotive Electrical School

[Ummm ... IC circuits? Integrated circuit circuits?]