README ok?

#2
by patrickvonplaten - opened

@julien-c , @lysandre , @sgugger , @osanseviero , @merve @valhalla , @niels - what do you think about the maintenance as proposed in the README?

  • The idea is that a dev advocate team member dispatches the issue to a OS team member, who is then responsible for answering.
  • All relevant maintainers should be added to the respective orgs then

I wonder if it really makes sense to have overhead from DA members are they might not necessarily have that much context (+ timezone difference might mean slow time to dispatch things).

Maybe this could instead be handled with email notification + filters making the dispatching a bit less needed?

HF Canonical Model Maintainers org

I agree with @osanseviero that dispatching might not really be needed, because for models inside orgs (i.E. Facebook, OpenAI, Google, Helsinki-NLP, Microsoft, AllenAI, sentence-transformers) the relevant team members can just join the org no?

Dispatching might be needed but just for canonical models. WDYT?

Other than that, love the new README. In particular the proposed Approval system is ๐Ÿ”ฅ

Sounds good, should we maybe then remove all DA members from the review/approval system?

HF Canonical Model Maintainers org

yes i think let's remove the "dispatched by" DA members in the 'co-maintained by HF orgs'?

and mention that everyone is still welcome to join those 'co-maintained by HF orgs' (love that name ๐Ÿ˜‚) cc @saullu

HF Canonical Model Maintainers org

(see #3)

Sounds good to me!

HF Canonical Model Maintainers org

ok-okay.gif

Sign up or log in to comment