Organize LibreOffice compile benchmarking
This is a development marketing idea. There is an ongoing discussion about build times of LibreOffice at:
- set up an email firstname.lastname@example.org
- publish a blog post calling out to send in the duration it takes to do a build of libreoffice at a specific tag (last release? or tip of master?) and send in a mail to email@example.com including:
- build configuration: ./autogen.sh flags
- hardware specs: CPU, RAM, SSD/spinning rust ...
- platform specs: OS, compiler version, ccache, filesystem ...
- collect the replies and put them on a wiki page
- reply to the sender and say "Thanks, great job! Now that you have a build of LibreOffice, consider doing an EasyHack (link) and join us on IRC if you need assistence (link). The EasyHack is really the easy part once you got your first build, so you shouldnt miss your opportunity to be able to claim to have contributed to LibreOffice code!"
- drive newcomers to the easyhack, with the suck cost argument ("you have a build already")
- collect data on good hardware for developers and tinderboxes
- fight the perception that LibreOffice is unbuildable by having vast data to prove the opposite
- identify pathological configs to warn newcomers about
- identify things to improve in our build system
If halfway successful, it could even be repeated annually with a current checkout of LibreOffice for the primary goal.