Is this and all other srcd projects dead?

[pombredanne]

https://sourced.tech is dead... what happened?
@bzz ? @vmarkovtsev ?

[mcuadros]

This repository is being hard-forked in a new go-erny organization. You can read about the status of a smilary repository at: https://github.com/go-git/go-git/wiki/go-git-has-a-new-home!-v5-and-some-explanations

[bzz]

@pombredanne sorry for delayed response.

Although I would be happy to maintain enry in some low profile mode even without the company support, I do not expect it to be ever updated under this URL any more, as nobody has access to src-d github account.

@mcuadros has more detailed explanation of the situation, I belive, under the link to go-git project.

[lafriks]

I could also probably help on maintaining it as we need it for Gitea project :)

[bzz]

I could also probably help on maintaining it as we need it for Gitea project :)

I have just release a post-srcd version at https://pkg.go.dev/github.com/bzz/enry/v2 but will be happy to move it under some shared org e.g https://github.com/mloncode and add @lafriks as a member if another contributor and MLonCode org member @kuba-- agrees.

[bzz]

After a very brief conversation with @mcuadros and @kuba-- and @lafriks comment above - a consensus seems to emerge:

• I'm volunteered to do some long-delay maintenance on the Support latest Go version bzz/enry#4
• next week a repo under https://github.com/go-enry/ is going to be created, all the code moved there
• it will run in collaborative OSS project spirit
• @mcuadros volunteered to setup go library releases using Github Actions
• @lafriks will be invited there ASAP
• a next release of the go library (at first) will be published ASAP from there

[mcuadros]

Ok, work done:

• enry moved to https://github.com/go-enry/go-enry
• CLI extracted from the library and moved to https://github.com/go-enry/enry

CI configured with GitHub Actions.

[lafriks]

Maybe github.com/src-d/go-license-detector could also moved to that org as it is functionally related?

[pombredanne]

@lafriks if you are looking for a decent license detection engine, may I suggest that you look at my https://github.com/nexB/scancode-toolkit ? 👼

[lafriks]

@pombredanne I need golang library to use in Gitea project ;)

[pombredanne]

@lafriks your call ... FWIW go-license-detector is fairly limited in terms of license detection accuracy ;)

None of the other Go-based tools in that space fare mucho better IMHO in terms of detection quality and accuracy, but at least they are maintained.

Check these:

• https://github.com/google/licenseclassifier by 👋 @rspier and team
• https://github.com/google/licensecheck by 🙇‍♂️ @rsc and 🙇‍♂️ @robpike

See also https://wiki.debian.org/CopyrightReviewTools for other pointers (I help maintain that page with other Debian license nerds)

[vmarkovtsev]

@pombredanne What do you mean by fairly limited? It is the only project of its kind that has a 1k test suite and measures in high 90-ies on it.

Regarding the maintenance, go-license-detector works as awesome as always, nobody has found (or at least, reported) any misdetection problems during the last two years, and I am still here to merge any PRs. The license DB was recently updated; apart from that, the project reached all the original goals, and the rest is up to the community.

[vmarkovtsev]

One day developers will consider license classification properly - as a machine learning problem, measure precision and recall, have a big dataset, etc. As we see, currently every dev thinks that they are smarter than the others, quickly reinvent the wheel that performs great for their narrow undisclosed usecase, and poor users end up with tens of libraries.

[bzz]

@pombredanne Enry's new and all the further releases are going to available at https://github.com/go-enry/go-enry/releases/tag/v2.3.0 🎉