Page MenuHomePhabricator

Outreachy 19 Proposal: Document improvements API pages on-wiki
Open, Needs TriagePublic

Description

Profile Information

Name: Priscila Vilemen
E-mail:priscilavilemen@hotmail.com
IRC Nick: Priscila
Github: https://github.com/PRISCILAVILEMEN
Location (country or state): Brazil, PE
Typical working hours (include your timezone) 9:00 AS 18:00 GMT -2

Synopsis

  • Short summary describing your project and how it will benefit Wikimedia projects

The Wikimedia Foundation supports hundreds of thousands of people around the world in creating the largest free knowledge projects in history. The work of volunteers helps millions of people around the globe discover information, contribute knowledge, and share it with others no matter their bandwidth.

my work will improve documentation of the Action API pages on-wiki.

link of my contribution --> https://github.com/wikimedia/mediawiki-api-demos/pull/185, I have contributed sample codes in Python, Javascript and PHP programming languages for the API: Pageswithprop.

  • Have you contacted your mentors already?Yes, I have been communicating with my mentor throughout the application process.

Deliverables

Describe the timeline of your work with deadlines and milestones, broken down week by week. Make sure to include time you are planning to allocate for investigation, coding, deploying, testing and documentation

5th Nov - 24th Nov

  • Improve on my PHP , Python, Java Script and MediawikiJS programming language skills.
  • Improve my knowledge on phabricator

26th November - 3rd December

  • Community bonding period - implement all the guidelines

Week 1 (3 th Dec - 8 th Dec)

  • Internships starts
  • Starts API page to review and improve --> API:Page - API:Siteinfo
  • Correcting api errors after mentor feedback --> API:Page - API:Siteinfo

Week 2 (9 th Dec - 15 th Dec)

  • Correcting api errors after mentor feedback --> API:Page - API:Siteinfo
  • End of review and improvement of API page --> API:Page - API:Siteinfo
  • The goal is to improve this page and one more

Week 3 (16 th Dec - 22th Dec)

  • Starts API page to review and improve --> API:Page - API:Iwbacklinks
  • Correcting api errors after mentor feedback --> API:Page - API:Iwbacklinks
  • 18 Dec -- > Initial feedback due

Week 4 (23 th Dec - 29 th Dec)

    • Correcting api errors after mentor feedback --> API:Page - API:Iwbacklinks
    • End of review and improvement of API page --> API:Page - API:Iwbacklinks
  • The goal is to improve this page and one more

Week 5 (30th Dec - 5th Jan)

  • Starts API page to review and improve --> API:Page - API:Revisiondelete
  • Correcting api errors after mentor feedback --> API:Page - API:Revisiondelete

Week 6 (6th Jan - 12th Jan)

  • Correcting api errors after mentor feedback --> API:Page - API:Revisiondelete
  • End of review and improvement of API page --> API:Page - API:Revisiondelete
  • The goal is to improve this page and one more

Week 7 (13th Jan - 19th Jan)

  • Starts API page to review and improve --> API:Page - API:API:Checktoken
  • Correcting api errors after mentor feedback --> API:Page - API:API:Checktoken
  • End of review and improvement of API page -->API:Page - API:API:Checktoken
  • The goal is to improve this page and one more

Week 8(20th Jan - 26th Jan)

  • Starts API page to review and improve --> API:Page - API:ClearHasMsg
  • Correcting api errors after mentor feedback --> API:Page - API:ClearHasMsg
  • End of review and improvement of API page -->API:Page - API:ClearHasMsg
  • The goal is to improve this page and one more

Week 9 (27th Jan - 2th Feb)

  • Starts API page to review and improve --> API:Page -API:Duplicatefiles
  • Correcting api errors after mentor feedback --> API:Page - API:Duplicatefiles
  • End of review and improvement of API page --> API:Page - API:Duplicatefiles
    • The goal is to improve this page and one more
  • 29th Jan Mid-point feedback due

Week 10 (3 th Feb - 9th Feb)

  • Starts API page to review and improve --> API:Page - API:Expandtemplates
  • Correcting api errors after mentor feedback --> API:Page - API:Expandtemplates
  • End of review and improvement of API page --> API:Page - API:Expandtemplates
    • The goal is to improve this page and one more

Week 11 (10 th Feb - 16th Feb)

  • Starts API page to review and improve --> API:Page - API:Compare
  • Correcting api errors after mentor feedback --> API:Page - API:Compare
  • End of review and improvement of API page --> API:Page - API:Compare
    • The goal is to improve this page and one more

Week 12 (17 th Feb - 23 th Feb)

  • Starts API page to review and improve --> API:Page - API:Tag
  • Correcting api errors after mentor feedback --> API:Page - API:Tag
  • End of review and improvement of API page --> API:Page - API:Tag
  • The goal is to improve this page and one more

Week 13 (24 th Feb - 03 th March)

  • Starts API page to review and improve --> API:Page - API:Validatepassword
  • Correcting api errors after mentor feedback --> API:Page - API:Validatepassword
  • End of review and improvement of API page --> API:Page - API:Validatepassword
  • The goal is to improve this page and one more
  • 3 th March Internships end
  • 10 th March Final feedback due

Note: I will do my best to make a minimum of 20 pages correction, but as this is the first project I work on, I estimated my 10 page timeline.

Participation

Describe how you plan to communicate progress and ask for help, where you plan to publish your source code, etc

  • Regular communication with my mentors and other community members at mediawiki
  • I will make a new repo on git and maintain two branches. Code will be uploaded to the dev branch periodically and will be merged with the master branch once review and testing is done.
  • I will be online on IRC in my working hours ( 9:00 am to 6:00 pm GTM +2:00) to collaborate with the mentors.
  • I will use Phabricator for managing bugs and subtasks.
  • I will be available in hotmail to be contacted when needed in the non-working hours.

About Me

Tell us about a few:

  • Your education (completed or in progress):

Graduated in 2015 at the Catholic University of Pernambuco (UNICAP) in Civil Engineering, maintenance of structures specialist, formed by the University of Pernambuco (UPE) Experience in the ​​civil construction area, and passionate about ​​project management. Knowledge in various engineering software, easy in communication and people management. Working directly to expand the Recife-PE office of multinational ThoughtWorks, an American company in the area of ​​information technology, particularly involved with the project called Buildout - Rec, where I was interested in the area of information technology.

  • How did you hear about this program? Referral from technology friends
  • Will you have any other time commitments, such as school work, an other job, planned vacation, etc, during the duration of the program? Not I am free for work in this program
  • We advise all candidates eligible for Google Summer of Code and Outreachy to apply for both programs. Are you planning to apply to both programs and, if so, with what organization(s)? Not, I am not eligible.
  • What does making this project happen mean to you? Is my first experience in the area of the technology, it's the beginning of my career in technology.

Past Experience

Describe any relevant projects that you've worked on previously and what knowledge you gained from working on them. Describe any open source projects you have contributed to as a user and contributor (include links). If you have already written a feature or bugfix for a Wikimedia technology such as MediaWiki, link to it here; we will give strong preference to candidates who have done so This is my first experience contributing open source

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMon, Nov 4, 11:17 AM
Prisicilavilemen updated the task description. (Show Details)EditedMon, Nov 4, 11:34 AM

@jeropbrenda , @Pavithraes --> How to know whats tasks to do week by week, please help me ;)

Assuming this task is about Outreachy Round 19.

Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)

@jeropbrenda , @Pavithraes --> How to know whats tasks to do week by week, please help me ;)

@Prisicilavilemen The weekly breakdown of tasks is based on your own judgement of how long you think each task will take :)

Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)

@jeropbrenda , @Pavithraes --> How to know whats tasks to do week by week, please help me ;)

@Prisicilavilemen The weekly breakdown of tasks is based on your own judgement of how long you think each task will take :)

@jeropbrenda and @Pavithraes , Please check my tasks is correctly. ;)

Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen added a comment.EditedMon, Nov 4, 8:14 PM

@jeropbrenda , @Pavithraes I finished mine proporsal, Now what I do?

@Prisicilavilemen Your proposal looks great! A few comments:

  • For those questions which you have not answered, you could leave them out e.g. Resume etc.
  • To make your proposal more readable, you could use a bold format on the questions then use a normal format on the answers.
  • We hope to cover at least 20 pages during the internship but you have mentioned less than ten.
  • Please mention in the task title that this is a proposal. You could use something like: "Outreachy 19 Proposal: Document..."

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 19) workboard in Phabricator. :)

Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen renamed this task from Documentation improvements to the ~20 top 100 most viewed MediaWiki Action API pages on-wiki to Outreachy 19 Proposal: Document improvements API pages on-wiki.Tue, Nov 5, 10:36 AM
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen updated the task description. (Show Details)
Prisicilavilemen added a comment.EditedTue, Nov 5, 12:12 PM

@jeropbrenda

  • We hope to cover at least 20 pages during the internship but you have mentioned less than ten.

About this item I enlarged the pages, in all there are 10 in my timeline, I'm not feeling to put 20 pages because that would mean 1 and a half pages a week I don't know if I can tell you how it's my first time on a project. but I will do my best to make the most pages, do you think putting 10 pages my proposal will not be accepted?

@Prisicilavilemen Your proposal looks great! A few comments:

  • For those questions which you have not answered, you could leave them out e.g. Resume etc.
  • To make your proposal more readable, you could use a bold format on the questions then use a normal format on the answers.
  • We hope to cover at least 20 pages during the internship but you have mentioned less than ten.
  • Please mention in the task title that this is a proposal. You could use something like: "Outreachy 19 Proposal: Document..."

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 19) workboard in Phabricator. :)

Prisicilavilemen updated the task description. (Show Details)

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!