Page MenuHomePhabricator

Add Pywikibot as a featured project to the software list on mw:New_Developers
Closed, ResolvedPublic

Description

https://www.mediawiki.org/wiki/New_Developers
It's the entry point of new developers, specially in events like Wikimedia-Hackathon-2016 and Google-Code-In-2016

Event Timeline

Restricted Application added subscribers: pywikibot-bugs-list, Aklapper. · View Herald Transcript

See https://www.mediawiki.org/wiki/New_Developers/Featured_Projects - is this wanted and supported by the Pywikibot maintainers when it comes to quick reviewing of patches?
https://lists.wikimedia.org/pipermail/pywikibot/2016-August/009493.html might only be an individual opinion and things might have changed, but it worries me when it comes to patch review of new contributions.

Just a quick note to share: Pywikibot showed up in our list of projects with most new volunteers in the quarterly report https://www.mediawiki.org/wiki/New_Developers/Quarterly/2018-01#New_developers_metrics_and_trends.

Aklapper renamed this task from Add Pywikibot to the New_Developers software list to Add Pywikibot as a featured project to the software list on mw:New_Developers.Feb 23 2018, 1:07 PM

Could you answer T179775#3965672 please, if possible?
Or any existing discussion among Pywikibot maintainers about this topic that you could link to? Thanks!

Framawiki added subscribers: Dvorapa, Xqt, Mpaa and 3 others.

is this wanted and supported by the Pywikibot maintainers when it comes to quick reviewing of patches?

Ping @Xqt @Dvorapa @zhuyifei1999 @Mpaa @jayvdb @Dalba, what do you think about this ?
IMO we're actually fast enough to review simple patches. Rereading the larger ones is already more complex.

what do you think about this ?

No objections

https://lists.wikimedia.org/pipermail/pywikibot/2016-August/009493.html is Amir attacking me without naming me, because his patches were not being accepted. It is full of lies. I have stepped away from Pywikibot as a result of that email, except for mentoring GSoC and GCI students.

(offtopic, but: @jayvdb: As a result of the hostility between you and Amir you both stepped away from Pywikibot and I would say we miss you jayvdb)

This task is about to help us to get more attendants from GSoC and GCI projects, right?

This task is about to help us to get more attendants from GSoC and GCI projects, right?

It would not be Google Code-In because GCI tasks need to be explicitly proposed by mentors, but in theory GSoC and Outreachy when it comes to outreach programs.

is this wanted and supported by the Pywikibot maintainers when it comes to quick reviewing of patches?

IMO we're actually fast enough to review simple patches. Rereading the larger ones is already more complex.

Obviously, larger patches takes time, but simple patches are really fast.

Well, it's not about "objections" here. It's about committing to maintain a list of tasks suitable for starters, to help, to review their code. :)

We will try to list all info needed from that page on some Pywikibot subpage on mediawiki.org, would it be okay?

https://lists.wikimedia.org/pipermail/pywikibot/2016-August/009493.html might only be an individual opinion and things might have changed, but it worries me when it comes to patch review of new contributions.

This is more like past issue now, both participants are not actively working on Pywikibot since then and (although we miss every retired developer) the developer base moved to other people who are continuously working on "making Pywikibot great again".

Well, it's not about "objections" here. It's about committing to maintain a list of tasks suitable for starters, to help, to review their code. :)

We will try to list all info needed from that page on some Pywikibot subpage on mediawiki.org, would it be okay?

Or better to direct edit https://www.mediawiki.org/wiki/New_Developers by us? Or create some draft or the frame to let you check if it suits?

We will try to list all info needed from that page on some Pywikibot subpage on mediawiki.org, would it be okay?

Based on experience I'd recommend to use the issue tracker itself to create such a list. Having separate lists often means that one list gets outdated.
https://phabricator.wikimedia.org/maniphest/query/zpglFo7OnNYS/#R lists some open good first task tasks for Pywikibot (not sure if the list of query tags is complete though).

I added the project to the page, improvements and mentors are welcome. I hope everything in the list is fulfilled with Pywikibot, please review anyway

Framawiki assigned this task to Dvorapa.

Great, thanks @Dvorapa !

Great, thanks @Dvorapa !

+1. But why to clone the repo from github clone instead of gerrit?

Great, thanks @Dvorapa !

+1. But why to clone the repo from github clone instead of gerrit?

I changed it to Gerrit then