| dholbach | good morning | 07:50 |
|---|---|---|
| czajkowski | aloha | 08:07 |
| mhall119 | morning | 13:21 |
| AlecTaylor | hi | 14:05 |
| AlecTaylor | Done: https://blueprints.launchpad.net/loco-team-portal/+spec/streamline-interface | 14:20 |
| mhall119 | AlecTaylor: ? | 14:25 |
| AlecTaylor | I have added a recommendation to streamline the website to better meet the requirements of groups and events. | 14:26 |
| mhall119 | AlecTaylor: I believe we already have bugs for most of that, and maybe a blueprint already too | 14:27 |
| mhall119 | cjohnston: ^^ can you confirm? | 14:27 |
| cjohnston | some of it is done.. | 14:30 |
| cjohnston | AlecTaylor: just fwiw, and keeping things upfront.. if you don't provide code, most of it probably wont happen.... there isnt really anyone working on LTP right now | 14:30 |
| AlecTaylor | cjohnston: Because I might just rebuild the whole thing | 14:31 |
| AlecTaylor | Working from the Pinax Symposion project, and building a meta architecture atop it | 14:31 |
| cjohnston | go for it... we will be happy to review code | 14:31 |
| AlecTaylor | cjohnston: Mind if I just spin a few things off you first? :) | 14:31 |
| cjohnston | sure | 14:32 |
| AlecTaylor | The Pinax Symposion is a project for "social" events. Users can login to the site using their Facebook/Twitter/LinkedIn/Meetup.com account. The purpose of the project is to facilitate a conference. There are many facets to this, including: paraphenalia sales (T-Shirts), ticket sales and sponsorship sales.' | 14:33 |
| AlecTaylor | What I plan on doing is to build an architecture around this, so that there are a directory of conferences, run by groups. Users profiles will show what groups they are in, and how many events (and even what events) they have been to. | 14:34 |
| AlecTaylor | Users can invite people to an event or group using from the facebook API I will integrate. | 14:35 |
| AlecTaylor | cjohnston: What are your thoughts on this? | 14:35 |
| mhall119 | AlecTaylor: that all sounds wonderful, but it also sounds like a lot of work. If you have the time and energy to do it, cjohnston and I will support you in any way we can | 14:39 |
| AlecTaylor | Thanks | 14:44 |
| mhall119 | AlecTaylor: let us know if you need any help getting the current LTP up and running | 14:47 |
| AlecTaylor | mhall119: Not sure, I'll take a look at the code but it might be best to start from the conferencing project and build in the LTP/Meetup.com style features, rather than start from the LTP base and add in the conferencing features. | 14:48 |
| mhall119 | AlecTaylor: whatever you think will work best, but it might help give you a better understanding of hot LTP currently works | 14:49 |
| AlecTaylor | Just looking for a free collaborative diagramming tool to show you the kinds of things I'm thinking about | 14:52 |
| AlecTaylor | mhall119: https://creately.com/diagram/gxlwjlce1/dSeLvvhMA5EUcT4rFsmEjNqJKI%3D | 14:57 |
| AlecTaylor | mhall119 / cjohnston: What do you think of the diagram thus far? | 15:14 |
| mhall119 | AlecTaylor: looks similar ot what we have now | 15:27 |
| mhall119 | AlecTaylor: are you thinking of incorporating LTP into this, or replacing it all together? | 15:27 |
| AlecTaylor | Probably replacing it altogether | 15:27 |
| mhall119 | AlecTaylor: there's years of work built into LTP currently, replacing it will be no small task | 15:28 |
| mhall119 | it might be easier to find a way to incorporate it, either in code of via it's API, into a separate project | 15:29 |
| AlecTaylor | Well the big problem with LTP is it doesn't have a social feel to it | 15:31 |
| mhall119 | agreed | 15:33 |
| mhall119 | but that's something we can build into it, especially using some of the pinax apps | 15:33 |
| mhall119 | rather that trying to re-implement everything | 15:33 |
| AlecTaylor | This system: http://i40.tinypic.com/hvzdrk.png - Doesn't look crazily complicated | 15:34 |
| AlecTaylor | Does it? | 15:38 |
| * AlecTaylor hasn't worked on any large projects | 15:38 | |
| mhall119 | AlecTaylor: it's not that your system is complicated, it's that there's a lot of value in teh current code that you will lose if you replace it | 15:38 |
| mhall119 | it'll just make your job harder | 15:38 |
| AlecTaylor | The map looked useful, but apart from that, wouldn't it be more complicated integrated social user system and conferencing rather than the reverse? | 15:39 |
| cjohnston | outside of the sponsor stuff, merchandice stuff, and profile stuff, everything is already there | 15:39 |
| mhall119 | the current code represents the time of several volunteer developers over the course of multiple years | 15:39 |
| cjohnston | so why not just add more to it | 15:39 |
| cjohnston | instead of start over | 15:39 |
| mhall119 | AlecTaylor: adding social features to the current code would be less work than re-implementing the current code on top of existing social features, IMO | 15:40 |
| AlecTaylor | Are you sure? | 15:40 |
| mhall119 | nope, you can't be sure until you do it | 15:40 |
| mhall119 | but from my familiarity with the LTP code, I'm pretty confident | 15:40 |
| === JanC_ is now known as JanC | ||
| paultag | anyone going to PyCon? | 17:45 |
| mhall119 | not I :( | 17:57 |
| paultag | looking to get a crew together to hack together | 18:00 |
| paultag | perhaps a keysigning | 18:00 |
| AlecTaylor | Okay, posted on the Pinax/Django mailing-list a very specific condensed question on implementation. | 18:00 |
| AlecTaylor | (https://groups.google.com/forum/#!topic/django-users/ex55qOYYs_s) | 18:04 |
| === Ronnie2 is now known as Ronnie | ||
| === h00k__ is now known as h00k | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
