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

Show HN: Paca – Lightweight Jira alternative for human-AI collaboration

github.com

Post reply on HN
Print view View original

31–40 of 81 posts

Re: Show HN: Paca – Lightweight Jira alternative for human-AI collaboration

#34

Post by andylynch »

crossroadsguy wrote: post #12

People who like Jira (or rather want; I doubt one ever “needs” this thing), and make decisions on its implementation and payment, and force it on others, are not the people who are shopping for alternatives. So who these alternatives are really for?

This always irritates me, because it used to be just like that. First time we bought Jira, it was like a (small ) one-off charge on someone’s card, and included full source code to let you build it yourself.

Re: Show HN: Paca – Lightweight Jira alternative for human-AI collaboration

#36

Post by spiderfarmer »

_pdp_ wrote: post #30

You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP. This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.

"Nobody needs it"

"Fits me well"

So maybe don't speak for everybody?

Re: Show HN: Paca – Lightweight Jira alternative for human-AI collaboration

#37

Post by re-thc »

_pdp_ wrote: post #30

You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP. This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.

> You can take it a step further and strip out the frontend.

You can take it a step even further and strip out all the code too!

Re: Show HN: Paca – Lightweight Jira alternative for human-AI collaboration

#38

Post by flo_r »

dagss wrote: post #23

What are people's workflows these days? As I use claude more and more I've started using git worktrees, one branch per worktree per PR, with possibly multiple agents working in each worktree at the same time on different aspects. And I manually instruct those agents. Like Emdash/Cursor/Zed. Sometimes I review code locally, sometimes agents push and I review in GitHub, no clear system yet. (jj seems promising, but Zed…

Gh issues works surprisingly well as an agent board. Labels for state, one issue per feature. The part i haven't figured out yet is how to know when the output is actually done vs just "looks done" to the agent.
Post reply on HN