Marketing

I set up Up For Grabs for Markus's crash reporting service. It only works for GitHub projects, so we cannot use it for core LibreOffice.

Your First PR seems confusing and looking at their method to share starter issues just increases the confusion: https://github.com/yourfirstpr/yourfirstpr.github.io/issues

CodeTriage is similarly GitHub-centric, so it's out as well.

CodeNewbie does not look like a good fit as it is about learning resources. I don't think the LibreOffice codebase is a good learning resource.

Thanks Ilmari for your feedback -- they don't look particularly suitable for us, then.

One other thing I could do is write an article here:

https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/

I could talk about how to get involved with LibreOffice (build it on Fedora, an overview of the code, other ways to help the project etc.)

Mike Saunders wrote:

Thanks Ilmari for your feedback -- they don't look particularly suitable for us, then.

One other thing I could do is write an article here:

https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/

I could talk about how to get involved with LibreOffice (build it on Fedora, an overview of the code, other ways to help the project etc.)

Sounds good :)

These Up For Grabs etc. are understandably trying to keep things viable and maintainable. I guess the OpenHatch web application never took off properly, because it was too ambitious in trying to aggregate reports from a whole bunch of different bug tracking systems. Having a new OpenHatch would be cool, but it would require a lot of funds to kickstart and keep going.

I've been given the rights to submit a pitch for an article, which I've done:

Summary: Describe ways that readers can get involved with LibreOffice and improve the software

Description: The purpose of this article would be to explain where LibreOffice came from (a short history, explanation of what The Document Foundation does etc.) Then describe the different parts of the community (development, design, marketing, QA, documentation etc.) and how readers can get involved. Some tasks will be bigger (like exploring the source code), whereas some will be 'bite sized' -- ie 10 minutes or less. The flow of the article would be as follows:

* Where did LibreOffice come from? What does TDF do?
* What are the different parts of the project?
* How can readers help out, and get experience contributing to a FOSS project?
* How does the community keep in touch and meet up? (eg LibreOffice Conference)

If it's accepted, I'll write it next week.

I've had some feedback on my Fedora Magazine article pitch; the editors would rather it focuses on new/lesser-known features in LibreOffice, with a section at the end encouraging users to get involved and contributed. So I've updated the pitch accordingly, and now waiting to get the go-ahead.

Got the go-ahead for the pitch, so I've written the article, and am now waiting for it to be published.