Project

General

Profile

Actions

Task #1979

closed

LibreOffice community weeks, to generate more interest and involvement

Added by Mike Saunders almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Team - Q4/2016
Start date:
Due date:
% Done:

0%


Description

Some communities find it difficult to bring in new participants. Each month, or every two weeks, focus on a specific community, eg "LibreOffice Community Week: Design".

Have daily blog posts with:

  • interviews
  • updates (eg what they did for LibreOffice 5.2)
  • how they communicate
  • how to get involved

Spread on social media, Reddit, Hacker News etc.

Actions #1

Updated by hari rawat almost 8 years ago

  • Subject changed from LibreOffice community weeks, to generate more interest and involvement to CALL ASSIGN+1-80.0-2.5.3.-07.5.9microsoft office tech nical support phone number
Actions #2

Updated by Florian Effenberger almost 8 years ago

  • Subject changed from CALL ASSIGN+1-80.0-2.5.3.-07.5.9microsoft office tech nical support phone number to LibreOffice community weeks, to generate more interest and involvement
Actions #3

Updated by Florian Effenberger almost 8 years ago

  • Target version set to Q4/2016

Do you plan that before or after LibOCon? I could imagine that we have enough things to "fire off" until then, but with the autumn season coming up after that, that might be a good opportunity?

Actions #4

Updated by Mike Saunders almost 8 years ago

I think this would be best after the conference. As with the Month of LibreOffice campaigns, these Community Weeks could be useful during the gaps between major releases -- when it's a bit "quieter" in the project (at least, to the outside world). I will plan some for September and October (with a Month of LibreOffice to run in November).

Actions #5

Updated by Florian Effenberger over 7 years ago

I think this would be best after the conference. As with the Month of
LibreOffice campaigns, these Community Weeks could be useful during the
gaps between major releases -- when it's a bit "quieter" in the project
(at least, to the outside world). I will plan some for September and
October (with a Month of LibreOffice to run in November).

Maybe October is even better, as until mid-September we have the
conference, so half the month is blocked with announcements and activity
anyways

Actions #6

Updated by Mike Saunders over 7 years ago

Had a reminder from JanI at the conference that for the Developer week, we should really highlight that we have a dedicated mentor in our team to help newbies. And we've been refactoring the code as well.

Actions #7

Updated by Mike Saunders over 7 years ago

Also had an idea from Björn: make sure each community has a list of Easy Hacks before running their weeks. This could be part of the final day ("Now get involved...")

Actions #8

Updated by Mike Saunders over 7 years ago

  • Status changed from New to In Progress

Starting planning this with the various teams. Objective is to have blog posts on Mon, Weds and Friday, including:

  • What the project does, who's who, mini interview
  • Recent changes, tools used
  • How to get involved, Easy Hacks

Current plan is to run Documentation as first week in October (working with Olivier on this)

Actions #10

Updated by Mike Saunders over 7 years ago

Second post for first week: https://blog.documentfoundation.org/blog/2016/10/06/community-week-documentation-whos-who-tools-used-and-get-involved/

Prepared in advance three posts (Mon, Weds and Fri) for next week: dev with JanI. I'll be on holiday but can just post them in the mornings and spread links around the usual channels.

Actions #14

Updated by Mike Saunders over 7 years ago

Actions #15

Updated by Mike Saunders over 7 years ago

  • Status changed from In Progress to Closed

Finished now, so closing this ticket, and here's a wrap-up post: https://blog.documentfoundation.org/blog/2016/11/02/libreoffice-community-weeks-wrapping-up/

This campaign brought in some new contributors, especially in development and documentation, but it's still tough to ensure people stay for the long term. Ideas for the future:

  • Video interviews
  • Reward new contributors to each project with badge/certificate
  • Live IRC sessions, one for each week, eg 3 hours where new or interested potential contributors can join in
Actions

Also available in: Atom PDF