UCOSP Spring 2012/Standups/14 Feb

yep! cool. I'm not. Think TonyC_ will get back to keyboard or not? I think he's almost always signed in which unfortunately means it is also likely he is not around :/ Actually, he's in a Freenode gateway, and they drop him if he's idling too long. Well, here's the news I was hoping to discuss with everyone: Tfinc and yuvipanda are thinking we should go to feature freeze mode, and start getting ready to publish. interesting Soon, not right away, but think aobut stopping adding new features. Well, that really means, Sumanah, that the *serious* work begins. QA? Once frozen, we focus on cleaning up the code, then QA. Things like: all the gps stuff has to be removed. And all the code tightened up. I like that idea Everything related to debugging has to be marked and ready for removal. That was one thing I was meaning to ask Me too. I was impressed that they thought we had enough ready to go. Did you notice amgine if the app using any debug logging? I haven't noticed any; but I'm using a debuggable dev version on the phone. Does that offer more capabilities? Well, other than I can't find *any* log, it works pretty well even when not attached to Eclipse. How well did the copy to clipboard work for you, dlemieux? Is that implemented yet? I thought Shea was still working on it He couldn't figure it out using the phonegap plugin. Last I heard, he and Patrick were talking about possibly doing it in Java. Just the android specific way? I think so, which isn't a good solution imo as it's platform specific, and likely going to change. true brittle. Well I am looking for items to look in to, so do you think I should give the phonegap plugin another try? Yes, there's a plugin for android and a different one for iOS. Heyla TonyC_ Hey tonyC_  hey, sorry i had it on a tab so will that still be platform dependent if there are two separate plugins? Hmmm Shouldn't be, dlemieux, but I don't know. TonyC_: how did the sound files work out?  they work! tonyC_: dlemieux, I haven't been able to follow everything here, but it would probably be a far better thing to do everything in phonegap even if that takes longer sumanah: when is the iphone app being published?  its all phonegap for the audio, so it should be fine for IOS too dlemieux: the iPhone Wiktionary app? I do not know. That, Patrick/Tomasz/Yuvi would know. I believe the wp version is published for iPhone. Thanks dlemieux, TonyC_: do we want to do official standups?  sure Okay, who first? I can go since it will be quick I had a bit of a busy week and missed the last meeting, but I saw in the logs Shea mentioned the Share feature was already implemented So that task was done for me, and then I switched my repo over and i'm not sure if we lost the pull request for my app icon update amgine, tonyC_ do you have the new icon? it is the W on a brown background No; that's why I thought Shea was still on the old version.  yeah its nice! Okay so I guess it is in there, I just couldn't find it in gitk We can ask Patrick later, after he gets done. Blockers: waiting for yuvi to edit the sprite sheet Next week: no features lined up, but I can look into the copy/paste phonegap plugin again if that's wise Oh. That's done. Not sure where. Or i could be put on the next priority item Lastly  im sure the icons are in there I'll mention now the two points patrick wanted me to bring up 1: Check that everyone is switched to new repo not yet, I will be when I put this back together again. TonyC_?  i switched and did a pull earlier  i just typed the 2 lines that patrick gave us  which im thankful he gave because i wouldnt have known you had to clear out the old upstream before changing Do we also need to change how we fork from patrick? or does changing the upstream cover that? It should indicate to your repo that you are forked from somewhere else now.\ I'm just looking at my github how it still says forked from pfhayes, and my pull requests are still directed at him I think hi sheaclare hi all!   hmm that doesnt show on github for me either Sorry I was late... sheaclare: Are you switched over to the new repo for your upstream?  i guess we should ask patrick if we need to re-fork for pull requests to work Dlemieux: we'll need to talk with patrick about how to clean that up, yes. amgine: nope, I'm getting on that right now Thanks, sheaclare. Okay and 2) he asked that we discuss how our code review process will work going forward and whether someone like yuvi will be reviewing all the code before merging, or if we will review and sign off on it ourselves Very good question: we are officially able to do it ourselves, but now both TonyC_ & Shea are here we will need to discuss the feature freeze after the standups are done.  featre freeze? That's all for me So, let's finish standups quickly then, and I'll explain TonyC_  kk You're up, btw.  Since last meeting i did a pull request for my audio feature, and hopefully you guys can test that out for yourselves  I found a few bugs in it, one is that im not freeing up resources after i load audio which i knew about and the function that does it is already there <tonyC_> and the 2nd is that sometimes the file you press to play isnt the one that gets played <tonyC_> they should both be pretty easy to fix so i should have them by friday hopefully Hmmm, do you know the mechanism for that one? <tonyC_> im pretty sure i know why, currently i expected to recieve the url from the file when i ask for it so i just push it on to the array Okay. Any blockers? <tonyC_> not really, could use an icon <tonyC_> unless you dont want it on the front buttons kk, I can get icons probably. Send me an e-mail of what you're looking for concept-wise, and I'll get on that. Sheaclare: you're up. <tonyC_> we will need to discuss eventually translations on all the new buttons we are adding ok Where's Patrick-from-Waterloo? (as opposed to globetrotting-Patrick) I think he has a time conflict every Tuesday at this time ohhhhh I just reached him though about the repo and he said we keep our fork from him, and ONLY need to do the upstream modification so I've been pretty swamped since we talked on Friday and haven't had a chance to do much more than get more familiar with jquery and how to use it to get what the HTML I want You and Patrick were talking about the possibilities for the clipboard copying; did you get any further on that Sheaclare? <tonyC_> i thought they said that was done? <tonyC_> its the "select text" button already in the wikipedia app Does that allow sending it to another app? <waves @ aude> hi aude: do you know if the select text button allows sending to another app? Working version available. amgine: no idea <tonyC_> its in the clipboard only amgine: I haven't gotten any further with that. I was going to look further into the method patrick proposed before I started trying things out Okay sheaclare. So, any blockers, sheaclare? i've cloned wikimedia mobile app but not wiktionary yet https://github.com/wikimedia/WiktionaryMobile <- aude amgine: no blockers other than my schedule last weekend haha :) I think I'm done my "go" Okay, well, then let's get to the discussion of feature freeze. :) The idea is to stop adding features, and start working on getting the code ready for publish. Yuvi and Tfinc think we're pretty much ready for that next step, once our current features are finished. I like that idea So, are there any other features on our list we think we absolutely must have before we go forward? Tony has the pronunciation feature almost done, the clipboarding sounds like it is about half-implemented? Just talked to brion, dlemieux, about the sprite sheet; he suggested we work with it as-is for now. I can explain that a bit if you'd like? Okay It's just a bunch of graphics smooshed into one; so you can find the space currently being used and just replace that part of it. Most of the 'sub-graphics' will be a single object, so easily removed. Okay so I will edit that myself then Just for information sake, the sprite sheet contains the image that goes in the top left corner It likely has the menu buttons as well. It does. Also also some spinner icons Thanks amgine Oh, that's a 'feature' I wanted to mention: the search bar spinner never stops. Is this only on your phone? It works fine in my emulator <tonyC_> try the new version, i think someone fixed it over at wikipedia Only on my phone, when I first load it. Okay, will try when I get this box back together and updated. Aude: that is actually one of the primary uses we talked about; wiktionary seems used by language learners more than any other group. wow! amgine: where is that research from? Wiktionarians. amgine: that's how i use it :) <- wiktionarian. amgine: you know what I mean. hi pfhayes! Patrick! hello and as a mobile app, (offline would be awesome) when traveling is Kiwix not really cutting it, aude/ ? Sumanah: about 75% of our reader interactions are with people learning a new language. It's *overwhelming*. amgine: ok, so, the people who use Wiktionary *and ask questions/need help* are often new learners..... I'm still interested to see research about user demographics. And reading patterns as well. http://arabcrunch.com/2009/09/yahoo-maktoob-launches-its-first-iphone-app-an-arabicenglish-free-dictionary.html is my favorite For people who are curious about other Wikimedia mobile stuff that is happening: https://test2.wikipedia.org/ we just deployed a new version of MediaWiki to a test site. You could test the MobileFrontend bit if you had a moment. (ip -> word != dominant language) sumanah: thanks Okay, Patrick: we did quick standups; did you want to do yours? <tonyC_> If we re-named the "Read in" button to be "translate" it wouldnt be far off :) (you can read the others in the log, which I will post as soon as we are done here.) i was able to start migrating to the new repo has everyone set their upstream to be the new official repo? amgine tonyC_ sheaclare dlemieux? <tonyC_> yeah, but we were concerned it wasnt showing up on github what wasn't showing up? all but me, 'cuz my box is torn apart as I am rebuilding OS. <tonyC_> it says my fork is still forked off of pfhayes oh… i see that makes sense i didn't think of that you might want to delete those forks and make new ones then <tonyC_> so if i did a pull request, will it end up going to you? yeah i think it would you should probably get rid of those forks and make new ones off the real repository once everyone's done that I can delete it i also submitted two minor changes they were submitted as pull requests to the new official repo how are we going to do review for these? keep reviewing them ourselves? get yuvi to review them? something else? I think we should make sure at least one WMF team member reviews. We need to do more txt reviews, too. <tonyC_> whats a txt review? Code review messages on git hub. Commenting, asking questions, and discussing commits, etc. Sometimes I might not understand something, and ask how/why it works this way. (for example) dlemieux: Heatherw is offering to help with the sprites. okay i agree that we should all read them, and comment where appropriate. are we going to wait for a WMF member sign off on commits before we merge them? Team decision: dlemieux, sheaclare, TonyC_ Thanks amgine yw i think that makes sense to me <tonyC_> sure If they can take on the work, then it would be good on board! I think that's a good idea but may slow things down a little Okay. I will make sure that gets communicated. thanks amgine yeah, once WMF is a bottleneck for development they need to know that <notices Amgine's stack is growing> Okay, Feature freeze, pfhayes: Yuvi and Tfinc think we're getting close to feature freeze, then we clean code and get ready for publication. okay, in that case we need to add those people to the repository as collaborators or watchers or something. so that they get notified when we make these pull requests Yes, they want this published, soon. amgine: makes sense to me do we have a target date for publication? No, not yet. I wanted to make sure we have no outstanding features we must have before we go further. none that i can think of On/before Friday we should find out what will be need to be worked on to get the code ready. Then we can set a date. ok <tonyC_> neat! Awesome. One thing: Yuvipanda is in charge of getting the WP 1.1 published. So, he may *start* us going, but we will have to push ourselves while he's distracted with that. sure But it sounds like everyone is interested in getting this out the door! Great to hear. :-) i noticed tonyc_ and sheaclare made their new forks on github - are they working? pfhayes I'm just about to run mine now. I'll let you know in a second cool <tonyC_> looks good though im up to wiktionaryMobile-2 you can delete the old ones and rename this one My new version is up and running awesome dlemieux? I think the official part of the meeting is over. I'd love to see you guys networking to support each other though. Yes? did you get to make a new fork? Not yet, I am currently working with heatherw in #wikimedia-mobile about the sprite sheets ok amgine: once dlemieux is set up i'm going to go ahead and delete the repo under my name. i know you're still forked off of it but having this repo blocks me from contributing to WikipediaMobile. you should still be able to migrate to the new repo once mine is gone dlemieux: let me know once you've got that done and i can make the migration no problem pfhayes. pfhayes, do you need to wait for me? I will be doing this tonight anyways I'll just delete and refor, k dlemieux: tonight is fine cool no rush I'll be back in a jiffy, all. Then I'll be working on the clipboard thing and perhaps asking questions here-ish okay is that everything then? <tonyC_> im pretty sure we can go ahead and merge those two pull requests
 * tonyC_ (461d4198@gateway/web/freenode/ip.70.29.65.152) has joined #Wiktionary-mobile
 * sheaclare (~sheaclare@host5-235.wifi.ubc.ca) has joined #Wiktionary-mobile
 * aude (~filbertkm@wikipedia/Aude) has joined #Wiktionary-mobile
 * aude can't wait to have wiktionary mobile
 * aude really wants wiktionary for translating.... someday
 * pfhayes (~pfhayes@CPE78cd8e7df0c0-CM78cd8e7df0bd.cpe.net.cable.rogers.com) has joined #Wiktionary-mobile
 * sheaclare has quit (Quit: sheaclare)