#fedora-meeting-3: "fedora-join"

Meeting started by FranciscoD at 16:04:29 UTC (full logs).

Meeting summary

  1. Rollcall (FranciscoD, 16:05:21)
  2. Agenda (FranciscoD, 16:06:22)
    1. New members (FranciscoD, 16:06:41)
    2. Announcements (FranciscoD, 16:06:47)
    3. Commops update (FranciscoD, 16:06:53)
    4. Status update on in-reach: https://pagure.io/fedora-join/Fedora-Join/issue/16 (FranciscoD, 16:07:13)
    5. Column idea: Help wanted Wednesday: https://pagure.io/fedora-commops/issue/100 (FranciscoD, 16:07:22)
    6. Fedora web space audit: https://pagure.io/fedora-join/Fedora-Join/issue/21 (FranciscoD, 16:07:30)
    7. Propose stage 2 to the Fedora Council as a project-level objective: https://pagure.io/fedora-join/Fedora-Join/issue/19 (FranciscoD, 16:07:40)
    8. Resurrect the mentoring programme: https://pagure.io/fedora-join/Fedora-Join/issue/18 (FranciscoD, 16:07:50)
    9. Resurrect the classroom programme: https://pagure.io/fedora-join/Fedora-Join/issue/22 (FranciscoD, 16:07:58)
    10. Any others here: https://pagure.io/fedora-join/Fedora-Join/issues (FranciscoD, 16:08:12)
    11. What can we do better (either in the meeting, or the ML, or anything else. An issue, followed by a suggestion.)? (FranciscoD, 16:08:25)
    12. Open floor (FranciscoD, 16:08:29)

  3. New members (FranciscoD, 16:08:55)
    1. Dhanesh B. Sabane. Member of CommOps, Marketing, Python, ML and hoping to be involved in lot more.. Find out more about me here: https://fedoraproject.org/wiki/User:Dhanesh95 (dhanesh95, 16:11:54)

  4. Announcements (FranciscoD, 16:14:15)
    1. We just had the elections - https://communityblog.fedoraproject.org/elections-retrospective-january-2017/ - hope everyone voted! (FranciscoD, 16:15:31)
    2. Flock 2017 bids are now open: https://communityblog.fedoraproject.org/flock-2017-bids-due-28-feb-2017/ (FranciscoD, 16:16:09)

  5. Status update on in-reach: https://pagure.io/fedora-join/Fedora-Join/issue/16 (FranciscoD, 16:18:21)
    1. https://fedoraproject.org/wiki/IRC_support_sig (FranciscoD, 16:20:41)
    2. pisg works, i'm trying to add some functionality to it now (FranciscoD, 16:21:49)
    3. A commblog post was published: https://communityblog.fedoraproject.org/where-point-newcomers-fedora/ (FranciscoD, 16:22:47)
    4. We'd also sent an e-mail out to the announce ML: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/message/6JA5JCI2GUUCMRPCVRMUUHVOMYB6HDWD/ (FranciscoD, 16:23:41)
    5. Leave #16 open for time being - until we put metric collection in place (FranciscoD, 16:26:04)
    6. Column idea: Help wanted Wednesday: https://pagure.io/fedora-commops/issue/100 (FranciscoD, 16:28:42)
    7. ACTION: everyone Please leave your comments on ticket CommOps ticket#100: Help wanted wednesday: https://pagure.io/fedora-commops/issue/100 (FranciscoD, 16:33:03)

  6. Fedora web space audit: https://pagure.io/fedora-join/Fedora-Join/issue/21 (FranciscoD, 16:33:28)
    1. https://apps.fedoraproject.org/ (skamath, 16:35:28)
    2. One goal of audit, among others, is to identify entry points that fedora join can then manage (FranciscoD, 16:39:11)
    3. ACTION: skamath make a list of public facing sites that would potentially act as entry points for new contributors and comment on the ticket? (FranciscoD, 16:41:28)
    4. ACTION: FranciscoD speak to various web ninjas to ascertain what metrics we should collect for the audit (FranciscoD, 16:42:45)
    5. ACTION: FranciscoD update ticket 21 with task assignment info (FranciscoD, 16:43:03)

  7. Propose stage 2 to the Fedora Council as a project-level objective: https://pagure.io/fedora-join/Fedora-Join/issue/19 (FranciscoD, 16:43:27)
    1. ACTION: skamath go through ML thread to understand better what ticket #19 requires, and then volunteer for the position if they're up to it (FranciscoD, 16:48:03)
    2. ACTION: dhanesh95 go through ML thread to understand better what ticket #19 requires, and then volunteer for the position if they're up to it (FranciscoD, 16:48:07)
    3. skamath dhanesh95 happy to pursue https://pagure.io/fedora-join/Fedora-Join/issue/19 (FranciscoD, 16:48:32)
    4. ACTION: FranciscoD update https://pagure.io/fedora-join/Fedora-Join/issue/19 with info (FranciscoD, 16:48:53)

  8. Resurrect the mentoring programme: https://pagure.io/fedora-join/Fedora-Join/issue/18 (FranciscoD, 16:49:29)
    1. ACTION: FranciscoD Seek out experienced Fedora contributors to collect advice on resurrecting the mentoring programme (FranciscoD, 16:51:00)

  9. Resurrect the classroom programme: https://pagure.io/fedora-join/Fedora-Join/issue/22 (FranciscoD, 16:51:14)
    1. Already set up pretty well: https://fedoraproject.org/wiki/Classroom (FranciscoD, 16:51:31)
    2. IDEA: How about we have a team of classroom wranglers that do the organising. People that want to take classes contact them, pick a slot. The wranglers book the room, send out the e-mails etc? (FranciscoD, 16:53:48)
    3. ACTION: FranciscoD document ideas in ticket (FranciscoD, 16:56:38)
    4. https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative (FranciscoD, 16:57:31)

  10. What can we do better (here, there, anywhere?) (FranciscoD, 17:01:20)
    1. ACTION: dhanesh95 find link to Fedora University ticket and send it to ML (FranciscoD, 17:02:32)
    2. If you have anything - use "plussing" - point out an issue, and follow up with a suggestion (FranciscoD, 17:03:24)
    3. ACTION: FranciscoD send out meeting logs to MLs (FranciscoD, 17:04:34)


Meeting ended at 17:07:00 UTC (full logs).

Action items

  1. everyone Please leave your comments on ticket CommOps ticket#100: Help wanted wednesday: https://pagure.io/fedora-commops/issue/100
  2. skamath make a list of public facing sites that would potentially act as entry points for new contributors and comment on the ticket?
  3. FranciscoD speak to various web ninjas to ascertain what metrics we should collect for the audit
  4. FranciscoD update ticket 21 with task assignment info
  5. skamath go through ML thread to understand better what ticket #19 requires, and then volunteer for the position if they're up to it
  6. dhanesh95 go through ML thread to understand better what ticket #19 requires, and then volunteer for the position if they're up to it
  7. FranciscoD update https://pagure.io/fedora-join/Fedora-Join/issue/19 with info
  8. FranciscoD Seek out experienced Fedora contributors to collect advice on resurrecting the mentoring programme
  9. FranciscoD document ideas in ticket
  10. dhanesh95 find link to Fedora University ticket and send it to ML
  11. FranciscoD send out meeting logs to MLs


Action items, by person

  1. dhanesh95
    1. dhanesh95 go through ML thread to understand better what ticket #19 requires, and then volunteer for the position if they're up to it
    2. dhanesh95 find link to Fedora University ticket and send it to ML
  2. FranciscoD
    1. FranciscoD speak to various web ninjas to ascertain what metrics we should collect for the audit
    2. FranciscoD update ticket 21 with task assignment info
    3. FranciscoD update https://pagure.io/fedora-join/Fedora-Join/issue/19 with info
    4. FranciscoD Seek out experienced Fedora contributors to collect advice on resurrecting the mentoring programme
    5. FranciscoD document ideas in ticket
    6. FranciscoD send out meeting logs to MLs
  3. skamath
    1. skamath make a list of public facing sites that would potentially act as entry points for new contributors and comment on the ticket?
    2. skamath go through ML thread to understand better what ticket #19 requires, and then volunteer for the position if they're up to it


People present (lines said)

  1. FranciscoD (179)
  2. skamath (81)
  3. dhanesh95 (52)
  4. zodbot (23)
  5. Southern_Gentlem (3)
  6. mailga (2)
  7. linuxmodder (0)
  8. jflory7 (0)


Generated by MeetBot 0.1.4.