The new contribution workflow for GNOME

Posted Apr 7, 2017 19:42 UTC (Fri) by kloczek (guest, #6391)
Parent article: The new contribution workflow for GNOME

> "No dependencies hell"

Yep. If you you will break thermometer definitely you will be able instantly cure the fever.

The new contribution workflow for GNOME

Posted Apr 8, 2017 17:22 UTC (Sat) by pbonzini (subscriber, #60935) [Link]

This is only about using flatpak to facilitate new contributions. Breaking the thermometer would be forcing the distributions to go to flatpak en masse, but they're unaffected.

The new contribution workflow for GNOME

Posted Apr 9, 2017 16:08 UTC (Sun) by ebassi (subscriber, #54855) [Link] (1 responses)

The "dependencies hell", in this context, means "building all dependencies needed to compile an application".

Flatpak allows GNOME to provide an SDK (nightly or stable) that can be used to build an application, and that does not break your own OS.

The new contribution workflow for GNOME

Posted Apr 11, 2017 8:33 UTC (Tue) by ovitters (guest, #27950) [Link]

For reference, previously contributing to GNOME meant compiling git master of loads of different components. Which means installing the needed development libraries in some cases. It's like an 3-7 day trial and error process to get started. Plus sometimes someone breaks 'git master' of one of the many components. It might even be a component GNOME depends on but doesn't maintain.

The whole process is terribly cumbersome and I wouldn't be surprised if loads of people gave up way before. You can also tell this because Google Summer of Code brings in most new contributors.