I'm proud to announce the Leadership Committee's 2017 election results. The results were prepared Matt Okeson-Harlow, processed by Andrew Hume, and confirmed by Scott Murphy.
Thanks to Paul English, George Beech, Ski Kacoroski, and other members of the board for supporting the Leadership Committee during the elections.
Extra special thanks to the Leadership Committee this year. Without having any incumbents re-run, there was much more work leading up to the election compared to usual. Our success is thanks to Adam Luck, Andrew Hume, Matt Okeson-Harlow, Scott Murphy, and Trevor Thorpe. They are our Leadership Committee.
I'd also like to recognize our exiting Board Members for their service. Thank you for your service Atom Powers, Paul English, Ray Thrush, and Ski Kacoroski.
Ski has served eight terms, which is the longest of any Board Member in LOPSA history. Thanks for your time and dedicatation, Ski. We wish you the best in your future endeavors.
The elections for the 2017 LOPSA Board of Directors has concluded. The winners are Drew Adams, Andy Cowell, Aleksey Tsalolikhin, and Danielle White.
We present below the report of the independent monitor, Andrew Hume. The Leadership Committee
Report on the 2017 election.
The 2017 LOPSA election was conducted as it has been in the past. Votes are automatically collected by software run by Matt Okeson-Harlow and at the end of the election are captured and processed by the Meek single transferable vote method. The software is available at http://www.openstv.org (although I just did a ‘yum install openstv’) and if you'd like to run the election yourself, the raw ballots are presented below. I used version 1.7 of OpenSTV.
For a more detailed explanation of the overall method, material may be found at http://www.openstv.org and Wikipedia.
The abbreviated summary for this election follows below.
Election title: LOPSA Vote 2017
Method: Meek STV with Droop-Dynamic-Fractional threshold
Ballot Cleaning: San Francisco
Number of total ballots: 54
Number of invalid or empty ballots: 0
Number of ballots used in the count: 54
5 candidate running for 4 seats.
Round 1: Aleksey Tsalolikhin and Danielle White are elected.
Round 2: Transferring surplus votes; no new electees.
Round 3: Transferring surplus votes; Andy Cowell and Drew Adams elected.
The election is over since all seats are filled.
The votes in BLT format (md5=c1d76489ea5fe1176d79d251adbbc022)
1 1 4 3 5 2 0
1 4 1 2 0
1 3 5 4 1 2 0
1 4 5 1 2 3 0
1 4 1 2 3 5 0
1 4 3 1 2 5 0
1 5 4 3 2 1 0
1 3 4 1 0
1 1 4 3 2 5 0
1 4 1 5 3 2 0
1 4 1 5 2 3 0
1 4 5 2 1 3 0
1 4 2 5 3 1 0
1 4 1 2 5 3 0
1 1 4 2 5 3 0
1 1 3 4 2 5 0
1 1 4 2 3 5 0
1 1 4 5 2 3 0
1 1 5 2 3 4 0
1 2 3 5 4 1 0
1 1 4 2 0
1 4 3 1 5 2 0
1 5 3 2 1 4 0
1 1 2 4 5 3 0
1 2 5 3 4 1 0
1 1 2 4 3 5 0
1 4 5 2 3 1 0
1 1 4 0
1 4 1 3 5 2 0
1 4 2 1 5 3 0
1 2 1 4 5 3 0
1 5 4 3 1 2 0
1 5 1 2 4 3 0
1 1 3 4 5 2 0
1 3 4 5 2 1 0
"LOPSA Election 2017"
Once again, my apologies for having to split the posts. I believe I can manage it with just two posts this time. This was lightly edited to remove some of the noise from the transcript
As mentioned in the beginning of the transcript, we also have Danielle White's answers to these questions.
With the benefit of answering these after the #LOPSA-Live session (and thank you for this opportunity) I see overlap between these questions.
Question #1: I strongly feel that there exists interest but is from an audience who isn't seeing us right now. In part due to my role change in mid-2016, to a position where I am doing more development than operations, I found local Research Triangle chapters of some groups, such as Girl Develop IT and Women Who Code, of people in similar capacities. Generally, they don't know of LOPSA even though sysadmin tasks are part of their jobs. Locally there are employers where nobody defines themselves as a system administrator even though many are doing so.
My approach to address this is to work on getting LOPSA into those spaces and make the case for our relevance. I feel strongly that we can be of substantial benefit because what I often see there are people who are doing ops work without a lot of support, and there is a solid case that we will make.
A Research Triangle specific note: LOPSA is still listed as affiliated with North Carolina System Administrators (NC*SA) which effectively no longer exists at this point. The other group where LOPSA is known, TriLUG, does not have participation from the individuals I described above and, for a number of reasons, almost certainly will not.
Question #2: If you'll allow me to take advantage of knowing the next question I believe questions #1 and #3 are our biggest at this time. I don't wish to suggest that if we solve them we've solved it all, only that we must focus on those two right now because solving those are critical to anything more.
Question #3: I would love to say that there is a way to make LOPSA-EAST viable but I am doubtful right now. The best approach that I see here is to look for conferences that are gaining and work with them. In the Research Triangle there is All Things Open. Also, there are a number of DevOps Days conferences where we need to be.
Don't forget the second session on June 21 @ 21:00 Eastern
The following series of posts are the transcripts from candidates #LOPSA-Live session. We have a size-of-post limitation for these items so it will be split across four posts.
1 Slight editing was performed to remove blank lines and entry/exit messages
The Leadership Committee is conducting moderated LOPSA Live sessions on Freenode IRC network in the #lopsa-live channel. These sessions will be your opportunity to ask questions of the candidates running for the LOPSA board.
We have two sessions, which should accommodate most time zones:
The Leadership Committee is proud to announce your election slate:
We have four seats up for election and a fantastic set of five candidates. This is your opportunity to influence the direction of LOPSA over the next year.
Keep an eye out, we will be sending notice for the LOPSA Live sessions soon. We will have two sessions before the election closes, where you can ask questions from the candidates before you vote.
The elections are open until July 1, 2017 at 11:59:59PM Eastern Time.
LOPSA is your organization and you'll get out of what you put into it, please vote and participate. It will make the organization better for us all!
I would like to announce my candidacy for the LOPSA Board.
I am a long time contributing openSUSE Member and Advocate in Southern California. I have been organizing and working the openSUSE booth at the Southern California Linux Expo (SCaLE) since 2012. I was the main organizers of the openSUSE miniSummit at SCaLE in 2015. I have represented openSUSE at booths at various conferences over the years such as LinuxCon, South East Linux Fest, and others. I attend meetups usually giving out openSUSE install media, stickers and other swag.
We have a strong Southern California openSUSE community. The great people of our local community come from all kinds of backgrounds and all have different levels of technical ability. However, the thing that unifies us is not openSUSE but our strong desire to help each other contribute and participate in building a strong community and learning and growing together.
I love finding people who have a desire to contribute and learn and grow in a community and help them get pointed in the right direction. Get them plugged in with others like them… connecting these people together and watching the community from and grow from the interactions. Not only do I love doing this, but this is what I have been doing for many years in the openSUSE community.
What I have done in the openSUSE community I would like to now bring to LOPSA and help us grow and build stronger and more active local communities with a fun and energetic culture of collaborative learning. I think we have a good base to build on and would like to lend my experience to the board so we can get to that next level.
The League of Professional System Administrators
1200 Route 22 East, Suite 200
Bridgewater, NJ, 08807
Phone: (202) LOPSA01 (202-567-7201)Email: email@example.com