User Details
- User Since
- Oct 11 2016, 9:19 PM (131 w, 6 d)
- Availability
- Available
- IRC Nick
- srishakatux
- LDAP User
- Unknown
- MediaWiki User
- SSethi (WMF) [ Global Accounts ]
Fri, Apr 19
Thu, Apr 18
@Ragesoss Is there anything remaining in this task from Outreachy Round 17? If not, then please consider marking it as resolved!
@farida29 Is there anything remaining in this task from Outreachy Round 17? If not, then please consider marking it as resolved!
@Barbvd @Etonkovidova Is there anything remaining in this task from Outreachy Round 17? If not, then please consider marking it as resolved!
@Ephemeralwaves Is there anything remaining in this task from Outreachy Round 17? If not, then please consider marking it as resolved!
Wed, Apr 17
User feedback gadget can currently be seen in action in the help namespace on Wikitech. Scroll to the bottom of the following page: https://wikitech.wikimedia.org/wiki/Help:Toolforge to view the documentation feedback form.
Tue, Apr 16
Mon, Apr 15
Thu, Apr 11
Instructions to fetch eventlogging data are in:
https://www.mediawiki.org/wiki/User:SSethi_(WMF)/Sandbox/Eventlogging_data_access
Tue, Apr 9
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
If you would like us to consider your proposal for review, please move it to the submitted column on Google-Summer-of-Code (2019) board.
(removing assignee as selection process is still ongoing)
@Jwu96 Thanks for your proposal! Could you also update the proposal w/ links to any prior contributions to FOSS projects or Wikimedia (if any)?
What we currently have in the diagram looks perfect! An alternative might be that these three are at the same level: Planning to work on a specific project, Want a mentor, Want to be a mentor. Also, as each one of these three ties to a specific audience: folks ready to hack, newcomers, mentors, etc., they all possibly fall under the bigger question: "Do you already know what you want to do?".
@Samwilson Thanks! Just sent you an invite.
+1 to keeping the skill-share board physical. In the past, I remember that we've tried to maintain an etherpad as well with a list of folks and the skills they can offer. From what I remember that was mostly an extra effort and not quite helpful.
Mon, Apr 8
@Townie Great proposal :) @Petar.petkovic @Niharika I've sent you both invitation to sign-up as a mentor on the GSoC site. It would be great if at least one of you could be active there.
@Rammanojpotla Looks great! Only one comment: include links to all merged patches you contributed to MediaWiki core/ extensions etc. Separate the ones contributed in this round from the previous one in different sections. When you are done making the changes, move your proposal on the submitted column on the Google-Summer-of-Code (2019) board. Also, remember to upload your proposal on the program website.
@Shivanshbindal9 Neat! I've read your proposal and it looks great! I've no further changes to suggest and you can move your proposal to the submitted column on the Google-Summer-of-Code (2019) board. Also, remember to upload the proposal on GSoC program website.
Sat, Apr 6
@Sumanth699 Looks great! The only thing that needs a change in your proposal is the section between Phase 1 & 2. What I imagine is that the documentation of code samples will happen alongside the coding work. So, the one month time period that you've allocated to documentation work feels too much. Some of the work in Phase 1 can be moved to Phase 2.
Fri, Apr 5
@Wisdomanthoni Looks great! Only thing that your proposal is missing right now is a brief overview of demo app. It is okay if you don't have a clear idea on what you would like to develop, just make sure you include demo app in the timeline. When you are done making the changes, move your proposal to the submitted column on Google-Summer-of-Code (2019) board. Also, remember to upload it on the program website before the deadline.
@Jayprakash12345 Hi! I've read your proposal and it looks great! Two small comments:
- In the timeline section, before Phase 1 evaluation, you can also include Javascript code samples as we still need some for certain API modules.
- Might be in the timeline section, you can add a note about the demo app that the priority would be to develop an app that is already in demand and might help a language community.
(Opening it as the initial application got approved before the deadline)
Mon, Apr 1
Folks interested in applying for this project, I encourage you to finish writing your proposal in Phabricator by Friday (April 5th). Ping me on Zulip when you're done so that I can review your application and give you some feedback that you can incorporate before the deadline.
@Aroravanshika Unfortunately, I will have to decline this task as your initial application for Outreachy didn't pass the eligibility check (as per our recent email). I encourage you to apply in the next round!
Thu, Mar 28
Mon, Mar 25
Mar 24 2019
@Areefa I've read your proposal, and it looks good to me. Totally optional: you could include in your proposal a project you've worked on previously, needn't be a big project, and also a link to it on Github or elsewhere.
Whenever you are ready, you can submit your proposal on the Outreachy site and move it to the "Proposals Submitted" column on the Outreachy (Round 18) workboard in Phabricator.
Mar 20 2019
@Didicodes Your proposal looks good to me! I only have one minor suggestion:
Mar 19 2019
@Eisheeta Your proposal looks good to me! Only curious about these pages you've mentioned:
https://www.mediawiki.org/wiki/Manual:EmptyUserGroup.php
Wrote documentation for the maintenance script emptyUserGroup.phphttps://www.mediawiki.org/wiki/Manual:Maintenance_scripts
Updated documentation of Manual: Maintenance_scripts by adding Manual:EmptyUserGroup.php's documentation to the list of maintenance scripts.https://www.mediawiki.org/wiki/Manual:Pywikibot/Third-party_Wiki_Quick_Start
Fixed typos and grammar in the above page to improve readability.https://www.mediawiki.org/wiki/API:FAQ/hi
Translating the above page from English to Hindi
@Nikitrain Your proposal looks good to me! I only have a couple of minor suggestions:
- You can club together some of the about me info, currently I see that some of it are before the timeline and towards the end of your proposal. You can add in it any relevant links, other FOSS projects you've contributed to, etc.
- I see that there are a lot of links to patches you've provided where you've made a typo fix. You can consider grouping them all under one point and cut down details.
Whenever you are ready, you can submit your proposal on the Outreachy site and move it to the "Proposals Submitted" column on the Outreachy (Round 18) workboard in Phabricator.
@jeropbrenda Your proposal looks great!! You've covered all the points and I don't have recommendation for more changes that you could add. Whenever you are ready, you can submit your proposal on the Outreachy site and move it to the "Proposals Submitted" column on the Outreachy (Round 18) workboard in Phabricator.
Mar 18 2019
@Usmanmuhd I would encourage you to read a few good proposals from previous years to get some pointers on what to include in your proposal: https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants#Application_process_steps (see Step 8).