search

kubeflow / blog

Kubeflow blog based on fastpages
https://blog.kubeflow.org
Apache License 2.0
17 stars 40 forks source link

Kubeflow 1.3 Blog Post draft #83

Closed jbottum closed 3 years ago

jbottum commented 3 years ago

@theadactyl Hi Thea, Please find the Kubeflow 1.3 Blog Post draft in this google doc. We would like to ask for your initial review of the structure (by Thu COB/Fri) so that we can enter into a Pull Request and then ask for wider comments. Thanks for your help. Josh / Jorge

https://docs.google.com/document/d/1B6yqMvwJGojjVh1Hjloy6ljSo8H_C_zStLyoax0EWrA/edit?usp=sharing

theadactyl commented 3 years ago

Sorry if I'm late for reviewing on the doc vs github. I think this mostly looks good, pending some style comments & TBDs being addressed.

On Tue, Mar 30, 2021 at 7:48 AM Josh Bottum @.***> wrote:

@theadactyl https://github.com/theadactyl Hi Thea, Please find the Kubeflow 1.3 Blog Post draft in this google doc. We would like to ask for your initial review of the structure (by Thu COB/Fri) so that we can enter into a Pull Request and then ask for wider comments. Thanks for your help. Josh / Jorge

https://docs.google.com/document/d/1B6yqMvwJGojjVh1Hjloy6ljSo8H_C_zStLyoax0EWrA/edit?usp=sharing

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubeflow/blog/issues/83, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABREJVIPMABHMXXB27CFVO3TGHQFHANCNFSM42CHDBNA .

jtfogarty commented 3 years ago

this is @jtfogarty and I approve this message Jeff Fogarty AVP ML Cloud Engineer US Bank

theadactyl commented 3 years ago

I think starting the first sentence with the Derby is a bit disorienting. It made me do a quick double-take. Maybe there is room for a toned-down of the analogy and making sure the title and first words in the sentence focus more on the 1.3 technology being delivered? I think that's the most useful news item for our audience. Also, best practices for new software announcements / launches are to avoid language like "win, beat, outperform".

Since that's my personal take, I'd like to hear from @Bobgy and the @kubeflow/wg-serving-leads @kubeflow/wg-notebooks-leads for their feedback considering the broad work being represented.

/cc @castrojo in case we should be discussing this on the PR instead. /cc @james-jwu who will need to approve blog post if we want it to go out before I'm back on April 12

jbottum commented 3 years ago

/close

google-oss-robot commented 3 years ago

@jbottum: Closing this issue.

In response to [this](https://github.com/kubeflow/blog/issues/83#issuecomment-837151066): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.