Allegheny Activism: Team Assignments

This page refers to the Allegheny Activism And Fedora project during the Spring 2010 semester.

Team Assignments
While it is true that the "open source way" would have us all dive in and contribute in our own way, organizing 40 people to contribute meaningfully in a short period of time is a bit tricky. Allegheny students are working in small groups to provide local support for each-other, as well as to provide some organization that their faculty can relate to as well.

Individuals may drift from one project to another; by no means are the teams "fixed." And, each individual remains responsible for keeping their own blog reflections up-to-date, and their information on this wiki page accurate. (The last sentence was missing an ending, so I guessed at it - Matt and Darren have the final say on whether my attempt is accurate, though. Mel Chua 18:29, 5 April 2010 (UTC))

Video Sharing
See Video hosting for project details.

Status comment: I've seen some good posts from this team to the list explaining your viewpoint - you seem to have reached the point where nobody is actively disagreeing with you any more, which means it's time to try out a first implementation, and then hand the keys over. See my email to the FS102 list from last night for details. Mel Chua 15:10, 29 April 2010 (UTC)

Twitter Strategy
See Marketing social networks for more details.

Status comment: I'm not sure where to find the work being done by this team - how can we make use of your work and thoughts, and what are your recommendations for a microblogging workflow? The wiki page linked-to from this section is a good place to leave notes behind, but make sure we can read and use them after your departure, and that you do the handoff on IRC and the mailing list and leave it in the hands of a specific person or small group of people from the community so that you can rest assured your work will live on (instead of simply being created and abandoned because nobody else knows it exists). Mel Chua 15:12, 29 April 2010 (UTC)

Press Kit
See F13 press kit for details.

Status comment: I'm not sure where to find the work being done by this team - how can we make use of your work and thoughts? The wiki page linked-to from this section is a good place to leave notes behind, but make sure we can read and use them after your departure, and that you do the handoff on IRC and the mailing list and leave it in the hands of a specific person or small group of people from the community so that you can rest assured your work will live on (instead of simply being created and abandoned because nobody else knows it exists). Henrik is a good person to find and make the handoff to; if you do a successful handoff of your work, it is very likely that your work will be used at the upcoming Red Hat Summit this summer. Mel Chua 15:14, 29 April 2010 (UTC)

One Page Release Notes
See F13 one page release notes for details.

Status notes: Your edits and contributions have been very helpful in improving the one page release notes for F13! To wrap up, it would be great to get your thoughts on what you think future people working on the notes should know, and what questions/confusions you had about this experience (and what was most helpful while you were doing it). Type notes into One page release notes SOP and I'll clean them up afterwards. Mel Chua 15:16, 29 April 2010 (UTC)

Feature Profiles
See F13 feature profiles for details.

Status update: Btrfs feature profile: AWESOME. Edits on existing feature profiles: AWESOME. (Thank you for your help on the Python one - it is infinitely more readable by normal human beings now). Aside from those two, what others have you worked on, what other feature profiles have you touched, what comments do you have on the overall process? The btrfs interview and the Python edits represent a lot of useful work, but I want to make sure we're not missing any other stuff you've done so we can give you proper attribution!

Also: what you've done this release cycle has been to confirm that it is very good to get newcomers' eyes on public-facing deliverables like feature profiles. For instance, Hannah asked questions in her btrfs interview that a more experienced Fedora contributor would probably not have asked - but they were exactly the questions that needed to be asked because they were the same ones that the audience reading the interview with Josef later would have. So - great work! Mel Chua 15:32, 29 April 2010 (UTC)

Wild West (design team tickets)
See Design team ticket tackling tools for more details.

Status update: I've touched base with a few of you on this throughout the semester, and I know some have been in #fedora-design and Mo (mizmo) has tried to get you started on tickets - but beyond that, I know almost nothing. How did this go? I would love to see a status update to the design team mailing list with your impressions and thoughts and pointers to your work, and if what you found was "this is confusing and frustrating, and we got stuck here, here, and here because of this, that and the other" - that is incredibly valuable as well. Mel Chua 15:24, 29 April 2010 (UTC)

Sugar on a Stick Spin Webpage
See Sugar on a Stick for more details.

The Spin webpage creation SOP would not exist if you hadn't come and shown us that it needed to, so even though it may not feel this way, you've been tremendously helpful in making it possible for others to make spin pages later on. It's difficult to be the first to do something, and I commend the courage you've shown in taking this on. Be bold. :)

If you have any thoughts or materials you've generated for this spin webpage - even if they're rough, like IRC interview transcripts or half-written emails - we'd love to have them. We can pick up and polish much of what you leave behind and fold them into the webpage before the May 18 launch. In particular, I know that one of you did an interview with a teacher, and there may be more materials that we haven't seen because they weren't announced to a mailing list... can you help us see the work you've done? Mel Chua 15:23, 29 April 2010 (UTC)

Design Suite Spin Webpage
See Design Suite for more details.

The Spin webpage creation SOP would not exist if you hadn't come and shown us that it needed to, so even though it may not feel this way, you've been tremendously helpful in making it possible for others to make spin pages later on. It's difficult to be the first to do something, and I commend the courage you've shown in taking this on. Be bold. :) We're currently trying to figure out where to find the work you've done - can you give us some pointers?

If you have any thoughts or materials you've generated for this spin webpage - even if they're rough, like IRC interview transcripts or half-written emails - we'd love to have them. We can pick up and polish much of what you leave behind and fold them into the webpage before the May 18 launch. In particular, difficulties you've had installing/getting the spin to run, and reviews of applications you were able to launch would be helpful. Mel Chua 15:22, 29 April 2010 (UTC)