Ok, not that “Hello”. I’ve been writing quarterly updates on what I’m working on to help the Fedora Community. If you’re new to the party, welcome. I have the privilege of being the current Fedora Community Action and Impact Coordinator. I wrote last week on the Red Hat Community blog about what this role means and how it interacts with the world.
So, without further ado, let me update you on what I’ve been working on relative to my goals.
How’d I do?
I listed these goals in my last update:
- Get to know the community
- FAmSCo and FOSCo
- Fedora Docs Publishing
Get to know the community
As I keep saying, this is a never-ending goal. I keep meeting amazing, passionate, intelligent and helpful contributors to the Fedora Project. As part of this goal I attended both DevConf.cz and FOSDEM. At DevConf.cz I got to focus on one area of the project by participating in the Diversity FAD. FOSDEM was its usual glory and I got to interact with the EMEA Ambassadors there.
I’ve started publishing my conference and travel schedule in my weekly Slice of Cake updates. If we’re going to be near each other, let me know so we can meet and say “hello.”
Speaking of my weekly updates, they are designed to be quick takes on the highlights of the actual things I did and not a high-level summary like this post. Are these (or this post) useful to you? Let me know in the comments, by email, on IRC, or via whatever other communication method you like. Help me with your motivational comments and constructive feedback please!
As you know, Budget.Next is the project to change the way Fedora manages money. A new fiscal year for Fedora began on March 1, 2017. The budget has been updated by the council to get us through the end of Quarter 1. There is a lot of conversation going on about the mission statement right now, so the council hasn’t fully allocated the budget for the year.
However, allocations are policy decisions. The budget process is a mechanical one designed to keep our spending and income open and transparent. To that end, the regional treasurers and credit card holders (Neville Cross (Yn1v), Mohd Izhar Firdaus Ismail (izhar), Abdel G. Martinez L. (potty), Zacharias Mitzelos (mitzie), Joerg Simon (jsimon), and Andrew Ward (award3535)) and I have been putting our transactions into a Pagure repository and now we have a website to view the results on. The site is currently being manually built, but is usually current. I haven’t published the Fedora Community Blog post announcing the site that I promised last time, yet. I am sorry about that. It is still a goal of mine to get it out soon. The highlights are:
- Built a data storage system using ledger, a plain text accounting system that has been packaged in Fedora for a while.
- Began storing transaction data in a Pagure repository.
- Wrote some basic reports to show the overall data and position for our project and the regions.
- This quarter we began publishing the new budget website.
My work on updated reimbursement policies and proposals for more formalized methods of using sponsored travel are stalled right now as I have too much to do. I hope that I can get to these in the upcoming quarter.
Interested in helping out? Feel free to contact me right now. On the technical side, I’d love some help from folks interested in Ruby, AsciiDoc, Jenkins, testing (CI – Continuous Integration) and automated deployments (CD – Continuous Deployment). On the policy and procedure side, let me know about ideas and help me draft a great way forward for us. This is a great project for new contributors and junior coders or system administrators.
FOSCo (and FAmSCo)
The Fedora Ambassador Steering Committee (FAmSCo) has been working well and I am seeing great stuff. I am so happy to see this group of contributors tackling so many tough issues. The ideas behind FOSCo have been shelved by the council and there is now a new Mindshare position. I am looking forward to seeing where Robert Mayr takes it. I hope you’ll join me in helping him succeed.
Fedora Docs publishing
Our documentation reboot work continues. The documentation team has decided to move to AsciiDoc and modular writing. The process has been very slow and this is an area where new contributors are definitely welcome.
I’ve been working on my AsciiBinder based proposal for the new tooling using the Fedora Budget website as a proof of concept. I’ll include more details when I write the formal site announcement.
Interested in helping out? Get involved with the Docs Project or feel free to contact me right now. On the technical side, I’d love some help from folks interested in format conversions (DocBook->AsciiDoc – think perl, python, bash, etc.), ruby, AsciiDoc, Jenkins, testing (CI – Continuous Integration) and automated deployments (CD – Continuous Deployment). We also need help on the writing side with modular writing and general updates.
Planning for Flock 2017 is in progress. Flock will be held in Cape Cod, Massachusetts, USA from 28 August – 1 September. We are making some changes to the registration and CFP engine before we make the formal announcement. If you haven’t already, join the flock-planning mailing list to stay informed and help out.
I successfully packaged DayJournal for Fedora. It was a rewarding and educational experience to have gone through the packaging process. Even if you don’t ultimately publish a package, you should try to package something to understand the process.
For the next few months, I’d like to focus on the following:
- Get to know the community
- Fedora Docs Publishing
I am continuing my work on four of my goals for the new quarter. I’ve got a lot of conference related travel as well as some personal holidays coming up so I don’t know that I can take on much that is new. These remain critical priorities for me, so this is where I want to invest my energy.
I’ve talked a lot about what I hope to accomplish in the future while describing my outcomes above. Therefore, I will just list summary goal statements for the next quarter below:
- Get to know the community: I want to meet you! Where are you? Who are you? Let’s meet!
- Budget.Next: I’d like the website to auto-publish after commits to the repository.
- Fedora Docs Publishing: I’d like the documentation team to have a full proof of concept to test of my proposed workflow. Ideally, I’d like us to publish F26 this way.
- Events: Flock will be ready to go. I’ll successfully represent Fedora at the events I travel too. Other events that want my help will have it.
Let me know if I’ve missed anything. Let me know if you have input into what I’m doing or want to help. And by all means let me know what we can work on together. I can’t do it all alone (and I don’t want too!) and I can’t even help with everything I want to, but I want to make sure my work is helping the community move forward.