Change the name field in package.json to '@WebOfTrust/signify'

[daviddm]

I suggest that we change the name field from signify-ts to @weboftrust/signify.
If we want we could also claim the scope @wot to make it more developer friendly?

It is the standard in the npm ecosystem, to not add 'js', 'node', etc.
That is why i suggest to remove the ts suffix.
https://docs.npmjs.com/cli/v10/configuring-npm/package-json#name

Adding a scope gives the ability to have all future package under the same scope with short names that might already be taken in the public scope eg signify.

The project can still be called signify-ts, just not published as such.

[pfeairheller]

Suggestion from @m00sey to use @keri as the scope.

@kentbull the sole dissenting vote

[2byrds]

From our vLEI dev community call today. We would like to align with the same organization naming as docker hub, which uses https://hub.docker.com/r/weboftrust/keria.
So we are advocating for @weboftrust/signify.

Maintainering members of that npm repo could be @pfeairheller and/or @m00sey representing WebOfTrust and @daviddm @lenkan @iFergal @rodolfomiranda as contributors.

[lenkan]

I noticed it is already taken: https://www.npmjs.com/org/weboftrust, but doesn't say who is the owner. Is it one of us?

[pfeairheller]

Yes, it is mine

[2byrds]

Yes, it is mine

@pfeairheller can we add more maintainers to @weboftrust/signify? or would you prefer us to find an alternative?
Maintainering members of that npm repo could be @pfeairheller and/or @m00sey representing WebOfTrust and @daviddm @lenkan @iFergal @rodolfomiranda as contributors.

[2byrds]

npm access grant <read-only|read-write> <org:team> [<package>]

[pfeairheller]

Sure thing, I'll add you folks today.