-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COBOL Working Group #581
Labels
2-annual-review
Annual Review for a Project or Working Group
Comments
yarille
added
meeting-agenda-future
2-annual-review
Annual Review for a Project or Working Group
labels
Oct 23, 2023
jmertic
changed the title
COBOL Working Group Annual Review- 08/22/2024
COBOL Working Group - Annual Review
Oct 30, 2023
I'm lost, John. What's gong on?
*Cameron Seay, Ph.D.*
*Adjunct Instructor, East Carolina University*
*LinkedIn: https://www.linkedin.com/in/cameron-seay-985bb21/
<https://www.linkedin.com/in/cameron-seay-985bb21/>*
*COBOL Working Group: https://lists.openmainframeproject.org/g/wg-cobol
<https://lists.openmainframeproject.org/g/wg-cobol>*
My Calendar: https://calendly.com/cwseay
Zoom link: https://us02web.zoom.us/j/2840878546
…On Mon, Jul 29, 2024 at 11:54 AM John Mertic ***@***.***> wrote:
@cwseay <https://github.com/cwseay> Flagging this one for you Cam -
@slandath <https://github.com/slandath> will be reaching out on
scheduling.
—
Reply to this email directly, view it on GitHub
<#581 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6O7G54OYIU4Q453LOGLE3ZOZQRTAVCNFSM6AAAAABJQ3OOK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJWGI4TMMZVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey @cwseay - this is for the project annual review. |
I understand. Do I have action items? |
Not immediately - @slandath will reach out to coordinate rescheduling and then from there you can prepare your presentation inline with the guidelines at https://tac.openmainframeproject.org/process/review_cycle |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: