After the news recently that Microsoft gave the Mono Project over to the Wine team, it has now been moved over to the Wine GitLab. Plus, some changes for Wine contributors may be coming with a new Code of Conduct.
A bunch of changes were announced on the Wine Developer mailing list from Alexandre Julliard. Which include some modernisation for the project. The Wiki was moved over to their GitLab along with appdb, vkd3d and wine-staging having their own Wiki too.
The Mono Project is now hosted directly by the Wine team on their GitLab, plus they've upgraded the server hardware for their GitLab which is "now noticeably faster" which will hopefully aid development for all the contributors long into the future.
Sadly they've had a bit of a spam problem which is why GitLab issue trackers were disabled, but they're going to be re-enabled with "an explicit user verification step, modelled along the procedure used by Freedesktop.org".
Lastly, along with the new sign-up process, they're currently looking into forming a proper Code of Conduct to "spell out our expectations". They're currently looking into using the popular Contributor Covenant, which was designed especially for open source communities. The Contributor Covenant is pretty simple to understand, and a lot of it is based on just reinforcing acceptable behaviour, not particularly different to the rules most forums have (including our comments and forum).
back to serious alexandre julliard approves recently on wine git remi bernon idea around gstreamer alternative
https://gitlab.winehq.org/wine/wine/-/merge_requests/6442
remi bernon use ffmpeg, show heavy activity maybe can improve some video playback in future
i actually stay testing
Last edited by mrdeathjr on 12 September 2024 at 1:02 pm UTC
Quoting: LamuNobody's in favour of these goofy, overbearing 'covenants' (as cultlike as it sounds).Any normal person is. The only people usually not in favour of them are the exact type of assholes they aim to keep away. It's utterly daft to be against such simple rules. Too many people turn into keyboard warrior idiots.
Quoting: Liam DaweThe only people usually not in favour of them are the exact type of assholes they aim to keep away.Hear fucking hear.
Adopting a decent CoC does not suddenly make the sky fall on developers' heads. The lack of one does not suddenly make a particular software product apolitical (hint: there is no such thing when it comes to being part of a group of people where not only do you have access to technology, but the free time and skills training on top). So if we want to encourage healthy collaboration on a project, we need to do so with a common basic understanding of respect and human decency.
Clearing murky waters and saying 'yes, being a shitty person will get you ostracized' in writing means much less wiggle room for them to try and get out of the repercussions of their own actions.
(Also, I'm sick of anti-CoC people essentially just using it as a dogwhistle for racism, sexism, homophobia and transphobia - absolutely hilarious to me considering how many fellow trans people work in open source and tech in general. I can virtually guarantee that at least a good chunk of the tech in your phone and Linux distro of choice has been worked on by a trans person for your benefit.)
Quoting: Liam DaweThank you for saying this. I was waiting for someone to criticize it in the comments the moment I read the title of the article. While "covenant" might come off as an odd word to use, it's exactly as you said and then some. If people don't like rules of civility, then GTFO. Projects are better off without you and your ilk.Quoting: LamuNobody's in favour of these goofy, overbearing 'covenants' (as cultlike as it sounds).Any normal person is. The only people usually not in favour of them are the exact type of assholes they aim to keep away. It's utterly daft to be against such simple rules. Too many people turn into keyboard warrior idiots.
Take for example this one.
It claims to be specifically designed for open source communities, but it's easy to see this one being implemented on a forum or really any place where people communicate which each other.
Were I to design one for open source community COC's, I would at least include clauses forbidding significant amounts of off topic communication, include a definitions clause at the top and included a policy with dependency projects.
Last edited by LoudTechie on 13 September 2024 at 8:42 am UTC
Quoting: KithopThe lack of one does not suddenly make a particular software product apolitical (hint: there is no such thing when it comes to being part of a group of people where not only do you have access to technology, but the free time and skills training on top).
I like this CoC over many others as if you read it and understand it, it is in fact apolitical which all CoC's should be IMO. As a CoC needs just be there so EVERYONE treats each other like a human being no matter their Race, Gender, sexual orientation or religion. I have been in a few communities their CoC's/rules lean one way or the other and let me tell ya that can be and is toxic as hell no matter which side its coming from. CoCs like this one should hold everyone equally and even if there are racist, sexist, or phobic people in said communities maybe they learn how to see people for humans no matter and learn to treat people like a decent human being should no matter if its online or IRL and if not they get banned. IMO this is how you show people that are racist,sexist or phobic they are wrong and should change, not by spitting the toxicity back at them.. that just makes them worst. There are a few CoC's for a couple projects I seen that leaves it a bit open ended and frankly is toxic AF.
Last edited by tohur on 14 September 2024 at 3:44 am UTC
Quoting: tohurI like this CoC over many others as if you read it and understand it, it is in fact apolitical which all CoC's should be IMO.
Oh totally - the Contributor Covenant is a good solid standard. I meant more: life isn't apolitical - the circumstances that lead some people to be able to contribute to FLOSS and not others is inherently derived from political actions. Which countries invest in related education (and which may not even have the resources at their disposal to offer it), what sort of systemic issues certain groups of people have to navigate and contend with versus others, that sort of thing.
So yes - you should *strive* to be as neutral as possible, but that involves recognizing that everyone comes from different backgrounds - by being equitable, it allows the work to be 'apolitical' in that we don't have to fight to be respected, but on the other hand, it *is* 'political' in that it's expressly countering some of those issues and biases baked into society in the first place.
See more from me