From a7e3ae961296b785ef0dce845d33790f827faac2 Mon Sep 17 00:00:00 2001 From: Jan Hartman Date: Tue, 26 Mar 2024 11:35:59 +0100 Subject: [PATCH 1/5] Add myself to the team page --- data/team.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/data/team.yml b/data/team.yml index dba4268e707e..b4c4bc411641 100644 --- a/data/team.yml +++ b/data/team.yml @@ -1828,3 +1828,15 @@ anish_lakhwara: location: Vancouver, Canada 🇨🇦 links: '[LinkedIn](https://www.linkedin.com/in/anish-lakhwara-0a62651bb/), [Website](https://anish.lakhwara.com)' description: Anish was born in Australia, raised in India, and now calls Canada home. Ever interested in computing, Anish enjoys building and contributing to open source, tinkering on his nvim config, and playing with shiny new tools. Always open to learning more, and aspiring to be a good engineer and a great human. When not touching computers, Anish likes rock climbing, sailing, gardening, and annoying his very loud cat, Imoh. + +jan_hartman: + name: Jan Hartman + email: jan.hartman@sourcegraph.com + github: janhartman + pronouns: he/him + role: Machine Learning Engineer + reports_to: head_ai + location: Ljubljana, Slovenia 🇸🇮 + links: '[LinkedIn](https://www.linkedin.com/in/jan-hartman)' + pronunciation: https://forvo.com/word/jan/ + description: Jan is a machine learning enthusiast. He has a master's degree in Computer and Data Science from the University of Ljubljana. Before joining Sourcegraph, Jan worked in adtech, building deep learning models for online recommendations and scaling them to over a billion predictions per second. Besides teaching machines to think, Jan enjoys hiking, gaming, DnD, and chilling on the couch with his dog, Rio. From e99794968c877f5b3e0e474a35412dc8fbdea79b Mon Sep 17 00:00:00 2001 From: Jan Hartman Date: Tue, 26 Mar 2024 11:46:16 +0100 Subject: [PATCH 2/5] Add geolocation --- content/team/locations.geojson | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/content/team/locations.geojson b/content/team/locations.geojson index 94b097364cda..804c2389cee9 100644 --- a/content/team/locations.geojson +++ b/content/team/locations.geojson @@ -780,6 +780,17 @@ 52.513384 ] } + }, + { + "type": "Feature", + "properties": "Jan Hartman", + "geometry": {a + "type": "Point", + "coordinates": [ + 14.40685, + 45.95371 + ] + } } ] } From 8c302ec4835f6660be055e422df187f1b8fa15a3 Mon Sep 17 00:00:00 2001 From: Jan Hartman Date: Tue, 26 Mar 2024 11:48:00 +0100 Subject: [PATCH 3/5] Fix typo --- content/team/locations.geojson | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/team/locations.geojson b/content/team/locations.geojson index 804c2389cee9..4533ffb29659 100644 --- a/content/team/locations.geojson +++ b/content/team/locations.geojson @@ -784,7 +784,7 @@ { "type": "Feature", "properties": "Jan Hartman", - "geometry": {a + "geometry": { "type": "Point", "coordinates": [ 14.40685, From 94f072196b1989c7d6d77f9e7cde37f84ca5e499 Mon Sep 17 00:00:00 2001 From: Jan Hartman Date: Tue, 26 Mar 2024 12:20:20 +0100 Subject: [PATCH 4/5] Remove inexistent Cody Slack channels --- .../communication/team_chat.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/content/company-info-and-process/communication/team_chat.md b/content/company-info-and-process/communication/team_chat.md index 367234ec861a..c0e152c98529 100644 --- a/content/company-info-and-process/communication/team_chat.md +++ b/content/company-info-and-process/communication/team_chat.md @@ -845,12 +845,6 @@ There’s no one-size-fits-all approach here. Just be mindful of the frequency o General dogfooding and external feedback from Cody users. Feedback that’s specific to a particular client should go in the relevant #wg- channel. - - #discuss-cody-context - - Discussion of Cody context - - #discuss-cody-strat @@ -881,12 +875,6 @@ There’s no one-size-fits-all approach here. Just be mindful of the frequency o Discussion space for Cody product teams to coordinate and collaborate on cross-team work - - #wg-cody-vs-code - - Discussion, questions, bug reports, and feedback specific to the VSC extension. VS Code team collaboration - - #wg-cody-neovim From 5b4f9e9f1de789c9264db92d1770329ce00026f4 Mon Sep 17 00:00:00 2001 From: Jan Hartman Date: Wed, 27 Mar 2024 13:27:14 +0100 Subject: [PATCH 5/5] Readd Slack channels with correct names --- .../communication/team_chat.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/company-info-and-process/communication/team_chat.md b/content/company-info-and-process/communication/team_chat.md index c0e152c98529..0f169bd3f238 100644 --- a/content/company-info-and-process/communication/team_chat.md +++ b/content/company-info-and-process/communication/team_chat.md @@ -845,6 +845,12 @@ There’s no one-size-fits-all approach here. Just be mindful of the frequency o General dogfooding and external feedback from Cody users. Feedback that’s specific to a particular client should go in the relevant #wg- channel. + + #discuss-context + + Discussion of Cody context + + #discuss-cody-strat @@ -875,6 +881,12 @@ There’s no one-size-fits-all approach here. Just be mindful of the frequency o Discussion space for Cody product teams to coordinate and collaborate on cross-team work + + #team-cody-clients + + Discussion, questions, bug reports, and feedback about Cody clients. + + #wg-cody-neovim