During the diversity team meeting today, we agreed upon defining diversity team's next 6 months goals/tasks. These will be the achievements we think, we can put in our next year council report of diversity team.
I am glad that I could invest a lot of time in the diversity team work, but it will be better that everyone (in the core team), own these tasks evenly and make them a success.
Owner of the task will get help from all the other team members, can also on-board volunteers and new members while performing the task. As on-boarding is the on-going process, not something which can be done in a week or two.
Here are major tasks with the ownership listed, this needs feedback and can be altered too in terms of ownership, but the objectives remains the same, in order to be practical and to maintain the quality of the tasks -
?? - It means consent is pending from owner.
All these are major/big goals and hence need an individual leader to lead them in right direction. Owner means, you are responsible to open a ticket/tickets for the objective, handle budget if any, need to co-ordinate with Fedora Magazine/Commblog to publish articles, distribute sub-tasks among team members and motivate them (by pinging in IRC/telegram etc) to finish the tasks and follow up . I know and experienced it needs a lot of time and energy to accomplish all of these thing and hence the time line is realistic and of 6 months.
@jflory7 @jonatoni @bee2502 ^^
Metadata Update from @amsharma: - Issue priority set to: by next release - Issue set to the milestone: Future releases - Issue tagged with: needs feedback
I will take the responsibility to organize FWD, including the article/agenda/budget etc (everything is needed). @bee2502 we can coordinate together to plan it, right?
Related to the other tasks we can discuss about them during our next meeting with @bee2502 @jflory7 and other members so we can have more feedback.
I will be passive till November 2017. I don't think I am up for this responsibility as I have prior commitments outside of Fedora which will take up most of my time.
@jonatoni thanks a lot for taking the ownership :) @bee2502 thanks for informing.
I will take Fedora Women Day (India) event ownership and will collaborate with @sumantrom on this.
Bee and Justin will be unavailable until November, 2017. So the tasks will be open for some one to volunteer - "Searching and Appointing new Fedora Diversity Adviser "
@bee2502 @jflory7 If you are available to take up some tasks and lead them, please check the list above and take the ownership, will be helpful. Thanks.
bee2502 @jflory7 If you are available to take up some tasks and lead them, please check the list above and take the ownership, will be helpful. Thanks.
There is one open task "Searching and Appointing new Fedora Diversity Adviser " - I am not sure if this is still valid. Even if it is, I don't think I am qualified to do that.
bee2502 @jflory7 If you are available to take up some tasks and lead them, please check the list above and take the ownership, will be helpful. Thanks. There is one open task "Searching and Appointing new Fedora Diversity Adviser " - I am not sure if this is still valid. Even if it is, I don't think I am qualified to do that.
May be, be a little more creative and expand the goals :) . Add translation team collaboration as team goal and take the ownership to lead it :wine_glass:
Metadata Update from @jflory7: - Issue tagged with: internal operations
Can we close this ticket since individual tickets are now open?
@amsharma I have added a ticket related to language inclusion #33 but would prefer it to be discussed during FLOCK or a team meeting first, divide it into sub tasks and then take ownership of those.
Can we close this ticket since individual tickets are now open? This ticket is to track annual goals of team so it will remain open until next diversity team report to council and there will again one for next year to track annual goals with new tasks. @amsharma I have added a ticket related to language inclusion #33 but would prefer it to be discussed during FLOCK or a team meeting first, divide it into sub tasks and then take ownership of those.
Can we close this ticket since individual tickets are now open? This ticket is to track annual goals of team so it will remain open until next diversity team report to council and there will again one for next year to track annual goals with new tasks.
Thanks for doing it. +1 for team meeting. Flock session agenda is different, which is already shared and approved as diversity session. Though we can have separate meeting at flock to discuss this with team members as and when time permits.
@bex @jflory7 do we have any update on Fedora Diversity Adviser for the team. TIA
Going good here according to what we targeted in this year. Nice so far. We need to plan next year objectives and Goals very carefully, in such a way that they will have impact and should be achievable within a year without too much pressure.
I would like to purpose a diversity team meeting during OR after devconf and before FOSDEM for this specifically. Defining goals is the most important milestone, it defines path for the rest of the whole year. @bee2502 @jonatoni @jflory7 Please comment on this one on priority as if we want to plan it, then this is the high time to do it :) Thanks.
Metadata Update from @jflory7: - Issue tagged with: meeting
Discussed in 2017-12-08 meeting.
We discussed having a short meetup during the DevConf / FOSDEM period for the Diversity Team to focus on our goals for 2018. Most of our team members will be at DevConf, but it's not yet certain for FOSDEM. One idea was having a 3-5 hour meeting during DevConf to whiteboard out ideas and plan for the next year. This is the most realistic option for us and should be possible.
We talked briefly about a 2-in-1 FAD for CommOps and Diversity, but because of time constraints and different goals / objectives, this is difficult to do. We planned to revisit next week to see if this is a realistic option or not.
We will open new ticket for next year's goal. Just to track, we will include https://pagure.io/fedora-diversity/issue/47 as one of our objectives.
@jflory7 @bee2502 @jonatoni @chhavi you guys are awesome and totally helped in every single way to achieve Fedora diversity goals in 2017 :) Now as the new year is approaching, we need to work on our new goals and objectives - here is the draft - https://pagure.io/fedora-diversity/issue/48 . I request all of you to please review and comment. Hope to have another brilliant year, thanks everyone :)
and I am glad that we have done almost everything, which we have planned. Closing this ticket now and discussion for devconf meetup can take place in - https://pagure.io/fedora-diversity/issue/48
Metadata Update from @amsharma: - Issue assigned to amsharma - Issue close_status updated to: Complete
Btw I think would be very good to write an article and share with the others what we have done for 2017. Would be great than even others know what Diversity Team has done so far ;)
@jflory7 @bee2502 @jonatoni @chhavi you guys are awesome and totally helped in every single way to achieve Fedora diversity goals in 2017 :) Now as the new year is approaching, we need to work on our new goals and objectives - here is the draft - https://pagure.io/fedora-diversity/issue/48 . I request all of you to please review and comment. Hope to have another brilliant year, thanks everyone :) Btw I think would be very good to write an article and share with the others what we have done for 2017. Would be great than even others know what Diversity Team has done so far ;)
Can we have a like/love button in pagure for liking the comments as well, I can't agree more :)
@amsharma hahaha I was thinking the same :P we can propose this to infra team ;)
I noticed there is a draft in the Community Blog titled: Fedora Diversity Team – 2 years and Running. We could update that and publish that post to cover our progress over the last year.
I noticed there is a draft in the Community Blog titled: Fedora Diversity Team – 2 years and Running. We could update that and publish that post to cover our progress over the last year. +1
Metadata Update from @jflory7: - Issue untagged with: meeting, needs feedback - Issue set to the milestone: Fedora 28 (to May 2018) (was: Future releases)
Login to comment on this ticket.