Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Whether to endorse working group outputs #89

Open
1 task
harisood opened this issue Apr 17, 2024 · 4 comments
Open
1 task

[Discussion] Whether to endorse working group outputs #89

harisood opened this issue Apr 17, 2024 · 4 comments

Comments

@harisood
Copy link
Member

Detail

This is an outstanding question from the drafting of the Consensus, Review and Objection document. This will be left as an open question and referenced from the latest process page on the website.

Actions

  • Hold conversation here and decide whether to close issue, or update the process

Who can help

No response

@harisood
Copy link
Member Author

Convo from the Google Doc, to continue here:

Simon Li: I'm coming around to the idea of not endorsing anything at the moment -just reject and approve.

Will Crocombe: Yes, keep is simple. And what's the difference between approve and endorse anyway? They're both a thumbs up.

David Sarmiento: I think there is value in not only thumbing up and sharing, and we can try to have that from the beginning.

To answer the comment on what it means I think it should mean the "formal opinion of the UK TRE Community"

Balint DARE UK: My sense is that we should approve or reject outputs only and leave out official 'endorsement' - I suspect the community will organically support/adopt/promote outputs that individually or collectively thinks are worthwhile or valuable and not otherwise, without the need for a top-down mechanism

Simon Li: It's still not clear to me what endorse means.... for example if we "endorse" a standard or workflow, do we have to consider de-endorsing it if it's later superceded by something better so is no longer best practice? Or does it remain "endorsed" because it was good at the time even though it's no longer relevant?

Simon Li: Discussed today: "Endorse" needs to be well defined. Can we omit this from v1, and leave the discussion of endorsement for a future update? Given the lifetime of WGs I don't think the need to endorse something is so urgent it needs to block the initial document.

@harisood
Copy link
Member Author

Simon Li: I think we need to define what endorse means, beyond a "special badge". For example, does endorsing an output mean:

  • it's the formal position of UK TRE?
  • it's a notable piece of work that people should take notice of but UK TRE remains neutral on what it means?

@harisood
Copy link
Member Author

Sorry (learning process) I realise the best way to do this is acc to have an issue here that j references the comment only GD, and then have the conversation there! I have closed the first comment now but left the other one on the GD, sorry all 🤦🏽

@Davsarper
Copy link
Contributor

This discusssion and #95 are the same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants