search

finos / technical-oversight-committee

đŸ“‹ FINOS Technical Oversight Committee
5 stars 3 forks source link

Added operations documentation and guides #145

Open eddie-knight opened 3 weeks ago

maoo commented 3 weeks ago

This is great @eddie-knight , thanks for this!

What do you think of https://github.com/finos/technical-oversight-committee/blob/main/responsibilities.md ? Shall we merge it into the new operations.md ?

chris-twiner commented 3 weeks ago

All the content looks great thanks. I do miss a bit of the flavour on resource / standards competition though. (This may have been explained in the call but I had technical issues, apologies if it did)

eddie-knight commented 3 weeks ago

I do miss a bit of the flavour on resource / standards competition though. (This may have been explained in the call but I had technical issues, apologies if it did) @chris-twiner

Sorry I'm not tracking on this! What do you mean by resource / standards competition?

chris-twiner commented 3 weeks ago

I do miss a bit of the flavour on resource / standards competition though. (This may have been explained in the call but I had technical issues, apologies if it did) @chris-twiner

Sorry I'm not tracking on this! What do you mean by resource / standards competition?

sorry, it wasn't well explained (and honestly rushed - had to travel to feed a cat..), although we have a link to the contribution-principles it's listed as something only the assigned TOC member would use to review.

I'm suggesting turning that around a bit and having that be upfront in the proposed project entry on the community page provided by the project team. E.g. "The contribution team should provide their alignment to the contributions principles describing the fit with existing FINOS projects, standards and the organisation as whole; an assigned TOC member will then review".

eddie-knight commented 3 weeks ago

@chris-twiner I think that's a really good point— in fact I think we might benefit from a more structured review process to help both contributors and reviewers.

Currently this PR doesn't include any changes to the review or contribution process (the diff is a result of moving things)... How do you feel about us working on that in a follow-up PR?

eminty69 commented 3 weeks ago

I do miss a bit of the flavour on resource / standards competition though. (This may have been explained in the call but I had technical issues, apologies if it did) @chris-twiner

Sorry I'm not tracking on this! What do you mean by resource / standards competition?

sorry, it wasn't well explained (and honestly rushed - had to travel to feed a cat..), although we have a link to the contribution-principles it's listed as something only the assigned TOC member would use to review.

I'm suggesting turning that around a bit and having that be upfront in the proposed project entry on the community page provided by the project team. E.g. "The contribution team should provide their alignment to the contributions principles describing the fit with existing FINOS projects, standards and the organisation as whole; an assigned TOC member will then review".

I like this idea as well but agree with @eddie-knight about looking at it in a separate PR

eminty69 commented 3 weeks ago

Ugh, sorry accidentally closed the PR. I shouldn't do anything with buttons to click at the end of the day !

eminty69 commented 3 weeks ago

Now that I've finishing messing up @eddie-knight's PR, I did have a general comment. I like the direction these documentation/guides outline but I think its something that we should discuss as a group at the TOC as it does change the way we work. I'd be interested in hearing others views - perhaps a topic for the next call?