Yes please, CLI is its own brand of user experience
- aaron
On Thursday, September 22, 2016 at 2:09:16 PM UTC-7, DL duglin wrote:
>
> yes yes yes huge +1
>
> -Doug
>
> On Sep 22, 2016, at 4:37 PM, Fabiano Franz > wrote:
>
> I've been talking to a few people in the past couple weeks and now we'd
That said, the draft link came across as '[1] "SIG-CLI' to me. Typo? This
seems like a group with potential overlap with other sigs like api
machinery, would be useful to better understand the boundaries.
- aaron
On Thursday, September 22, 2016 at 4:50:47 PM UTC-7, Aaron Crickenberger
wrote:
API machinery does not want to own the user-facing half of kubectl, I'm
reasonably sure.
On Thu, Sep 22, 2016 at 4:53 PM, Aaron Crickenberger
wrote:
> That said, the draft link came across as '[1] "SIG-CLI' to me. Typo?
> This seems like a group with potential overlap with other sigs like api
>
Would love to see more development on kubectl.
Our wish list:
https://github.com/kubernetes/community/wiki/Roadmap:-kubectl
On Thu, Sep 22, 2016 at 4:50 PM, Aaron Crickenberger
wrote:
> Yes please, CLI is its own brand of user experience
>
> - aaron
>
> On Thursday, September 22, 2016 at 2:09:1
Yeah, the API machinery charter explicitly disclaims the CLI:
https://goo.gl/x5nWrF
On Thu, Sep 22, 2016 at 5:42 PM, Clayton Coleman
wrote:
> +1 - API machinery supports clients and sigs, but does not own them (it
> can help own client machinery though)
>
> On Sep 22, 2016, at 7:55 PM, 'Daniel S
+1 - very good idea
On Thu, Sep 22, 2016 at 10:37 PM, Fabiano Franz wrote:
> I've been talking to a few people in the past couple weeks and now we'd
> like to formally propose the creation of SIG-CLI (Special Interest Group
> for the Kubernetes Command Line Interface).
>
> The idea would be to
