Establish community contribution process

Problem

Our CI Component Catalog is a valuable resource that provides users with a wide range of modular CI components to enhance their CI/CD pipelines. To further enrich this catalog and encourage community involvement, we recognize the need to establish a clear and inclusive process for community contributions. Currently, there is no formalized process in place for community members to contribute to the catalog.

added to epic &11538

changed the description

@dhershkovitch, Please add a group or category label to identify issue ownership.

You can refer to the Features by Group handbook page for guidance.

If you are unsure about the correct group, please do not leave the issue without a group label, and refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issue.

This message was generated automatically. You're welcome to improve it.

This issue was automatically tagged with the label grouppipeline execution by TanukiStan, a machine learning classification model, with a probability of 0.91.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan

This message was generated automatically. You're welcome to improve it.

added automation:ml grouppipeline execution labels

added devopsverify sectionci labels

mentioned in issue gitlab-org/quality/triage-reports#14243 (closed)

added grouppipeline authoring label and removed grouppipeline execution label

Setting label(s) Category:Pipeline Composition based on grouppipeline authoring.

added Category:Pipeline Composition label

@stingrayza @dnsmichi @dhershkovitch @fabiopitino - Since we want to create an easy way for people to contribute to building components, I think it would be helpful if we added a section in https://docs.gitlab.com/ee/ci/components/ that is called something like "How Can I Contribute?".

I'm wondering if under that section we start to promote links like https://about.gitlab.com/community/hackathon/ and/or https://devpost.com/hackathons?organization=GitLab where people can go to get the latest events we have to contribute to component development.

We could also consider promoting our quick win issues too. WDYT? Just trying to continue on the thoughts we've been discussing recently to get the word out.

/cc @marcel.amirault (for awareness since it's docs-related)

I agree that adding a development guide for community contributors is a good first start. What do you all think should we create a dedicated doc issue for that?

@marknuzzo @dhershkovitch I think this is directly related to #432281 (comment 1719803817)

I found I needed the majority of information on that page, so I'm not sure how we could do a generic quick start that would have less than that information.

@marcel.amirault - to your point above in the other issue, I'm wondering if the quick start reference could fall along the same lines of How Can I Contribute?. Something like following this quick start tutorial would get you on your way to contributing. Thoughts everyone? Maybe this issue becomes the implementation of that short quick start.

/cc @fabiopitino

@marknuzzo Coming back to this ping, we've tinkered with the docs here and there, and I now wonder if perhaps just a better introduction to this section would help with this issue? https://docs.gitlab.com/ee/ci/components/#write-a-component

better introduction to this section would help

Hi @marcel.amirault - thanks for reaching out. In general, is it better to blend in screenshots or video with text to strengthen our docs? I ask because I'm wondering if a video like what @fabiopitino did in https://www.youtube.com/watch?v=Vw8-ce8LNBs (it would need to be updated since we have templates/ directory now) could help others visualize the step-by-step process following along. WDYT? To my earlier point, whichever we go to get users up and running quickly I'm fine with doing.

@marknuzzo I think Add project template for Gitlab CI/CD components (!151560) is the perfect tool for a get started guide. When that merges, I'll add a section on how to use that template to get started with components quickly

@dhershkovitch - since we have a path forward here now with !151560 and a follow-up section to be added, I think this issue can be closed now. WDYT?

Fine by me

changed epic to &12135

mentioned in issue #437893 (closed)

mentioned in design management/design #433394 (closed)[Verified-creator-icon-only-popover.png]

closed