#106 Swag Printing Proposal
Closed: Complete 4 years ago by bex. Opened 5 years ago by bex.

I'd like to see Mindshare create a new policy to speed up swag issues. I believe we should empower the FCAIC and those who work with this person to help with budget/swag to print swag from a budget as needed.

Swag items and use concepts will be approved by Mindshare, in general, and then the FCAIC/others will fulfill needs for the various events based on their best judgement in concert with the event owner/coordinator. They will come back to Mindshare if there are questions.

As an example, this would look like this for the Fedora Booklets in #105

  1. Mindshare makes a decision about the use of the booklets in general and about Fedora providing them
  2. FCAIC/others arrange to have them printed and in-stock or on-demand for use
  3. Event Owners suggest when they will be useful at their events
  4. AMAZING EVENTS!

To support this, I believe we should allocate a budget for swag to be managed by the FCAIC/others. I suggest we start with $10,000. Let's evaluate that as we move forward.


Sounds very reasonable for me +1 too

It sounds pretty reasonable. +1

Do we have any idea what mindshare's budget will be for the upcoming year?

Seems reasonable to me. I'm all about simplifying the approval process when possible and getting things done.

Do we have any idea what mindshare's budget will be for the upcoming year?

The project's global budget is not yet finalized. We are working on a "same as last year" assumption. The budget allocation for last year should support this.

@nb does this answer your question?

This is up for final approval with 3+1s and no -1s by our next meeting on 10 April.

Metadata Update from @bex:
- Issue priority set to: next meeting (was: awaiting triage)

5 years ago

Approved. Needs to be documented.

Metadata Update from @bex:
- Issue assigned to bex

5 years ago

Metadata Update from @bex:
- Issue priority set to: None (was: next meeting)

5 years ago

@bex Yes, that answered my question and I am +1

Metadata Update from @bex:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata