Skip to content

Standardization process transparency #7

Closed
@DanielMazurkiewicz

Description

@DanielMazurkiewicz

As I find it a separate topic - this is a continuation to this post: webmachinelearning/webnn#3 (comment)

In response to:

PS. And again, if someone doesn't want training functionality at all or in v1, please provide good reasons. Simple "No" isn't an argument into discussion.

@anssiko wrote:

The group makes decisions based on consensus and participants do not need to provide reasons why they are not willing to expand the agreed upon scope.

I mentioned that to clarify the process and mechanics for making charter changes (voting) differs from day-to-day decision-making (consensus-based). These aspects are explained in the charter document. You can reach out to me privately and I’m happy to answer any further procedural questions you may have to keep this issue focused on technical discussion.

Thank you for clarification, just hope you were driven with need of helping me (which I really appreciate then), but such a response comments are sensitive thing and otherwise I would find it highly inappropriate.


And as we are here already, I would like to rise this topic as well. While I understand a right to not to provide a reasons of decisions for things that would touch things like for example religion, ethnicity or sexual preferences, I completely disagree for the sake of transparency of this process for not providing reasons for (both including and not including) functionalities that are clearly strictly technical and not touching these sensitive areas.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions