Sure thing, thanks for the nudge @01tonythomas :)
Mar 3 2016
Feb 29 2016
Thanks everyone, it's been a great ride! @Niharika I definitely plan to. :)
Feb 26 2016
No problems, done. :)
Hi @Niharika, should I put in the relevant links or is this solely for the mentors to do?
Feb 25 2016
Thanks @Niharika ! :) I've edited the wiki.
Feb 24 2016
Thanks @01tonythomas :)
Feb 23 2016
@Nicolas_Raoul Okay, done! :)
@Nicolas_Raoul Sorry, not too clear about this - do you think we should remove the entirety of the features list? I have pared it down quite substantially already.
@Nicolas_Raoul thanks, that clears things up a lot. :) Which 'user guide' stuff do you mean? I have been modifying the first one over the past few hours and I think I've taken out most of the irrelevant stuff, but I might have missed something?
@Nicolas_Raoul ah okay, thanks. Hrmm so I should update both https://www.mediawiki.org/wiki/Wikimedia_Apps/Commons and https://commons.wikimedia.org/wiki/Commons:Mobile_app ? Doesn't it seem a bit redundant to have so many pages about the same apps? Would be harder for future contributors to update also.
Modified https://www.mediawiki.org/wiki/Wikimedia_Apps/Commons . @Nicolas_Raoul do you know which the most current repo for the iOS app is so we can link to them also? The repo on that page hasn't been updated for 3 yrs.
Feb 22 2016
Thanks for the feedback @Nicolas_Raoul ! I changed the rationale for #1, but still not sure how to explain what we did for #3 without referring to prefix search. Will think on it...
Feb 21 2016
No worries @Riley_Huntley :)
Thanks for reporting this. I think https://github.com/nicolas-raoul/apps-android-commons/issues might be a better place for your bug report, as the Commons-App-Android-Upload board is for the Outreachy project which is due to finish in a couple of weeks, and templates are not within the scope of this project? I have copied your bug report over to https://github.com/nicolas-raoul/apps-android-commons/issues/72, and will untag the Commons-App-Android-Upload board if you are okay with that. :)
Feb 20 2016
@Nicolas_Raoul @Niedzielski Javadocs have been added in the latest pull request. Currently still working on GitHub documentation to explain category suggestions - https://github.com/nicolas-raoul/apps-android-commons/wiki/Category-suggestions-(readme) .
Feb 19 2016
Feb 18 2016
@Niharika - got it, thanks. :)
Feb 17 2016
Thanks @Niharika! I was looking through https://www.mediawiki.org/wiki/Outreachy/Past_projects , where most of the wrap-up reports seemed to be done as blog posts instead. So we will ideally have both a wrap-up report (Phab task) and a wrap-up blogpost? I am not opposed to that, but they seem to both be about the same thing. Is it okay to have duplicate content between the two?
Feb 16 2016
Feb 13 2016
I think we will be wanting documentation for both users and contributors? I figure user documentation is fairly straightforward, maybe I could see what I can add to the Google Play page. Contributor documentation will be a bit more tricky, as the preexisting codebase has very minimal documentation and I'm not familiar with many of the files that weren't part of my project. Maybe I could write a summary on the GitHub wiki for the files that I did create/modify? @Nicolas_Raoul and @Niedzielski , what do you guys think?
Feb 12 2016
Feb 9 2016
Feb 8 2016
Feb 7 2016
Thanks @Niedzielski ! Followed up on your follow-up. :)
Feb 5 2016
Preference checking implemented and merged into the current pull request.
Feb 4 2016
@Niedzielski @Nicolas_Raoul - Thanks for the feedback. I've made a second attempt at implementing the location check, using a MyLocationListener subclass and onLocationChanged callback. Code is on the same pull request, do let me know what you think. It seems to work fine for me when I test it.
Feb 3 2016
@Niedzielski @Nicolas_Raoul - Ah, okay, thanks. Are we wanting something like this, then? http://developer.android.com/intl/es/training/location/receive-location-updates.html
@Niedzielski (cc: @Nicolas_Raoul) I read the article that you linked me yesterday, and while it's definitely informative, I'm unsure about its suitability for our task. I don't think we need passive listeners or even listeners at all, since it seems to me that we only want to get the location once (upon image upload, if image has no coords), instead of listening for location updates like a Yelp or Foursquare app.
Feb 2 2016
@Niedzielski and I were discussing what we should do next, and we thought this task would be a good one for me to focus on this week. :) What do you think?