#fedora-meeting-1 Meeting

Meeting started by rbergeron at 20:02:13 UTC (full logs).

Meeting summary

  1. Agenda (rbergeron, 20:04:41)
    1. http://fedoraproject.org/wiki/Marketing_meetings (rbergeron, 20:05:01)

  2. Marketing FAD 2010 - followup (rbergeron, 20:07:03)
    1. http://fedoraproject.org/wiki/Marketing_FAD_2010 (rbergeron, 20:07:34)
    2. ACTION: mchua to send out FAD Summary wiki link - this should cover what we did, accomplished, and task items that came out of the meeting (rbergeron, 20:09:13)
    3. ACTION: rbergeron to add task items to trac, and start discussions as appropriate... and follow up with email to the marketing list. (rbergeron, 20:09:35)
    4. ACTION: Add to next week's marketing meeting agenda - ensure that all wiki items / tasks / etc. have been followed up on, documented (rbergeron, 20:11:44)
    5. ACTION: rbergeron to go through that list and double check she or someone followed up on everything, and get owners at next tuesdya's meeting for any leftover / unvolunteered items (rbergeron, 20:12:11)
    6. next time, when going for giant deliverables, talk with experts in that field who've made such deliverables before to help scope out the plan of action beforehand. (mchua, 20:15:08)
    7. ACTION: add to future FAD ideas list (if we have that, i'll figure something out) - talk with experts about the things we want to accomplish for realisty check (rbergeron, 20:15:16)
    8. ACTION: rbergeron to set up meeting after next tuesday marketing meeting for prioritizing task list, NOT a regular marketing meeting - will be a one-off. (rbergeron, 20:16:13)
    9. ACTION: consider target date for next FAD... document somewhere. we should consider timing with cycle. (rbergeron, 20:16:52)

  3. Feature profiles (rbergeron, 20:17:02)
    1. https://fedoraproject.org/wiki/Marketing#Release_deliverables (mchua, 20:18:05)
    2. https://fedoraproject.org/wiki/Category:F13_in-depth_features (stickster, 20:18:18)
    3. https://fedoraproject.org/wiki/Feature_profiles (mchua, 20:18:19)
    4. https://fedoraproject.org/wiki/Feature_profiles (mchua, 20:18:23)
    5. https://fedoraproject.org/wiki/Category:In-depth_features (mchua, 20:18:30)
    6. AGREED: the name of the deliverable is "Feature profiles" (mchua, 20:22:09)
    7. ACTION: mchua to redirect wiki stuff for consistency on "feature profiles" (rbergeron, 20:22:26)
    8. https://fedoraproject.org/wiki/Feature_profiles_SOP (mchua, 20:22:50)
    9. https://fedoraproject.org/wiki/Category:F13_in-depth_features (mchua, 20:23:32)
    10. ACTION: stickster to look into how much traction / hits podcast feature profile from last cycle got (rbergeron, 20:32:09)
    11. ACTION: determine whether it is bringing people in / really popular (rbergeron, 20:32:27)
    12. ACTION: robyn to take HW enablements feature profile (rbergeron, 20:33:24)
    13. ACTION: mchua to take python feature profile (mchua, 20:34:23)
    14. ACTION: mchua find remaining feature profiles (boot.fp.o, btrfs) writers. (mchua, 20:36:26)
    15. ACTION: stickster to take boot.fedoraproject.org feature profile (mchua, 20:37:45)
    16. ACTION: ke4qqq to send initial mails on podcast of btrfs feature profile (rbergeron, 20:42:11)
    17. ACTION: ke4qqq and rbergeron to figure out the rest of the btrfs process (rbergeron, 20:42:51)
    18. ACTION: rbergeron to invite spin groups to use SOPs to do their own feature profiles, talking points, etc. (rbergeron, 20:45:25)
    19. ACTION: mchua clean up talking points and feature profiles SOPs so that spin groups can do exactly that (mchua, 20:45:43)
    20. we need an easy way to find out where to contact spins - if that's not spins.fedoraproject.org, it should be (mchua, 20:46:10)
    21. http://spins.fedoraproject.org/ (rbergeron, 20:46:12)
    22. IDEA: spins.fp.o redesign profile story (mchua, 20:47:40)

  4. Give Work To People, Yay (mchua, 20:48:32)
    1. http://meetbot.fedoraproject.org/fedora-fad/2010-03-14/fedora-fad.2010-03-14-13.41.html (mchua, 20:50:34)
    2. mchua looking for good "new contributor" tasks for college students to do (mchua, 20:50:47)
    3. http://meetbot.fedoraproject.org/fedora-fad/2010-03-14/fedora-fad.2010-03-14-13.41.html (mchua, 20:53:44)
    4. IDEA: get students to write feature profile esque things (mchua, 20:54:42)
    5. IDEA: get students to do wiki cleanup (mchua, 20:54:46)
    6. list of allegheny students stuff is captured on link here (rbergeron, 20:59:13)
    7. http://meetbot.fedoraproject.org/fedora-fad/2010-03-14/fedora-fad.2010-03-14-13.41.html (rbergeron, 20:59:19)
    8. ACTION: mchua get Allegheny profs into Marketing and Design teams respectively (mchua, 20:59:28)
    9. ACTION: robyn to dump statistics brainstorm from dinnertime at FAD into [[statistics 2.0]] (rbergeron, 21:00:29)


Meeting ended at 21:01:50 UTC (full logs).

Action items

  1. mchua to send out FAD Summary wiki link - this should cover what we did, accomplished, and task items that came out of the meeting
  2. rbergeron to add task items to trac, and start discussions as appropriate... and follow up with email to the marketing list.
  3. Add to next week's marketing meeting agenda - ensure that all wiki items / tasks / etc. have been followed up on, documented
  4. rbergeron to go through that list and double check she or someone followed up on everything, and get owners at next tuesdya's meeting for any leftover / unvolunteered items
  5. add to future FAD ideas list (if we have that, i'll figure something out) - talk with experts about the things we want to accomplish for realisty check
  6. rbergeron to set up meeting after next tuesday marketing meeting for prioritizing task list, NOT a regular marketing meeting - will be a one-off.
  7. consider target date for next FAD... document somewhere. we should consider timing with cycle.
  8. mchua to redirect wiki stuff for consistency on "feature profiles"
  9. stickster to look into how much traction / hits podcast feature profile from last cycle got
  10. determine whether it is bringing people in / really popular
  11. robyn to take HW enablements feature profile
  12. mchua to take python feature profile
  13. mchua find remaining feature profiles (boot.fp.o, btrfs) writers.
  14. stickster to take boot.fedoraproject.org feature profile
  15. ke4qqq to send initial mails on podcast of btrfs feature profile
  16. ke4qqq and rbergeron to figure out the rest of the btrfs process
  17. rbergeron to invite spin groups to use SOPs to do their own feature profiles, talking points, etc.
  18. mchua clean up talking points and feature profiles SOPs so that spin groups can do exactly that
  19. mchua get Allegheny profs into Marketing and Design teams respectively
  20. robyn to dump statistics brainstorm from dinnertime at FAD into [[statistics 2.0]]


Action items, by person

  1. ke4qqq
    1. ke4qqq to send initial mails on podcast of btrfs feature profile
    2. ke4qqq and rbergeron to figure out the rest of the btrfs process
  2. mchua
    1. mchua to send out FAD Summary wiki link - this should cover what we did, accomplished, and task items that came out of the meeting
    2. mchua to redirect wiki stuff for consistency on "feature profiles"
    3. mchua to take python feature profile
    4. mchua find remaining feature profiles (boot.fp.o, btrfs) writers.
    5. mchua clean up talking points and feature profiles SOPs so that spin groups can do exactly that
    6. mchua get Allegheny profs into Marketing and Design teams respectively
  3. rbergeron
    1. rbergeron to add task items to trac, and start discussions as appropriate... and follow up with email to the marketing list.
    2. rbergeron to go through that list and double check she or someone followed up on everything, and get owners at next tuesdya's meeting for any leftover / unvolunteered items
    3. rbergeron to set up meeting after next tuesday marketing meeting for prioritizing task list, NOT a regular marketing meeting - will be a one-off.
    4. ke4qqq and rbergeron to figure out the rest of the btrfs process
    5. rbergeron to invite spin groups to use SOPs to do their own feature profiles, talking points, etc.
  4. stickster
    1. stickster to look into how much traction / hits podcast feature profile from last cycle got
    2. stickster to take boot.fedoraproject.org feature profile
  5. UNASSIGNED
    1. Add to next week's marketing meeting agenda - ensure that all wiki items / tasks / etc. have been followed up on, documented
    2. add to future FAD ideas list (if we have that, i'll figure something out) - talk with experts about the things we want to accomplish for realisty check
    3. consider target date for next FAD... document somewhere. we should consider timing with cycle.
    4. determine whether it is bringing people in / really popular
    5. robyn to take HW enablements feature profile
    6. robyn to dump statistics brainstorm from dinnertime at FAD into [[statistics 2.0]]


People present (lines said)

  1. rbergeron (208)
  2. mchua (196)
  3. stickster (60)
  4. wonderer (25)
  5. ke4qqq (18)
  6. zodbot (3)
  7. yn1v (2)
  8. spevack (1)


Generated by MeetBot 0.1.4.