Okay, after much discussion about countervandalism support for WIkiGrok with Chris Steipp, Wikidata team and analytics, we decided to revamp the following stuff:
* All wikigrokresponse API calls go to wikidata.org and get logged there * The API will require a new parameter to disambiguate between wikis: wiki id * The wiki id has already been added to EL[1] * This should be accomplished simultaneously in the API[2] and UI[3]
---- [1] https://meta.wikimedia.org/w/index.php?diff=11225245 [2] https://trello.com/c/InOkrliI/ [3] https://trello.com/c/nXel0ldz/
Thanks for the write-up, Max :)
I know you wanted to fast-track some of these tasks so you could get unblocked. Which of these are most important to do now (this sprint) and which can we save for next sprint (kicking off next Tuesday)? I don't wanna cause chaos by introducing new unestimated tasks into a current iteration, but if there's stuff that needs to get done asap, I'm okay with bending the rules – as long as our glorious scrummaster is okay with it, too ;)
On Tue, Feb 10, 2015 at 1:43 PM, Max Semenik maxsem.wiki@gmail.com wrote:
Okay, after much discussion about countervandalism support for WIkiGrok with Chris Steipp, Wikidata team and analytics, we decided to revamp the following stuff:
- All wikigrokresponse API calls go to wikidata.org and get logged there
- The API will require a new parameter to disambiguate between wikis: wiki
id
- The wiki id has already been added to EL[1]
- This should be accomplished simultaneously in the API[2] and UI[3]
[1] https://meta.wikimedia.org/w/index.php?diff=11225245 [2] https://trello.com/c/InOkrliI/ [3] https://trello.com/c/nXel0ldz/
-- Best regards, Max Semenik ([[User:MaxSem]])
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
On Tue, Feb 10, 2015 at 2:35 PM, Maryana Pinchuk mpinchuk@wikimedia.org wrote:
I know you wanted to fast-track some of these tasks so you could get unblocked. Which of these are most important to do now (this sprint) and which can we save for next sprint (kicking off next Tuesday)? I don't wanna cause chaos by introducing new unestimated tasks into a current iteration, but if there's stuff that needs to get done asap, I'm okay with bending the rules – as long as our glorious scrummaster is okay with it, too ;)
I've been wrestling with submitting responses for so long, constantly hampered by Wikibase breakages and changing requirements. Now this week we learn that I need to redo half of what was done so far. If the cross-wiki part was done (and API and frontend changes need to be done in sync and merged at the same time), I would be able to quickly rebase on top of it instead of adding it to the already unsurmountable main commit.
Hey folks,
I'm disappointed – but not surprised, given what we've already experienced – to hear this.
Given this new information and that we've got our story review/estimation meeting coming up I feel like I should ask the following questions:
- As a team, how and do we evaluate whether our plan for implementing the submit-to-Wikidata part of Wikigrok is still correct? - Are there alternative plans that require less (estimated) development effort?
Please don't read this as "abandon ship!". We should always be asking ourselves these questions. I just want to be sure that we have answers to them.
–Sam
On Tue, Feb 10, 2015 at 10:49 PM, Max Semenik maxsem.wiki@gmail.com wrote:
On Tue, Feb 10, 2015 at 2:35 PM, Maryana Pinchuk mpinchuk@wikimedia.org wrote:
I know you wanted to fast-track some of these tasks so you could get unblocked. Which of these are most important to do now (this sprint) and which can we save for next sprint (kicking off next Tuesday)? I don't wanna cause chaos by introducing new unestimated tasks into a current iteration, but if there's stuff that needs to get done asap, I'm okay with bending the rules – as long as our glorious scrummaster is okay with it, too ;)
I've been wrestling with submitting responses for so long, constantly hampered by Wikibase breakages and changing requirements. Now this week we learn that I need to redo half of what was done so far. If the cross-wiki part was done (and API and frontend changes need to be done in sync and merged at the same time), I would be able to quickly rebase on top of it instead of adding it to the already unsurmountable main commit.
-- Best regards, Max Semenik ([[User:MaxSem]])
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
On Wed, Feb 11, 2015 at 9:42 AM, Sam Smith samsmith@wikimedia.org wrote:
Hey folks,
I'm disappointed – but not surprised, given what we've already experienced – to hear this.
Given this new information and that we've got our story review/estimation meeting coming up I feel like I should ask the following questions:
- As a team, how and do we evaluate whether our plan for implementing
the submit-to-Wikidata part of Wikigrok is still correct?
- Are there alternative plans that require less (estimated)
development effort?
Heh, it's like you read my mind for what I wanted to talk about at story
review :)
Let's chat in person at 11 – I've got some creative pivoting ideas...
Please don't read this as "abandon ship!". We should always be asking ourselves these questions. I just want to be sure that we have answers to them.
–Sam
On Tue, Feb 10, 2015 at 10:49 PM, Max Semenik maxsem.wiki@gmail.com wrote:
On Tue, Feb 10, 2015 at 2:35 PM, Maryana Pinchuk mpinchuk@wikimedia.org wrote:
I know you wanted to fast-track some of these tasks so you could get unblocked. Which of these are most important to do now (this sprint) and which can we save for next sprint (kicking off next Tuesday)? I don't wanna cause chaos by introducing new unestimated tasks into a current iteration, but if there's stuff that needs to get done asap, I'm okay with bending the rules – as long as our glorious scrummaster is okay with it, too ;)
I've been wrestling with submitting responses for so long, constantly hampered by Wikibase breakages and changing requirements. Now this week we learn that I need to redo half of what was done so far. If the cross-wiki part was done (and API and frontend changes need to be done in sync and merged at the same time), I would be able to quickly rebase on top of it instead of adding it to the already unsurmountable main commit.
-- Best regards, Max Semenik ([[User:MaxSem]])
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l