Live data from Hacker News

Plane – Open-source Jira alternative

plane.so

131–140 of 151 posts

Re: Plane – Open-source Jira alternative

#131

Earlier quoted context omitted.

As a user, that's the best for a software like this, because it means it cannot be ever closed source!

> cannot be ever closed source Cannot be closed source unless the maintainer dual licenses and stops making OS (assuming a single maintainer or group that all agree, or that other contributors have signed a relevant copyright waiver). (though what has already been released can't be retracted)

Not the maintainer, all the copyright holders. If you accept contributions without a CLA, that closes that avenue.

I couldn't find any outside contribution in the repo yet, we'll see how they go.

Re: Plane – Open-source Jira alternative

#132

> Simplify your transition to Waterfall, Agile, and other workflows to keep up team's momentum with Cycles and Modules. LOL, at least they are honest about companies doing waterfall style planning being their target audience.

I mean sometimes waterfall is required depending on the industry, especially industrial or space and some of government and medical.

At least with waterfall you get a sense of completion

Re: Plane – Open-source Jira alternative

#133

It’s AGPL licensed which is interesting. Much like Redmine this means modifications or customizations are a license violation unless shared correct? I wonder if these licenses are hurting the adoption of OSS alternatives for enterprise software

> It’s AGPL licensed which is interesting. Much like Redmine this means modifications or customizations are a license violation unless shared correct?

No, AGPL means that if you're using it to provide a network service you must offer the source *to the users*, but not necessarily share it with the world as a whole.

If you use it internally at a company, your modified source must be made available to your internal users. It is not required to be shared with the upstream project or the world as a whole. This is the same as any other GPL software, just with the AGPL network interaction provision.

The only time AGPL requires sharing your modifications with the world is if you're using the AGPL code to provide services to the world.

> I wonder if these licenses are hurting the adoption of OSS alternatives for enterprise software

There are definitely a lot of enterprises that are paranoid about even using anything GPL related, mostly without good reason.

If an organization that doesn't want to even consider sharing their modifications to code they're getting for free avoids using (A)GPL software as a result I think most developers who choose those licenses would say everything is working as intended.

Re: Plane – Open-source Jira alternative

#134
post #85
post #2

License AGPL3 https://github.com/makeplane/plane/blob/develop/LICENSE.txt

Until last month they used the Apache license. https://github.com/makeplane/plane/commit/a3f6d61347ef98171f...

Good catch thanks for pointing this out

Re: Plane – Open-source Jira alternative

#135

As 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.

I disagree. SSO is something that big companies care about and early-stage startups and hobbyists don't. It's a super easy gate to generate revenue from the people who can afford to pay (and mindshare from the people who can't).

You seem to be advocating for SSO for personal use too, to which I say: hell no. I don't even use the same email address between different sites. Why should I give every site I log in to a freebie for cross-site tracking?

Re: Plane – Open-source Jira alternative

#136
post #54

> Simplify your transition to Waterfall, Agile, and other workflows to keep up team's momentum with Cycles and Modules. LOL, at least they are honest about companies doing waterfall style planning being their target audience.

The closer you are to agile the more basic your ticketing system needs and vice versa. You could probably do without one at all even.

this is very true.

my team just merged with another, larger team.

before this merge we operated off only github issues and never had problems with it

now we have length jira planning sessions, new meetings every 2-3 weeks on updated jira expectations, and a whole group of people whose job it is to track our jira usage and let us know if we aren't using it correctly / meeting standards

under one system we always finished work ahead of time and could actively pursue more projects

under one we are constantly behind the "estimate" for our assigned work

care to guess which is which?

Re: Plane – Open-source Jira alternative

#137
post #11

Looks very promising I will give it a try. Related: I would love to see an open source confluence alternative as well, as for issues there are many (more or less capable) options to choose from.

Have a look at https://www.getoutline.com/

I'm really impressed by the product. Seems to be a good Confluence alternative.

Re: Plane – Open-source Jira alternative

#138

Earlier quoted context omitted.

I strongly disagree. You can't easily have conversations about issues in Git and even if you could do you really want to have a commit for each message? I'm aware of some systems that try to tack issue tracking onto Git in a similar way to Fossil, but they just aren't as good as a proper issue tracker. That said, Jira is a terrible issue tracker. I do not understand how it is so bad given that it is literally its onl…

As you touched on, the major problem with Jira is actually that it does so much nobody (roughly) knows how to use it. You get 3 levels if you include Epic (Epic > Task > Subtask). You can set up a sprint/kanban board filter to cover multiple projects, so this does actualy gives you multiple projects per sprint. I do agree that it's slow and doesn't update itself to reflect changes. The two groups of people who hate J…

> You get 3 levels if you include Epic (Epic > Task > Subtask).

Indeed but that's still an artificial limitation, and subtasks are not really fully featured tasks.

Re: Plane – Open-source Jira alternative

#139
post #48

Earlier quoted context omitted.

This bothers me on almost all project management software. What I'd love to see, is to be able to assign one person as the one "responsible" and then assign others ad-hoc when/if they work on-, review-, discuss, or co-author it. Some software allows multiple assignees, but as the ancient management-saying goes: if everyone is responsible, no-one is. So i'd still love to have one person assigned with a special role or…

Yeah this is an issue with my current company's use of Jira. They're super worried about tickets being "lost" so they all have to be assigned to one person, but then that means you can't tell who is actually working on something. My previous company used Phabricator and you only assigned yourself a task when you actually started working on it. It meant anyone could work on anything - much more agile and much much bet…

> You want a "person who is responsible for making sure this eventually gets done" field and a "person who is currently working on this" field.

Indeed. But the last part should be plural. Because in reality multiple people work on it. A reviewer, someone who helped with the UX, the person you spoke to to get the exact business-details right, that colleague you needed to finetune the SQL, or the moment bob goes on vacation and you need to step in and take over his work.

Re: Plane – Open-source Jira alternative

#140
post #7

My opinion based on feature and screenshots is that the UX is as shitty as Jira. The nightmare with Jira is this product manager obsession with kaban boards that become overwhelmed once your project become serious.

You can use Jira just fine without Kanban boards. That's really the beauty and the curse of Jira, it can be pretty much anything you want it to. To truly compete with Jira you need a level of flexibility that almost guarantees that your product will suck to. If you run Jira, Confluence and Bitbucket, the level of integration you can achieve is pretty unmatched. The cost: You need to buy the data center edition, on-pr…

Even in list view, it goes very fast to so overwhelmed that it is unusable. There are then usually 2 cases: - teams have strategy like closing every issues that can't be worked on immediately. So clean board but rotten software with lots of issues buried and regularly rediscovered. - team just letting issues list grow unmanageably and will only look at the most recent things or what arrived in the parking.

In the few different companies of different sizes that I worked, I never saw a Jira that did not become a hot mess until people start new projects or new boards when they can't bear anymore.

I find it also extremely difficult to find anything. Like you know that an issue exist but search will not help you find it easily. Very often I have to go to Gmail to search in notifications to find back the link to an issue.

Post reply on HN