*** tpb has joined #melange | 00:00 | |
*** madrazr has left #melange | 00:31 | |
*** madrazr has joined #melange | 00:51 | |
*** dmitrig01|afk has quit IRC | 02:03 | |
*** mithro_ has quit IRC | 03:36 | |
*** mithro_ has joined #melange | 04:33 | |
*** ChanServ sets mode: +v mithro_ | 04:33 | |
*** Lennie has joined #melange | 04:51 | |
*** madrazr has quit IRC | 05:03 | |
*** Lennie has quit IRC | 05:57 | |
*** lisppaste9 has quit IRC | 07:31 | |
*** lisppaste9 has joined #melange | 07:31 | |
*** MatthewWilkes has joined #melange | 11:13 | |
*** madrazr has joined #melange | 11:59 | |
*** madrazr is now known as madrazr|oota | 12:03 | |
*** madrazr|oota has quit IRC | 12:31 | |
*** Lennie has joined #melange | 13:20 | |
*** solydzajs has joined #melange | 13:27 | |
*** tlarsen has joined #melange | 13:28 | |
*** ChanServ sets mode: +o tlarsen | 13:28 | |
solydzajs | tlarsen: hi | 13:30 |
---|---|---|
Lennie | hi solydzajs and tlarsen :) | 13:30 |
solydzajs | tlarsen: IRC meeting in 30 minutes :-) | 13:30 |
solydzajs | Hi Lennie | 13:30 |
solydzajs | recent Sverre's commits messed up things a little bit , I have couple commits queued up with fixes | 13:31 |
tlarsen | solydzajs: Good afternoon (evening). | 13:33 |
Lennie | hehe he wrecked it did he solydzajs? | 13:34 |
solydzajs | tlarsen: how are you ? How is Linkable going ? | 13:34 |
solydzajs | I really don't like some of his changes | 13:34 |
solydzajs | tlarsen: did you look at Sverre's recent commits ? | 13:34 |
tlarsen | I am wading through everything. | 13:36 |
tlarsen | Monday mornings usually get completely absorbed by my construction project. :( | 13:36 |
solydzajs | ah ok. | 13:36 |
solydzajs | Like I said I will fix couple things in his recent commits | 13:37 |
tlarsen | solydzajs: That is fine. | 13:37 |
tlarsen | I am trying to work out how to take a URL suffix like google/gsoc2009/asf/foobar and get back to the "foobar" entity. | 13:38 |
solydzajs | Invitation is also almost working, we need to add invitation email sending, and User Roles view | 13:38 |
solydzajs | ah scope thingy ? | 13:38 |
*** SRabbelier has joined #melange | 13:38 | |
*** ChanServ sets mode: +v SRabbelier | 13:38 | |
tlarsen | Yes. | 13:38 |
tlarsen | "foobar" in that example is not unique all by itself. | 13:38 |
tlarsen | So, a query of objects with Linkable.id == "foobar" returns all of them. | 13:38 |
solydzajs | We have 4 days left till Friday, I would like to know what we are aiming for to present to CHris on Monday, suggestions ? | 13:39 |
tlarsen | Then, you have to take those, and see if their "scope" points to something with a Linkable.id of "asf", and then "gsoc2009", etc. | 13:39 |
tlarsen | I want to get the static Terms of Service stuff implemented before then. | 13:39 |
tlarsen | I will also get the Linkable stuff finished, but he won't see that. | 13:39 |
tlarsen | Unless it has changed recently, I really *don't* like the Home Settings form. It is very non-intuitive. | 13:40 |
tlarsen | Also, as part of the Linkable changes, I will need to create a two-form "User profile wizard" that asked for the "Public Name" first, and then suggests a Linkable.id. | 13:40 |
tlarsen | (since we are making Linkable.id immutable) | 13:40 |
solydzajs | yep true | 13:41 |
solydzajs | SRabbelier: when do you plan to commit edit_self fix ? | 13:41 |
SRabbelier | solydzajs: meh, turns out I was retarded and was using the original code :( | 13:42 |
SRabbelier | tlarsen: I mailed you about Site Settings -_-" | 13:42 |
solydzajs | SRabbelier: ok so it's not fixed | 13:42 |
SRabbelier | solydzajs: I know what's wrong though | 13:43 |
SRabbelier | solydzajs: it requires e-mail as a field :) | 13:43 |
SRabbelier | solydzajs: but it never passes it along ;) | 13:43 |
SRabbelier | solydzajs: nor shows it | 13:43 |
SRabbelier | solydzajs: so you don't see an error | 13:43 |
SRabbelier | solydzajs: so I can fix it, but it'll take a while; I'll do it after invites are done | 13:43 |
SRabbelier | tlarsen: it's fixed now where you don't have to fill in the partial_path/link_name for the site settings, only for the document | 13:44 |
SRabbelier | tlarsen: if you want it with a select thingy, I can make it where you get redirected to the document list view; like how invites work curerntly | 13:44 |
SRabbelier | oh, and hi all :) | 13:44 |
tlarsen | SRabbelier: OK, I am still merging from all of the changes over the weekend. I will take a look at the new functionality today. | 13:44 |
SRabbelier | tlarsen: good luck with that; merging can be hell | 13:44 |
tlarsen | SRabbelier: Yes, we need to be able to select the Document from existing ones, not know about details like partial_path and link_name. | 13:44 |
solydzajs | SRabbelier: ok invites first I agree | 13:45 |
tlarsen | OK, I will: finish the Linkable change (Chris won't notice...), write a two-step User profile wizard, and work on the site-wide Terms of Service. | 13:46 |
tlarsen | I think those three are going to keep me busy all week. | 13:46 |
SRabbelier | tlarsen: user profile wizard? | 13:46 |
tlarsen | Yes, the first form would ask them for their "Public Name" and contain a *detailed* explanation of what it is, how it is used on the site, etc. | 13:48 |
solydzajs | tlarsen: Ok I will fix couple thing in Sverre's recent commits and make sure that all the current functionality works correctly, including former ids etc. | 13:48 |
SRabbelier | solydzajs: awesome | 13:48 |
tlarsen | The second form would then suggest a Linkable.id and also let them know that *the ID cannot be changed once it is saved*. | 13:48 |
solydzajs | tlarsen: we can have it on one page, just JavaSciprt can propose link id based on values in Public Name what do you think ? | 13:49 |
SRabbelier | so we'll have that just be an admin feature? | 13:49 |
tlarsen | I am not a Javascript programmer. | 13:49 |
SRabbelier | tlarsen: we have dmitri for that ;) | 13:49 |
tlarsen | Besides, I think this is important enough that it needs to be *two* steps. | 13:49 |
tlarsen | They should not see the ID field until they have entered some sort of Public Name. | 13:49 |
solydzajs | tlarsen: ok | 13:49 |
SRabbelier | tlarsen: why do they need to not see it? | 13:49 |
tlarsen | Let's just ask them for a Public Name (after carefully explaining what it is for), then have a Next> button that takes them to the form showing the suggested Linkable.id that was created from their Public Name entered on the previous form. | 13:50 |
tlarsen | I want to make it more like a "sign-up" process of sorts. | 13:50 |
solydzajs | ok will you create any entity after first step ? | 13:50 |
solydzajs | or entity will be created only after full signup ? | 13:51 |
tlarsen | solydzajs: No. I will forward the Public Name to the second form as a hidden parameter or something. | 13:51 |
tlarsen | solydzajs: I haven't exactly worked out how to implement it. | 13:51 |
tlarsen | solydzajs: We can't create a User entity without a Linkable.id. | 13:51 |
tlarsen | The entity is only created in the Datastore once we have a valid and unique (for User entities) Linkable.id and a "valid" Public Name (whatever that means for Public Names, probably not much...). | 13:52 |
SRabbelier | ok, so that means I can drop my work on edit_self altogether | 13:52 |
SRabbelier | if you're gonna replace it with a wizard in the first place | 13:53 |
tlarsen | SRabbelier: Why, what is edit_self? | 13:53 |
SRabbelier | tlarsen: replacement for ugly the /user/edit code we have atm (remnant from long forgotten ages :P) | 13:53 |
tlarsen | You should keep existing features functioning, in case I can't get this to work. | 13:53 |
SRabbelier | tlarsen: the old code is still in place | 13:53 |
SRabbelier | I'm just not going to try and fix the generic replacement | 13:53 |
tlarsen | OK, as long as the old code still works, then, yes, you can stop working on edit_self. | 13:53 |
tlarsen | For the User entity in particular, I think generic is *not* the way to go. | 13:54 |
SRabbelier | for the admin part we should | 13:54 |
SRabbelier | for the part the user sees | 13:54 |
SRabbelier | sure | 13:54 |
SRabbelier | that could do with some tailoring | 13:54 |
tlarsen | It is the first place where we ask Users to enter information on the site, so it should have lots of hand-holding and be used as an opportunity to educate about "unique IDs". | 13:54 |
tlarsen | SRabbelier: Yes, feel free to make the Developer view generic. | 13:55 |
SRabbelier | tlarsen: they already are | 13:55 |
* SRabbelier buff | 13:55 | |
Lennie | ello SRabbelier | 13:56 |
SRabbelier | Lennie: heya :) | 13:56 |
solydzajs | ok so I guess we've discussed everything | 13:59 |
solydzajs | any questions ? | 13:59 |
tlarsen | Nope. | 13:59 |
SRabbelier | solydzajs: what will you be doing? :) | 14:00 |
SRabbelier | and what will we be demo-ing for Chris? | 14:00 |
solydzajs | SRabbelier: fixing what have broken :P | 14:00 |
SRabbelier | solydzajs: ok :) | 14:00 |
solydzajs | what you have broken :-) | 14:00 |
solydzajs | :D | 14:00 |
SRabbelier | :( | 14:00 |
tlarsen | So, what will we be demoing? | 14:00 |
tlarsen | Invites? Are these Host invites only? | 14:00 |
SRabbelier | tlarsen: they are atm, but it's like, 20 lines of code to add it for another type | 14:01 |
tlarsen | SRabbelier: except that we don't have any other type at the moment, correct? (not without the Club stuff, anyway). | 14:01 |
Lennie | + Mailing templates are easy :) | 14:01 |
solydzajs | I hope to have Host invitations and profiles working till Friday, SRabbelier you think it;s doable ? | 14:01 |
SRabbelier | solydzajs: mhhh.. I can try :) | 14:02 |
SRabbelier | solydzajs: depends on school | 14:02 |
solydzajs | SRabbelier: ok | 14:02 |
tlarsen | We need to have *something* Chris can actually *do* on the site besides create a User profile (again). :) | 14:02 |
SRabbelier | we can already create invites anwyay | 14:02 |
solydzajs | SRabbelier: I want to have all the current functionality working | 14:02 |
SRabbelier | solydzajs: obviously :) | 14:02 |
tlarsen | By the way, the Linkable changes *will* require you to empty your Datastore. :) | 14:02 |
SRabbelier | that's np | 14:03 |
SRabbelier | well, the sidebar is a lot cleaner now, that should count ;) | 14:03 |
tlarsen | Hopefully we won't have any more major incompatible schema changes like this again. | 14:03 |
solydzajs | tlarsen: he has developer rights already so he will be able to do more stuff | 14:03 |
tlarsen | SRabbelier: Nicer? | 14:03 |
tlarsen | SRabbelier: It looks *really* cluttered to me. :) | 14:03 |
SRabbelier | tlarsen: yeah, I think it looks a lot more streamlined now | 14:03 |
SRabbelier | :-/ | 14:03 |
solydzajs | SRabbelier: :-) I'm not all +1 on your recent changes too :-) | 14:04 |
SRabbelier | I am :D | 14:04 |
solydzajs | But it's not only your decision | 14:04 |
SRabbelier | maybe it would be better if the menu's start out collapsed | 14:04 |
SRabbelier | solydzajs: ofcourse | 14:04 |
SRabbelier | solydzajs: feel free to change what you don't like | 14:04 |
tlarsen | SRabbelier: I think we should default with some of the menus closed. I wonder if Dmitri could make the sidebar menu state work. | 14:04 |
SRabbelier | tlarsen: that would help I think | 14:05 |
SRabbelier | so what don't you like about the new sidebar? | 14:05 |
SRabbelier | solydzajs: the global sidebar is how we discussed it would be earlier though | 14:05 |
SRabbelier | solydzajs: we are forced to have a global since Django works that way | 14:06 |
solydzajs | SRabbelier: you will see my commits | 14:06 |
SRabbelier | solydzajs: sure | 14:06 |
tlarsen | SRabbelier: I haven't looked at the way this is implemented, but I am curious. Did you incorporate some of the stuff where a Views class registers a callback that returns an entire sub-menu? | 14:08 |
SRabbelier | tlarsen: no, I just have it return the menu in a call atm | 14:08 |
SRabbelier | tlarsen: it's not dynamic (yet) | 14:08 |
SRabbelier | but it would be trivial to make it dynamic | 14:08 |
tlarsen | SRabbelier: So, here is my question: | 14:09 |
solydzajs | I hate when you say "trivial" :P | 14:09 |
SRabbelier | :D | 14:09 |
tlarsen | SRabbelier: each time the menu is displayed, is that method called to return the menu object? | 14:09 |
SRabbelier | my trivial is under a day ;) | 14:09 |
SRabbelier | non-trivial is like, a week :P | 14:10 |
solydzajs | SRabbelier: ye ye sure :-) | 14:10 |
SRabbelier | tlarsen: at the moment it's not | 14:10 |
SRabbelier | tlarsen: but that would actually be 2 minutes :P | 14:10 |
SRabbelier | tlarsen: I can do it right now :D | 14:10 |
tlarsen | SRabbelier: If I recall, that is the functionality we were going for. | 14:10 |
SRabbelier | tlarsen: yup | 14:10 |
SRabbelier | tlarsen: didn't think to :) | 14:10 |
tlarsen | SRabbelier: Each method that returns the menu structure could: | 14:10 |
SRabbelier | didn't have time to either | 14:10 |
SRabbelier | tlarsen: yeah, that's how itw orks atm | 14:10 |
SRabbelier | just they get called only once | 14:10 |
SRabbelier | (at load time) | 14:10 |
tlarsen | 1) return a static object once it was lazy-generated | 14:10 |
SRabbelier | tlarsen: yeah, it still can do all that now | 14:11 |
tlarsen | 2) build a sidebar sub menu every single time it was called | 14:11 |
tlarsen | 3) a mix of #1 and #2 | 14:11 |
SRabbelier | tlarsen: it's just nothing is doing that atm :) | 14:11 |
SRabbelier | tlarsen: that is,everything is doing 2, with the note it's only getting called once | 14:11 |
tlarsen | SRabbelier: Why is it only getting called once? | 14:12 |
tlarsen | SRabbelier: If it is a callback, it should be called every time the sidebar is displayed, no? | 14:12 |
SRabbelier | tlarsen: yes, but the sidebar is only being contstructed once is what I'm saying | 14:12 |
tlarsen | SRabbelier: I don't think that is correct. | 14:13 |
SRabbelier | tlarsen: its' not | 14:13 |
SRabbelier | tlarsen: but it works for now | 14:13 |
SRabbelier | tlarsen: as said, it is easy to fix it | 14:13 |
tlarsen | SRabbelier: The callbacks should be called every time the sidebar menu is going to be displayed. | 14:13 |
SRabbelier | just move the code into the function | 14:13 |
tlarsen | SRabbelier: OK, I look forward to seeing it. :) | 14:13 |
SRabbelier | it'll be after invites | 14:13 |
SRabbelier | it's not a show stiopper | 14:13 |
SRabbelier | s/sti/st/ | 14:14 |
tlarsen | OK, so are we done with the meeting? | 14:14 |
tlarsen | (I've got code to write :) | 14:14 |
SRabbelier | ok | 14:14 |
Lennie | Do we have lined out what Chris is going to be seeing? | 14:15 |
SRabbelier | hopefully working invites :) | 14:15 |
solydzajs | yep we are done | 14:15 |
solydzajs | He will see all the current admin and user functionality working | 14:15 |
tlarsen | Lennie: And a much nicer User profile creation wizard. | 14:16 |
solydzajs | so including invites and host hopefully | 14:16 |
solydzajs | + terms of service | 14:16 |
tlarsen | Lennie: And a Terms of Service feature. | 14:16 |
solydzajs | and new user wizard | 14:16 |
Lennie | k | 14:16 |
solydzajs | yep exactly ;-) | 14:16 |
SRabbelier | anything Lennie could do here? | 14:16 |
tlarsen | Lennie: (even if I have to implement the Terms of Service as a static form...) | 14:16 |
tlarsen | Lennie: My first pass at a Terms of Service is to make it possible to select a Document (that was created using the generic Document editor) and display it, along with an "I agree" check box. | 14:17 |
tlarsen | Initially, I am going to add this as a Property to the User entity (for now). | 14:17 |
Lennie | tlarsen: Some sort of quiz view right? | 14:17 |
tlarsen | I will refactor to that later. | 14:17 |
tlarsen | We *really* need a site-wide Terms of Service at this point. | 14:18 |
tlarsen | So, I've got to go eat lunch. Are we done? | 14:18 |
SRabbelier | sure | 14:18 |
solydzajs | yep we are done | 14:18 |
solydzajs | thx for the meeting | 14:18 |
solydzajs | I will schedule next one for Friday | 14:18 |
SRabbelier | ok | 14:19 |
Lennie | solydzajs: I'm out for Friday but dont let that stop you :D | 14:19 |
solydzajs | Lennie: ok | 14:19 |
solydzajs | Will catch you later guys | 14:19 |
solydzajs | see you | 14:19 |
SRabbelier | solydzajs: cheers | 14:20 |
Lennie | bb | 14:20 |
tlarsen | Oh, I have one more thing I was thinking about. solydzajs, have you got a second (and anyone else who wants to listen). | 14:20 |
SRabbelier | tlarsen: sure, go ahead | 14:20 |
solydzajs | sure | 14:20 |
tlarsen | I am thinking that site-wide stuff needs to be "scoped" to some sort of entity. | 14:20 |
tlarsen | The current candidate is the SiteSettings entity. | 14:20 |
SRabbelier | tlarsen: what other site-wide stuff do we have? | 14:20 |
tlarsen | I want to have the SiteSettings Linkable.id be fixed to "site". | 14:20 |
SRabbelier | tlarsen: it already is | 14:21 |
tlarsen | Several: | 14:21 |
tlarsen | "I agree" Question | 14:21 |
tlarsen | "Terms of Service" Quiz | 14:21 |
tlarsen | "Site Home Page" Document | 14:21 |
SRabbelier | ah, like that | 14:21 |
SRabbelier | sure | 14:21 |
tlarsen | I need some where to "root" them. | 14:21 |
SRabbelier | tlarsen: sure, go ahead | 14:21 |
SRabbelier | tlarsen: good a place as any | 14:22 |
solydzajs | everything should be in SiteSettings ? | 14:22 |
tlarsen | The restructuring would rename SiteSettings to just Site, and make it a Group. Then, I would eliminate HomeSettings and put that into Group. | 14:22 |
solydzajs | I guess SiteSettings is the best place for that | 14:22 |
solydzajs | since we will also have Terms of Service for each program right ? | 14:22 |
SRabbelier | tlarsen: wait wait | 14:22 |
SRabbelier | tlarsen: why does it need to be a group? 0.o | 14:22 |
tlarsen | I don't like the separate "Settings" classes. A Group has a home page, not a "Group HomeSettings". | 14:23 |
solydzajs | Group has way too many fields that shouldn't be included in Settings | 14:23 |
tlarsen | solydzajs: Hmmm. | 14:23 |
Lennie | But the current homesettings is ambigious if you ask me | 14:24 |
tlarsen | All of the groups (Clubs, Organizations, Sponsors) have home pages. Why should we have a parallel settings entity hierarchy? | 14:24 |
SRabbelier | tlarsen: I think group should just have a reference to HomeSettings | 14:24 |
tlarsen | OK, fine. | 14:24 |
SRabbelier | tlarsen: they don't need to have their own entity :-/ | 14:24 |
SRabbelier | tlarsen: why can't they all make do with just HomeSettings | 14:24 |
tlarsen | But, there isn't much that goes into a "Site" object (like there is with a "Group"). | 14:24 |
Lennie | or atleast not intuitive :) | 14:24 |
SRabbelier | tlarsen: wat bedoel je? | 14:25 |
Lennie | lol @ dutch :P | 14:25 |
tlarsen | Here is the problem I have: HomeSettings and SiteSettings are orphans. I need to be able to attach ("scope") all sorts of things to the site, but SiteSettings would be a lame place to do so. | 14:25 |
tlarsen | I don't have Organization Documents "scoped" to their HomeSettings entity. That would be silly. | 14:25 |
solydzajs | If you make Site a Group, what about all the not needed fields there ? | 14:25 |
SRabbelier | fail | 14:26 |
SRabbelier | tlarsen: what do you mean? :P | 14:26 |
tlarsen | Organizations own Documents (and Quizzes and Questions) and have members (Mentors), Clubs do the same, etc. | 14:26 |
SRabbelier | tlarsen: organization documents should be scoped to their organization ofcourse | 14:26 |
tlarsen | Why should a SiteSettings object own the site's Documents and Developers? | 14:26 |
SRabbelier | solydzajs: site should defnitly not be a group | 14:26 |
tlarsen | That seems weird. | 14:26 |
tlarsen | Then we need *some* Model class that both Site and Group *are*. | 14:27 |
tlarsen | (a common base class) | 14:27 |
SRabbelier | no... why? | 14:27 |
tlarsen | Also, why is a Site not a group? It "owns" Documents and has members (Developers). | 14:27 |
solydzajs | Linkable ?;-) | 14:27 |
SRabbelier | they have nothing in common? | 14:27 |
tlarsen | Why can't the Site have contact information? | 14:27 |
SRabbelier | well, yes, except Linkable ofcourse | 14:27 |
tlarsen | The more I think about it, the more I think Site *is* a Group. | 14:28 |
solydzajs | tlarsen, and what do you want to put in address fields for Site ? | 14:28 |
SRabbelier | tlarsen: it's a model with containing side wide settings | 14:28 |
SRabbelier | tlarsen: it's not even close to being a group :-/ | 14:28 |
tlarsen | solydzajs: Yes, I think there needs to be some parent class of Group that omits the address stuff. | 14:28 |
tlarsen | solydzajs: Maybe Owner or something. | 14:28 |
tlarsen | Owner <- Group | 14:28 |
tlarsen | Owner <- Site | 14:28 |
tlarsen | Owner <- Program | 14:29 |
solydzajs | What kind of fields will be in Owner model ? | 14:29 |
SRabbelier | tlarsen: errr, but... Owner == Linkable | 14:29 |
tlarsen | solydzajs: back references to Documents and Role. | 14:29 |
solydzajs | I mean properties | 14:29 |
SRabbelier | tlarsen: Linkable has that | 14:29 |
tlarsen | SRabbelier: No, Owner != Linkable | 14:29 |
SRabbelier | tlarsen: through the scope back reference | 14:29 |
tlarsen | SRabbelier: Linkable is *just* the id and scope. Everything on the site can have that, regardless of whether they "own" Documents or have members. | 14:30 |
tlarsen | SRabbelier: Ugh, no. | 14:30 |
SRabbelier | tlarsen: define 'own' | 14:30 |
tlarsen | SRabbelier: I want to have named back-references for specific things. | 14:30 |
solydzajs | Why does Site need back reference to Role ? | 14:30 |
tlarsen | solydzajs: Sites have Developers. | 14:30 |
tlarsen | solydzajs: We hacked in Developers. | 14:30 |
SRabbelier | ... :-/ | 14:31 |
tlarsen | solydzajs: Just because we didn't figure out the parallelism that is in Site. | 14:31 |
solydzajs | tlarsen: true | 14:31 |
SRabbelier | tlarsen: why does a site need a developer? | 14:31 |
solydzajs | tlarsen: we need Developer Role anyway, and we need developers to fill in profile too | 14:31 |
tlarsen | SRabbelier: My point is that there are lots of "tuples" in Melange: | 14:31 |
tlarsen | (group, members) | 14:31 |
tlarsen | (group, documents) | 14:31 |
tlarsen | Where "group" is all sorts of things. | 14:32 |
SRabbelier | tlarsen: oh sure | 14:32 |
tlarsen | I'm just saying that the current schema "smells funny". | 14:32 |
SRabbelier | tlarsen: I told pawel that on the Melange meeting | 14:32 |
solydzajs | SRabbelier, we need Developers to fill in their profile, and they don't need to have any other Roles, just a Developer Role. | 14:32 |
SRabbelier | tlarsen: that it could be greatly simplified | 14:32 |
tlarsen | Here is what I am trying to figure out (and this is a discussion to figure stuff out, not a concrete proposal...): | 14:33 |
tlarsen | Programs have home pages (and other Documents), Groups (Organizations, Clubs, etc.) have home pages (and other Documents), and the Site has a home page (and other Documents, like the ToS). | 14:33 |
solydzajs | true | 14:33 |
tlarsen | Groups (Organizations, Clubs, etc.) have members (Mentors, Members, etc.). | 14:34 |
tlarsen | Groups (...) have administrators, too (Sponsors have Hosts, Organizations have Administrators, Clubs have Founders, etc.). | 14:34 |
tlarsen | Site does as well: Developers. | 14:34 |
SRabbelier | tlarsen: like that, ok, that is true | 14:35 |
solydzajs | true | 14:35 |
tlarsen | How is the stuff that is in HomeSettings not really part of, say, an Organization (its feed, its home page...) | 14:35 |
tlarsen | I'm not saying that a Program is a Group, since it doesn't have members. That is where the analogy breaks down. | 14:35 |
tlarsen | That is why I haven't just made *everything* a group. | 14:35 |
SRabbelier | tlarsen: it should at least be scoped under it | 14:35 |
solydzajs | ok | 14:35 |
SRabbelier | so basically we have 'bukits' and 'items' | 14:36 |
solydzajs | so we can have some additional model which Program, Group and Site inherit from | 14:36 |
SRabbelier | group, sponsor, organizations, sites, as bukits | 14:36 |
tlarsen | I think it needs to be something like: | 14:36 |
tlarsen | ??? <- Program | 14:36 |
tlarsen | ??? <- Group <- Site, Organization, Club, Sponsor | 14:37 |
tlarsen | I just don't know what the ??? is. | 14:37 |
SRabbelier | bukit, obviously :P | 14:37 |
solydzajs | and what kind of properties you want to put into ??? ? | 14:37 |
tlarsen | WTF is a "bukit" ? | 14:37 |
durin42 | I think he meant bukkit, as in the walrus picture | 14:37 |
solydzajs | tlarsen: I have no idea :-) dutch again ?;-) :D | 14:38 |
SRabbelier | durin42: yup | 14:38 |
tlarsen | ???: home page Document link, home page feed, and also other things could "scope" to it. | 14:38 |
tlarsen | (like ToS Quizzes, etc.) | 14:38 |
solydzajs | ok | 14:38 |
solydzajs | hmm | 14:38 |
solydzajs | do we want all the Groups to have home page feed ? | 14:39 |
SRabbelier | http://icanhascheezburger.com/2007/01/14/i-has-a-bucket/ | 14:39 |
tpb | <http://ln-s.net/2Ttw> (at icanhascheezburger.com) | 14:39 |
solydzajs | do we want all the groups to have home pages ? | 14:39 |
tlarsen | solydzajs: Yes, all Groups can have a feed. | 14:39 |
tlarsen | solydzajs: Yes, all Groups can have home pages. | 14:39 |
solydzajs | tlarsen: ok then it make sense :-) | 14:40 |
SRabbelier | scope? | 14:40 |
SRabbelier | why not call it scope? | 14:40 |
tlarsen | How about "Home"? | 14:41 |
SRabbelier | Home? | 14:41 |
tlarsen | Yes, because it is the "home page", the "home feed", the home for Documents, etc. | 14:41 |
tlarsen | The scopes all point to "home". | 14:41 |
tlarsen | (I know, its a stretch.) | 14:42 |
tlarsen | Or maybe "Presence". | 14:42 |
solydzajs | Presence is much better | 14:42 |
SRabbelier | Presence? 0.o | 14:42 |
solydzajs | maybe let's just call it Settings ?;-) | 14:43 |
solydzajs | BaseSettings ? | 14:43 |
tlarsen | solydzajs: But why would Documents point back to "Settings"? | 14:43 |
SRabbelier | Base | 14:44 |
tlarsen | Root | 14:44 |
SRabbelier | yes | 14:44 |
SRabbelier | Root is good | 14:44 |
tlarsen | *sigh* | 14:44 |
solydzajs | +1 for Root | 14:44 |
tlarsen | How about RubeGoldbergDevice | 14:44 |
solydzajs | :-) | 14:44 |
tlarsen | I also like BlackHole. | 14:44 |
Lennie | QuantumSingularity ? | 14:45 |
tlarsen | "everything gets sucked in" | 14:45 |
tlarsen | Widget? | 14:45 |
tlarsen | FooBar? | 14:45 |
tlarsen | :) | 14:45 |
Lennie | tlarsen, you need food :P | 14:45 |
* tlarsen is getting silly from low blood sugar... | 14:45 | |
Lennie | lol :) | 14:45 |
SRabbelier | tlarsen: let's stick with Root and be done with it | 14:45 |
tlarsen | "Root" is too meaningless. | 14:45 |
tlarsen | Why would my home page be in a "Root"? | 14:46 |
solydzajs | Container ?:-) | 14:46 |
Lennie | cause it should be rooted somewhere in the domain structure? | 14:46 |
SRabbelier | Right, that's what I said, a bukkit | 14:46 |
tlarsen | It might be in a Presence, though (think: my "Presence" on the site, or my Group's "Presence" on the site, or the Site's "Presence" on the web). | 14:46 |
SRabbelier | I don't think Presence makes any sense, sorry | 14:47 |
durin42 | GroupRoot? | 14:47 |
durin42 | EntityRoot? | 14:47 |
durin42 | as distinct from a SiteRoot? | 14:47 |
solydzajs | I'm ok with Presence | 14:48 |
solydzajs | GroupRoot can't be cause not only Groups will inherit from it | 14:48 |
tlarsen | Manifestation :) | 14:48 |
SRabbelier | origin? | 14:49 |
tlarsen | http://www.synonyms.net/synonym/presence | 14:49 |
tpb | Title: presence Synonym (at www.synonyms.net) | 14:49 |
*** scorche|1h is now known as scorche|sh | 14:50 | |
solydzajs | nothing interesting there :-) | 14:50 |
tlarsen | http://www.synonyms.net/synonym/home | 14:50 |
tpb | Title: home Synonym (at www.synonyms.net) | 14:50 |
tlarsen | solydzajs: What? You don't like Comportment? | 14:51 |
tlarsen | :) | 14:51 |
SRabbelier | it just links to itself... | 14:51 |
solydzajs | http://www.synonyms.net/synonym/base | 14:52 |
tpb | Title: base Synonym (at www.synonyms.net) | 14:52 |
solydzajs | :-) | 14:52 |
SRabbelier | solydzajs: I'm ok with base | 14:52 |
solydzajs | synonym for base: al-Qaida | 14:52 |
solydzajs | :-) | 14:52 |
solydzajs | heh | 14:52 |
SRabbelier | yeah | 14:52 |
SRabbelier | let's do that :P | 14:52 |
SRabbelier | I'm sure that will go over very well | 14:53 |
tlarsen | solydzajs: Interesting. There are no "base" nouns on your link. | 14:53 |
solydzajs | foundation ? | 14:53 |
SRabbelier | I sear | 14:53 |
SRabbelier | the hardest part in coding | 14:53 |
SRabbelier | making up the damn name | 14:53 |
tlarsen | solydzajs: Foundation is the potential name for a Group... | 14:53 |
SRabbelier | right | 14:54 |
tlarsen | OK, I'll come up with something. | 14:54 |
SRabbelier | let's swap them | 14:54 |
tlarsen | It is just a type name. | 14:54 |
SRabbelier | call it Group | 14:54 |
SRabbelier | and rename Group to Foundation :P | 14:54 |
tlarsen | It will be easy enough to change. | 14:54 |
tlarsen | If you dislike what I choose badly enough, you can change it. :) | 14:54 |
SRabbelier | fair enough | 14:54 |
solydzajs | ok sure :-) go ahead | 14:54 |
solydzajs | anything else to discuss ? | 14:54 |
SRabbelier | let's get to coding please | 14:55 |
solydzajs | ok meeting is over ? | 14:55 |
solydzajs | I"m done :-) | 14:55 |
SRabbelier | sure | 14:55 |
Lennie | k bb | 14:55 |
SRabbelier | solydzajs: thanks for hosting once more | 14:55 |
solydzajs | next one on Friday, you will get email :-) | 14:55 |
solydzajs | soon | 14:55 |
solydzajs | see you later | 14:55 |
SRabbelier | solydzajs: sure | 14:55 |
SRabbelier | cheers | 14:55 |
tlarsen | OK, later. | 14:55 |
tlarsen | Have a good evening. | 14:55 |
SRabbelier | tlarsen: you too | 14:56 |
SRabbelier | tlarsen: good luck with Linkable | 14:56 |
*** solydzajs has left #melange | 14:56 | |
Lennie | have a good lunch todd | 14:56 |
*** tlarsen is now known as tlarsen|afk | 15:24 | |
*** Lennie has quit IRC | 17:57 | |
*** mithro_ has quit IRC | 18:00 | |
*** SRabbelier has quit IRC | 18:10 | |
*** MatthewWilkes has quit IRC | 18:10 | |
*** MatthewWilkes has joined #melange | 18:13 | |
*** MatthewWilkes has quit IRC | 19:03 | |
*** mithro_ has joined #melange | 19:57 | |
*** ChanServ sets mode: +v mithro_ | 19:57 | |
* Sidnei is away: I'm busy | 20:01 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!