[2009-10-26 14:34:23] -->| tr (n=chatzill@c-24-16-47-224.hsd1.wa.comcast.net) has joined #d7uc [2009-10-26 14:34:35] hey TR, thanks for joining [2009-10-26 14:36:08] |<-- DamZ has left freenode () [2009-10-26 14:36:45] =-= rszrama has changed the topic to ``Drupal 7 Ubercore Initiative | http://d7uc.org | First sprint planning meeting today at 7 PM GMT. Discussion will be logged and posted on the site after the fact.'' [2009-10-26 14:37:43] Hi Mike. [2009-10-26 14:38:25] tr: so, stephthegeek is into amateur robotics for school now ;) [2009-10-26 14:39:02] -->| Lynn_ (n=lynn@c-69-142-194-32.hsd1.pa.comcast.net) has joined #d7uc [2009-10-26 14:39:08] -->| duellj (n=duellj@c-24-21-68-115.hsd1.or.comcast.net) has joined #d7uc [2009-10-26 14:39:41] <--| duellj has left #d7uc [2009-10-26 14:40:01] cool! Tell her she can come to me for help if she needs it. [2009-10-26 14:40:27] Did i miss the sprint planning? I'm down with swine flu [2009-10-26 14:40:29] sure thing :) [2009-10-26 14:40:43] I mean down like physically [2009-10-26 14:40:46] Lynn_: sorry to hear it... and nope, we won't be kicking off for another 20 min. [2009-10-26 14:40:53] Cool [2009-10-26 14:41:32] Lynn_: what will happen then is anyone's guess... I'm hoping amye has some management magic up her sleeve [2009-10-26 14:41:42] rszrama: Shortly, shortly. [2009-10-26 14:41:43] Lynn is supposed to be jody btw but my irc name is fubar [2009-10-26 14:41:53] d'oh [2009-10-26 14:42:08] amye: you just can't sit there and giggle at me the whole time ;) [2009-10-26 14:42:10] rszrama: There's some stuff we can decide here, but not all of it. [2009-10-26 14:42:16] +1 [2009-10-26 14:42:25] rszrama: Whatever, I answered questions when I needed to. ;) [2009-10-26 14:42:26] hehe [2009-10-26 14:43:06] rszrama: My goal for this is to have a list of goals for the first sprint. Not even like 'tickets' yet. [2009-10-26 14:43:57] |<-- Lynn_ has left freenode ("Rooms • iPhone IRC Client • http://rooms.derflash.de") [2009-10-26 14:46:44] rszrama: That may just be crazytalk, though. [2009-10-26 14:47:45] amye: hehe, we'll see - I think this sprint will be useful as a learning experience and for further communication; group decisions over IRC are probably too difficult to achieve in a short period of time, but we can summarize conversation and take votes, etc.; getting help establishing and maintaining good feedback channels would be great, too [2009-10-26 14:49:05] amye: so, +1 for a goal of goals, and for gauging commitment and making sure there aren't any serious objections to the planned focuses as visible on "the whiteboard" here: http://d7uc.org/node/58 [2009-10-26 14:49:24] I like that a lot. [2009-10-26 14:50:57] -->| japerry (n=japerry@drupal.org/user/45640/view) has joined #d7uc [2009-10-26 14:54:01] rszrama: Do we want to discuss a direct port to D7 today? (We don't have to.) [2009-10-26 14:54:47] amye: there's been good discussion at http://d7uc.org/node/42 - I think it's worth at least summarizing, and in a call w/ mikejoconnor I realized we didn't _have_ to have a decision since D7 is still a few months out [2009-10-26 14:56:17] I think we'll have enough to talk about with just the sprint planning [2009-10-26 14:56:45] -->| Jody (n=Jody@c-68-80-217-159.hsd1.pa.comcast.net) has joined #d7uc [2009-10-26 14:57:09] D7 API freeze has happened already though, so it would be good to get a decision on the port soon. [2009-10-26 14:57:16] hmm, I can't remember... did we establish a time limit for these meetings? [2009-10-26 14:57:35] rszrama: Anything more than an hour seems crazy. [2009-10-26 14:57:35] no, I don't think we did [2009-10-26 14:57:52] Usually a sprint planning is timeboxed at 4 hours, but in our case, I think that is waaaay too long [2009-10-26 14:57:55] I like crazy. Let's go crazy. [2009-10-26 14:57:59] DamZ is 'locked in the Metro for security-related reasons and I vote that we start without him. [2009-10-26 14:58:03] lol [2009-10-26 14:58:13] DamZ sucks at traveling [2009-10-26 14:58:17] ;) [2009-10-26 14:58:17] seriously? [2009-10-26 14:58:33] if this keeps up, he's never going to leave his house [2009-10-26 14:58:36] I think it's like his special superpower or something. [2009-10-26 14:58:44] Mine used to be 'always missing the bus'. [2009-10-26 14:58:59] heh [2009-10-26 14:59:10] I told him it's not that long of a walk from the office to his house [2009-10-26 15:00:24] Ahem. Ryan, you want to kick off? [2009-10-26 15:00:39] sure [2009-10-26 15:00:47] So, we're getting started now. :) [2009-10-26 15:01:00] A few introductory words -> [2009-10-26 15:01:12] 1) We decided on a schedule for sprint planning and review meetings at our sprint in San Francisco. [2009-10-26 15:01:31] 2) I vote Amye manages them, and she does her best to keep them under an hour. [2009-10-26 15:01:48] 3) Today we're looking at our goals for the first Ubercore sprint, roughly the month of November. [2009-10-26 15:01:50] * amye agrees, ok. [2009-10-26 15:01:53] :) [2009-10-26 15:02:23] 4) Her goal is goals, and I concur. The primary targets for development as sketched out in the sprint are available on http://d7uc.org/node/58 [2009-10-26 15:03:14] 5) Other than that, we'll be looking for feedback on our communication so far and also on how to open and establish good feedback channels for everyone following along. [2009-10-26 15:03:17] any other thoughts? [2009-10-26 15:04:03] ideally we need to also estimate the goals, so we can begin to establish our velocity [2009-10-26 15:04:38] i.e. make our best guesses at how long tasks will take so we can measure our expectations vs. reality at the sprint review meeting? [2009-10-26 15:04:44] yep [2009-10-26 15:05:08] do we need to get a second on Mike's ideas? [2009-10-26 15:05:26] * IslandUsurper seconds [2009-10-26 15:05:29] (he is fake Irish, after all) [2009-10-26 15:05:34] :) [2009-10-26 15:05:36] alrighty, it stands [2009-10-26 15:06:18] Is there no other writeup for that whiteboard? (I was in that meeting and I can still barely read it.) [2009-10-26 15:06:26] hehe [2009-10-26 15:06:34] not yet... unfortunately [2009-10-26 15:06:36] zoom a bit [2009-10-26 15:06:43] you can click to view the full image [2009-10-26 15:06:51] amye: I intended to start that, but the swine got the best of me [2009-10-26 15:06:58] That's better. Ohsad! [2009-10-26 15:07:07] so instead I just laid in bed [2009-10-26 15:07:30] basically, port what we can, grok the Fields API, and develop our base product class; on d7uc.org, hash out the order model and community mgmt. [2009-10-26 15:07:43] (like feedback channels, site maintenance teams, doc editors, etc.) [2009-10-26 15:07:58] however from what I remember, our goal was to port CA, and TAPiR, re-factoring them for the new coding standards, and updating them as needed [2009-10-26 15:08:05] -->| robeano (n=robeano@c-67-183-109-234.hsd1.wa.comcast.net) has joined #d7uc [2009-10-26 15:08:25] rszrama: It's always nice to try and tackle the biggest, scariest problems first. Which ones would you say would be the biggest problem and should be our first priority? [2009-10-26 15:08:32] ah, I just remembered that "No Views" means that Views wasn't available on D7 then [2009-10-26 15:08:33] mikejoconnor: CA for the 2.0 direct port? [2009-10-26 15:08:45] fieldable products and the add to cart form will probably be the biggest hurdle [2009-10-26 15:09:00] sorry, calling it the "Add to Cart Field" so it's not just a form... could be a cart link after all [2009-10-26 15:09:09] |<-- thill has left freenode () [2009-10-26 15:09:19] http://d7uc.org/node/57 has where we gave priorities to the various core systems / entities [2009-10-26 15:09:20] japerry: ya, porting the current ca from uc2 to ubercore [2009-10-26 15:09:33] why aren't we using rules? [2009-10-26 15:09:39] because that's not a direct port [2009-10-26 15:09:50] nono, to ubercore [2009-10-26 15:10:01] I understand 2.0 D7 using CA [2009-10-26 15:10:05] k [2009-10-26 15:10:06] I'm down to help with porting CA, but I'm not sure exactly how to port it in isolation of everything else, how will we be able to look at it and see if it's doing anything? [2009-10-26 15:10:38] Jody: my thoughts exactly... we kind of have to have a product w/ conditions or something... [2009-10-26 15:11:02] japerry: our basic feeling is that although rules is a good system, rules isn't running on d7, and it's far more complex than ca [2009-10-26 15:11:17] I'd say either 1) a pluggable inference engine or 2) CA with compat. for Rules and/or core Actions [2009-10-26 15:11:39] * gregharvey likes 1) [2009-10-26 15:12:05] Jody: fortunately, I don't think a direct port of CA should be that difficult - it's one of the brighter pieces of Ubercart atm [2009-10-26 15:12:47] rules will be released and running on D7 day one its released -- but we're talking about a 3-4 month window (at best) between d7 coming out and ubercore coming out [2009-10-26 15:12:57] amye: is it better to discuss these things here or isolate these as pressure points and off-put discussion to d7uc.org? [2009-10-26 15:13:19] I'm not even sure I know what CA is/does.. and how it impacts things. [2009-10-26 15:13:35] I agree that CA needs to be ported for the 2.0 release on d7 though. too many variables if we try to change that now :-P [2009-10-26 15:13:56] japerry: I think the general idea is that we can have a basic inference engine working(ca) in a week. That's not to say we will never switch to rules, it's just saying that we can have a large piece of functionality working very soon [2009-10-26 15:14:24] I agree that it needs to be part of the conversation, but I'm not convinced that we're going to get to consensus here. We'll go until :25 on this, so that we can isolate problems and move on. [2009-10-26 15:14:29] -->| DamZ (n=damz@drupal.org/user/22211/view) has joined #d7uc [2009-10-26 15:14:44] amye: it's the core inference engine... it automates things like order workflow and provides the UI for things like setting up taxes, shipping quotes, etc. [2009-10-26 15:14:50] welcome DamZ, we started without you [2009-10-26 15:14:53] amye: (CA stands for Conditional Actions) [2009-10-26 15:15:11] hey everyone [2009-10-26 15:15:13] mikejoconnor: thanks ;) [2009-10-26 15:15:18] for the record: I was NOT the security issue [2009-10-26 15:15:19] DamZ: we're reviewing http://d7uc.org/sites/default/files/pictures/PA160308.JPG [2009-10-26 15:15:48] well I think we should ask ourselves two questions. 1. can we currently begin integrating with rules, and 2, is there any harm in porting ca, and evaluating rules when it's ready to be evaluated. [2009-10-26 15:16:02] my hunch is 1) no, and 2) no harm [2009-10-26 15:16:17] fago is never there when we need him :( [2009-10-26 15:16:22] (I should have pinged him) [2009-10-26 15:16:45] DamZ: agreed :-/ [2009-10-26 15:17:01] so maybe the 3rd question is: will an inference engine be valuable to us in the next 3 months [2009-10-26 15:17:02] my understanding (through the grapevine): rules 1.x is pretty much stable, but the 2.x branch has been open for a few months now [2009-10-26 15:17:04] -->| stephthelaptop (n=stephani@doecev-wlan2-148-42.AirBears.Berkeley.EDU) has joined #d7uc [2009-10-26 15:17:13] and there are some very intense refactoring going on there [2009-10-26 15:17:29] I think the 3rd answer is "maybe by the 3rd month" [2009-10-26 15:17:37] so I'm a little bit worried about the timeframe of that [2009-10-26 15:18:13] I think it makes sense to heavily rely on the inference engine [2009-10-26 15:18:30] that's apparently the direction even unrelated modules like OG are going [2009-10-26 15:18:32] (could someone pastebin some backscroll if possible?) [2009-10-26 15:18:48] * IslandUsurper is on it [2009-10-26 15:18:59] thx IslandUsurper. [2009-10-26 15:19:24] so, if we added an inference engine class through which we pulled triggers and such, could we not support in Ubercore 1.0 a plugin to that for CA and then get a Rules plugin when that code solidifies? [2009-10-26 15:19:52] I suppose that doesn't take full consideration of the Drupal hook model for defining stuff, tho... [2009-10-26 15:20:06] or maybe that doesn't matter :? [2009-10-26 15:20:42] rszrama: I tend to think we could do something like that with the hook system, but I also think that it's a little out of scope right now. [2009-10-26 15:20:48] rszrama: I don't believe so [2009-10-26 15:21:03] rszrama: every possible conditions and actions would need to be reimplemented [2009-10-26 15:21:15] rszrama: and the glue code for them [2009-10-26 15:21:28] DamZ: unless we standardized on CA's syntax and the Rules plugin massaged its data into the inference engine class's [2009-10-26 15:21:43] [INFO] 1 matches for ``ste'': [stephthelaptop, ] [2009-10-26 15:21:59] but then if you do that, why not make that a target for Ubercore 2.0 and get 1.0 out faster? [2009-10-26 15:22:03] stephthelaptop, not the best site to choose, but here you go: http://drupalbin.com/12062 [2009-10-26 15:22:13] japerry: what would you suggest right now? do you think we should just shelf the ca upgrade until the next sprint? [2009-10-26 15:22:22] thanks :) [2009-10-26 15:22:45] mikejoconnor: well, I'm a big believer in 2.0 for D7... so in that regard, if CA is an easy win, we should get it ported quick [2009-10-26 15:22:58] CA is easy enough [2009-10-26 15:23:03] I can do that in my bath [2009-10-26 15:23:14] (oups, I think I volunteered) [2009-10-26 15:23:15] Please don't, but cool. [2009-10-26 15:23:26] at least don't let the laptop fall in with you [2009-10-26 15:23:28] erm... we can video conference that? [2009-10-26 15:23:38] rszrama: sure ;) [2009-10-26 15:23:56] but I'm more concerned about the next 3 months (before Jan D7 release) and less concerned about ubercore at the moment. I think the landscape of d7 code we can use to build ubercore will be much different in 3 months [2009-10-26 15:23:57] Jody also offered help above, and I'm certainly available [2009-10-26 15:24:16] japerry: jan D7 release? you are dreaming ;) [2009-10-26 15:24:25] end of Jan [2009-10-26 15:24:25] ;-) [2009-10-26 15:24:38] japerry: let's say March [2009-10-26 15:24:40] thats what David and Chx think [2009-10-26 15:24:48] Jody: I'd be happy to work with you on the ca upgrade. I've been coding with ca a lot lately [2009-10-26 15:24:55] That definitely gives us a start, it sounds like CA is a good thing to upgrade, but also keeping in mine that we'll need to reevaluate Rules. [2009-10-26 15:25:05] I have to agree with japerry - I think a straight 2.0 port is essential, and I don't think that a port and a new Ubercore are mutally exclusive, because they can be done by separate groups. [2009-10-26 15:25:10] I don't think we need to touch rules until it comes to ubercore [2009-10-26 15:25:22] straight port of Ubercart 2.0 is completely out of question, IMO [2009-10-26 15:25:30] why is that? [2009-10-26 15:25:31] tr: agreed. [2009-10-26 15:25:33] DamZ: why? [2009-10-26 15:25:34] DamZ: Explain? [2009-10-26 15:25:53] I don't believe you realize the amount of work it is [2009-10-26 15:26:05] so, we're switching topics now? if so, I'd like to point everyone to http://d7uc.org/node/42 for starters [2009-10-26 15:26:10] I've ported some modules to D7, so I'm aware of many of the issues ... [2009-10-26 15:26:19] I'd rather talk about how to implement the rest of the sprint [2009-10-26 15:26:20] there are definitely pros listed, and then mostly me chiming in with the cons :P [2009-10-26 15:26:27] webchick has been talking about her ideal as feb/march for D7 [2009-10-26 15:26:47] you first have to port the module(s), then you have to maintain two different, but slightly similar branches [2009-10-26 15:27:10] rszrama: We're working on switching topics, but with small backtracking. (Small.) [2009-10-26 15:27:10] DamZ: I don't see ubercore and ubercart being similar at all, or at least I hope not [2009-10-26 15:27:29] japerry: you have seen the amount of work that has gone in porting Views [2009-10-26 15:27:36] DamZ: yup, I was there ;-) [2009-10-26 15:27:37] DamZ: Yes, and that speaks to the process of how Ubercart moves forward from the project management point of view [2009-10-26 15:27:39] I'm with TR on the "we can do this in separate groups" portion, however I'd like to try to focus on the next 30 days of ubercore [2009-10-26 15:27:42] japerry: and the size of the patch, and the fact that we are still at the begining [2009-10-26 15:27:52] DamZ: yup, there is a lot of work [2009-10-26 15:28:05] or schedule a irc meeting specifically for the 2.0 upgrade discussion [2009-10-26 15:28:14] we have a 10k lines patch or something [2009-10-26 15:28:35] porting every ubercart queries to the new database layer will be an insane amount of work [2009-10-26 15:28:38] It's a lot of work, granted, which is why both a port an Ubercore CANNOT be done by the same people. But that isn't an argument for abandoning a port ... [2009-10-26 15:28:56] especially because (1) there are ZERO unit tests, (2) some of those queries are *insane* [2009-10-26 15:29:18] Tests written for a port should be mostly applicable for Ubercore [2009-10-26 15:29:26] process tests for instance [2009-10-26 15:29:30] tr: well, if someone wants to do the port and maintain it, that's very fine by me [2009-10-26 15:29:42] but it should not take the time of any member of the ubercore team [2009-10-26 15:29:51] tr: that's mostly a pipe dream [2009-10-26 15:29:58] which is problematic [2009-10-26 15:30:00] tr: could be great, but I really doubt it [2009-10-26 15:30:43] real quick... [2009-10-26 15:30:46] DamZ: I look at ubercart port to d6, and it took wayyy to long. I don't think a totally rewritten ubercore+contrib modules + ui will be working well by a d7 release, much less SF. [2009-10-26 15:30:47] ok, quick question to try and guide our focus. Is anyone here against the idea of someone working on a strait port of 2.0? [2009-10-26 15:31:06] can we establish the reasons _for_ a port? [2009-10-26 15:31:07] japerry: well, then work with us in making that happen ;) [2009-10-26 15:31:25] rszrama: I'd rather not try to establish a reason right now, because that is not planning the sprint [2009-10-26 15:31:31] ok [2009-10-26 15:31:31] I think there are many in the community, (and yes, I'll volunteer myself) who would volunteer to help with a port, but can't do that until the process is changed (put things in CVS, for instance ...) [2009-10-26 15:31:32] mikejoconnor: I don't think anyone's -against- it, it's just a concern of time. [2009-10-26 15:31:33] agreed [2009-10-26 15:31:34] which is the focus of this meeting [2009-10-26 15:31:46] japerry: piping ressources away from Ubercore just because you believe it will not happen in a timely manner will not make Ubercore happen faster [2009-10-26 15:31:50] perhaps amye can direct our conversation atm? [2009-10-26 15:32:12] discussion about pros / cons? postponed decision? [2009-10-26 15:32:14] Probably best to take this into forums, I think. [2009-10-26 15:32:23] * IslandUsurper seconds [2009-10-26 15:32:24] Unless someone has strong disagreements? [2009-10-26 15:32:27] DamZ: no I just look at all the other projects that decided a drupal revision was a good reason to upgrade their module, and we have d6 all over again [2009-10-26 15:32:44] hmm, well, it's there... is there something beyond a forum thread we can do? i.e. outline pros / cons and actually get people taking part in the discussion to commit to action? [2009-10-26 15:32:45] thats why D7CX was started -- to get people to PORT their modules, not rebuild them from scratch. [2009-10-26 15:33:04] japerry: so one dissenting project won't kill things, right? ;P [2009-10-26 15:33:05] japerry: when that happens you get delays but end up with way better modules [2009-10-26 15:33:08] japerry: not really [2009-10-26 15:33:36] I think we're hearing a lot of the cons, but maybe not as much of the pros.. [2009-10-26 15:33:46] Forum discussion would be fine - I think however that this is a key decision which locks down a lot of others for Ubercore. For example, Rules v. CA is a much different discussion if absolutely nothing in UC works on D7 [2009-10-26 15:33:56] japerry: I think you are wrong about the motivations behind D7CX [2009-10-26 15:34:16] i definitely think japerry has good points to consider but since this is the ubercore sprint we should move on for now [2009-10-26 15:34:31] yah we can take this offline [2009-10-26 15:34:36] japerry: it's because everything is rethinked at each major release that Drupal still goes forward [2009-10-26 15:34:40] and talk about this in the forum, focus back on the sprint [2009-10-26 15:34:47] japerry: stop that, and it's the end of Drupal [2009-10-26 15:35:03] heh [2009-10-26 15:35:04] so: CA will be ported. Next is Product Fields [2009-10-26 15:35:07] japerry: D7CX is just about starting the process *earlier* so that modules are ready in a timely maner [2009-10-26 15:35:12] -->| duellj (n=duellj@c-24-21-68-115.hsd1.or.comcast.net) has joined #d7uc [2009-10-26 15:35:15] I'm very concerned about a whole Drupal 6 situation happening again and UC being a year behind the times and always playing catch up, rather than driving development of the next Drupal version. [2009-10-26 15:35:21] Let's schedule a time to talk about 2.0 upgrade through the Forums on uc.org, mmkay? [2009-10-26 15:35:22] I second japerry on the "lets continue the sprint" [2009-10-26 15:35:42] uc.org or d7uc.org? [2009-10-26 15:35:44] japerry: nobody is saying that all D7CX modules should be straight ports [2009-10-26 15:35:55] d7uc.org would be my vote [2009-10-26 15:35:55] http://d7uc.org/node/42 [2009-10-26 15:35:56] I'm all kinds of happy to come in and help 'moderate' that this week. Oops! d7uc.org, my bad. [2009-10-26 15:35:57] tr, uc.org, I'd say [2009-10-26 15:36:04] oh [2009-10-26 15:36:07] lol [2009-10-26 15:36:12] yah I guess that'd make sense actually.. because 2.0 is ubercart [2009-10-26 15:36:16] and d7uc is for ubercore [2009-10-26 15:36:17] :-P [2009-10-26 15:36:20] yeah [2009-10-26 15:36:22] United front, we totally can haz it. :P [2009-10-26 15:36:30] the only issue is we have some discussion already on d7uc [2009-10-26 15:36:41] port it! [2009-10-26 15:36:44] that can be worked around [2009-10-26 15:36:45] hehe [2009-10-26 15:36:47] so if we start another thread, that will be lost, but I'm ok with either [2009-10-26 15:36:54] ok. so next item on our list, [2009-10-26 15:36:56] -->| davidstrauss (n=davidstr@wikimedia/davidstrauss) has joined #d7uc [2009-10-26 15:37:02] so I'm clear on the action here... [2009-10-26 15:37:09] DamZ: suggested porting tapir, and making a module out of it [2009-10-26 15:37:26] sorry rszrama continue, I didn't mean to cut you off [2009-10-26 15:37:28] 1) New thread on uc.org summarizing the discussion on http://d7uc.org/node/42 and focusing explicitly on UC 7.x-2.x [2009-10-26 15:37:42] 2) Close comments on the thread on d7uc.org? [2009-10-26 15:37:59] rszrama: with a link to the new thread [2009-10-26 15:38:05] mikejoconnor, yes [2009-10-26 15:38:11] 3) Emphasize the resources we expect it to take [2009-10-26 15:38:22] and let people ante up? [2009-10-26 15:38:41] well, I suppose we still have to reach a consensus [2009-10-26 15:38:48] is that enough to move on, amye? [2009-10-26 15:38:48] sounds good [2009-10-26 15:38:51] I like. [2009-10-26 15:39:09] ok, so DamZ, you recommend porting Tapir [2009-10-26 15:39:17] ok, so what about http://drupal.org/project/tapir? is this even necessary if we have a Views dependency? [2009-10-26 15:39:25] I think we said yes at the sprint [2009-10-26 15:39:33] tapir is basically what theme_table() should be in the D7 rendering layer [2009-10-26 15:39:40] rszrama: we did say yes, but it's good to have the discussion [2009-10-26 15:40:03] (I wished I had time to push http://drupal.org/node/80855 in D7) [2009-10-26 15:40:07] :) [2009-10-26 15:40:08] DamZ: since you've already worked on a patch to d7, and with tapir, would you be willing to work on the port? [2009-10-26 15:40:26] tapir does have limitations that people have been bumping against... do we address those or simply port? [2009-10-26 15:40:35] oh, and it doesn't have a UI right now :P [2009-10-26 15:40:37] rszrama: yes, it's still necessary if we have a Views dependency [2009-10-26 15:40:44] no UI, please. [2009-10-26 15:40:56] who said a module should have an UI [2009-10-26 15:40:59] this is pure API [2009-10-26 15:41:09] Is Ubercore going to have a Views dependency? [2009-10-26 15:41:11] DamZ: reading my mind exactly [2009-10-26 15:41:21] rszrama: and yes, I would be for a rewrite, not a straight port [2009-10-26 15:41:22] tr: we had discussed a views dependency [2009-10-26 15:41:29] ubercore does not need a views dependency because ubercore should be an API [2009-10-26 15:41:34] tr: for things like admin/store/orders [2009-10-26 15:41:37] rszrama: it should not be that hard, based on the D7 patch [2009-10-26 15:41:59] Views is definitely a Ubercore dependency [2009-10-26 15:42:07] * davidstrauss was called in to comment here. [2009-10-26 15:42:21] davidstrauss: welcome ;) [2009-10-26 15:42:25] davidstrauss: hola :) [2009-10-26 15:42:30] davidstrauss: thanks for joining [2009-10-26 15:42:35] davidstrauss: want some ramen? ;) [2009-10-26 15:42:36] davidstrauss: 4 Kitchens == definitely my favorite t-shirt [2009-10-26 15:42:50] If the choice is between porting all of Ubercart to D7, including redundant modules, then I prefer the Ubercore option. [2009-10-26 15:42:52] davidstrauss: he apparently has a lot of ramen. [2009-10-26 15:42:53] rszrama: :-) [2009-10-26 15:42:54] davidstrauss: what they said smiley face [2009-10-26 15:43:19] amye: yes, for some strange reason [2009-10-26 15:43:35] well, i meant "between porting all of ubercard and ubercore" [2009-10-26 15:43:37] well, I mean. he does have 4 kitchens [2009-10-26 15:43:40] ubercart* [2009-10-26 15:43:54] japerry: The important measure is coffee pot count. [2009-10-26 15:44:01] ahh, yeah, for anyone who doesn't know, 4 Kitchens has definitely had to work against Ubercart's limitations in the past ;) [2009-10-26 15:44:06] japerry: That determines your peak ramen throughput. [2009-10-26 15:44:12] LOL ;) [2009-10-26 15:44:17] davidstrauss: <3 <3 <3 [2009-10-26 15:44:35] in an ocean of private jokes [2009-10-26 15:44:36] i had a dream recently it was called fork itchings [2009-10-26 15:44:56] to back up a little bit, tr: we did discuss a Views dependency, and japerry: we're still looking for this to ship as a coherent project - administration Views are low hanging, pluggable, overridable fruit ripe for pickin' [2009-10-26 15:45:02] hehe [2009-10-26 15:45:13] rszrama: oh, yes I agree totally on that [2009-10-26 15:45:16] as a coherent project [2009-10-26 15:45:17] so Tapir? [2009-10-26 15:45:22] lol [2009-10-26 15:45:23] Jody: Time to step away from the Drupal. [2009-10-26 15:45:28] Tapir? what's that? [2009-10-26 15:45:36] :P [2009-10-26 15:45:43] lol [2009-10-26 15:45:44] but specifically, when we talk about tapir vs views, I think views and theme functions should do what we need [2009-10-26 15:46:08] and the core core part, should need no dependency on views.. just wanted to check that was agreed upon [2009-10-26 15:46:12] If there's a Views dependencey, then why Tapir? Those things that we currently use Tapir for, like order history table, cart table, products table, will be better done with Views, no? [2009-10-26 15:46:13] "A tapir (pronounced /ˈteɪpər/ "taper", or /təˈpɪər/ "ta-pier") is a large browsing mammal, roughly pig-like in shape, with a short, prehensile snout." [2009-10-26 15:46:19] like there is ubercore and uberui or soemthing like that :-P [2009-10-26 15:46:19] Stop that. [2009-10-26 15:46:19] ok, if DamZ is going to work with that, he shouldn't be working on CA more than he already has (http://drupal.org/node/548144) [2009-10-26 15:46:40] cart table, really not a view [2009-10-26 15:46:44] mike and i can do ca then [2009-10-26 15:46:47] invoice, really not a view [2009-10-26 15:46:50] tr: I think we isolated things like the add to cart form, the cart table, products form on the order display [2009-10-26 15:47:03] order review, really not a view [2009-10-26 15:47:04] etc. [2009-10-26 15:47:05] tr: and I meant cart view form, not add to cart [2009-10-26 15:47:32] but why not make those table displays that cant use views just be theme functions that can overridden [2009-10-26 15:47:37] it would be crazy to think that all Ubercart tabular data will be Views [2009-10-26 15:47:41] Jody: yup thats right [2009-10-26 15:47:53] Jody: that's what Tapir is [2009-10-26 15:48:01] Jody: a way to properly override themed tables [2009-10-26 15:48:07] ok [2009-10-26 15:48:12] Jody: and tabular forms [2009-10-26 15:48:13] I think the primary reason is developer experience... Tapir would let you simply disable a column in a table instead of overriding the whole theme func, tweaking $header, etc. [2009-10-26 15:48:17] specifically by only overriding the part you care about [2009-10-26 15:48:20] DamZ: Sure, they're not "traditional" views, but they could be done with Views. Right now they're raw queries, which makes theming and extension difficult [2009-10-26 15:48:21] like adding columns / removing columns [2009-10-26 15:48:24] reordering columns [2009-10-26 15:48:25] etc. [2009-10-26 15:48:32] tr: there are not raw queries [2009-10-26 15:48:33] -->| Bojhan (n=Bojhan@mb30f36d0.tmodns.net) has joined #d7uc [2009-10-26 15:48:35] not at all [2009-10-26 15:48:37] hay [2009-10-26 15:48:40] hola [2009-10-26 15:48:42] all this is processed data [2009-10-26 15:48:42] yo [2009-10-26 15:48:43] hey Bojhan thanks for joining [2009-10-26 15:48:43] hihi [2009-10-26 15:48:46] rendered in a table [2009-10-26 15:48:53] Hey, sorry - couldn't get airport wifi to work. [2009-10-26 15:48:54] Bojhan: hey you [2009-10-26 15:48:56] IslandUsurper: can we get another backlog posted? you can set it to render as Text to avoid the syntax highlighting [2009-10-26 15:48:59] is it just like a drupal_alter on an array of header and rows? [2009-10-26 15:48:59] Bojhan: still in SF? [2009-10-26 15:49:02] DamZ: at SFO now [2009-10-26 15:49:03] DamZ: not my experience ... [2009-10-26 15:49:05] rszrama: The rule of thumb for dependencies is: (1) Try to keep the dependency optional and degrade functionality if it's missing. (2) If you can't elegantly degrade functionality, don't replicate substantial functionality in your own code in order to avoid a dependency. Just require it. [2009-10-26 15:49:20] davidstrauss: yep, we are in (2) here [2009-10-26 15:49:31] rszrama, sure [2009-10-26 15:49:36] -->| CKIDOW (n=CKIDOW@g229053016.adsl.alicedsl.de) has joined #d7uc [2009-10-26 15:49:44] Jody: it allows you to have a tabular #type element [2009-10-26 15:49:52] davidstrauss: what are you thinking in regard to Views, Tapir, etc. given the 2 options? [2009-10-26 15:49:55] Jody: that can be altered without breaking everything [2009-10-26 15:50:04] DamZ: I'd rather see a Views dependency that makes me grumble than unreliable code. [2009-10-26 15:50:07] backlog: http://pastebin.com/m1617db36 [2009-10-26 15:50:19] -->| gusaus (n=charlie@drupal.org/user/22137/view) has joined #d7uc [2009-10-26 15:50:23] davidstrauss: there is no discussion about Views [2009-10-26 15:50:24] :) [2009-10-26 15:50:25] rszrama: So, based on what DamZ's said about Tapir, I think you should port and include it. [2009-10-26 15:50:37] * rszrama nods. [2009-10-26 15:50:44] davidstrauss: we can ditch about 30% of the Ubercart code with Views ;) [2009-10-26 15:51:12] rszrama: If Tapir is superior to what core does, then by all means experiment and show off your superior system. [2009-10-26 15:51:12] bah, I wouldn't put it at more than 25% ;) [2009-10-26 15:51:31] rszrama: Core moves forward when contrib discovers and implements better ways of doing things. [2009-10-26 15:51:34] we decided against dependency on views bulk operations tho [2009-10-26 15:51:46] Jody: +1 [2009-10-26 15:51:58] davidstrauss: Tapir for D7 will basically be a refactored theme_table, based on the ideas of http://drupal.org/node/80855 [2009-10-26 15:52:04] Jody: and it'll make for a hella tight contrib mod ;) [2009-10-26 15:52:16] DamZ: All the more reason to move forward with it. [2009-10-26 15:52:30] Jody: we did? [2009-10-26 15:52:35] There's no better argument for inclusion of something in core than a great example of the API's usefulness. [2009-10-26 15:52:35] [INFO] 2 matches for ``Da'': [DamZ, davidstrauss] [2009-10-26 15:52:36] i think the tapir name is confusing [2009-10-26 15:52:44] Tables API? :D [2009-10-26 15:52:45] DamZ, yes, but we can still implement things for VBO [2009-10-26 15:52:59] So do we agree on including tapir in this sprint? [2009-10-26 15:53:06] rszrama: Let's avoid things that make it seem like a DB system [2009-10-26 15:53:16] rszrama: Personally, I think the naming is rather unimportant [2009-10-26 15:53:21] :D [2009-10-26 15:53:26] davidstrauss: DB system? [2009-10-26 15:53:26] IslandUsurper: in that case, you have degraded features when VBO is not available? [2009-10-26 15:53:30] tables API Ryanszarma [2009-10-26 15:53:33] rszrama: tables, databases, etc. [2009-10-26 15:53:40] rszrama: We can debating naming if/when it goes into core [2009-10-26 15:53:44] :D [2009-10-26 15:53:52] At least Tapir is unambiguous [2009-10-26 15:54:01] DamZ, right. Mostly, VBO lets us edit a lot of things at once. We should always be able to edit those things one at a time [2009-10-26 15:54:18] IslandUsurper: ok, good for me [2009-10-26 15:54:21] ok, so, mikejoconnor's question - is this good to target for this month? I think so, and I'm happy to turn http://drupal.org/project/tapir over to DamZ as long as he agrees to to take on CA work in a significant way ;) [2009-10-26 15:54:41] *not to*? [2009-10-26 15:54:43] Now, I strongly think CA should be abandoned in favor of Rules. [2009-10-26 15:54:59] lol [2009-10-26 15:55:03] DamZ: yeah, that :P [2009-10-26 15:55:05] davidstrauss: there is no debate here either, but we have a timing issue [2009-10-26 15:55:16] DamZ: OK. [2009-10-26 15:55:17] DamZ: trying not to ruin your life for the next month between work and contrib ;) [2009-10-26 15:55:21] DamZ: what about instead of porting CA we help out Fago? [2009-10-26 15:55:22] davidstrauss: because Rules is ongoing a very significant revamp [2009-10-26 15:55:26] davidstrauss: the general idea is we will port ca for now, and re-evaluate when rules is ready [2009-10-26 15:55:31] DamZ: understood [2009-10-26 15:55:48] japerry: open, I haven't spoken with him since DCParis [2009-10-26 15:55:50] mikejoconnor: That's reasonable, especially since CA should be reasonably easy to port to D7. [2009-10-26 15:55:51] |<-- duellj has left freenode () [2009-10-26 15:56:19] japerry: I think we want to start that discussion asap, anyway [2009-10-26 15:56:19] ok, so the next item on the list is products? [2009-10-26 15:56:33] DamZ: definitely agreed, we need to get rolling with rules [2009-10-26 15:56:39] and figure out where he actually is [2009-10-26 15:56:49] for products, see http://d7uc.org/node/49 for a summary of thinking so far [2009-10-26 15:56:49] and get all that figured out, THEN make a decision to use CA in ubercore [2009-10-26 15:56:50] I see fields api there as well, but I think that was simply evaluating how to use the fields api with products [2009-10-26 15:56:55] Fields are fieldable, correct? [2009-10-26 15:56:56] it's extremely exciting ;) [2009-10-26 15:56:58] yeah [2009-10-26 15:57:05] If we're talking re-architecture, then products need to be simple decorators on regular node types. [2009-10-26 15:57:16] want to make sure that feature actually got in [2009-10-26 15:57:21] davidstrauss: yeah, node = product display, not a product definition [2009-10-26 15:57:25] davidstrauss: don't jump to conclusions ;) [2009-10-26 15:57:33] davidstrauss: we spent two days on products already ;) [2009-10-26 15:57:42] DamZ: ok :-) [2009-10-26 15:57:50] davidstrauss: you should have joined us, we could have really used your input :) [2009-10-26 15:57:50] hmm, that forum thread summarizes it - lemme link in the appropriate pics [2009-10-26 15:58:08] davidstrauss: and the basic assumption is that products are first level objects [2009-10-26 15:58:08] too bad we didn't have a planner inviting people... where were you at, amye? ;) [2009-10-26 15:58:09] I suppose we still can, but maybe it would have been a lot less confusing [2009-10-26 15:58:09] davidstrauss: ie. not nodes [2009-10-26 15:58:29] rszrama: Running a DrupalCamp, so sue me. :) [2009-10-26 15:58:33] hmm the first thing that pops out to me is associating prices with products [2009-10-26 15:58:34] hehe [2009-10-26 15:58:46] davidstrauss: products are what is in your warehouse (physical or virtual), and are keyed by SKU [2009-10-26 15:58:58] DamZ: Ah, makes sense [2009-10-26 15:59:03] davidstrauss: nodes can have a special "product display" field that can display one or more products [2009-10-26 15:59:07] japerry: it's merely a default price, fwiw - i.e. it can be altered or ignored, but if you're simply adding something to an order through admin, it would have a default [2009-10-26 15:59:19] davidstrauss: nodes are what your customer can see and interact with [2009-10-26 15:59:20] DamZ: Well, anything but the sorta CCK Drupal 4.7-ish system it has going right now would be good. [2009-10-26 15:59:26] lol [2009-10-26 15:59:33] davidstrauss: agreed 100% [2009-10-26 15:59:34] japerry: basically we wanted to include teh base info that you have with any accounting system. modelno, price, title [2009-10-26 15:59:36] davidstrauss: 200% [2009-10-26 15:59:56] I can't remember, btw - did we determine the need for a uniqid on products in addition to SKU? [2009-10-26 16:00:06] I know QuickBooks has one, they call it the listId or something [2009-10-26 16:00:10] okay, cool, so as long as we can easily define price modifiers per product, which is a little difficult at the moment [2009-10-26 16:00:10] rszrama, I think we said it didn't [2009-10-26 16:00:21] rszrama: we said we go with a string SKU [2009-10-26 16:00:27] kk [2009-10-26 16:00:33] hm [2009-10-26 16:00:36] or maybe not? [2009-10-26 16:00:40] are there any objections to that from the folks in the discussion now? tr, japerry, davidstrauss ? [2009-10-26 16:00:53] would someone please copy this whole chat somewhere when you're done? I need to go pass out now (swine flu) [2009-10-26 16:00:54] japerry: we talked about that inconvenience as well, but I think that comes in a later sprint [2009-10-26 16:00:58] japerry, it looks like price modifiers and such are slated for the next sprint [2009-10-26 16:01:01] I remember a discussion during which I changed my mind about that [2009-10-26 16:01:22] Jody: feel better :( [2009-10-26 16:01:26] I don't remember why [2009-10-26 16:01:27] we discussed the need to change a sku [2009-10-26 16:01:29] Jody: we'll have it on d7uc.org when we're done [2009-10-26 16:01:30] |<-- Jody has left freenode () [2009-10-26 16:01:45] we also discussed revisions [2009-10-26 16:01:50] DamZ: yeah, I was thinking about that, too [2009-10-26 16:01:55] mikejoconnor, and I think we said that would just be creating a new product [2009-10-26 16:02:01] I guess what I'd like to see is a flexible way to add prices to products, without having to hook_alter or impliment custom_price like what currently happens [2009-10-26 16:02:04] because the old orders still had to refer to the old product data [2009-10-26 16:02:05] if we're going to have revisions, we must have a uniqid unless we do a new product [2009-10-26 16:02:19] japerry: hmm, maybe we make sure there's a price field for that? [2009-10-26 16:02:32] IslandUsurper: ahh, yeah [2009-10-26 16:02:34] rszrama: yah thats what I was thinking [2009-10-26 16:02:37] I'm just trying to remember why we re-evaluated the sku issue [2009-10-26 16:02:40] IslandUsurper: orders have to be self-contained [2009-10-26 16:03:05] IslandUsurper: totally agree about statefulness [2009-10-26 16:03:14] sorta the same issues addresses run into [2009-10-26 16:03:17] I remember arguing that we need a display ID [2009-10-26 16:03:21] can't remember why [2009-10-26 16:03:45] DamZ: maybe you're confusing the order discussion? [2009-10-26 16:03:46] japerry: orders have to be self-contained, ie. they do not reference anything from outside the order itself [2009-10-26 16:03:51] DamZ: that was part of our discussion on what a cart is, and if a cart just be an order without a display id [2009-10-26 16:03:55] DamZ: we did discuss a uniqid and a display ID for orders [2009-10-26 16:03:57] DamZ: yup. [2009-10-26 16:04:08] DamZ: once an order is made, its its own object [2009-10-26 16:04:09] japerry: it's basically already the case in UC2 [2009-10-26 16:04:21] rszrama: mikejoconnor: that's it ;) [2009-10-26 16:04:34] ok so, a string SKU it is [2009-10-26 16:04:40] here was our "what is a product" list: http://d7uc.org/node/59 [2009-10-26 16:04:58] I'd also like to vote for calling it anything but sku [2009-10-26 16:05:09] sku is only used in north america [2009-10-26 16:05:12] product_id? [2009-10-26 16:05:17] I need to head off, but I trust DamZ's judgment in case people are looking for a tie-breaker. :-) [2009-10-26 16:05:17] sounds great [2009-10-26 16:05:25] we started with "model", but some people said that confused them [2009-10-26 16:05:27] lol [2009-10-26 16:05:31] davidstrauss: #flatered [2009-10-26 16:05:38] I think product_id is good [2009-10-26 16:05:42] lol, trusting damz, hmm [2009-10-26 16:05:44] DamZ: yah, sorry, UC2 is working properly in that case. I'm glad we're all remembering that for ubercore ;-) [2009-10-26 16:05:45] davidstrauss: lol - thanks for stopping by, David :) [2009-10-26 16:06:06] model can be confusing, because in some cases you have many versions of one model, each with their own unique id [2009-10-26 16:06:09] Bojhan: people have strange ideas ;) [2009-10-26 16:06:19] DamZ: I know right [2009-10-26 16:06:42] (OT: I linked in the images to http://d7uc.org/node/49 - does anyone know the module that lets you put in [#nid] and converts it to a link?) [2009-10-26 16:07:18] http://drupal.org/project/link_node ? [2009-10-26 16:07:24] http://drupal.org/project/node_link [2009-10-26 16:07:39] lol [2009-10-26 16:07:48] duplication at its best [2009-10-26 16:07:49] (again OT, we may want to get Druplicon in this channel sometime) [2009-10-26 16:07:49] I thought that was a filter ... [2009-10-26 16:08:11] is there a module that works for D6? :P [2009-10-26 16:08:11] I can bring in drupalfr, as a temporary solution [2009-10-26 16:08:18] rszrama: link_node [2009-10-26 16:08:36] DamZ: ahh, thanks [2009-10-26 16:08:56] DamZ: does drupalfr condescend to speak English? ;) [2009-10-26 16:09:12] rszrama: no, you have to speak frensh [2009-10-26 16:09:19] rszrama: sure ;) [2009-10-26 16:09:22] ^_^ [2009-10-26 16:09:29] ok, so... where were we, again? [2009-10-26 16:09:36] ok, so we are 10 minutes past our target time. I'd like to finish up the list, and do some quick estimates. is anyone against extending this for another 30 minutes? [2009-10-26 16:09:46] I'm game [2009-10-26 16:09:50] -->| Drupalfr (n=Drupalfr@core2.drupalfr.org) has joined #d7uc [2009-10-26 16:10:08] ok for me [2009-10-26 16:10:09] ok, so we will take silences as a go for it :) [2009-10-26 16:10:27] Do you think we can finish in 30? [2009-10-26 16:10:30] vu Damz [2009-10-26 16:10:35] If we stay focused we can :) [2009-10-26 16:10:54] |<-- Drupalfr has left freenode (Remote closed the connection) [2009-10-26 16:10:57] -->| Drupalfr (n=Drupalfr@core2.drupalfr.org) has joined #d7uc [2009-10-26 16:11:01] enabling logging [2009-10-26 16:11:12] are there any issues with the product outline in node/49? [2009-10-26 16:11:14] http://bot.drupalfr.org/bot/log/d7uc [2009-10-26 16:11:31] I'm game for another 20 mins, then I have a phone conf call. but I'll still be here [2009-10-26 16:11:48] ok. Product entry fields take references to product objects [2009-10-26 16:11:56] mikejoconnor: it needs to be refined, but the principles are ok for me [2009-10-26 16:12:08] I agree [2009-10-26 16:12:10] IslandUsurper: wheeee! yes! [2009-10-26 16:12:20] it needs to be updated to address "product describer" attributes... the ol' name on the plaque :-/ [2009-10-26 16:12:22] IslandUsurper: that is for product kits, correct? [2009-10-26 16:12:29] it's for everything [2009-10-26 16:12:31] mikejoconnor: nein, in general [2009-10-26 16:12:45] ah, I was thinking of something else [2009-10-26 16:12:51] rszrama: descriptions? [2009-10-26 16:12:53] there will be some setting that dictates whether multiple values means product kit or "select one" [2009-10-26 16:12:59] rszrama: that's part of the node for me [2009-10-26 16:13:05] I started calling it an "Add to Cart Field"... [2009-10-26 16:13:05] it may be possible to do both at once [2009-10-26 16:13:13] "Product display field"? [2009-10-26 16:13:18] DamZ: yeah, definitely - I'm talking about things like textfield attributes [2009-10-26 16:13:32] the field formatter should provide some way (link or form) to add the product(s) to the cart [2009-10-26 16:13:39] well, do we want the same field to handle both display and adding to the cart? [2009-10-26 16:13:54] rszrama: oh... yes indeed [2009-10-26 16:14:11] DamZ: i.e. a field that displays a product w/o any option to add it to the cart? [2009-10-26 16:14:16] rszrama, themers should be able to extract the product data and display it how they want [2009-10-26 16:14:20] rszrama: yes [2009-10-26 16:14:32] but to display the entry field itself means to have a way to add it to the cart [2009-10-26 16:14:36] ok, in that case, "Add to Cart Field" isn't generic enough [2009-10-26 16:14:46] Fields can be loaded but not displayed, right? [2009-10-26 16:14:49] not in what I just described above that Damz affirmed [2009-10-26 16:15:09] hm. ok [2009-10-26 16:15:17] |<-- davidstrauss has left freenode () [2009-10-26 16:15:20] that part needs to be clarified [2009-10-26 16:15:21] I'm not saying he's right, that's just where the discussion was ;) [2009-10-26 16:15:25] that will be for another meeting I believe [2009-10-26 16:15:30] kk [2009-10-26 16:15:52] the basic idea is to have one or more fields to display one or more product and eventually add them to the cart [2009-10-26 16:16:01] as a new product or as individual products [2009-10-26 16:16:17] that's very complex, and there are several different use cases [2009-10-26 16:16:23] we need to build a generic solution [2009-10-26 16:16:39] at the very least, we have enough to get started, right? a fieldable product entity, a way to store these in the database, good hook coverage, Views integration [2009-10-26 16:16:55] yep [2009-10-26 16:17:05] Where, will this product entity show up in the UI? [2009-10-26 16:17:13] in terms of adding fields ect [2009-10-26 16:17:24] Just like any other entity as terms, users ect? [2009-10-26 16:17:30] yeah, I think that was the idea [2009-10-26 16:17:31] |<-- stephthelaptop has left freenode (Connection timed out) [2009-10-26 16:17:37] not sure we really got that far in terms of administration :-/ [2009-10-26 16:17:41] Bojhan: not completely sure yet [2009-10-26 16:17:50] the most we drew up was http://d7uc.org/node/62 [2009-10-26 16:17:54] Bojhan: we have not discussed in depth what the IA will be [2009-10-26 16:18:05] Bojhan: nor what "bundles" will be available for products [2009-10-26 16:18:08] mostly, it will probably depend on how much the Field UI gives us [2009-10-26 16:18:26] Bojhan: we will probably have something like admin/stores/product-types//fields [2009-10-26 16:18:43] the same way we have admin/structure/content-types//fields [2009-10-26 16:18:46] DamZ: alright, that sounds like fields [2009-10-26 16:18:47] yhea [2009-10-26 16:18:54] DamZ: Alright, thats simple enough [2009-10-26 16:19:22] IslandUsurper: the Field UI does mostly everything for us, but we have to define the bundles [2009-10-26 16:19:28] (aka "product types/classes") [2009-10-26 16:19:55] (OT: yay, link_node worked fine ;) ) [2009-10-26 16:20:12] are we targeting a simple "Add to Cart" field (or whatever it's called) for this sprint? [2009-10-26 16:20:19] wait [2009-10-26 16:20:23] that depends on a cart :) [2009-10-26 16:20:34] I guess it can be developed, though, and just not actually add to the cart [2009-10-26 16:20:35] rszrama, if nothing else, we can stub a cart link [2009-10-26 16:20:44] * rszrama high fives IslandUsurper. [2009-10-26 16:20:46] form with no submit [2009-10-26 16:20:47] so are we comfortable with our sprint as is? [2009-10-26 16:21:01] i.e. have we selected too much, too little? [2009-10-26 16:21:06] CA, Tapir, budding products and a product field? [2009-10-26 16:21:19] outsource discussion to UC.org for Uber Tuber on D7 [2009-10-26 16:21:33] I think we can task amye with continued follow-up on developer leads [2009-10-26 16:21:38] rszrama: The 2.0 port will have to be discussed, but maybe we don't have to resolve it this month. [2009-10-26 16:21:40] I think that the add to cart field is not critical [2009-10-26 16:21:43] rszrama: Like? [2009-10-26 16:21:44] * rszrama nods. [2009-10-26 16:22:02] I expect I'll be working on products, and I think that's enough for me [2009-10-26 16:22:04] DamZ: I tend to agree, since we don't have a cart / order to add too [2009-10-26 16:22:22] Actually, yeah, if I could see who's committed to what piece for this sprint.. [2009-10-26 16:22:23] mikejoconnor: Is there a page,which outlines what you will do for Sprint 1? [2009-10-26 16:22:25] amye: not sure... we can come back to that [2009-10-26 16:22:43] Bojhan: not yet, but Ryan just summarized it [2009-10-26 16:22:44] Bojhan: we'll have it after this sprint [2009-10-26 16:22:48] ok [2009-10-26 16:22:58] Port CA, and Tapir, and create products [2009-10-26 16:23:11] rszrama, is there anything left but make sure who is going to do what? [2009-10-26 16:23:26] Bojhan: what about all this interests you, btw? speccing out UI for product administration? the add to cart field? [2009-10-26 16:23:35] one sec... lemme review [2009-10-26 16:23:53] rszrama: Well, obviously product has to be done - that is mostly conforming to Drupal 7 standards in regards to tabs, and fields ui. [2009-10-26 16:24:04] I think it would be good to decide on coding tasks and then to talk meta-initiative stuff... website maintenance, outreach, communication, etc. [2009-10-26 16:24:10] rszrama: The add to cart view, somewhat confuses me , as it seems critical - but the actual functionality is not laid out yet? [2009-10-26 16:24:24] IslandUsurper: I think we need a better understanding of what we are actually doing. i.e. what happens during hte port of ca? [2009-10-26 16:24:38] Bojhan: specced out roughly on http://d7uc.org/node/49 ... basically, a field you can add to a node type to present products for purchase [2009-10-26 16:24:58] rszrama: oke [2009-10-26 16:25:01] mikejoconnor: ahh, yeah - where / how to get this code rolling... when do we commit to http://drupal.org/project/ubercore, how do we use Github (if we use it) [2009-10-26 16:25:16] Bojhan: but we had kind of wireframed modal support for adding products on the fly [2009-10-26 16:25:22] so lets start on who wants to contribute to what [2009-10-26 16:25:23] I'm now arguing for bzr, and against git [2009-10-26 16:25:34] DamZ: I agreee [2009-10-26 16:25:36] lol [2009-10-26 16:25:40] rszrama: Do you have a picture of that for me? [2009-10-26 16:25:44] (based on the "better of wrong with the crowd then right alone" paradigm) [2009-10-26 16:25:46] I like bzr, why switch to git? [2009-10-26 16:25:53] I hate bzr [2009-10-26 16:25:54] DamZ: because bzr is superior, or because you think d.o will be using bzr soon? [2009-10-26 16:25:59] let's switch to bzr [2009-10-26 16:26:06] Bojhan: we'll call this a rough pic - http://d7uc.org/sites/default/files/pictures/PA160311.JPG [2009-10-26 16:26:15] DamZ: Dropbox works [2009-10-26 16:26:16] mikejoconnor: there is a movement to get do to bzr [2009-10-26 16:26:46] the good thing is, we can easily switch from git to bzr [2009-10-26 16:26:51] or the other way around [2009-10-26 16:27:03] on the other hand, I have no idea how good is the bzr / CVS integration [2009-10-26 16:27:07] launchpad was really effective for the d7cx stuff [2009-10-26 16:27:11] not very at all, DamZ [2009-10-26 16:27:11] ya, I have no issues either way, other than my personal preference. [2009-10-26 16:27:24] Bojhan: a lot of things need to be specced out on d7uc.org, one thing I hope to address before ending this meeting is how to effectively facilitate that on the site [2009-10-26 16:27:27] launchpad is a pile of crap [2009-10-26 16:27:34] but hey [2009-10-26 16:27:36] lol [2009-10-26 16:27:38] DamZ: I have a script that migrates from one to the other [2009-10-26 16:27:40] Bojhan: erm, things as in IA, how the fields work, etc. [2009-10-26 16:27:43] apparently people want bzr, for some reason [2009-10-26 16:27:53] rszrama: Oke, no problem - I can wait. [2009-10-26 16:27:59] DamZ: because they are comparing it to cvs :) [2009-10-26 16:28:00] I'm comfortable with it, and not git for some reason [2009-10-26 16:28:08] lauchpad really doesn't stand the comparaison against github [2009-10-26 16:28:08] DamZ: talk to Davidstrauss about it ;-) [2009-10-26 16:28:29] It sounds like we've got momentum towards bzr, so let's do it. [2009-10-26 16:28:38] amye: that's exactly my point [2009-10-26 16:28:48] (even if the tool is not that great in so many ways) [2009-10-26 16:28:56] either way, as much as I'm for GIT, I think that we should make the same poor choice as d.o. [2009-10-26 16:28:57] Why do things differently than d.o ? That just makes it more difficult for the community to become involved [2009-10-26 16:29:01] (but hey, it has a *WINDOWS* version) [2009-10-26 16:29:12] tr: that's exactly what everyone is saying! ;) [2009-10-26 16:29:23] that's what I'm saying [2009-10-26 16:29:26] d.o doesn't use bzr ... [2009-10-26 16:29:27] yah the barrier to entry for bzr is much lower, which is why I'm for it [2009-10-26 16:29:30] better of wrong with the crowd then right alone [2009-10-26 16:29:35] however, didn't we decide to keep cvs as the main repo, and the use what ever we wanted personally in our working groups? [2009-10-26 16:29:53] i.e. sync from cvs to bzr instead of from bzr to cvs ? [2009-10-26 16:30:01] mikejoconnor: that would require manual merging [2009-10-26 16:30:01] mikejoconnor: yeah [2009-10-26 16:30:06] I hope so :-P [2009-10-26 16:30:11] mikejoconnor: not sure Ryan wants to manually apply patches [2009-10-26 16:30:19] mikejoconnor: but if he is confortable with that, good for me [2009-10-26 16:30:22] I don't mind syncing, but the way it is now all that's in CVS is the tarball, right? [2009-10-26 16:30:24] I'd have my own Bzr repo, right? [2009-10-26 16:30:29] hmm in bzr, there was some command we were doing to easily sync the patches [2009-10-26 16:30:46] will have to go look at my .bash_history ... David is the bzr expert [2009-10-26 16:31:10] we kind of left the "resource allocation" aspect of the conversation behind in the VCS storm [2009-10-26 16:31:13] tr: the idea is to sync all patches one by one [2009-10-26 16:31:36] tr: we are not willing to repeat the current "sync eventually a big patch" model [2009-10-26 16:32:06] I support putting DamZ in charge of the vcs issue [2009-10-26 16:32:09] DamZ: but we still wanted to have much better management of the code on d.o CVS than what we've had, right? [2009-10-26 16:32:35] rszrama: yep [2009-10-26 16:32:37] i.e. we aren't just pushing bulk changes to CVS when we think about it? [2009-10-26 16:32:56] rszrama: we want to have the full history on d.o CVS [2009-10-26 16:33:01] what I really want is a bzr post-commit hook to commit to CVS every time a commit is made to the main repo [2009-10-26 16:33:03] * rszrama nods. [2009-10-26 16:33:07] rszrama: but we don't need to work directly on d.o CVS [2009-10-26 16:33:15] right [2009-10-26 16:33:20] IslandUsurper: yep, that's the basic idea I have [2009-10-26 16:33:37] So we have about 10 minutes left [2009-10-26 16:33:39] IslandUsurper: having the main branch (managed by Ryan) push automatically to d.o CVS [2009-10-26 16:33:44] So your plan is CVS is the master, and whatever the dev wants to use (bazaar, etc.) is fine as long as it will sync? [2009-10-26 16:34:05] but for the long tail of contributors, they can easily checkout Ubercore from CVS and roll minor patches... this whole VCS discussion really affects the initial co-development frenzy [2009-10-26 16:34:09] tr: no, we plan to have a bzr master branch, that is automatically pushed to d.o CVS [2009-10-26 16:34:28] So in order to contribute I will have to use bazaar? [2009-10-26 16:34:38] tr: no [2009-10-26 16:34:47] we want to avoid that... that's basically the way it is now [2009-10-26 16:34:57] tr: because the full history is in d.o CVS, you can simply roll your patch from there [2009-10-26 16:35:05] tr: I think the plan is that from the general developer perspective, you use d.o. cvs, however behind the scene, you can optionally use a bzr repo, which is always in sync with cvs [2009-10-26 16:35:06] mikejoconnor: I haven't heard anything about 'yes, we have enough to work on', or 'no, too much'.. [2009-10-26 16:35:21] tr: it will be reviewed, committed by Ryan on the main branch, and automatically pushed to d.o CVS [2009-10-26 16:35:33] I know that, of course, and I've advocated to push UC into CVS for a good long while ... I just don't understand what you're proposing [2009-10-26 16:35:37] mikejoconnor: we really want bzr to be the master [2009-10-26 16:35:39] amye, I have enough to work on :) [2009-10-26 16:35:52] mikejoconnor: it will be easier [2009-10-26 16:36:11] ok, so... we can begin development without nailing down the VCS workflow, but it needs to fall into place extremely fast [2009-10-26 16:36:13] IslandUsurper: You have like, one thing. :P [2009-10-26 16:36:14] DamZ: yes, but to the the general joe developer, it will be seamless. The average Drupal developer can use cvs without an issue [2009-10-26 16:36:21] amye, it's a big one, though [2009-10-26 16:36:23] DamZ: but Ryan will be committing to bzr [2009-10-26 16:36:33] tr: from what I understood, the advantage of initially using Bzr / Git was to enable people to develop major patches in tandem [2009-10-26 16:36:35] IslandUsurper: I knows, I'm kidding. [2009-10-26 16:36:42] and behind the scenes, bzr will be updating cvs, at every commit. [2009-10-26 16:36:45] rszrama: ok, I'm taking the action [2009-10-26 16:37:02] tr: however, development can just as easily occur from CVS, esp. for the long tail of contributors [2009-10-26 16:37:51] DamZ: ok, would it be possible to have a proposal on d7uc.org for review this week? [2009-10-26 16:37:52] tr: does that make sense / sound good? [2009-10-26 16:38:02] rszrama: sure [2009-10-26 16:38:20] ok, so are we all ok with the size of this sprint? [2009-10-26 16:38:22] ok, DamZ now has the most tasks [2009-10-26 16:38:26] ;) [2009-10-26 16:38:30] mikejoconnor: I thought that's what *I* had said, then I was contradicted ... [2009-10-26 16:38:51] rszrama, does that mean he wins? [2009-10-26 16:39:02] nah, it means he loses more sleep [2009-10-26 16:39:16] IslandUsurper: I just need more ramen now [2009-10-26 16:39:25] time to buy stock in coffee pots [2009-10-26 16:39:27] (and more coffee pots as a consequence) [2009-10-26 16:39:29] tr: ahh, I see what you're referring to above; I think the only difference in DamZ's clarification was that there's still a Bzr master branch, and it's mirrored _to_ d.o CVS, not vice versa [2009-10-26 16:39:31] so size of the sprint [2009-10-26 16:39:50] Ok, so we were going to try and use d.o to track our progress and use it for project management. [2009-10-26 16:40:05] Does this still fit with the using bzr, i mean cvs.. [2009-10-26 16:40:09] hehe [2009-10-26 16:40:11] tr: sorry for the misunderstanding [2009-10-26 16:40:12] yes [2009-10-26 16:40:18] Size of the sprint is good then :) [2009-10-26 16:40:47] amye: do we want to open individual tasks on d.o? [2009-10-26 16:40:52] I think the size is good [2009-10-26 16:41:02] DamZ: I think so [2009-10-26 16:41:08] DamZ: Probably best. Then you know what you're signed up for. [2009-10-26 16:41:12] DamZ: otherwise people won't know where to start helping / what's going on [2009-10-26 16:41:16] Where will future sprints be announced? [2009-10-26 16:41:21] Possibility of cc'ing me on that? [2009-10-26 16:41:22] amye: can you work on this? [2009-10-26 16:41:28] tr: d7uc and twitter [2009-10-26 16:41:37] http://d7uc.org/development/schedule - we have the dates planned, we can do better to communicate the contents [2009-10-26 16:41:47] I can start, but I don't have enough about 'Products' to be able to really break those down. [2009-10-26 16:41:52] tr: do you have bandwidth to get in on coding atm? [2009-10-26 16:41:53] Can d.o have custom components on projects? [2009-10-26 16:42:02] Bojhan: I believe so [2009-10-26 16:42:07] Bojhan: yes [2009-10-26 16:42:15] Bojhan: d.o is awesome ;) [2009-10-26 16:42:21] d.o++ [2009-10-26 16:42:28] lol [2009-10-26 16:42:29] *cough* right [2009-10-26 16:42:34] Did we decide that ca should be a separate module, or a core include [2009-10-26 16:42:48] the good thing about d.o is that if it is bad, it's your fault [2009-10-26 16:43:00] you should have contributed to it ;) [2009-10-26 16:43:02] mikejoconnor: hmm, if we can encapsulate it in a class, core include +1 [2009-10-26 16:43:27] DamZ: I did :') [2009-10-26 16:43:33] rszrama: I'm still unsure about this class encapsulation idea ;) [2009-10-26 16:43:36] hehe [2009-10-26 16:43:52] rszrama: anyway, I would say separate module [2009-10-26 16:44:00] yeah, me, too [2009-10-26 16:44:00] I think that would change it from a port to a rewrite [2009-10-26 16:44:04] k [2009-10-26 16:44:04] yeah [2009-10-26 16:44:13] rszrama: yes, to some extent. I'd be interested in a port if that's in the plans... [2009-10-26 16:44:16] rszrama: Can you add a User Interface component to Ubercart ? [2009-10-26 16:44:20] Jody, do you want to create the module? [2009-10-26 16:44:35] ok, so, CA and TAPIr are easy tickets... should we make tickets for tasks like determining VCS workflow? [2009-10-26 16:44:38] Jody's gone, mikejoconnor [2009-10-26 16:44:43] Bojhan: will do [2009-10-26 16:44:44] oh.... [2009-10-26 16:44:45] oops [2009-10-26 16:45:01] Bojhan: rszrama: on it [2009-10-26 16:45:10] Bojhan: oh, there is already one [2009-10-26 16:45:16] DamZ: o.O? [2009-10-26 16:45:47] it's there for Ubercore, not on Ubercart [2009-10-26 16:45:48] amye, there are about 3 sections to the Products task: Create a product field, add fields like price, etc. to product fields, and formatting the field as an add to cart form or link [2009-10-26 16:45:56] * Bojhan is so silly [2009-10-26 16:46:04] now it's in both places [2009-10-26 16:46:30] IslandUsurper: and creating a fieldable product entity itself, right? [2009-10-26 16:46:39] IslandUsurper: with all the pertinent UI components [2009-10-26 16:47:00] I suggest a pinned topic on uc.org announcing d7uc.org and pointing to future discussions ... [2009-10-26 16:47:13] Ok, so here's my current list of tickets to add to d.o: CA,TAPIR,Determining VCS workflow,Create a product field, add fields like price, Formatting the field as an add to cart form or link [2009-10-26 16:47:15] rszrama, yeah, the product value of the field [2009-10-26 16:47:38] IslandUsurper: does not compute [2009-10-26 16:47:42] amye, add "Product entity" to connect the first two [2009-10-26 16:47:54] first two product tickets* [2009-10-26 16:48:00] Ok. [2009-10-26 16:48:11] IslandUsurper: ok, I think I'm with you... the product field _is_ the base of the product entity? [2009-10-26 16:48:15] yeah [2009-10-26 16:48:22] something like that [2009-10-26 16:48:23] IslandUsurper: and that has the SKU and default price / title? [2009-10-26 16:48:29] I've got a month to figure it out [2009-10-26 16:48:34] IslandUsurper: will that afford us a products table? heh [2009-10-26 16:48:35] ok [2009-10-26 16:48:44] I expect Field API to give me that for free [2009-10-26 16:48:57] I don't... [2009-10-26 16:49:09] ok [2009-10-26 16:49:11] so... [2009-10-26 16:49:17] there are other issues to discuss [2009-10-26 16:49:30] regarding making sure we have good feedback channels [2009-10-26 16:49:48] and are maintaining the ol' design document instead of just cowboy coding [2009-10-26 16:49:50] rszrama: "product entity" is basically the base table for the fieldable entity [2009-10-26 16:49:59] DamZ: that was my thought [2009-10-26 16:50:02] DamZ: it's distinct from a field, right? [2009-10-26 16:50:14] DamZ: or is it itself a field? [2009-10-26 16:50:15] rszrama: yes, it's the base table in the star database schema [2009-10-26 16:50:19] kk [2009-10-26 16:50:20] thanks [2009-10-26 16:50:42] rszrama: the entity is the base table, fields are tables around the entity in a star schema [2009-10-26 16:51:03] DamZ: can we call bundles constellations? [2009-10-26 16:51:05] rszrama: think "node table" and "color field" [2009-10-26 16:51:16] * rszrama nods. [2009-10-26 16:51:16] rszrama: we should! ;) [2009-10-26 16:51:28] re: tr's suggestion - I think communication on Ubercart.org is a good thing, I don't know how to make it happen [2009-10-26 16:52:22] well moving the port discussion to ubercart.org should help [2009-10-26 16:52:27] * rszrama nods. [2009-10-26 16:52:47] Ok, I need to step out for a bit, but I have the tickets and will put those up on D.O, and it looks like things are progressing nicely. [2009-10-26 16:52:48] agreed [2009-10-26 16:53:12] amye: alrighty, maybe I'll just send a quick e-mail to follow-up re: eaton and other contributors [2009-10-26 16:53:17] Thanks! [2009-10-26 16:53:17] We should do some quick feature scoring [2009-10-26 16:53:24] your mom's a feature score [2009-10-26 16:53:38] I want to try to stay on the topic of communication / feedback channels first [2009-10-26 16:53:44] amy, did we agree on a 1,2,3,5,8 [2009-10-26 16:54:03] rszrama: ok [2009-10-26 16:54:30] if we're going to improve communication, we need to make sure we're actually keeping d7uc.org current and have effective ways for people to provide feedback [2009-10-26 16:54:52] for example, Bojhan should know where / how to contribute UI advice to the discussion even if he never writes a line of code [2009-10-26 16:55:03] and this sprint is already bringing UI trouble to the table :) [2009-10-26 16:55:07] mikejoconnor: I think that makes more sense. [2009-10-26 16:55:54] does anyone have any ideas on improving communication / feedback, or should I just make stuff up and see how it flies? :P [2009-10-26 16:56:01] rszrama: So you know have 3 places of communication. d.o , d7uc.org , ubercart.org? [2009-10-26 16:56:11] -k [2009-10-26 16:56:16] well my issues with uc1/uc2 is that I never really knew what was happening, and how to help [2009-10-26 16:56:35] right, we roughly addressed this here: http://d7uc.org/node/52 [2009-10-26 16:56:45] I think a good place to start is breaking down what we intend to do into nice chunks [2009-10-26 16:57:31] what do you mean? [2009-10-26 16:57:31] so for ca, I would have something like Update to the new coding standards, Update to the D7 api, Unit testing, UI testing [2009-10-26 16:58:10] Those last two are available for everybody's tasks, too [2009-10-26 16:58:14] hehe, do we want to open the UI can of worms? [2009-10-26 16:58:17] yeah [2009-10-26 16:58:18] I might even break the unit/ui testing into sub tasks [2009-10-26 16:58:31] rszrama: not yet [2009-10-26 16:58:34] will d.o ever have parent / child tasks? [2009-10-26 16:58:41] rszrama: but I said it anyway [2009-10-26 16:58:41] rszrama: yes [2009-10-26 16:58:47] -->| davidstrauss (n=davidstr@wikimedia/davidstrauss) has joined #d7uc [2009-10-26 16:58:50] Bojhan: that'd be beautiful [2009-10-26 16:58:55] rszrama: but not soon :( [2009-10-26 16:59:00] d'oh >_< [2009-10-26 16:59:02] The idea is that we need the items to be granular enough that others can contribute [2009-10-26 16:59:17] yeah [2009-10-26 16:59:43] rszrama: which is going to take a lot of discipline on our part, but I think it's for the good of the project as a whole [2009-10-26 16:59:52] mikejoconnor: What about issue queue [meta] Outline and then a whole bunch of smaller issues? [2009-10-26 16:59:59] Bojhan: I like the idea [2009-10-26 17:00:00] ok... so we need to delineate tasks, the type of feedback we want, and where such feedback should be generated? [2009-10-26 17:00:13] Bojhan: can you explain a little bit more? [2009-10-26 17:01:05] rszrama: So for core, we have had several large issues that needed to get in, by creating a [meta] Outline issue, where we outlined the purpose, why and what we where doing, it provided a lower barrier to contribute to just a part of the larger issue we are solving [2009-10-26 17:01:58] rszrama: I think most issues, worked pretty well - for core atleast [2009-10-26 17:02:13] Bojhan: can you link me to an example issue on d.o? [2009-10-26 17:02:17] rszrama: Where as having a subsite for an iniative, atleast for the d7ux.org stuff - was a massive pile of shit [2009-10-26 17:02:39] lol [2009-10-26 17:03:13] http://drupal.org/node/546956 [2009-10-26 17:03:13] http://drupal.org/node/546956 => [meta-issue] Overhaul of Information Architecture => Drupal, base system, critical, active, 1 IRC mention [2009-10-26 17:03:21] fwiw, d7uc.org is meant to actually hold the design documents for Ubercore, images, schedules, etc. [2009-10-26 17:03:21] Probally a better one, around [2009-10-26 17:03:21] DamZ: you know? [2009-10-26 17:03:58] Bojhan: ok, so you started the issue here and then consider it closed when related issues are done, w/o ever really managing patches through the issue itself? [2009-10-26 17:03:59] rszrama: Right, you should just be very carefull having two discussions on the same topic, at two places (issue queue and website) [2009-10-26 17:04:06] Bojhan: +1 [2009-10-26 17:04:19] rszrama: Yes, [2009-10-26 17:04:37] http://drupal.org/node/563106 [2009-10-26 17:04:39] http://drupal.org/node/563106 => Cannot upgrade from Drupal 6 to Drupal 7 - meta issue => Drupal, update system, critical, needs work, 1 IRC mention [2009-10-26 17:06:21] ok, so, I think I'll just take all the feedback into consideration and implement, w/ a doc page under our development process that outlines how to be involved [2009-10-26 17:06:33] we can throw a block up that links to key pages like this... :? [2009-10-26 17:06:47] rszrama: Sounds good [2009-10-26 17:07:18] Bojhan: I think w/ the current assumptions, the meta discussion would happen in the forum on d7uc.org till it's solid and then be worked into the Specification handbook [2009-10-26 17:07:36] rszrama: Oke, thats a lot of managing - hope you are up for it [2009-10-26 17:07:38] and we'd take a snapshot of the handbook at releases to implement some soft versioning of the document [2009-10-26 17:07:40] lol [2009-10-26 17:07:50] yeah, I'm not sure... [2009-10-26 17:08:04] definitely will need feedback once the doc is up... I wish we'd gotten more of our notes edited / on the site before today [2009-10-26 17:08:20] <--| robeano has left #d7uc [2009-10-26 17:08:25] rszrama: You should evaluate as you go, [2009-10-26 17:10:04] does anyone have any closing thoughts? are there rocks that need to be turned over? [2009-10-26 17:10:26] rszrama: some feature scoring [2009-10-26 17:10:34] explain? [2009-10-26 17:11:25] we should look at what we have taken on, and assign a score representing it's complexity [2009-10-26 17:11:33] ok [2009-10-26 17:11:36] not its priority? [2009-10-26 17:11:39] correct [2009-10-26 17:12:05] CA port = 1, TAPIr port / rework = 3, Products = 12 [2009-10-26 17:12:20] the idea is that if we accomplish 12 points of tasks during this sprint, and we try to select 42 points of tasks during the next sprint, we have a good idea that we are not being realistic [2009-10-26 17:12:42] re: products, I don't think IslandUsurper should take 'em on alone, so we really need DamZ to prioritize VCS workflow before Tapir [2009-10-26 17:12:47] ahh, ok [2009-10-26 17:12:53] I'd say the ca port will be a little more than on, only because of simpletesting everything [2009-10-26 17:12:55] fields on products = 2, product entities = 5, product entry fields = 3 [2009-10-26 17:13:17] if we're going to use Fibbonacci number scaling [2009-10-26 17:13:20] also, we should use the following scale 1,2,3,5,8 [2009-10-26 17:13:22] IslandUsurper: by product entry field, you mean just associating products through the field, not figuring out an add to cart form? [2009-10-26 17:13:50] eh, I'll switch those last two [2009-10-26 17:14:08] product entities = 3, product entry fields (including a simple add to cart) = 5 [2009-10-26 17:15:07] where is the UI in that? [2009-10-26 17:15:14] product entry fields [2009-10-26 17:15:28] well, all three of them really [2009-10-26 17:15:40] they all have pieces of UI [2009-10-26 17:16:11] yeah... I think getting that right increases the complexity [2009-10-26 17:16:13] and do those estimates include a) coding standards, b) testing, 3) documentation [2009-10-26 17:16:21] esp. if we're talking modal support, peer review, etc. [2009-10-26 17:16:28] mikejoconnor: what's a 1? [2009-10-26 17:16:31] Back again. [2009-10-26 17:16:44] I don't have a point of reference, so, these numbers don't actually mean much to me [2009-10-26 17:17:05] IslandUsurper: that's always the issue during hte initial estimate [2009-10-26 17:17:19] so, yes, those things are included until further notice [2009-10-26 17:17:22] so lets start with ca, if you don't mind, since it already exists [2009-10-26 17:17:30] mikejoconnor: are we ranking items? [2009-10-26 17:17:33] we have to upgrade it, and write unit tests [2009-10-26 17:17:39] mikejoconnor: or just assigning a number... [2009-10-26 17:17:45] mikejoconnor: meaning two tasks can have the same number [2009-10-26 17:17:46] score [2009-10-26 17:17:47] rszrama: just assigning a number [2009-10-26 17:17:51] correct [2009-10-26 17:17:52] ok, thought so [2009-10-26 17:17:55] we are scoring the tasks [2009-10-26 17:18:20] Re: CA and Testing... it'll be impossible to have full test coverage w/o modules defining entities, triggers, etc. [2009-10-26 17:18:22] ahh [2009-10-26 17:18:23] however [2009-10-26 17:18:30] there are core entities, actions, conditions [2009-10-26 17:18:50] so with ca, I would say that each of those are a 1, however there are a few patches in the queue we might want to evaluate, so I 'll say that the port is actually a 2, and the testing is a 2, because we need to write some example entities, conditions, and actions [2009-10-26 17:19:23] both are relatively easy, but not something that I could do in the bathtub. [2009-10-26 17:19:30] I'm making testing a part of the ticket, FYI. [2009-10-26 17:19:42] my tub looses heat rather quickly :) [2009-10-26 17:19:53] mine isn't comfortable [2009-10-26 17:20:10] tighten down the heat sink then [2009-10-26 17:20:25] I think the heat sink is "surface area." :P [2009-10-26 17:20:40] LOLz. Ok, I think we've confirmed that CA port is something around a 3? [2009-10-26 17:20:50] I think that sounds fair [2009-10-26 17:21:01] And Products may be too much and should be broken down further? [2009-10-26 17:21:03] ok, should that now be our point of reference for other tasks? [2009-10-26 17:21:05] yeah [2009-10-26 17:21:06] so now we have a benchmark [2009-10-26 17:21:21] what all is involved in TAPIr? [2009-10-26 17:21:25] if CA is a 3, then TAPIr would be a 2 [2009-10-26 17:21:28] But DamZ is idle, so there's likely going to be conversation again.. [2009-10-26 17:21:53] -->| thill (n=tim@c-98-243-237-10.hsd1.mi.comcast.net) has joined #d7uc [2009-10-26 17:22:02] amye: Its quite late in europe [2009-10-26 17:22:03] i.e. the tables api is easier than porting ca [2009-10-26 17:22:13] Bojhan: damz doesn't sleep :) [2009-10-26 17:22:16] TAPIr can just be ported as is... it sounded like DamZ wanted to propose some changes, and after davidstrauss's comment, I couldn't gather whether it should be a standalone module or not :D [2009-10-26 17:22:23] Bojhan: Yeah, we know better than that. ;) [2009-10-26 17:22:33] well, still - one can dooze off :) [2009-10-26 17:22:36] rszrama: so there's still some discussion to have [2009-10-26 17:22:40] |<-- davidstrauss has left freenode (Read error: 104 (Connection reset by peer)) [2009-10-26 17:22:52] hehe [2009-10-26 17:22:53] which adds a bit to the complexity [2009-10-26 17:23:12] * Bojhan has to go trough security checks, brb 5 minutes [2009-10-26 17:23:14] can we put Tapir at 3 and CA at 4? :P [2009-10-26 17:23:17] heh [2009-10-26 17:23:17] however Damz has also worked some on his core patch [2009-10-26 17:23:26] -->| davidstrauss__ (n=davidstr@wikimedia/davidstrauss) has joined #d7uc [2009-10-26 17:23:27] Sure [2009-10-26 17:23:53] so that brings us to products [2009-10-26 17:24:11] the product entry field will be the most complex part [2009-10-26 17:24:24] that can easily be broken down into several pieces [2009-10-26 17:24:30] Ideally you don't want to have a feature above 8, so should we break this down into sub-feature? [2009-10-26 17:24:34] cool [2009-10-26 17:24:38] Ok. 1) A fieldable product entity. 2) A UI to define bundles of that entity. [2009-10-26 17:24:44] adding fields to products is almost trivial, so that's a 1, I think [2009-10-26 17:24:54] 2) Views integration for the core entity. [2009-10-26 17:24:56] erm [2009-10-26 17:24:57] that was a 3 [2009-10-26 17:25:14] IslandUsurper: would that be wrapped up in #2? [2009-10-26 17:25:23] more like 1 [2009-10-26 17:25:30] ahh, duh [2009-10-26 17:25:33] -->| davidstrauss (n=davidstr@wikimedia/davidstrauss) has joined #d7uc [2009-10-26 17:25:39] because the Views integrations is mostly taken care of by the fields on the product [2009-10-26 17:25:48] only the product_id is left [2009-10-26 17:25:53] but not the core entity items -> SKU, Title, Price [2009-10-26 17:26:00] hmm [2009-10-26 17:26:06] how can we have a default price without a price object? :P [2009-10-26 17:26:14] I've been wondering about that [2009-10-26 17:26:33] "Why is that marked as a priority 2 when products are 1?" [2009-10-26 17:26:38] well, let's do it anyways - a default price would assume default currency settings [2009-10-26 17:26:50] heh [2009-10-26 17:27:04] So, to not confuse issues with scoring, we have: [2009-10-26 17:28:00] A. Fieldable product entity (incl. the entity table and Views integration). B. Making bundles of said fields. C. A product entry field of some sort... [2009-10-26 17:28:19] I feel C really needs to be defined better - I don't understand a product entry field that doesn't operate as an add to cart field [2009-10-26 17:28:46] mostly, it loads the product into the other entity [2009-10-26 17:28:57] ok, so it would be an add to cart field w/ no display? [2009-10-26 17:29:04] not much [2009-10-26 17:29:13] eh? [2009-10-26 17:29:17] Oof. Which of these things do we want to be tickets? [2009-10-26 17:29:33] A and B for sure [2009-10-26 17:29:35] er. hm [2009-10-26 17:29:39] C needs to be clarified [2009-10-26 17:30:10] ok, how about this [2009-10-26 17:30:11] (tapir evaluation looks good for me) [2009-10-26 17:30:41] damz: And CA? [2009-10-26 17:30:51] amye: all good [2009-10-26 17:30:53] a field can be displayed for edit (how this is done is determined by its widget?) and displayed for viewing (how this is done is determined by a display handler?) [2009-10-26 17:30:53] the product entry field can have the themed products as part of its display. The other part is the add to cart form [2009-10-26 17:31:07] but what is a themed product? [2009-10-26 17:31:17] that depends entirely on its fields [2009-10-26 17:31:47] it depends on the "product entry" formatter [2009-10-26 17:31:50] it doesn't have to be anything in particular [2009-10-26 17:31:51] so, we're talking the product entry field should do something like embedding a node in a node? [2009-10-26 17:31:52] and on the "products" fields [2009-10-26 17:31:55] the formatter [2009-10-26 17:31:56] ok [2009-10-26 17:32:03] so, we don't have to target every conceivable formatter for this sprint [2009-10-26 17:32:08] DamZ: Fields UI has no Formatter UI? [2009-10-26 17:32:09] certainly not [2009-10-26 17:32:19] @rszrama [2009-10-26 17:32:20] rszrama: basically yes, the product entry formatter will embed products [2009-10-26 17:32:39] formatters will be specific to their use case [2009-10-26 17:32:39] DamZ: ok, I just hadn't conceived of this use case when we were sprinting [2009-10-26 17:32:51] |<-- davidstrauss__ has left freenode (Read error: 145 (Connection timed out)) [2009-10-26 17:32:53] ie. the simple product, the customized product, the product kit, etc. [2009-10-26 17:32:58] all those are different formatters [2009-10-26 17:33:13] the field widget, on the other hand, is more the "back-office configuration form" [2009-10-26 17:33:16] and "product display"? [2009-10-26 17:33:17] of the formatter [2009-10-26 17:33:29] rszrama: that's the same thing for me [2009-10-26 17:33:35] rszrama: we just need to agree on one term [2009-10-26 17:33:52] how do you have a formatter that can _either_ display a product _or_ present a form or link to add the item to the cart? [2009-10-26 17:33:52] we have a "field" that you can attach to nodes that: [2009-10-26 17:33:57] would that not be two separate formatters? [2009-10-26 17:34:17] rszrama, it could be a checkbox in the widget "Display add to cart form" [2009-10-26 17:34:20] (1) has a "widget" that allow you to list products and configure the formatter [2009-10-26 17:34:35] (2) has a "formatter" that display the product and the add to cart form [2009-10-26 17:34:40] IslandUsurper: that's just not the way it works right now, tho :-/ [2009-10-26 17:34:50] rszrama: you specify the display type when you build a node type [2009-10-26 17:35:10] there are several types of "formatters", depending on what you want [2009-10-26 17:35:14] ok [2009-10-26 17:35:20] can I get a correlation from existing CCK fields? [2009-10-26 17:35:39] or are we talking about something unique here? [2009-10-26 17:35:46] rszrama: imagefield and derivative-specific image formatters [2009-10-26 17:36:07] rszrama: ie. "imagefield" and "display a 100x100 thumbnail in the full node page view" [2009-10-26 17:36:24] "imagefield" is the field/widget, "display a 100x100 thumbnail in the full node page view" is the formatter [2009-10-26 17:36:29] DamZ: right, so would imagefield in one formatter let you either view the image or provide a download link through a checkbox selection on the node edit form? [2009-10-26 17:36:36] you can pick different formatters based on the node build types [2009-10-26 17:36:49] rszrama: no, it's a per node-type configuration [2009-10-26 17:37:04] but, you can specify the alt attribute per node [2009-10-26 17:37:08] I feel like you're confirming why I've been saying what we're describing isn't tenable [2009-10-26 17:37:30] if you don't put in a value for alt, it doesn't get in the HTML [2009-10-26 17:37:31] IslandUsurper: that still has to do with rendering an image tag [2009-10-26 17:37:42] IslandUsurper: not rendering an image tag vs. rendering a download linnk [2009-10-26 17:38:01] rszrama: why would you want that? [2009-10-26 17:38:42] DamZ: I don't. :P That's just my correlation for having an option to present either a themed product or an add to cart form through one formatter... [2009-10-26 17:38:46] rszrama, doesn't mean it couldn't be done that way [2009-10-26 17:39:08] rszrama: it's probably two different formatters [2009-10-26 17:39:23] (and for me, the add to cart form *is part* of the product) [2009-10-26 17:39:35] DamZ: so how is having a separate formatter for an add to cart form vs. a themed product display different? [2009-10-26 17:40:02] am I totally missing something here? [2009-10-26 17:40:39] rszrama: I'm not sure where is the misunderstanding here [2009-10-26 17:41:01] So, I create a product bundle and add some fields to it. Then I create a product node type and add a product display field to that node type. When I add that field, I have to specify how it's going to display the product data on the node. [2009-10-26 17:41:21] At that point, I say whether it will display an add to cart form or a full rendering of the product, right? [2009-10-26 17:41:36] Meaning I can't have one product display node type that can do either / or per node instance. [2009-10-26 17:41:46] is that all correct? [2009-10-26 17:42:06] you can do that on a per-node-build-type [2009-10-26 17:42:14] ie. teaser vs. full node vs. rss [2009-10-26 17:42:27] I'm not sure we need that to be per node instance [2009-10-26 17:42:35] That's the way it is now. I add an imagefield to a node type and specify it's going to be displayed using imagecache preset XXX on every instance of that node. No overriding it per node. [2009-10-26 17:42:47] that's basically the same idea [2009-10-26 17:42:50] Ok. I feel like IslandUsurper was talking about per node instance, and you were corroborating him. [2009-10-26 17:42:58] if that's not the case, then I just misunderstood Lyle [2009-10-26 17:43:02] Stock modules will want to disable the add to cart button for out of stock products, though [2009-10-26 17:43:15] we don't want per-node instance stuff [2009-10-26 17:43:16] IslandUsurper: then they'd override the add to cart form, right? [2009-10-26 17:43:18] as less as possible [2009-10-26 17:43:33] we don't want to replicate the "attributes per product instance" nightmare [2009-10-26 17:43:40] IslandUsurper: fwiw, a cart link can be displayed through a form [2009-10-26 17:43:52] my current thinking is that the stock module could define a overriden formatter [2009-10-26 17:43:53] what is that worth? [2009-10-26 17:44:03] like "shippable product" formatter [2009-10-26 17:44:06] |<-- davidstrauss has left freenode () [2009-10-26 17:44:09] IslandUsurper: a stock module could override that form to not show the cart link if it's out of stock [2009-10-26 17:44:33] IslandUsurper: though I guess since we're using the Fields API, they could just use hook_nodeapi() [2009-10-26 17:45:21] DamZ: So, what we need is a product display field and some formatters? [2009-10-26 17:45:21] actually, for stock, it's more per-product than per-node [2009-10-26 17:45:31] IslandUsurper: oof, good call [2009-10-26 17:45:46] DamZ: One formatter might simply list products, another would display an add to cart form? [2009-10-26 17:46:02] rszrama: we will have to figure that out [2009-10-26 17:46:06] ok guys/gals, I need to take off. I promised my wife I was going to leave 15 minutes ago [2009-10-26 17:46:07] rszrama: I'm not completely sure [2009-10-26 17:46:25] yeah, we have to get the other stuff done first anyway. We can work on it later [2009-10-26 17:46:42] Ok, but is it clear where we were differing, IslandUsurper? [2009-10-26 17:46:51] or were you not ever thinking per node formatter? [2009-10-26 17:47:12] Can someone email me the breakdown of products, and the score? [2009-10-26 17:47:22] no, I wasn't. I was thinking of a widget setting that affected the way the formatter worked. which is, indeed, a bad idea [2009-10-26 17:47:29] mikejoconnor: 24 - 21, Cardinals - Giants [2009-10-26 17:47:34] that's to everyone who came [2009-10-26 17:47:35] Rszrama: You think you have that one? [2009-10-26 17:47:42] <--| mikejoconnor has left #d7uc [2009-10-26 17:47:43] amye: have what one? [2009-10-26 17:47:56] rszrama: Breakdown of 'product' and scores? [2009-10-26 17:47:59] ahh, sure [2009-10-26 17:48:01] ok [2009-10-26 17:48:09] so, amye, did you get tickets A and B above? [2009-10-26 17:48:12] rszrama: I did. [2009-10-26 17:48:19] I was waiting around to see what happened with C. [2009-10-26 17:48:21] Lyle's going to be spearheading those, and I think Bojhan will be a good resource re: UI implementation [2009-10-26 17:48:32] for C, at the very least, we can define a product display field [2009-10-26 17:48:36] Yhea, anything that involves UI, just ping me [2009-10-26 17:48:48] for now, we won't have all the formatters - we don't have a cart anyways, so an add to cart formatter isn't necessary [2009-10-26 17:48:59] with at least 3 formatters: simple product with set variations (color, size), customizable product, and product kits [2009-10-26 17:49:03] rszrama: I will try working on the Products listing page, just to get an idea of what we have, and I worked on the IA - but it requires more thourough review of you guys [2009-10-26 17:49:09] it can be a postponed task [2009-10-26 17:49:13] Bojhan: awesome [2009-10-26 17:49:24] Bojhan: admin products listing or customer? [2009-10-26 17:49:46] rszrama: admin, I am not doing any customer - untill in the last sprints? [2009-10-26 17:49:59] I don't have much on my plate, atm, so I volunteer for fleshing out the "Product display field" in the docs and get some code rolling if it gets that far [2009-10-26 17:50:21] Bojhan: ok, great; yeah, customer facing stuff is largely different on a store-by-store basis... it'll most likely just be some default View [2009-10-26 17:50:40] rszrama: right [2009-10-26 17:51:26] IslandUsurper: DamZ: I'll start by summarizing the discussion above and actually correlating user stories to CCK components [2009-10-26 17:51:41] i.e. if you want to list a product on a node, you'll add this field and use this formatter... [2009-10-26 17:51:59] amye: I'm not sure that needs a ticket, per se, unless we're using tickets for general project management? [2009-10-26 17:52:22] rszrama: We might as well. As we did want to keep the docs updated too, that's a task. [2009-10-26 17:52:26] kk [2009-10-26 17:52:29] rszrama: So where do I post stuff I want feedback upon? [2009-10-26 17:52:43] Bojhan: are you thinking mock-ups? [2009-10-26 17:52:56] rszrama: yes, and just wireframes/thoughts [2009-10-26 17:53:02] rszrama: sounds good [2009-10-26 17:53:08] rszrama: We'll also want to have the discussion about d7 straight port. [2009-10-26 17:53:36] amye: ahh, yeah, you can make that a task and I'll self-assign [2009-10-26 17:53:46] amye: that and getting a sticky announcement on d7uc.org on uc.org [2009-10-26 17:54:01] Great. Thanks! [2009-10-26 17:54:12] Off for a meeting, back again soon. [2009-10-26 17:54:25] Bojhan, I'd put them in the d7uc forums. Brainstorming or something [2009-10-26 17:54:27] Bojhan: hmm, so, what feeling do you have about using Picture nodes on d7uc.org? I'm thinking there we can have comments on the mock-ups, easy linkage through docs... [2009-10-26 17:54:34] wow - this is a very well coordinated effort [2009-10-26 17:54:52] Bojhan: you can use a tag, and it will organize it into an image gallery like this: http://d7uc.org/taxonomy/term/7 [2009-10-26 17:54:53] rszrama: That sounds fine, as long as people actually see it. [2009-10-26 17:55:06] Bojhan: ok, I'll make sure it's given attention [2009-10-26 17:55:10] gusaus: thanks :) [2009-10-26 17:55:16] rszrama: Ok, sure [2009-10-26 17:55:27] Bojhan: I think Top Notch Themes should be good "feedback"ers [2009-10-26 17:55:36] heh, I feel like that should be a football position :P [2009-10-26 17:55:53] rszrama: yhea, but best feedback is from you guys. [2009-10-26 17:55:57] ok, I'm going to head out, so I'll post the logs that I have up later tonight. [2009-10-26 17:56:01] Bojhan: I'll be there with bells on. :) [2009-10-26 17:56:05] IslandUsurper: awesome, thanks! [2009-10-26 17:56:06] cool [2009-10-26 17:56:33] hmm, dunno why I didn't turn logging on :P [2009-10-26 17:56:35] duh [2009-10-26 17:57:15] for info, drupalfr is logging this channel now [2009-10-26 17:57:25] ahh, ok, great [2009-10-26 17:57:26] http://bot.drupalfr.org/bot/log/d7uc [2009-10-26 17:57:33] |<-- amye has left freenode (Remote closed the connection) [2009-10-26 17:57:35] access denied [2009-10-26 17:57:38] rszrama: at some point in the very near future, I think this drupal learning group could help w/ this effort - http://drupalkata.com/ [2009-10-26 17:57:38] rszrama: could you autovoice drupalfr? [2009-10-26 17:57:59] -->| davidstrauss (n=davidstr@wikimedia/davidstrauss) has joined #d7uc [2009-10-26 17:58:00] rszrama: fixed permissions [2009-10-26 17:58:05] gusaus: great - should get us exactly the kind of feedback we'll need on how all this stuff "works" :) [2009-10-26 17:58:08] DamZ: autovoice? [2009-10-26 17:58:46] that's good. I can't figure out where my log file was saved [2009-10-26 17:59:03] ummm... drupalfr didn't come in for 30 minutes after conversation started :P [2009-10-26 17:59:12] rszrama: /msg ChanServ FLAGS irc://irc.freenode.net/#food7uc drupalfr V [2009-10-26 17:59:14] yeah, but I did post a backlog [2009-10-26 17:59:20] ahh, yeah [2009-10-26 17:59:25] oups [2009-10-26 17:59:38] I meant /msg ChanServ FLAGS irc://irc.freenode.net/#food7uc member:drupalfr V [2009-10-26 17:59:40] grr [2009-10-26 17:59:42] hehe [2009-10-26 17:59:51] silly clients using an HTML canvas ;) [2009-10-26 18:00:07] so /msg ChanServ FLAGS #d7uc drupalfr V [2009-10-26 18:00:20] (at last) [2009-10-26 18:00:20] * Bojhan has a quick question [2009-10-26 18:00:25] Would products have a type? [2009-10-26 18:00:40] what do you mean? [2009-10-26 18:00:43] like [2009-10-26 18:01:05] Clothing, Technology, Building [2009-10-26 18:01:25] ahh, product would be generic, but you'd bundle it into product types [2009-10-26 18:01:33] Bojhan: yes, product will probably have a type [2009-10-26 18:01:47] Bojhan: each type has a different set of fields [2009-10-26 18:01:50] Or is SKU - Title - - Price - Operations enough, I imagined having a type would be usefull information [2009-10-26 18:02:00] on products listing page [2009-10-26 18:02:06] I guess we'd ship with a generic product type? [2009-10-26 18:02:14] rszrama: that would be a good idea