Could you change the current Bluejeans link to Google Meet link on the
"ChRIS on the MOC" schedule that is set as every Thursday on our
Because at the ChRIS meeting last week, the participants agreed on
using Google Meet instead of Bluejeans as a trial for next meeting.The
reason is Google Meet has the following features to help us.
* Captions to convert voice to text. It helps "me" to understand
English. Ref: https://support.google.com/meet/answer/9300310?hl=en
* Noise canceling. It helps someone in noisy environments. Ref:
Jun | He - His - Him
Let me introduce a new GitHub repository "ChRIS_contributer-support"
 to help you, that is an issue tickets only repository without
managing actual files.
If you have an issue (from Slack setting to container setting or
anything) that prevents you from accomplishing your goal or task and
that do not belong in the specific repositories on FNNDSC , asking
it on Slack #onboading or a proper channel is one way to solve it. And
another way is to open your issue on this "ChRIS_contributer-support"
Because the downside of asking someone your issue on Slack is that
your workflow might be stopped while you wait for someone trying to
solve your issue. And supporting tasks tends to be concentrated on
specific people. As most (every?) people from Red Hat are part-timers,
this can happen.
It's like a patient waiting for a doctor's diagnosis. When your doctor
is busy for other patients, you as a patient have to wait more. Your
next contact with the doctor is postponed.
Opening your ticket in the GitHub repository gives an opportunity that
everyone can help for your issue.
You can also ask people outside this ChRIS and COVID-Net projects to
help, pointing out your GitHub issue ticket URL with an easy way,
without explaining the entire context. For example you can ask your
colleague working on OpenShift or RHEL related to your issue or
tech-list ML (internal Red Hat mailing list).
So, if you are happy to support other members, please watch the
Right now there are 3 tickets.
Thank you & Cheers,
Have a nice weekend.
Jun | He - His - Him
I would like to share a list of people  from Red Hat working for COVID-Net.
The "List" sheet - A (Email Address), C (GitHub account name), D
(Slack account name) columns might be useful to contact them.
You can bookmark it. @duffy and I are also using the sheet to manage
the people's working status.
Jun | He - His - Him
I can't make it to tomorrow's status call, unfortunately, so I'll report my status here.
I did make some progress on the k8s task. The services are now all up and running, and connectivity is established. There's still work to be done, though.
All the best,
The ChRIS Community Central talk was moved to September 24; attached is
the meeting invite in case you'd like to join.
-------- Teachtaireacht Ar Aghaidh --------
Ábhar: Updated invitation: Community Central: Revisiting ChRIS:
Solutions for the Fr... @ Thu Sep 24, 2020 11am - 11:45am (EDT)
Dáta: Thu, 10 Sep 2020 18:13:12 +0000
Ó: Brian Proffitt <bproffit(a)redhat.com>
Freagra-Chuig: Brian Proffitt <bproffit(a)redhat.com>
I would like to discuss with every participant from Red Hat about this topic.
You might wonder why Duffy is promoting us to report the working status.
The reason is Duffy needs to report Alexandra every other week (once
per 2 weeks). Alexandra is managing the entire team-19 projects in Red
Hat. Alexandra and some people might use the report to decide if they
continue team-19 projects by the return (= our report) on the
investment (= our working time).
So, in this context, you can imagine what will happen when we do not report.
Let me share a process with you to have ideas (define it as A) to
improve this situation.
I just wanted to use this process I learned. :)
When we report our working status to Duffy regularly smoothly (=
define it as D), what are the merits (= B)?
## [B]: Merits to report the working status to Duffy.
* Duffy can spend less time summarizing the report.
* We can do our best to continue COVID-Net.
On the other hand, when we do NOT report the working status to Duffy
regularly (= define it as D' = D dash = opposite of D), there are
hidden merits for us. Because right now a few people are reporting it.
What are the merits (= C)?
## [C]: Mertis: NOT to report the working status to Duffy
* We can save time to report it to Duffy.
* We do not need to spend energy to remember and report the working
So, finally what is the idea [A] that is filling "both" [B] & [C]?
So, the [A] can be our realistic solution.
Jun | He - His - Him
Hi Team-19 volunteers!
You should have all received a calendar invite to a weekly meeting
called "ChRIS on the MOC." This is a weekly status / scrum meeting
that's been ongoing for the past 2+ years where we basically just share
quick status updates.
This meeting is completely optional for you, but we wanted you to be
aware of it and add you to the calendar invite so you would feel free to
drop in anytime, say hi, or drop in and show off what you've been
working on if you have something to share - a demo or just a rundown of
your work. We'd love to hear from you!
My status for this week is pretty light. I have been chugging away at
the new "join us" page at chrisproject.org:
I completed the first three tutorials and have the last two to go. I
also need to add it to the main nav bar. It's already linked up to
Looking forward to hear what everyone else has been up to!
Just wanted to give a regular call out to the open tasks we have on the
Team-19 kanban that are up for grabs in case you're looking for
something to work on. There is a green "help wanted" tag on all of the
new / open tasks that are in a good state to grab and go:
Here's a rundown of all of those issues at this point in time:
# 1. Add timing logic to pipelines in ChRIS backend #234
This is a new one; this is going to be really important to enable
unattended analyses in ChRIS out of the box.
# 2. Deploy the ChRIS Store to the MOC's OpenShift cluster #28
If you have experience with the MOC and are into devops, this is a good
one to grab.
# 3. Browser testing for COVID-Net frontend #102
This should have all the info you need to get started.
# 4. ChRIS UI: We need a JS front end for PACS search
This one involves front-end, there's an initial set of mockups posted
too, but if you have ideas for improvement on the design/mockups that is
totally welcome too! I haven't had time to revisit the design.
# 5. ChRIS Website: Design for Code section of chrisproject.org:
This section of the website needs some fleshing out, to give a bit of a
rundown of the repositories in our github org and help orient new
# 6. ChRIS Website: Content for Plugins section of chrisproject.org:
Another website page that needs content /design - see ticket for details.
# 7. ChRIS Store: Implementation of user groups / teams in the ChRIS
The idea is kind of similar to how you can have orgs or teams on GitHub.
We want to enable multiple users to be able to update plugins listed in
Don't hesitate to reach out (here, or in slack, or directly on the
tickets) if you're curious about any of these and would like more info.
If you would like to grab any tickets. feel free to assign it to
yourself (or reach out if you need perms to do so, depending on the repo
the ticket is filed against you might need help self-assigning) so
others know it's taken.