We're forking Flutter

Re:We're forking Flutter by riku_iki on Monday October 28, 2024 @03:34PM (#41975182)

> What do you do if the team won't work on that bug for 2 years? Well, if it's a serious bug for your company, then you stop using Flutter. You don't have a choice. You need to keep moving forward. Your team doesn't know how to work on the Flutter framework, and the Flutter framework team is either unresponsive, or at least completely non-committal towards a fix.

they could pay contributor or issue bug bounty..

[ Parent | on HN ]

Re:We're forking Flutter by hobs on Monday October 28, 2024 @03:47PM (#41975356)

Based on the article's premise getting that merged is the problem, not fixing code.

[ Parent | on HN ]

Re:We're forking Flutter by riku_iki on Monday October 28, 2024 @04:52PM (#41976158)

right, making maintainers happy is part of that work.

[ Parent | on HN ]

Re:We're forking Flutter by throwaway032023 on Monday October 28, 2024 @08:24PM (#41978106)

Yeah this isn’t drive-by contributions where you shit out a PR that works for you but makes the test infra fail and you get upset. Ppl need to think big picture.

One big problem, I think, it may not be visible all of the test infrastructure if your outside google. Don’t know. Gerritt is its own world and googlers live there not in GH (it appears).

[ Parent | on HN ]