You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My dear Community,
I am product owner of Atlas bot for Hangouts Chat:
@Atlas supports Bitbucket both server and cloud version. It can notify you about builds, branch changes, new comments and more.
Developing and maintaining a bot is a very refreshing and challenging task and we would like to push it further. This is why I would like to ask you all about next steps on our bot's roadmap and overall shape of our product. I am using a "product" word because, eventually, we will introduce paid subscriptions for @Atlas in some way or another.
Our bot currently serves more than 2k of messages per day and we are already reducing our costs of maintenance by automating all the toolchain we use to produce and maintaining it (hey @Bitbucket thanks for your pipeline tool!).
We have logged several big changes on the roadmap currently and we are struggling to know whether we have taken a good direction. Please share your thoughts on the following items:
I would like to know your opinion on the matter of paid subscriptions for such bot. In our vision we are rather pursuing model in which we gather small payments but for the big as possible customer base. Currently we are exploring possibilities to charge each product @Atlas can integrate with separately to allow customers choose what they want to use.
Having said that I would love to hear some feedback on this. Discussion is welcome, ideas will be logged, and thoughts on how to push our bot forward will be listened :)
Thank you in advance and regards,
Product Owner for @Atlas Hangouts Chat bot.