OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita] Subcommittee governance


That's more along the lines of what I was thinking. Let me see if I can come up with a better phrasing for you. If the TC believes it cannot advance a work itself and that another community will be able to do so, then I'd imagine we could work with you to find a way to make that happen. It wouldn't involve OASIS giving up ownership of the existing work though. That's what I was reacting to. 

Like I say, we want you to be successful, so we can find a way. 

On Wed, May 24, 2017 at 3:06 PM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

Chet, mainly what we have considered is establishing an Open OASIS repo -- if someone from the TC is willing to be the point person.

If the TC cannot maintain a work product, and no one from the TC is willing to be the point person for an Open OASIS repo, then I think we'd consider a way to let the community outside of OASIS (if interested) have the source code for an non-OASIS GitHub repo.

Obviously, our preference is to keep our subcommittees active and in good standing; two TC members recently stepped forward to co-chair the Learning & Training subcommittee.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 5/24/2017 2:53 PM, Chet Ensign wrote:
Hi Kris, hi Bob and all - 

I skimmed over these and I have a question about one of your points: 

"The TC should consider the following options for dealing with work products left by decommissioned subcommittees:

Removing the work product from OASIS control..." 

Can you explain a bit more about your thinking there? On first read, that sounds more harsh than I imagine you mean. 

Thanks, 

/chet



On Tue, May 23, 2017 at 8:08 AM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

This was approved (with a typo to be corrected) at the TC meeting on 25 October 2016.

Bob uploaded the source to SVN (dita\trunk\administration) last week, to make it easier for use to access and update. It's supposed to be a living document.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)



-------- Forwarded Message --------
Subject: Re: [dita] Subcommittee governance
Date: Tue, 11 Oct 2016 08:32:59 -0600
From: Bob Thomas <bob.thomas@tagsmiths.com>
To: Scott Hudson <scott.hudson@jeppesen.com>
CC: Kristen James Eberlein <kris@eberleinconsulting.com>, dita@lists.oasis-open.org <dita@lists.oasis-open.org>


Here is an update to the straw proposal based on feedback from the last TC meeting:

DITA Technical Committee subcommittee governance

This document specifies the policies and expectations for subcommittees operating under the auspices of the DITA Technical Committee (TC).

Rationale

This document establishes concrete policies and expectations for subcommittees. The TC is doing this to help subcommittees be more productive and to avoid the misunderstandings that can arise when expectations are informal.

Criteria for subcommittee creation

A prerequisite for subcommittee creation is evidence that sufficient interest exsists to support a subcommittee. Several criteria must be met before the TC will vote to approve the creation of a subcommittee. A prospective subcommittee must have the following:

    1. A charter that explains the subcommittee's mission
    2. A chairperson or secretary who is a voting member of the TC
    3. Subcommittee members from two or more companies
    4. A willingness to comply with all of the policies and expectations in this document

Criteria for remaining in good standing

The TC expects the following conditions to be met for a subcommittee to be in good standing with the TC:

    1. The chairperson shall maintain voting status on the TC.
    2. The subcommittee should have work in progress. Idle periods must not last more than six months.
    3. The subcommittee shall meet at least once a month when work is in progress
    4. Maintenance of the OASIS subcommittee web resource. This includes posting minutes for each subcommittee meeting before the next meeting occurs and the keeping upcoming meeting details current on the subcommittee calendar.
    5. The subcommittee shall report to the TC at least once a month when work is progress.

Policies affecting subcommittee chairpersons

The following policies affect subcommittee chairpersons. A subcommittee chairperson:

    1. Can be removed for any reason by a majority vote in the TC
    2. Is accountable to both the TC and the subcommittee
    3. Is responsible for keeping the subcommittee in good standing
    4. Must maintain voting status on the TC. A one month grace period is automatically in place for chairpersons who lose voting status. Beyond that, the TC is willing to consider extenuating circumstance. For example, a chairperson may live in a timezone that makes attending TC meetings impractical or a chairperson may have a persistent work-related conflict that coincides with TC meeting times. In such cases, the TC may agree to have the subcommittee represented by another subcommittee member who is also a voting member of the TC.

Deactivating and reactivated a subcommittee

A subcommittee can deactivate itself if no work is anticipated for six or more months. If a subcommittee believes that it will not be needed in the future, it should ask the TC to decommission the subcommittee. A deactivated subcommittee can reactivate itself providing it still meets all of the criteria for subcommittee creation.

Decommissioning a subcommittee

The TC should consider decommissioning a subcommittee under any of the following circumstances:

    • The subcommittee requests it
    • The subcommittee has been out of good standing for more than six months
    • A deactivated subcommittee has been abandoned by its members and by its chairperson

Disposition of work products from decommissioned subcommittees

The TC should consider the following options for dealing with work products left by decommissioned subcommittees:

    • Removing the work product from OASIS control
    • Appointing an advocate to service the work product
    • Asking the OASIS DITA community for volunteers who would be interested in re-instantiating the subcommittee by meeting the criteria for subcommittee creation
Best Regards,
Bob Thomas

On Fri, Sep 30, 2016 at 12:02 PM, Scott Hudson <scott.hudson@jeppesen.com> wrote:
FYI, subcommittees usually have their own OASIS page and calendar. It is not necessary to place their meetings on the DITA TC calendar. This allows interested parties to subscribe if they are interested rather than cluttering the TC calendar with non-essential appointments.

Thanks and best regards,

 

--Scott

 

Scott Hudson
Content Strategist

Training & Documentation
Global Services & Support

line

Jeppesen  |  Digital Aviation  |  Boeing

55 Inverness Drive East Englewood, CO 80112 | www.jeppesen.com

 

This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations.


From: <dita@lists.oasis-open.org> on behalf of Kristen James Eberlein <kris@eberleinconsulting.com>
Date: Friday, September 30, 2016 at 11:44 AM
To: "dita@lists.oasis-open.org" <dita@lists.oasis-open.org>
Subject: Re: [dita] Subcommittee governance

Hi, Bob.

Thanks for taking initiative on this. I think it's a solid start. Another thing that I'd like subcommittees to do is to ensure that their meetings are on the DITA TC calendar.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 9/30/2016 11:20 AM, Bob Thomas wrote:
Hi,

As I prepare to step in as a co-chair for the Technical Communications subcommittee, I have been thinking about Subcommittee/TC governance and how things ought to work. This seems appropriate since our last couple of TC meetings have dealt with such matters. I put together a DITA topic to focus my thoughts. It occurred to me that the topic would make a good a straw proposal for TC/SC governance, so I changed it to be that, and I offer it for your consideration. While some may find the specificity to be overkill, it is worth noting that the TC will inevitably have to decide how it will conduct itself in each of these matters. It is far easier to do this all at once and not on the fly when a misunderstanding has cropped up between the TC and an SC.

I have attached the DITA topic. Meanwhile, here it is as rendered in HTML:

DITA Technical Committee subcommittee governance

This document specifies the policies and expectations for subcommittees operating under the auspices of the DITA Technical Committee (TC).

Rationale

This document establishes concrete policies and expectations for subcommittees. The TC is doing this to help subcommittees be more productive and to avoid the misunderstandings that can arise when expectations are informal.

Criteria for subcommittee creation

Several criteria must be met before the TC will vote to approve the creation of a subcommittee. A prospective subcommittee must have the following:

  1. A charter that explains the subcommittee's mission
  2. A chairperson who is a voting member of the TC
  3. At least one other subcommittee member who is affiliated with a different company
  4. A willingness to comply with all of the policies and expectations in this document

Criteria for remaining in good standing

The TC expects the following conditions to be met for a subcommittee to be in good standing with the TC:

  1. The chairperson shall maintain voting status on the TC.
  2. The subcommittee should have work in progress. Idle periods must not last more than six months.
  3. The subcommittee shall meet at least once a month when work is in progress
  4. Minutes for each subcommittee meeting must be posted in the subcommittee’s OASIS document repository (Kavi) before the next meeting occurs.
  5. The subcommittee shall report to the TC at least once a month when work is progress.

Policies affecting subcommittee chairpersons

The following policies affect subcommittee chairpersons. A subcommittee chairperson:

  1. Can be removed for any reason by a majority vote in the TC
  2. Is accountable to both the TC and the subcommittee
  3. Is responsible for keeping the subcommittee in good standing
  4. Must maintain voting status on the TC. A one month grace period is automatically in place for chairpersons who lose voting status. Beyond that, the TC is willing to consider extenuating circumstance. For example, a chairperson may live in a timezone that makes attending TC meetings impractical or a chairperson may have a persistent work-related conflict that coincides with TC meeting times. In such cases, the TC may agree to have the subcommittee represented by another subcommittee member who is also a voting member of the TC.

Deactivating and reactivated a subcommittee

A subcommittee can deactivate itself if no work is anticipated for six or more months. If a subcommittee believes that it will not be needed in the future, it should ask the TC to decommission the subcommittee. A deactivated subcommittee can reactivate itself providing it still meets all of the criteria for subcommittee creation.

Decommissioning a subcommittee

The TC should consider decommissioning a subcommittee under any of the following circumstances:

  • The subcommittee requests it
  • The subcommittee has been out of good standing for more than six months
  • A deactivated subcommittee has been abandoned by its members and by its chairperson

Disposition of work products from decommissioned subcommittees

The TC should consider the following options for dealing with work products left by decommissioned subcommittees:

  • Ousting the work product from OASIS control
  • Appointing an advocate to service the work product
  • Asking the OASIS DITA community for volunteers who would be interested in re instantiating the subcommittee by meeting the criteria for subcommittee creation
Best Regards,
--
Bob Thomas
Skype: bob.thomas.colorado
Instant messaging: Gmail chat (bob.thomas@tagsmiths.com) or Skype
Time zone: Mountain (GMT-7)




---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
Bob Thomas
Skype: bob.thomas.colorado
Instant messaging: Gmail chat (bob.thomas@tagsmiths.com) or Skype
Time zone: Mountain (GMT-7)
--
/chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 



--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]