${taskforce.name} Avatar
  1. OMG Task Force

AB Process Subcommittee — Closed Issues

  • Key: ABPSC
  • Issues Count: 2
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
ABPSC-34 P&P has no section 3.3, numbering jumps from 3.2 to 3.4 ABPSC 3.3 ABPSC 3.4 Closed; No Change closed
ABPSC-6 OMG should have a Code of Conduct ABPSC 3.3 ABPSC 3.4 Closed; No Change closed

Issues Descriptions

P&P has no section 3.3, numbering jumps from 3.2 to 3.4

  • Key: ABPSC-34
  • Status: closed  
  • Source: Object Management Group ( Jason Smith)
  • Summary:

    pp/20-06-01 jumps from 3.2 to 3.4, fix is to poke Word to use contiguous numbering, and adjust necessary references elsewhere in document.

  • Reported: ABPSC 3.3 — Fri, 29 Jan 2021 21:40 GMT
  • Disposition: Closed; No Change — ABPSC 3.4
  • Disposition Summary:

    Obsoleted by ABPSC-30

  • Updated: Wed, 21 Sep 2022 22:14 GMT

OMG should have a Code of Conduct

  • Key: ABPSC-6
  • Status: closed  
  • Source: 88solutions ( Pete Rivett)
  • Summary:

    Which covers expected behavior and courtesy at physical meetings, phone meetings and online. Along with process and sanctions for not following it.

    Many other conferences and communities have been caught out by lack of such, and there have been several publicized incidents which has led to people withdrawing from participation since they did not feel safe or comfortable, or to support such people. Here's the latest example https://twitter.com/MatthewGerstman/status/1110363827655376897

    In terms of precedent, here is a generic conference one https://confcodeofconduct.com/ and what the W3C has: https://www.w3.org/Consortium/cepc/

    And here is what I wrote to a current OMG working group:
    >>>
    In the meantime let’s please be polite to each other, whether in meetings or via email. And bear in mind that:
    • 1) We’re all doing this as volunteers in parallel with our “day job”;
    • 2) Hence we may have different levels of availability for this, and that may vary over time; both for calls and to read materials or work on assignments;
    • 3) Let’s show appreciation for any contributions people do make even, if they do need more work
    • 4) We each bring a different background, perspective and expertise. What may be obvious to us may need explanation to others, or them pointed to background reading (but see 2) above)
    • 5) Similarly, what may be interesting to some may not be to others.
    • 6) interpersonal issues are best dealt with one-to-one (ideally by speaking directly) rather than email to the whole list since emails can easily be misunderstood (as I’ve personally found from experience)
    • 7) we’re still new as a team so can expect to go through a “storming” stage as we get used to each other and develop a way of working and communicating. See https://en.wikipedia.org/wiki/Tuckman%27s_stages_of_group_development
    <<<

  • Reported: ABPSC 3.3 — Thu, 28 Mar 2019 10:12 GMT
  • Disposition: Closed; No Change — ABPSC 3.4
  • Disposition Summary:

    resolved completely outside the ABPSC

  • Updated: Thu, 25 Jun 2020 15:23 GMT