"ChRIS_contributer-support" repository to open your issue
by Jun Aruga
Let me introduce a new GitHub repository "ChRIS_contributer-support"
[1] 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 [2], 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"
repository.
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
ChRIS_contributer-support repository.
Right now there are 3 tickets.
Thank you & Cheers,
Have a nice weekend.
Jun
[1] https://github.com/FNNDSC/ChRIS_contributer-support
[2] https://github.com/FNNDSC
--
Jun | He - His - Him
3 years, 2 months
Ideas to report working status regularly with a low energy
by Jun Aruga
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.
* etc
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
status regularly.
* etc.
So, finally what is the idea [A] that is filling "both" [B] & [C]?
So, the [A] can be our realistic solution.
Cheers,
Jun
--
Jun | He - His - Him
3 years, 2 months
Invitation: ChRIS weekly status meetings
by Máirín Duffy
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!
Cheers,
~m
3 years, 2 months
