[MEETING-NOTES] Community meeting 2020-08-24

["Elek, Marton" <el...@apache.org>]

TOPICS:

  1. 1.0.0-RC0 vote is open (thanks to Sammi), please vote!!!!!!

  2. 67 open pull requests (!!!) please review

    (we can close /pending requests after a certain time (HDDS-4140))

  3. Update on Ozone as a TLP (proposal will be updated on this week and 
first discussion on ozone-dev will be started about the proposal)

  4. contrib repositories?

There are some Ozone related tools which are developed by personal 
repositories.

For example:

https://github.com/elek/ozone-build-results
https://github.com/elek/ozone-perf-env
https://github.com/elek/ogh
https://github.com/elek/ozone-go

(And I know that others also have some, for example test tools).


Some of them are more and more mature and might be useful to move them 
closer to the Apache.

But at the beginning they require a lot of additional Pull request / 
reviews and we might not have the bandwidth...

One possible option is to create separated git repository (under apache 
org) for them but use post-commit reviews:

https://medium.com/@copyconstruct/post-commit-reviews-b4cc2163ac7a

I would use this approach only for experiments / tools after discussing 
to create a repository for each (NEVER for code released under Apache)

Pull requests would be required to merge (because CI), but it would be 
possible to auto-merge after 2-3 days.

Any thoughts?






RECORDING:

 
https://cloudera.zoom.us/rec/share/x9FFcJ_s1GdLfqfs-R_6W6Q4MbXVX6a80CZP-KAPmk99oqnamRBoAGbJalTKzpaP 
Passcode: e+&&CMd1


Marton

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-dev-help@hadoop.apache.org