@Tgr the scope looks good. Since the requirements are community specific, please direct any prospective Outreachy candidates whom you know from the community and who fulfill https://wiki.gnome.org/Outreachy#Eligibility to this place so that they can discuss upon the project and submit a proposal.

Would this be suitable for GSoC or Outreachy? We are currently recruiting projects and mentors for May-Aug 2017. @Tgr, if you would be interested to mentor for this round still, please add a Outreach-Programs-Projects tag to this project. Thanks!

I think it would be ideal although potentially hard to find an applicant for.

I thought translation work was forbidden by GSoC rules: did you check? On the other hand, i18n work is always welcome and porting gadgets has nothing to do with l10n (but it's always questionable what impact such gadgets have).

In T147618#3063698, @Nemo_bis wrote:

I thought translation work was forbidden by GSoC rules: did you check? On the other hand, i18n work is always welcome and porting gadgets has nothing to do with l10n (but it's always questionable what impact such gadgets have).

Non-coding tasks are not allowed in GSoC but allowed in Outreachy. The task is certainly better suited for Outreachy, but I think there are enough coding tasks to fill a GSoC project as well - it would focus on writing Zotero plugins and adapting gadgets to VE.

Gadgets are unlikely to have direct impact on new editor retention (although I would expect them to have a major impact on the productivity of experienced editors), but porting them would help the editor community to adapt VE. It's hard to get useful help as a newcomer when none of the experienced users use the same tool that you do.

In T147618#3063710, @Tgr wrote:

In T147618#3063698, @Nemo_bis wrote:

I thought translation work was forbidden by GSoC rules: did you check? On the other hand, i18n work is always welcome and porting gadgets has nothing to do with l10n (but it's always questionable what impact such gadgets have).

Non-coding tasks are not allowed in GSoC but allowed in Outreachy. The task is certainly better suited for Outreachy, but I think there are enough coding tasks to fill a GSoC project as well - it would focus on writing Zotero plugins and adapting gadgets to VE.

Gadgets are unlikely to have direct impact on new editor retention (although I would expect them to have a major impact on the productivity of experienced editors), but porting them would help the editor community to adapt VE. It's hard to get useful help as a newcomer when none of the experienced users use the same tool that you do.

Assuming enough coding tasks, adding GSoC-2017 tag. @Tgr given the specificity of Hungarian language, is there any channel where we can post about this project that would motivate someone eligible from the Hungarian community to take this up?

Also, can you point to people who can be potential co-mentors?

@Adammia Welcome! :) I saw that you have submitted a proposal on the Outreachy's system, just want to make sure that you know you are expected to submit the same proposal here on Phabricator as well. There are some instructions in the "Recommended Next Steps" section https://www.mediawiki.org/wiki/Outreachy/Round_14#Recommended_Next_Steps, and links of some example proposals that will help you prepare one. If you've specific application related questions, let me know, and any project related ones ask @Tgr. Thank you!

In T147618#3068173, @Sumit wrote:

Assuming enough coding tasks, adding GSoC-2017 tag. @Tgr given the specificity of Hungarian language, is there any channel where we can post about this project that would motivate someone eligible from the Hungarian community to take this up?

Sorry, forgot to answer this. I posted it on Facebook and some more specific channels (hu.wikipedia village pump, Women in Tech Budapest, Women in IT Budapest, Django Girls Budapest) a while ago.

A possible microtask:

There is an old (source-based) and a new (WYSIWYG) editor on Hungarian Wikipedia. You can test them e.g. at https://hu.wikipedia.org/wiki/Special:MyPage/Teszt?action=edit (you need to select which one to load when visiting the URL for the first time, then can switch between them with the pencil icon at the top right corner of the editor area). They both have a character insertion tool but use a different format. The configuration for the old tool is at https://hu.wikipedia.org/w/index.php?title=MediaWiki:Edittools&action=edit (the special characters are listed within <charinsert>...</charinsert>, space-separated, with sometimes + used to separate start and end character); the configuration for the new tool is https://hu.wikipedia.org/w/index.php?title=MediaWiki:Visualeditor-specialcharinspector-characterlist-insert&action=edit (the format should be obvious). You can get the character insertion tool in the old editor at the bottom of the edit page (there is a dropdown with the text "Alap" which can be used to select other character sets); in the new editor with the Ω button on the toolbar.

Write a simple script that converts the old configuration to the new one. (Programming language can be arbitrary, input/output can be standard I/O or file or a literal or whatever is convenient.) Put it somewhere where it can be commented and iterated on (e.g. a paste, or a gist on GitHub).

Hi! I am Laszlo Karsai from Budapest. I would like to apply for this project in the Google Summer of Code. I would like to write my proposal but I would like to ask some questions before doing so.
Does this microtask above equals to the VisualEditor related old templete converting task?
Would it be ok if I list the tasks which are suggested in the project description in GSoC project ideas page? I would create my time line week-by-week according to the tasks.

I have gained experience with:
Android - home made projects and open source organization
Java - working experience, home made projects, homeworks
bash - working experience
python - working experience
Javascript - final project in BSc
C/C++ - Arduino, home made projects, homeworks
MySQL - working experience, homeworks

Thanks for the information in advance!

Best Regards,
László Karsai

Hi László,

In T147618#3144477, @Karsai1993 wrote:

I am Laszlo Karsai from Budapest. I would like to apply for this project in the Google Summer of Code.

Great! Note though that there is another applicant, and in the end only one person can work on this project, so if you have enough time it might be a good idea to apply for another project as well.

Does this microtask above equals to the VisualEditor related old templete converting task?

No, that one is about converting XML template descriptions like this (used by a tool called Sablonmester) into TemplateData descriptions like this. If you want to do that as a microtask, feel free!

Would it be ok if I list the tasks which are suggested in the project description in GSoC project ideas page? I would create my time line week-by-week according to the tasks.

Most of those are non-coding tasks (which are allowed in Outreachy but not in Google Summer of Code). The coding tasks are the VisualEditor-related ones:

• write software tool for converting hu.wikipedia's old template documentation system to TemplateData (explained above)
• enable Citoid (see https://www.mediawiki.org/wiki/Citoid/Enabling_Citoid_on_your_wiki)
• write Zotero plugins for major Hungarian information sources (see https://www.mediawiki.org/wiki/Citoid/Creating_Zotero_translators)
• convert the old CharInsert-based character map (explained in T147618#3139742)
• make sure all custom edit buttons/tools for which it makes sense are ported; review gadgets on large wikis and import the most useful ones (these are various custom javascript plugins for the editor, which have been written and maintained by the Wikipedia community)

The task description is somewhat superficial and the deadline is close so feel free to reach out if you have questions. You can find my availability on my user page.

Hi Gergő! Thanks for the information. I have sent you a mail to your email address.

I'm abandoning this for the current Outreachy round. My past experience was that the number of serious applicants averaged somewhere between 0 and 1 (closer to 0) so I proposed 3 projects this round, but the other two proved pretty popular, so this would be well beyond my capacity to manage.