Skip to Content

XWiki Days

Last modified by Vincent Massol on 2024/11/28 14:43
Contents

We organize special Days every Thursday, where we try to get the maximum number of committers and contributors to work on a special task, in order to get the maximum work for that task and reduce the backlog.

These events are indicated in the XWiki.org Event Calendar.

Active XWiki Days

Those are the types of XWiki Days we do regularly.

Bug Fixing Day

The goal of this day is to close the maximum number of bugs (note that I've said "close" and not "fix"!) in order to have globally more bugs closed than bugs created. The idea is to take the low hanging fruits. Here are some ways of closing bugs:

  • Fixing a bug of course (the hardest but the best too)
  • Closing a bug as invalid (the bug doesn't make sense)
  • Closing a bug as cannot reproduce
  • Closing a bug as duplicate of another existing JIRA issue (the simplest to do)
  • Closing a bug as won't fix (the bug exists but we don't want to fix it for some reason)
Information

Use the label bugfixingdayif you close jira issues done as part of that Day.

Doc Fixing Day

Improve xwiki.org (add missing docs, write guides, improve navigation, clean e.x.o - marking old extensions as deprecated, writing documentation, specifying what version the extension is working on -, etc.

Information

Use the label docfixingday if you close jira issues done as part of that Day.

Deprecation Fixing Day

Reduce # of deprecated calls and move code to legacy.

Information

Use the label deprecationfixingday if you close jira issues done as part of that Day.

Quality Fixing Day

Reduce issues found in quality reporting tools (SonarQube, Checkstyle, etc). For example, see https://sonarcloud.io/project/issues?resolved=false&id=org.xwiki.platform%3Axwiki-platform).

Information

Use the label qualityfixingday if you close jira issues done as part of that Day.

Test Fixing Day

Some ideas:

Information

Use the label testfixingday if you close jira issues done as part of that Day.

Automation Fixing Day

Work on stuff that could be automated or improved to win time during development.

Some ideas:

  • CI related improvements
  • speed up the build
  • improve the release script and release process in general
  • new automation of some repetitive task
Information

Use the label automationfixingday if you close jira issues done as part of that Day.

Ideas of other XWiki Days

  • Broken Links Day: fix as many broken links as possible on xwiki.org.
  • Improvements Closing Day: close as many small improvements as possible
  • Pull requests Closing Day: close as many PRs as possible
  • Localization Improvement Day: Add as many translations as possible on l10n, improve l10n itself, add missing keys in code, etc
  • Todo Fixing Day: resolve and remove TODO and FIXME markers in our code
  • Usability Improvement Day: Resolve small usability issues for end users (navigation, home page content, help pages, more simple macros, etc).
  • Contribution pain points days: discuss/fix things listed on ContributingPainPoints page
  • Build/release tooling days: improve build/release related scripts and tools especially automation
  • ProgrammingRights Fixing Day: Work on removing the need to have PRs on pages that are part of the XWiki Standard Flavor and Recommended Extensions.
  • Javadoc Improvement Day: Add missing javadocs in our code and remove checkstyle excludes

History

Information

We used to create reports for each XWiki Say, but we don't do that anymore.

Bug Fixing Days

Improvement Fixing days

DocHour days

Pull Request Days

Test Fixing Day

ProgrammingRights Fixing Day

Deprecation days

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected