ROCm / ROCm/FastFlowLM

[ Request/Plea ] Let the Open Source Community Support You

Open
#690 38 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.9k
Forks
152
Avg merge
4h 14m
Merged PRs (30d)
11

Description

Description of errors

How about you consider documenting structural changes?

Anyone wanting a custom finetune model is, as you have designed, stuck to 1.0.1 using heavily rewritten converters or paying you to convert things by presumably a closed-source tooling you won't ever open up. That's a great way to ensure only the bare minimum of adoption, and only by companies you already have deals with.

AMD; Charging companies to get special one off models converted and dependent on you for updates is NOT smart business, getting wider adoption IS. You sell chips not models, and it's utterly Wrong in both a business software development sense. Wrong as in the clear incorrect choice for literally any business.

You guys seem somehow new to open source. We have conventions such as what a Major vs minor version means -- you hide breaking changes under x.x.n bugfix level bumps. You actively make other developer's lives harder, and the only thing we can do is abandon your updates.

I watch. I see what you're all coding individually. I cherry pick. It turns out you didn't need to change any of the closed parts to fix any of the bug reports.

AMD, you can do better for your community. And that will sell your NPU chips. Don't break yourselves trying to defend something that IS replaceable.

Terrible idea overall. Might want to discuss what "open source" means, how the ecosystem actually works, and actually open things up. Until then, it's been nice. I'll maintain my 1.0.1 models, but otherwise everyone good luck.

Attach any links, screenshots, or additional evidence you think will be helpful.

https://github.com/Atomic-Germ/FastFlowLM_v1 on the 1.0.1-add1 branch Is significantly more capable than the official 1.0.3, without breaking 1.0.1 models.
https://huggingface.co/Atomic-Germ has dozens of models.
https://github.com/Atomic-Germ/q4nx-build can convert from tensors to q4nx in one shot.
https://github.com/Atomic-Germ/flm-test proves the model thinks, sees, and uses tools
https://github.com/Atomic-Germ/flm-add makes using them easy.

One person put that ecosystem together. Imagine what the whole community could do if you actually opened the damn code. The AMD team itself isn't enough, and FastFlow's growth and adoption is so bad most people don't even know what the NPU is for.

Try working out an explanation to shareholders as to why AMD thought it was a good idea, or even a sensible idea, to hamstring its own hardware and give people less reason to buy your chips. Does it seem convincing? No it doesn't of course it doesn't, because it isn't.


If I come off harshly, that's more passion than anger. Judge me and my point separately please. The title is the message.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the issue discussion and comparing the linked FastFlowLM 1.0.1-add1 branch with official 1.0.3, then inspect q4nx-build for the cited conversion workflow. A useful outcome would need a concrete, maintainer-approved scope for documenting structural changes or opening conversion tooling; the issue names no repository file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.