Re: [Wikitech-l] Phabricator monthly statistics - 2015-09
Thank you for your message. I am currently out of the office, with no email access. I will be returning on October 12, 2015. Vielen Dank für Ihre Nachricht. Ich bin derzeit nicht im Büro und lese auch keine E-Mails. Ich bin ab dem 12.Oktober 2015 zurück und werde dann meine E-Mails bearbeiten. Falls Sie Fragen bezüglich der Studie zur “Forschungspraxis in den Geisteswissenschaften” haben, wenden Sie sich bitte an Frau Alexa Schlegel (alexa.schle...@inf.fu-berlin.de). Vielen Dank. Herzliche Grüße, Claudia Müller-Birn On Oct 1, 2015, at 2:00 AM, communitymetr...@wikimedia.org wrote: > > Hi Community Metrics team, > > this is your automatic monthly Phabricator statistics mail. > > Number of accounts created in (2015-09): 363 > Number of active users (any activity) in (2015-09): 863 > Number of task authors in (2015-09): 477 > Number of users who have closed tasks in (2015-09): 268 > > Number of projects which had at least one task moved from one column > to another on their workboard in (2015-09): 209 > > Number of tasks created in (2015-09): 3351 > Number of tasks closed in (2015-09): 2981 > > Number of open and stalled tasks in total: 25811 > > Median age in days of open tasks by priority: > Unbreak now: 11 > Needs Triage: 125 > High: 164 > Normal: 301 > Low: 660 > Lowest: 528 > (How long tasks have been open, not how long they have had that priority) > > TODO: Numbers which refer to closed tasks might not be correct, as described > in T1003. > > Yours sincerely, > Fab Rick Aytor > > (via community_metrics.sh on iridium at Thu Oct 1 00:00:08 UTC 2015) > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] How to get permission to view deleted revision information via API?
On May 8, 2013, at 3:46 PM, Chad innocentkil...@gmail.com wrote: For a personal wiki, this means you need the 'deletedhistory' and 'deletedtext' permissions (which is by default assigned to the admin group). On WMF wikis, this requires being an administrator (although I think there's some exception for researchers handed out via Meta). -Chad Hi Chad, Thank you very much for your information. Your reply came so fast that I somehow missed it. Sorry. Since this question occurred within a research project I will try to apply for researcher access. Claudia ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] How to get permission to view deleted revision information via API?
Hi all,
I don't know whether this is the correct mailing list to ask such question but
it is the one I am reading regularly…
Does anyone know about the adequate procedure to get permission to request
deleted revision information from the MediaWiki API?
I just stumbled over this problem...
{
servedby: mw1140,
error: {
code: drpermissiondenied,
info: You don't have permission to view deleted revision information
}
}
Many thanks.
Best, Claudia
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
Dear Roan, Thank you very much for your detailed explanations. I appreciate it very much. Even though, I do not fully agree with all your design decisions (regarding two different feedback mechanisms), they are understandable from your position (as far as I can anticipate it). Last comment on this, wouldn't be great to integrate both mechanisms in a way. I mean that the user can simply decide whether and when she wants to send some additional information (about the browser used etc.) by just selecting a checkbox (that explains the difference). So in every situation (before and after editing) the user can provide some feedback. The user can easily and understandable (at least I believe) decide about the extent of the feedback. Maybe is this (=my) feedback useful for the beta-testing-version :) Claudia On Apr 29, 2013, at 9:52 AM, Roan Kattouw roan.katt...@gmail.com wrote: On Fri, Apr 26, 2013 at 11:37 AM, Claudia Müller-Birn c...@inf.fu-berlin.de wrote: Hi James, Thanks for clarifying. I am just wondering why the two feedback mechanisms send to different targets which I personally find a bit confusing. What has been the decision behind it? They are different feedback mechanisms with different privacy expectations. The Leave feedback flow collects general, free-form feedback about the editor and posts it publicly. Only the text the user types into the form is collected and published. The Something is wrong flow is intended to collect data about cases where users see a diff they don't expect. It collects a lot of information to help us figure out what happened and why; this not only helps us find bugs, but it also collects the information we need to track it down and fix it. Because the information collected includes the text the user was attempting to save but apparently chose not to save, we treat it as private information. So one flow collects general feedback and the text field is all we collect, whereas the other collects data about a specific failure and the text field just serves as a footnote on a lot of technical data we collect along with it and is narrowly focused on the specific problem at hand: what did the user do to trigger the bug. In the general feedback flow, we communicate to the user that what they submit will be public, and it's very easy to explain what will be public (the text they put into the field). In the bad diff report flow, the data we collect (editor contents with an unsubmitted edit, among other things) is a bit more privacy-sensitive and it's hard to explain to the user what we'll be collecting. And why is the Something is wrong or Etwas ist schief gelaufen a privately sent feedback? Wouldn't be great to have here an open process and not sending the feedback to a black hole? This flow is mostly for reporting bugs, and the form asks them to provide details about the specific bug they encountered rather than general feedback. These comments wouldn't be particularly useful without the associated debugging data. The debugging data isn't particularly interesting to the general public, only to developers (that's not an argument for why it shouldn't be public, just one for why it doesn't hurt too much that it's not public). We feel like it would be against the spirit if not the letter of the privacy policy to publish this data without telling the user what we're publishing (especially since unsaved editor contents are privacy-sensitive: there is no expectation they'll be published because they're unsaved). But it's also difficult to explain to the user what exactly it is that we would be publishing. Contrary to the confusion and other reports on this thread, I can assure you that the data submitted through the Report problem interface isn't sent to a black hole. It's being collected by the Parsoid team, and they have in the recent past analyzed it and discovered bugs in both Parsoid and VE. Roan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
On Apr 27, 2013, at 12:05 AM, Lukas Benedix bene...@zedat.fu-berlin.de wrote: I'm not a non-tech-user, but I don't like using bugzilla. here is the new bug: https://bugzilla.wikimedia.org/47755 btw: While testing the black-hole feedback-mechanism I found another issue with VisualEditor. There are lines marked as changed in the diff that I never touched: http://lbenedix.monoceres.uberspace.de/screenshots/tlv5b64zcj_(2013-04-26_23.41.46).png http://lbenedix.monoceres.uberspace.de/screenshots/tlv5b64zcj_%282013-04-26_23.41.46%29.png Is this a (known) bug? It is :) Just read the pop up that appears when editing the page. clmb LB Am Fr 26.04.2013 20:49, schrieb Claudia Müller-Birn: On Apr 26, 2013, at 4:42 PM, K. Peachey p858sn...@gmail.com wrote: On Fri, Apr 26, 2013 at 11:23 PM, Lukas Benedix bene...@zedat.fu-berlin.de wrote: ... You can share your feedback on https://www.mediawiki.org/wiki/Project:VisualEditor/Feedback but 'visual editor' - 'review and save' - 'something is wrong' - 'report problem' is not working for me. You can report it straight into Bugzilla, As mentioned at the top of that page. Here is the direct link https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditorcomponent=General Well, that is correct. But my major concern are the non-tech-users and getting their opinion on the visual editor. As a non-experienced user I might click the link… and then I most likely have to create an account. Even though I take the time doing so, I have to understand the various drop-down menus in Bugzilla - challenging. I guess, I would be stressed out and give up before sending the feedback, which is a pity. Don't get me wrong, I think the visual editor is great. I am just thinking aloud and wondering about this and that... Anyway, Bugzilla works great for me :) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
Hi James, Thanks for clarifying. I am just wondering why the two feedback mechanisms send to different targets which I personally find a bit confusing. What has been the decision behind it? And why is the Something is wrong or Etwas ist schief gelaufen a privately sent feedback? Wouldn't be great to have here an open process and not sending the feedback to a black hole? An additionally question, what would be if the German community decides/wishes/asks for having a slightly different visual editor as for example the English Wikipedia community. Would that be possible at all? I could not find any possibilities to adapt the editor to the local needs on the extension page… just out of curiosity… Claudia On Apr 26, 2013, at 6:51 PM, James Forrester jforres...@wikimedia.org wrote: The feedback tool (Leave feedback or Rückmeldungen hinterlassen) posts your feedback to a page on-wiki (for dewiki, this was https://de.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback but has now been moved to https://de.wikipedia.org/wiki/Wikipedia:VisualEditor/R%C3%BCckmeldungen this morning). The Parsoid bug tool (Something is wrong or Etwas ist schief gelaufen) posts privately to a server so we can work out what went wrong. J. On 25 April 2013 10:27, Claudia Müller-Birn c...@inf.fu-berlin.de wrote: Hi James, Great news! Is the already given feedback publicly available? If yes, where. Thank you. Claudia On Apr 25, 2013, at 7:09 PM, James Forrester jforres...@wikimedia.org wrote: On 18 April 2013 17:32, James Forrester jforres...@wikimedia.org wrote: TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an opt-in alpha. Your assitance is requested to inform your wikis about this and help get the software translated. This is now done (for de, nl, fr, it, ru, es, sv, pl, ja, ar, he, hi, ko, and zh). Grateful for feedback, bug reports and suggestions of how we can improve the VisualEditor for you. Yours, -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
On Apr 26, 2013, at 4:42 PM, K. Peachey p858sn...@gmail.com wrote: On Fri, Apr 26, 2013 at 11:23 PM, Lukas Benedix bene...@zedat.fu-berlin.de wrote: ... You can share your feedback on https://www.mediawiki.org/wiki/Project:VisualEditor/Feedback but 'visual editor' - 'review and save' - 'something is wrong' - 'report problem' is not working for me. You can report it straight into Bugzilla, As mentioned at the top of that page. Here is the direct link https://bugzilla.wikimedia.org/enter_bug.cgi?product=VisualEditorcomponent=General Well, that is correct. But my major concern are the non-tech-users and getting their opinion on the visual editor. As a non-experienced user I might click the link… and then I most likely have to create an account. Even though I take the time doing so, I have to understand the various drop-down menus in Bugzilla - challenging. I guess, I would be stressed out and give up before sending the feedback, which is a pity. Don't get me wrong, I think the visual editor is great. I am just thinking aloud and wondering about this and that... Anyway, Bugzilla works great for me :) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Deploying alpha of VisualEditor to non-English Wikipedias
Hi James, Great news! Is the already given feedback publicly available? If yes, where. Thank you. Claudia On Apr 25, 2013, at 7:09 PM, James Forrester jforres...@wikimedia.org wrote: On 18 April 2013 17:32, James Forrester jforres...@wikimedia.org wrote: TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an opt-in alpha. Your assitance is requested to inform your wikis about this and help get the software translated. This is now done (for de, nl, fr, it, ru, es, sv, pl, ja, ar, he, hi, ko, and zh). Grateful for feedback, bug reports and suggestions of how we can improve the VisualEditor for you. Yours, -- James D. Forrester Product Manager, VisualEditor Wikimedia Foundation, Inc. jforres...@wikimedia.org | @jdforrester ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Proposal: Wikitech contributors
Hi, I'm not at all concerned about the rate at which you iterate -- it isn't about how fast you put out the shiny and new, but whether the assumptions that motivate this big undertaking are testable and falsifiable. Before we can say anything with confidence about what newcomers truly need, we need to do some usability testing and research. Because newcomers are generally voiceless, there is an unconscious tendency to project onto them a set of subjective preferences and intuitions, and the only way around that is data. I don't know if this is useful in this context but because of the term usability testing I thought this extension might be interesting for you: http://www.mediawiki.org/wiki/Extension:UIFeedback This project is still under development and we haven't gotten through code and design review yet… --Claudia -- Ori Livneh ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Complete (basic) analysis of MediaWiki
Hi Andre, On Dec 3, 2012, at 7:51 PM, Andre Klapper aklap...@wikimedia.org wrote: On Mon, 2012-12-03 at 19:40 +0100, Federico Leva (Nemo) wrote: Compare e.g. https://www.ohloh.net/p/mediawiki/contributors?query=sort=commits Also, https://bugzilla.wikimedia.org/weekly-bug-summary.cgi?tops=10days=10 proves they're not talking of the whole bugzilla but then they don't say which components. Would be helpful to mention the exact dataset you refer to. Also I'd rather challenge weekly-bug-summary.cgi's results: MediaWiki extensions has 2031 open bugs, and only 1883 have been filed in the last 10 days? = 148 bug reports got opened more than 274 years ago? But maybe I fail to read weekly-bug-summary.cgi correctly. Well, you don't. I think the UI is just misleading because the 10 days are just automatically positioned in the table header. The script does not account for the real age of the bug. The oldest bug with the number 1 has been created by Brion on Aug 10, 2004. Between this day and today are 3039 days (including today). Therefore, by replacing the number of days in the request, the same result occurs. At least in my data, the first bug has been closed on May 22, 2005 which are then 2754 days... But now it becomes complicated because there are too many changes that do not show up in my data (that are based on the bugzilla API). But you get my point :) However, I very much like the Bitergia stats - very good first step. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ Claudia ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
