Multiple times, it happened to me that I missed a stdlibs package or method. We need t

Related with <a class="issue-link js-issue-link" data-error-text="Failed to load title

Contributing policies for adding/updating new stdlibs packages about gno HOT 2 OPEN

moul commented on May 26, 2024

Contributing policies for adding/updating new stdlibs packages

from gno.

moul commented on May 26, 2024

Related with #486

from gno.

moul commented on May 26, 2024

Update

We should also make a process for porting good go libraries to gno, and publish them under a special domain prefix.

gno.land is for the main GnoVM chain; the sources are published using TXs.
foobar.land is for a new GnoVM chain; the source will be fetched using IBC2.
github.com or maybe imported.land/github.com is a special prefix where we know that the publisher is not the actual author, the license is inherited from GitHub, and the original author will be able to claim ownership later.

That being said, we can't have a process to port existing libraries without supporting versioning:

import "gno.land/p/stuff" could be the alias of gno.land/p/stuff/a1b2c3d4, updatatable to a newer version.
import "gno.land/p/stuff/5e6f7g8g" is the exact version.

Maybe make something equivalent for the stdlib, and manage #486 by adding a new version.

from gno.