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

Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

news.ycombinator.com

Post reply on HN
Print view View original

41–50 of 88 posts

Re: Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

#43

Post by ldd »

Does this include typescript projects? i couldn't find my own.[0]

Also, I can see my two most popular packages ( 40 stars[1] and 14[2] respectively), and I've realized that not updating them frequently probably hurts.

The thing is, what about bots like dependabot? I have one or two other packages that auto update and close issues quickly because they have some bots helping out, and I was wondering if you took that into account.

I am also sad that things that I worry about, like testing, and bundle size are nowhere to be found.

But overall, great idea. Keep at it!

[0]:https://github.com/ldd/vscode-jq/

[1]:https://openbase.io/js/gatsby-source-github-api

[2]:https://openbase.io/js/react-tech-tree

Re: Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

#44

Post by liorgrossman »

sdesol wrote: post #34
liorgrossman wrote: post #31

Earlier quoted context omitted.

Thank you for sharing this! As you mentioned, we're focused on the discovery part, and package insights is a part of that, but so are reviews, ratings, search, and categorization. Your tool looks like a great solution for software teams to get insights into their code and dev processes, this also connects with the "developer velocity" trend I've heard several times in recent years. Looks like quite a lot of work too,…

> Looks like quite a lot of work too, kudos! Thanks. I don't think people realize how complex it is to generate actionable code insights. Indexing code is easy, indexing history is an order of a magnitude more difficult, in my opinion. > Is it in production with some customers? No, the product isn't finished yet (I pivoted a bit from my initial idea). My goal is to have it ready by the end of this month, so that I ca…

Yeah, it is pretty darn complicated!

A couple of things that helped us with the rate limits are: * Limiting most of our graphs/reporting to the past 3 years (some repos are pretty old) * Fetching the data incrementally - namely, the first fetch is kinda of large, but then we're only trying to get the minimal set of changes/detla to a repo on a regular basis!

That sounds awesome, I can't wait to see the product when it goes live!

Re: Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

#46

Post by liorgrossman »

ldd wrote: post #43

Does this include typescript projects? i couldn't find my own.[0] Also, I can see my two most popular packages ( 40 stars[1] and 14[2] respectively), and I've realized that not updating them frequently probably hurts. The thing is, what about bots like dependabot? I have one or two other packages that auto update and close issues quickly because they have some bots helping out, and I was wondering if you took that in…

Thanks!

We currently only cover npm packages (not all GitHub repos), does vscode-jq have an npm package?

We currently don't have any special handling for bots, but this is on the pipeline. Same goes for consolidating contributors (sometimes the same person shows up as 2 different GitHub users, you can see that on GitHub too).

Bundle size is a big one for us, highly prioritized.

Testing isn't, though, what would you like to see about testing that isn't covered by badges? (e.g. test coverage, passing/failing, etc.)

Re: Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

#48

Post by sdesol »

liorgrossman wrote: post #44
sdesol wrote: post #34

Earlier quoted context omitted.

> Looks like quite a lot of work too, kudos! Thanks. I don't think people realize how complex it is to generate actionable code insights. Indexing code is easy, indexing history is an order of a magnitude more difficult, in my opinion. > Is it in production with some customers? No, the product isn't finished yet (I pivoted a bit from my initial idea). My goal is to have it ready by the end of this month, so that I ca…

Yeah, it is pretty darn complicated! A couple of things that helped us with the rate limits are: * Limiting most of our graphs/reporting to the past 3 years (some repos are pretty old) * Fetching the data incrementally - namely, the first fetch is kinda of large, but then we're only trying to get the minimal set of changes/detla to a repo on a regular basis! That sounds awesome, I can't wait to see the product when i…

> Limiting most of our graphs/reporting to the past 3 years (some repos are pretty old) *

I really need the entire history, so limiting time ranges isn't possible. The biggest issue is really with cloning/fetching, since GitHub doesn't like people synching thousands of repos on a daily basis. Outside of those things, my search and analytics engine doesn't really need GitHub, since GitHub is unable to provide the data that I need anyways.

I talked about it before, but what I'm really doing is moving Git's history into SQL (postgres in my case) and Lucene, so that I can slice and dice its history, to surface developer insights. Hence me calling it "business intelligence" for your codes history.

>That sounds awesome, I can't wait to see the product when it goes live!

Thanks and I think your product has potential as well and you should look at the Enterprise angle. Discovery in large companies is actually a serious problem. Companies really need a single place that they can go to, to see all that is available.

GitHub, with their "Discuss" feature gets you part of the way, but companies still need a centralized place that can help them easily discover/discuss what is available internally.

Re: Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

#49

Post by jacques_chester »

liorgrossman wrote: post #37
lend000 wrote: post #28

Earlier quoted context omitted.

Why not charge the maintainers themselves to advertise validation by your brand (once you have established that trusted brand)? I mean, I see that you are attacking this problem from the analysis and search perspective, which is great and well needed, but there is an intersecting need for security validation and preventing malicious package updates. There is more liability that way, but imo there is greater incentive…

That's a really interesting thought, we've never thought of this direction! Are there any successful products/companies with such business model (providing testing and certificates for money)

I think the reference examples would be certificate authorities, ratings agencies, Underwriters Laboratories, ISO9000 or SCAMPI inspectors/auditors, organic/kosher/halal/GMO-free food stamp companies etc.

Selling quality marks can be quite lucrative, but you'd definitely need to think about exactly what people buy. And definitely think hard about deep insurance.

Re: Launch HN: Openbase (YC S20) – reviews and insights for open-source packages

#50

Post by asutekku »

neximo64 wrote: post #47

Nice, now we can review someone's open source contributions they usually worked for free on.

Just because someone worked free on something does not mean it’s suddenly free of criticism. I’d say it’s healthy to criticize even these projects.
Post reply on HN