#title #ubuntu-touch-meeting: Ubuntu Touch RSS App Meeting Meeting started by popey at 20:01:21 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-03-07-20.01.log.html . == Meeting summary == *introductions *Update blueprints - assign work items ''LINK:'' http://pad.ubuntu.com/JaommSul0o <--- please click (popey, 20:08:45) *milestones *populate ppa ''LINK:'' https://docs.google.com/a/canonical.com/document/d/1n10BX56XzRGeIDW0ityt3I6IKXOTYT2Zx_oB_NffQnw/edit?usp=sharing is the doc joey_chan was talking about... (popey, 20:35:00) Meeting ended at 20:35:38 UTC. == Votes == == Action items == * (none) == People present (lines said) == * popey (69) * mhall119 (38) * poisonedslo (29) * larsgk (23) * fcrochik (19) * dragly (14) * joey_chan (9) * meetingology (3) * srxavi (1) == Full Log == 20:01:21 #startmeeting Ubuntu Touch RSS App Meeting 20:01:21 Meeting started Thu Mar 7 20:01:21 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 20:01:21 20:01:21 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 20:01:26 #topic introductions 20:01:47 I'm Alan Pope, I'm an Engineering Manager at Canonical, and have been asked to act as a Developer Liaison for all the touch apps.. 20:02:14 mhall119 from Canonical is also around somehwere.. 20:02:23 want to introduce yourself? 20:02:27 (everyone) 20:02:48 * larsgk I'm Lars Knudsen, worked in Nokia on the browser for N9 (WebKit2, Qt, QML) and now working as a contractor on a Qt/QML project for a medical company. 20:02:51 hi everybody 20:03:16 like popey said, I'm from Canonical, specifically I'm on the Community Team, which means it's my job to work with you and help you 20:03:34 hi 20:03:55 My name is Felipe Crochik and I have developed Qt applications for maemo,meego,symbian,bb10, ... pretty much any device I can get my hands on :) 20:04:09 heh 20:04:52 I'm Svenn-Arne Dragly. Studying for my master's degree in the Computational Physics gruop at the University of Oslo, and have made a few apps with Qt and QML for Meego/Maemo and Android. 20:06:05 I'm super excited about these apps you guys are making. Looking forward to playing with them on real devices :D 20:06:10 hey 20:06:14 #topic Update blueprints - assign work items 20:06:37 So the first thing I wanted to talk about was the work items on the blueprint:- https://blueprints.launchpad.net/ubuntu-rssreader-app/+spec/initial-rssreader-development 20:07:01 lots of work to do, clearly, and it's important we track what's happening.. 20:07:33 lots of "TODO" items, and some have been allocated to people, which is great.. I know who to come and talk to for things! 20:08:39 so I just pasted the items into an etherpad so we can start attacking the list.. 20:08:45 http://pad.ubuntu.com/JaommSul0o <--- please click 20:09:17 "Either you have not been granted access to this resource or your entitlement has timed out. Please try again." 20:09:34 I'm getting the same message. 20:09:36 same here 20:09:42 if you get told you don't have access, then just join this team:- https://launchpad.net/~ubuntu-etherpad 20:10:13 we have to restrict access or spammers / bots make a mess of the etherpads 20:10:30 popey: does it take some time for it to register? 20:10:35 nope 20:10:44 nope, you should be approved now 20:10:44 you join, I approve, you refresh the etherpad 20:10:54 popey: works thanks 20:11:11 excellent, sorry about that hurdle 20:11:31 ok, so I split the list into "new" and "old" with the new list having assignments 20:11:50 basically we need to find volunteers for the tasks in the bottom list and move them to the top 20:12:18 So it's this point that we all look at eachother and wait for someone to edit the page... 20:12:35 or we decide that the work items aren't needed 20:12:51 i can take the tagging stuff 20:12:53 I think some of the functionalty should be considered for a later milestone 20:13:04 like what? 20:13:06 liek sharing feeds and tag lists 20:13:09 some of it is more high level - like test plan, tests, requirements, ... and some is pure development. Is the plan to split non-dev tasks between us evenly somehow? 20:13:30 yeah, first initial cut I'd imaging you would be able to add and view feeds. 20:13:35 What is the purpose for tagging? To have the user set tags to RSS items for organizing it on their device? 20:14:01 I have never tagged in an RSS reader myself 20:14:03 I understand it as tagging articles 20:14:16 I can see tagging feeds, like having a "Tech" list and a "Food" list 20:14:20 but not articles 20:14:31 ah that makes more sense 20:14:56 tagging articles is useful if you want to find them later 20:15:08 what about scanning competition for good and bad. E.g. I know that most of my friends using rss feeds do so through google reader 20:15:08 I don't but tagging articles may also make some sense... "to read later" , ... 20:15:29 fcrochik: also true 20:15:32 Perhaps "read later" is sufficient for tagging articles? 20:15:44 you might want more than one 20:15:49 that would be a nice feature 20:15:50 Or "starring" in other terms. 20:15:58 I would agree as long as we can save bookmarks.... 20:16:24 how about we just keep anythign with an article tag 20:16:45 so if I mark something as "read later", then it's effectively bookmarked under the "read later" bookmark group 20:17:04 agreed, anything more than that seems like a 2.0 feature? 20:17:15 yeah, I'd say sharing is a 2.0 feature 20:17:17 not sure about this 20:17:25 it makes sense to developer 20:17:32 I am curious about how we are going to interface with other applications, like web browser 20:17:33 mhall119: I agree, but I think functionality for other tags could be "hidden" in the sense that it's likely most useful for advanced users? 20:18:05 dragly: maybe, but it seems a lot of work to make it possible, only to hide it 20:18:27 I think we should separate read later and tags 20:18:43 because articles tagged as read later 20:18:46 mhall119: You're right. I didn't really mean to hide it completely, but perhaps have a star button rather than a tag button on the main toolbar (if we have a main toolbar). 20:18:51 should disappear from read later list 20:18:51 why would "read later" be separate from tags? 20:18:56 when you actually read them 20:19:50 One idea: We implement the "read later" functionality, but in such a way that it is easily extended to other tags? At least for v1.0. 20:20:03 agreed 20:20:05 I'd be happy with that 20:20:07 dragly: agreed 20:20:41 ok 20:20:42 we can even start with just using the "Stat" idea... so each user can use however he wants 20:20:46 I'd like to suggest an "Import from OPML" work item 20:20:51 *star I meant 20:20:57 for people coming from other RSS readers 20:21:22 I'd be interested to know how you get the OPML file into the phone, but that's a detail for another day 20:22:02 mhall119: makes sense for people not to be forced to reorganize subscriptions (agreed) 20:22:03 popey: point to a URL maybe? 20:22:04 Ubuntu One? 20:22:06 another one could be getting your feeds from google reader but that is a 2.0 or a custom app :) 20:22:11 both good ideas 20:22:15 mhall119: I've never heard of OPML, but if it means that we can import Google Reader and other feeds in a standardized way (have I gotten it right), then I think it is an awesome idea. 20:22:17 i agree with having an import from OPML feature 20:22:30 and other feed readers* was what I meant to say 20:22:31 yes it is dragly 20:22:34 dragly: OPML is basically an XML file of RSS urls 20:22:36 most of them support it 20:22:37 q: would google reader e covered by this import? 20:22:45 e=be 20:22:46 reader can export oplm 20:22:48 yes 20:22:49 opml 20:22:50 good 20:22:56 then +1 20:22:59 +1 20:23:09 who wants that item? ☺ 20:23:13 larsgk I would omit any vendor specific stuff ATM 20:23:22 I can take it 20:23:27 thanks 20:23:49 poisonedslo: ok ;) 20:23:51 popey: Should we tag work items with a milestone? v1.0, v1.1, v2.0 etc? 20:24:15 dragly: excellent question 20:24:21 no, I think we should just have 1.0 work items in this blueprints 20:24:26 since it is initial development 20:24:30 right now I think we just need names on work items 20:24:31 hi.. 20:24:39 hi joey_chan 20:24:39 and make new blueprints for future development efforts 20:24:42 joey_chan: hi....welcome! 20:24:46 hi joey_chan! 20:24:48 it's 4am in china... 20:24:56 golly 20:25:03 joey_chan: coffee? 20:25:07 we should still have stuff for later versions written somewhere 20:25:11 joey_chan: we all admire your dedication 20:25:14 yes 20:25:24 ok, we only have 5 mins of the RSS meeting left 20:25:43 joey_chan: hi 20:25:44 so if people could take a moment to grab some tasks on the pad, by tagging with your nickname, that would be super awesome 20:25:50 just wake by my phone .. 20:25:52 am I alone worried about interfacing with the web browser? 20:25:56 popey: Functionality for tagging should be moved up 20:25:56 on the subject of milestones.. 20:26:04 even if it's rudamentary for 1.0 20:26:18 and Functionality for managing feeds as well 20:26:25 I'll take the config than 20:26:25 so .. have u guys seen my doc? 20:26:32 popey: what about the high level tasks (test plan, requirements, ?) 20:26:47 I'm not really familiar with TDD 20:26:55 keep in mind that just because your name is on a work item, doens't mean you're going to have to implement it, it just means that if you're not going to implement it it's your job to find someone to pass it off to 20:27:06 ok, I'll take those larsgk 20:27:20 Hello everyone 20:27:25 we need the browser link - or people will have trouble getting feeds easily 20:27:29 so, we do tags in 1.0 or not? 20:27:29 poisonedslo: don't worry, we're going to get support from our QA guy for those 20:27:30 I can take that 20:27:41 it's snowshoe, right? 20:27:51 poisonedslo: at least enough to give star/read later functionality 20:27:59 okay, give it to me 20:28:01 larsgk: not necessarily 20:28:27 we're running out of time... 20:28:37 we can continue discussion in #ubuntu-touch when the meeting is over 20:28:42 ok 20:28:42 I just had a couple more things to mention.. 20:28:44 ok 20:28:50 .. 20:28:52 Should we have a design mockup item? 20:29:04 popey: put me on the browser integration - stretch goal for 1.0 then ;) 20:29:09 heh 20:29:19 larsgk: shouldn't that just be calling xdg-open or something? 20:29:24 why don't we move our chat to pad? 20:29:30 we can chat in peace there 20:29:39 poisonedslo: logging? 20:29:47 ok, agreed 20:29:49 poisonedslo: popey and I have another meeting after this one 20:29:56 and another, and another 20:30:03 yeah, fun times 20:30:03 ok, so final words... 20:30:11 any one seen my shared doc ? 20:30:15 #topic milestones 20:30:16 open the link on a browser should be the easiest right? I am worried about adding the rss reader from the browser 20:30:21 joey_chan: no, link it to the etherpad 20:30:26 joey_chan: yes.. not in detail though.. 20:30:36 fcrochik: I don't think that's a high priority atm 20:30:39 we have a target date of May 16th for "alpha quality" release 20:30:50 mhall119: how to you add a new rss then? 20:30:52 so that's 10 weeks away.. plenty of time 20:31:06 fcrochik: copy/paste? 20:31:10 wow, 30 mins wasn't enough! 20:31:12 fcorchik: copy/paste url? 20:31:13 sorry! 20:31:17 no problem 20:31:25 #topic populate ppa 20:31:40 mhall119: doesn't sound good enough to me.... 20:31:41 the other brief thing I wanted to mention is the ppa... https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily 20:31:45 popey: we had some important discussions on the possible need for C++ code in the app. Allowed or not (for portability reasons perhaps)? 20:32:07 we have builds of all core apps in that ppa.. 20:32:14 it builds daily for x86, amd64 and armhf 20:32:17 mhall119: user friendly enough I should have said 20:32:33 ok 20:32:40 falling sleep again ... goodnight 20:32:44 fcrochik: good enough for an alpha though 20:32:49 sorry joey_chan ☺ 20:33:04 mhall119: agreed 20:33:04 mhall119: agreed 20:33:26 popey: are we good on the new work items then? 20:33:37 it is just something else that most likely will require C++ 20:33:40 i'm fine , pls tell me the sumary of this conversation via email .. 20:33:41 looks good to me 20:33:47 joey_chan: will do on the mailing list 20:33:55 thanks 20:34:00 fcorchick: collating the list? 20:35:00 https://docs.google.com/a/canonical.com/document/d/1n10BX56XzRGeIDW0ityt3I6IKXOTYT2Zx_oB_NffQnw/edit?usp=sharing is the doc joey_chan was talking about... 20:35:17 ok, lets move over to #ubuntu-touch for further discussion if required... 20:35:33 popey: ok 20:35:38 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)