Leantime: Open-Source Jira Alternative

Prompt is here: https://news.ycombinator.com/item?id=37611571

--

More seriously and charitably though, affero is vaguely scary because there's a (perhaps misunderstood, but I can understand) feeling that if you cooperate with it in any way in the backend and then a value-added product of that interaction makes it to a user of yours then you're up for copyright infringement.

This isn't a reason not to release under affero, nor is it a bad thing that entities producing non-free software need to take care what they leverage, but I can see how the decision could be made to avoid using agpl style software whereever possible to err on the side of caution.

A good example is ghostscript. At what point does an app converting PDFs to images (to display thumbnails, for example) as a small part of its workflow become an aggregate of that free software? According to the faq it ends up being a fairly subjective question of form and intent. Syscalls or static linking? Etc.

Again, I agree with the reasoning for libraries, devTools, infrastructure etc given that those libraries end up in commercial products. However in the case of full fleshed enduser applications AGPL is a great protector against the amazons of the world.

In a Jira workflow, there's a lot of customization required and a lot of thought needed to go into how to set up your workflow. Leantime is intended to be "opinionated" in the way that it's already set up -- each work function already has a home. The thing you have to decide is how you want to see the tasks.

Our "home" screen is intended for individual users to have pre-defined organization and not needing to set up their own dashboards either.

The other approach we do differently is to work to engage ICs in the value of the work and we do that by making the goals and work more clear. Some of this is still being developed out and rounded out better by our AI features -- which can be better read about here and how we view it in relationship to our own ADHD and the features behind it... https://leantime.io/2023/07/30/the-top-digital-planner-for-a....

Lastly, for Confluence fans, we come default with docs and (on cloud) we have whiteboards. Some of which will be coming out in plugins to OSS here soon.

I'm not sure what this means entirely, but across our projects we have some with different workflows than the others. These are necessary in that we have certain workflows that must meet compliance requirements, and those workflows are the best way to ensure we execute those. In other projects, they are less onerous and apply to different kinds of work (so, different workflows.)

> Our "home" screen is intended for individual users to have pre-defined organization and not needing to set up their own dashboards

This is good, but we generally keep our exec leadership out of JIRA (they don't really have the context for the details.) Our users can design their own dashboards, but that's a personal preference. We use the standard views.

> making the goals and work more clear

I would prefer to see more fall-into-the-pit-of-success for the equivalent of JIRA stories to be more oriented toward the outcome or feature or capability, as opposed to the accounting/I-got-receipts feeling I get from JIRA. While story points are fine, I prefer a focus on clarity and a better measurement for effort than the subjectivity of a team's interpretation of the fibonacci sequence.

> for Confluence fans, we come default with docs and (on cloud) we have whiteboards

So, Leantime includes a markup engine as well as a whiteboard feature? If I already have a deep investment in other tools that do those things, how do they integrate?