Add WG AutoML #358
Add WG AutoML #358
Conversation
|
This change is |
|
Why are training and autoML two different working groups as opposed to sub projects within in one working group? What is the overlap in terms of:
|
|
@jlewi Ref #356 (comment) |
|
Thanks @gaocegege @andreyvelich I replied on #356 lets continue the discussion there. |
|
I have added meeting time (10 am UTC second Wednesday, 4 pm UTC fourth Wednesday). |
|
@andreyvelich Are we planning on having 1 WG for training and automl? If so which PR are we going to use? |
|
I removed WIP status, since we decided to move forward with 2 WG: Training and AutoML. |
This time looks good to me. |
|
/lgtm |
|
/lgtm |
|
lgtm |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
according to KF process the Charter is to be submitted _after_: > Add WG-related docs like charter.md, schedules, roadmaps, etc. to your new kubeflow/community/wg-foo directory once the above PR is merged from here: https://github.com/kubeflow/community/blob/master/wgs/wg-lifecycle.md#:~:text=Add%20WG%2Drelated%20docs%20like%20charter.md%2C%20schedules%2C%20roadmaps%2C%20etc.%20to%20your%20new%20kubeflow/community/wg%2Dfoo%20directory%20once%20the%20above%20PR%20is%20merged The group however pointed out in more recent WGs creation the Charter was submitted with the WG creation PR. example: kubeflow#358 Therefore, advancing Charter proposal at once in this PR.
according to KF process the Charter is to be submitted _after_: > Add WG-related docs like charter.md, schedules, roadmaps, etc. to your new kubeflow/community/wg-foo directory once the above PR is merged from here: https://github.com/kubeflow/community/blob/master/wgs/wg-lifecycle.md#:~:text=Add%20WG%2Drelated%20docs%20like%20charter.md%2C%20schedules%2C%20roadmaps%2C%20etc.%20to%20your%20new%20kubeflow/community/wg%2Dfoo%20directory%20once%20the%20above%20PR%20is%20merged The group however pointed out in more recent WGs creation the Charter was submitted with the WG creation PR. example: kubeflow#358 Therefore, advancing Charter proposal at once in this PR.
according to KF process the Charter is to be submitted _after_: > Add WG-related docs like charter.md, schedules, roadmaps, etc. to your new kubeflow/community/wg-foo directory once the above PR is merged from here: https://github.com/kubeflow/community/blob/master/wgs/wg-lifecycle.md#:~:text=Add%20WG%2Drelated%20docs%20like%20charter.md%2C%20schedules%2C%20roadmaps%2C%20etc.%20to%20your%20new%20kubeflow/community/wg%2Dfoo%20directory%20once%20the%20above%20PR%20is%20merged The group however pointed out in more recent WGs creation the Charter was submitted with the WG creation PR. example: kubeflow#358 Therefore, advancing Charter proposal at once in this PR. Signed-off-by: tarilabs <matteo.mortari@gmail.com>
I added AutoML WG.