Delete community appreciation page

1. If possible please include a link with your thanks that points to the subject matter that you are giving thanks for, for example a link to a merge request.

1. We generally avoid recognizing people for working outside of working hours to minimize the pressure to do so. At times, team members may decide to work outside their core working hours to complete a task or attend an event. When team members work outside their core hours to deliver [results](/handbook/values/#results), we acknowledge their flexibility and contribution [transparently](/handbook/values/#transparency). It is appropriate to thank team members who flex their schedule to meet GitLab goals whether that's resolving a customer emergency, accommodating global team meetings, or delivering on a critical deadline.

1. Do not thank the CEO or other executives for something that the company paid for, thank GitLab instead.

1. To thank someone who is not a team member, you can [nominate them for community swag](/handbook/marketing/developer-relations/contributor-success/community-appreciation/).

1. To thank someone who is not a team member, [nominate them as a Notable Contributor](https://contributors.gitlab.com/docs/notable-contributors).

1. Understand that everyone doesn't need or want recognition. Once this is advised, please respect when they don't.

#### Values emoji

---

title: "GitLab Nominations for Community Swag"

---

## Let's Award Contributors Together

We want to recognize amazing contributions from the wider community with GitLab swags.

All GitLab team members and members of the wider community are encouraged to nominate others or themselves (for campaigns such as #myfirstMRmerge).

## Include Everyone

If you think that someone deserves a swag prize, nominate them!

If you reached an important campaign milestone (e.g. #myfirstMRmerged) with your contribution, you can also nominate yourself!

## Eligibility

Anyone who you feel deserves an extra special something for their contribution, comment, or community involvement is eligible for swag.

This can include, (but is not limited to):

* Great contributions to the GitLab product via issues or merge requests

* Representing the voice of GitLab at a speaking event, with a blog post, at a Meetup, or with a presentation

* Achieving the `#myfirstMRmerged` milestone

* Leaving a great answer on our [community forum](https://forum.gitlab.com/)

* Posting a great answer to on a [GitLab StackOverflow](https://stackoverflow.com/questions/tagged/gitlab) or [GitLab subreddit](https://www.reddit.com/r/gitlab/) question

* Bug Bounty reporters who submitted a quality report that did not qualify for monetary reward in our [Bug Bounty program](https://hackerone.com/gitlab?type=team).

For cases not listed above, use your best judgement, and create a merge request to add new cases to the list.

### Eligibility for Self Nomination

If you've contributed to our community or reached an important campaign milestone, you're eligible to self nominate for GitLab swag. Note that to self nominate, you must provide relevant links and evidence of your contributions to be evaluated by the GitLab team.

| Contribution | Notes for Self Nomination|

| ------ | ------ |

| #myfirstMRmerged | Must include link the merged MR |

| Community Blog Post | Must include link to published blog post |

| GitLab Forum Answer | Must include link to high quality answer provided on the GitLab Forum |

| Meetup/Presentation | Must include link to the meetup/event page |

## Nomination Process

The following process can be used either

* To nominate a wider community member for swag, or nominate yourself for swag, please fill the [nomination form](https://docs.google.com/forms/d/e/1FAIpQLSfGo-3kEimVPpC5zKKxXHkFjgYx8-vQAanzAX2LxGgXQqXikQ/viewform). Make sure to include links that show your community contribution ready before you send the form.

That's it! Contributor Success team members will be in touch with the person nominated on how to get the swag!

The form is reviewed weekly, and at a minimum each month, by Contributor Success, and you can check the status of each nomination in [column K](https://docs.google.com/spreadsheets/d/1WvZwL48Y5URNOr6KI26Lr4xgwlDQeOQJ8PK4dK9IaDA/edit?usp=drive_web&ouid=109629804026010673224) of the form's spreadsheet (only for GitLab Team members).

## Form Processing by Developer Relations Team

1. The Developer Relations team will review the nomination request and send the merchandise to the wider community member.

2. If the application is valid, communicate the giveaway link and code to the community member via email.

## Templates for Sending Swag Links

### Email Template

```markdown

Hi [NAME]!

The GitLab team has noticed the awesome support you provide on [Social Channel] to users asking questions about GitLab.

We'd love to recognize your efforts with some free GitLab swag!

The link below will take you directly to an order form where you can choose your favorite GitLab swag item.

[Giveaway Link] / [Code]

If you have any questions, don't hesitate to reach out. Thanks for your contributions to the GitLab community!

```

## Finding Community Member Contact Information

This section outlines the strategies that GitLab team member might use to contact community members during this process

* Always default to email communication. Email information of a contributor, if not known, can be requested from the Director of Contributor Success (only for Developer Relations team members)

  * Create a confidential issue with the list of GitLab usernames

  * Explain the source of the GitLab usernames

  * Add the communication method where you would like to receive the contact details

  * Emails given will only be the main email present in the GitLab profile.

## Sustainability and Swag Alternatives

We love swag, but there is an impact on the environment.

In an effort to offset this, we now offer the option of planting trees instead.

Contributor Success process the tree orders via [Tree Nation](https://tree-nation.com/)

using credentials from their 1Password vault.

There will be a quarterly [Hackathon](https://about.gitlab.com/community/hackathon/) for GitLab community members to come together to work on merge requests, participate in tutorial sessions, and support each other on the [GitLab Discord](https://discord.gg/gitlab).  Agenda, logistics, materials, recordings, and other information for Hackathons will be available on the [GitLab Community Hackathon](https://about.gitlab.com/community/hackathon/) page.

The event planning will be done following the [Hackathon issue template](https://gitlab.com/gitlab-org/developer-relations/gitlab-hackathon/-/issues/new?issuable_template=hackathon%20event%20plan) in the [GitLab Hackathon project](https://gitlab.com/gitlab-org/developer-relations/gitlab-hackathon).

GitLab teams are encouraged to use the following [Hackathon issue template](https://gitlab.com/gitlab-org/developer-relations/gitlab-hackathon/-/issues/new?issuable_template=hackathon%20team%20plan) to plan and prepare.

The event planning will be done following the [Hackathon issue template](https://gitlab.com/gitlab-org/developer-relations/contributor-success/team-task/-/issues/new?description_template=hackathon).

### Virtual hackathons/hackathon-in-a-box

Every time a contributor is opening a merge request to a GitLab namespace for the first time, the label "~1st contribution" is automatically applied to the merge request.

Once the merge request is reviewed and merged, the contributor can apply for the `#myfirstMRmerged` gift via a self-nomination form on the [nominations for GitLab swag page](/handbook/marketing/developer-relations/contributor-success/community-appreciation/#nomination-process).

Contributor Success team members can use the [outreach email/message template](/handbook/marketing/developer-relations/contributor-success/templates/email-templates) when sending the link for the first-time contributor gift.

### Working with the Core Team

More information on the [Core Team](https://about.gitlab.com/community/core-team/) is available in the [Core Team handbook page](/handbook/marketing/developer-relations/core-team/).

To be respectful to the contributor's privacy, we will only use contact data that is publicly available to reach out to them.

Here are some ways to reach out to contributors to e.g. distribute Hackathon prizes or MVP swag:

Here are some ways to reach out to contributors:

- You can mention them in an issue using their GitLab username.

- In private through our communication platform (Discord, Slack, etc.).

- A user might have e-mail or Twitter info on their GitLab profile. Sometimes users have the same username in other platforms (e.g. GitHub), and might have more information on their profiles there.

- A user might have e-mail on their GitLab profile. Sometimes users have the same username in other platforms (e.g. GitHub), and might have more information on their profiles there.

- Their e-mail address is stored in their git commits, unless they choose to use a [private commit e-mail](https://docs.gitlab.com/ee/user/profile/index#private-commit-email).

If you need assistance finding a contributor's email address please see [Finding Community Member Contact Information](/handbook/marketing/developer-relations/contributor-success/community-appreciation/#finding-community-member-contact-information)

Once you've found out the best way to contact them, you can choose to use a mention, e-mail or Twitter for instance.

Once you've found out the best way to contact them, you can choose to use a mention, e-mail, or Discord.

### Contributor blog post series

### Appreciation for highlighted contributions

From time to time, a wider community member will submit a particularly outstanding contribution. Other than thanking them on the MR, we might want to additionally show our appreciation by sending them some GitLab merchandise. Anyone in the GitLab team or in the wider community can follow the process to [nominate a contributor](/handbook/marketing/developer-relations/contributor-success/community-appreciation/).

From time to time, a wider community member will submit a particularly outstanding contribution. Any GitLab team member or the wider community can follow the process to [nominate them as a Notable Contributor](https://contributors.gitlab.com/docs/notable-contributors).

### Top Annual Contributors

#### General Moderator Best Practices

- Leave all interactions and replies open-ended. We want our forum users to feel like they can always come back and pick up the conversation.

- [Consider gifting swag](/handbook/marketing/developer-relations/contributor-success/community-appreciation/) to forum users that contribute a lot or in a really exceptional way! Do this via a DM/private message.

- Consider nominating forum users that contribute a lot or in a really exceptional way as [Notable Contributors](https://contributors.gitlab.com/docs/notable-contributors).

#### Moderator Only Access

title: "Swag: Process & FAQ"

---

## Assets

* Google Sheet "Developer Relations Swag Coupon Codes & Delivery Tracking".

  * The file can be found in the Shared Google Drive `Contributor Success`, and is titled "[GitLab] Developer Relations Swag Coupon Codes & Delivery Tracking"

* Swag Redemption portal

  * https://gitlab-contributor.brilliantmade.com/

## Swag Redemption Portal

This portal shows the items you can claim, given the right coupon code. This is the link sent out to Wider Community Members.

## Inventory Portal

This portal shows everything we've ordered and that is in stock & ready to ship.

Access can be requested through an [access request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Access_Change_Request). Mention "MyBrightSites" as the tech stack, and ping a manager from the [Developer Relations department](/handbook/marketing/developer-relations/).

A list of the items in our inventory with the amount of items left to be claimed is accessible in the Google Sheet.

## Sending Swag codes

If you are sending swag codes for the first time, you will need [a personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) with the `read_api` scope.

1. Request access to the [Google Sheet "Developer Relations Swag Coupon Codes & Delivery Tracking"](https://docs.google.com/spreadsheets/d/1LXXAXrxwx3HW1zFdBTB9OLQtjOqqECef9mCbvnzdnU8/edit?usp=sharing).

1. Go to the tab "Issue rewards".

1. Add the `Date`, `Username`, `Tier`, `Nominated by/cc` (if applicable), and `Link to contribution/event?` fields for the recipient.

1. Highlight the `Username` field you entered and from the `GitLab` menu, select `Create issues (highlight usernames)`

1. It’ll prompt you for your access token (personal, needs api access). Once entered, the macro will populate the rest of the fields and create an issue to reward the recipient in the [Contributor Success rewards project](https://gitlab.com/gitlab-org/developer-relations/contributor-success/rewards/-/issues/).

## Swag Nomination

If you think that a community member, contributor, or GitLab team member deserves a prize, [nominate them for some swag](/handbook/marketing/developer-relations/contributor-success/community-appreciation/#nomination-process)! This also applies if you've reached an important milestone with your contributor (e.g First MR merged).

## Tiers & Categories

### Tiers

Currently we work with 3 value tiers. A coupon tier describes the roughly montary value you are able to claim in the gift shop.

* Tier 1 Code

  * You can claim 3 items.

  * You have access to category 1 & 2

  * Expense range is on average $25

* Tier 2 Code

  * You can claim 4 items.

  * You have access to category 1,2 & 3

  * Expense range is on average $50

* Tier 3 Code

  * You can claim 6 items.

  * You have access to category 1,2 & 4

  * Expense range is on average $100

### Categories

* Category 1

  * You can claim 3 items

  * Examples include Keychain, a set of pens, a journal or sticker tattoos.

  * The maximum monetary value of an item is between $2-$10

* Category 2

  * You can claim 1 item

  * Examples include a GitLab T-Shirt

  * The maximum monetary value of an item is between $10-$15

* Category 3

  * You can claim 1 item

  * Examples include a GitLab Hoodie

  * The maximum monetary value of an item is between $15-$35

* Category 4

  * You can claim 1 item

  * Examples include a GitLab Hoodie or a Backpack

  * The maximum monetary value of an item is between $30-$65

For details on what is available in each category, please see the Inventory tab in the Google Sheet "Developer Relations Swag Coupon Codes & Delivery Tracking".

## Swag Order Process overview

1. GitLab will requests new swag orders through emailing support@brilliantmade.com

   * Quantity of items

   * Date by which the inventory needs to be fulfilled

   * Which category this item belongs to

1. Boundless recommends planning swag requests 2.5 weeks in advance to order, especially for international shipping because there can be issues with customs.

1. Provide the basic order requirements, optionally with the requirement of a custom notecard or a dedicated redemption page.

1. Boundless places the order so that it's in the inventory.

1. GitLab decide in which category the items belong

1. Boundless adds the items to the store front.

## External access to swag stores

There is a possibility to create access for, say, Meetup organizers, to self-service their required swag within our budget. Please file an access request and assign this to your manager.

## Additional resources

* [Merchandise handling](/handbook/marketing/brand-and-product-marketing/brand/merchandise-handling/)

* [Field Marketing](/handbook/marketing/field-marketing/)

* [Email templates for sending swag links](/handbook/marketing/developer-relations/contributor-success/community-appreciation/#templates-for-sending-swag-links)

* [Finding Community Member Contact information](/handbook/marketing/developer-relations/contributor-success/community-appreciation/#finding-community-member-contact-information)

## FAQ

### Is there any reason why Boundless would need to follow up if someone uses their coupon?

We will need a way to verify that swag has been expensed, to verify that our swag budget is not exceeded, or calculate how much budget is left i.e. for quarterly reports.

Once individuals have ordered swag, Boundless updates the spreadsheet to let us know if the coupon was redeemed. We need to make sure it gets delivered. They were some issues with deliveries recently - getting stuck at customs, etc. Sometimes it costs more than planned so they have to follow up and let us know if there's additional invoicing.

### Is there a documented process how to request new codes?

Create an issue within the [Developer Relations - Community Building](https://gitlab.com/gitlab-com/marketing/community-relations/community-building/-/issues) project and assign to @sugaroverflow (Fatima), and ping `@gitlab-org/developer-relations/contributor-success`

### I don't understand why we should plan ahead

This is a strong request from Boundless. They need to move orders into the inventory so they need us to plan ahead and request number of items, which items, and by which date. After that, we can let contributors decide what to get.

If you'd like to make it easier, you could plan ahead for a lot of items, pay for the invoice and ask for the items to be added to an existing or new category

### Can I have my own portal for my own program?

No, we simplified the historical situation on purpose as it was difficult to understand what we had in stock, difficult to send out items and a lot of `busy work`. The reason it is a single front, with Tiers & Categories allows us to scale and minimize human operations.

### Can we send to an individual with an appreciation note?

Yes. You can request to add custom notecards to kits.

* Boundless needs the verbiage to print on the card

* Generally 3 x 5" with a GitLab logo on top

### Who can help me with a declaration letter / support with getting Swag items released from customs?

Please email Brilliant team via email support@brilliantmade.com and they can assist you with getting Swag items cleared.

Contributor Success team members can award [Reward Store](https://rewards.gitlab.com/) credits via the [Contributor Platform](https://contributors.gitlab.com/rewards). Credits are redeemable for swag or virtual rewards, for example, to plant trees in the [GitLab Forest](https://tree-nation.com/profile/gitlab/).