GitHub projects are wild good now
But then your PMs and all stakeholders need to have github accounts.
This is the entire point
Plane – Open-source Jira alternative
91–100 of 151 posts
Re: Plane – Open-source Jira alternative
#92They meant “linear.app”, not Jira, and “copy” instead of alternative.
There’s currency in this type of knock off. Find a well executed closed source app, clone as open source, pick an alternative pitch “the Jira killer”, then raise YC because open core is the fashionable argument.
Re: Plane – Open-source Jira alternative
#93As someone who typically rejects/hard-passes on products with the SSO tax (sometimes even when there’s budget/will to go with the SSO-included tier), I really appreciate the lack of the SSO tax here.
The era for security and in particular identity and auth management to be pay-to-play is long over and I appreciate when projects and businesses are honest about that.
Re: Plane – Open-source Jira alternative
#94Earlier quoted context omitted.
I think Notion (my employer) https://notion.so/product made it popular. However .so gave us a lot of trouble over the years, so I wouldn’t recommend.
Out of interest: what sort of troubles has it given? (if you're able to say)
- Corporate firewalls don’t like people visiting .so Somalia URLs. Wouldn’t have this problem with .com. We had to fight hard for domain reputation.
- Back in the day communication between us, our registrar, a middleman registrar in Germany, and SomaliNIC wasn’t too good. We weren’t notified of a takedown report and got DNS blocked by a bunch of ISPs offline for 8 hours. Even figuring out what happened on that one was baffling.
Re: Plane – Open-source Jira alternative
#95Earlier quoted context omitted.
Lots of dovnvotes. I am curious to know the reasoning behind these. :)
I come to HN for high-quality discussion. If I were looking for snark and meme content I'd be on Reddit. In this particular case, your parent made a very reasonable case that a web app could simply choose to respect the system light/dark mode and that would be enough. I happen to disagree with them, but they were sincerely contributing to the discussion. You came along with a 4-word + emoticon + hashtag parody of wha…
I see your point - I suppose it was quite snarky. My take is (and I suspect the same as the people who upvoted my comment) that the comment was disregarding another persons feature request/preferences based because the did not match his/her own. It is an, in my experience, attitude not uncommon - and it (unfortunately) gets my blood boiling every time.
Re: Plane – Open-source Jira alternative
#96Earlier quoted context omitted.
It has that in common with essentially all other open source license. And it only extends to the version given to you under the license. The copyright holder(s) retain the right to change their mind. Which is a reason AGPL v3 is popular with companies that are looking to sell commercial licenses for their software. There are quite a few startups out there that attempted to keep control whose primary business model is…
What if a project has a plugin architecture and plugins are compiled files that can be dropped in at runtime? Those plugins can be any license then, is it not?
Plug-ins are generally considered a derived work, if directly written to use a specific API. You would need to build a module that works for many different systems and only uses the Plane APIs as a shim.
Even then, the shim might be argued to be infected, and thus the rest of the module too. In that case, you still could be facing an expensive and risky lawsuit, because I don’t think there are any precedents to predict how those winds will blow.
Re: Plane – Open-source Jira alternative
#97Earlier quoted context omitted.
Bugzilla still exists. And if you think something is the wrong thing to copy, just copy the "right" thing yourself.
It's also valid to make a comment where a bunch of developers might see it, and hope one of them agrees and has the time and skills to do it. Or maybe just to reach someone who never used bugzilla and doesn't realize it's light-years better than jira or rally.
That's valid, but saying that a product a few developers created for FREE, and made open source so anyone could copy and change is the "wrong thing to copy" is just disrespectful.
Re: Plane – Open-source Jira alternative
#98Why .so? I understand payara.fish, because payara is based on glassfish. What is the story here? I'm just curious (and bored) :).
Short for software
Re: Plane – Open-source Jira alternative
#99Earlier quoted context omitted.
It's also valid to make a comment where a bunch of developers might see it, and hope one of them agrees and has the time and skills to do it. Or maybe just to reach someone who never used bugzilla and doesn't realize it's light-years better than jira or rally.
That's valid, but saying that a product a few developers created for FREE, and made open source so anyone could copy and change is the "wrong thing to copy" is just disrespectful.
It would be disrespectful if thats all they said, but including "it would be nice.." and "...imho" changes it to politely giving their opinion on a third party forum. If it were a show hn, or the projects own forum I might agree with you, but this is the appropriate place to give armchair opinions.
Re: Plane – Open-source Jira alternative
#100Earlier quoted context omitted.
Sure, but you can have plenty of options where there's one responsible person, but you may still want to track another person who's involved. Maybe another engineer who's paired on the project, or the PM who's taking point on it, or the QA who's testing it, or the other engineer who's reviewing it. Having to rely on comments or assignment history to uncover that information is a bad experience.
Wouldn’t child tickets address that problem?
Perhaps? But I do plenty of projects where I'm just paired with another engineer. I'm maybe taking lead, but they're sitting in on all the meetings and helping make decisions when I want someone to check my work. That may be worth noting in a ticket in case I'm busy or out of office and someone needs an answer around the project, even if they don't have a specific task they're responsible for that they'd be assigned a child ticket for.
It's also a level of precision question. At some point, having a lot of child tickets is just extra work if it's mostly just documenting something that could have been as easily documented by attaching another person's name to the parent ticket.