Page MenuHomePhabricator

Collect tasks related code and security review
Open, Needs TriagePublic6 Story Points

Description

Some are in Wikispeech, but there may be others, though they should be connected somehow. Also make an inventory of notes we have connected to the reviews.

The following tasks and documents are related to the reviews. Each lists what has been identified as blocking work that needs to be done before proceeding. They also include the WMF-people that has been involved in the discussion, so we know who to contact once we are ready to move forward.

T180021: Security review for extension Wikispeech

Original request for security review. No review was initiated since there were too many fundamental problems detected.

WMF-people involved

@Reedy, @charlotteportero (no longer employed by WMF)

Blockers

T180015: Deploy extension Wikispeech on beta cluster

Get Wikispeech running on the beta cluster before it gets added as beta function to Wikipedia.

Blockers

WMF-people involved

@Reedy, @greg

T192990: Use Swift for audio-file storage

Enable Swift storage to be used instead of basic file storage.

Blockers

A Swift-server to use in development.

T200735: Work with Wikispeech towards their production deployment goal and generate documentation

Intended to help us figuring out how to get things deployed.

WMF-people involved

@bd808

T193072: TTS server deployment strategy

Focused on deployment of the TTS-server as a service on Wikimedia servers.

WMF-people involved

@akosiaris, @bd808

Möte med WMF

Notes from meetings during second half of 2018, trying to figure out what would be needed before review could commence.

WMF-people involved

@bd808, @thcipriani

Event Timeline

Sebastian_Berlin-WMSE set the point value for this task to 8.Mon, Nov 25, 10:56 AM
Sebastian_Berlin-WMSE changed the point value for this task from 8 to 6.Mon, Dec 2, 7:56 AM
Sebastian_Berlin-WMSE added a subscriber: Lokal_Profil.

This is what I could find. Not quite sure what to do with this task now: if we close it it may get lost. Maybe keep it opened as stalled or something until we've acted on the things that were identified.

Thanks. I'll take a look at the collected info and see if I remember any additional details.

This is what I could find. Not quite sure what to do with this task now: if we close it it may get lost. Maybe keep it opened as stalled or something until we've acted on the things that were identified.

We could possibly rephrase the intro somewhat and change it to a Goal? Or we extract it into a separate document and close the task.

I 'll remove myself from this if you don't mind. I guess I was added because of T240175#5723047 but that was an answer to a very cut and clear question. Overall, I honestly I have no idea what the project is about, nor how I could be of help (at least for now). Feel free to readd me if you disagree.

greg removed a subscriber: greg.Mon, Dec 9, 11:26 PM