Hi David & Ryan,
I had some comments for you on an old design team ticket here:
The ticket was filed in November and hasn't really been updated since
then, so I was wondering if it's still and open issue or if we should go
ahead and close the ticket?
A while back you requested a hackergotchi. Nicu tried to pick up the
ticket but it seems you didn't respond to his question about it. The
ticket is here:
Is your hackergotchi request something you are still interested in? If
so, can you answer Nicu's question on the ticket so we can move forward?
If not, can you let us know and we'll close out the ticket?
A while back you put in a request with the Fedora design team to design
a logo for Fedora localization.
We actually did a logo back in July but never heard back from you on it:
I went ahead and closed the ticket, but I wanted to make sure you knew
we did do a design from you and are happy to modify or update the logo
as you might need. Please feel free to reopen the ticket if there are
changes you'll need to it.
As this years EMEA FUDCon will happen in Zurich we would be very
pleased if you could helps us desinging a Logo/T-Shirt.
As Zurich is surrounded by mountains and a lake it would be great to
see these elements in the design.
Looking forward for your submissions.
Darren + Matt - possibly a bit wordy, but all the info I wanted to
convey is in there... feel free to cleanup/rearrange/annotate/send to
the class. Cc'ing the Design and Marketing lists so folks can see what's
Allegheny students, if you're reading this, anything your professors say
or send to the list supersedes anything you read or see on these lists -
this is a draft I'm sending out to keep Fedora community members in the
The third "Allegheny Meets Fedora" class just finished (Fedora people,
see http://blog.melchua.com/2010/04/06/fedora-hat-fleisige-helfer/ for
more context). Thanks to ke4qqq, rbergeron, sdziallas, and mizmo (David
Nalley, Robyn Bergeron, Sebastian Dziallas, and Mo Duffy) for helping us
The remainder of this email is written for the class. There's a link to
the IRC log from today somewhere in there.
A few notes:
0. You all did an *extremely* good job today - we're throwing you into
the deep end of something that's moving fast, and you're doing a great
job of asking questions and keeping up. Remember our mantra:
Productively Lost. Sometimes, the best thing you can do is ask questions
and tell us exactly why you're confused - it helps us fix things better
for the next people who come around.
A good target before our next class on Thursday morning might be to have
your team write an introduction email explaining your project,
introducing yourselves, describing your current plans, and asking any
questions you might currently have to the mailing list of the team
you're working with (there is a link to the mailing list subscription
page at the bottom of this email). You don't have to do this - it's just
a suggestion - but it's what I'll suggest to any team that asks me
"we're not sure what to do, what should we do?" between now and Thursday.
1. My email is mchua AT fedoraproject DOT org if you need *anything.*
You can always start by emailing me; if we need to move to another list
or an IRC channel or something, I'll let you know.
2. I am on campus between Wednesday morning and Friday night, and I
would like to spend as much time as possible in those 3 days working
with teams on their projects. Just email me and let me know a time and
place (I'm unfamiliar with campus, so will need directions) to come out
and work with you/your team. Note that I have a flexible schedule all
day, and that my usual bedtime is somewhere between 1am-4am. So if I'm
awake, I will come out to campus. If I'm asleep, I won't reply until I
wake up. ;)
3. Information about the class is at
each of your teams has an information page on
some resources that members of the Fedora community have tried to pull
together to help you get started.
4. I've heard that some people would like alternate images burned - for
instance, it may help the Sugar on a Stick webpage folks to have one of
those sticks to play with, and the Design Suite people may want a Design
Suite liveCD... if you'd like one of these things (Darren and Matt
included), please email me and let me know and we'll figure out a way to
take care of it. We have CDs available for those who want CDs, but
you're going to have to bring your own (2GB+) stick to burn (make sure
it's got nothing on it that you want to keep - but you can always wipe
it and reuse it afterwards).
5. A log of today's chat is available at
6. Some of you may have been asked to join other mailing lists and
channels by the Fedora folks you were talking to today. This is a good
idea. The lists you may have been invited to join are likely:
* https://admin.fedoraproject.org/mailman/listinfo/design-team (design)
* https://admin.fedoraproject.org/mailman/listinfo/marketing (marketing)
* https://admin.fedoraproject.org/mailman/listinfo/websites (websites)
And the channels may be:
The last two channels require a special sort of registration with IRC;
if you need to get into one of those channels and need help figuring out
how to register, email me.
PS: ADDENDUM! You folks have just made the lives of future contributors
easier - after class there was a bit of discussion on IRC about people
not being able to get into the #fedora-mktg channel to help out because
of registration issues. Bob Jensen saw this, popped in and changed the
settings... and you should be able to just join that channel now.
Thanks, Bob! (And thanks to the class for pointing this out to us!)
We may see questions from newcomers hitting this list shortly, as a team
from Allegheny College
is tackling this project:
I will be present in person this week to buffer, and will also be
handling as many of their questions on IRC as possible - but part of
that will be guiding students towards asking good questions in the
channel and on the list, and learning how to come up with their own
answers - with thinking-out-loud "how we came to this conclusion"
rationale clearly stated, as befits the open source way of doing things. ;)
Just a heads-up - this is a good excuse to (1) flag easy/urgent tickets
for them to start with and (2) for us to learn what the Design Team
looks like to new contributors who are trying to figure out how to get
--- excerpt below ---
So here's the problem:
The Design team has a bunch of tickets.
They need to be done.
They also need to be made more possible to work through - right now the
pile is large and daunting, assumes a lot of background knowledge, uses
acronyms, may not have a clear workflow... and so forth. Can you, as a
newcomer, figure out what the Design Team does and how to help it? If
not, this is a bug - and it's a bug that is our fault, and you will be
helping us by pointing out how we can fix it. What resources do we need
to provide to new Design contributors in order to smoothly get them started?
Your mission: close tickets. (Contact Mel Chua if you're not exactly
sure what that means.)
Remember, the goal is to be "productively lost" - this is all the
information we have right now, and you will probably have questions
right away - we don't know what questions you need answers to, though,
so once you find them we'll be pulling up (or making up!) the
information for those answers. You should feel free to make up answers,
Would you mind taking a few minutes to take the Duke University Fedora
survey? We need more design-minded folk to take it. It only took me
about 15 minutes to do it, it's not that bad. Research like this can
really help us understand how to make Fedora a better community to work
in and to attract new contributors.
-------- Forwarded Message --------
From: Greg DeKoenigsberg <gdk(a)redhat.com>
Subject: Fedora research survey.
Date: Thu, 1 Apr 2010 12:23:03 -0400 (EDT)
As some of you may know, professors at the Fuqua School of Business at Duke
University have been conducting a study of Fedora, and have put together an
online survey based on interviews they conducted with several dozen folks from
You can access the survey here:
Their research goal is to focus more deeply on three primary themes that
emerged from over 20 interviews they conducted with participants in the Fedora
o Values that are relevant to participants (e.g., to what
extent is 'Open Source' a relevant value across the Fedora
o Activities that participants engage in to help sustain the
community (e.g., to what extent is 'testing' a collaborative
activity across the Fedora Project?), and
o Tools participants use for communication or workflow (e.g.,
to what extent is 'Planet' or 'Koji' used across the Fedora
The findings of this research will go a long way to helping us better
understand what makes the Fedora community tick. I think it is a hallmark of
our success as a community that academics are starting to study in detail the
ins-and-outs of how our community works.
Please respond as soon as possible. If you have any comments or concerns,
please feel free to email me.
Thanks again for taking the time to answer these questions.
Educational materials should be high-quality, collaborative, and free.
Visit http://opensource.com/education and join the conversation.