Page MenuHomePhabricator

i18n maintenance for MediaWiki and extensions
Closed, DeclinedPublic

Description

Type of activity:

or

  • an Unconference session, if the main topic is already overloaded.

Main topic:

''How to manage our technical debt''

The problem

Several i18n/language support issues for MediaWiki does not have clear maintenance ownership.

Expected outcome

A common understanding on how to deal with the legacy issues around i18n support for MediaWiki and extensions.

Current status of the discussion

e.g. T46667#2677469 . There are more tickets with similar conversations.

Links

  • ...

Pre-scheduling status

  • 2016-10-31: Deadline for submitting a new proposal. Work-in-progress drafts are OK.
  • 2016-11-14: Deadline for defining a good problem statement, expectations, and links to relevant resources.
  • 2016-11-28: Deadline for consolidating a discussion, regularly summarized in the proposal.

Event Timeline

Arrbee created this task.Oct 3 2016, 5:29 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 3 2016, 5:29 AM
Qgil updated the task description. (Show Details)Oct 5 2016, 8:31 AM
Isarra added a subscriber: Isarra.Oct 19 2016, 4:30 AM
Tgr added a subscriber: Tgr.Oct 31 2016, 2:59 AM

IMO a more specific problem statement would be helpful.

Qgil added a subscriber: Qgil.Nov 10 2016, 11:32 AM

Please remember the next deadline in the selection process:

2016-11-14: Deadline for defining a good problem statement, expectations, and links to relevant resources.

That is next Monday.

Missing a clear problem statement and expectations from session. @Arrbee are you still the owner for this proposal?

@Niharika , this was a follow up that came up from T46667 as an open proposal for general i18n maintenance . I would go with what @greg or @Nikerabbit think is best for this session i.e. pre-defined or unconference.

greg added a comment.Dec 1 2016, 5:52 PM

The time to show interest and discussion about a topic to get into the pre-scheduled queue was a couple weeks ago. This now could only be during the unconference.

The first thing that should be done by the proposer is to clearly articulate the problem statement.

Qgil added a project: I18n.Dec 2 2016, 8:25 AM

@Arrbee Hey! As developer summit is less than four weeks from now, we are working on a plan to incorporate the ‘unconference sessions’ that have been proposed so far and would be generated on the spot. Thus, could you confirm if you plan to facilitate this session at the summit? Also, if your answer is 'YES,' I would like to encourage you to update/ arrange the task description fields to appear in the following format:

Session title
Main topic
Type of activity
Description Move ‘The Problem,' ‘Expected Outcome,' ‘Current status of the discussion’ and ‘Links’ to this section
Proposed by Your name linked to your MediaWiki URL, or profile elsewhere on the internet
Preferred group size
Any supplies that you would need to run the session e.g. post-its
Interested attendees (sign up below)

  1. Add your name here

We will be reaching out to the summit participants next week asking them to express their interest in unconference sessions by signing up.

To maintain the consistency, please consider referring to the template of the following task description: https://phabricator.wikimedia.org/T149564.

@Arrbee: Did this session take place?
If yes, are there any notes or action items to share? Are there any actionable items (tasks to create / link?) from this session?
If not, could you close this task as declined? Thanks in advance!

@Arrbee: Did this session take place?
If yes, are there any notes or action items to share? Are there any actionable items (tasks to create / link?) from this session?
If not, could you close this task as declined? Thanks in advance!

Aklapper assigned this task to Arrbee.Apr 27 2017, 12:36 PM
Aklapper closed this task as Declined.Apr 3 2020, 3:36 PM

@Arrbee: No reply for many years, hence closing

Restricted Application removed a subscriber: Liuxinyu970226. · View Herald TranscriptApr 3 2020, 3:36 PM