Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Tegon: Open-source alternative to Jira, Linear

github.com

Post reply on HN
Print view View original

51–60 of 133 posts

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#51

Post by Daviey »

malcolmgreaves wrote: post #45
harshithmul wrote: post #10

Earlier quoted context omitted.

Thank you for your suggestion. You’re absolutely right; we are actively exploring licensing options, including AGPL, to ensure that our product remains protected. We value input from the community and are open to suggestions and assistance in making this decision. Our goal is to prevent unauthorized copying and resale of our product under different names while fostering a collaborative and innovative environment.

You can also expressly state that you have a commercial license too. Your entire license can be something like “ If you’re using it for commercial purposes, you must see a commercial license with XYZ. Otherwise, for all noncommercial uses, you may use the software according to the terms of the AGPL license.”

Please define "commercial use", because it means different things to different people.

Also, lots of organisations have a blanket ban on AGPL, so offering it under an alternative commercial license is a great approach to enable them, but explicitly blocking it for "commercial use" makes it no longer free software, which would be a shame.

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#52

Post by harshithmul »

itomato wrote: post #50
harshithmul wrote: post #47

Earlier quoted context omitted.

We thought auto-generated titles could make life a bit easier. Creating the perfect title for every task can be tricky, especially when things get complicated. So, we added this feature to help with that. (This is also something I faced as a challenge while I was working in Airbyte the community does a great job at explaining the issues but we always have to edit the title to make it more crisp.) Right now, we’re usi…

Lack of "crispness" in user titles is a tooling problem? Isn't this "wrinkly" technical detail lost?

We were experimenting if it could potentially help in taking that off the plate. Feedback taken we will work on improving that or taking a call based on how it performs.

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#53

Post by denysvitali »

harshithmul wrote: post #48
CapeTheory wrote: post #43

IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction.…

True performance is our priority. From the very beginning, we focused on ensuring that our app ran smoothly and quickly. To achieve this, we load all the data locally, allowing you to experience everything at lightning speed. Our background server keeps your data synchronized seamlessly between the server and the client, so you get the best of both worlds: speed and reliability.

> True performance is our top priority

The server is written in Node.JS

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#54

Post by harshithmul »

denysvitali wrote: post #53
harshithmul wrote: post #48

Earlier quoted context omitted.

True performance is our priority. From the very beginning, we focused on ensuring that our app ran smoothly and quickly. To achieve this, we load all the data locally, allowing you to experience everything at lightning speed. Our background server keeps your data synchronized seamlessly between the server and the client, so you get the best of both worlds: speed and reliability.

> True performance is our top priority The server is written in Node.JS

My bad. We focused on the performance on the front end currently, as said before we loaded all the data locally and kept the data synced in the background to make the interactions fast. We chose nodejs as that was easy for us to get started with. But definitely, if things get hampered we will start looking into it.

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#55

Post by inhumantsar »

harshithmul wrote: post #49
CapeTheory wrote: post #43

IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction.…

We are also working on a more chat-based approach to interact with the tool. To let you directly handle things from the messaging tools like slack.

I completely agree. I've often found myself copy pasting links to slack threads or screenshotting messages to append to tickets. being about to flag a thread and have a service create a ticket, summarize the discussion, highlight the requirements, and (importantly) include the things we decided against doing, would make life so much easier.

the flip side of course is that the easier it is to create a ticket, the easier it is to create duplicate or contradictory tickets. does your system offer the ability to check for existing tickets that are a close match for whatever is being created?

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#56

Post by harshithmul »

inhumantsar wrote: post #55
harshithmul wrote: post #49

Earlier quoted context omitted.

We are also working on a more chat-based approach to interact with the tool. To let you directly handle things from the messaging tools like slack.

I completely agree. I've often found myself copy pasting links to slack threads or screenshotting messages to append to tickets. being about to flag a thread and have a service create a ticket, summarize the discussion, highlight the requirements, and (importantly) include the things we decided against doing, would make life so much easier. the flip side of course is that the easier it is to create a ticket, the easi…

Hey, that's where we bring in triage grouping and duplicate identification. We show you what are the similar issues and we are also working on smart merging so to merge the information from both the issues.

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#58

Post by inhumantsar »

malcolmgreaves wrote: post #44
satvikpendem wrote: post #38

Earlier quoted context omitted.

AGPL doesn't prevent anyone from taking your code wholesale and hosting the entire thing. They didn't make any changes so they don't have to contribute anything back per AGPL. OP can make any part that interacts with it, such as billing and infrastructure code, closed source as they are the copyright holder and thus do not have to abide by AGPL or any license themselves. If they make every contributor sign a CLA, the…

If you build something interacts over a network with an AGPL’d program, then you are hitting the distributing over a network clause in the license.

But that only stipulates that the third party has to make the code available if they've modified it.

This is fine if you expect people to want to modify the backend, but it won't stop people who only care about cloning the service.

Which is sort of the point, good software made available to as many people as possible as cheaply as possible, but it's not really protection against others who would monetize the software you wrote.

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#59

Post by peterldowns »

First, congratulations on launching. I think people are so used to seeing beautiful products these days that it can be hard to remember how hard it is to make anything. Nice work! With that out of the way, here is some critical feedback:

- What is the pitch that you made to YC that convinced them to back you? The market size just doesn't seem that large and I don't understand what will differentiate you from Linear (whose design language you seem to have ripped off, somewhat poorly.) This post and the current featureset is vague and does not seem like a significant improvement. What is the core problem you're solving and why is that valuable? Your launch post above describes a lot of "how" but not a lot of "why".

- Why are you bothering to pretend to be "open source"? You're backed by YC and you'll make money selling access to the product on your "Tegon Cloud". If you're really going to be open-source, you need to make some significant improvements before anyone would consider contributing. Some documentation on how to self-host would be a good start. Look at all the environment variables in this dockerfile — which ones are necessary to run this service myself? https://github.com/tegonhq/tegon/blob/main/docker-compose.ya...

- If you're going to be "open source", the quality of your codebase and engineering skills is going to be a deciding factor in whether or not you get outside contributors. Consider writing actual descriptions in your pull requests, describing what you've done and why. Here's a PR picked at random — this is bad engineering work and does not encourage others to contribute. https://github.com/tegonhq/tegon/pull/114

My advice is that you drop the facade of being "open source", hire a designer, and do some actual user research to figure out where people are actually struggling with their ticketing systems. The features you're building (automatic title suggestion, thread summarization, and "find similar tickets") do not solve the problems that I have had with ticketing systems. They're small, potentially nice-to-have features that absolutely do not help me understand the core question for all engineering teams: who is doing what, how will they do it, why, and when will it be done.

Re: Show HN: Tegon: Open-source alternative to Jira, Linear

#60

Post by peter_l_downs »

peterldowns wrote: post #59

First, congratulations on launching. I think people are so used to seeing beautiful products these days that it can be hard to remember how hard it is to make anything . Nice work! With that out of the way, here is some critical feedback: - What is the pitch that you made to YC that convinced them to back you? The market size just doesn't seem that large and I don't understand what will differentiate you from Linear…

By the way, you've left the notiz.dev LICENSE file in your server code, probably you want to remove that.

https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61...

Separately, there seems to be a ton of unused or broken or dead code sprinkled throughout — for instance, in the auth code, I can't tell if you're doing basic email/password auth or using Supertokens and a third-party login via Google. You have code for both and some routes seem dead or missing.

https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61...

Also, I mentioned the lack of documentation for how to run Tegon locally because your docs are entirely insufficient. The main docs page is just a README template. https://github.com/tegonhq/tegon/tree/main/docs

The quickstart guide has a broken link to instructions on how to self-host https://github.com/tegonhq/tegon/blob/main/docs/quickstart.m...

The oss/local-setup guide is entirely empty https://github.com/tegonhq/tegon/blob/main/docs/oss/local-se...

The oss/deploy-tegon guide does not explain anything and the script it references seems out of date https://github.com/tegonhq/tegon/blob/main/docs/oss/deploy-t...

I'm done looking at this project. I strongly recommend hiring the best engineer you can find as quickly as you can.

Post reply on HN