Show HN: Documind – Open-source AI tool to turn documents into structured data

Re:Show HN: Documind – Open-source AI tool to turn documents... by ankenyr on Thursday November 21, 2024 @09:25PM (#42210625)

Your initial commit makes it look like you wrote all the code. https://github.com/DocumindHQ/documind/commit/d91121739df038... This is because you copied and uploaded the code instead of forking. You could do a lot by restoring attribution. Your history would look the same as https://github.com/getomni-ai/zerox/commits/main/ and diverge from where you forked.

People are getting upset because this is not a nice thing to do. Attribution is significant. No one would care if you replaced all the names with the new ones in a fork because they would see commits that do that.

[ Parent | on HN ]

Re:Show HN: Documind – Open-source AI tool to turn documents... by Tammilore on Friday November 22, 2024 @04:22AM (#42212363)

Hi. Thank you for pointing this out. I totally understand now that forking would have kept the commit history visible and made the attribution clearer. I have since added a direct note in the repo acknowledging that it is built on the original Zerox project and also linked back to it. If there’s anything else you’d suggest, happy to hear it. Thanks again.

[ Parent | on HN ]

Re:Show HN: Documind – Open-source AI tool to turn documents... by ankenyr on Friday November 22, 2024 @01:03PM (#42216000)

It would be better to attribute. You can still do this by fixing the git commit history and doing a force push. It would do a lot to make people feel better.

[ Parent | on HN ]