tfjaeckel

Thank you!

Thanks for adding more color to your original answer.

I like you enforce the commit/ticket relationship. Is this purely an agreed process or do you use other measures to keep things consistent? E.g. we typically add the ticket ref to each commit but at times that gets omitted.

Also, I think that (internal) release tool is something crucial as the team grows. Will check shipit a bit further.

Would you mind expanding a bit on the things you enforce for each of your releases?

I think Slack notifications are really nice to see what's going on right now but not so great to see the state of dozens of service, i.e. what version is deployed to what environment.

Then there is the issue of linking the Git release/tag with the corresponding changes, say from a ticketing system such as Jira. That can be helpful to communicate changes to other people within the organization and to users.

How do you define dependencies for releasing new versions to service? Likely going to happen at some point when you have non-trivial changes to services.

Step Functions are convenient but for the reason you stated we stopped using them. Pricing seems off for what they do, especially when it's in volume.

It's great feedback, definitely more food for thought. Thank you! It's a fine line between cutting features vs. trying to solve too many things at once.

Our current approach to the collaboration part can be seen when you link a Google Drive account. When you want to edit a Google Doc it takes you right there, no need for the GDrive UI. You can actually create a Google Doc from within Shelf.

Also, "good" to hear what you wanted to know but didn't learn immediately from the website. We'll surely be working on making the use cases and functionalities more clear.

All good. That's not really the use case for Shelf. You'd publish final versions of deliverables on Shelf, not necessarily your whole work-in-progress.

Just to share a different perspective, not even to disagree with your view: Think of a marketing team that wants to publish and share presentations to be used by sales reps. Or a team of researchers that wants to curate different types of information (docs, links, videos) for later perusal. Enrich each of those with meta data. These are different use cases, that's where Shelf shines.

Enterpriseready is a good site, agreed. I'll also check Replicated to see how you support on-prem and would gladly take your offer to hear more about your learnings.

Got it. I first thought you wanted that content to disappear altogether. Thanks for clarifying.

Data is secured at rest and in transmission. We take every measure available in Elastic to secure the search indexes themselves.

Thanks for sharing your thoughts on this topic. It's a challenge for all SaaS products I believe but yes, the more business critical the product the more important to address.

Apart from self-host and open source, do you have other suggestions on how to address this on a product level? Would you feel comfortable with structured exports for example?

May I ask what makes Confluence look more professional from your perspective?

Like I mentioned somewhere else, I actually like using Confluence depending on the use case. It tends to require much more attention in making sure things stay organized and well structured. Shelf has this built-in by being more opinionated (for better or worse, depending on what you need).

Thanks for that perspective. Put on the list. Won't let them keep us from making money along the journey.

Thanks! Fixed. :)

Thanks for taking time to try out Shelf! And for providing your feedback as well.

Tags: delimiters are [comma], [enter] and [tab]. 50 tags are the max. 30 characters are the max. We'll see how we can make tagging a better experience. Including suggested tags based on content/previous behavior.

Can you explain what you mean exactly by: expiration on items?

Thanks Jedd for your kind words! We have a great Team that made this happen and is working hard to keep making Shelf better every day. And help cure that pain you share. :)

My use of 'cloud' wasn't very exact, you're right. I suppose most enterprises have or will have their 'own' infrastructure in the cloud and manage it there themselves. I really meant cloud in the way of a SaaS-model.