On Wed, Jun 6, 2018 at 6:44 PM, Máirín Duffy <duffy@xxxxxxxxxx> wrote:
Hi Matthew,This is what we've had in the past that the design team worked on:- travel guide- wifi portal logo- tshirt- fedora mag banners- blog banners ("i'm going to flock")- qr scan poster for badge- fedora badges associated with event- room signage / directional signage- lanyards- sticker sheets- schedule booklet / printouts (last year ryan did a wall schedule)Not knowing what swag / collateral budget is available and what items might be planned, nor what rooms or how many rooms there will be, nor the schedule to create the schedule booklet.... I'm concerned about how we'll make progress on anything listed above except for:- the blog banners- the Fedora magazine banners- the logo which we could use for a t-shirt design if there's budget and intention to have t-shirts.We have already gotten started on the logo, and can get started right away on the other two banners. I am concerned about the other items.
Thank you for the comprehensive list Mo, this was super helpful. Also, thank you for working on completing the new art and CSS. I think I integrated it correctly into the site. That said, your feedback/improvements are always welcome.
I talked to Matthew yesterday about the artwork. We want to continue to put the focus on the Fedora brand, Since Flock is an internally focused conference, it doesn't need fancy external branding work. We wonder if we the design team could focus on a logo and concept that could become a standard design to be used from year to year. This design could feature an optionally changing element, for example (and not restricted to) a line art city-theme that changes in the background of the logo. This, it seems would allow us to create a set of design tasks that would be good easyfix/first tasks each year (i.e. update the Flock logo with a new number), and opportunity for creativity when the team has the capacity for it (add the line-art like thing), and reduce the amount of effort that needs to be put in each year to produce all of the various collateral.
This would seem to translate into set designs (with, ideally simple mandatory updates and some optional creativity updates) for:
- A logo/masthead for printed/pdf'ed documents
- A website/magazine banner header
- Blog/tweet promo banners
- "attended" fedora badge
Effort can be focused each year on the:
- "party" fedora badge
- T-shirt, if we have one
- any extras, if needed
A special note about T-shirts. We would like to make Fedora the prominent brand on the t-shirt, possibly even not mentioning Flock at all. The goal here is to give our contributors a shirt to wear that starts a conversation about Fedora first, and not a "What is Flock?" conversation. If we have sponsors who will be on the shirt, we would consider producing a second t-shirt that is a Fedora-branded and themed Flock shirt with sponsors. This gets around the issue that many people have raised about not wanting to wear a sponsor branded shirt.
Right now, we have budgeted for the Fedora t-shirt mentioned. We currently do not have sponsors requesting a t-shirt printing.
How can we help make this happen? Would me opening design tickets help?
Thanks,
bex
I am on vacation the first week in July, and I will be taking on and orienting a new intern the second week of July, so I won't be available in July until the second half, which is 2-3 weeks before the event and too late to create and have designs ready for vendors to produce including their production time.~m
On Wed, Jun 6, 2018 at 11:45 AM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:On Tue, Jun 05, 2018 at 02:06:53PM -0400, Máirín Duffy wrote:July is a big vacation month, and there's not so much time left even if that wasn't the case, so to make sure nothing falls on the floor, can someone let us know what items need to be designed for Flock so we can work on them?Bex is on vacation this month. I don't know if he was planning a printed program. Things I can think of other than that are: * badges * tshirt * maybe a promotional graphic for Magazine articles / sharing online? What else have we had in previous years?--Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ design-team mailing list -- design-team@lists. fedoraproject.org To unsubscribe send an email to design-team-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/design-team@ lists.fedoraproject.org/ message/ 4ABSIOOPGQFDEIU63VW3BUENPS5GJP JL/
_______________________________________________
flock-planning mailing list -- flock-planning@lists.fedoraproject.org
To unsubscribe send an email to flock-planning-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/flock- planning@lists.fedoraproject. org/message/ 6NLS6IUASQFJWQ5NJDBRP2IQKC7CBQ AK/
Brian (bex) Exelbierd | bexelbie@xxxxxxxxxx | bex@xxxxxxxxx
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
_______________________________________________ design-team mailing list -- design-team@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to design-team-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/design-team@xxxxxxxxxxxxxxxxxxxxxxx/message/BDKYWU2XHHMKC3B7WCE22PJULTAA4R7F/
