Hi Harshith, love what you'll are building and love the clean interface. We've started using Tegon and I think this might be the PM tool we've always been looking for
Untitled topic
11–20 of 136 posts
Re: undefined
#12Impressive. I'd love to know why you chose to go open-source.
Thank you. We chose open source for several reasons: 1. We are building for Engineering Teams: Being in the public domain allows us to collaborate openly with engineering teams and build a better product. 2. Building Trust in AI Agents: Trust is crucial in AI development. By going open source, we demonstrate transparency and accountability, enhancing trust in our AI agents. 3. Enabling Marketplace Development: Our vi…
To be clear, being in “the public domain” has a specific and clear definition. You’ve licensed under MIT (which is great!) but it’s not the same thing as PD or a PD-equivalent licence like CC0.
Re: undefined
#13Congrats on the launch! We'd be in business for an alternative and I also thought about building something on my own. What I'm missing would be project-specific workflows (i.e. coding tasks have QA stages at our company) and higher flight levels like initiatives to sync product management, design and engineering.
Do you have a roadmap?
Re: undefined
#14Earlier quoted context omitted.
Thank you. We chose open source for several reasons: 1. We are building for Engineering Teams: Being in the public domain allows us to collaborate openly with engineering teams and build a better product. 2. Building Trust in AI Agents: Trust is crucial in AI development. By going open source, we demonstrate transparency and accountability, enhancing trust in our AI agents. 3. Enabling Marketplace Development: Our vi…
To be clear, being in “the public domain” has a specific and clear definition. You’ve licensed under MIT (which is great!) but it’s not the same thing as PD or a PD-equivalent licence like CC0.
We apologize for the confusion. You are right our project is under the MIT License, allowing open use but not placing it in the public domain like CC0.
Re: undefined
#15Aren't you afraid of a potential lawsuit from Linear[1]? Your interface looks like a copy paste. Dont get me wrong, it's amazing what you've build but cloning a well funded startup may not be the best strategy.
Re: undefined
#16Congrats on the launch! We'd be in business for an alternative and I also thought about building something on my own. What I'm missing would be project-specific workflows (i.e. coding tasks have QA stages at our company) and higher flight levels like initiatives to sync product management, design and engineering. Do you have a roadmap?
Our documentation is a work in progress, with our roadmap soon to be posted there.
We refer to the stages as workflows (To Do, In Progress, In Review, Done, etc.). Currently, we are focusing on the engineering teams and have predefined workflows. However, we plan to launch team-based workflow customization soon.
Regarding initiatives, we are working on a module that will provide a combined view of teams (such as Product, Design, etc.). This initiative module, for example, “Integrations,” will cut across these teams for better tracking.
Re: undefined
#17Aren't you afraid of a potential lawsuit from Linear[1]? Your interface looks like a copy paste. Dont get me wrong, it's amazing what you've build but cloning a well funded startup may not be the best strategy. 1 https://linear.app
Todoist has had this interface for years. It's standard nowadays, like a grid. I really don't get what people see in Linear; it is way overhyped but a polished app.
Re: undefined
#18Aren't you afraid of a potential lawsuit from Linear[1]? Your interface looks like a copy paste. Dont get me wrong, it's amazing what you've build but cloning a well funded startup may not be the best strategy. 1 https://linear.app
Indeed, our user interface (UI) shares similarities with Linear’s. We, too, are fans of Linear and appreciate its user experience (UX). After speaking with a lot of people, we concluded that it’s top-notch. Consequently, we wanted to give that experience rather than attempting to reinvent the wheel.
Despite drawing inspiration from Linear, we built everything from scratch. Our primary focus is the AI and task prioritization, which consumes most of our effort. We anticipate that our product will evolve and change over time.
Our aim was not to duplicate Linear, but to build a great product, and incorporating elements of Linear’s UX was a part of that process.
Re: undefined
#19Congrats on launch! It’s inspiring to see you building in the open.
Why build Nest on the server when you already have Next for the client?
Re: undefined
#20> Then we use AI to automatically create a title from the description, so you don't have to spend time figuring out a title
Yes please, tickets that POs spent even less time thinking and writing about.