profile
viewpoint
Christina Forney christinaforney Sourcegraph Woodside, CA christinaforney.com

lsif/lsif.github.io 3

https://lsif.dev

rubyforgood/panda_app 2

Ruby for Good 2016: A tool to help researchers score observations of animal behaviors

christinaforney/Documentation 0

Documentation repository

christinaforney/gradle-wrapper 0

stock gradle wrapper

christinaforney/minimal-mistakes 0

:triangular_ruler: A flexible two-column Jekyll theme perfect for building personal sites, blogs, and portfolios.

christinaforney/my_jekyll_site_example 0

Example setup and steps for configuring Jekyll with Minimal Mistakes and Circle CI

PullRequestReviewEvent

PR opened sourcegraph/about

Reviewers
Add link to Security roadmap Google doc
+1 -1

0 comment

1 changed file

pr created time in 7 hours

create barnchsourcegraph/about

branch : christinaforney-patch-1

created branch time in 7 hours

delete branch sourcegraph/about

delete branch : christinaforney-patch-1

delete time in 7 hours

push eventsourcegraph/about

Christina Forney

commit sha ec66b9729f01c53765787d0d4a4c0616f73b3cca

Add Technical writer to careers page (#1842)

view details

push time in 7 hours

PR opened sourcegraph/about

Add Technical writer to careers page
+1 -0

0 comment

1 changed file

pr created time in 7 hours

create barnchsourcegraph/about

branch : christinaforney-patch-1

created branch time in 7 hours

PullRequestReviewEvent

push eventsourcegraph/about

Christina Forney

commit sha 986e1ead3b0b1c22da4429dd997038d4015de365

Monitor company files (#1835)

view details

push time in 2 days

delete branch sourcegraph/about

delete branch : cf-codenotify

delete time in 2 days

PR merged sourcegraph/about

Monitor company files
+2 -0

1 comment

1 changed file

christinaforney

pr closed time in 2 days

PR opened sourcegraph/about

Monitor company files
+2 -0

0 comment

1 changed file

pr created time in 2 days

create barnchsourcegraph/about

branch : cf-codenotify

created branch time in 2 days

push eventsourcegraph/about

Christina Forney

commit sha c34d85fa9bf93b34dc10dc89139002ddbb285969

Improvements to onboarding docs (#1801)

view details

push time in 3 days

delete branch sourcegraph/about

delete branch : cf/tech-writer-onboarding

delete time in 3 days

PR merged sourcegraph/about

Reviewers
Improvements to onboarding docs

Cleaning up and organizing information from https://github.com/sourcegraph/about/pull/1446

Changes:

  • General
    • The general onboarding list was long and hard to read. I moved it to it's own page and cleaned up the sections.
    • Added a section for before starting at Sourcegraph
    • Cleaned up spending company money to remove redundancy and organize/format
  • Product
    • Added resources and section to product onboarding about contributing to the docs
    • Extracted some processes to the technical writer page
    • ~Created a developing with Windows guide (TBD if this should be kept and/or moved)~ Removed
+140 -68

0 comment

6 changed files

christinaforney

pr closed time in 3 days

issue commentsourcegraph/sourcegraph

Support diff/commit search on more than 50 repositories at a time

This is preventing https://app.hubspot.com/contacts/2762526/company/947819054 from using commit searches entirely.

slimsag

comment created time in 3 days

PullRequestReviewEvent

push eventsourcegraph/about

AlicjaSuska

commit sha 12eced1776efcc7e572698fe4a8f1e175657506e

Change 'Working with design' section (#1779) * Change 'Working with design' section * Apply grammatical and formatting suggestions Co-authored-by: Christina Forney <christina@sourcegraph.com> Co-authored-by: Christina Forney <christina@sourcegraph.com>

view details

Chayim

commit sha adb0ffcacf77caa9eacabcc417fe77e05448341d

Clarifying vulnerability payment amounts and categories (#1756) Co-authored-by: Quinn Keast <qkeast@sourcegraph.com> Co-authored-by: Nick Snyder <nick@sourcegraph.com> Co-authored-by: ElizabethStirling <40177171+ElizabethStirling@users.noreply.github.com> Co-authored-by: Chayim I. Kirshen <chayim@gnupower.net>

view details

Noah Santschi-Cooney

commit sha ff2d51e1363e1b01b31a4b8506696b4631a5b92d

Fixed image src for Scott Raney in About page (#1803)

view details

aileenrose

commit sha d01fca7bfbd93208f3f1048ebe07a5d01100490b

Add logo (#1804)

view details

Renovate Bot

commit sha 2b62af1d81c0614328f4a90ba30c86a216b2b66c

Update dependency @sourcegraph/eslint-config to ^0.20.12

view details

Christina Forney

commit sha 201f2152c96f2c9164175f4e08d8312c02459e7c

Fix links to product docs in the handbook (#1802) * Fixing search and campaigns links * Remaining user links * Dev docs links

view details

aileenrose

commit sha cb703a7dd133808c53943a140e959ded22a91f6d

Add open positions for marketing (#1800) * Add open positions for marketing * Update apply links

view details

aileenrose

commit sha 61e126e5fd97982e78f8f5bce212084a15dc6f99

Update marketing_operations.md (#1605)

view details

Chris Pine

commit sha e1a50127945e7b637330b706e95171862e1d5fad

update campaigns roadmap (#1808) Removed completed items and added our current, up-to-date roadmap

view details

lorihey

commit sha 1754b7f54c21e32075fa4242e8d0adce19a46086

Update director_of_community.md (#1809) * Update director_of_community.md Changed first subhead from "content strategy" to "community relations strategy" Changed Open Source to open source (per our style guide) * Update director_of_community.md Co-authored-by: aileenrose <aileenrose@users.noreply.github.com>

view details

Noemi Mercado

commit sha 8a1abdd348648750fc42566eeff0da6c875b01f6

Update director_of_community.md (#1811)

view details

Noemi Mercado

commit sha ccf9d9ad517ba67e75451761a40c47137fc43769

Update editor_in_chief.md (#1812) Fixed the first apply link.

view details

joekirscherSG

commit sha 592bec0f821da1a5c5253cb0a45706eb24948cf2

Update salesresources.md (#1813)

view details

María Craig

commit sha d3a5e11c80ce0402b4b55dfd29d7deef1b270646

Update Code Intel roadmap (#1786) Updated roadmap items after 3.22 planning and added Code Intel Gantt chart section

view details

Kacie Jenkins

commit sha fe2723730823517b37766571001f6c6f046749fa

Update editor_in_chief.md (#1816)

view details

Kacie Jenkins

commit sha 0ee95e0c96a850a81aaf919a3a688d85288d56de

Update careers.md (#1817)

view details

ElizabethStirling

commit sha bd718e86ecc01577e85381900b16d31d7b509230

High agency expansion (#1807) Expand comments on high agency to include insight from colleagues

view details

Kacie Jenkins

commit sha 75de4cd21c8fbd8ffaf0241b11c760f43bc76286

Update index.md (#1774) small typo fix Co-authored-by: aileenrose <aileenrose@users.noreply.github.com>

view details

joekirscherSG

commit sha 3c57ad02ad7b54c3a0236d8b771a5513cdf8527a

Update salesresources.md (#1818)

view details

aileenrose

commit sha bf3701b9d46e7983711613a9b6868ce93926b498

Add blog rss feed (#1788)

view details

push time in 3 days

push eventsourcegraph/about

Christina Forney

commit sha fd2e90812f6c17c7d2957c5c5ff21945fbf7b2b4

Removing windows guide

view details

push time in 3 days

Pull request review commentsourcegraph/about

Improvements to onboarding docs

+# Using a windows environment

Ok, makes sense. I think your recommendation to always use a Linux environment and just follow those instructions is sufficient. I don't want to keep documentation that will lead to more confusion. I'll delete this page.

Thank you for all the clarification!

christinaforney

comment created time in 3 days

PullRequestReviewEvent

push eventsourcegraph/about

Christina Forney

commit sha 88e14a29f06ae1589281162960b81c735a12f3c7

Update handbook/people-ops/hiring/evaluating_values.md Co-authored-by: Nick Snyder <nick@sourcegraph.com>

view details

push time in 3 days

Pull request review commentsourcegraph/about

Add evaluating values to hiring process

+# Evaluating values in an interview++We expect every teammate, team, and our company to live up to the [Sourcegraph values](../../../company/values.md). It is therefore important taht we evaluate every candidate on the values to determin how successful they will be within Sourcegraph.++It is the responsibility of every interviewer to think about these values when interviewing a candidate. When submitting feedback for a candidate, copy the list of values into your notes and score the candidate out of 5 based on the rubric.++## Rubric++Scored out of 5:++- 1 - Exhibited behavior that is contrary to this value+- 2 - I did not have any evidence towards or against this value (neutral)+- 3 - Gave the impression they have this value, but lacking evidence+- 4 - Demonstrated this value with evidence+- 5 - Exceptionally demonstrated this value, with abundent evidence++## Values to copy into feedback++Use this plaintext format for easy addition to the Lever feedback area.++```markdown+- Be customer driven:+- Work as a team:+- High agency:+- High quality:+- Open and transparent:

Yes, I think so. Where can we clarify this?

christinaforney

comment created time in 3 days

PullRequestReviewEvent

Pull request review commentsourcegraph/about

Add evaluating values to hiring process

+# Evaluating values in an interview++We expect every teammate, team, and our company to live up to the [Sourcegraph values](../../../company/values.md). It is therefore important taht we evaluate every candidate on the values to determin how successful they will be within Sourcegraph.++It is the responsibility of every interviewer to think about these values when interviewing a candidate. When submitting feedback for a candidate, copy the list of values into your notes and score the candidate out of 5 based on the rubric.++## Rubric++Scored out of 5:++- 1 - Exhibited behavior that is contrary to this value+- 2 - I did not have any evidence towards or against this value (neutral)+- 3 - Gave the impression they have this value, but lacking evidence+- 4 - Demonstrated this value with evidence+- 5 - Exceptionally demonstrated this value, with abundent evidence

Love this suggestion!

christinaforney

comment created time in 3 days

PullRequestReviewEvent

Pull request review commentsourcegraph/about

Added Kubernetes Training Video To CE Onboarding

 Welcome to Sourcegraph! This document will guide you through customer engineerin - Watch [Dan's recorded demo](https://drive.google.com/file/d/1VUZ0rnZQpNgjtGDI0tMC-h-OtL0Czz8H/view?usp=sharing)  - Schedule a demo from the most recent CE hire before you - [Install Sourcegraph](https://docs.sourcegraph.com/admin/install/) using each of the three deployment options+  - Watch Dave's Kubernetes Walkthrough video: https://drive.google.com/drive/folders/1Mqlndi3anVp9Eq8tYgVoyjodyoxsfik2?usp=sharing
  - Watch [Dave's Kubernetes Walkthrough video](https://drive.google.com/drive/folders/1Mqlndi3anVp9Eq8tYgVoyjodyoxsfik2?usp=sharing)
tistru

comment created time in 3 days

PullRequestReviewEvent

Pull request review commentsourcegraph/sourcegraph

Add Cases For Connecting To Sourcegraph

  Sourcegraph periodically sends a ping to Sourcegraph.com to help our product and customer teams. It sends only the high-level data below. It never sends code, repository names, usernames, or any other specific data. To learn more, go to the **Site admin > Pings** page on your instance. (The URL is `https://sourcegraph.example.com/site-admin/pings`.) +## Connection to Sourcegraph+1. To send pings that:+   - Check for new product updates.+   - Send anonymous, non-specific, aggregate metrics back to Sourcegraph.com. You can see the full list below. +1. Sourcegraph extensions are fetched from Sourcegraph.com's extension registry (unless you are using a private extension registry: https://docs.sourcegraph.com/admin/extensions#publish-extensions-to-a-private-extension-registry).
1. Sourcegraph extensions are fetched from Sourcegraph.com's extension registry (unless you are using a [private extension registry](https://docs.sourcegraph.com/admin/extensions#publish-extensions-to-a-private-extension-registry)).
tistru

comment created time in 3 days

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentsourcegraph/about

Add evaluating values to hiring process

@withdavidli Yes! That format sounds perfect. I would put it at the bottom of the form so that the interview module feedback is at the top.

christinaforney

comment created time in 3 days

PR opened sourcegraph/about

Reviewers
Add evaluating values to hiring process

I think we should immediately start having every interviewer follow this process.

@withdavidli - is it possible to add this as a separate section/field? It would be better if we didn't have to copy and paste every time.

+33 -0

0 comment

2 changed files

pr created time in 3 days

create barnchsourcegraph/about

branch : cf/hiring-values

created branch time in 3 days

pull request commentsourcegraph/sourcegraph

docs: update search assets to work on dark background

Looks good!

rvantonder

comment created time in 3 days

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentsourcegraph/about

Be a good human

 These values are the beliefs and principles that help us achieve our [goals](goa - [**High quality**](#high-quality): You are responsible for finding out what high-quality work looks like and producing that high-quality work iteratively. - [**Open and transparent**](#open-and-transparent): You proactively communicate in an open and transparent way. - [**Continuously grow**](#continuously-grow): You strive to continuously grow and learn by genuinely soliciting feedback early and often, and humbly reflecting on your past mistakes.-- [**Be human**](#be-human): You are kind, empathetic, authentic, humble.+- [**Be good human**](#be-a-good-human): You are kind, empathetic, authentic, humble.
- [**Be a good human**](#be-a-good-human): You are kind, empathetic, authentic, humble.
nicksnyder

comment created time in 4 days

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentsourcegraph/about

Update Code Intel roadmap

I just confirmed it worked for me locally - sorry I missed that the netlify was out of date! It does not render mermaid in GitHub, only when deploying the docsite.

we do have issue breakdowns for each of these but it seemed a bit too task-oriented for a roadmap. I will work on finding a middle ground granularity where we have smaller efforts labeled in a more product-oriented way.

Sounds good!

macraig

comment created time in 5 days

PR opened sourcegraph/about

Fix links to product docs in the handbook

We moved a bunch of documentation around, this cleans up links to those docs.

+90 -90

0 comment

51 changed files

pr created time in 6 days

create barnchsourcegraph/about

branch : cf/fix-doc-links

created branch time in 6 days

Pull request review commentsourcegraph/about

Improvements to onboarding docs

+# Using a windows environment

@davejrt and @pecigonzalo - you were both mentioned as using PC's in the guide. Is the information on the Windows doc helpful to you at all? Do you think it will be useful to other teammates? Going forward, anyone on the product team is expected to be running a unix environment (windows is not acceptable).

christinaforney

comment created time in 6 days

PullRequestReviewEvent

push eventsourcegraph/about

Christina Forney

commit sha 5a32f32ad30eca7caba8dfc2a5f1b3dcaafa3ec0

Cleaning up tech writer onboarding and moving into separate pages

view details

push time in 6 days

PR closed sourcegraph/about

Reviewers
Tech writer onboarding

@christinaforney I couldn't figure out how to fix the issue with the numbering in Local Environment - Windows section, but please look over the rest (especially the Mac sections)

+260 -0

2 comments

2 changed files

kghopson

pr closed time in 6 days

pull request commentsourcegraph/about

Tech writer onboarding

Moving to https://github.com/sourcegraph/about/pull/1446

kghopson

comment created time in 6 days

PR opened sourcegraph/about

Improvements to onboarding docs

Cleaning up and organizing information from https://github.com/sourcegraph/about/pull/1446

+269 -67

0 comment

6 changed files

pr created time in 6 days

create barnchsourcegraph/about

branch : cf/tech-writer-onboarding

created branch time in 6 days

push eventsourcegraph/about

Christina Forney

commit sha f2c76471f118f56d1277be7680a1d5d6e0684b49

Fixing broken link

view details

push time in 6 days

push eventsourcegraph/about

Christina Forney

commit sha e0bf5e1c9130374c6f885680d225b0006ae8bd00

Add roles folder and move jd

view details

push time in 6 days

push eventsourcegraph/about

Christina Forney

commit sha 58e3a63cf3f00ae5d5f1dece2ffa2b1df43b8301

Be a good human

view details

push time in 6 days

push eventsourcegraph/sourcegraph

ᴜɴᴋɴᴡᴏɴ

commit sha b5d4dd7c638f8090f422e92a88e7641aad9850a8

authz: remove read/write paths of permissions in binary format (#14660)

view details

Eric Fritz

commit sha f3efc2e657915a064867b7db3df5dbd0126ecff2

chore: Fix enterprise frontend build (#14721)

view details

Eric Brody-Moore

commit sha a3daa7bdb59ccf9be4ad58127e9861b13c18dda1

Add homepage panel stats to pings (#14589) * started homepage panel pings * added files * updated sql query, still wip * updated sql query * types.go * update data types * updated struct * float32 to float64 * updated type error * updated sql query with nullif * updated sql * finally the right sql query * remove print statement * add to docs * format with prettier * format files * Use more efficient query * fixup! Simplify GetHomepagePanels * fixup! Use timestamp index (thanks @mrnugget) Co-authored-by: Tomás Senart <tomas@sourcegraph.com>

view details

Chris Pine

commit sha d1a826c0d07832607178b9b3feffe6fff20b8ab4

Updates old instructions in our development docs (#14688) * Updates old instructions in our development docs * Update doc/dev/background-information/campaigns/index.md Co-authored-by: Adam Harvey <aharvey@sourcegraph.com> * Update doc/dev/background-information/campaigns/index.md Co-authored-by: Adam Harvey <aharvey@sourcegraph.com> Co-authored-by: Adam Harvey <aharvey@sourcegraph.com>

view details

Eric Fritz

commit sha f774b7940e72b3b2213038f9a1eaa315bc171f07

chore: Fix enterprise server build (#14722)

view details

TJ Kandala

commit sha 4ace73fa18f7a7dcca4048b61a67d454e8b5f25a

web: hide arrows and borders for uncontrolled popovers (#14692)

view details

Felix Becker

commit sha e6e134559e01805245c537d034dcc84198b5fd5f

Fail integration test on missing mock (#14703) Co-authored-by: Marek <marek@sourcegraph.com> Co-authored-by: Loïc Guychard <loic@sourcegraph.com>

view details

Tomás Senart

commit sha ae88cbadfbc6f2c11d9e2eea8dac5d665438839d

usagestats: Fix bug in GetHomepagePanels (#14730) I noticed this while taking another look at the query.

view details

Marek

commit sha e3c143c0661f4748f458a6cbc93967f398cf3982

Fix RepoContainer to match spaces in repo name (#14681)

view details

davejrt

commit sha 6818c8093042c91194b5383ecc8fced2833bc33c

Update latest release to 3.21.0 (#14732)

view details

TJ Kandala

commit sha f43ef927de7dceff7c634da6153804323d8f638a

Restore Logo + link to search on sign up and sign in pages (#14727) Co-authored-by: Felix Becker <felix.b@outlook.com> Co-authored-by: Marek <marek@sourcegraph.com>

view details

Felix Becker

commit sha c9b29a7be120f8f5d7420efe525caee5d356939c

Adapt in-app messaging to native integration (#14659) Co-authored-by: TJ Kandala <kandalatj@gmail.com>

view details

TJ Kandala

commit sha 55bcd84a4bc26341137dad68e94c94c47e87ebdf

bext: make URL required in options menu (#14731)

view details

Joel Kwartler

commit sha afaca5a64319ecea6691a9a3ffd545f2da115231

Add label notifier workflow? (#14683) Added the SHA and taking Tomás's addition of himself in the yml as implicit approval, so merging in! Co-authored-by: Tomás Senart <tomas@sourcegraph.com> Co-authored-by: Loïc Guychard <loic@sourcegraph.com> Co-authored-by: Nick Snyder <nick@sourcegraph.com>

view details

Tomás Senart

commit sha 5218bbadff139ce5ba0a9143c93dd65a900ef0f8

db: Improve defaultRepos.List query (#14600) * db: Improve defaultRepos.List query This commit improves the `defaultRepos.List` query to use a better plan — it results in rougly 450ms runtime in production currently, vs the previous 1.4s Thanks @felixge for the SQL hacking session :) * fixup! More stable query * fixup! Back to square one

view details

Eric Fritz

commit sha 91659bb2bdd34057c36da0820d6f69b4b8fa51d5

codeintel: Clean up internal HTTP server setup (#14733)

view details

Stephen Gutekanst

commit sha 16b3bbfaefb7076ceaafc2c785e5fce3d793ec9c

third-party-licenses: add syntect_server licenses (#14458) This PR adds third-party licenses for syntect_server. I did not use CSV format and used multiple files because documenting/explaining all of this is a little bit cumbersome to do. The `dependencies.json` is auto-generated via [a script](https://github.com/sourcegraph/syntect_server/blob/master/gen-license-dependencies.sh) while the `syntaxes.txt` is hand-crafted and will have to be maintained as part of adding any new language syntaxes: https://github.com/slimsag/Packages#license Note: This information is only up-to-date for Sourcegraph >= v3.21, since that version of Sourcegraph [removes some syntaxes which had missing/incompatible licenses](https://github.com/sourcegraph/sourcegraph/pull/14456) Fixes #11269

view details

Chris Pine

commit sha 8107875f1789986c461870cce54f2a2f541e1a39

fix bad instructions in docs (#14735) As seen [here](https://github.com/sourcegraph/src-cli/blob/main/internal/campaigns/campaign_spec.go#L58), the field is called `repository`, not `repo`.

view details

Keegan Carruthers-Smith

commit sha b408e9fb8fac4b31fbafd2a6ed4bc17895055980

search: stream diff/commits and symbol in PoC (#14617) We stream the same interface used by our web client for commits. This is just the generic search result interface. This change originally started off trying to use a better API, but ran into two problems: 1. There is a lot of potential metadata used to create a commit result. Commit author name/time, message, etc. 2. The results we return are markdown files with highlights. Translating this from something more abstract (eg just offsetAndRange) would of been very complicated. After this work, I realised we probably want to keep a generic interface for better extensibility in the future. So commits will keep using our generic interface for now. Additionally this commit streams symbol results. Rather than embedding it into FileMatch we introduce a new type.

view details

Felix Becker

commit sha cfa4fd83d34afee1ed38a7a1d365c9a576126ae4

Ignore logspam from "Target closed." (#14747)

view details

push time in 6 days

create barnchsourcegraph/sourcegraph

branch : cf-docs-web

created branch time in 6 days

Pull request review commentsourcegraph/sourcegraph

docs: update search assets to work on dark background

 conflict with the syntax of parameters in this Sourcegraph language.                 </td>                 <td class="d"><code class="c"><a href="#commit-parameter">commit parameter</a></code></td>                 <td class="le"></td>+                </td>

I think this is an extra closing </td>

rvantonder

comment created time in 6 days

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentsourcegraph/about

blogpost: Introducing a new database for code intel

+---+title: 'Introducing a new database for Code Intelligence'+author: 'Eric Fritz'+publishDate: 2020-10-18T00:00-07:00+tags: [+  "blog"+]+slug: introducing-a-new-code-intelligence-database+heroImage: https://image.flaticon.com/icons/png/512/51/51333.png+published: true+---++With the release of 3.21, Sourcegraph will ship with a _second_ Postgres database instance, named `codeintel-db`, which we use to store the data that powers [precise code intelligence](https://docs.sourcegraph.com/code_intelligence/explanations/precise_code_intelligence).++We've [written previously](https://about.sourcegraph.com/blog/evolution-of-the-precise-code-intel-backend/) about the architectural changes we have made to the code intelligence backend. This post is yet another submission in the archaeological trail of how the code intelligence team shapes Sourcegraph on a technical level. The post explains why we chose to swap out our persistence layer - a very non-trivial difference in our architecture.++**TL;DR 1**: If you are a customer currently using precise code intelligence, [skip to the notes below](#notes-for-site-admins) to see how this could affect your instance.++**TL;DR 2**: If you are here for a daily dose of schadenfreude, read about how [we mucked this migration on our production instance](https://eric-fritz.com/articles/migrating-to-postgres/) on Sourcegraph.com.++## The impetus for a second database++A bit over a year ago, the code intelligence backend started as a single node process with access only to its own persistent volume. We chose SQLite as our persistence mechanism for a handful of reasons:++- It was the faster implementation compared to other contending designs we tried.+- Our MVP did not have access to Postgres at the time, which was owned solely by another team. Only later did we get access to Postgres to store cross-repository metadata and work queue data.+- SQLite had some nice properties such as easy data warehousing opportunities (on which we have not capitalized) and bulk deletion of expired data was straightforward. All we had to do was delete the SQLite file.++Using SQLite for this data has become an operational and feature burden for the code intelligence team.++1. We need to maintain a periodic process to reconcile the data on disk with the metadata we store in Postgres.+2. We have good instructions and tips for backup and recovery of our Postgres data store, but have never officially recommended backing up other persistent volumes.+3. We locked ourselves into a node topology which is not easily scalable. We essentially have a singleton service over a persistent volume. In order to scale this service horizontally (which would become necessary once either the amount of data or the frequency of queries increased), we would need to shard the data across multiple volumes. This throws a lot of wrenches into our plans: we need to be able to automatically move data on increase or decrease of shard counts; we need to be able to route requests to the correct node with that data; we need to ensure that reconciliation between the data on disk and the metadata we store in Postgres is aware that there are multiple nodes where data _could_ reside.+4. There is no efficient way to implement certain data access patterns we may need in the future. For example, looking for data matching a certain identifier _name_ would require us to open every SQLite database on disk (and, no, _batching it_ is not a solution).++Instead of forging ahead and tackling the complexity we've made for ourselves, we decided to take a step back and re-evaluate whether or not our previous architecture choices were meeting our current needs. And it seems like they did not.++Moving this data into Postgres seems like an obvious choice that will (eventually) be able to reduce or completely remove all of the burdens listed above.++1. Reconciling pieces of data in the same datastore is trivial compared to reconciling pieces of data in two different datastores, especially if it should be done transactionally. Even though we're not in the same _physical_ database instance, having all of our data in _some_ Postgres-compatible store opens up the possibility of transactions spanning multiple physical Postgres instances via [postgres_fdw](https://www.postgresql.org/docs/12/postgres-fdw.html#id-1.11.7.42.12).+2. Moving data to an existing technology allows us to re-use the same advice and documentation for backup and disaster recovery strategies. Removing the number of knobs that must be turned by site-admins is always going to be a win across the board.+3. Moving from an embedded database to a server-client database removes the nasty singleton property on the service. Now that multiple servers can interact with the same data concurrently without risk of corruption, we can scale the services horizontally without requiring additional effort into implementing sticky sessions or complex request routing rules.+4. Moving data into a single relational store allows us to create additional indexed views into the data. We can now query over dimensions that were not possible before without opening tends of thousands of relatively small database files.++## Notes for site admins

Let me know if you need more input on this post (I skimmed through it, and my concerns are the same that Nick mentions above - making sure the context is in the appropriate location).

efritz

comment created time in 6 days

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentsourcegraph/about

Update Code Intel roadmap

Cant seem to be able to view the code intel section in the gantt chart on my side. Is that just me?

Hmmm, yeah the preview (https://deploy-preview-1786--sourcegraph.netlify.app/handbook/product/roadmap) isn't rendering that row. @macraig were you able to get this working locally? This can happen if mermaid gets grumpy about the formatting of one of your items. Try removing/commenting out to figure out the offender.

macraig

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project
### Tracking design priorities
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 While design does adds time at the beginning of a project, it improves velocity  Our design process is documented here: **[Design process](design_process.md)** -## Working with design--Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.--You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged.- ### Figma
## Figma
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project++Design Team uses this board for managing current and future work, design debt and work requests.++Columns:++- Design debt - issues connected to design debt that haven't been scheduled yet+- **Backlog** - issues that need design work but don't have any development resources allocated and haven't been scheduled yet+- **Coming soon** - no designer assigned yet, development resources have been allocated. Add **design deadline** to the issue, if possible+- **Up next** - designer assigned, design work scheduled+- In progress - ongoing design work+- QA - design work done, designer is assisting the implementation+- Measure success - design shipped, designer is working with the bizops team to analyse the impact +- Done - success measured, all work done++### GitHub design labels++- **needs-design** - for design work requests - add to 'design priorities' project, add a deadline, if possible..+- **design** - for design-oriented issues. This label should be mostly used by designers+- **design-debt** - for issues connected to the design debt.
- **`needs-design`**: design work requests. Add to [Design priorities project](https://github.com/orgs/sourcegraph/projects/66) and if possible add a deadline.
- **`design`**: design-oriented issues. This label should be mostly used by designers
- **`design-debt`**: issues connected to design debt.
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project++Design Team uses this board for managing current and future work, design debt and work requests.++Columns:++- Design debt - issues connected to design debt that haven't been scheduled yet+- **Backlog** - issues that need design work but don't have any development resources allocated and haven't been scheduled yet+- **Coming soon** - no designer assigned yet, development resources have been allocated. Add **design deadline** to the issue, if possible+- **Up next** - designer assigned, design work scheduled+- In progress - ongoing design work+- QA - design work done, designer is assisting the implementation+- Measure success - design shipped, designer is working with the bizops team to analyse the impact +- Done - success measured, all work done++### GitHub design labels++- **needs-design** - for design work requests - add to 'design priorities' project, add a deadline, if possible..+- **design** - for design-oriented issues. This label should be mostly used by designers+- **design-debt** - for issues connected to the design debt.++### Requesting design work++If you need some design help:++- add the tag **needs-design** to your GitHub issue+- you can assign one of the designers, if you already know who will take care of the issue+- add your issue to the **[design priorities project]**(https://github.com/orgs/sourcegraph/projects/66)+- assign your issues to one of the columns - (see the 'GitHub Design Priorities project' section above for details)++Please, make it clear how urgent the issue is (adding the deadline is encouraged) and if development resources have been allocated. It is important to focus design team's attention on the work that can be implemented soon. ++Use #design Slack channel for any urgent matters or questions.
- Add the **`needs-design`** tag to your GitHub issue
- Assign one of the designers if you know who will take care of the issue
- Add your issue to the [design priorities project](https://github.com/orgs/sourcegraph/projects/66)

Please clarify the urgency of the issue (adding a known deadline is encouraged) and if development resources have been allocated. It is important to focus the design team's attention on the work that can be implemented soon. 

Use the #design Slack channel for any urgent matters or questions.
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project++Design Team uses this board for managing current and future work, design debt and work requests.++Columns:++- Design debt - issues connected to design debt that haven't been scheduled yet+- **Backlog** - issues that need design work but don't have any development resources allocated and haven't been scheduled yet+- **Coming soon** - no designer assigned yet, development resources have been allocated. Add **design deadline** to the issue, if possible+- **Up next** - designer assigned, design work scheduled+- In progress - ongoing design work+- QA - design work done, designer is assisting the implementation+- Measure success - design shipped, designer is working with the bizops team to analyse the impact 
- Measure success - design shipped, designer is working with the BizOps team to analyze the impact 
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project++Design Team uses this board for managing current and future work, design debt and work requests.++Columns:++- Design debt - issues connected to design debt that haven't been scheduled yet+- **Backlog** - issues that need design work but don't have any development resources allocated and haven't been scheduled yet+- **Coming soon** - no designer assigned yet, development resources have been allocated. Add **design deadline** to the issue, if possible+- **Up next** - designer assigned, design work scheduled+- In progress - ongoing design work+- QA - design work done, designer is assisting the implementation+- Measure success - design shipped, designer is working with the bizops team to analyse the impact +- Done - success measured, all work done
- Done - success measured, all work completed to scope
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project++Design Team uses this board for managing current and future work, design debt and work requests.++Columns:++- Design debt - issues connected to design debt that haven't been scheduled yet+- **Backlog** - issues that need design work but don't have any development resources allocated and haven't been scheduled yet+- **Coming soon** - no designer assigned yet, development resources have been allocated. Add **design deadline** to the issue, if possible+- **Up next** - designer assigned, design work scheduled+- In progress - ongoing design work
- In progress - design work actively being worked on
AlicjaSuska

comment created time in 6 days

Pull request review commentsourcegraph/about

Change 'Working with design' section

 Here are a few of the things we strive to make true:  - #design channel or @design-team on Slack +## Working with design / requesting design work++Working with design should feel fluid, you should be able to open an issue or bring up a concern in slack, and receive actionable feedback: either implementable, or a call to explore further.++You should also not feel limited to words, images (sketches, or references made by editing the broswer DOM) are also encouraged. ++### GitHub Design Priorities project++Design Team uses this board for managing current and future work, design debt and work requests.
The Design Team uses a [GitHub project board](https://github.com/orgs/sourcegraph/projects/66) for managing current and future work, design debt, and work requests.
AlicjaSuska

comment created time in 6 days

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentsourcegraph/sourcegraph

Design debt issue template

+---+name: Design debt+about: Describes the problem that needs attention because of design debt +title: ''+labels: 'design-deb'
labels: 'design-debt'
AlicjaSuska

comment created time in 6 days

PullRequestReviewEvent
PullRequestReviewEvent

PR opened evildmp/documentation-system

Add Sourcegraph to Divio adoption

We are actively working on converting our documentation to the Divio system. We've started by updating the hierarchy of all our docs, and are actively working on continued improvement.

Thank you so much for sharing this system!

+1 -0

0 comment

1 changed file

pr created time in 8 days

push eventchristinaforney/documentation-system

Christina Forney

commit sha 119c747f3b949288576a811df6fdd16b95125963

Add Sourcegraph to Divio adoption

view details

push time in 8 days

push eventsourcegraph/sourcegraph

Christina Forney

commit sha e4958b671babc04d515ab4dda52d0a6b4f1ab1c7

Elevate product areas in documentation (#14792)

view details

push time in 8 days

delete branch sourcegraph/sourcegraph

delete branch : cf-docs-elevate

delete time in 8 days

PR merged sourcegraph/sourcegraph

Elevate product areas in documentation

Elevating product features in the left nav (and moving docs directories to match).

Looks like this:

image

If you look at commits, first you can see the renames, then the updates too all the links separated by product area. Tagging one person from each team to verify the links for their area.

There is now a "Getting started area" that is still the same document from "Usage" and includes the tour. I will be improving these docs content ASAP.

Note: search had to be renamed to code_search because of the overlap with the docs search functionality.

+144 -99

2 comments

111 changed files

christinaforney

pr closed time in 8 days

push eventsourcegraph/about

Eric Brody-Moore

commit sha 56a2ad2c48f9551cd788df3fae241bfcfdf3ad43

Update company_meeting.md Update owners and bullets to reflect company meeting today

view details

AlicjaSuska

commit sha 6726e66a88c5f39105ba54a1e903677e4c58bf51

Add Quinn and Alicja to the interview process (#1599)

view details

aileenrose

commit sha eba039fc11a467bcab5135a19527d2270ede44cc

More news on big code survey (#1732)

view details

aileenrose

commit sha 5746b2dc3873a70ebd38ec16f861bbdcdb7a6bf5

More coverage of big code survey (#1739)

view details

Gonzalo Peci

commit sha 8118bdb72cd41d62fe2629a0de9cf4c322d2e723

Update distribution team to include Dax (#1744) This also contains a formatting fix of indentation from 4s to 2s

view details

Joel Kwartler

commit sha 01536b3fd52fc2dfb410da3f0b40fd76a4547d2d

adding events calendar (#1745) Couldn't find this documented anywhere. Still not ideal but can't seem to find the equivalent "join link" for the events calendar that we use for the social calendar and this works functionally.

view details

juliasourceress

commit sha 703eb5b16cd67f3d719e10e8deac55f4f97e873a

Bring up to date with some recent CE changes.

view details

juliasourceress

commit sha a80edcbb59fdf6de48a49d8b0db1a3d85d953295

Adding Head of Customer Support role/link

view details

juliasourceress

commit sha 40255bdb886fe5230620c557b5d3622ba45139d7

Link fix

view details

juliasourceress

commit sha aa6ed524a731b329e7a15bbe13f303b15db8cc97

Fixed individual team members links

view details

Renovate Bot

commit sha 185848b8937250091344b988168c755dc06afd6c

Update dependency @sourcegraph/eslint-config to ^0.20.9

view details

Rijnard van Tonder

commit sha 66781736142cc53ae03a0f871e88e4124f1cd69b

Update iteration_log.md

view details

Gonzalo Peci

commit sha 778ea737b137cf77abc0f2c475dd6fffb8c35dc6

Add to gcp/projects information (#1718)

view details

Robert Lin

commit sha ead7fe2b0cb5faa6b9026c2ebe3ccb0019469952

playbooks: add tip on pod failures, group general tips together (#1737) * add tip on pod failures * group general tips together, reorder playbook section, consolidate kubectl tips

view details

Robert Lin

commit sha feebc6b825e3bafe1f6a28ea59395c11b741f546

release: align steps with new command names (#1749)

view details

Beyang Liu

commit sha ceb61fdb53613efc332c18cf44093d9dd6730a04

podcast: clean up ep 12 transcript

view details

Beyang Liu

commit sha c8baf27d7a58f68f6149db0a1f92004baaf17ce6

podcast: publish ep 12

view details

Beyang Liu

commit sha 34a18b7aa2863f11092fe576b69649929e23c68e

Revert "podcast: publish ep 12" This reverts commit c8baf27d7a58f68f6149db0a1f92004baaf17ce6.

view details

Chris Pine

commit sha 6f255118d51019840781f4f24e15eaec82d56783

move team goals into handbook (#1743)

view details

Robert Lin

commit sha 344e7aabdb47f9d341cd64af0410f074ad202f77

release: allow pull requests to be release blockers (#1751)

view details

push time in 10 days

push eventsourcegraph/about

Christina Forney

commit sha ba786dcab47d457a53f9ed75f51527872ee0cfc9

Order the values in detail to match top level value order

view details

push time in 10 days

push eventsourcegraph/sourcegraph

Christina Forney

commit sha 435abe79d503ed0c933a9caa269374d496dbdd41

Fixing whitespace in snapshot file

view details

push time in 10 days

Pull request review commentsourcegraph/sourcegraph

Elevate product areas in documentation

 exports[`CampaignsDotComPage renders 1`] = `         title={           <React.Fragment>             Campaigns-             +

Nvm. It was grumpy (hidden because of flaky failure).

christinaforney

comment created time in 10 days

PullRequestReviewEvent

delete branch sourcegraph/about

delete branch : cf/values

delete time in 10 days

push eventsourcegraph/about

Christina Forney

commit sha 29b0c0a7a3101debc90fa53ff8fcaa023f94bcca

Updating company values (#1738)

view details

push time in 10 days

PR merged sourcegraph/about

Reviewers
Updating company values

@nicksnyder and I felt that there was a gap in our values that would help with hiring decisions, growth conversations, process decisions, and more. We also felt that a short, clear list of values would help more clearly communicate the values in a way that can be digested and remembered. The details are valuable for clarifying the shorter list and adding more color to what this means to us but isn't necessary for communicating the high level understanding of values.

The newly added values have empty sub-sections and TO DOs. I propose we merge as is, and can follow up with additional explanations.

Specifically, we have tweaked two of the existing values:

  • 'We not I' -> 'Work as a team'
  • ~'High quality' -> 'Be iterative' - this was sending the wrong message (as indicated by the need to clarify in company meeting). Instead, what we value is being iterative to creating value of high quality work.~ This still needs more work, reverting back to high quality here to move the PR forward and open up a follow up PR to clarify.
+30 -8

10 comments

1 changed file

christinaforney

pr closed time in 10 days

Pull request review commentsourcegraph/sourcegraph

Elevate product areas in documentation

 exports[`CampaignsDotComPage renders 1`] = `         title={           <React.Fragment>             Campaigns-             +

Seems to be failing for a different reason. Doesn't seem to mind the whitespace.

christinaforney

comment created time in 10 days

PullRequestReviewEvent

Pull request review commentsourcegraph/sourcegraph

Elevate product areas in documentation

 exports[`CampaignsDotComPage renders 1`] = `         title={           <React.Fragment>             Campaigns-             +

Sorry about the whitespace changes to this file - this got autosaved. Should I revert them?

christinaforney

comment created time in 11 days

PullRequestReviewEvent

push eventsourcegraph/sourcegraph

Christina Forney

commit sha dbd963a9903de189e8d6c34fa65e8ef9799f3dc0

Fixing typo

view details

push time in 11 days

PR opened sourcegraph/sourcegraph

Reviewers
Cf docs elevate

Elevating product features in the left nav (and moving docs directories to match).

Looks like this:

image

If you look at commits, first you can see the renames, then the updates too all the links separated by product area. Tagging one person from each team to verify the links for their area.

There is now a "Getting started area" that is still the same document from "Usage" and includes the tour. I will be improving these docs content ASAP.

Note: search had to be renamed to code_search because of the overlap with the docs search functionality.

+149 -104

0 comment

111 changed files

pr created time in 11 days

create barnchsourcegraph/sourcegraph

branch : cf-docs-elevate

created branch time in 11 days

pull request commentsourcegraph/sourcegraph

Change "later" to "another time"

"Another time" isn't clear either. Can we be more precise? E.g. "remind me on my next visit" or "Remind me in X days" or something like that? What will their experience be?

felixfbecker

comment created time in 11 days

more