Discussed in 2015-12-08 meeting.

decause plans to discuss the possibilities of when a vFAD would be most helpful and effective with jkurik and maxamillion. This is a long-term planning effort, and once more information is available, this ticket will be updated, or this ticket will be closed in favor of more specific tickets about organizing the vFAD.

This will be on the shelf for a while.

Discussed in 2016-05-31 meeting.

Time to unbury this ticket now. ;)

Summer is getting into full speed and the time to begin planning our virtual Fedora Activity Day (FAD) is close. We originally discussed this ticket six months ago and were going to defer it until CommOps grew some more and Fedora Hubs was making steady progress. I think both requirements have now been fulfilled!

Our wiki page

We now have a wiki page for our own vFAD proposal. This will be where we begin working on what the event will consist of, what objectives we want to knock out, and working on some milestones that we need to accomplish in order to pull this off.

Organizing our vFAD

There are some existing guidelines on how to organize a FAD. While it's most likely not going to be possible for us to request a travel budget for the event (thus this primarily being a virtual event), some of these guidelines will not apply, like a travel budget.

However, the page first suggests beginning with the expected impact we would like to get out of the event and how it will help accomplish the Fedora Mission. Either at our next meeting or hack session, it would be a good idea to brainstorm what we want to accomplish at this event and how we want to go about doing that.

Then, we should probably move on to picking a date and time for the event (as well as duration). I'm inclined to think July would be a better time to hold this event.

Other thoughts

Anyone else want to throw some ideas into the pit for now? If not, we will hold discussing this next time CommOps meets.

Discussed in 2016-06-07 meeting.

Updated purpose, impact, objectives

Based on discussion we had in our meeting today, I have created a preliminary "proposal" for '''what we want to accomplish''' and '''how it will benefit Fedora''' on the wiki page. You can read particular sections here.

To summarize in this ticket, I will do a little copy+pasting of the new additions to the wiki page.

Purpose

• Our purpose is to complete the following primary goals:
• Clean up the existing queue of tickets and follow up on older / pre-existing tasks
• Also related: clean up and better organize our own workflow in a more centralized way (there's lots of stray git repos and Etherpads - finding a way to unify this information would be helpful for new contributors to CommOps)
• Work on new contributor on-boarding, specifically with the Badges series proposals that are in progress
• Build new ways CommOps can help contribute to supporting other sub-projects in Fedora
• In addition, we will attempt to complete the following '''secondary''' goals as time allows:
• Better categorize and organize the wiki
• Develop a "satisfaction survey" for CommOps members to (anonymously?) provide feedback about how engaged they feel, what they think is working, what isn't, how we could improve, etc.
• Contribute art assets to the Badges Trac where possible

Impact

The completion of these goals will create the following positive change within the project:

On-boarding

• One of the founding principles and goals of CommOps is to help make it easier for new contributors to get involved with the project and help spend time and effort on the project.
• There are existing efforts in CommOps to help improve the process for newcomers by taking advantage of Fedora Badges, improving existing documentation by various sub-projects for getting involved, and devising solutions of how to make the barrier to entry much lower. Taking explicit time to focus on the existing tickets and ideas related to on-boarding specifically would allow us to help improve the "first experience" of a new contributor to Fedora IMMEDIATELY and DIRECTLY. This is work that would improve that user experience and draw more contributors into Fedora.

Increased efficiency

• As far as Fedora goes, CommOps is a newer sub-project and started (officially) around October 2015. When we first began, it was hard to be able to tell how things would go, and many of the original methods of organization and initial guidelines for how CommOps operates could be updated based on the current context of how things are now.
• At the vFAD, we would be able to spend time looking at our own tooling (Trac tickets, Pagure repos, etc.) and devise ways to improve organization, construct an efficient and effective workflow, and spend time improving the "foundation" of the "CommOps house". Ideally, this would allow us to more efficiently respond to new tickets, follow up on old ones, and keep current on where our time and efforts are best spent.

More heat and light

• Lots of things have started happening since CommOps started, and some older tasks and tickets have been neglected because of other (important) tasks. Having a time dedicated to revisiting older items and spending time working on them (or closing them, if necessary) would help us keep on top of tasks related to our objectives as a sub-project.
• These changes would benefit Fedora as a whole because it will allow us to better spend our time and efforts supporting Fedorans across the project in more relevant and important ways in the long run.

These outcomes connect with the following Fedora Community Objectives by advancing the development and progress of all Fedora sub-projects in a general sense, and it allows us to better bring new contributors into Fedora. With the on-going development of Hubs in progress (and not too far away from being in a "first demo" state), it is important for CommOps to spend the time and effort readjusting our own practices, supporting the on-boarding methods of other teams, and catching up on the queue of tasks so as to be prepared for a new generation of contributors and contributions, but also being able to support the existing contributors and contributions in the best way possible.

Feedback, then choosing dates

Feedback on the above proposed purpose, impact, and general objectives is welcome. If you have ideas of things to add (or change, or remove) from this list, please feel free to leave your thoughts, opinions, and ideas as a reply to this ticket.

Once we have a general consensus on this ticket, we can move forward on selecting dates for the vFAD and organizing the final planning details / logistics.

+1 I can't guarantee that I can make it to the vFad, but I am interested and the scope sounds good.

+1, definitely a go. Also, would be nice to have video conferencing through FOSS software such as Ring [1] or Tox [2].

[1] - https://Ring.cx

[2] - https://tox.chat/

+1 not sure if I can be all the time, GSoC priorities

Discussed in 2016-06-14 meeting.

A mailing list post was just made to try to determine which of the possible dates work for the most number of people. Anyone interested, please make sure you fill out that form! Thanks. :)

Discussed in 2016-06-28 meeting.

Postponing for Flock

As discussed in our meeting last week, we're going to postpone the plans for organizing this event to focus on the CommOps workshop at Flock 2016 (detailed in ticket #79).

I'd like to bring the (v)FAD topic up at Flock to work on planning details on it then. For the time being, going to remove this ticket from the meeting agenda and revisit at a future date.

Adding this to this weeks' agenda for further discussions. We can plan for this now :)

For now, going to leave the link to this super amazing awesome incredible repository for organizing thoughts and ideas into useful, visual planning that helps track and measure success…

I think in lieu of the Flock 2016 workshop we held, this ticket has stagnated, and I will close it now. We can revisit the idea of holding a FAD in the future, but it's probably best to start fresh if we want to do that than pick up this ticket again.