|
1 | 1 | ## Meeting Agenda: |
2 | 2 | ### Tues, June 9th 8:00 a.m PST / 11:00 a.m EST |
3 | | -[Meeting link](https://ibm.webex.com/meet/sudharsana.srinivasan) |
4 | | - |
5 | 3 |
|
6 | 4 | - Welcome & Introduction of TSC - John |
7 | 5 | - TSC Members Introductions - All |
8 | 6 | - Share TSC Charter - Sudharsana |
9 | 7 | - Review PR #133 (Course Content Future) - Mike |
10 | 8 | - Discuss PR review process/ pdf creation timeline - Mike |
11 | | -- 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 |
| 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 |
12 | 10 | - Q&A |
13 | 11 |
|
14 | 12 |
|
15 | 13 | ## Meeting Minutes: |
16 | 14 | Attendees: All Core team members & 12 other community participants |
17 | 15 |
|
18 | 16 | 1. John opened with an introduction of role/purpose of a TSC: |
19 | | -* set overall direction for the project |
20 | | -* ensure have the resources available for success |
21 | | -* be responsive to the community |
22 | | - |
| 17 | + * set overall direction for the project |
| 18 | + * ensure have the resources available for success |
| 19 | + * be responsive to the community |
23 | 20 | 2. Core Team members introduced themselves |
24 | | - |
25 | | -3. Sudharsana shared the TSC mission and goals (TSC Charter) |
26 | | - |
27 | | -4. Mike walked through the restructured content of the repo and all the updates made to the readme.md file. |
28 | | -* The course content has been split into 3 pieces |
29 | | -a. The beginner course is released in Getting Started |
30 | | -b. Advanced topics in incubation |
31 | | -c. Testing in Incubation |
32 | | -* The readme.md file is always a good place to start and point people to when they are getting started with this content |
33 | | -* The Getting Started book points to Providers who provide system access for doing the labs. |
34 | | -* There is a commercial offering folder that showcases IDz. Note: this is the free trial version of the tool |
35 | | - |
36 | | - |
37 | | -5. Mike reviewed PR# 103 (Scott Cosel's PR) with the following suggestions: |
38 | | -* Create a separate document for the FAQs and the Resources- this will help to keep the readme.md file simple and clear |
39 | | -* suggest pointing to the COBOL video page as opposed to individual video replays, etc. |
40 | | -https://developer.ibm.com/technologies/cobol/series/cobol-fridays-webinar-videos. 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/ |
41 | | -* Scott was good with these suggestions. |
42 | | - |
43 | | - |
| 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. |
44 | 34 | 6. Q&A |
45 | 35 | #### How do we handle questions coming to Slack from Coursera offering? |
46 | 36 | The core team will discuss this further on next weekly call |
47 | 37 |
|
48 | | -#### 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, coz I can see a lot of people on Slack, having issues about understanding JCL, all those double slashes, dots, DD limitations etc |
| 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 |
49 | 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 |
50 | 40 | https://learn.ibm.com/course/view.php?id=6815 |
51 | 41 | https://learn.ibm.com/course/view.php?id=7419#section-4 |
|
0 commit comments