Highlight projects that want maintainers in some way

[caniszczyk]

The use case is here: projects should be able to specify that they are interested in attracting more maintainers

This probably is some type of github issue projects can create with a label specifying they'd like new maintainers that we can highlight in some special way and feature it.

[jeefy]

Could it also perhaps be a hashtag that a repo puts in their description? #prswelcome? 😁

[caniszczyk]

I think linking to a github issue with more details on how to become a contributor/maintainer is what I'm looking at imho I don't have a good template though... it's like something we'd invite/encourage projects to do?

…

On Mon, Apr 3, 2023 at 12:55 PM Jeffrey Sica ***@***.***> wrote: Could it also perhaps be a hashtag that a repo puts in their description? #prswelcome? 😁 — Reply to this email directly, view it on GitHub <#249 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIJX63ZXFF22AF64FHDW7MFJTANCNFSM6AAAAAAWRTTN2E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Cheers, Chris Aniszczyk https://aniszczyk.org

[tegioz]

That sounds cool 👍

Could this be defined in the CLOMonitor data files that are used to feed and sync projects configuration for both CLOMonitor and CLOTributor? Some projects maintainers are already using them to modify projects' settings via PRs (and maybe you'd like to highlight this status on both sites :). We could have a section to enable this interest in new maintainers that could include some links to an introductory issue, contributing docs, where to start, etc.

[tegioz]

Maybe something like:

maintainers_wanted:
  - enabled: true
  - links:
    - title: How to become a maintainer?
      url: https://link1
    - title: Contributing guide
      url: https://link2
  - contact: @handle
  ... 

Plus any other piece of data that we may need eventually 🙂

[caniszczyk]

I'd probably put this in the landscape.yml in l.cncf.io tbh because we'd also highlight it there That's a good idea though!

…

On Mon, Apr 3, 2023 at 1:30 PM Sergio Castaño Arteaga < ***@***.***> wrote: Maybe something like: maintainers_wanted: - enabled: true - links: - title: How to become a maintainer? url: https://link1 - title: Contributing guide url: https://link2 - contact: @handle ... Plus any other piece of data that we may need eventually 🙂 — Reply to this email directly, view it on GitHub <#249 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIMBZQ6IWGQCDPJFPXLW7MJL5ANCNFSM6AAAAAAWRTTN2E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Cheers, Chris Aniszczyk https://aniszczyk.org

[tegioz]

We have an issue open in CLOMonitor to Consider using the landscape YAML file as data source. The main problem is that we may need to make some changes to the landscape yaml file to make that happen, so it'd be good if you could take a look and share your thoughts as some may be important 😇

So to get this going we can add it to where we have the rest of the configuration right now (it may be confusing otherwise), and once the landscape data files are ready to be used as a CLO* data source we can move this to it with the rest of the settings.

[caniszczyk]

I'd be totally open to updating the l.cncf.io format let me think about it but things are getting a bit busy before kubecon

…

On Mon, Apr 3, 2023 at 1:47 PM Sergio Castaño Arteaga < ***@***.***> wrote: We have an issue open in CLOMonitor to Consider using the landscape YAML file as data source <cncf/clomonitor#471>. The main problem is that we may need to make some changes to the landscape yaml file to make that happen, so it'd be good if you could take a look and share your thoughts as some may be important 😇 So to get this going we can add it to where we have the rest of the configuration right now (it may be confusing otherwise), and once the landscape data files are ready to be used as a CLO* data source we can move this to it with the rest of the settings. — Reply to this email directly, view it on GitHub <#249 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIMCXT3UWKXOHPF7AOTW7MLMLANCNFSM6AAAAAAWRTTN2E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Cheers, Chris Aniszczyk https://aniszczyk.org

[ashutosh887]

I've read the above conversations
Please let me know if I can work on this @caniszczyk @jeefy @tegioz

[tegioz]

Hi @ashutosh887 👋

This is probably not a good first issue on this project, so @cynthia-sg and I will take care of it. When an interesting good first issue that we need help with comes up, we'll add the labels help wanted and good first issue to it 🙂

I would recommend you to take a look at https://clotributor.dev. It lists ~1k issues from Cloud Native projects that are looking for help (all issues on it are labelled as help wanted!), and you can use the filters to find the ones that best suit your interests and skillset.

[tegioz]

This is ready! 🙂

Some information about how to set it up: https://github.com/cncf/clotributor#maintainers-wanted

And a sample screenshot of how it looks like in the UI: