The WMF Annual Plan 2015-16 includes a goal related to this task:

Set and monitor code review KPIs for all community-sourced contributions

Solving this task will help identifying "community-sourced" contributions.

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. T101393: Goal: All completed GSoC and Outreachy projects have code merged and deployed by September for details.

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

Good luck!

@Acs @Dicortazar this project is still featured at Possible-Tech-Projects. Do you want to propose it for Outreachy-Round-11 for December-March?

This is a message sent to all Possible-Tech-Projects. The new round of Wikimedia Individual Engagement Grants is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after (T105414). If someone is interested in obtaining funds to push this task, this might be a good way.

Is there any chance that this project gets proposed for Outreachy-Round-11. I'd like to contribute. I've worked with PHP, Javascript, HTML5, CSS3 and I am quite familiar with Angular framework as well. I've made an app with python flask framework as well. Here's the link to my Github Repository https://github.com/simmimourya1

In T60585#1677452, @Simmimourya3107 wrote:

Is there any chance that this project gets proposed for Outreachy-Round-11.

@Dicortazar and @Acs: Could you answer this, as possible mentors? See Qgil's comment above.

Hi there,

I'm having some discussion at https://phabricator.wikimedia.org/conpherence/200/ about this.

I guess that link is public, so anyone is welcome to participate :).

@Dicortazar, that link is not public. :)

In T60585#1683422, @Dicortazar wrote:

I'm having some discussion at https://phabricator.wikimedia.org/conpherence/200/ about this.

You need to explicitly add participants to allow them accessing that discussion thread

Hi! I would like to this project for Outreachy December 2015-March 2016
I am familiar with data analytics and machine learning. I have worked on a project to detect skin diseases by analysing images.
I am also familiar with Django and Python. I am developing a website for integration of APIs using Django.
@jgbarah could you suggest what I should do next?

In T60585#1677452, @Simmimourya3107 wrote:

Is there any chance that this project gets proposed for Outreachy-Round-11. I'd like to contribute. I've worked with PHP, Javascript, HTML5, CSS3 and I am quite familiar with Angular framework as well. I've made an app with python flask framework as well. Here's the link to my Github Repository https://github.com/simmimourya1

Sorry for my delay in coming here. Yes, you can work on the project. But it is much more in the area of Python than PHP, I have to say... Currently the basic technology is SortingHat, which provides access to identities, merging of identities, affiliation, etc. I'm updating the description to reflect that, and be a bit more precise about the idea.

In T60585#1706581, @Oakshweta11 wrote:

Hi! I would like to this project for Outreachy December 2015-March 2016
I am familiar with data analytics and machine learning. I have worked on a project to detect skin diseases by analysing images.
I am also familiar with Django and Python. I am developing a website for integration of APIs using Django.
@jgbarah could you suggest what I should do next?

As I've just commented, I'm going to update the description a bit. Let's talk after that. I guess there is probably little need of analytics and the like, the project is mostly about implementing an HTTP API to a MySQL database in Python, and an Angular-based HTML5 front-end to it.

Proposal for GSoC 2015, by Sarvesh Gupta, moved to this comment, to make the description more clear, while preserving the interesting analysis and planning, that maybe somebody can use as inspiration.

Proposal

Name and contact information

Name: Sarvesh Gupta
Email: sarvesh.onlyme@gmail.com(primary), sarveshgpt1991@yahoo.com
IRC or IM networks/handle(s): s1991
Location: Roorkee, India
Timezone: Kolkata, INDIA, UTC+5:30
Typical working hours: 1pm to 2am untill 20th July, 5pm to 2am after 20th July

Synopsis

This project was thought up for providing a way for contributors to manage their identities, update or make possible changes to their information by providing a web interface above korma technology. Along with this develop a dashboard for admin, so that she can have control over contributor's profile and identities. For now contributor of MediaWiki has to go through a process which consumes more time in updating information to database for updating their profile and also there is no admin control due to unavailability of web interface, so it is a kind of necessary for community to have a web interface which facilitates them to have an easy access to their profile. Moreover, sortingHat is required to implement REST API and provide more precise method for identity matching, so this project also aims to improve as well as implement the sortingHat to flask framework.

What it means to accomplish?

Extends the functionality of MediaWiki-Dashboard

Step 1: Develop an angularJS based UI providing contributors with authentication access to deal with their identities, affiliation.

Step 2: Presenting information to the users i.e. identities, affiliation or organizations.

Step 3: Allowing users to update their information, add new identities and so on.

Step 4: Allow contributors to search for their profile using some sort of identity and to perform actions like sync or merge with their existing multiple identities which will be handled by sortingHat.

Step 5: Work on SortingHat so that it fulfill the requirement of our project.

How it will benefit MediaWiki or Wikimedia projects such as Mediawiki Community Metrics?

• It will help improving the information about Contributor's activity in tech Community metrics for example here.
• It make less cumbersome for contributors for submitting and editing their data by providing a web interface.
• It'll provide an search method for identities to further sync contributor's account.

Possible mentor

• Alvaro del Castillo
• Daniel Izquierdo

Deliverables

The main deliverable will be a working web application for contributors to manage community identity.

Required Deliverables

• The angularJS technology based web interface of each and every page of the web application required (milestone 1)
• Flask (python based web-framework) based back-end part with implementation of templates(front-end) part to it (milestone 2)
• Optimized search facility with autocomplete feature. User can search and filter the data or information (milestone 3)
• Working and modeling SortingHat so that our project can took full advantage of SortingHat (milestone 4)
• Implementation of Authentication techniques to our project (probably openstack-Keystone). (milestone 5)
• Testing and Documentation.

Optional Deliverables

• An admin dashboard, so that admin can manage/control contributor's activity.

Schedule

Envisioning phase (May 5 - May 24)

• Remain in constant touch with my mentor(s) and community.
• Getting myself familiarize with community and development environment.
• Getting myself familiarize with working of Flask.
• Study required docs.
• Fix some bugs along the way and get my hands dirty.

Community bonding period(1 weeks, May 25 - May 31)

• Further discussion with my mentor(s) and my community about the prototype and its implementation.
• Make a Roadmap or workflow for development phase

AngularJS implementation (2 weeks, June 1 - June 14) - Milestone-1

• Thinking of using ngbp repo to get kick-started with AngularJS, Bootstrap
  • Get myself familiar with repo's architecture and implementation
• Design AngularJS UI, which will be implemented in Flask framework.
  • Methods for Login/Signup, will work on authentication at last.
  • Methods for Contributor's profile view
  • Methods to list the identities, affiliation, etc
  • Prototypical implementation of search tools.
• This will require use of AngularJS or may be Ajax

Flask implementation part (2 weeks, June 15 - June 28) - Milestone-2

• Getting myself familiarize with Flask (already familiar with Django, so won't take too much time)
• Setting up Flask project
• Implement the back-end
  • Contributors to view her/his profile
  • Updating information and identities.
  • List identities, affiliation
• In parallel to above step, syncing angularJS to Flask
• This will require use of Flask framework, python, angularJS

Mid-term evaluation

• For mid-term, I will be submitting the working model up-till now.

Implement search and filter (1 week, June 29 - July 5) - Milestone-3

• Investigating search options
  • Discussing with mentor about search techniques that can be implemented, such as Flask libraries aiding to search techniques such as Woosh or Haytack.
  • Understanding the library that needs to be implement.
• Script for search and filter implementation in which contributor can search for his/her other existing identities.
• Syncing it with front-end.
• This will require use of python, Ajax and javascript.

Research Period (1 week, July 6 - July 12)

• Getting my self familiar with working of sortingHat.
• Discuss with mentor(s) with the future work on sortingHat related milestone.

Implementing sortingHat (2 weeks, July 13 - July 26) - Milestone-4

• Improving the sortingHat heuristics, so that it can be implemented to our project.
• (Not so sure about milestone for now, need to figure out in Research Period)

Implementing Authentication Technique (1 week, July 27 - Aug 2) - Milestone-5

• Discuss with mentor about existing techniques for authentication (probably openstack-keyston).
• Getting myself familiar with finalized technique
• Implementing the technique to project.

Deploying phase (2 weeks, Aug 3 - August 16)

• Code Review
  • Conduct code review by myself, then mentor(s)
  • Inact information gained by code review
• Testing
  • Further unit and integration testing
  • Conduct several rounds of testing for real-world users.
• Documentation
  • Write approach program and functional descriptions
  • Document deployment and testing.

Pencil Down

• August 17: Soft Pencil down - A weak for final polishing
• August 21: Firm Pencil down
• Submission to Google

Participation

Communication of progress

• IRC channel: I'll stay online on IRC at #metrics-grimoire in freenode, in my working hours.
• Email: I will make several check points (within 24 hours) for reading emails and replying as soon as possible.
• Mailing list: metrics-grimoire will be used to communicate progress
• Blog: Though I've need started blogging, I would surely try to maintain a blog throughout the project.

Publishing Source code

• Github

Where I would turn for help?

• Solve by myself: Read documentation, search online, etc
• Seek helps from community: Discuss on IRC, mailing list or mentor(s).
• Seek helps from outside the community: My work has a lot to do with Flask, authentication techniques, so can turn to different communities for help.

Amenities: I understand, there have been power and internet issues with students from India in past. I've a stable and always-on internet connection and live in a housing society with 24-hours power backup, so that will not be a problem.

About you

I'm Sarvesh Gupta, third year student at Indian Institute of Technology - Roorkee with major Computer Science. I enjoy trying out and learning new things related to web technology.

I love coding and experienced with python, Django, php, javascript, jQuery, mysql, coffescript, MVC architectures and I always do keep working on some project, here's my Github profile.

I want to go for organisation which is mostly used by people. Also I would feel better is my project could work beyond GSoC and used by as many users as possible.

Lastly, I promise to work for at least 40 hr. per week. No other obligations interfere throughout GSoC project.

Past experience

I’ve worked for Oregon State University Open Source Organization in last summer during GSoC-14, here is the link of abstract of work done to last year’s GSoC.

My github link can be found here

Wikimedia will be my third encounter with Open Source. I've fix some bugs(#1, #2, #3) for Mozilla organization related to Automation and Tools. My commits can be seen here with username 'sarvesh-onlyme'.

For now, I'm planning to contribute for MediaWiki through GSoC.

Links

• https://github.com/metricsgrimoire
• http://metricsgrimoire.github.io
• http://korma.wmflabs.org
• https://www.mediawiki.org/wiki/Community_metrics
• http://demo.bitergia.com/doc/
• https://github.com/MetricsGrimoire/sortinghat

In T60585#1706581, @Oakshweta11 wrote:

@jgbarah could you suggest what I should do next?

I would start with T114838: Microtask: Create a very simple REST API for SortingHat, which shouldn't be too time-consuming.

In T60585#1677452, @Simmimourya3107 wrote:

Is there any chance that this project gets proposed for Outreachy-Round-11. I'd like to contribute. I've worked with PHP, Javascript, HTML5, CSS3 and I am quite familiar with Angular framework as well. I've made an app with python flask framework as well. Here's the link to my Github Repository https://github.com/simmimourya1

If interested, I would start with T114838: Microtask: Create a very simple REST API for SortingHat, which shouldn't be too time-consuming.

I'll start with T114838: Microtask: Create a very simple REST API
Thanks.

I am shifting this to Outreachy-Round-11 as the project description has atleast two mentors, micro-tasks and looks ready for the 11th edition of Outreachy ( Dec 2015 - Mar 2016 ) . Potential candidates should start by submitting their proposals as a blocker for this task, by November 02.

Feel free to revert it back, if this task has some relevant issues which might block its completion in this term of Outreachy.

Hi @Aklapper, we've just included some changes in our affiliation process. Before starting to match identities we get a JSON file that you can modify in a private repo. After sortinghat (the tool who handles the identities imports this data and get the new people) finishes we export again that file to the private repo. In order to give you access to that file, please send me via email your github user.

My email is lcanas at bitergia.

(this is @Lcanasdiaz from a different account due to login issues)

In T60585#1734314, @01tonythomas wrote:

I am shifting this to Outreachy-Round-11 as the project description has atleast two mentors, micro-tasks and looks ready for the 11th edition of Outreachy ( Dec 2015 - Mar 2016 ) . Potential candidates should start by submitting their proposals as a blocker for this task, by November 02.

Feel free to revert it back, if this task has some relevant issues which might block its completion in this term of Outreachy.

Fine with me. Thanks.

@jgbarah : are you planning to mentor https://phabricator.wikimedia.org/T89135 - 'Improving MediaWikiAnalysis' too in this program, as it still have your name in the Primary mentor list ?

Hello! I would like to work on this project for Outreachy Round 12 and I have also started with the first microtask T114838: Microtask: Create a very simple REST API for SortingHat. I wanted to know how to proceed further, i.e., where to send the link of my github repo of the first microtask.

In T60585#2007384, @Kurisutina24 wrote:

Hello! I would like to work on this project for Outreachy Round 12 and I have also started with the first microtask T114838: Microtask: Create a very simple REST API for SortingHat. I wanted to know how to proceed further, i.e., where to send the link of my github repo of the first microtask.

Great to know about your interest @Kurisutina24. I am not sure yet if this task would be Featured for GSoC/Outreachy this round, but since it is still in https://phabricator.wikimedia.org/tag/possible-tech-projects/ - you are welcome to understand the problem, and come up with a proposal.

You can find the lifetime of a GSoC/Outreachy project over here - https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project, and you should be updating the microtask, once you have done something relevent with it. In case you have some questions about it, please ask directly in the relevant micro-task ( and not in the project task ).

@Kurisutina24: Hi and welcome! Please also check https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Communicate_that_you_work_on_a_bug - Thanks!

@jgbarah , @Dicortazar , @Acs, are you ready to push this project in this round of GSoC '16/Outreachy-12 ?

This task featured in GSoC 15', but does it need further work? whats the current progress? Is this still a Possible-Tech-Projects candidate that we can have it for an Outreachy round? Some clarifications would be great!

@jgbarah @Dicortazar @Acs Would there be any interest in mentoring this project for Google-Summer-of-Code (2018) or Outreachy (Round-16)? More here:
http://www.mediawiki.org/wiki/Google_Summer_of_Code/2018
https://www.mediawiki.org/wiki/Outreachy/Round_16
Roles and responsibilities of mentors before, during and after the program: https://www.mediawiki.org/wiki/Google_Summer_of_Code/Mentors.

Note: The task description is very outdated and links to technology and websites that we do not use anymore.
More important though: It is unclear to me how and why a random person would be motivated to edit "the information about themselves and other contributors" (like what exactly? Maybe the name and affiliation, but what else is even relevant?) and who/how those changes would get verified.

Removing Possible-Tech-Projects as we are planning on killing that workboard soon. In its current state, it is not a good fit for Outreach-Programs-Projects either..