Hello all,
I'm finishing up the evaluation portion of my API client library internship project. As a part of that, I'm making sure that feedback/bug reports/feature requests end up where they should be. I made several suggestions at the end of the pywikibot-core evaluation,[1] and have been linking bugzilla issues to some of the criteria. I also left comments on the documentation RFC [2] with the documentation-related suggestions.
This leaves a handful of larger-scale/general/structural suggestions for change:
* As of 25 July 2014, there are 105 open patches in gerrit. The patch review process should be streamlined and/or prioritized to reduce the backlog of unreviewed patches.
* Iterating over a list and calling the API for each item is an inefficient use of API calls. Pywikibot could be made more efficient by combining API calls as much as possible (e.g. using generators and combining resultstitle=title1|title2|...). One option may be a constructor method that collects Page requests and enables larger, less frequent API calls.
* The initial installation process features a series of obscure options and confusing installation documentation. Redesign the initial installation/configuration process to be lighter-weight, soliciting and valuing feedback from new or one-time users in the redesign process. Is it necessary to be logged in before `import pywikibot` will not cause an error?
* Foster a hospitable attitude on pywikipedia-l, especially to new and/or inexperienced users. Consider agreeing on community standards for interaction; the Hacker School social rules[3] may be a useful starting point.
Is Bugzilla the best place for these? Would these be useful to discuss at the pywikibot hackathon at Wikimania? Is there somewhere else these suggestions ought to go?
-Frances
[1] https://www.mediawiki.org/wiki/API:Client_code/Evaluations/Pywikibot#Suggest... [2] https://www.mediawiki.org/wiki/Manual:Pywikibot/Documentation_RFC#Suggestion... from pywikibot gold-standard evaluation [3] https://www.hackerschool.com/manual#sec-environment
I think the Hackathon and IRC (and here) are the best places to discuss about this
If you want to make a feature request the best place is bugzilla you need to mark to severity to "enhancement" but these issues are more general than what people usually report in bugzilla.
Another thing: pywikipedia-l isn't a hospitable place?
On 7/26/14, Frances Hocutt frances.hocutt@gmail.com wrote:
Hello all,
I'm finishing up the evaluation portion of my API client library internship project. As a part of that, I'm making sure that feedback/bug reports/feature requests end up where they should be. I made several suggestions at the end of the pywikibot-core evaluation,[1] and have been linking bugzilla issues to some of the criteria. I also left comments on the documentation RFC [2] with the documentation-related suggestions.
This leaves a handful of larger-scale/general/structural suggestions for change:
- As of 25 July 2014, there are 105 open patches in gerrit. The patch
review process should be streamlined and/or prioritized to reduce the backlog of unreviewed patches.
- Iterating over a list and calling the API for each item is an
inefficient use of API calls. Pywikibot could be made more efficient by combining API calls as much as possible (e.g. using generators and combining resultstitle=title1|title2|...). One option may be a constructor method that collects Page requests and enables larger, less frequent API calls.
- The initial installation process features a series of obscure
options and confusing installation documentation. Redesign the initial installation/configuration process to be lighter-weight, soliciting and valuing feedback from new or one-time users in the redesign process. Is it necessary to be logged in before `import pywikibot` will not cause an error?
- Foster a hospitable attitude on pywikipedia-l, especially to new
and/or inexperienced users. Consider agreeing on community standards for interaction; the Hacker School social rules[3] may be a useful starting point.
Is Bugzilla the best place for these? Would these be useful to discuss at the pywikibot hackathon at Wikimania? Is there somewhere else these suggestions ought to go?
-Frances
[1] https://www.mediawiki.org/wiki/API:Client_code/Evaluations/Pywikibot#Suggest... [2] https://www.mediawiki.org/wiki/Manual:Pywikibot/Documentation_RFC#Suggestion... from pywikibot gold-standard evaluation [3] https://www.hackerschool.com/manual#sec-environment
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Hi Amir,
On 27 July 2014 07:14, Amir Ladsgroup ladsgroup@gmail.com wrote:
Another thing: pywikipedia-l isn't a hospitable place?
Today, I discussed this with Frances and Sumana a bit, and these are my thoughts on it. Basically, I think there are several things we could improve on. It's not so much that pywikipedia-l is inhospitable, it's rather that it's not as hospitable we could make it.
There are three points I can think of: 'passive inhospitability', in that e-mails sometimes do not get answered. Luckily, you are always very quick in replying to new users, which is great! Still, some mails stay unanswered, and we (as pywikipedia-l) could improve on that. Maybe we can also mention on the mailing list page that IRC might be a better choice than the mailing list for people just getting started to get help.
Secondly, a lot of the discussion on-list is aimed at experienced developers, and assumes a high level of understanding of pywikibot. This can scare people away that want to ask a simple question. This is something we could improve by maybe explicitly mentioning on the mailing list page that basic questions are very welcome, and by actively promoting discussions with people who are unsure how to contribute.
Thirdly, there is 'active inhospitability', which can range from 'RTFM' emails to venting frustration to berating others. Pywikipedia-l (or any other mailing list, for that matter) is /not/ the place for that. I've fallen for the 'venting frustration' a myself, but it's important to keep in mind this shapes the image of the project for people who may not be actively participating at the moment. They might not participate because of a negative atmosphere. Please send frustration-venting emails to me ;-), and send only the constructive mails to the mailing list :-)
Merlijn
Hey!
On 7/29/14, Merlijn van Deen valhallasw@arctus.nl wrote:
Hi Amir,
On 27 July 2014 07:14, Amir Ladsgroup ladsgroup@gmail.com wrote:
Another thing: pywikipedia-l isn't a hospitable place?
Today, I discussed this with Frances and Sumana a bit, and these are my thoughts on it. Basically, I think there are several things we could improve on. It's not so much that pywikipedia-l is inhospitable, it's rather that it's not as hospitable we could make it.
There are three points I can think of: 'passive inhospitability', in that e-mails sometimes do not get answered. Luckily, you are always very quick in replying to new users, which is great! Still, some mails stay unanswered, and we (as pywikipedia-l) could improve on that. Maybe we can also mention on the mailing list page that IRC might be a better choice than the mailing list for people just getting started to get help.
Thank you :) Sometimes I can't be online for a while otherwise I'll answer them as soon as I can. but saying IRC is a better place, I doubt that because I saw several times A person came and asked but since there was no one online (no one who checks the channel) the question remained unanswered.
Secondly, a lot of the discussion on-list is aimed at experienced developers, and assumes a high level of understanding of pywikibot. This can scare people away that want to ask a simple question. This is something we could improve by maybe explicitly mentioning on the mailing list page that basic questions are very welcome, and by actively promoting discussions with people who are unsure how to contribute.
I agree :)
Thirdly, there is 'active inhospitability', which can range from 'RTFM' emails to venting frustration to berating others. Pywikipedia-l (or any other mailing list, for that matter) is /not/ the place for that. I've fallen for the 'venting frustration' a myself, but it's important to keep in mind this shapes the image of the project for people who may not be actively participating at the moment. They might not participate because of a negative atmosphere. Please send frustration-venting emails to me ;-), and send only the constructive mails to the mailing list :-)
As I told before If pywikibot doesn't work properly you can yell at me ;) no matter it's my fault or not. so please if you angry about something in pywikibot please send your e-mail to me not here.
Merlijn
pywikipedia-l@lists.wikimedia.org