IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

meeting-minutes.md 68.2 KB
Newer Older
1
2
3
4
* [Meeting Information](https://opensource.ieee.org/oscom/meetings/-/blob/master/README.md)
* [Meeting Agenda](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-agenda.md)
* [Meeting Attendance](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md)

5
6
**Open Source Committee Minutes**

7
8
Minutes are subject to OSCom edits and passive approval within two weeks of the meeting if there are no objections. They are for OSCom use only and are not to be copied or quoted for other than Committee business. 

9

10
[[_TOC_]]
11
## 2021 06 10 Draft Minutes<br>
12

13
14
15
16
**IEEE Standards Association Open Source Committee (OSCom)**<br>
Draft Meeting Minutes<br>
Teleconference/Webex<br>

17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
10 June 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-06-10-attendees). This meeting was quorate.

**Notes:**

1. Introductions and approval of the agenda - Robby
2. SA Standards Board Ops Manual review - Robby <br>
  2.1 [Feedback](https://opensource.ieee.org/oscom/meetings/-/issues/6) <br>
  2.2 Tabled to finalize language. Final language to be reviewed at the next meeting.
3. Pipeline Review - Robby for Josh <br>
  3.1 We expect two incoming proposals. <br>
  3.2 Make sure ICADEs are available for review. <br>
4. [Community Manager Report](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Robby for Josh <br>
5. ED Report - Silona <br>
  5.1 Community Update <br>
  5.2 Platform Features Update - with Lisa Marie Maginnis <br>
    5.2.1 Pages Microsites <br>
    5.2.2 Continuous Integration/Continuous Development (CI/CD) <br>
  5.3 [TAG: You're IT Workshop](https://saopen.ieee.org/upcoming-events/)<br>
6. Ad Hoc Check-in<br>
  6.1 Governance Ad Hoc - Don <br>
    6.1.1 Don and Josh will meet next week to set foundation and then schedule meeting.s<br>
  6.2 Naming Ad Hoc - Cat<br>
  6.3 OSCom OpsMan - Robby<br>
   6.3.1 Robby and Hong to meet tomorrow for discussion.<br>
   6.3.2 Meetings to begin soon.<br>
7. Adjourn <br>


## 2021 05 27 Minutes<br>

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
27 May 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-05-27-attendees). This meeting was quorate.

**Notes:**

1. Introductions and approval of the agenda - Robby <br>
2. ProCom [Feedback](https://opensource.ieee.org/oscom/meetings/-/issues/6) - Robby <br>
3. Pipeline Review - Josh <br>
  3.1 We hope for an update to the pipeline early next week. <br>
4. [Community Manager Report](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Josh <br>
5. ED Report - Silona <br>
  5.1 [March Public Status Deck](https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/IEEE_SA_OPEN_March_Status_Deck.pdf)<br>
6. Ad Hoc Check-in<br>
7.  SMDC MIBA Update - Chuck - A request for Feedback on the CERN 2.0 fmaily of licenses was sent to Entity contacts.
  7.1 [Public CERN Feedback](https://opensource.ieee.org/oscom/meetings/-/issues/4) is also welcome from individuals.   <br>
8. Adjourn <br>



## 2021 05 13 Minutes<br>

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
13 May 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-05-13-attendees). This meeting was quorate.

**Notes:**

1. Introductions and approval of the agenda - Robby <br>
2. Appointment of volunteer chair for ad hoc on model governance documents - Robby <br>
  2.1 Welcome to Don Wright. <br>
3. Informational Items - Robby <br>
  3.1 One Hour presentation on IEEE SA OPEN at Board of Directors meeting <br>
  3.2 CERN 2.0 Distribution <br>
4. Project Proposal Reviews - Josh <br>
  4.1 P7014 <br>
    4.1.1. [P7014 Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/9) <br>
    4.1.2. [PAR](https://development.standards.ieee.org/myproject-web/public/view.html#pardetail/7001)<br>
    4.1.3. Chuck proposes that we approve<br>
    4.1.4. Motion unanimously approved<br>
5. Request to ProCom - Yve <br>
  5.1 An issue will be created in the GitLab Group and that link posted to the mailing list for feedback. <br>
6. Pipeline Review - Josh <br>
7. [Community Manager Report](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Josh <br>
8. ED Report - Silona - Delayed to next meeting <br>
9. Ad Hoc Check-ins - Delayed to next meeting <br>
  9.1. Naming - Cat <br>
  9.2. Governance - Don <br>
  9.3. Operations Manual - Robby <br>
10. Adjourn <br>


## 2021 04 29 Minutes<br>
**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

120
121
122
123
124
125
126
29 April 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-04-29-attendees). This meeting was quorate.

**Notes:**
127
128
129
130
131
132
133
134
135
136
1. Introductions and approval of the agenda - Robby <br>
2. CERN Vote will be May 27th. Feedback has been extended to May 24th. - Robby <br>
  2.1 [GitLab Comment](https://opensource.ieee.org/oscom/meetings/-/issues/4)<br>
  2.2 Email to opensource@ieee.org Please add the subject 'CERN 2.0 public comment.’<br>
3. Welcome all Members and new Vice Chair<br>
4. Pipeline Review - Josh<br>
5. [Community Manager Report](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Josh<br>
6. ED Report - Silona <br>
  6.1 [Microsite Implementation Roadmap](https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/OSCom_Microsite_Implementation_Roadmap_Slide.pdf)<br>
  6.2 Reactivating Naming Advisory Group - Naming standards, microstes, chat channels, etc.<br>
Beth Hancock's avatar
Beth Hancock committed
137
  6.3 [Tool Workflow](https://opensource.ieee.org/technical-advisory-group/meetings/-/blob/master/Supporting%20Documentation/New_Tool_Addition_Workflow.pdf)<br> 
138
139
140
141
142
143
  6.4 Donation Drive<br>
  6.5 [May 4th Event](https://saopen.ieee.org/upcoming-events/)<br>
7. Appoint AdHoc Committees <br>
  7.1 Timelines and deliverables for [Operations Manual Updates](https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/OSCOM_Operations_Manual.pdf) - Don, Dennis, Robby (chair), Josh, Hong, Yve - end of June<br>
  7.2 Timelines and deliverables for model governance documents - Don, Michael, Josh volunteered. Hong will probably also be interested.<br>
  7.3 Naming Ad Hoc - Cat (Chair), Silona, Susan, Beth<br>
144
 
145
8. Adjourn<br>
146
147
148
149
150
151
152
153



## 2021 04 15 Minutes<br>
**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
15 April 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-04-15-attendees). This meeting was quorate.

**Notes:**
1. Introductions and approval of the agenda - Robby <br>
  1.1 Agenda was approved. <br>
2. 1484.2 <br> 
  2.1 [Integrated Learner Record Project Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/7) <br>
  2.2 [PAR](https://development.standards.ieee.org/myproject-web/app#viewpar/11656/8328) <br>
  2.3 [Open Credential Publisher Project Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/8) <br>
  2.4 Discussion occurred. <br>
  2.5 Robby declared his affiliation with the group under which the project is organized and recused himself from the vote. <br>
  2.6 Don moved to approve both projects. <br>
  2.7 Cat seconded the motion. <br>
  2.8 Motion carried. Robby abstained from the vote.  <br>
3. CERN Feedback - Robby <br>
  3.1 Please provide feedback in one of the following two ways: <br>
    * [Issue](https://opensource.ieee.org/oscom/meetings/-/issues/4) <br>
    * [Email](opensource@ieee.org) please add the subject 'CERN 2.0 public comment' <br>
Beth Hancock's avatar
Beth Hancock committed
176
 3.2 Feedback will be accepted through April 26th. All feedback will be shared publicly.<br>
177
178
179
180
181
182
183
184
185
4. Elect Vice Chair - Robby <br>
  4.1 Hong volunteered to serve. <br>
  4.2 She was accepted contingent on resolution of a procedural issue. <br>
5. Pipeline Review - Josh <br>
6. [Community Manager Report](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Josh <br>
7. ED Report - Silona <br>
  7.1 Work on Feature and Tool Review Processes <br>
  7.2 [May 4th Event](https://opensource.ieee.org/workshops/maymagworkshop/20210504-workshop-info) <br>
8. Use of platform for PARs in which the working group has been granted permission but for a different PAR - Josh<br>
Beth Hancock's avatar
Beth Hancock committed
186
  8.1 Standards Board Operations Manual 6.5.1 Project authorization:  "Use of the IEEE Open Source Platform for development of Open Source incorporated into an IEEE standard requires approval by the responsible committee of the IEEE SA Board of Governors. If a Standards Committee or Working Group intends to develop Open Source to be incorporated in an IEEE standard, the Standards Committee or Working Group shall indicate this intent to the responsible committee of the IEEE SA Board of Governors."<br>
187
188
189
  8.2 How to handle new PARs (informational item) OScom provides authorization to a working group (or a standards committee subgroup) to make use of the platform. Generally speaking there is an associated Project Authorization Request (PAR) associated with the WG.<br>
  8.3 After a WG has received authorization to use a platform, how does OSCom wish to handle additional PARs assigned to a given WG after the WG has been<br>
  8.4 When a standard is being revised what should be the process? <br>
190
9. Examination of [OSCom Operations Manual](https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/OSCOM_Operations_Manual.pdf) - Robby<br>
191
192
193
194
195
196
197
198
199
200
201
202
203
204
  9.1 Known issues include appointment of members and terminology<br>
  9.2 Potential issues include pilot projects, peer review, new functions (e.g. review of microsites, review of governance documents) - confirm that samples of governance documents are available<br>
  9.3 Written Comments: <br>
	 * I think "Approving" includes expectation that a project conform to rules imposed, without requirement of close oversight by the OSCom. Matter of narrow or broad interpretation. The comment that every change in text in a project be specifically approved seems way too narrow. <br>
   * Governance of OS projects ought to have some approval process, because brand and reputation of IEEE OS platform will likely be affected. <br>
 10. Adjourn<br>



## 2021 04 01 Minutes<br>
**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

205
206
207
208
209
210
211
01 April 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-04-01-attendees). This meeting was quorate.

**Notes:**
Beth Hancock's avatar
Beth Hancock committed
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
1. Introductions and approval of the agenda - Robby <br>
  1.1 Cat moved to approve.  <br>
  1.2 Dennis seconded. <br>
  1.3 Agenda was approved. <br>
2. 1484 <br> 
  2.1 [Project  Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/7) <br>
  2.2 [PAR](https://development.standards.ieee.org/myproject-web/app#viewpar/11656/8328) <br>
  2.3 Discussion of next steps for completing the proposal so that it can be voted on. <br>
3. Update on the CERN license Process - Robby <br>
  3.1 Please provide feedback in one of the following two ways: <br>
    * [Issue](https://opensource.ieee.org/oscom/meetings/-/issues/4) <br>
    * [Email](opensource@ieee.org) please add the subject 'CERN 2.0 public comment' <br>
4. Operations Manual Updates - Robby <br>
  4.1 We will be updating the operations manual <br>
    4.1.1. [Most Recent version](https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/OSCOM_Operations_Manual.pdf) <br>
5. Pipeline Review - Josh <br>
  5.1 Two new submissions for Q2 expected <br>
6. [Community Manager Report](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Josh <br>
7. ED Report - Silona <br>
  7.1 Please check out activity in the Advisory Groups <br>
  7.2 [May 4th Workshop](https://opensource.ieee.org/workshops/maymagworkshop/20210504-workshop-info) <br>
8. New Business <br>
9. Adjourn <br>
235
236
237
238
239
240
241


## 2021 03 18 Minutes<br>
**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
18 March 2021<br>
10:00 a.m. – 11:00 a.m. Eastern<p>

**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-03-18-attendees). This meeting was quorate.

**Notes:**
1.  Approval of the agenda, administrative items <br>
 1.1 Agenda was approved. <br>
2. CERN License Discussion and Public Review
2.1 [CERN License information](https://ohwr.org/project/cernohl/wikis/Documents/CERN-OHL-version-2) from the Open Hardware Repository <br>
3. Project Pipeline - Josh <br>
 3.1 Josh gave a brief update on the project in queue and answered questions. <br>
4. [Community Manager Update](https://opensource.ieee.org/oscom/meetings/-/wikis/Community-Manager-Report) - Josh
5. ED Report - Beth for Silona <br>
	5.1 Silona had to leave the meeting early for a speaking engagement, so Beth gave a brief update on her behalf. <br>
6. Future Actions: Review and Updates of Governance Documents - Robby <br>
  6.1 Robby spoke about the documents that OSCom will be updating and the different sources of feedback he recommends. <br>
7. Adjourn <br>


## 2021 03 04 Minutes<br>
**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

268
04 March 2021<br>
269
10:00 a.m. – 11:00 a.m. Eastern<p>
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
**Attendees:**
Please see [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-03-04-attendees). This meeting was _not_ quorate.

**Notes:**
1.  Approval of the agenda, administrative items <br>
 1.1 As the meeting was not quorate, we held an informal meeting. <br>
 2. Project Proposal  <br>
 2.1 As this was an informal meeting, Robby continued to act as chair while we addressed P1484.2. <br>
 2.2 [Project  Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/7) <br>
 2.3 [PAR](https://development.standards.ieee.org/myproject-web/app#viewpar/11656/8328) <br>
 2.4 A vote on this proposal will be taken by email ballot after BOG approval of OSCom nominees. <br>
3. [CERN License Update](https://ohwr.org/project/cernohl/wikis/Documents/CERN-OHL-version-2) <br>
 3.1 Yvette provided [this brief slidedeck](https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/CERN_OHL_Update_OSCom_20210303.pdf) explaining the approval process for new licenses and license updates, along with a summary of the CERN licensing changes.  <br>
4. Project Pipeline - Josh <br>
 4.1 Josh gave a brief update on the project in queue and answered questions. <br>
5.  Simone Ravaioli and Marty Reed joined us and spoke and answered questions on the p1484.2 project discussed in item 2 above. <br>
6. ED Report - Silona <br>
	6.1 Silona was unable to attend, so Beth gave a brief update on her behalf.
7. Adjourn <br>


291
## 2021 02 11 Minutes
292
293

**IEEE Standards Association Open Source Committee (OSCom)**<br>
294
Meeting Minutes<br>
295
296
Teleconference/Webex<br>

297
11 February 2021<br>
298
10:00 a.m. – 11:00 a.m. Eastern<p>
299
300
301
302
303

**Attendees**

See [Attendance list](https://opensource.ieee.org/oscom/meetings/-/blob/master/meeting-attendance.md#2021-02-11-attendees). This meeting was quorate.

Beth Hancock's avatar
Beth Hancock committed
304
**Notes:**
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
1. Introductions <br>
  1.1 Introductions were completed as we had many new attendees. <br> 
2. Approval of the agenda, administrative items <br>
  2.1 Chuck moved to approve the agenda. <br>
  2.2 Annette seconded the approval. <br>
  2.3 Agenda approved. <br>
3. Appointments and Goals <br>
  3.1 Appointments are still awaiting approval <br>
  3.2 Robby gave a summary of [OSCom’s Roles and Goals for 2021](). <br>
4. Project Proposal  <br>
  4.1 To address P1484.20.1, Robby recused himself from his role as chair. Dennis took over this role. <br>
  4.2 [Project  Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/6) <br>
  4.3 [PAR](https://development.standards.ieee.org/myproject-web/public/view.html#pardetail/110) <br>
  4.4 Annette moved to approve this project. <br>
  4.5 Chuck seconded the approval <br>
  4.6 Project approved. <br>
5. [CERN License Update](https://ohwr.org/project/cernohl/wikis/Documents/CERN-OHL-version-2) <br>
322
  5.1 Yvette provided [this brief slidedeck](https://opensource.ieee.org/oscom/meetings/-/blob/master/Supporting%20Documentation/CERN_OHL_Update_OSCom_20210303.pdf) explaining the approval process for new licenses and license updates, along with a summary of the CERN licensing changes.  <br>
323
324
325
326
327
328
329
330
331
332
333
334
335
6. ED Report - Silona <br>
  6.1 Silona gave a brief update on progress on the platform and answered questions. <br>
7. [Community Manager Report](https://opensource.ieee.org/oscom/oscom/-/wikis/community-manager-report) - Josh <br>
8. Adjourn <br>



## 2020 12 03 Minutes

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
03 December 2020<br>
6:00 p.m. – 7:00 p.m. UTC<p>

**Attendees**

See [Attendance list](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#2020-12-03-attendees). This meeting was quorate.
 
1. Approval of the agenda, previous minutes and introduction of new guests <br>
  1.1 Annette moved to approve the agenda <br>
  1.2 Chuck seconded the motion. <br>
  1.3 Agenda was approved. <br>
2. Project Approval<br>
  2.1 [P1765 Reference Waveforms, Baseline EVM Algorithm, and related source code](https://opensource.ieee.org/oscom/official-project-requests/-/issues/5) - Kate Remley and Martin Hudlička presented <br>
  2.2 [Updated PAR](https://opensource.ieee.org/oscom/oscom/-/blob/master/Supporting%20Documents%20for%20Meeting%20Notes/Updated-PAR-P1765-Dec-2019_R1.docx)  <br>
    2.2.1 Annette moved to approve <br>
    2.2.2 Chuck seconded the approval <br>
    2.2.3 The project was approved <br>
3. Next Meeting <br> 
  3.1 Regular meeting on Friday, December 18th at 9am Eastern. <br>
4. ED Report - Silona <br>
  4.1 December 8th - [Spirit of Mentorship Workshop](https://opensource.ieee.org/workshops/advisory-groups) Update   <br>
  4.2 Advisory Group Update <br>
  4.3 Other updates <br>
5. Community Manager Report - Josh [10 mins] <br>
  5.1 Platform Statistics and Status  <br>
    5.1.1 About 500 users, 237 projects (200 projects by users) <br>
    5.1.1 Moving in to Dev and QA  <br>
  5.2 Project Pipeline <br>
    5.2.1 We expect one more project for approval before year end. <br>
6. ICCom Update (Robby) <br>
7. SMDC report - Chuck <br>
8. New Business <br>
9. Adjourn <br>


## 2020 11 13 Minutes

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

13 November 2020<br>
1:00 p.m. – 2:00 p.m. UTC<p>

**Attendees**

See [Attendance list](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#2020-11-13-attendees). This meeting was quorate.

**Notes:**

**1. Approval of the agenda, previous minutes and introduction of new guests** - Robby <br> 
  1.1 Dennis motioned to approve the consent agenda.<br>
  1.2 Chuck seconded the motion.<br>
  1.3 The motion was approved unanimously.<br>

**2. Executive Director Report** - Silona <br> 
  2.1 We continues to recruit for advisory groups. <br>
  2.2 We are deep in work for the December 8th Advisory Group Workshop. <br>
 
**3. Community Manager Report** - Josh <br>
 3.1 First to second week of December for the new platform to be available.<br>
 3.2 Project Pipeline includes: Power and Energy 1457 and IEEE ILR <br>

**4. SMDC Report** - Chuck <br>
  4.1 Chuck gave a thorough summary of what the SMDC is doing, both in philanthropic and venture efforts.<br>
  4.2 OSCOM is moving toward becoming a traditional IEEE program. <br>

**5. New Business** <br>
  5.1  No new business was reported. <br>

**6. Next Meeting** <br>
  6.1 Our next meeting will be **Thursday December 3rd at 13:00 Eastern.** <br>

**7. Adjourn** <br>



## 2020 10 30 Minutes

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

30 October 2020<br>
1:00 p.m. – 2:00 p.m. UTC<p>

**Attendees**

See [Attendance list](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#2020-10-30-attendees). This meeting was quorate.

**Notes:**

**1. Call to Order; Approval of the Agenda** <br>
The Agenda was approved.

**2. Executive Director Report** <br>
  2.1 Silona spoke regarding leadership roles for Advisory Groups that are being filled.<br>
  2.2 A [slidedeck](https://opensource.ieee.org/oscom/oscom/-/blob/master/Supporting%20Documents%20for%20Meeting%20Notes/ATO_Retrospective_2020.pdf) was presented regarding All Things Open (ATO).  <br>

**3. Community Manager Report** <br> 
  3.1 Josh gave a brief summary of progress on the platform.<br>
  3.2 Josh gave a summary of external projects. A full summary will be appended later.<br>

**4. Minutes Process**<br>
  Approval of Previous Minutes will be added as part of consent agenda.<br>

**5. Volunteers for Next Year** <br>
  Robby spoke regarding volunteer recruitment for next year’s OSCom.<br>

**6. SMDC Report**<br>
  Chuck gave an update on the state of the SMDC for Incubation<br>

**7. New Business**<br>
  Robby called for any additions or new business. None was reported.<br>

**8. Next Meeting**<br>
  Our next meeting will be Friday, November 13th, 2020 at 9am Eastern.<br>

**9. Adjournment**<br>
  The meeting was adjourned.<br>



## 2020 10 16 Minutes


**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

16 October 2020<br>
1:00 p.m. – 2:00 p.m. UTC<p>

**Attendees**

See[ Attendance list](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20201016-attendees). This meeting was quorate.

**Notes:**

**1. Call to Order; Approval of the Agenda and Previous Minutes; Introduction of Guests**

Robby called the meeting to order and the agenda was approved. Our guest Thomas Cox briefly introduced himself.

**2. Project Approvals** (15 Min)

  2.1 Blockchain Governance Standards Working Group <br>
  * 2.1.1 [Project Proposal](https://opensource.ieee.org/oscom/official-project-requests/-/issues/4)<br>
  * 2.1.2 PAR [P2145](https://standards.ieee.org/project/2145.html)<br>
  * 2.1.3 Annette moved to approve the project.<br>
  * 2.1.4 Chuck seconded the approval.<br>
  * 2.1.5 The project was approved unanimously.<br>

There was a discussion of available licenses and adding licenses. 

**3. Executive Director Report** - Silona (15 Min)

  3.1 Silona reported on advisory group status <br>
  3.2 The Naming Advisory Group is awaiting input on recommendations from Marketing before issuing a formal recommendation to OSCom. <br>
  3.3 We will have a presence, including a booth, at All Things Open. If you’d like to know more, please [visit their site](https://2020.allthingsopen.org/). Attendance is free.<br>
  3.4 A brief review of the IEEE SA OPEN website occurred. Feedback is welcome.  Please send it to [opensource@ieee.org](mailto:opensource@ieee.org). The website address is:  [saopen.ieee.org](https://saopen.ieee.org) <br>


**4. Community Manager Report** - Josh (10 mins)

4.1 Josh gave a brief overview of the platform status.<br>
4.2 Josh and Andy (Oram) are working on a more thorough presentation of project statistics.<br>
  * 4.2.1 One or possibly two new project proposals are expected to be ready for review at the next meeting.<br>

**5. Volunteers for Next Year**

Robby spoke regarding the need for new volunteers and reiterated the changes coming as OSCom shifts to a more operations-focused role.

**6. Next Meeting**

Our next meeting will be Friday, October 16th, at 9am Eastern.

**7. Adjournment**


## 2020 10 02 Minutes

**IEEE Standards Association Open Source Committee (OSCom)**<br>

Meeting Minutes<br>

Teleconference/Webex<br>


2 October 2020 <br>

1:p.m. - 2:00 p.m. UTC<p>


**Attendees**<br><br>

See [Attendance list](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20201002-attendees). This meeting was quorate.<p>

**Notes:**

**1. Call to Order; Approval of the Agenda and Previous Minutes**

Robby called the meeting to order and the agenda was approved. Previous minutes will be distributed to committee members via email for ballot.

**2. Naming Advisory Group Progress**

Beth spoke regarding progress on the Naming Advisory Group, including meeting date and drafts of documentation for the group. 

**3. ED Report**

The IEEE SA OPEN Webpage update is currently under review. A link and information to elicit your feedback will be distributed before the next meeting.

**4. Community Manager Report**

We expect one and possibly two new proposals for review at the next meeting.

**5. Volunteers for Next Year**

Robby and Chuck spoke regarding the changes coming to OSCom’s shift to a more operations-focused role.

**6. Next Meeting**

Our next meeting will be Friday, October 16th, at 9am Eastern.

**7. Adjournment**



## 2020 09 18 Minutes

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>


18 September 2020 <br>
1:p.m. - 2:00 p.m. UTC<p>

**Attendees**<br><br>
See [Attendance list](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200918-attendees). This meeting was not quorate.<p>

**1. Call to order and approval of the agenda (Robby)**<br>

Robby opened the meeting and the agenda was approved. It was noted that this meeting does not meet quorum and that items 2 and 3 on the agenda would be reviewed, but that balloting would need to be deferred to email, as this is an informal meeting.<p>

**2. OSCom Official Project Request from Verifiable Vaccinations**<br>

Approval of this request was deferred to the email ballot process. The PAR was reviewed and discussed briefly.

- [Request for Approval *p2418.6 Verifiable Vaccinations*](https://opensource.ieee.org/oscom/official-project-requests/-/issues/3) 
- [See also, Approved PAR](https://development.standards.ieee.org/myproject-web/public/view.html#pardetail/6673)<p>


**3. Review of OSCom Webpage**<br>

- Those present reviewed the [OSCom webpage](https://docs.google.com/document/d/1V113oXAHAn5dUt6b94vX0Lmw05RjmaWILXV5k_LDU5g/edit) 

- Robby created the Naming Advisory Group to review the use of 'Official" in our documentation and to address other naming concerns. Members include:  Helene Workman, Don Wright, Josh Gay, Silona Bonewald, along with an OS Community representative, and a representative of IEEE SA Marketing.
<p>

**4. Executive Director Update** <br> 

Silona reported on progress on the platform and website dates.<p>

**5. Best Practices Update**<br>

Andy Oram spoke regarding the creation of best practices documentation for the community.<p>

**6. Community Manager Update (Josh)**<br> 

Josh gave a report on the progress fo the platform.<p>

**7. IPR Update**<br>

An update was received from Yvette Ho Sang regarding IPR: We received one CLA under the Apache License for Contributions to the UVVM project on 4 September.<p>

**8. Next Meeting**<br>

Our next meeting will be Friday, October 2nd, 2020 at 9:00am Eastern.<p>

**9. Adjournment**<br>


## 2020 09 04 Minutes

**IEEE Standards Association Open Source Committee (OSCom)**<br>
Meeting Minutes<br>
Teleconference/Webex<br>

04 September 2020<br>
1:00 p.m. – 2:00 p.m. UTC<p>


**Attendees**<br>

See [Attendance list](Attendance-List). This meeting was quorate. <br>
<br>
**1. Call to order and approval of agenda (Robby)** <br>

Robby opened the meeting and the agenda was approved.<p> 

**2. Proposed meeting shift (Beth)** <br>

OSCom meeting schedule will be changed as follows: 

- The November 27th meeting will now be on December 4th. 
- The December 11th meeting will now be on December 18th. 

**3. Change to Peer Review (Robby)** <br>

Robby announced the following changes: 

- The Peer Review (Ad Hoc) subcommittee is being terminated  
- The Technical Advisory Group will handle drafting of the peer review process
- Efforts will be made to recover information from the subcommittee that was formed as their input would be valuable

**4. Executive Director update (Silona)**<br>

Silona provided a progress report on the new SA Open website.<p>  

It was noted that feedback is being encouraged via the [Welcome project's issues](https://opensource.ieee.org/groups/welcome/-/issues).

**5. Community Manager update (Josh)**<br>

- Josh shared an overview of the architectural update. 
- Josh introduced Daniel Sabin to present the IEEE PQDIF Software Libraries.

**6. OSCom approval of Official Project Request by IEEE PQDIF Software Libraries**<p>

**Motion:** A motion to approve the IEEE PQDIF Software Libraries project was made by Chuck and seconded by Dennis. <p>

**Vote:** Approve IEEE PQDIF Software Libraries as an Official IEEE Open Source Project. [yes=4, no=0]<p>

**Resolved:** IEEE PQDIF Software Libraries is an Official IEEE Open Source Project<p>

**7. Adjournment** 


## 2020 08 21 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200821-attendees)

* The agenda was approved and Robby introduced new guests.
* Robby announced that the IEEE SA BOG has approved the proposed changes to the SASB Operations Manual. Once the changes have been made and solidified, there will be another review of the OSCom Operations manual to ensure consistency with the changes and with current practice. 
* Silona introduced the new contractors for her team, who will be supporting Open Source as it launches:
  * Beth Hancock - Project Manager - Focused on OSCom administration, including meeting management 
  * Andy Oram - Community Architect  - Focused on supporting IEEE SA Open communities
  * Heather Vescent - Product Manager - Focused on supporting IEEE SA Open product growth
  * Katie Schueths - Program Manager - Focused on IEEE SA Open coordination and advisories. 
* Silona reported that progress on new features continues. Release continued to be planned for next month: 
  * Each individual project will be able to create their own webpages and documentation via a static site generator (Gitlab Pages) and project management tools.
  * The landing page will be updated with enhanced Getting Started information, Roadmap, Products to facilitate users with getting set up on the platform, Mattermost, etc. 
* Katie walked the Committee through the steps to create an account and add notifications     
  * There was a request for step-by-step instructions to submit a request using the template. 
  * It is requested that all OSCom members set up notification to be alerted of any new submissions, as review of these submissions is the committee's primary responsibility. 
  * Feedback is welcome via submitting an issue.
* Josh provided an update on platform statistics and existing IEEE Open Source Projects.
* Topics for the next meeting:  Update on Peer Review, Review of (3) new projects (pending submission of project inquiry forms).  

## 2020 08 07 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200807-attendees)

* The agenda was approved. 
* Platform updates - Silona reported that new features are anticipated for release next month: 
    * Each individual project will be able to create their own webpages and documentation via a static site generator (Gitlab Pages) and project management tools.
    * The landing page will be updated with enhanced Getting Started information, Roadmap, Products to facilitate users with getting set up on the platform, Mattermost, etc. Please submit website content suggestions via email.
* Katie walked the Committee through the steps to get to the [Project Inquiry Form](https://opensource.ieee.org/oscom/official-project-requests) (Groups-Explore Groups-OSCOM-Official Project Requests). 
    * Former projects that were not approved as Official IEEE Open Source Projects will be asked to resubmit. 
    * There was a request for step-by-step instructions to submit a request using the template.
    * OSCom members would need to set up notification alerts if they would like to be notified of any new submissions. 
    * Feedback is welcome via submitting an issue.
    * There was a suggestion to conduct at a future meeting a tutorial on how to get on the platform.
* Yve reported that Legal Counsel is reviewing the following licenses: CERN OHL-S and OHL-P, BSD-3 Clause Clear and OpenAirInterface.
* Josh provided an update on the existing IEEE Open Source Projects.
* Topics for the next meeting: (a) Three projects have expressed interest in submitting a Project Inquiry Form for OSCom review. (b) Update on Peer Review.  


## 2020 07 24 Minutes 

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200724-attendees)

* The agenda was approved. Silona introduced Katie Schueths, who will be project managing the logistics for the IEEE SA Open advisory groups and roadshow.

* It was noted that, while these advisory groups represent the voice of the community, they are not IEEE SA governing bodies and do not have formal authority. They will be operating as open source projects, using the platform to conduct business. 

* There was a brief demo of the [Marketing Advisory Group](https://opensource.ieee.org/marketing-advisory-group) subgroups/projects. 

* The Technology Advisory Group is currently planning two projects (1) feature requests from non-developer and (2) customer requests.

* OSCom members were asked to contact Silona if they would like to learn about using the platform and the tools available. 

* Future meetings - It was agreed to henceforth schedule OSCom meetings every two weeks. There was a question about extending the length of the meeting to 1.5 hr; Robby will explore this further.
  
## 2020 07 17 Minutes 

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200717-attendees)

[Project inquiry form](https://docs.google.com/document/d/1GEzryW5V04Jdv9vDRZnhkS7jYp_AniLvhtkEKNFJWYk/edit?usp=sharing) 
* Robby mentioned that "Project Inquiry Form" may be a misnomer since this is intended to be a simple form that would be used for applying to become an Official IEEE Open Source Project. 
* Project governance would be reviewed separately, but it was agreed that some type of project governance should exist. Silona reported that part of the charge of the Open Source advisory groups will be to create tutorials and guidance on how to create governance documents, rather than requiring projects to use default governance documents or templates. A page of references on good governance documents can be done fairly quickly, and there are lots of examples available online to address the different scenarios and use cases from an IEEE perspective. 
* It was moved (Dennis), seconded (Alfredo) and voted to approve the Project Inquiry Form as written. No objections.
* Approval is contingent on the form being compliant with IEEE's data access and use policy.
* There was a request to add the following placeholder language:"References to governance documents will be added later." 

Community Manager Report   
   a. [Approval Requests](https://opensource.ieee.org/oscom/approvals/-/issues) - Josh has worked recently with both OSVVM and UVVM to get clarification on their IPR. Dennis reported that a [blog](https://www.linkedin.com/pulse/osvvm-call-participation-jim-lewis/?trackingId=4rPKSBYDpWiukTYZ5Q0dhg%3D%3D) was recently published announcing that OSVVM has received the go ahead to upload their repositories onto the IEEE Open Source GitLab hosting platform. Josh will get back to OSCom regarding the recommendation to help with IPR issues and licensing.  
   b. OSCom reviewed the default governance models.  
**i.** [simple example](https://opensource.ieee.org/snippets/5) - The following suggestions were made under License: (1) "See the LICENSE file distributed with this work for ~~copyright~~ **all appropriate legal notices** and
licensing information, the AUTHORS file for a list of copyright
holders, and the CONTRIBUTORS file for the list of contributors." (2) "~~SPDX-License-Identifier~~ **License**: BSD-3-Clause" <br>
**ii.** [medium-complexity (WIP)](https://opensource.ieee.org/oscom/maintain/-/blob/CONTRIBUTING_example/content/CONTRIBUTING_example.md)  
The plan is to have the OS Community Groups review these governance models. <br>
   c. Platform user stats - Josh reported that there has been a 5% uptick in users.

ED Report - Silona reported that she hired a contractor to assist with management of the Open Source advisory groups. Meetings are expected to be begin in 1-2 weeks.   
    
[Peer review](https://opensource.ieee.org/oscom/peer-review) - Tabled

Future Meetings - Topics for next meeting:
* Review of all OS projects
* Introduction of new hire
* Discussion on terminology (engage marketing)

## 2020 06 26 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200626-attendees)

* Yve reported on the final update to the [OSCOM Declaration](https://opensource.ieee.org/oscom/oscom/uploads/aedb377bfefae4108ac56ddbf5235466/OSCom_Declaration_Form_NAME_20200619.pdf), which refers to the duration of the classification.
* OSCom reviewed the comments on the [Project inquiry form](https://docs.google.com/document/d/1xUfFKK5AX2S7zKugRYNrv3E9OUdWcY28p5OCgwFTwxE/edit?usp=sharing). There was discussion on whether to allow other options for licenses, as well as default options for security and governance, including appeals. Once the document has been  edited and cleaned up, it will be sent to OSCom for ballot, with copy to the OSCom mailing list (regular OSCom attendees).  
* Alfredo asked about potential liabilities resulting from peer review. This item has been forwarded to Legal. 
* No Meeting on 3 July (U.S. 4th of July holiday)

## 2020 06 19 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List) 

* Robby Robson presented a simplified project inquiry form developed by him and Adam Newman (Sr. Directors, IEEE SA) based on input and suggestions on the previous inquiry form 
  * Joshua Gay asked to provide a simplified/default governance model for review by OSCom by EOB June 24th. 
* Joshua Gay provided an update and status on UVVM
* Silona presented a roadmap for developing and growing SA Open advisory groups  
* Chuck Adams: provided an update and overview of the SA Venture business model under developed 
* Robby Robson: announced next meeting will be on June 26th; no meeting on July 3rd. 

## 2020 06 12 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200612-attendees) 

1. There were no objections to approval of the agenda. <br>
2. Robby provided an update on the proposal that were reviewed and approved by the IEEE SA Standards Board [Procedures Committee](https://standards.ieee.org/content/dam/ieee-standards/standards/web/governance/procom/procom-01062020min.pdf) during its 1 June meeting. The changes address harmonization of terms and the initiation of an open source project. The proposed changes are currently with the Standards Board undergoing a 30-day ballot. <br>
3. Silona reported that she is working on getting the structure in place for the three advisory groups: Marketing, Community, Technical. There will be staff and volunteer leads for each group. The Marketing group would include use cases, events, policies and procedures, etc., with the intent to provide the tools to help the projects self-organize. <br> 
4. [Approval Requests](https://opensource.ieee.org/oscom/approvals/-/issues) - No updates <br> [Project inquiry form](https://docs.google.com/document/d/1GEzryW5V04Jdv9vDRZnhkS7jYp_AniLvhtkEKNFJWYk/edit) - OSCom plans to take a vote on the form at the next meeting. The goal is to keep the form as simple as possible, while making sure that there is nothing missing. While the vote is limited to OSCom members, everyone is welcome to comment. There was a question regarding plans to include CERN 2.0 as a license for hardware, and the process by which new licenses are approved: IEEE Legal reviews and approves, after which it is sent to OSCom for approval. Currently there is a hiatus on review and approval of new licenses until the platform is stable. <br> 
5. Alfredo reported on the recent activities of the [Peer review](https://opensource.ieee.org/oscom/peer-review) group. He is waiting for input from Marketing regarding the draft Call for Participation. <br>
6. Topics for next meeting: Approval of project inquiry form; UVVM, community architecture, Venture model. FYI There will be no Meeting on 3 July (U.S. 4th of July holiday) <br>


## 2020 05 29 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200529-attendees)

1. The agenda was accepted with no objections. There was no quorum present. It was noted that the RevCom meeting is being held concurrently.   
2. Silona reported on her efforts regarding a marketing plan for 2020 and 2021. The plan would include the development of collateral, community, marketing, and technical guides. It is intended to be created on an open platform, which would include input from the community via their use cases.    
3. a. [Approval Requests](https://opensource.ieee.org/oscom/approvals/-/issues) - Josh reported that UVVM's request is being held off until the next meeeting.   
   b. [Project inquiry form](https://docs.google.com/document/d/1GEzryW5V04Jdv9vDRZnhkS7jYp_AniLvhtkEKNFJWYk/edit) - Robby reported on the suggested changes to the inquiry form, which provides an option for a project to submit a governance document, or fill out the information on the form as needed. This is intended to facilitate the initiation of an IEEE Open Source project. Josh reported that submissions will likely be done by editing an issue on the platform; an online/web form is anticipated by the end of summer.  
4. Robby reported on [proposed changes](https://app.box.com/s/q1hqmo5bwtv7e5prhxyhee19cw25rm99) that have been submitted for consideration at the [next ProCom meeting](https://standards.ieee.org/content/dam/ieee-standards/standards/web/governance/procom/agenda.pdf). Anyone interested in attending the ProCom meeting (or any of the SASB committee meetings) should send an email to [Dave Ringle](mailto:d.ringle@ieee.org). Folks who have comments or are planning to comment are requested to first contact [Robby](mailto:robby@computer.org) over the weekend, prior to Monday's ProCom meeting.  
5. There is a meeting conflict on 5 June with the SASB Forum; the June 5 OSCom meeting has been cancelled. The SASB meeting schedule can be found [here](https://standards.ieee.org/about/sasb/meetingnotice.html). The next OSCom meeting will be held on 12 June.


## 2020 05 22 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200522-attendees)

1. The agenda was approved with no objections.   
2. Proposal to the IEEE SA Standards Board Procedures Committee - Robby and Yvette provided a background on a new proposal for the [ProCom agenda](https://standards.ieee.org/content/dam/ieee-standards/standards/web/governance/procom/agenda.pdf). The proposed update would not require NesCom approval for the use of open source incorporated in standards; however, a Working Group that is developing open source incorporated into standards will need to submit a project inquiry form to OSCom. <br>   
3. [OSCom declaration](https://opensource.ieee.org/oscom/oscom/-/issues/2) update - There were no comments or objections regarding the [updated version](https://opensource.ieee.org/oscom/oscom/uploads/c7884e1f142320a1e1407d3e0ef68012/OSCom_Declaration_Form_NAME_20200509.pdf). This will be the version that OSCom members will be asked to sign. <br>
4. Community Manager's Items  <br>
   a. [Project inquiry form](https://docs.google.com/document/d/1GEzryW5V04Jdv9vDRZnhkS7jYp_AniLvhtkEKNFJWYk/edit) - Josh requested feedback on the latest version. There were suggestions to add the 'Affiliation' of the Project Lead, and 'Optional' to the applicable questions. Josh requested that comments be entered directly into the [Google doc](https://docs.google.com/document/d/1GEzryW5V04Jdv9vDRZnhkS7jYp_AniLvhtkEKNFJWYk/edit) by Wednesday May 27. Observer comments are welcome. Josh will schedule a separate meeting, if needed, to go over comments.       
   b. [Maintainers Manual](https://opensource.ieee.org/community/manual) - No update.    
   c. [Approval Requests](https://opensource.ieee.org/oscom/approvals/-/issues) - Josh mentioned that he will be helping a few projects, i.e. UVVM and two standards projects, to fill out and submit project inquiry forms. The latest version will be used. It was noted that, at this time, information is not automatically tracked in the myProject database. <br> 
5. ED's report was tabled until the next meeting. <br>  
6. Future Meetings <br>
   a. Topics for next meeting: ED update, ProCom update, UVVM approval   
   b. Conflicts (e.g. with SASB) - and reminder about upcoming SASB meetings - It was noted that the May 29 OSCom meeting is scheduled at the same time as the next RevCom meeting; however, no schedule conflicts were raised by any of the members present. Additionally, there is a meeting conflict on 5 June with the SASB Forum; the June 5 OSCom meeting has been cancelled. The SASB meeting schedule can be found [here](https://standards.ieee.org/about/sasb/meetingnotice.html). <br>      

Alfredo provided the following report offline: <br>
* [Peer review](https://opensource.ieee.org/oscom/peer-review) <br>
1. I have completed setting up the group's repository:
   [https://opensource.ieee.org/community/peer-review/admin](https://opensource.ieee.org/community/peer-review/admin) <br>
2. We are using issues to track action items. We have not discussed deadlines and a project schedule yet but that shall be on the committee's next call <br>
3. We will request help from IEEE-SA marketing in sending a call for participation to all IEEE members to get new members for the committee <br>
4. We have split some initial tasks among the group and I am really encouraged by the enthusiasm of the committee members. <br>

## 2020 05 08 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200508-attendees)

1. There were no objections to approve the agenda.
  
2.  Silona reported that SA Open Planning will be moving to the platform. The IEEE SA Open Mission, Vision, and Core Values have been drafted and will be presented to the SA BOG. Three communities have been identified: Marketing, Technical, and Community. Participants are invited to join a Marketing Advisory Group. The team is also working on creating the Technical and Community groups.  
 - Josh reported on the new projects and user statistics, which include student groups that are migrating from Github.  
 - Yve reported that no new CLAs were received since last week. A sentence was added to the OSCom declaration to address questions about the term of the declaration. It was noted that documents will need to have the proper confidentiality marking. Yve will refer to the legal team about the confidentiality considerations for members who bring in IEEE SA Open customers or clients.  
  
3. Members reviewed Chuck's comments on the updated Open Source Content in AudCom Baselines. There was discussion about the removal of Maintainer, which may be necessary due to a change in health, work responsibilities, or other, and whether a simple or super majority would be needed for such action. It was noted that, while SA membership is required for Maintainers, they are not officers of the WG. There was agreement in using the same process used for subgroups, for open source incorporated in standards. Peter will bring OSCom's comments to the AudCom ad hoc. 
  
4.  Review of Project Boards  
a.  [Approval Requests and Approval Process](https://opensource.ieee.org/oscom/approvals/-/issues) - Josh reported on two new projects (PQDIF and UVVM). Staff is looking into the  most optimal sequence of steps for project approvals and will report back at the next meeting.  
b.  [Maintainers Manual](https://opensource.ieee.org/oscom/maintain) - It was noted that sample governance documents are to be provided as part of the Maintainers Manual, and it would be helpful to have a list of topics to have in a governance document. The  [OSCom Operations Manual](https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/other/OSCOM_Operations_Manual.pdf) and the  [Maintainers Manual](https://opensource.ieee.org/community/manual) have statements about information that shall be provided when a project seeks authorization to become an Official IEEE Open Source Project by posting a request on the platform. Josh proposed that existing projects can help improve the sample governance documents and was asked to create an issue for OSCom to review.  
c.  [Project inquiry form](https://docs.google.com/document/d/1GEzryW5V04Jdv9vDRZnhkS7jYp_AniLvhtkEKNFJWYk/edit) - This item will be placed in the beginning of the agenda for OSCom to review at the next meeting.  
d.  [Peer review](https://opensource.ieee.org/community/peer-review/peer-review) - The following report was submitted after the meeting:
Alfredo contacted the societies where he knows someone at the society-level (status in parenthesis):  
 - Communications Society (no response yet)   
 - Computer Society (email response and phone call are positive)   
 - Consumer Electronics Society (no response yet)   
 - Education Society (no response yet)   
 - Industry Applications Society (no response yet)
 - Instrumentation and Measurement Society (no response yet)   
 - Nuclear and Plasma Sciences Society (no response yet)
 - Oceanic Engineering Society (no response yet)  
 - Power & Energy Society (email response is positive) 
 - Society on Social Implications of Technology (no response yet)   
 - Technology and Engineering Management Society (email response is positive)
 - Vehicular Technology Society (no response yet)   
 - Council on Electronic Design Automation (no response yet)   
 - Systems Council (no response yet)
The following societies  have not been contacted (need contact info at the society-level, but based on their websites they could be interested):  
 - Computational Intelligence Society   
 - Engineering in Medicine and Biology Society   
 - Product Safety Engineering Society   
 - Robotics and Automation Society
 - The  [tracking spreadsheet](https://docs.google.com/spreadsheets/d/1qWVfBJpXmz-Lk0sxTnT9lIMRjCd0dIxrFEcSWlymjjc/edit?usp=sharing)  has been updated.  
The Peer Review ad hoc has agreed to have three web calls on May 19, June 2 and June 16.  They already had a first call to introduce one to another and we have started preparing our project repository to host our work:  [https://opensource.ieee.org/community/peer-review/](https://opensource.ieee.org/community/peer-review/)  
[FOLLOW-UP]  
 - Alfredo has not yet sent the minutes of the initial call. Will do before next scheduled call  
 - Martin contributed his ideas to the committee repository but they were lost during the move and subsequent changes to the project: Alfredo will investigate  
 - Alfredo will ask for Melissa's support in sending the request to participate in the ad  hoc with the help of marketing  
  
5. New Business  
 - There was a suggestion to begin a mailing list for interested parties. Silona will talk to Josh about feeds on Gitlab since most of the action will be the wiki or chat.  
 - It was agreed to cancel the meeting  on 15 May since it coincides with the BOG meeting. The next meeting is scheduled on 22 May.

## 2020 05 01 Minutes

[Attendee List](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200501-attendees)

1.  The agenda was approved.    
2.  OSCom members reviewed the comments received on the draft open source content in AudCom Baselines. Don reported that he had also submitted comments directly to Peter, who will send them to the ad hoc to consolidate, reword the draft, and send back to OSCom as needed.      
    
3.  Review of Project Boards (25 min)  
    a. [Approval Requests](https://opensource.ieee.org/oscom/approvals/-/issues): Approval of P1484.1 and P1484.2 requests for open source - Michael C. took on the role of chair for this item. Richard provided an update on the two PARs. The open source reference has been removed in order to proceed with conditional approval from NesCom. It was noted that the query form is one of the governance templates that have been in progress since December, and the form that was submitted is not aligned with the Maintainers Manual. For example, the form does not identify Project Lead or Maintainer. There was a question regarding when project deliverables need to be provided to OSCom, and whether it would be sufficient to have a declaration from the WG that they will provide the necessary information later. It was agreed to continue the discussion offline. After the PARs are approved by NesCom and the projects have been set up, the WG will again seek OSCom approval.  
    b. [Maintainers Manual](https://opensource.ieee.org/oscom/maintain) - No action. <br>
    c. [Project inquiry form](https://opensource.ieee.org/community/support/forms/issues/new?issue%5Bdescription%5D=%23%23+Authorization+to+create+a+new+Official+IEEE+Open+Source+Project+%28DRAFT+USE+ONLY+FOR+TESTING%29+%0D%0A%0D%0A%23%23%23+Project+Information%0D%0A1.+%2A%2AProject+Name%3A%2A%2A+%0D%0A2.+%2A%2AProject+Description%3A%2A%2A%0D%0A3.+%2A%2ABackground%3A%2A%2A%0D%0A%0D%0A%23%23%23+Leadership+and+Affiliation+%0D%0A4.+%2A%2AProject+leadership%3A%2A%2A+%0D%0A5.+%2A%2AOrganization%3A%2A%2A%0D%0A6.+%2A%2AIEEE+Standard+Development+Working+Group%3A%2A%2A%0D%0A%0D%0A%23%23%23+Additional+info%0D%0A7.+%2A%2AGovernance+model%3A%2A%2A+%0D%0A8.+%2A%2ARelated+works%3A%2A%2A%0D%0A9.+%2A%2AFiscal+sponsorship%3A%2A%2A%0D%0A%0D%0A%0D%0A%3C%21--+Instructions+and+notes%0D%0A%0D%0ASubmitting+this+form+is+the+first+step+in+becoming+an+Official+IEEE+Open+%0D%0ASource+Project.+Submission+of+this+form+may+initiate+a+conversation+with+%0D%0AIEEE+staff+or+the+proposed+project+may+move+directly+to+the+next+step%2C+%0D%0Awhich+is+submission+to+the+Open+Source+Committee+%28OSCom%29+for+approval.%0D%0A+++%0D%0AIEEE+staff+shall+review+requests+and+will+try+to+provide+feedback+within+ten+%0D%0Aworking+days.+Requests+for+initiating+Official+IEEE+Open+Source+Projects+are+%0D%0Athen+forwarded+to+OSCom+for+review+and+approval%2C+which+takes+a+minimum+of+%0D%0Afourteen+calendar+days.+%0D%0A%0D%0ATips%3A%0D%0A%2A+Answer+what+you+can%3A+it+is+OK+if+you+are+unable+to+answer+all+questions+%0D%0A%2A+Other+than+listing+the+names+of+project+leadership+and+their+usernames%2C+%0D%0A++personally+identifiable+information+is+not+required+or+recommended.%0D%0A%2A+HTML+comments+are+not+included+in+the+submitted+document.+%0D%0A%2A+Instructions+and+notes+can+be+found+at+the+bottom+of+this+form+for+select+%0D%0A++questions%0D%0A%0D%0A%0D%0AQ2%3A++If+this+is+an+established+project%2C+please+provide+any+important+background+%0D%0A+++++information%2C+including+project+age%2C+contributor%2Fdeveloper+community%2C+user+%0D%0A+++++base%2C+etc.+Links+to+existing+websites+and+official+hosting+%28e.g.%2C+github+%0D%0A+++++page%29+are+appreciated.+%0D%0A%0D%0AQ4%3A++Instructions%3A+Provide+the+names+of+the+project+leadership.+if+possible%2C+%0D%0A+++++list+their+%28e.g.%2C+%22%40username%22%29.+If+you+have+determined+roles+such+as+leads%0D%0A+++++maintainer%2C+etc.+for+the+project%2C+please+indicate+the+roles+as+well.+%0D%0A+++++All+Official+IEEE+Open+Source+projects+require+that+one+or+more+persons+%0D%0A+++++must+have+the+role+of+Project+Lead+and+Project+Maintainer+%0D%0A%0D%0AQ5.++If+this+application+is+being+proposed+or+lead+by+an+organization%2C+please+%0D%0A+++++indicate+the+organization%28s%29+here.+%0D%0A%0D%0AQ6.++If+this+is+a+project+of+an+existing+standards+development+working+group%2C+%0D%0A+++++please+specify+the+name+of+the+working+and+any+related+standards.+%0D%0A%0D%0AQ7.++Please+provide+any+info+you+can+at+this+time+about+how+you+intend+for+the+%0D%0A+++++governance+of+this+project+to+be+conducted%2C+or+put+%22IEEE+Recommendation%22+if%0D%0A+++++you+wish+for+IEEE+to+recommend+a+default+governance+model+for+your+project.+%0D%0A%0D%0AQ8.++Please+describe+if+and+how+your+project+relates+to+other+known+%0D%0A+++++Open+Source%2C+open+hardware%2C+specifications%2C+or+technical+standards+projects%0D%0A+++++or+similar+efforts.+%0D%0A%0D%0AQ9.++Please+indicate+if+you+are+interested+in+seeking+fiscal+sponsorship+through%0D%0A+++++the+IEEE+at+this+time.+%0D%0A%0D%0A--%3E+%0D%0A%0D%0A%0D%0A) - No action. <br>
    d. Peer review - Alfredo provided the following report after the meeting:
      - Held initial call with initial members of ad hoc committee: Alfredo Herrera (chair), Tobias Wenzel, Martin Häuer, Stefano Zacchiroli. (RSVP Emilio Velis)
      - We reviewed the charter provided by IEEE-SA OSCom and  discussed with regards to our roles
      - The ad hoc committee focused particularly on scope of peer review: beyond documentation but also including claims, and data to back claims it up
      - Peer review will require adequate levels of expertise from reviewers: How is process going to address creation of reviewer pool without requiring in-depth knowledge?
      - It is not clear at this moment if peer review will be called upon throughout development (incubation acceleration or mentoring role?) or at end of process (validate readiness to release?)
      - Initial schedule, milestones and tasks will be posted on  [https://opensource.ieee.org/community/peer-review/admin](https://opensource.ieee.org/community/peer-review/admin)
      - Repository setup required quite some work: the admin project was finally created to host internal work of ad hoc committee and a public Wiki. Public projects will be created under the group at  [https://opensource.ieee.org/community/peer-review/](https://opensource.ieee.org/community/peer-review/)
      - A first email and call was held with the Computer Society. They are the first Society to accept helping us find a participant from their membership for ad hoc committee.
      - Emails to Consumer Electronics Society and Education Society need follow up. Other emails societies to come in next few days
    
4.  Reports <br>
 a. Executive Director <br> 
    - [Mission, Vision, Purpose, and Core Values](https://docs.google.com/document/d/1ZVImrJzPnJbuAUKE4OwOxwjYO8K6RYtz-RzPG-ZH4ho/edit?usp=sharing); [Labels](https://docs.google.com/document/d/1UPvp-Leh5q8CPdIyiuz3Xd1Vdg-v-ci6cD9QhzQeHZI/edit?usp=sharing) - Silona requested feedback. She plans to send the Mission, Vision and Core Values document to the Marketing Team by May 8. <br>
 b. IPR Manager - Yvette reported there there were no additional CLAs received since the last meeting. Additional comments regarding the OSCom declaration have been sent to the legal team.  <br>
        
5.  OSCom agreed to move up the start time of future meetings by an hour. OSCom meetings will henceforth take place on Fridays at 9:00 a.m. ET


## 2020 04 24 Minutes 

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200424-attendees) <br>

- There were no objections to approve the agenda.
-  OSCom members reviewed the draft open source content in the AudCom Baselines. It was agreed to recommend removing Clause 5.6 (b). Additionally, there were questions about the Open Source Maintenance Subgroup. Noting that the SASB expects the baselines to be done by June, it was agreed to continue the dialogue via email and dedicate 15 minutes at the next meeting towards review of the document. A separate meeting will be scheduled if the review isn't completed by then. Peter will summarize the comments and forward them to AudCom. Robby will send a request to the AudCom chair to see if the document can be publicly posted.  
    
-   Silona provided an update on the [labels taxonomy for IEEE SA Open](https://docs.google.com/document/d/1UPvp-Leh5q8CPdIyiuz3Xd1Vdg-v-ci6cD9QhzQeHZI/edit#heading=h.wdrgxv8g88tw). There was discussion on the use of pdf, doc, or Markdown for governance documents on the Gitlab platform.  Versioning is not provided for the former two. 
- Yvette referred to the OSCom declaration which is intended to address confidentiality and executive sessions for OSCom members, without the heavy-handedness of an NDA. Yve and Chuck will follow up regarding the question of timeouts/expiration dates.  
- Josh reported on the most recent usage statistics for IEEE SA Open.  There has been an uptick in users and repos created.  Currently, in lieu of sending the inquiry form, a meeting is set up with interested parties to learn more details about a potential open source project. Josh expects to share proposed templates for the Maintainers Manual shortly.
- Robby mentioned that there has been a request from folks from the US west coast to schedule the OSCom calls at a later time. He will send a query to OSCom member about options. He hopes that in the future, the platform will be used as a mechanism for discussion and communication. 
    

## 2020 04 17 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200417-attendees)

1. Approval of agenda - Item 3b Peer Review was moved up in the order of business. <br>
 
2. Reports <br> 
  a. Executive Director - Silona shared the proposed taxonomy for Gitlab labeling. Robby encouraged everyone to provide input directly onto the [document](https://docs.google.com/document/d/1UPvp-Leh5q8CPdIyiuz3Xd1Vdg-v-ci6cD9QhzQeHZI/edit#). A demo of labeling projects with the new taxonomy may be helpful for the next meeting. <br> b. IPR Manager - Yve mentioned that she had received one individual CLA on P1752. She will work with Legal on the proposed language for an NDA declaration for OSCom members.  <br> c. Community Manager -  Josh reported on the platform usage statistics. It was noted that most of the users are coming in via word-of-mouth. Silona will double-check with the marketing team if there is a way to obtain geographic data or entry point for the users. <br>

3. Review of Project Boards   
  a. [Maintainers Manual](https://opensource.ieee.org/oscom/maintain)  - There was discussion on the types of  governance expected for Official IEEE Open Source projects. Josh pointed to the [open items](https://opensource.ieee.org/oscom/maintain/-/issues) in the issues list. He was encouraged to reach out to the volunteers in case they are interested in drafting some of the model governance examples. Michael C. was asked to open an issue under [Roadmaps](https://opensource.ieee.org/community/support/roadmap) regarding the user account alerts. <br> 
  b. [Peer Review](https://opensource.ieee.org/oscom/peer-review)  - Alfredo sent a list of Societies and contacts to OSCom. Members of OSCom who have any other contacts were asked to email Alfredo. <br> 
  c. Approval Requests – Melissa reported on the projects that are in the pipeline. There was discussion about the status of the [project inquiry form]( https://opensource.ieee.org/community/support/forms/issues/new?issue%5Bdescription%5D=%23%23+Authorization+to+create+a+new+Official+IEEE+Open+Source+Project+%28DRAFT+USE+ONLY+FOR+TESTING%29+%0D%0A%0D%0A%23%23%23+Project+Information%0D%0A1.+%2A%2AProject+Name%3A%2A%2A+%0D%0A2.+%2A%2AProject+Description%3A%2A%2A%0D%0A3.+%2A%2ABackground%3A%2A%2A%0D%0A%0D%0A%23%23%23+Leadership+and+Affiliation+%0D%0A4.+%2A%2AProject+leadership%3A%2A%2A+%0D%0A5.+%2A%2AOrganization%3A%2A%2A%0D%0A6.+%2A%2AIEEE+Standard+Development+Working+Group%3A%2A%2A%0D%0A%0D%0A%23%23%23+Additional+info%0D%0A7.+%2A%2AGovernance+model%3A%2A%2A+%0D%0A8.+%2A%2ARelated+works%3A%2A%2A%0D%0A9.+%2A%2AFiscal+sponsorship%3A%2A%2A%0D%0A%0D%0A%0D%0A%3C%21--+Instructions+and+notes%0D%0A%0D%0ASubmitting+this+form+is+the+first+step+in+becoming+an+Official+IEEE+Open+%0D%0ASource+Project.+Submission+of+this+form+may+initiate+a+conversation+with+%0D%0AIEEE+staff+or+the+proposed+project+may+move+directly+to+the+next+step%2C+%0D%0Awhich+is+submission+to+the+Open+Source+Committee+%28OSCom%29+for+approval.%0D%0A+++%0D%0AIEEE+staff+shall+review+requests+and+will+try+to+provide+feedback+within+ten+%0D%0Aworking+days.+Requests+for+initiating+Official+IEEE+Open+Source+Projects+are+%0D%0Athen+forwarded+to+OSCom+for+review+and+approval%2C+which+takes+a+minimum+of+%0D%0Afourteen+calendar+days.+%0D%0A%0D%0ATips%3A%0D%0A%2A+Answer+what+you+can%3A+it+is+OK+if+you+are+unable+to+answer+all+questions+%0D%0A%2A+Other+than+listing+the+names+of+project+leadership+and+their+usernames%2C+%0D%0A++personally+identifiable+information+is+not+required+or+recommended.%0D%0A%2A+HTML+comments+are+not+included+in+the+submitted+document.+%0D%0A%2A+Instructions+and+notes+can+be+found+at+the+bottom+of+this+form+for+select+%0D%0A++questions%0D%0A%0D%0A%0D%0AQ2%3A++If+this+is+an+established+project%2C+please+provide+any+important+background+%0D%0A+++++information%2C+including+project+age%2C+contributor%2Fdeveloper+community%2C+user+%0D%0A+++++base%2C+etc.+Links+to+existing+websites+and+official+hosting+%28e.g.%2C+github+%0D%0A+++++page%29+are+appreciated.+%0D%0A%0D%0AQ4%3A++Instructions%3A+Provide+the+names+of+the+project+leadership.+if+possible%2C+%0D%0A+++++list+their+%28e.g.%2C+%22%40username%22%29.+If+you+have+determined+roles+such+as+leads%0D%0A+++++maintainer%2C+etc.+for+the+project%2C+please+indicate+the+roles+as+well.+%0D%0A+++++All+Official+IEEE+Open+Source+projects+require+that+one+or+more+persons+%0D%0A+++++must+have+the+role+of+Project+Lead+and+Project+Maintainer+%0D%0A%0D%0AQ5.++If+this+application+is+being+proposed+or+lead+by+an+organization%2C+please+%0D%0A+++++indicate+the+organization%28s%29+here.+%0D%0A%0D%0AQ6.++If+this+is+a+project+of+an+existing+standards+development+working+group%2C+%0D%0A+++++please+specify+the+name+of+the+working+and+any+related+standards.+%0D%0A%0D%0AQ7.++Please+provide+any+info+you+can+at+this+time+about+how+you+intend+for+the+%0D%0A+++++governance+of+this+project+to+be+conducted%2C+or+put+%22IEEE+Recommendation%22+if%0D%0A+++++you+wish+for+IEEE+to+recommend+a+default+governance+model+for+your+project.+%0D%0A%0D%0AQ8.++Please+describe+if+and+how+your+project+relates+to+other+known+%0D%0A+++++Open+Source%2C+open+hardware%2C+specifications%2C+or+technical+standards+projects%0D%0A+++++or+similar+efforts.+%0D%0A%0D%0AQ9.++Please+indicate+if+you+are+interested+in+seeking+fiscal+sponsorship+through%0D%0A+++++the+IEEE+at+this+time.+%0D%0A%0D%0A--%3E+%0D%0A%0D%0A%0D%0A). It was agreed to dedicate some time to the discussion of the form at the next meeting. <br>
 
4. New Business - None reported. 



## 2020 04 10 Minutes

[Attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List#20200410-attendees)

1. Approval of agenda  
  It was noted that the [agenda](https://opensource.ieee.org/oscom/oscom/-/wikis/Agenda) is now being hosted on the [OSCom wiki](https://opensource.ieee.org/oscom/oscom/-/wikis/home). Attendees were asked to record their names and affiliations on the webex chat. A [wiki page for attendees](https://opensource.ieee.org/oscom/oscom/-/wikis/Attendance-List) to record their names and affiliations has been added for future meetings.<br>

2. Reports <br>
   a. Executive Director - Silona reported that she is working on diagramming the various IEEE SA Open processes. She also reported that her team is working on bug issues on opensource.ieee.org. (Josh later reported that these issues have been solved and a root cause analysis was done (IT security firewall issues). <br>  
   b. IPR Manager - Yvette reported that there have been no new CLAs since her last report. Silona is working on automating the CLA submission process. Responsibility for CLAs falls with the Project Leads/Maintainers. SA Staff audits the process prior to MEC or public release.  <br>

3. Review of Project Boards - Views of the various OSCom pages that have been created on the platform were presented. <br>
   a. [Maintainers Manual](https://opensource.ieee.org/oscom/maintain/-/issues) - Members were encouraged to create an issue and draft the templates, e.g., examples, forms, etc.  <br>
   b. [Peer Review](https://opensource.ieee.org/oscom/peer-review) - Alfredo reported that he is working on items that Annette had brought up in their previous correspondence. He expects to provide an update on Monday and will request feedback from OSCom. <br>
   c. Approval Requests - The list of open projects can be found [here](https://opensource.ieee.org/oscom/approvals/-/issues). Robby expects some approval requests for the next meeting. <br>

4. New Business - There was discussion on the use of Executive Sessions and NDAs, should the need arise, and given the need for transparency expected in the open source community. Yve will take this back to the IEEE legal team to get more guidance. <br>