wadenick

Joined 14 years ago

Karma

Submissions

Member since

Dec 7

Recent submissions

...agree, even spending time singing on anything else in the first paragraph instead of breaking the bad news WITH THE DATE first feels rather off.

Comment · 1 year ago

I really think any help the community could offer - and also receive - would be welcome news for those still on Fauna service right now. Especially open source. People could move quickly – with multiple options – to help themselves, which after all is the only thing Fauna the co is able to offer anyway. Like the other commenter said, if you do release it open source please post on Hacker News and maybe Reddit and we'll all try to help boost it.

Comment · 1 year ago

yes, or even just be able to stand up your own for a longer period while you figure out how to migrate to something else altogether.

Comment · 1 year ago

This is a very tough announcement for any customers relying on the Fauna service. The announcement itself hides the all key details, clicking into the FAQ reveals the date is not several months away but in fact 2 months 11 days away, and there is no FaunaDB open source release to start saving your own ass today.

> we have made the hard decision to sunset the Fauna service over the next several months. clicks into the FAQ vs > Fauna service will be ending on May 30, 2025.

Comment · 6 years ago

+1, works well for me

Comment · 7 years ago

Nick from DigitalOcean here; yes! It's in the bottom of the blog post

>>> Our engineering team is working hard to bring you even more functionality for your databases in 2019. We plan to have additional engines such as Redis and MySQL, private networking with enhanced VPC, metrics, and alerting through Insights.

Comment · 8 years ago

Hey, Nick from DigitalOcean here. We're working on upgrade functionality, and it should be available soon. Here's our K8s PM on this topic in the blog comments https://blog.digitalocean.com/announcing-limited-availabilit...

As for test user feedback I'll leave that to others.

Comment · 9 years ago

Thanks for noticing! JIRA Jr. is indeed an April 1st thing we did 2013. Notice the first date that the Internet Archive captured the page: https://web.archive.org/web/20130215000000*/https://www.atla...

Interestingly enough we did in fact have that swag, and we sold quite a number. Both my kids had JIRA Jr onesies. Fun times :)

Comment · 10 years ago

The first article I read made it clear he was doing 114 hours a week: http://www.nbcbayarea.com/news/local/BART-Janitor-Made-270K-...

The headline figure includes his benefits in order to seem worse in some way. Wages were around $230K.

Reality is 114 hours of work every week makes for a dismal sort of life for most people. Perhaps this is a case of Chinese work ethic plus pension spiking?

Comment · 10 years ago

Sorry I'm late here. Yes those are different, given the differences between the software running in the cloud and running on customers' own servers.

Comment · 10 years ago

Also note you're on an old version of JIRA so check that you're reading the related version of the API references.

Comment · 10 years ago

This developer is asking about developing for JIRA Server though, so I pointed them straight at that content. Connect is great for JIRA Cloud.

Comment · 10 years ago

So you're going to develop something for JIRA Server (internally hosted software). You'll be using Plugins2*

1. Start here https://developer.atlassian.com/jiradev/getting-started/gett...

2. Install the SDK (it has some pre-reqs) and build Hello World https://developer.atlassian.com/docs/getting-started/set-up-...

3. Bone up on Plugins2 a bit more https://developer.atlassian.com/jiradev/jira-platform/buildi...

4. API Reference https://developer.atlassian.com/jiradev/jira-apis (I recommend the REST APIs + Webhooks wherever possible).

I'm really keen to talk with you about your experience going through that - there's a lot of history and we're aware we need to clean up the journey.

_* If you were developing for JIRA Cloud you'd be using Atlassian Connect.

Comment · 10 years ago

Something I totally forgot to mention, which was remiss of me, is that the platform I'm talking about is also where developers who have their own product - SaaS or otherwise - can also distribute free integrations to our products. Loads of them do that and successfully bolster their own value within any joint customers we share a bit more too.

Comment · 10 years ago

I guess it's relative. Our market isn't the number of users of a consumer market like the Apple App Store or Google Play. But then again there's millions of apps in each and getting yours noticed is extremely hard.

Part of what we're trying to do for our devs is grow it steadily year by year, and small developers are able to grow along with us (often faster as they first gain new customers). You may not know this but there's more than 60,000 organizations with anywhere from 10 to thousands of users in our customer base. There's a whole lot more startups with 1 to 9 folks too. They've collectively bought a few hundred thousand licenses of our ecosystem developers products so far since we launched.

I'd also counter that we're fairly open about what you can build. We work hard to have supported, public, documented APIs and patterns, but within that you can pretty much build anything you want. Candidly you probably don't want to build something directly in competition with Atlassian but there's lot of value to add around what we do. Last thing we released publicly on this was a while ago - I'm working on another release because our devs are much further along at this point but here you go https://techcrunch.com/2015/12/15/atlassians-marketplace-for...