Skip to content

Commit 0dddd0f

Browse files
authored
Merge branch 'master' into Challenge-Covid-19
2 parents 2c737af + c206796 commit 0dddd0f

File tree

1 file changed

+51
-0
lines changed

1 file changed

+51
-0
lines changed
Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
## Meeting Agenda:
2+
### Tues, June 9th 8:00 a.m PST / 11:00 a.m EST 
3+
4+
- Welcome & Introduction of TSC - John 
5+
- TSC Members Introductions - All
6+
- Share TSC Charter - Sudharsana
7+
- Review PR #133 (Course Content Future) - Mike 
8+
- Discuss PR review process/ pdf creation timeline - Mike 
9+
- Review PR #103 - share our ideas on how we can put all this content into an FAQ and for links, just point to COBOL Hub page, to avoid data duplication/discrepancy. Discuss the idea with Scott (PR owner) and come to a solution - Mike & Sudharsana
10+
- Q&A
11+
12+
13+
## Meeting Minutes:
14+
Attendees: All Core team members & 12 other community participants
15+
16+
1. John opened with an introduction of role/purpose of a TSC:
17+
* set overall direction for the project
18+
* ensure have the resources available for success
19+
* be responsive to the community
20+
2. Core Team members introduced themselves
21+
3. Sudharsana shared the TSC mission and goals (TSC Charter)
22+
4. Mike walked through the restructured content of the repo and all the updates made to the readme.md file.
23+
* The course content has been split into 3 pieces
24+
* The beginner course is released in Getting Started 
25+
* Advanced topics in incubation
26+
* Testing in incubation
27+
* The readme.md file is always a good place to start and point people to when they are getting started with this content
28+
* The Getting Started book points to Providers who provide system access for doing the labs.
29+
* There is a commercial offering folder that showcases IDz. Note: this is the free trial version of the tool
30+
5. Mike reviewed PR #103 (Scott Cosel's PR) with the following suggestions:
31+
* Create a separate document for the FAQs and the Resources- this will help to keep the readme.md file simple and clear
32+
* Suggest pointing to the [COBOL video page](https://developer.ibm.com/technologies/cobol/series/cobol-fridays-webinar-videos) as opposed to individual video replays, etc. This will avoid data discrepancy/duplication and give access to all the other COBOL resources available on the [COBOL hub page](https://developer.ibm.com/technologies/cobol/)
33+
* Scott was good with these suggestions.
34+
6. Q&A
35+
#### How do we handle questions coming to Slack from Coursera offering?
36+
The core team will discuss this further on next weekly call
37+
38+
#### Setting a path for "What's next": are we going to put JCL as an important part of "Starting COBOL with z/OS" course - asking, because I can see a lot of people on Slack, having issues about understanding JCL, all those double slashes, dots, DD limitations etc
39+
This course is all about COBOL. And, the thought is with the DevOps tools available, focus can be on COBOL and the JCL part of it taken care by the modernization of the environment and tooling.That said, we would like to point our participants to the z/OS Practitioner that dives into JCL
40+
https://learn.ibm.com/course/view.php?id=6815
41+
https://learn.ibm.com/course/view.php?id=7419#section-4
42+
https://learn.ibm.com/course/view.php?id=7512
43+
44+
#### What is the cadence of the TSC calls?
45+
Monthly on second Tuesday
46+
47+
#### How to access the Slack channel?
48+
Link to the channel is in the readme.md file of the repo and is also sent out in the registration email when you signup for system access
49+
50+
#### Next Meeting
51+
Tues, July 14th 8 a.m PST / 11 a.m EST

0 commit comments

Comments
 (0)