RE: androiddev.social/@MishaalRahm…
It’s worth repeating. Android is not a viable base for an independent or even just collaborative operating system. Android is Google and only Google’s project.
If you want to see an actually transparent, international, and collaborative system on phones, support @postmarketOS
🚨Breaking: Google will now only release Android source code twice a yearGoogle has announced that it will publish Android source code to AOSP in Q2 and Q4 of each year.
More details👇
🔗androidauthority.com/aosp-sour…
Breaking: Google will now only release Android source code twice a year
Instead of four times a year, Google will now only release Android source code to AOSP twice a year, once in Q2 and again in Q4.Mishaal Rahman (Android Authority)
💙🩷💜Ⓑⓡⓔⓣⓣ🐡🍉🐧 likes this.
reshared this
Anthropy
in reply to Thib • • •I mean, google's projects aren't even safe to google itself
I would much love a project like PostmarketOS to take off and become a serious contender to Android.
Right now it's still not there yet (at least in my limited experience), but with how well the developers are making use of the limited budget, and the backing of many great opensource projects, I have no doubt it'll move mountains.
Fell
in reply to Thib • • •Bonsai861
in reply to Fell • • •Tony Schmidt
in reply to Thib • •like this
Ozzelot, freechelmi and Wesley Moore like this.
f_underscore reshared this.
kcxt @ 39c3
in reply to Tony Schmidt • • •@opensourceit
forking AOSP would be a ridiculously huge effort, since Google has evolved to scale through increasing abstractions you need to have teams of people working maintenance like security fixes across bespoke compilers, apis and code, responsible for having compatible expensive test farms, and establishing governance for changing UI features, updating security APIs, and interacting with vendors.
To support that you would need funding that really can only be obtained by having lots of vendors using your OS, but vendors aren't gonna do that without the governence in place.
basically this is limitied to corporations and states.
elly likes this.
Tony Schmidt
in reply to kcxt @ 39c3 • •like this
Midwestern ally and freechelmi like this.
f_underscore reshared this.
kcxt @ 39c3
in reply to Tony Schmidt • • •@opensourceit more or less yeah that's my take.
I believe this is one of the reasons postmarketOS is better. We intentionally work towards decentralisation in a many2many style, so that the number of centralised components that could bottleneck the project are kinimal.
we aim to make it easier to set up your own paclage repositories, CI, and automated testing, and do t force people to pick a side by ensuring that our automated hardware testing allows one device to be tested from multiple gitlab instances.
the binary repo and tooling like pmbootstrap let you easily replace on the fly any part of the OS (same way you would replace a package on your desktop linux pc) since it's literally Linux. The immutable version will also make this possible
stavpup
in reply to kcxt @ 39c3 • • •Claudius
in reply to Tony Schmidt • • •@opensourceit the scale of a project like this means, it can't meaningfully be forked. You'd need a team of experienced developers just to keep up, let alone make some headway.
So
"fork": yes
Fork and be viable long-term: extremely hard
😩
Tony Schmidt
in reply to Claudius • •Claudius
in reply to Tony Schmidt • • •Claudius
in reply to Claudius • • •@opensourceit 2/ Even with this *much* smaller problem to solve, this project is not ready:
> The goal is to make postmarketOS usable for non-technical people too, but we are not there yet. Usability and most importantly stability issues need to be worked out first.
from: postmarketos.org/state/
So, I would say: no, postmarketOS *currently* is not an alternative. And I personally doubt it will be any time soon.
postmarketOS // State of postmarketOS
postmarketOSClaudius
in reply to Claudius • • •Claudius
in reply to Claudius • • •@opensourceit 4/4 Without backing of a steering entity and MASSIVE effort (human labour, infrastructure, money) I don't see this happening. To reach something that can even begin to compete with current Android or iOS, you'd have to be a pretty large company. Not even Samsung does its own operating system.
It would basically take a nation state or the EU to start from scratch and be competitive in 5 years.
kcxt @ 39c3
in reply to Claudius • • •@claudius @opensourceit you're largely spot on that the "damage" is largely device specific support at least from a hardware enablement standpoint.
We have a very upstream-first community (it's something we take extremely seriously for the obvious reasons in this thread but also because it is just the right thing to do) and as a result upstream projects also increasingly consider mobile usecases, for example GNOME's libadwaita graphics toolkit treats mobile as a first-class citizen, and all GNOME core apps works great on a phone through convergence.
Despite this, we're still operating at a very small scale when it comes to working on things for our own sake and we are still a while away from being able to fully fund even core maintenance of the project.
That being said, 2025 has imo been a year of preparation for us, we have improved our governance
... Show more...@claudius @opensourceit you're largely spot on that the "damage" is largely device specific support at least from a hardware enablement standpoint.
We have a very upstream-first community (it's something we take extremely seriously for the obvious reasons in this thread but also because it is just the right thing to do) and as a result upstream projects also increasingly consider mobile usecases, for example GNOME's libadwaita graphics toolkit treats mobile as a first-class citizen, and all GNOME core apps works great on a phone through convergence.
Despite this, we're still operating at a very small scale when it comes to working on things for our own sake and we are still a while away from being able to fully fund even core maintenance of the project.
That being said, 2025 has imo been a year of preparation for us, we have improved our governance with the aim of making it easier to grow the team and scale more horizontally, we also made a lot of progress towards automated testing which is gonna be huge!
With immutable pmOS also on the horizon I'm really excited for 2026 when it comes to reliability!
reshared this
kcxt @ 39c3, papiris and Neil Brown reshared this.
kcxt @ 39c3
in reply to kcxt @ 39c3 • • •@claudius @opensourceit
In the long term I think we'll grow to fill a niche and ideally be self-sustaining along with our community of contributors. We are always trying to bring users in and turn them into developers, return to when you could just tinker with your devices! Our next biggest hurdle is probably going to be figuring out how to collaborate with vendors and shipping pmOS out of the box.
There is also the growing inevitability of climate and economic collapse and an increasing necessity for longer lasting hardware, if there comes a time when Google/Android is no longer a viable option for the EU, I want postmarketOS to be there when that time comes
kcxt @ 39c3 reshared this.
Claudius
in reply to kcxt @ 39c3 • • •@cas @opensourceit thank you for the added details. I hope you were not offended by my post. I really like what you are doing. But it is a HUMONGOUS task that you picked. I would love nothing more than this to get funding to a degree where everyone could work on this as much as they wanted.
Basically, I wish the EU had given you the millions of euros it chose to burn up in AI subsidies.
Claudius
in reply to Claudius • • •kcxt @ 39c3
in reply to Claudius • • •@claudius @opensourceit thanks for the response! I'm definitely with you when it comes to funding heh, and no your description was pretty realistic imo, no offence taken.
the upside is that even if we don't succeed in taking over the world, the journey is absolutely one for a lifetime, it's amazing to be part of this project and work on something that brings joy to peoples lives today and now
Thib
in reply to kcxt @ 39c3 • • •thanks all for the excellent points.
One thing I failed to mention in my post is that I support @postmarketOS to help it grow to the point it can seek the public funding it deserves to become a general public solution.
I support financially so the team can
- Go from a prototype to a MVP
- Identify what it’s missing to become mainstream
- Make a case for it to the relevant funders
Individuals alone won’t fund the project, but we can kickstart its next phase.
Loïc Rouchon
in reply to kcxt @ 39c3 • • •Tony Schmidt
in reply to Loïc Rouchon • •Loïc Rouchon
in reply to Tony Schmidt • • •Loïc Rouchon
in reply to Loïc Rouchon • • •1. Going Android (Pixel or Fairphone), 7 years of software update, which is better, but still Android
2. Going Murena /e/OS, but doubts regarding apps compatibility (more on that later)
3. Going SailfishOS with @jolla, but still that app compatibility
Loïc Rouchon
in reply to Loïc Rouchon • • •Options 1. and 2., still are Android dependent, so not changing the status quo, even though /e/OS is a privacy improvement.
Options 2. and 3., problem with app compatibility as no Google Play services.
Loïc Rouchon
in reply to Loïc Rouchon • • •Loïc Rouchon
in reply to Loïc Rouchon • • •So unless we get EU regulation that websites (of critical services?) should be accessible without proprietary applications and should rely instead on your choice of MFA/TOTP applications, we are pretty much stuck.
So funding is important, but we need more than that. We need regulations to ensure critical services are accessible without requiring proprietary applications which are only available on proprietary systems.
freechelmi
in reply to Loïc Rouchon • • •pabloyoyoista
in reply to Claudius • • •@claudius
In fully agreement with @cas, I think your assessment is fair, even if it can sometimes hurt seeing it written like that. Personally, one of the things that motivates me the most is that we all know that the task is humongous... But honestly, so was the effort needed to get from news.ycombinator.com/item?id=1… to where we are now.
We (postmarketOS but also the whole mainlineLinux Mobile community: Mobian, Phosh, Plasma Mobile, etc.) have already succeeded in something that is a humongous task, that most considered completely impossible, and that very few even dared to dream. Yet, here we are, and we're not stopping any day soon. Personally, this looking back and seeing what once was thought as impossible as accomplished, is one of the things that motivates me the most to keep going.
@opensourceit @thibaultamartin @postmarketOS
PostmarketOS: Aiming for a 10 year life-cycle for smartphones | Hacker News
news.ycombinator.comelly
in reply to pabloyoyoista • • •@pabloyoyoista @claudius @cas @opensourceit Hopefully you don't mind me chipping in here.
I used to maintain my own fork back in high-school (when LineageOS was still called CyanogenMod... ouch, my back). Back in those days smartphones were a wild west. People carrying computers full of personal data in their pockets without any encryption, banking apps and other essential applications didn't care whether you modified your device or not. It was trivial to root your device and relatively easy to maintain your fork.
That started to change around 2016 - 2018. Around Android 8 codebase started increasing, maintaining your forks/rebasing became
... Show more...@pabloyoyoista @claudius @cas @opensourceit Hopefully you don't mind me chipping in here.
I used to maintain my own fork back in high-school (when LineageOS was still called CyanogenMod... ouch, my back). Back in those days smartphones were a wild west. People carrying computers full of personal data in their pockets without any encryption, banking apps and other essential applications didn't care whether you modified your device or not. It was trivial to root your device and relatively easy to maintain your fork.
That started to change around 2016 - 2018. Around Android 8 codebase started increasing, maintaining your forks/rebasing became a pain in the butt. That's why many "Custom ROMs" started disappearing, it simply consumed too much time and required a lot of resources to build the bloody thing.
Around that time prices of smartphones started to drop, and people in developing countries could afford a smartphone (where they couldn't afford a computer). This was the time when we observed a general population shifting their daily computing needs from desktop onto mobile.
With people shifting their habits, companies decided to track users and sell their data in exchange for "free" utilities and forcing everyone to use their stupid apps (where most people couldn't block ads).
Mobile market became a much more lucrative target for spyware and malware, because now everyone had a computer connected to the internet in their pocket at all times. That's why banks started to detect/block people using modified Android builds for "accountability". Soon after, it essentially became a war.
For that reason, I bought an iPhone with my first real paycheck in 2016. Not having to deal with Android's atrocious security, potential malware in custom builds (it happened many times).
It just worked... until 2022, when Apple started adding ads to App Store and so on. It made me angry that I spent a small fortune on a device and manufacturer dared to serve me ads, so I bought a Google Pixel 6 and installed GrapheneOS on it.
To put it bluntly: I despise that phone. I still have it kicking around, but I'm working on gs101-mainline. Heavy, bulky, no expandable storage, no headphone jack, no physical keyboard.
Using GrapheneOS meant I couldn't use contactless payments, notifications didn't work, and in ~2025 my bank added Play Integrity API, which prevented me from using my banking applications whatsoever.
Some people will say it's about keeping users safe, I call it "control". Device manufacturers are trying to take away device ownership from you by removing the ability to "unlock bootloader" (in reality just flipping a flag whether ABL should check signatures) because they want you to stay within their ecosystems.
Google Services that track your every move, $VENDOR shipping uninstallable applications and harvesting your data/serving you ads. I've looked at my brother's Samsung S25 (or whatever it's called) running stock firmware and I was absolutely horrified.
If my brother and I would be talking about sensitive topics, I would ask him and his girlfriend to put their phones into a Faraday cage. That's how bad modern smartphones are.
AOSP is done for, Google doesn't care about opensource anymore (unless it benefits them).
Releases twice a year, delayed security updates. Not publishing trees for Pixels anymore (their own freakin' devices!).
They laid off the entire ChromeOS team, cancelled AMD Chromebooks, and now there are rumors of ditching coreboot in the future (where they could easily lock-down the boot chain and fuse devices with their own signing keys).
One vendor I've worked with (and whom I'll likely work again this year) almost went bankrupt because of Google and amount of control they have on device manufacturers.
Out-of-the-blue Google cancelled Android XR partnership (even though said vendor helped Google get that project off the ground) and left them with AOSP scraps provided by silicon vendor (Qualcomm).
Said company has ~15 employees whom can't possibly write replacements for what Android XR offers nor maintain it down the road. Hell, you need a system with ~64GB of RAM and ~480GB of disk space to build those sources. It's absolutely ridiculous.
While I haven't done much in postmarketOS, I've been tracking the project since 2018 and messing with/maintaining few devices, as well as suggesting ideas myself.
It's the only way we can have computers in our pockets that don't track our every move and that can easily be pwned by 3-letter agencies if your suspected of any (even insignificant) crime.
It's been a wild ride and I'm extremely proud of everyone who's involved in this project. Tremendous amount of work done and plenty still to do. Slowly but surely it will become a viable replacement for Android.
like this
it/its kitten, Remiberry, sog, WeirdTreeThing, samueldr and Bitslingers-R-Us like this.
Danct12 reshared this.
Tony Schmidt
in reply to elly • •@elly So I take it you don't think #grapheneos #eos #calyxos or #iode are doing a good job on privacy? Or at least a good enough job since #postmarketos is still barely usable (for most mobile OS users)? I don't hear those communities giving up on AOSP while it lasts, even with their recent changes. Don't get me wrong, I think PostmarketOS is a great project and wish it all the best, but IMO it's not a viable option yet, especially for lesser technical normies who want to degoogle or deapple and/or have access to a FOSS ecosystem that can meet the requirements of most users.
kcxt @ 39c3
in reply to Tony Schmidt • • •@opensourceit @claudius @pabloyoyoista @elly dude read what she wrote and stop reading into what she didn't
do you think any of the android derivatives you mentioned have the ability to take on a full fork of AOSP?
Tony Schmidt
in reply to kcxt @ 39c3 • •GrapheneOS
in reply to elly • • •@elly @claudius @opensourceit @cas@treehouse.systems @pabloyoyoista @postmarketOS
> contactless payments
There are multiple working options for contactless payments on GrapheneOS. They won't work on PostmarketOS.
> notifications didn't work
Push notifications work perfectly well on GrapheneOS.
> which prevented me from using my banking applications
That's not solved using something where hardly any open source mobile apps or especially mainstream apps will be available compared to it.
GrapheneOS
in reply to GrapheneOS • • •@elly @claudius @opensourceit @pabloyoyoista
> consumed too much time and required a lot of resources to build the bloody thing
Building the OS as a whole from source it not the same as using other people's builds of binary packages.
> AOSP is done
Moving from 1 major release per year to 4 and then to 2 doesn't mean that. People should really stop spinning everything to suit their biases.
> delayed security updates
AOSP isn't the only project with embargoes.
GrapheneOS
in reply to GrapheneOS • • •@elly @claudius @opensourceit @pabloyoyoista
> laid off the entire ChromeOS team
> cancelled AMD Chromebooks
> ditching coreboot in the future
> where they could easily lock-down the boot chain
These claims aren't true but it's not really relevant.
> you need a system with ~64GB of RAM and ~480GB of disk space to build those sources
You don't need anywhere close to that much RAM. Building a whole OS does use a lot of space.
GrapheneOS
in reply to GrapheneOS • • •@elly @claudius @opensourceit @pabloyoyoista
> It's been a wild ride and I'm extremely proud of everyone who's involved in this project.
Does that include the multiple core PostmarketOS developers who have participated in attacks on the GrapheneOS team with libel, bullying and harassment including linking to Kiwi Farms content repeatedly?
> Slowly but surely it will become a viable replacement for Android.
Doesn't seem to be getting there.
Claudius
in reply to GrapheneOS • • •Tony Schmidt
in reply to Claudius • •GrapheneOS
in reply to Tony Schmidt • • •@opensourceit @claudius @elly The person who originally this thread made inaccurate claims about GrapheneOS and other projects based on misinterpreting news stories. Many people in the thread attacked it and claimed it's non-viable, useless, misguided and downplayed the work we do.
Multiple postmarketOS developers are directly involved in harassment towards our team. Several people friends with them including the person who posted the thread are active here.
Why wouldn't we be defensive here?
Tony Schmidt
in reply to GrapheneOS • •elly
in reply to GrapheneOS • • •GrapheneOS
in reply to elly • • •@elly You claim the entire ChromeOS team is laid off and yet we know people working there and it's still having active development/releases. How is that supposed to be true?
How are AMD Chromebooks cancelled when they're still getting new models and receiving the expected updates? It sounds more like a specific project or generation was cancelled or skipped over.
Where's your source for them ditching coreboot and doing what you claim they will by locking out other operating systems?
elly
in reply to GrapheneOS • • •@GrapheneOS
Mostly maintenance by underpaid workers in India. They were given cheapest, crappiest machines and can barely do their job as they’re expected to build remotely in US and tools are timing out due to latency. All proper engineering resources go into merging ChromeOS codebase with Android (which will be a disaster for resulting codebase and overall complexity).
Just check coreboot’s gerrit and look for accounts with chromium.org emails that are no longer active.
... Show more...@GrapheneOS
Mostly maintenance by underpaid workers in India. They were given cheapest, crappiest machines and can barely do their job as they’re expected to build remotely in US and tools are timing out due to latency. All proper engineering resources go into merging ChromeOS codebase with Android (which will be a disaster for resulting codebase and overall complexity).
Just check coreboot’s gerrit and look for accounts with chromium.org emails that are no longer active.
What’s your source on this? Last AMD models were released in ~2023 with release of Zen2-based Ryzen 7000 models (“Mendocino”, baseboard “Skyrim”). Phoenix and subsequent generations were cancelled, people at AMD were either laid off or re-located to server segment. Google’s engineers personally confirmed there are no plans to release new models with AMD SoCs.
Compared to that, they currently have EVTs with Intel PantherLake (“fatcat”) that was just released to the public.
That’s just a speculation and rumors, you’re right about this one.
GrapheneOS
in reply to elly • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •elly
in reply to GrapheneOS • • •@GrapheneOS If you're referring to alleged attacks, then all I would have to say would be that I will not believe for a second that someone from postmarketOS's team attacked other project or person working on it.
I intentionally skipped this part because I'm sure you will try to convince me otherwise, but that's something we won't reach an agreement on.
They are genuinely some of nicest people I've ever met, we've been meeting semi-regularly at events in Europe for the past 3(?) years, during which I've never heard GrapheneOS mentioned in a bad manner.
If anything, I'm the one who tends to get too fired up about things I care about and people need to calm me down from time to time (which is something I'm actively working on).
One single contributor that ever made me uncomfortable (mansplaining UFS bringup while I was holding a phone in my hand running mainline Linux kernel and booted into userspace from internal UFS storage) was (as far as I'm aware) banned for transphobia towards other contributors and few other things. That's literally it.
GrapheneOS
in reply to elly • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •GrapheneOS
in reply to GrapheneOS • • •dmi 💽
in reply to GrapheneOS • • •@GrapheneOS @elly this reads extremely funny as someone who’s a) vaguely adjacent to pmOS and b) has been targetted by channers and KF before.
are you, like, for real? pmOS people are some of the nicest folks i’ve met online 🙁
GrapheneOS
in reply to dmi 💽 • • •GrapheneOS
in reply to GrapheneOS • • •dmi 💽
in reply to GrapheneOS • • •Dźwiedziu reshared this.
GrapheneOS
in reply to dmi 💽 • • •dmi 💽
in reply to GrapheneOS • • •@GrapheneOS @elly even if this was true, which i doubt
… do you really think people are watching an hour long video that does nothing but bullies grapheneos? nobody does that! nobody worth anything, at least…
GrapheneOS
in reply to dmi 💽 • • •dmi 💽
in reply to GrapheneOS • • •GrapheneOS
in reply to dmi 💽 • • •dmi 💽
in reply to GrapheneOS • • •@GrapheneOS @elly just to be clear:
one of the biggest linux DEs has made a smear campaign about an android distro
and we are hearing about this now, in a thread where someone voiced critique of you
… why. i still don’t get what GNOME, us, or anyone has to gain from this 🙁
GrapheneOS
in reply to dmi 💽 • • •@domi @elly You keep downplaying how well known GrapheneOS is along with the size of the userbase and importance of the work we do. You wrongly think it's a tiny niche thing and yet it's a widely known project with a lot of users that's partnered with one of the largest Android OEMs. How do you think we have millions of dollars in funding to pay a team of full time developers if it's a tiny niche project as you seem to believe?
We never said GNOME or postmarketOS themselves is attacking us.
dmi 💽
in reply to GrapheneOS • • •GrapheneOS
in reply to dmi 💽 • • •dmi 💽
in reply to GrapheneOS • • •@GrapheneOS @elly @claudius @opensourceit @pabloyoyoista i didn’t think it was possible, but i’ve just lost the remaining sliver of respect for your project.
well done!
elly
in reply to dmi 💽 • • •maxmoon 🌱
in reply to Thib • • •The last time I checked postmarketOS, it was a hacky hobby project not being able to use it on daily base, because almost nothing worked.
And the only usable messenger – if you want to connect with normies – is Signal and because it's the desktop version, it will look weird and UE is bad using desktop versions on mobile devices.
Do you use postmarketOS on a daily base?
BohwaZ
in reply to maxmoon 🌱 • • •maxmoon 🌱
in reply to BohwaZ • • •Axolotl - postmarketOS Wiki
wiki.postmarketos.orgBohwaZ
in reply to maxmoon 🌱 • • •Steve Leach
in reply to Thib • • •I'm always amazed by how bad the Android ecosystem is considering how good the Linux ecosystem is.
I really don't understand how it happened that there has never been a basic set of tools like file managers, text editors, etc. etc. that are all (of course) free, open-source, and (obviously) ad free.
I mean there's *no* paid/spamware stuff in any distro repositories, but it's *all* there is on Android.
Steve Leach
in reply to Steve Leach • • •Like how is it even possible that the "Play" store is so bad that there's no way to filter out applications with paid/pro features or with ads.
I gave up on using my phone for much other than as a phone shortly after I got my first "smart" phone.
There's no point in trying to install software on it - it's a phone... the screen is too small, there's no keyboard, and it's impossible to find software that isn't terrible because of the "Play" store.
Martina Neumayer
Unknown parent • • •@pherjung Yes, they both are pretty good usable as a daily basis systems. Especially SailfishOS. I am using it few years long now and I have no complaints nor any issues at all. Moreover, I'm very happy to not being dependent anymore with google's trash or similar parasitic corpo's junk.
@thibaultamartin
GrapheneOS
in reply to Thib • • •What does the release schedule for major releases being 2 times per year instead of the previous 1 time per year or then 4 times per year matter?
PostmarketOS has poor privacy, atrocious security, weak functionality and isn't compatible with most open source mobile apps or mainstream apps. The core development team behind PostmarketOS has extensively participated in harassment of the GrapheneOS team. How is participating in Kiwi Farms harassment collaborative?
Thib
in reply to GrapheneOS • • •explicitly say they are not consumer-ready.
postmarketos.org/state/
I am not advocating for people to install postmarketOS now as a daily driver, I'm advocating for people to support a project that doesn't depend on Android because it is not a viable route for Europeans.
I am happy that @GrapheneOS exists and that it can serve an overlapping audience today.
I'm asking you to please be respectful of other projects, and I will not engage further.
postmarketOS // State of postmarketOS
postmarketOSGrapheneOS
in reply to Thib • • •> I'm asking you to please be respectful of other projects, and I will not engage further.
You're making highly inaccurate claims about GrapheneOS and disparaging our work. You're claiming it's not viable and dead end. At the same time, you're supporting a project which has numerous core developers and contributors engaging in attacks on GrapheneOS and our team with fabricated stories, bullying and harassment. That includes spreading Kiwi Farms content.
GrapheneOS
in reply to GrapheneOS • • •Enää 4kk kesälomaan
in reply to GrapheneOS • • •postmarketOS
in reply to GrapheneOS • • •if anyone on our team or in our community has been engaging in the behavior you describe we would very much like to know about it so we can take appropriate action.
You can contact coc@postmarketos.org or a subset of CoC team members listed here: docs.postmarketos.org/policies…
CoC reports are kept highly confidential, if a report is made to an individual it won't be shared even with other members of the CoC team without explicit consent.
Code of Conduct - Policies and Processes
docs.postmarketos.orgocdtrekkie
in reply to Thib • • •GrapheneOS
in reply to ocdtrekkie • • •@ocdtrekkie What does the release schedule for major releases being 2 times per year instead of the previous 1 time per year or then 4 times per year matter?
PostmarketOS has poor privacy, atrocious security, weak functionality and isn't compatible with most open source mobile apps or mainstream apps. The core development team behind PostmarketOS has extensively participated in harassment of the GrapheneOS team. How is participating in Kiwi Farms harassment collaborative?
ocdtrekkie
in reply to GrapheneOS • • •Jeff McNeill
in reply to Thib • • •Pablo Martínez
in reply to Jeff McNeill • • •GrapheneOS
in reply to Pablo Martínez • • •@pablo_martan @jeffmcneill What does Android's release schedule for major releases being 2 times per year instead of the previous 1 time per year or then 4 times per year matter?
PostmarketOS has poor privacy, atrocious security, weak functionality and isn't compatible with most open source mobile apps or mainstream apps. The core development team behind PostmarketOS has extensively participated in harassment of the GrapheneOS team. How is participating in Kiwi Farms harassment collaborative?