what should we do about this repo?

[moul]

It seems to be unmaintained, which may not be a problem if the text is primarily intended to showcase an archive or if it is updated to exclude overly dynamic information.

[michelleellen]

I think this could be re-purposed where we build out the best practices for contributing and being a part of the gno.land ecosystem. In essence a directory of sorts that lays out the guide of being a gnome.

A Guide to Contributing so to say, or a 'Hitchhiker's Guide to gno.land' we could include the contributing md link and provide the what makes a good contributor and how to showcase your work.

The steps recommended: namespace, home realm, and documenting your journey...etc. We could include the available tools that are at the contributors disposal.

My question: do we want to transition this type of information to gnoverse?
My take: The gno repo, should provide the canonical guides, and information for contributors and gnoverse is where they go to add their projects for ecosystem consumption.

My question: Would this idea compete with getting started?
My take: Probably not, as getting started is more about the technical side of gno.land where a contributors guide is more about the individual in the ecosystem.

This might be a good place one day for the constitution?

[Kouteki]

My question: do we want to transition this type of information to gnoverse?

Gnolang should still be initial point of contact, and Gnoverse should be a safe space to play around with Gno.

As such, it makes more sense to have the bulk of the contributing info on gnolang, and some gnoverse specific info on gnoverse. Both should have clear links to each other.

My question: Would this idea compete with getting started?

We can have a clear distinction between the two types of content. I'd be happy to drive the effort for this repo.