Add Code Insights team page #2140
Conversation
|
Notifying subscribers in CODENOTIFY files for diff f997b0c...7df0f4e.
|
Co-authored-by: Nick Snyder <nick@sourcegraph.com>
Co-authored-by: Joel Kwartler <LoJoel3+gh@gmail.com>
jeanduplessis
changed the title
|
@christinaforney @nicksnyder I've updated the "goals" section of this to align with what we want goals to be, if one of you can take another look. I'll also be updating the web team goals to this format, and after that will plan to update https://about.sourcegraph.com/company/goals/guidelines with a few relevant points. (For example, one question I had, based on the examples of cloud and code intel, is whether goal problems should be exclusively feature-based or whether they should include business "problems" – code intel mentions business problems like demonstrating the benefit of existing features, while cloud focuses more on the customer needs/feature value). |
|
|
||
| 1. Customers can easily create their own custom insights in an intentionally-designed UI. | ||
|
|
||
| - **Outcome:** Code insights can move from prototype to beta feature (easy to enable or enabled by default, documented, and supported by the CE team rather than the product team). |
There was a problem hiding this comment.
Should we have an outcome like "We have at least one customer created code insight that is actively used"?
|
|
||
| - **Outcome:** Code insights features are actively in use by VPs/Directors at 5+ enterprise customers. | ||
|
|
||
| 1. Customers can easily create their own custom insights in an intentionally-designed UI. |
There was a problem hiding this comment.
in an intentionally-designed UI.
What does this mean?
There was a problem hiding this comment.
I should have said "dedicated UI" for clarity, even if the this milestone's UI form won't be as "dedicated" as something like the campaigns UI yet.
There was a problem hiding this comment.
So like a WYSIWYG editor for creating code insights?
There was a problem hiding this comment.
Sort of, though I don't know what WYSIWYG means when WYS is code and WYG is a visual graph (is Looker/Bigquery what you mean?) because it might still be code-as-UI here. The core of this is "you don't have to go and set it up like a prototype in your settings file" but "there's a UI that we built for this purpose" even if this isn't its final form as we learn about problems or personas who would prefer a different UI.
The simplest first step would be to just pull out the code insights settings code into its own settings-like editor you access somewhere in the UI so you don't get distracted or confused by a busy interface when setting up an insight.
Co-authored-by: Nick Snyder <nick@sourcegraph.com>
|
Merging this so that folks can begin referencing it (and I can move this info off the web team page for clarity when the new hires start). @felixfbecker we can continue to make updates, just know you're not back til the new hires start. |
|
Looks great! Thanks for making all the updates @Joelkw! |
* Code insights now has a dedicated page (the 2-person team is still "parented" by and linked to from the web team page.)
The goal of this is to have a page to reference when telling candidates about code insights as one of the different teams that will come out of the web team, to get them excited about this team. I.e. the target audience of this page are candidates.
It would be awesome to attract candidates that are specifically excited about code insights, but that is difficult if we don't have any documentation about this team in the handbook.
Goals were copied from the web team page.
I did not yet add anything from the usual team page structure about contact, processes, members etc, as that doesn't make sense without an operating team yet (and will be "forked" from the web team).
We can add more here that could be attractive (e.g. principles for this feature) but I think this is a good start.