#fedora-mktg Meeting

Meeting summary

1. 1. soas page needs content help, want to sync up allegheny student material with current spin page material (mchua, 14:53:50)
   2. design page needs about section, think allegheny team *may* have material for that (mchua, 14:54:02)
   3. http://git.fedorahosted.org/git/?p=fedora-web.git;a=commit (sdziallas, 15:52:32)
   4. https://fedoraproject.org/wiki/F13_one_page_release_notes (mchua, 16:04:16)
   5. https://fedoraproject.org/wiki/Moblin_Spin#Spin_description (mchua, 16:46:09)
   6. http://moblin.org/projects/libsocialweb (mchua, 16:47:11)
   7. https://fedoraproject.org/wiki/Moblin_Spin#Spin_description (mchua, 17:06:35)
   8. https://fedoraproject.org/wiki/Moblin_Spin#About (mchua, 17:06:40)
   
   
2. howto use the Fedora Marketing Trac queue (mchua, 17:07:40)
   1. https://fedorahosted.org/marketing-team/report/1 (mchua, 17:07:46)
   2. the ticket queue is supposed to be an accurate description of what mktg needs done at any point in time (mchua, 17:08:41)
   3. our ticket queue is based on Trac, an open source python-based ticket tracker (mchua, 17:09:03)
   4. you can log into our Trac instance - there's a login link at the top right - using your FAS credentials (mchua, 17:09:26)
   5. clicking on a ticket gives you more details about that ticket (mchua, 17:09:37)
   6. let's look at an example, ticket #11. (mchua, 17:10:01)
   7. https://fedorahosted.org/marketing-team/ticket/11 (mchua, 17:10:06)
   8. We'll explain the various "fields" in a ticket now (mchua, 17:11:32)
   9. Reported by - who created the ticket? (usually the person who requested the task/found the problem or bug that needs to be fixed) (mchua, 17:12:02)
   10. Priority - how important is this? (major, minor, etc) (mchua, 17:12:12)
   11. Component - what is the ticket about? is it a release deliverable, part of a project (limesurvey, fedora insight, etc)? (mchua, 17:12:58)
   12. Keywords - we don't really use this except to mark things as meeting topics, so you can ignore this for now (mchua, 17:13:19)
   13. Assigned to - who is working on this ticket? You can assign a ticket to yourself if you want to take on a task, we'll cover this in a moment. (mchua, 17:13:40)
   14. Milestone - when does this task need to be completed by? (mchua, 17:13:49)
   15. Severity - how quickly does this taks need to be completed? (which is different from "priority" - things can be important but not urgent, or urgent but not important. this is the "urgent" part.) (mchua, 17:14:26)
   16. Cc - who is watching this ticket? these are the people who are interested in the ticket but are not working on it themselves, they will get notifications when anything about the ticket changes. (mchua, 17:14:56)
   17. Description - the actual task that needs to get done. (mchua, 17:15:09)
   18. And then below that is the conversation - comments on the ticket, which may be further clarification of the task, or notes about what people are doing to work on it. (mchua, 17:15:24)
   19. and then below that is the interface you can use to make changes to the ticket. we'll go through three kinds you may want to make if you're working on a ticket: (1) taking it, (2) commenting on it, and (3) closing it (mchua, 17:17:17)
   20. : To take a ticket - meaning to say "yes, I will work on this!" - go to the "action" section at the bottom and either click "accept ticket" (if nobody is working on it yet) or "reassign to:" and then select your username (if you want to take over a task from its existing owner - it's good etiquette to ask first though!) - and then click "Submit Changes." (mchua, 17:18:43)
   21. If you just want to watch a ticket but don't want to work on it yet, type your name in the "Cc:" box at the bottom of the ticket (right above the "Action" section) and click "Submit changes." (mchua, 17:19:10)
   22. Now, you're either watching a ticket (Cc) or working on it (accepted/reassigned). As you go along, you should keep others updated on your progress. To do that, type your notes in the comment box and then click "Submit changes." (mchua, 17:19:58)
   23. for instance, "I wrote half the text the ticket said was needed, and uploaded it to <LINK!> but didn't finish the rest yet." (mchua, 17:20:15)
   24. Finally, when a ticket is complete - when you think the work is done - you comment one last time with a link/pointer to the finished work, and then in the "action" section, click "resolved as:" and select "fixed", then click "Submit changes" and you're done. (mchua, 17:21:15)
   25. It's also good to email the Marketing list if you've closed a ticket so we know about the work you just completed. ;) (mchua, 17:21:36)
   26. If you have a task you'd like to see someone on the Marketing team do, you should make a ticket and add it to the queue! (mchua, 17:22:02)
   27. log into the Trac instance, and then click the "new ticket" link in the top right hand corner. (mchua, 17:22:21)
   28. https://fedorahosted.org/marketing-team/newticket (mchua, 17:22:25)
   29. You'll be able to describe the task you'd like completed - more information/details is better, so that whoever starts on this can actually just launch in without having to ask a lot of questions. (mchua, 17:22:49)
   30. remember to click "submit ticket" to actually create the ticket - and emailing the Marketing list with the link to your ticket and a summary asking for help is a good idea, as is asking around the #fedora-mktg IRC channel if anyone can take the ticket (mchua, 17:23:30)

Action items

1. (none)

People present (lines said)

1. mchua (239)
2. sdziallas (94)
3. gwerra (29)
4. rbergeron (18)
5. zodbot (15)
6. nmarques (14)
7. threethirty (9)
8. wonderer (7)
9. fedbot (3)
10. Southern_Gentlem (1)
11. EvilBob (1)
12. ke4qqq (1)