Code Monkey home page Code Monkey logo

policies-consultation's Introduction

THE INITIAL POLICY DEVELOPMENT PROCESS IS COMPLETE - THANK YOU FOR YOUR FEEDBACK

This fork is to help develop an IAB Conflict of Interest policy based on the LLC equivalent I forked the entire repo to provide continuity. I've also made some initial edits doing the basic s/LLC/IAB/ changes.

policies-consultation

Materials for a consultation with the IETF community on IETF LLC policies.

The draft polices are in this project. You can comment on the policies here or via the LLC-Consultation mailing list (subscribe at https://www.ietf.org/mailman/listinfo/llc-consultation). If you wish to use GitHub, you can open Issues or create Pull Requests. Opening an issue is like opening a discussion item, and so you can raise a point and begin a discussion. Creating a pull request is proposing an editorial change to a part of a given document. Both will work for our process, but initially it may be best to open an issue for discussion.

Timing of the community consultation process:

Wednesday, June 19, 2019 at 15:00 UTC

Four Week Review Period - June 19 - July 16, 2019

Starting July 17, 2019

  • Board review & discussion of community input
  • Revision of policies
  • Repeat community input & revision steps if needed
  • Formal adoption of policies

Within One Week of Approval

  • Approved policies posted on the IETF website, with links in the standard page footer
  • Email sent to IETF announce list advising that approved policies are posted, with a link to them
  • GitHub project closed

Finally, as noted earlier, the community consultation process we’re following is new. At the conclusion of this first consultation, we welcome your feedback on how we might improve it in the future.

Thank you in advance for your review and feedback.

policies-consultation's People

Contributors

coopdanger avatar jlivingood avatar richsalz avatar seanturner avatar sftcd avatar

Watchers

 avatar  avatar  avatar

Forkers

hardaker

policies-consultation's Issues

are likely violations covered?

Christian raised a point in discussion at IETF106:

"I'd like us to do some brainstorming to see what a violation of the policy would be. And check whether those are logically covered in the text."

I think that's worth recording as an open issue as discussion of it might help us frame any preamble text or guidance for IAB members as to what to include on their forms.

Act in the best interests of the IAB?

This seems wrong; I think it reinforces the idea that the IAB is insular and self-serving.

How about "in the best interests of the Internet community"?

do "family" need to be included for IAB?

Just noting that we had some discussion of whether or not "family" are relevant for the IAB CoI policy. I think that's definitely less of a deal for IAB than LLC board, but might be worth keeping in. OTOH, I think some people seemed uncomfortable with it, so this issue should provide a hook for that discussion. For now, I've left in the text about "family."

how many other orgs to list?

The section of the form on other orgs says:

"The names of organizations for which I or a family member serves as a board member, officer, or director, or organizations for which I or a family member is the sole owner, co-owner, controlling shareholder, or significant shareholder (under the US Securities and Exchange Commission’s definition), other than for the IAB for which there is an actual or potential perceived conflict of interest:"

I wonder if we should just drop that last bit and reduce it to:

"The names of organizations for which I or a family member serves as a board member, officer, or director, or organizations for which I or a family member is the sole owner, co-owner, controlling shareholder, or significant shareholder (under the US Securities and Exchange Commission’s definition)":

Seems ok to me to list all board memberships, but maybe that'd be more onerous for some of you than me? And "potential perceived CoI" seems like it could mean "all" in any case:-)

Not covered individuals

I would suggest limiting "Who is not a covered individual?" to ones where there is actual chance of confusion (e.g., liaisons, program members, Executive Administrative Manager, IRTF Chair, etc.). I think including all the other groups makes things more confusing than clarifying.

Maybe delete "Prohibited Conflicts" section entirely?

Having removed one of the prohibited conflict bits (in response to Mark's issue#3) and looking at it again, maybe we should just delete that section entirely as it mainly relates to the LLC board and money, which we don't much deal with.

Is this the right approach even?

Current COI process -- which we have been following even if it is undocumented is about observing a conflict prior to a discussion or a vote, and recusing from that as appropriate. Sometimes by the person, sometimes by someone else making the observation "maybe you nn need to recuse because xyz".

The proposed policy is one of a declaration-based, rather than topic based. It seems frankly difficult to apply, because most of the issues we face come up in the context of selecting people, not handing out contracts, and the people issues are quite dynamic. I don't know who is going to sign up for a liaison or appear in an IESG slate. I don't even necessarily know who my line manager, project leader, or close team member will be next month, as this keeps changing in most modern organizations.

The suggested approach is also declaration-based in the sense that only you can make the declaration and others cannot make suggestions. It is also declaration based in the sense that there seems to be an IAB decision related to a declaration rather than a topic. And that decision is an IAB decision rather than the person's own declaration. Is this necessary? Could we have rather a more per-topic/event based COI policy where everyone has to declare their conflicts at the start of a discussion of a new topic and that the documentation is in the minutes. And there should be a possibility for someone to raise an issue with the stated declarations for a topic, or lack thereof, and then IAB could make a decision that yes nn needs to recuse for this discussion.

"code of conduct"?

I deleted the phrase about "code of conduct" as we don't have one (that I know of:-).
I guess we could replace that with a reference to BCP39 but that also doesn't seem quite right, and in any case the text seems ok without the deleted phrase.

"Other activity" disclosure

The form asks to disclose:

Other activities I participate in that may be in a similar area of activity as the IAB, or other potential conflicts of interests with my IAB responsibilities:

So, would my chairing of the HTTP and QUIC WGs count as potential conflicts, since they might not see everything the same as the IAB?

Don't use member count numbers

I would strongly advise against using things like "(currently 12)" in the text. Using a number doesn't really help anything and only makes updates a pain.

Board review

Pending the Board’s review and resolution of a potential conflict of interest, disclosing Covered Individuals will conduct themselves so as to minimize the possible impact of the potential conflict of interest on the IAB.

Is this just a missed incidence of LLC board, or are we assuming that the LLC will review IAB conflicts, or...?

"Shall not act..."

Covered Individuals shall not engage in any outside business, professional conduct, or other activities that are directly adverse to the interests of the IAB.

That seems ... problematic, depending on who is judging "directly adverse", and whether someone's employers' actions are considered in-scope.

Covered Individuals

Does this include non-voting members (i.e., liaisons and ex-officio officers)?

Best interests of the Internet community

I think this language is far too subjective to be included: "In carrying out their IAB role, covered Individuals must act in the best interest of the Internet community."

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.