what's the strategy about having this tool in the main organization?

[moul]

how do we plan to integrate it with the rest of the official tools?

[notJoon]

how do we plan to integrate it with the rest of the official tools?

@moul

Good and tough question. In fact, since I did not expected to migrate this project to the organization repository from the beginning, I currently lack a strategy.

However I'm considering the following approachs:

1. Maintain the Lint Tool Separately: Continue managing this tool in a separate repositiory, like this, keeping it independent from the gno codebase as we do currently.

2. Itegrate as a Submodule: Later, add this tool as a submodule to replace the existing lint implementation and continuously update module periodically, if there are changes.

By applying this method, I believe we can develop and maintain the tool independently of the gno's state. If the integration proceeds smoothly, we might also consider adding it to the CI/CD pipeline. Additionally, this approach os similar to the one used by Rust's Clippy, which I am referencing (although it appears somewhat different from the approach used by go tools).

However, still a lot of stabilization work is needed, it seems best to gather varipus opinions in the meantime and establish a comprehensive plan.