chore: update CODEOWNERS

[moul]

See title.

Depends on #1176

Checklists...

Contributors Checklist

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests
• Added new benchmarks to generated graphs, if any. More info here.

Maintainers Checklist

• Checked that the author followed the guidelines in CONTRIBUTING.md
• Checked the conventional-commit (especially PR title and verb, presence of BREAKING CHANGE: in the body)
• Ensured that this PR is not a significant change or confirmed that the review/consideration process was appropriate for the change

[thehowl]

judging from the error, group needs write access to repo

[mvertes]

What is the purpose of the @gnolang/devrels ?

[moul]

The @gnolang/devrels team is all about making developers happy and eager to use our product.

Right now, we're focusing mainly on developers. We can split what we need to do into two groups: building stuff and everything else. 'Everything else' includes writing documentation, giving support, putting on presentations and events, and handling marketing. The core team, which you're a part of, handles the building part. Meanwhile, the devrel team takes care of the 'everything else,' either directly or indirectly.

What's special about Gno is that we also expect our devrel team to get their hands dirty with code. This includes creating examples or tools and helping review PRs. While the core team members are busy squashing bugs, the devrel team can take the time to dive deep and figure out why a developer ran into a problem in the first place.

[moul]

I suggest we consider a tool similar to this: component-owners. However, its current version doesn't support "team" functionality. This tool was discussed here.

Given that it's based on YML, perhaps we can directly incorporate team support (with advanced YML features). This could streamline our management of contributors, reviewers, and related processes through commits.

[moul]

I will soon revive this issue, not just for devrels, but for the entire project and its subprojects.

Depends on #1176.

[moul]

Closing in favor of more recent changes.