PR Feedback Requested by EOD Wednesday

[Dawn Foster]

Hi everyone,

Just a friendly reminder to provide feedback on the PR with all of the initial docs for the repo by the end of your day on Wednesday so that we can merge it on Thursday.
https://github.com/coredashio/community/pull/1

A big thank you to Julius and Augustin for all of their feedback so far! As a part of that feedback, I've made a bunch of updates, so please have a look and provide feedback.

Almost everything is clearly marked as a draft (governance, scope, goals, etc.), so our goal right now should be to get this "good enough" that we can open things up with plans to continue iterating and finalizing our docs as our plans start to solidify.

As a reminder, our first public meeting will be on September 2.
https://docs.google.com/document/d/1FZy-tuIz-C5NSQe3AdeT-DixZZXMjDi-BnQy2kj_9xU/edit

Let me know if you have any questions.

Cheers,
Dawn

[Alexis Richardson]

Thanks Dawn 

Just to clarify my comments re target users.  

Of course in a sense the target users include everyone.  But that isn't a scope. 

My view is that we should try very hard to avoid creating tools that can only be used by a small elite of Go devops type people.  Or if you like, the existing early adopters of Kubernetes.  Quite frankly they will figure out how to use any tool, if it does what they need, however bad the UX.  (please don't ask me to provide recent examples :) 

That is why I suggested that we envisage a target user who is creating a Web front end (or similar).  This is someone who will benefit hugely from a simple system for dashboard widgets and screens, that can be used anywhere that js will run and hooked up to data sources. 

If you don't target these people, then you will probably design another cleverman cloud native multitool that, in the end, excludes them. 

In addition we have all seen how Grafana has been hard to use for these folks due to some early design choices that makes it all quite alienating if your experience is a modern frontend stack. 

Let's aim for a big user base by opening the field to a large set of well established users who create screens.  That doesn't include the backend people. 

--
You received this message because you are subscribed to the Google Groups "coredash-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coredash-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/coredash-discuss/C999A016-9D99-4DB9-92F6-4F077AFD79B8%40vmware.com.
For more options, visit https://groups.google.com/d/optout.

[Dawn Foster]

Hi Alexis,

 

This is super helpful, thank you! I think positioning the audience specifically as a “Javascript developer” was confusing, so I’ve re-written it to be a bit more general and highlight what we’re trying to achieve.

 

There is a new commit that adds this to the top of the Draft Goals section in the README:

 

We aim to make CoreDash easy to use by not requiring highly specialized skills

to be able to benefit from these tools and dashboards. Anyone with basic web

front end skills (Javascript, etc.) should be able to create dashboard widgets

and screens and connect them to a variety of data sources without needing to

write complex code or be a sys admin / DevOps expert. We hope that by making

these technologies more inclusive to people with a wide variety of skills, we

can open the field to a larger set of well established users who create and

customize dashboard screens.

 

Cheers,

Dawn

[Alexis Richardson]

This is great, thank you! 

[Jaana Dogan]

Off PR comment:

Do we need to mention that the relationship to Grafana, especially in the intro? I think we should clearly strongly message that coredash is a new initiative, a new set of tools. When we mention Grafana so strongly, it makes it look like it's just a counter response to the license change and minimizes the motivation a bit.

To view this discussion on the web visit https://groups.google.com/d/msgid/coredash-discuss/CAOSi4U4__D5yMx9o9SWoHf%2BVC5%2BmeK0Gg_0p0oMNSHDrO-ECUw%40mail.gmail.com.

[Alexis Richardson]

+1, agree with Jaana

this is where the right name helps!

[Augustin Husson]

Yeah probably more catchy to introduce CoreDash like that indeed Jaana ! :)

And it should be more accurate as visualisation is just one part of the goals of this project.

To view this discussion on the web visit https://groups.google.com/d/msgid/coredash-discuss/CAOSi4U40oJUjiq6uZcH-7EkeUa%2BAZo5fydzNV-rTZ_v0oJ7MJQ%40mail.gmail.com.

[Alexis Richardson]

so let's have a purposeful and clear name

To view this discussion on the web visit https://groups.google.com/d/msgid/coredash-discuss/CAOJizGfj5xLAY4NnfcWP1Zvy98d2ES2rE5Ts9%3Doz%3D20SqqLFUQ%40mail.gmail.com.

[Augustin Husson]

Nop :)

[Josh Powell]

Is this the phase where we start throwing out names and put together a survey?

How about Chartible. Doesn’t seem to be taken and I like it’s pun with charitable. 

Josh Powell

On Aug 24, 2021, at 12:27 PM, Augustin Husson <husson....@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/coredash-discuss/CAOJizGfEceM1mR4cFAyY7P%2BXDtndD6CyBwv78LtJYOF1x2PS0w%40mail.gmail.com.

[Alexis Richardson]

A list might help 

[Dawn Foster]

Jaana,

 

Agreed. I’ve removed the mention of Grafana from the top of the readme, and made the other change you suggested about Jaeger / OpenTelemetry.

 

All - Let me know if you have any additional suggestions / additional improvements.

 

For the record, I’m staying out of the naming discussions. My experience with naming has led me to believe that no matter what name we select, some portion of the community will love it, another portion will hate it, and eventually everyone one will be used to whatever we call it. Naming at big companies / foundations involves mostly legal discussions about things like trademarks and searches for whether we can get the name on all the things (GH, web, social, etc.), which isn’t much fun, and I don’t really care what we call it as long as we’re making progress on the project, so I’ll be over here quietly making progress while other people can argue about names. :)

 

Cheers,

Dawn

[Augustin Husson]

Thanks for your work @Dawn Foster !

So cool to see things moving.

To view this discussion on the web visit https://groups.google.com/d/msgid/coredash-discuss/5DEDE543-81DA-4C71-A424-1A84BE5364A6%40vmware.com.

[Jaana Dogan]

Thanks so much, Dawn!!!