Open Project PGB members and OASIS members,

At its meeting on June 14, 2022, the OASIS Board of Directors approved updates to the OASIS Open Project Process as well as minor changes to the Committee Operations Process and the Open Repository Guidelines and Procedures. Staff recommended these changes to address issues raised by several projects as well as our own lessons learned. The proposals go into effect immediately.

The specific changes can be seen in the attached red-line copies of these documents. We do not anticipate these to have a significant impact on your ongoing project work.

Briefly:

1. The first (and most important) change can be found in the OP Rules at lines 121 to 137 as a proposed new section 5.7. This change would allow OP PGBs to elect to apply the same quorum, non-voting, and persistent non-voting rules that TCs enjoy to their OP operations. Several PGBs have struggled to achieve regular quorum and make progress. By adopting a Standing Rule, OPs will now be able to gracefully scale down voting and quorum to those who show up and vote regularly. As with TCs, this would not change any other commitments or privileges of Sponsorship.

2. The second change is about Technical Steering Committees (TSC), and can be found in the attached marked OP Rules at lines 70 to 78 and 142 to 152. These changes simply clarify that a project can have multiple TSCs and how TSCs are represented on the PGB.

3. At lines to 242 to 245 (Section 10), we attempt to emphasize that, generally speaking, we don't expect Open Projects to adhere to a lot of rigid formalities; they're entitled to run as a consensus process, without a lot of formal motions, seconding and Roberts Rules behaviors. Related changes on the same topic also are in the OASIS Committee Operations Process at lines 74 to 76 and 162 to 166.

4. In the Open Repository rules, which allow TCs to launch open source projects on the side, we changed the language from a list of applicable open source licenses that would require maintaining to a statement that it is the same as for the Open Project Rules. Lines 53 to 58.

5. Two other minor patches to the OASIS Committee Operations Process were approved, in addition to the "consensus" issue noted above. The first is at lines 136 to 145, where the role and requirements for "standing rules" is slightly clarified. The second is to the informative table of project roles and functions after line 56. These were made to better explain what each role in an Open Project may do.

6. Finally, as general clean-up, small, non-substantive editorial corrections were made at lines 21, 80, 84, 87, and 205 of the OP Rules, and lines 82, 83 and 99 of the OASIS Committee Operations Process.

Again, we do not expect these to have major impacts on your work but, as always, feel free to contact us with any questions.

Best regards,

/chet


Additional information

- Open Project Rules - https://www.oasis-open.org/policies-guidelines/open-projects-process/

- Committee Operations Process - https://www.oasis-open.org/policies-guidelines/oasis-committee-operations-process/

- Open Repository Guidelines and Procedures - https://www.oasis-open.org/policies-guidelines/open-repositories/
--

Hi PGB amd TSC people,

Team leaders,

From time to time, we get reports of outsiders crashing team calls. There has been a recent spate of such disruptions again. The effect of these interruptions can be anywhere from merely annoying to very upsetting. Either way, you may want to take steps to protect your meetings from unwanted intruders. Feel free to share this with others in your committee. 

- First, please note that anything in your calendar entry is publicly visible. It takes a bit of digging, but it is accessible. So you don't want to put info that will allow access to the event there, particularly passcodes. Instead, consider putting the information on accessing the meeting in a file that only team members can access or sending the details in a private message to participants before the meeting starts. For TC members using Kavi, information can be entered in an action item. Only logged in TC members have access to those.

- Always use a password if the tool allows it. Zoom allows you to set up a passcode in the security section. Teams does not but apparently you can configure access rules to hold unknown parties in a lobby until you can verify their identity. 

- If the tool allows for a waiting room or lobby area, consider using it. The 'Join before host' will not work and you, as host, will have to start the meeting before others can come in and start discussion. However, a waiting room will let you keep people you don't recognize out of your call.

- In Zoom, if the waiting room is enabled, you can click the More button to the right of a guest's name in the meeting Participants display, then select 'Put in waiting room' to send them back outside of your meeting.

- If you can collect identifying information on the intruder, we can report them to Zoom. While it may not have an immediate effect, users who abuse access to Zoom can be banned from the platform.

- According to Zoom, while in a meeting, you can report a participant for inappropriate behavior. Reported participants are removed from the meeting.

To do this:

* As the meeting host or a participant, click the meeting information icon  in the top-left corner of the window.
* In the bottom-left corner of the meeting information dialog, click the red Report link.
* Fill out the dialog box; enter the participant(s) you would like to report and the reason for reporting the person.
* If you are not currently signed in to your Zoom account, enter your email address.
* (Optional) Select the Include desktop screenshot check box to include a current screenshot of your desktop.
* Click Submit.
You will receive a notification that your report was sent successfully.

More information on responding to inappropriate behavior can be found at https://support.zoom.us/hc/en-us/articles/360042791091

No one likes having to take these sorts of precautions. But it is a fact of our modern life that we have to. We hope these suggestions help you avoid hassles. If you have any tips of your own, please send them along so that we can share them. 

PGB/TSC members,

OASIS staff is looking into infrastructure changes to address problems that groups have reported. Please share this with others in the group as you see fit. 

We would like to know if any of you are restricted, whether by organizational policy or other reason, from using the G-Suite applications - gmail, google calendar, google drive, etc. If so, please let us know including any insight you might have into why the restrictions or limitations exist.

Also, if you are so restricted, are there other tools you can use in their place?

Thank you for your feedback. We are looking at several alternatives. We want to find a solution that works for as close to everyone as possible. 

Members of the PGB,

As you know, the Baseline TSC approved submitting the Baseline Version 1.0 specifications to you for consideration as an official Release, the first step forward on the OASIS standards track workflow. I've confirmed with Andreas that the following links are the permalinks to the editions of the draft specifications approved by the TSC:  

- Baseline Core Version 1.0 - https://github.com/eea-oasis/baseline-standard/blob/e4620597c739a9fa7cdabdcc26fb17b76b24beee/core/baseline-core-v1.0-psd01.md

- Baseline API and Data Model Version 1.0 - https://github.com/eea-oasis/baseline-standard/blob/e4620597c739a9fa7cdabdcc26fb17b76b24beee/api/baseline-api-v1.0-psd01.md

- Baseline CCSM Specification Version 1.0 - https://github.com/eea-oasis/baseline-standard/blob/e4620597c739a9fa7cdabdcc26fb17b76b24beee/ccsm/baseline-ccsm-v1.0-psd01.md

The files are now turned over to you for your consideration and action. Please let us know if we can help you in any way. 

/chet
--

Members of the Baseline TSC,

I apologize for not getting this out to you earlier.

One of the first items to address at tomorrow's meeting is to elect a chair or two co-chairs. Chairs are responsible for scheduling meetings, setting agendas, managing the discussion, making sure minutes are taken and published to the mailing list, etc.

Claudia and I will manage the election.

If you are interested in serving as a chair, please feel free to reply to this message and let everyone know. We will also ask for nominations from the floor before holding the vote. If there are only one or two candidates, we'll ask for objections to unanimous approval. If there are three or more, we will hold a roll call vote. 

The 2021 Baseline Technical Steering Committee (TSC) election announced October 13 2021 in https://lists.oasis-open-projects.org/g/baseline-tsc/message/102 has closed.

There were 19 candidates for the 11 TSC seats. 25 of the 40 eligible voters cast ballots. OASIS Project Administration staff collected, tallied, and reported the results.

We are pleased to announce the following members elected to the 2021/2022 Baseline TSC:

- John Wolpert
- Kyle Thomas
- Stephan Schmidt
- Andreas Freund
- Kartheek Solipuram
- Ryan Fisch
- Samrat Kishor
- Mehran Shakeri
- Cale Teeter
- Jack Wiering
- Luiz Soares

Our congratulations to the new TSC members and our thanks to all who participated in the process. 
--