Code of Conduct/Committee/Members
Code of Conduct for Wikimedia Technical Spaces |
---|
Principles |
Report a problem |
Handling cases |
Committee (members ) |
Amendments |
FAQ |
Members
Amir Sarabadani (Ladsgroup)
I am a Wikipedian and have been active in the Wikimedia movement since 2006, mostly in Persian and English Wikipedia and Wikidata. I have been active and contributed in technical projects such as Wikidata, MediaWiki core and its extensions, i18n, RTL, operations, cloud services, pywikibot, and I am open to help in any other areas if that's going to help the Wikimedia movement (I'm trying to keep track of my volunteer work in user subpage).
I want to make sure we have a welcoming space and collaborative environment for everyone so we all can thrive as a movement and as individuals. I consider everyone's responsibility to keep it safe and welcoming.
Egbe Eugene Agbor (Eugene233)
I am a Wikimedian and currently I coordinate a majority of the community projects which are conceived in Cameroon which are both technical and non-technical. This gives me a bright horizon on community needs and also insight on how these issues pertinent to the African continent could be addressed.
I have worked on several community projects and campaigns which can be seen on my user page.
Greg Grossmeier (User:Greg_G)
I'm a long time member of the Free Culture/Software communities doing everything from starting a local linux user group, working on a university OER project, intern and staff at Creative Commons, and now staff at the Wikimedia Foundation since 2013. These roles have been a mix of staff and volunteer which I hope brings a useful perspective. For these reasons and more I am excited to be a member of the Code of Conduct Committee to support this important work.
My name is Jay Prakash and Username is Jayprakash12345. I am Wikipedian since 2 July 2015. I had joined Wiki Technical Community in early 2017. I am mostly working on MediaWiki and its extensions. Where I work for User Experience. Currently, I am holding the volunteer lead developer role in meta:Indic-TechCom, where I am the primary source of Tool creation, RFC, Reports, etc.
I am willing to serve my term for Code of Conduct Committee.
Kamila SouÄkovĂĄ (User:VatBatCat)
I've been contributing to the wikis on a small scale for years (mostly typos and wikidata edits), and I've been working at WMF as a ServiceOps SRE for over a year. I have also been an active volunteer in several other open-source projects, most notably FreeBSD. As a young female-presenting person, I've experienced a wide range of behaviors from more established community members, which provided me with insights into how community culture affects its direction. As a member of the CoCC, I aim to approach situations with an open mind. To enable people from diverse backgrounds and foster meaningful contributions, we must welcome, understand and accommodate their differences.
Auxiliary members
Effie Mouzeli
Throughout my involvement in Wikimedia projects, I have actively contributed to various technical spaces, including but not limited to localization, documentation, and project coordination. I have participated in the localization of several Wikimedia software projects, such as MediaWiki extensions and tools, where I have gained a deep understanding of the technical aspects involved. I have led and facilitated several developer programs, Wikimedia Hackathon Satellite events, and technical community sessions both in Ghana and Africa at large. Additionally, I have been an active member of relevant Wikimedia technical communities, engaging in discussions, providing assistance to other contributors, and promoting collaboration.
I believe that a well-defined and strictly enforced code of conduct is essential for maintaining a positive and inclusive environment in Wikimedia technical spaces. It establishes clear guidelines for acceptable behavior, ensuring that all contributors can participate in a respectful and safe manner. The code of conduct fosters diversity, encourages open dialogue, and promotes the spirit of collaboration, which are fundamental values of the Wikimedia movement.
My name is Martin Urbanec and I work mainly on the Czech Wikipedia, where I serve as a current sysop, bureaucrat and a checkuser. From November 2016 to February 2019 I served as a Czech Wikipedia ArbCom member. In the technical community, I'm active mainly in the site requests field.
I would like to keep the technical community a friendly space to everyone, and I think the CoC committee is an important tool to handle that.
I am MusikAnimal. I've been a long-time user of Wikimedia projects, and have been contributing almost daily since March 2013. My home project is the English Wikipedia, where I serve as an administrator, CheckUser and AbuseFilter manager. Within the technical space, my work spans from contributions to MediaWiki core and a few extensions, while also maintaining a number of tools, gadgets, and bots. I am also a software engineer with Community Tech at the Foundation. I thoroughly enjoy the collaborative spirit of Wikimedia, and I feel lucky I've been part of the movement. Working together allows us to foster innovation and learn from each other. For this reason it's imperative that we maintain a healthy technical space through our Code of Conduct. Just as with content contributions, working within our technical space can have far-reaching effects, offering a great sense of reward. This has been my experience, and I look forward to helping ensure everyone gets to experience it for themselves.
I joined Wikipedia as an editor in 2014. Over the 9 years of being on Wikipedia and contributing on all things technical â ranging from user scripts, bots, bot libraries, web tools hosted on Toolforge, gadgets, modules and templates, patches to MediaWiki core and extensions â I have seen plenty of evidence of why it is necessary to have a well-enforced enforced code of conduct across all our tech spaces.
I believe that a strong code of conduct is crucial for fostering collaboration, and inclusive environments influenced by a broad range of perspectives result in better software. I have been in my fair share of conflict â including some which in my early days were poorly handled by me. These experiences have shaped me to take a more open-minded approach towards conflicts, and understand that dispute arises in every healthy community because everyone has the projects' best interests in mind. Acquiring the ability to recognise and address disagreements is an essential ingredient to development of software that works predictably and is sustainably maintained to meet the requirements of our users.