In light of the Moq... situation... an @getsdkbin update - we're rewriting our "NuGet meets AppStore" platform from scratch in order to fulfill our mission. Details: aaronstannard.com/sdkbin-rew…
In light of the Moq stuff, maybe now is a good time to put this in public: we haven't shared much about @getsdkbin (NuGet meets App Store) recently. I'll address that briefly here and longer subsequent blog post:
1. It's been a commercial success for us.
2. Is implemented extremely poorly - I didn't write any of the code (other than our Pulumi bits) but it's my biggest failure ever as an engineering manager. Have already promised to do a live "post-mortem" stream on that.
3. We've prioritized other projects over the past couple of years - but recently we've decided we want to change how Phobos is licensed and distributed (make it easier to do trials / use for free under various revenue thresholds) and we can't do that with Sdkbin's current limitations.
4. We're re-writing it - spent a month trying to rescue the existing implementation earlier this year and decided that it's beyond saving it.
5. I'm personally leading the re-write effort and it'll be done with all of the lessons we've learned about the business realities of Sdkbin - i.e. how to deal with complex issues like 100% of your previous contacts with a B2B customer all leaving and needing to replace them with the same tenant / license id.
6. We're getting back on-track with supporting third party publishers - we opted not to do that with the previous implementation given the inflexibilities and tech debt required to fix it.
7. Probably won't happen this year, but we're adding support for selling support plans through Sdkbin. We need it for our own use cases.
Supporting OSS really requires creating a business - we're trying to lower the logistical overhead of doing that. This is my passion and my mission and why I've spent nearly 10 years working full-time in .NET OSS.
I really hope @Aaronontheweb can/will launch GetSdkBin as planned.
If he could take the friction aways from hobby OSS maintainers to become a “company” - that would be great.
Phobos 2.0-beta1 is now live on @getsdkbin !
In this release we have migrated all Phobos 1.x functionality to @opentelemetry - all functions pass our test suite and the performance is comparable to 1,x,
Release Notes: phobos.petabridge.com/articl…
Live on @getsdkbin - Phobos 1.4.0 is now released with two major new features
- All actor lifecycle behavior: PreStart, PostStop, Pre/PostRestart is now traced by default.
- Akka.Persistence recoveries + persist operations are now traceable end to end through all implementations
Just released: Phobos v1.2.1 - we've made some major improvements to actor tracing and have upgraded to @AkkaDotNET v1.4.23.
You can read the full release notes at sdkbin.com/publisher/petabri…@getsdkbin
I'm streaming on Twitch tonight at 7pm CDT (~1 hr from now)
twitch.tv/stannardian
Going to:
- Build @getsdkbin DDD/ES protocol design and state modeling
- Begin integrating a second domain with the first (part of the design validation process)
- Wonder why I didn't use F#
Going live tonight on twitch at 7pm CDT (~1hr, 15 minutes from now) twitch.tv/stannardian
I'm going to work live on the code for @getsdkbin v2.0 which at the moment involves: event sourcing a bunch of immutable C# domain events and models types using @AkkaDotNET
Finally have a Twitch schedule up: twitch.tv/stannardian/schedu…
7pm - 9pm CDT on Tuesdays / Thursdays
_Tonight_, I'm going to discuss:
- Developer salaries - from both sides of the table
- BabelJS and OSS funding in general
- OSS cost drivers and why they matter
All this code though is actually my first _closed source_ library - I'm planning to sell access to it for various text processing needs (stripping function words, stemming support, sentiment analysis, tokenization) when @getsdkbin is available.
The "multi-tenancy model" that you described sounds awesome. Years ago, I was a dev in a large org which only got larger after an acquisition. It was hard enough to understand what we already had licenses for!
Imagining being able to go to a portal and track this is very cool. 👍
We are publishing our back-catalog of earlier Phobos releases to @getsdkbin today to help support some of our users who've been running versions of Phobos < 1.0
phobos.petabridge.com/
And you can see the releases here:
sdkbin.com/publisher/petabri…
Phobos is the first product being sold through @getsdkbin and we've been selling more and more through the platform since we launched on September 30th! sdkbin.com/publisher/petabri…
Now live on @getsdkbin - Phobos v1.0.3
sdkbin.com/publisher/petabri…
TL;DR; - added proper @datadoghq tracing support by making it possible to inject the ActorScopeManager for better actor correlation
The more I think and talk with others about OSS, the more I'm starting to believe what @Aaronontheweb has been saying all along. Sustainable OSS projects are a business.
Here's an example of what selling a product on the Sdkbin marketplace looks like: sdkbin.com/publisher/petabri…
A lot of the same information you'd get from @nuget - but for proprietary packages that you can't access directly without a paid subscription
Two days until launch and @petabridge starts onboarding its own customers onto the platform.
We've made a ton of progress, have been using our product to build itself for weeks, and already have a big list of post-launch developer features we're preparing.
It'll be a good while longer before we begin onboarding third party publishers - we want to make sure the experience meets our (@petabridge) own standards and ours customers' and that takes time
But that being said, the marketplace we've built thus far will make it easier than ever to automate your sales, fulfillment, subscription management, and it will make it easy for your customers to manage who has access to the licenses they purchase within their organization