Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sourcegraph is now open source

about.sourcegraph.com

Post reply on HN
Print view View original

81–90 of 95 posts

Re: Sourcegraph is now open source

#81

Post by sqs »

Dowwie wrote: post #60

Know those cool features in your editor that allow you to hover over source and get more detail on what you are looking at? Also, know that feature in an editor that lets you go to definition? Imagine this and not within your editor but rather your browser, whatever host you choose, such as GitHub or GitLab. Sourcegraph enables this feature with browser extensions.

Sourcegraph CEO here. This is a great way to describe how Sourcegraph integrates with your code host. I love it. :)

Links to save you from searching:

https://chrome.google.com/webstore/detail/sourcegraph/dgjhfo...

https://addons.mozilla.org/en-US/firefox/addon/sourcegraph/

Re: Sourcegraph is now open source

#82

Post by felixfbecker »

mikepurvis wrote: post #74
sytse wrote: post #72

Earlier quoted context omitted.

Yes, for sure there is a need now. We can do either a plug-in or just integrate Sourcegraph directly into GitLab.

It would be great to do it via a generic plugin interface, if possible.

Sourcegraph engineer here - that's the goal of the Sourcegraph extension API, being generic and code-host agnostic. One Sourcegraph extension can provide the same features on any code host (Gitlab, GitHub, Bitbucket, ...)

Re: Sourcegraph is now open source

#83

Post by marcinkuzminski »

sqs wrote: post #79
mikepurvis wrote: post #63

Earlier quoted context omitted.

It's too bad that a browser extension is required to make this work. I've asked previously for GitLab to provide the necessary hooks so that any plugin could offer this type of functionality in a first class way, and was told that the proposal lacked a "concrete first need". I suppose SourceGraph has now demonstrated the usefulness of such a thing, which is great! Ref: https://gitlab.com/gitlab-org/gitlab-ce/issues/3…

Yes, we would love to integrate Sourcegraph into all code hosts directly and not require users to install a browser extension. Please provide the same feedback to other code hosts you use (GitHub, Bitbucket, Phabricator, etc.) as well and link to this thread. :)

How is the process for that? I'd like to get that integrated into RhodeCode as well.

Re: Sourcegraph is now open source

#84

Post by ijsnow »

sytse wrote: post #39
sqs wrote: post #3

Sourcegraph CEO here. We're back to work on testing release candidates for Sourcegraph 2.12, coming out this week. I'm especially excited about a few big new features that fit really nicely into the code search and browsing workflows people use Sourcegraph for: - https://github.com/sourcegraph/about/blob/master/projects/ex... - https://github.com/sourcegraph/about/blob/master/projects/so... - https://about.sourcegrap…

Thanks for creating Sourcegraph for GitLab https://github.com/sourcegraph/about/blob/master/projects/so... we really appreciate it. Every single developer that used Sourcegraph and talked to me about it loved the product. I think that every code product must have intelligent navigation. I saw you already responded to my tweet in https://twitter.com/sqs/status/1046986755919024129 We're looking forward to add Sourcegra…

Hey, I worked on the GitLab support. I'm glad developers are liking it so far!

Thanks for building a great product with clean APIs and user interfaces that are easy to integrate with!

Re: Sourcegraph is now open source

#85

Post by ijsnow »

marcinkuzminski wrote: post #83
sqs wrote: post #79

Earlier quoted context omitted.

Yes, we would love to integrate Sourcegraph into all code hosts directly and not require users to install a browser extension. Please provide the same feedback to other code hosts you use (GitHub, Bitbucket, Phabricator, etc.) as well and link to this thread. :)

How is the process for that? I'd like to get that integrated into RhodeCode as well.

Hey! Sourcegrapher who works on the browser extension and other integrations here.

The road to complete integration in a product is a bit longer as it takes collaboration if the product isn't open source. This is what we'd like in every product we integrate with.

However, I just did quite a bit of refactoring to make it easier and more straight forward to add support for new code hosts to the browser extension.

If you want to add support, we'd gladly accept a PR!

Always feel free to reach out and ask questions. Check out how it's done on GitHub, GitLab and Phabricator here: https://sourcegraph.com/search?q=repo:graph%5C/browser-exten...

Re: Sourcegraph is now open source

#86

Post by marcinkuzminski »

ijsnow wrote: post #85
marcinkuzminski wrote: post #83

Earlier quoted context omitted.

How is the process for that? I'd like to get that integrated into RhodeCode as well.

Hey! Sourcegrapher who works on the browser extension and other integrations here. The road to complete integration in a product is a bit longer as it takes collaboration if the product isn't open source. This is what we'd like in every product we integrate with. However, I just did quite a bit of refactoring to make it easier and more straight forward to add support for new code hosts to the browser extension. If yo…

Thanks for your answer. Our product is actually also open-core. And the source is here: https://code.rhodecode.com/rhodecode-enterprise-ce

In this case, what's the best process to start, should we open an issue, or send support email?

Cheers

Re: Sourcegraph is now open source

#87

Post by ijsnow »

marcinkuzminski wrote: post #86
ijsnow wrote: post #85

Earlier quoted context omitted.

Hey! Sourcegrapher who works on the browser extension and other integrations here. The road to complete integration in a product is a bit longer as it takes collaboration if the product isn't open source. This is what we'd like in every product we integrate with. However, I just did quite a bit of refactoring to make it easier and more straight forward to add support for new code hosts to the browser extension. If yo…

Thanks for your answer. Our product is actually also open-core. And the source is here: https://code.rhodecode.com/rhodecode-enterprise-ce In this case, what's the best process to start, should we open an issue, or send support email? Cheers

In that case, let's build it right in to RhodeCode!

A good place to start would be opening an issue on your product's issue tracker and start discussing requirements there.

Re: Sourcegraph is now open source

#88

Post by mikekchar »

xorcist wrote: post #61
mikekchar wrote: post #32

Earlier quoted context omitted.

I tend to agree, although I probably wouldn't state it in exactly the way you have. Open core's main goal is to sell proprietary software using the open source version as a loss leader. Having said that, I think there are some companies/individuals who truly believe that open core is a good way of funding free software development. I have even heard Bruce Parens claim that dual licensing is practically the only reaso…

"Open core" and dual licensing are two completely separate business models. They should not be conflated. Open core business models depends on selling non-free software. Normally all or nearly all development is done by a singular company. The core software could probably just as easily have been free-of-charge, and everything else would have been completely identical. (But on the other hand, if you're not making mon…

As a business model dual licensing means having a free software license (which may or may not be copy-left) and a proprietary software license. Having 2 or more free software licenses is not a business model, even if it is handy for letting people get around the GPL. There is no reason to pay for the second free software license. Otherwise you could just use MIT or the equivalent and be rolling in money. Obviously it doesn't work that way. Pedantically, "dual licensing" means to have 2 licenses. Companies are willing to pay for the proprietary software license because they want to use that code with their own proprietary code.

The only potential difference between that and "open core" is that open core generally talks about applications. Dual licensing a library allows people to use that library in proprietary software. But let's not kid ourselves -- that library is proprietary. That's the whole point.

Can you point to a project with dual licencing where all or nearly all of the development is not done by a singular company. This is rare (if it even happens at all), because you need to have copyright assignment in order to relicense the software under the proprietary license. Any other changes essentially causes a fork in the free vs. proprietary version. This is precisely the same reason why open core and other dual licensed projects tend to be controlled by a single entity. Unless you fork, there is no way to contribute without having to go through the controlling entity.

Potentially, you have in mind that many dual licensed libraries do not offer more features in the proprietary version as compared to the free version. With open core applications, where the license is less important (or not important) to the customer, you need to add different functionality to get them to buy the proprietary version. So I'll grant you that.

I'm not aware of any common difference in terminology usage. Open core is dual licensing. The fact that applications tend to diverge between then free and proprietary versions is due to the fact that nobody wants to link it to another application -- they just want to use it. In order to get people to pay for the proprietary version you need to add more features. But that's not a difference in strategy, it's just a reality of the thing you are selling. Libraries usually don't bother making different feature sets because there is no need -- people are willing to pay for the proprietary version without the extra work.

Re: Sourcegraph is now open source

#89

Post by tmerr »

keegancsmith wrote: post #54
tmerr wrote: post #42

Earlier quoted context omitted.

Some comparisons based on my reading so far: Adding a language: Kythe: a language implementation provides some structured graph SourceGraph: a language implementation is an LSP server Backend logic: Kythe: has common logic for querying for relationships SourceGraph: simply proxies LSP requests through to the appropriate language server. Terminology: Kythe: An indexer is a language implementation SourceGraph: The inde…

We (I work at Sourcegraph) actually started off with a similar model to kythe: https://srclib.org/ This project existed before kythe was published, but was based on the ideas talked about pre-dating kythe. If I remember correctly Steve Yegge had some blogpost about solving the MxN problem, which turned into him doing grok at Google. We ended up switching away from that model for a few reasons: - At the time it was ve…

Thanks for the clarification. The approach makes sense. I am actually impressed by the lack of NIH syndrome, it is rare to see open source software integrated so effectively. That is a +1 for protocol standardization

Re: Sourcegraph is now open source

#90

Post by wholien »

slimsag wrote: post #56
frou_dh wrote: post #51

I remember Sourcegraph as being a sort of sidecar to your text editor. Based on your caret position, it would automatically show you crawled examples of how other people use the functions/classes you are dealing with. Has that been de-emphasised or gone away?

I think you might be confusing Sourcegraph with Kite[1] (zero relation with Sourcegraph). Kite tries to do something like what you are describing. With Sourcegraph, we have editor plugins for various editors[2] but they only perform "Open current file on Sourcegraph" and "Search selection on Sourcegraph" actions, nothing like what you are describing yet. [1] https://kite.com/ [2] https://about.sourcegraph.com/docs/in…

It might have been what I worked on at my internship at SG; demo here: https://vimeo.com/164809163

It makes sense not to make this a big part of SG though, since latency is a huge issue and detracts from the rest of the product which is amazing!

Post reply on HN