I vote a.
----- Original Message ----- | From: "Ted Gould" ted@gould.cx | To: "Inkscape Board" inkscape-board@lists.inkscape.org | Sent: Saturday, March 5, 2022 2:59:00 AM | Subject: [Inkscape-board] VOTE: Coordinator Job Description Update | | | B ackground | | We voted on a job description for a project coordinator. There was | some confusion on whether it was an employment situation or a | contractor. This is an update to the job description to hopefully | make it more clear on that point. To give appropriate credit the | changes were suggested by Karen and a recruiter at my work, I'm just | the scribe. You should read the whole thing, but an overview of | changes: | | * | Change it to say "This is a 12-month contract position" | * | Switched to an hourly salary range instead of a yearly one (more | common for contractors) | * | Removed mention of being an "equal opportunity employer" since we're | not an employer if we're a contractor | * | Cleared up the work times as they couldn't be available for all US/EU | work times (that's more than twenty hours) | | | Also, I've included the "To Apply to This Job" section that was | included on the website to ensure the PLC reviewed it. I made one | change there which was to change the email address for submission. | This is to help the anonymization process to ensure that committee | one doesn't see the unanonymized resumes. | | Personally, it took me quite a bit to understand the anonymization | process, but Karen was patient and it resulted in me trying to write | it down and her correcting me (several times). I wanted to include | that here in the background section as well for perhaps others who | were confused like I was. I don't think this changes anything, but | it seemed like the best place to put it. | | How the anonymization thing works: | | * | Applicants send resume/cover letter to Pono, he removes spam, but | generally keeps them and assigns a number to them. | * | Committee one prepares a list of questions and grading criteria for | those questions. | * | Pono sends those questions out to the applicants and they reply with | answers. | * | Pono then anonymizes the answers and sends the responses to committee | one for grading. Committee one selects their top candidates (ideally | three to four) based on the grading system they established earlier. | * | Meanwhile, committee two decides on the list of questions they intend | to ask along with a grading system they intend to use. | * | Pono schedules interviews between the committee two members and the | candidates that committee one selected along with giving committee | two members the resume/cover letter of the person they're | interviewing. | * | Committee two members grade their interviews using the rubric that | they'd created and submit their grading to Pono. | * | Pono churns the results and a contract is offered to the person | selected. | | Timeline | | To not mess up the timeline and then provoke more discussion I'm | planning to close this vote on Tuesday March 8th, 2022. Would be | awesome if folks could get their votes in before that. Votes | | | * | a. Update the job description and application instructions as | presented in this email. | * | b. Keep the job description as previously voted on. | * | c. Old one plus this change: ____________ | * | d. New one plus this change: ____________ | * | e. Stop the hiring process | | Job Description | | This role is open to everybody who fits the requirements. It requires | a good coordination, communication and community skills to knit | together a growing Free and Open Source project in an online space. | The job encompasses the following responsibilities and would require | availability for twenty hours a week so tasks should be prioritized | according to the project's needs and the available work time. | | Some training and skills hand-off will be made available from the | current volunteers to ease the use of tools and current project | processes. | This is a 12-month contract position, with a three month trial period | and an opportunity for extension after the first year. Depending on | experience the rate would be $28 to $43 per hour. | | We welcome candidates from a variety of backgrounds and experience | levels. All Inkscape contributors, including Inkscape staff, are | required to follow the Inkscape Code of Conduct. | | Project Coordination | | Watch over all communication channels and project activities, and | share timely and relevant updates between channels. Have excellent | awareness of happenings within the project and share information | between teams. | | Attend, assist, or organize meetings and their agendas for teams, | ensure teams record minutes and calendar entries are up to date with | all needed information. | | Make sure all parts of the project get attention and the resources | they need, bringing to the PLC any deficiencies. Identify community | weak spots. | Report monthly to the Leadership committee on the project's state of | health, progress and events. | | Community Management | | Direct new contributors to the right parts of the project when | available. | Help organize in person and online-only hackfests and other community | events. | Help write task list templates that volunteers can follow to perform | common project objectives consistently. | Contact previous contributors and see how they're doing and if they | had difficulties or needed tasks and direct them as needed. | | Funding Assistance | | Assist in preparing funding request with prepared PLC votes, ensure | they follow SFC rules and follow up. | Monitor on-going funded projects task lists, contact involved people | and periodically check in. | Keep accounts and budget up-to-date in a consistent online location. | Handle and follow up with reimbursements/payments and record their | completion. | Monitor current fund-raising efforts if any. | Manage Sponsors and make sure they get the perks, write articles in | case no volunteer can be found and have the correct expiry dates. | Check in with sponsors for renewal. | | Requirements | | * | Flexibility: This is a new position, we're sure it will evolve. | * | Speak and write English for online and in person communication. | * | Be available for some hours that overlap with EU/USA work times. | * | Self-motivated. Plan out your own tasks and execute them within a | reasonable time-frame. | * | Results orientated. Start planning by setting SMART objectives. | * | Experience in a volunteer organisation. | * | Ability to use on-line tools (Gitlab, Nextcloud, etc.). | * | Good time management and positive work/life balance | | | Nice to Have | | * | A familiarity with the Inkscape project or a comparable open source | project. | * | Some programming or documentation experience. | * | Familiarity with Software Development processes. | | Application Instructions | | Send your resume and cover letter to pono@sfconservancy.org . Please | customize your resume for this role. | In your email, tell us which timezone you are located in. | | We will work around your holiday celebrations and religious holidays, | and do our best to support your other obligations when scheduling | interviews. | An approximate application timeline is as follows: | | * | Resumes will be reviewed through March 25th 2022 | * | An email screening interview will take place with some questions for | you to answer. | * | Final video chat interviews will take place from April 3rd to April | 10th. The final interviews will ask questions about your skills and | experiences working on or volunteering with teams. | * | The Inkscape organizers and Inkscape Project Leadership Committee | (PLC) will review final candidate information and make a hiring | decision. The Inkscape PLC will approve the position and hourly | rates. | * | All candidates will be notified of our decision by April 17th, 2022. | | _______________________________________________ | Inkscape Board of Directors mailing list -- | inkscape-board@lists.inkscape.org | To unsubscribe send an email to | inkscape-board-leave@lists.inkscape.org |