Wikidata:Property proposal/Go package path

Go package path edit

You have not transcluded your proposal on Wikidata:Property proposal/Generic yet. Please do it.

Under discussion

Description	path of a Go package
Data type	External identifier
Example 1	GoPacket (Q115156585) → github.com/google/gopacket
Example 2	Gin (Q96279007) → github.com/gin-gonic/gin
Example 3	quic-go (Q105941555) → github.com/lucas-clemente/quic-go
Source	https://pkg.go.dev
External links	Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Formatter URL	https://pkg.go.dev/$1

GZWDer (talk) 10:29, 19 November 2022 (UTC)[reply]

Discussion edit

Notified participants of WikiProject Websites Regards, ZI Jony ^(Talk) 13:17, 19 April 2024 (UTC)[reply]

Notified participants of WikiProject Informatics/Software Regards, ZI Jony ^(Talk) 13:17, 19 April 2024 (UTC)[reply]

Support Laftp0 (talk) 05:03, 20 November 2022 (UTC)[reply]
Oppose The Go package path can be automatically derived from source code repository URL (P1324), e.g:

so there is really no point in us duplicating that information. Links to https://pkg.go.dev/ would of course be handy but these should be created automatically with a user script for any software that is programmed in (P277) Go (Q37227). I am happy to develop such a userscript :) --Push-f (talk) 20:27, 20 November 2022 (UTC)[reply]

Is this always repo address? Some seems not, e.g: k8s.io/kubernetes, google.golang.org/protobuf, gorm.io/gorm Laftp0 (talk) 15:55, 22 November 2022 (UTC)[reply]

https://pkg.go.dev/github.com/kubernetes/kubernetes and https://pkg.go.dev/github.com/go-gorm/gorm indeed also work. https://pkg.go.dev/github.com/protocolbuffers/protobuf-go interestingly enough does not work ... probably because it declares module google.golang.org/protobuf in its go.mod file.

I still think that this is something that should be addressed by pkg.go.dev ... it shouldn't be too hard for them to store such module directives and automatically redirect from the repository path to the right documentation URL. Push-f (talk) 16:16, 22 November 2022 (UTC)[reply]

I guess some modules work with repo address are outdated versions that don't contain go.mod as pkg details say "The Go module system was introduced in Go 1.11 and is the official dependency management solution for Go." Laftp0 (talk) 16:28, 22 November 2022 (UTC)[reply]

Huh, both kubernetes and gorm do also set module in their go.mod. So I really don't know what's causing protobuf-go to not work with the repo path. --Push-f (talk) 17:31, 22 November 2022 (UTC)[reply]

I think k8s.io/kubernetes and github.com/kubernetes/kubernetes are not the same. Maybe you can realize the difference. I guess kubernetes added go.mod after it's implemented, so module name changed after added. Against it, protobuf has go.mod since its first version. Laftp0 (talk) 02:56, 23 November 2022 (UTC)[reply]

Right ... I still think that this is something that pkg.go.dev could implement ... I just asked Drew DeVault (Q64995795) about it[1], he has his own pkg.go.dev alternative (https://godocs.io/) and I figure that he'll be more responsive than the Go developers ... let's see. --Push-f (talk) 09:09, 23 November 2022 (UTC)[reply]

Okay, that might be better to identify a module. Laftp0 (talk) 09:53, 23 November 2022 (UTC)[reply]

@Push-f:, any update/response from Drew DeVault. Or any changes in your opinion. Regards, ZI Jony ^(Talk) 05:32, 25 January 2024 (UTC)[reply]

@GZWDer:, could you please fulfil the minimum requirements. Regards, ZI Jony ^(Talk) 05:33, 25 January 2024 (UTC)[reply]

Support --MMo (talk) 09:49, 9 June 2023 (UTC)[reply]