Thank you @Phoenix303 for your proposal. Are you are eligible for Google-Summer-of-Code (2015) ? If so, please apply to GSoC as well, since this project is within scope for that program.

@Qgil, she has mentioned that she isn't eligible for GSoC above. :)

Thanks, Phoenix303. Let me give just a quick feedback for now; in these days, our priority is the review of your patches.

What I see as missing from this application, for now, is an overall cohesion and self-sustainability. Without a clear picture of what you want to reach at the end of your journey, it's very easy to get lost and a lot of energy is wasted on micro-management.

Our proposal (T89103) is mostly a blank page, I know: some scenes are offered, but it's your responsibility to define the overall story. This week, I believe that the best use of your time is to use the product and interact with its users: I see you made 7 translations and reviewed 11, but that's really too little. Ideas: perform some hundreds edits and log actions, check the edits of other users, talk with them on the wiki, look for other Translate wikis, contact bug reporters and translators.

Without this, all the suggestions below would just become meaningless paperwork.

Improvements possible for your application, from absolutely necessary to optional:

1. a clear definition of your customers, per http://agilemanifesto.org/ (ideally usernames, or a concrete plan to identify some): they are the persons you'll be working for, you will be in constant contact with them during these months to (re)determine your goals and progress;
2. a testing plan: your own environment, which IIRC you already mostly made; the environment where to interact with (1);
3. all the specific user stories/reports, including requirements and plans thereof, moved from your application's text to the specific task descriptions (the 5 tasks you proposed have their own reports, IIRC);
4. an overall "narrative"/"epic story" for the project, including a title which summarises the idea and helps convey it (it doesn't help to replicate the content of T89103);
5. if all the rest is done, you could try and update https://commons.wikimedia.org/w/index.php?title=File%3ATranslate-workflow-spec.pdf&page=21 etc. with new visual designs/mockups/prototypes (if you reach this stage we can give pointers to pages which describe how Pau does it).

In T92929#1124331, @Qgil wrote:

Thank you @Phoenix303 for your proposal. Are you are eligible for Google-Summer-of-Code (2015) ?

She says not, in the text. Unless I misunderstood.

@Qgil, No, I am not applying for GSOC as I am not eligible for it.

@Nemo_bis Thank you so much for your feedback. I'll work on it and keep updating my proposal to improve and give more clear picture of the project.

I have just applied as mentor/org admin in https://outreachy.gnome.org/ and my request is awaiting approval. Meanwhile... @Phoenix303, have you submitted your proposal there?

You don't need to maintain two full proposals in sync. The good one is this one, and you can link from the Outreachy submission to this task.

Thanks, I like how this application is evolving. I'm sure it will get better as you can in touch with more users. :)

@Qgil Thank you for informing me. I have applied to Outreachy and have given a link to this page.
@Nemo_bis Thanks for the feedback :) I am getting in touch with more users.

I plan to publish my work on Github.com while the project is under progress

I think this evolved to be gerrit.wikimedia.org? We've been working there together all the time. :)

No, other than 4 hours in a week for volunteering work at an elementary school,

(wow)

I have no other time commitment.

Do you plan for this to stay the same, or are you seeking other commitments?

@Nemo_bis It has eventually evolved to Gerrit as now I am comfortable working there. :)
Yes, I am not seeking any other commitments during that period of time.

Thanks.

Some thoughts:

• Why no Wikimedia wiki are in the customers? Would give some more variety.
• "in target language (expected to come from the Universal Language Selector by default)" - In Translate the target language is assumed to be the interface language, that info is provided by MediaWiki core. We also provide language selector to change the target language.
• For "Specialized Searches", how do we make these shortcuts discoverable? If users do not know they exist, it will be lot of effort to implement them for small benefit. One option is to show random example when user first reaches Special:SearchTranslations without a query.
• In the mock-ups it is not clear to me how user switches between the modes of search:
  • Multilingual search: search in all languages (source language = target language)
  • Monolingual search: search in a particular language (source language = target language)
  • Cross language search: search in a particular language (source language != target language)

The UI can be different depending on whether you group these as [multilingual & monolingual] or [monolingual and cross language] or not group at all. This is probably something to test and discuss with actual users, and reserve some time for it.

With regards to timeline:

• You have already set up testing environment, haven't you? Timeline probably needs updating to reflect that.
• I am traveling May 10-31 and Nemo_bis is traveling also on some days, so better not to plan any major discussions on the last week of May.
• Make sure you have adequate time to think and implement backend changes: schema, indexing etc. as it can easily block development and testing
• A user interface already exists. I do not see proposals to redo it completely (which is good), so I think you do not need to reserve time dedicated for UI building. It should be fine to add new features to the UI as you implement the features rather than adding non-functional place holders.
• Personally, I would prioritize missing features (such as cross language search) and features involving backend changes (such as case insensitive search).

Let's talk more in the meeting today ;)

On top of that, I'd add:

• "Deploy the code in the test wiki" I don't like much, ideally you would be developing straight on your test wiki and the deployment to mediawiki.org etc. would happen with the 1.26wmf1 etc. branches.
• The three slots which take 10 days each seem not-so-defined yet. I feel they'd have to take less time or to be split in smaller items and/or to be moved in strategic points of the timeline.
• Many of the bugs, which we'd want to fix first, have 2 days assigned. Those should perhaps come first and have some flexibility in case they require more time than expected.
• We should better identify interdependencies between those tasks: which tasks block which other? Is there some point where a bottleneck could block any progress? Niklas already mentioned some periods of travels when we'll be able to offer less help.

Based on today's meeting there are several action items to make the plan clearer. When these are done and the timeline is rewritten accordingly, linked to tasks with all the interdependencies we were able to think of today, let's reassess the plan. Phoenix, let us know when you're done so that we can comment on the various tasks. When the discussion on Phabricator slows down, let's wrap up with another meeting.

1. 15.23 < phoenix303> yes Nemo_bis I will move it [test wiki setup] to 4th may?
2. Subtasks per T93527#1254537; separate task(s) for implementing facets or advanced search form or autocompletion to access those operators
3. Close T54703 as appropriate, file bug for "The translator cannot reach subgroups after clicking on any group" -> "simplest solution would be to fix the facets show the subgroups when aggregate group is selected: https://translatewiki.net/w/i.php?title=Special:SearchTranslations&query=user&group=mediawiki here I would expect to see second level list of top N subgroups of MediaWiki"
4. File or find task for "use AJAX to show the list of subgroups without loading new page" (can be attempted later)
5. Reports for "Task 3: UI Enhancements" can be in the timeline in May 11–29; for T93527#1254537, (a) can be the very first thing worked on, (b) and (c) should not be in May 11–29
6. Define web API modules to add that can then "feed" the cross-language search T55656 and perhaps some future Special:Translate feature
7. Move T55656 after the other tasks; remove "Finalize the design" and "Build the user interface based on the finalized mock-up" timeline items, a buffer to wait for tests and feedback by users (during which smaller bugs can be worked on) + time to assess the feedback and act on it
8. Add subtask T55656: how to surface the cross-language search function in the GUI, which is not in F102971
9. Add UI polishing task re F102971: status selection either as tab or as facet, but not both
10. Add or find task to make facet unselection more discoverable (not only re-click)

I don't remember: have we completed all the action points in T92929#1254548?

In T92929#1254548, @Nemo_bis wrote:

Based on today's meeting there are several action items to make the plan clearer. When these are done and the timeline is rewritten accordingly, linked to tasks with all the interdependencies we were able to think of today, let's reassess the plan. Phoenix, let us know when you're done so that we can comment on the various tasks. When the discussion on Phabricator slows down, let's wrap up with another meeting.

1. 15.23 < phoenix303> yes Nemo_bis I will move it [test wiki setup] to 4th may?
2. Subtasks per T93527#1254537; separate task(s) for implementing facets or advanced search form or autocompletion to access those operators
3. Close T54703 as appropriate, file bug for "The translator cannot reach subgroups after clicking on any group" -> "simplest solution would be to fix the facets show the subgroups when aggregate group is selected: https://translatewiki.net/w/i.php?title=Special:SearchTranslations&query=user&group=mediawiki here I would expect to see second level list of top N subgroups of MediaWiki"
4. File or find task for "use AJAX to show the list of subgroups without loading new page" (can be attempted later)
5. Reports for "Task 3: UI Enhancements" can be in the timeline in May 11–29; for T93527#1254537, (a) can be the very first thing worked on, (b) and (c) should not be in May 11–29
6. Define web API modules to add that can then "feed" the cross-language search T55656 and perhaps some future Special:Translate feature
7. Move T55656 after the other tasks; remove "Finalize the design" and "Build the user interface based on the finalized mock-up" timeline items, a buffer to wait for tests and feedback by users (during which smaller bugs can be worked on) + time to assess the feedback and act on it
8. Add subtask T55656: how to surface the cross-language search function in the GUI, which is not in F102971
9. Add UI polishing task re F102971: status selection either as tab or as facet, but not both
10. Add or find task to make facet unselection more discoverable (not only re-click)

Following tasks created for all the action points:

1. T98301: Search Translations test wiki
2. Based on a)T97943 b)T97944 c)T100175; Separate task for T98559
3. Should I close T54703? Filed another bug T97961: The translator cannot reach subgroups after clicking on any group
4. Since this T97961: The translator cannot reach subgroups after clicking on any group might work. Should I file task another bug for "use AJAX to show the list of subgroups without loading new page" ?
5. Reports for "Task 3: UI Enhancements" has been mentioned in the timeline in May 11–29; for T93527#1254537, (a) T97943: Add operators for filters which already exist ( language and group ) patch review is in progress
6. Will require more discussion (For what task to define web API module, not so clear to me)
7. Moved T55656 after the other tasks. Time to assess the feedback and act on it after each task has been added.
8. T100181
9. T98560
10. T98560

@Nemo_bis @Nikerabbit: Can we have another meeting whenever you are free? Need clarification for T98665.

On point 6 we agreed that there's no need to have it as first thing, the objective is just clean code. So any backend functionality can be split to an API module if appropriate during code review or later or in a separate task/patch.

@Nemo_bis @Nikerabbit: As per discussion I have updated the timeline. Please let me know if I have missed any point.

(Ok, we got back from France.) Thanks, this is a clearer map of the work to do.

• Please check the dependencies better, for instance T100181 is before T100417 which is its blocker; blockers should be first or they're not blockers.
• I don't understand what the "index mapping" is and "brainstorm" is not a clear task, please associate a task description. If it's the conversion from ElasticSearch results (messages keys) to message collections/message tables/message lists, it has to be before the multilingual search.
• T97944 is listed twice and I don't understand how testing can be almost one month after the fact.
• https://wiki.gnome.org/Outreachy/2015/MayAugust#Payments_Schedule implies some sort of mid-way assessment à la GSoC so there must be some sort of minimum product deployed and used by that time. Any relevant patches should be merged by July 6 (or June 29 if the roadmap will have no deployment on July 14) due to Niklas being in Mexico.
• "Add support to perform message-key and case sensitive searches" should be ok for two days. It should be either before the deadline of the previous point, or after July 13.
• July 13–28 seems overestimated to me and July 29–31 underestimated.
• "Perform Usability testing" should be after the low-level features you really want to test have already been developed, unless you plan to make non-functioning prototypes (in which case we need to know whether you already have experience with that).
• The June 8–26 period seems almost entirely composed of usability testing and user testing. I'm not sure it's wise to have such a big block all together but if you think it is then it should perhaps be in the July 13–24 period when Niklas will be in Mexico and code review will slow down.

So, until now I was unable to test anything because of a misunderstanding, the interface only really worked with English language (or some precise combination of UI language and content language). Now that we figured this out I'm able to look into things more.

Hello!

End of GSoC is fast approaching. 17 August is "Suggested pencils down" deadline and 21 August is "Firm pencils down" deadline. It is expected that you don't dive into new features which might take longer than two weeks to complete and instead work on polishing up your project, testing thoroughly and getting your code merged into the main branch. I hope this project is almost complete so you can merge it and make it available to everyone as quickly as possible. :)

A few questions (for both mentors and student):

Are you confident in completing the project on time?
By when do you think you can merge the code, if at all?
Are there any major blockers or important missing features?
We are looking for projects which are (nearly) complete to feature on our post on Wikimedia and Google OSPO's blogs (for example: http://google-opensource.blogspot.in/2015/02/google-summer-of-code-wrap-up-processing.html). If you're interested in getting yours up there, hurry up and get this finished!

The hard deadline on getting code merged is September. Refer T101393: Goal: All completed GSoC and Outreachy projects have code merged and deployed by September.

We'll be asking the students to demo their projects towards the end of the program as well.

Good luck!

Hello @NiharikaKohli

In T92929#1527730, @NiharikaKohli wrote:

A few questions (for both mentors and student):

Are you confident in completing the project on time?

Yes, the project is almost complete. It is available here

By when do you think you can merge the code, if at all?

The code review is in progress by @Nikerabbit.

Are you confident in completing the project on time?

Yes, the project is almost complete. It is available here

Wow! This looks good. It works nicely for me in both english and hindi. Thanks for working on this @Phoenix303. :)
If you want me to add this project to the google blog-post, could you write up a little description of the project? This would be a really cool project to feature on it.

@Nikerabbit, @Nemo_bis any idea by when we can get this merged onto production?

any idea by when we can get this merged onto production?

Everything that is merged goes in production by itself, so most of the tasks planned for the project are already in production (mostly the minor bugs). The main deliverable of this project is T55656 and that's being deployed next week, thanks to recent merges.

Among the open tasks I basically identify T70518, T62570, T100013 as real todos, and they are mostly at a good stage in code review. The other todo is adding a couple paragraphs of documentation to https://www.mediawiki.org/wiki/Help:Extension:Translate or subpage thereof.

Hi, I have associated two blocked-by tasks with this project.

For the student:

1. Please go through the checklist in the end-term evaluation and fill out the fields which require any links. The checkboxes are for the mentor(s) only. Adding information on the past projects page is your task.
2. Ensure that you have completed all the items listed in the end-term evaluation task. If there's a strong reason about why a particular item was not completed, please comment on the task and we shall look into it.
3. Wrap-up report is mandatory and so is a demo-able link to the project (either in production or in a demo server).
4. If you want your project to be featured in the blogpost on the Google OSPO blog, kindly comment back with a short, catchy description of the project along with a screenshot.

If you want your project to be featured in the blogpost on the Google OSPO blog, kindly comment back with a short, catchy description of the project along with a screenshot.

This would be nice. Dibya, you could recycle the [[help:Extension:Translate]] paragraphs and the screenshot you made.

If you want your project to be featured in the blogpost on the Google OSPO blog, kindly comment back with a short, catchy description of the project along with a screenshot.

Description: Without a search feature, it is difficult for translators to find specific messages they want to translate. Traversing all the translations or strings of the project is inefficient. Also, translators often want to check how a specific term was translated in a certain language across the project.

This is solved by the special page Special:SearchTranslations. Translators can find the messages containing certain terms in any language and filter by various criteria: this is the default. After searching, they can switch the results to the translations of said messages, for instance to find the existing, missing or outdated translations of a certain term.