| [00:08:29] |
<Zenom> |
keep in mind this is very very basic |
| [00:08:29] |
<Zenom> |
http://paste.pocoo.org/show/89365/ |
| [00:08:36] |
<Zenom> |
but the general idea for starters i think |
| [00:09:32] |
<Zenom> |
i think projects can have multiple milestones |
| [00:09:40] |
<Zenom> |
you may have short term and long term milestones |
| [00:09:57] |
<Zenom> |
so its like group-> many projects -> many users |
| [00:11:27] |
<ronny> |
Version in milestone? |
| [00:12:18] |
<ckknight> |
Zenom: version in milestone should be name, imo, and be a string |
| [00:12:21] |
<Zenom> |
well wouldn't you want milestones per verion |
| [00:12:22] |
<ckknight> |
what if you have 1.2.3? |
| [00:12:32] |
<Zenom> |
version |
| [00:12:42] |
<ronny> |
a string is better |
| [00:12:45] |
<ckknight> |
or a non-numeric name? |
| [00:12:46] |
<Zenom> |
changed to string |
| [00:13:11] |
<Zenom> |
do i need an intermediate project <-> versions table? |
| [00:13:25] |
<Zenom> |
since a project can have multiple versions then link the milestone to that? |
| [00:13:25] |
<ckknight> |
I wouldn't think so... |
| [00:13:40] |
<ckknight> |
depends on how you want to treat versions and milestones |
| [00:13:42] |
<ronny> |
Zenom: let versions just be milestones |
| [00:13:54] |
<ronny> |
and please no floats for versions |
| [00:13:59] |
<Zenom> |
ya i changed to string |
| [00:14:17] |
<Zenom> |
so version == milestone with version being its 'title' |
| [00:15:57] |
<Zenom> |
like i said its basic, needs like a ticket system per project too for bugs |
| [00:16:53] |
<ronny> |
Zenom: buts are just tasks, too |
| [00:16:56] |
<ronny> |
*bugs |
| [00:17:04] |
<Zenom> |
true |
| [00:17:10] |
<listonb> |
what |
| [00:17:11] |
<listonb> |
wtf |
| [00:17:18] |
<ckknight> |
and bugs are just handled through tickets, if you ask me |
| [00:17:20] |
* |
listonb stabs all of your db skills |
| [00:17:20] |
* |
highwaychile has quit IRC |
| [00:17:29] |
<Zenom> |
lol |
| [00:17:38] |
<ckknight> |
listonb: ? |
| [00:17:45] |
<Zenom> |
listonb: is one of my programmers |
| [00:17:55] |
<Zenom> |
and our server "guru" |
| [00:18:00] |
<ckknight> |
k. |
| [00:18:04] |
<ronny> |
listonb: if you can do better please do so ;P |
| [00:18:22] |
<listonb> |
le grumble |
| [00:18:24] |
* |
listonb pulls up textmate |
| [00:18:28] |
<ckknight> |
lol |
| [00:18:29] |
* |
listonb puts on music |
| [00:18:36] |
<ronny> |
Zenom: tasks need a state for stuff like (new, in progress, wontfix) |
| [00:18:58] |
<listonb> |
Zenom: plz to send 2nd monitor. thx ;) lol |
| [00:19:09] |
<ckknight> |
oh, and tickets can be of different types |
| [00:19:28] |
<ckknight> |
here's ours: TICKET_TYPES = ((u'd', u'Defect'), (u'e', u'Enhancement'), (u't', u'Task'), (u'p', u'Patch'), (u'o', u'Other')) |
| [00:19:40] |
<listonb> |
fuckign to many windows open |
| [00:19:55] |
<ckknight> |
and for statuses, TICKET_OPEN_STATUSES = ((u'n', u'New'), (u'a', u'Accepted'), (u'w', u'Waiting'), (u'r', u'Replied'), (u's', u'Started')) and TICKET_CLOSED_STATUSES = ((u'f', u'Fixed'), (u'v', u'Verified'), (u'i', u'Invalid'), (u'u', u'Duplicate'), (u'd', u'Declined')) |
| [00:20:59] |
<Zenom> |
so should I just have a relation for task type? |
| [00:21:05] |
<Zenom> |
and allow tasks/tickets to be anything? |
| [00:21:22] |
<listonb> |
just doign a quick mockup in mysql |
| [00:21:23] |
<listonb> |
1 sec |
| [00:21:26] |
<ckknight> |
that's a possibility. We just use a fixed enum |
| [00:21:40] |
<ronny> |
hmm |
| [00:21:50] |
<ronny> |
GOD DO I HATE MYSQL |
| [00:22:06] |
<listonb> |
yes but its quick for me to type these up by hand |
| [00:22:11] |
<listonb> |
i would do it in pgsql later |
| [00:22:13] |
<Zenom> |
ya we use postgresql at work |
| [00:22:27] |
<ronny> |
nice |
| [00:22:29] |
<ckknight> |
ronny: what's the issue? |
| [00:22:32] |
<listonb> |
i'm tyoing these tables by hands chill |
| [00:23:31] |
<ckknight> |
ah |
| [00:23:39] |
<Zenom> |
should those task names be per project or per group? |
| [00:24:09] |
<ronny> |
Zenom: sounds like an unimportant detail |
| [00:24:52] |
<listonb> |
milestones shouldnt have versions |
| [00:25:08] |
<ronny> |
listonb: should be a name, and a string |
| [00:25:10] |
<Zenom> |
milestones are versions essentially |
| [00:25:14] |
<listonb> |
... |
| [00:25:20] |
<listonb> |
milestones are goals |
| [00:25:46] |
<ckknight> |
milestones have names, not versions |
| [00:25:51] |
* |
listonb nods |
| [00:25:55] |
<listonb> |
milestones are names of a goal |
| [00:25:56] |
<Zenom> |
ok let me change |
| [00:25:58] |
<ckknight> |
a milestone's name might be == your resultant version name |
| [00:26:01] |
<listonb> |
"zomg the webpage is done" |
| [00:26:03] |
<listonb> |
isa milestone |
| [00:26:19] |
<ronny> |
hmm |
| [00:26:20] |
<listonb> |
you've reached said milestone when all tasks are completed |
| [00:26:27] |
<listonb> |
tasks should be assigned to a mile stone |
| [00:26:32] |
<listonb> |
think of a milestone as a sprint |
| [00:26:36] |
<Zenom> |
http://paste.pocoo.org/show/89367/ |
| [00:26:37] |
<listonb> |
tasks as a task in the sprint |
| [00:26:39] |
<Zenom> |
latest |
| [00:26:44] |
<listonb> |
each sprint is completed (milestone) then the project is updated |
| [00:26:51] |
<ckknight> |
not every ticket might be assigned to a milestone, some might be left hanging |
| [00:26:52] |
<listonb> |
next milestone can be attempted to complete |
| [00:27:04] |
<listonb> |
not talking tickets here |
| [00:27:06] |
<listonb> |
tickets != tasks |
| [00:27:10] |
<listonb> |
tickets should be bugs |
| [00:27:19] |
<ckknight> |
I consider tasks a subset of tickets |
| [00:27:22] |
<listonb> |
after a bug is submited a taskis created to fix the bug(ticket) |
| [00:27:24] |
<ckknight> |
just as bugs are a subset of tickets |
| [00:27:39] |
<listonb> |
bugs/tickets should not have a 1:1 to tasks |
| [00:27:42] |
<ckknight> |
that's just the way I operate, though |
| [00:27:47] |
<listonb> |
sohuld be a relation to the project or milestone |
| [00:28:00] |
<listonb> |
and then a task can be created that references back to a ticket |
| [00:28:06] |
<listonb> |
not a ticket to a task. but a task to a ticket |
| [00:28:44] |
<Zenom> |
ok so tickets to projects, tasks to tickets and projects? |
| [00:29:04] |
<listonb> |
ticket is an optional int |
| [00:29:06] |
<listonb> |
default 0, unsigned |
| [00:29:11] |
<Zenom> |
right |
| [00:29:14] |
<ronny> |
i think its reasonable to view bug/task as the same thing |
| [00:29:20] |
<listonb> |
sure |
| [00:29:27] |
<listonb> |
when you view the task that ahs teh bug associated with it you would |
| [00:29:36] |
<listonb> |
you couldessentially do the same backwards but the ticket shouldnt be directly linked to a task |
| [00:29:44] |
<listonb> |
when you pull up said ticket tho you can query for any bugs associated with it |
| [00:29:45] |
<ckknight> |
ronny: some things are not bugs, though, e.g. feature requests |
| [00:29:50] |
<listonb> |
*tasks associated with it |
| [00:29:57] |
<listonb> |
you could have 15 tasks for 1 ticket |
| [00:29:59] |
<Zenom> |
thats why i was thinking TaskType |
| [00:30:01] |
<listonb> |
you could have 0 tickets |
| [00:30:05] |
<Zenom> |
you could have Bug, Feature etc |
| [00:30:15] |
<Zenom> |
and assign that to as a task type |
| [00:30:20] |
<listonb> |
in reality there should be tasktype, ticketype, projecttype |
| [00:30:22] |
<ronny> |
listonb: so tickets are like a milestone ? |
| [00:30:27] |
<ckknight> |
for my ticket tracking system, I mostly stole Googlecode's semantics. |
| [00:30:31] |
<listonb> |
tickets are requests |
| [00:30:37] |
<listonb> |
tasks are shit thats being worked on |
| [00:30:43] |
<listonb> |
or already entered into the system for somebody to work on |
| [00:30:50] |
<listonb> |
tickets are requestswaiting for shit to be done rofixed |
| [00:30:51] |
<ronny> |
hmm |
| [00:30:58] |
<listonb> |
ie feature request or bug fix |
| [00:31:03] |
<listonb> |
milestones are goals to be reached |
| [00:31:06] |
* |
ckknight shrugs |
| [00:31:12] |
<listonb> |
milestone 1) integrate database system |
| [00:31:19] |
<listonb> |
task 1) build databasemodels |
| [00:31:24] |
<listonb> |
task 2) implement models to videws |
| [00:31:25] |
<listonb> |
whatever |
| [00:31:26] |
<ckknight> |
imo, I don't see the point of separating tickets and tasks |
| [00:31:36] |
<listonb> |
task 1 complete |
| [00:31:40] |
<listonb> |
because they arent the esame |
| [00:31:43] |
<listonb> |
a task isnt a bug |
| [00:31:48] |
<ronny> |
oh yay - this reminds me more and more of the models i did read about in "Getting things done" |
| [00:31:49] |
<listonb> |
a task is something you are doing |
| [00:32:04] |
<ckknight> |
I never said a task was a bug |
| [00:32:08] |
<ckknight> |
nor did I say a ticket was a bug |
| [00:32:11] |
<Zenom> |
the point though to is to keep things "simple |
| [00:32:12] |
<listonb> |
well a bug is a ticket |
| [00:32:14] |
<ckknight> |
wrong |
| [00:32:18] |
<listonb> |
not wrong |
| [00:32:18] |
<listonb> |
heh |
| [00:32:30] |
<ckknight> |
yes, wrong, what if you ticket a feature you want? |
| [00:32:31] |
<listonb> |
Any request forsomething to be done or fixed isa ticket |
| [00:32:32] |
<ckknight> |
that's not a bug. |
| [00:32:34] |
<Zenom> |
keep in mind its more or less just for tracking |
| [00:32:38] |
<listonb> |
yes like is said 3 times |
| [00:32:43] |
<listonb> |
Any feature request or bug is a ticket |
| [00:32:53] |
<ronny> |
so a ticket is an idea thats not directly actionable ? |
| [00:32:58] |
<Zenom> |
wouldnt a feature request be a task though? |
| [00:33:03] |
<listonb> |
depends howitwas put in |
| [00:33:10] |
<listonb> |
say you start from scratch and you justcreated a milestone |
| [00:33:13] |
<listonb> |
and you assigned sometasks to it |
| [00:33:18] |
<ckknight> |
oh well, I still think having tasks as a type of ticket is a lot cleaner, then if you fix a bug, you close the ticket rather than dealing with a separate task system |
| [00:33:25] |
<listonb> |
later you find out you need someshit changed you putina ticket for your devs to fix or add somethin |
| [00:33:31] |
<listonb> |
they create a task associated to that ticket to get it done |
| [00:33:51] |
* |
ckknight is now known as ckknight|away |
| [00:33:56] |
<listonb> |
if a task isa type of ticket then all you are doingis buildinga ticketing system |
| [00:33:59] |
<listonb> |
not a management system |
| [00:34:13] |
<listonb> |
and you'll be flooded with tickets |
| [00:34:15] |
<Zenom> |
but task can be essentially a ticket with a different name |
| [00:34:21] |
<ronny> |
listonb: this sounds like "tickets" folow the same semantics as milestones |
| [00:34:23] |
<Zenom> |
i mean you can set the type of it |
| [00:34:30] |
<listonb> |
a milestone is a point in time |
| [00:34:36] |
<listonb> |
have you guys never done scrum and sprints? |
| [00:34:37] |
<listonb> |
hehe |
| [00:34:50] |
<listonb> |
http://en.wikipedia.org/wiki/SCRUM |
| [00:34:51] |
<Zenom> |
no dick i havn't |
| [00:35:05] |
<ronny> |
listonb: i havent done scrum/sprints, but i recently got started with GTD |
| [00:35:28] |
<listonb> |
"During each sprint, a 15-30 day period (length decided by the team), the team creates an increment of potential shippable (usable) software. The set of features that go into each sprint come from the product backlog, which is a prioritized set of high level requirements of work to be done" |
| [00:35:48] |
<listonb> |
so a milestone would be a 'sprint' |
| [00:35:53] |
<listonb> |
and the backlog would be tickets |
| [00:35:59] |
<listonb> |
tasks would be the current items tobe worked on in a milestone |
| [00:37:10] |
<listonb> |
ronny: whats gtd |
| [00:37:14] |
<Zenom> |
so your idea is to keep tasks associated to milestones, tickets are separate which are more or less associated to just a project, and tasks can be assocaited to a ticket to ensure tickets completio? |
| [00:37:22] |
<listonb> |
ya |
| [00:37:28] |
<ronny> |
listonb: "getting things done" by david allan |
| [00:37:35] |
<listonb> |
that way you keep your 'working' on data seperate from your 'tobeworked' |
| [00:37:55] |
<listonb> |
makes a difference if you have 43423234223 projects |
| [00:38:16] |
<listonb> |
i'm always thinking scaling when i design stuff so thus the seperation like this |
| [00:39:18] |
<ronny> |
listonb: roughly translated to gtd - tickets are things that arent actionable, tasks are actions, and milestones are collections of actions |
| [00:39:28] |
<listonb> |
ya |
| [00:39:33] |
<listonb> |
that make a lil more sense? |
| [00:40:05] |
<ronny> |
gtd makes more sense to me, as its a more simple system |
| [00:40:18] |
<Zenom> |
ronny but from what i understand gtd is what bryan says |
| [00:40:33] |
<ronny> |
bryan == listonb ? |
| [00:40:34] |
<Zenom> |
essentially maybe he's just not making himself clear |
| [00:40:35] |
<listonb> |
ya |
| [00:40:37] |
<Zenom> |
ya , sorry |
| [00:40:59] |
<listonb> |
ronny: i didnt mean howa i was explaining it make senseimeant more the method after you came to that conversion |
| [00:41:07] |
<listonb> |
fuck my space bar is fubar |
| [00:41:20] |
<Zenom> |
and ronny , listonb is mr "no" |
| [00:41:32] |
<ronny> |
mr "no" ? |
| [00:41:33] |
<Zenom> |
i will ask him to do something and he will say "no" then I have to threaten him |
| [00:41:38] |
<Zenom> |
before he does it |
| [00:41:45] |
<Zenom> |
so he is always the negative to everyone else's positive |
| [00:42:18] |
<Zenom> |
i think the concept you guys want is the same its just he explains it different |
| [00:42:26] |
<ronny> |
but hes fscking good at knowing what exactly the data model needs |
| [00:42:41] |
<Zenom> |
ya he's a smart cookie |
| [00:42:43] |
<ronny> |
his view on that stuff is more clear than mine |
| [00:42:50] |
* |
ckknight|away is now known as ckknight |
| [00:42:51] |
<Zenom> |
thats why i hired him :) |
| [00:43:02] |
<listonb> |
ckknight: read the last thing i wrote after the quoted paste |
| [00:43:05] |
<listonb> |
well including the quoted paste |
| [00:44:27] |
<ronny> |
imho users<>group should be m2n tho |
| [00:44:39] |
<listonb> |
m2n? |
| [00:44:44] |
<listonb> |
mnany 2 none? |
| [00:44:50] |
<listonb> |
or did you typo another m |
| [00:44:58] |
<ronny> |
gah |
| [00:45:12] |
<listonb> |
but yes m2m makes sense |
| [00:45:18] |
<listonb> |
you should have a group_users metadata table |
| [00:45:22] |
<listonb> |
with group_id, user_id |
| [00:45:27] |
<listonb> |
users should be allowed in multiple groups |
| [00:45:37] |
<ronny> |
we always used m2n for many 2 many - different symbol for each side |
| [00:45:39] |
<listonb> |
and groups can be assigned to milestones i'd say |
| [00:45:43] |
<listonb> |
ronny: ah never seen that |
| [00:46:49] |
<ronny> |
in 10 minutes i'll go to sleep |
| [00:47:50] |
<Zenom> |
http://paste.pocoo.org/show/89368/ |
| [00:47:53] |
<Zenom> |
latest version |
| [00:48:17] |
<listonb> |
god i hate looking at that |
| [00:48:33] |
<Zenom> |
and true user <-> group should be m2m |
| [00:49:05] |
<listonb> |
ok lemme do this shit in tetmate |
| [00:49:12] |
<Zenom> |
which is not in this version i pasted but added notes |
| [00:51:13] |
<ronny> |
hmm |
| [00:51:36] |
<ronny> |
i think i'll like to read sql more, too |
| [00:52:59] |
<ckknight> |
ronny: I've seen M:N |
| [00:53:07] |
<ckknight> |
to describe a many-to-many relationship |
| [00:53:20] |
<Zenom> |
well depends on your background too |
| [00:53:22] |
<listonb> |
weird i've never seen the N |
| [00:53:23] |
<listonb> |
hehe |
| [00:53:27] |
<Zenom> |
like N+N is redundant redundant |
| [00:53:39] |
<Zenom> |
mostly networking people I have seen use N |
| [00:57:40] |
<listonb> |
almost done with a basic mock |
| [00:57:43] |
<listonb> |
bunch o chango |
| [01:00:53] |
<ronny> |
^^ |
| [01:01:38] |
<Zenom> |
he's working on it |
| [01:01:41] |
<Zenom> |
he's just mental |
| [01:01:46] |
<Zenom> |
so it takes a little bit more time |
| [01:02:06] |
<listonb> |
oh sorry |
| [01:02:09] |
<listonb> |
i have like 8 windows open |
| [01:02:13] |
<listonb> |
and i keep adding shit to it |
| [01:02:14] |
<listonb> |
1 sec |
| [01:02:38] |
<listonb> |
i gotta explain it once i paste it, lemme add the last 3 tables |
| [01:10:03] |
<listonb> |
so much typing |
| [01:14:53] |
<listonb> |
k here? |
| [01:16:52] |
<Zenom> |
yes an hour later |
| [01:17:02] |
<listonb> |
http://pastie.textmate.org/private/niegsvd9iplry4hiyhllg |
| [01:17:22] |
<listonb> |
mind you that was rushed |
| [01:17:40] |
<listonb> |
companies own projects, users, groups |
| [01:18:13] |
<listonb> |
projects own milestones, tickets |
| [01:18:34] |
<listonb> |
milestones owns tasks, |
| [01:18:45] |
<listonb> |
users can be assigned to as many tasks and groups as needed |
| [01:19:09] |
<listonb> |
that way 1 company can have 18 projects and have a user assigned to all or as few as they want, or assign that user by group, etc. |
| [01:20:44] |
<listonb> |
channel sure got quiet |
| [01:22:01] |
* |
ckknight is now known as ckknight|away |
| [01:34:17] |
* |
aconbere has joined #pocoo |
| [01:53:10] |
* |
aconbere has quit IRC |
| [01:57:35] |
* |
sulo_ has quit IRC |
| [02:36:00] |
* |
KirkMcDonald has quit IRC |
| [02:58:39] |
* |
KirkMcDonald has joined #pocoo |
| [04:11:56] |
* |
izibi has quit IRC |
| [04:12:20] |
* |
izibi has joined #pocoo |
| [04:55:23] |
* |
ckknight|away is now known as ckknight |
| [07:11:15] |
* |
damjan has quit IRC |
| [07:17:04] |
* |
izibi has quit IRC |
| [07:46:19] |
* |
damjan has joined #pocoo |
| [07:48:10] |
* |
damjan has joined #pocoo |
| [08:35:36] |
<ronny> |
moin |
| [09:05:43] |
* |
ckknight is now known as ckknight|away |
| [09:32:28] |
* |
sulo_ has joined #pocoo |
| [10:01:42] |
* |
springmeyer has quit IRC |
| [10:20:55] |
* |
leche has joined #pocoo |
| [10:22:03] |
* |
leche has quit IRC |
| [10:25:31] |
* |
leche has joined #pocoo |
| [10:37:25] |
* |
aa__ is now known as aa_ |
| [10:38:17] |
* |
sulo_ has quit IRC |
| [11:27:45] |
* |
KAeL has quit IRC |
| [11:49:30] |
* |
sulo_ has joined #pocoo |
| [11:54:42] |
<asmodai> |
14 |
| [11:59:59] |
* |
maix has joined #pocoo |
| [12:02:38] |
<dennda> |
15 |
| [12:30:18] |
<asmodai> |
Sure? |
| [12:30:24] |
<asmodai> |
maybe it was a trick |
| [12:34:04] |
<steg> |
13 |
| [12:34:17] |
<steg> |
it was a countdown to something dreadful :( |
| [12:48:46] |
<asmodai> |
oh dear |
| [12:48:50] |
<asmodai> |
well |
| [12:48:55] |
<asmodai> |
handed in my resignation today |
| [13:28:29] |
* |
KAeL has joined #pocoo |
| [14:38:42] |
* |
ckknight|away is now known as ckknight |
| [14:42:13] |
* |
plaes has quit IRC |
| [14:42:25] |
* |
plaes has joined #pocoo |
| [14:46:18] |
* |
lakin has joined #pocoo |
| [14:47:45] |
* |
ckknight has quit IRC |
| [14:50:20] |
* |
ckknight has joined #pocoo |
| [15:15:31] |
* |
ckknight has quit IRC |
| [15:20:36] |
* |
topcat has joined #pocoo |
| [15:26:59] |
* |
ckknight has joined #pocoo |
| [15:37:17] |
<topcat> |
could someone help me ease into jinja2? need some tips, best practice from someone more experienced |
| [15:47:56] |
<prencher> |
how about you go read the documentation, get going and then ask questions when you actually have any? |
| [15:57:28] |
* |
derdon has joined #pocoo |
| [15:59:36] |
<tux21b> |
the tutorial is already quite practical. I suggest you to read that |
| [16:12:32] |
* |
topcat has quit IRC |
| [16:17:27] |
* |
Kaelten has quit IRC |
| [16:17:34] |
* |
Kaelten has joined #pocoo |
| [16:19:26] |
<prencher> |
stop spamming Kaelten! |
| [16:19:35] |
<Kaelten> |
:P |
| [16:19:42] |
<Kaelten> |
it didn't like it when I pasted a long ass line in |
| [16:19:44] |
<Kaelten> |
http://paste.pocoo.org/show/89419/ |
| [16:23:13] |
<apollo13> |
empty: http://bigboychoy.com/2008/oct/29/introducing-django_git/ |
| [16:24:48] |
<prencher> |
meh |
| [16:29:13] |
<empty> |
apollo13: someone else just sent me that. :) |
| [16:30:28] |
<empty> |
pretty cool |
| [16:30:55] |
* |
izibi has joined #pocoo |
| [16:42:49] |
<Kaelten> |
me no like git |
| [16:42:54] |
<Kaelten> |
me like mercurial |
| [16:50:51] |
* |
springmeyer has joined #pocoo |
| [17:00:58] |
<ronny> |
Kaelten: good boy |
| [17:02:01] |
<apollo13> |
Kaelten: me no like hg, cause you can check in broken queues which can fuck up your repo |
| [17:02:11] |
<apollo13> |
bundles I mean |
| [17:03:02] |
<empty> |
oh noes not again |
| [17:03:08] |
<aa_> |
whereas with git you can't to anything at all |
| [17:03:17] |
<aa_> |
(because it's so insane) |
| [17:03:29] |
<aa_> |
"security by probablility" |
| [17:03:43] |
<aa_> |
(ignore me, I am just fanning the flames) |
| [17:04:04] |
<apollo13> |
I see :þ |
| [17:04:31] |
<apollo13> |
But I really would like hg to run hg verify before letting you check in broken stuff |
| [17:07:44] |
<ronny> |
apollo13: git has whorse screw ups |
| [17:08:46] |
<apollo13> |
well every vcs has I guess ;) |
| [17:09:09] |
<apollo13> |
and I am using git hg and svn, so I'm kinda fine with all of them |
| [17:11:23] |
<ronny> |
basically all currents vcs's are insane shit |
| [17:12:00] |
<apollo13> |
Right, but I try to see the positive aspects ;) |
| [17:12:39] |
* |
sulo_ has quit IRC |
| [17:12:57] |
<ronny> |
cvs is completely wrong, svn is not realizing that it cant be fixed, git is undocumented piles of confusion, hg is who cares about massive design flaws, bzr is we do everything, just way too complicated in ways any sane person will hate |
| [17:13:32] |
<aa_> |
ronny: tla? monotone? |
| [17:14:13] |
<ronny> |
aa_: anyone still even remotely considering tla deserves death |
| [17:14:25] |
<aa_> |
ronny: tla is *sweet* |
| [17:14:48] |
<aa_> |
ronny: monotone was still going strong last I checked |
| [17:15:04] |
<ronny> |
and monotone is - we do metadata right, we just screw up at storage and ease of use |
| [17:15:53] |
<aa_> |
ronny: heard of this thing called "anyvc" ? |
| [17:16:05] |
<aa_> |
ronny: apparently the command line client doesn't care what vc you are using |
| [17:16:17] |
<aa_> |
ronny: and you can use it in a library for stuff |
| [17:16:23] |
<aa_> |
sounds very cool |
| [17:16:27] |
<aa_> |
I should download it |
| [17:16:29] |
<ronny> |
aa_: yeah - its bascially patching together differently colored shit |
| [17:16:39] |
<empty> |
lowest common denominator |
| [17:16:40] |
<empty> |
:P |
| [17:17:00] |
<ronny> |
empty: its usualy the subset most people will use |
| [17:17:42] |
<ronny> |
empty: btw, when will gitpython use more iterators and give us workdir/index states? |
| [17:17:57] |
<ronny> |
anyvc git is still kinda patched up |
| [17:18:05] |
<ronny> |
i want to wire up history soon |
| [17:18:14] |
<ronny> |
(at least for git, bzr and hg) |
| [17:18:38] |
<empty> |
ronny: We're looking for stuff to add to gitpython. So if you have ideas please post to the list. |
| [17:21:04] |
<ronny> |
list? |
| [17:21:29] |
<ronny> |
url? |
| [17:24:12] |
<empty> |
ronny: http://groups.google.com/group/git-python and #git-python on freenode |
| [17:26:26] |
<plaes> |
windows support? :D |
| [17:26:35] |
<plaes> |
sorry.. just kidding :D |
| [17:28:25] |
* |
stifal has joined #pocoo |
| [17:39:07] |
* |
plaes has quit IRC |
| [17:39:07] |
* |
listonb has quit IRC |
| [17:39:07] |
* |
alowry has quit IRC |
| [17:39:07] |
* |
maze has quit IRC |
| [17:39:07] |
* |
izibi has quit IRC |
| [17:39:07] |
* |
lakin has quit IRC |
| [17:39:07] |
* |
mq has quit IRC |
| [17:39:07] |
* |
benoitc has quit IRC |
| [17:39:07] |
* |
Zenom has quit IRC |
| [17:41:01] |
* |
izibi has joined #pocoo |
| [17:41:02] |
* |
lakin has joined #pocoo |
| [17:41:02] |
* |
plaes has joined #pocoo |
| [17:41:02] |
* |
listonb has joined #pocoo |
| [17:41:02] |
* |
alowry has joined #pocoo |
| [17:41:02] |
* |
mq has joined #pocoo |
| [17:41:02] |
* |
maze has joined #pocoo |
| [17:41:02] |
* |
Zenom has joined #pocoo |
| [17:41:02] |
* |
benoitc has joined #pocoo |
| [17:41:59] |
* |
derdon has quit IRC |
| [17:43:17] |
<ronny> |
plaes: windows support for what? |
| [18:12:47] |
<plaes> |
git-python :) |
| [18:15:36] |
* |
Leslie has joined #pocoo |
| [18:15:57] |
* |
mattt_ has joined #pocoo |
| [18:16:10] |
<empty> |
plaes: does it not work. |
| [18:16:17] |
<empty> |
We had some users using it on windows |
| [18:16:17] |
<Leslie> |
hi, I just visited the pygments site and noticed a grave mistake -- Common Lisp definitely belongs to the "Agile Languages" section... |
| [18:20:20] |
* |
EnTeQuAk has joined #pocoo |
| [18:40:50] |
* |
sulo_ has joined #pocoo |
| [19:10:05] |
* |
leifkb_ has quit IRC |
| [19:10:06] |
<apollo13> |
last time I checked it worked fine |
| [19:10:12] |
<apollo13> |
plaes: so what's with windows support? |
| [19:14:36] |
* |
leifkb has joined #pocoo |
| [19:18:30] |
<plaes> |
it was a joke :D |
| [19:21:25] |
<ckknight> |
hey all, I'm having a hell of a time trying to debug something with jinja2 |
| [19:21:50] |
<ckknight> |
I have a macro that appears to be called, but it returns nothing, which makes absolutely no sense. |
| [19:25:25] |
<apollo13> |
ckknight look at the macro source, macros don'T have to return stuff afaik, they could set vars etc... |
| [19:25:39] |
<ckknight> |
no, it's meant to return stuff |
| [19:25:48] |
<apollo13> |
oh |
| [19:25:49] |
<ckknight> |
even if I change the macro's innards to just a string |
| [19:26:24] |
<ronny> |
how about showing some code?! |
| [19:27:06] |
<ckknight> |
k, hang on |
| [19:28:19] |
<ckknight> |
{% macro alpha() %}Hello{% endmacro %} |
| [19:28:19] |
<ckknight> |
{% block facts_box_rows %}"{{ alpha() }}"{% endblock %} |
| [19:28:24] |
<ckknight> |
it shows: "" |
| [19:33:06] |
<ronny> |
might be scoping |
| [19:33:43] |
<ckknight> |
if I do {{ alpha|escape }}, it shows <Macro alpha> or something |
| [19:53:18] |
* |
_paneb has joined #pocoo |
| [19:58:01] |
<ckknight> |
yea, by adding some debugging code in, I can see that it doesn't appear to be defining the mactro properly |
| [19:58:23] |
<ckknight> |
basically just t_4 = []; pass; return concat(t_4) |
| [20:04:28] |
<ckknight> |
okay, reverting to a month old dev version fixed it |
| [20:05:40] |
<Kaelten> |
mitsuhiko: ^ |
| [20:06:38] |
<Zenom> |
cutting edge using dev :) |
| [20:06:50] |
<_paneb> |
how am i supposed to partially update a resource? say the resource is a user with email addresses, phone numbers, postal addresses, nickname, etc...if i only wanted to update an email address, could i just check the data passed to the server in the PUT request? otherwise i would have to repost the whole representation of the resource (which may be large) |
| [20:07:37] |
<ronny> |
_paneb: put has to be idempotent - what makes your user resource so large ?! |
| [20:08:09] |
<empty> |
bah where's mitsuhiko |
| [20:08:12] |
<alowry> |
_paneb: Generally one would only include data to be changed in a put; you don't need to include email if the caller isn't changing it. |
| [20:08:27] |
<_paneb> |
ok that's what i was thinking |
| [20:08:37] |
<ronny> |
alowry: sounds plain wrong |
| [20:08:44] |
<_paneb> |
why? |
| [20:08:52] |
<ronny> |
ignores the need for idempotence |
| [20:09:09] |
<alowry> |
No, repeated puts would have no additional effect |
| [20:09:14] |
<_paneb> |
how? if i replace the primary email by another, i can do it 10 times with no effects |
| [20:09:17] |
<ronny> |
put has to be the same, for no data yet and data availiable |
| [20:09:48] |
<ronny> |
you still haven told why it gets so large tho |
| [20:10:10] |
<ckknight> |
mitsuhiko: if you need me to, I could run a bisect and figure out what revision caused the breakage |
| [20:10:13] |
<alowry> |
Right; so {'name': 'foo'} is different than {'name': 'foo', 'email': ''}. The first makes no change to email; the second blanks email. |
| [20:10:19] |
<_paneb> |
ronny, it's not large, but i find it awkward to have to send the whole representation when i am only updating parts of it |
| [20:11:37] |
<ronny> |
its called representional state transfer for a reason |
| [20:11:42] |
* |
listonb yawns |
| [20:11:53] |
<ronny> |
yo listonb |
| [20:12:25] |
<listonb> |
sup |
| [20:12:39] |
<ronny> |
listonb: the tables look nice, i kinda dont see the point for company for all of my stuff tho |
| [20:13:07] |
<ronny> |
now it needs to get ui tho |
| [20:13:20] |
<listonb> |
company is required toallow multiple projects belong to 1 person/company |
| [20:13:24] |
<listonb> |
users are owned by company so are groups |
| [20:13:38] |
<listonb> |
sure if your running this by your self on your local box ya |
| [20:13:52] |
<listonb> |
but if you ran this public and had multiple diff ppl using it you'd want company/etc |
| [20:15:18] |
<ronny> |
well, we just do multiple open-source projects - everybody belongs to everything |
| [20:19:45] |
<listonb> |
well sure i'm just saying for expansion |
| [20:20:27] |
<ronny> |
im not yet sure how to keep that an optional part, i'll take a shower |
| [20:20:47] |
<listonb> |
you just create your company name and yer done thats it |
| [20:20:53] |
<listonb> |
you dont hafta create multiple companies |
| [20:20:54] |
<listonb> |
its optional |
| [20:27:29] |
<ronny> |
hmm, yeah |
| [20:28:53] |
<ckknight> |
mitsuhiko: I ran the bisect, it starts not creating macros properly at 585:c78f8c799730: The hopefully final fix for the bug apollo13 spotted earlier. |
| [20:58:42] |
* |
mardig has joined #pocoo |
| [21:02:49] |
* |
_paneb has quit IRC |
| [21:11:31] |
* |
highwaychile has joined #pocoo |
| [21:59:15] |
* |
springmeyer has quit IRC |
| [22:09:38] |
<ronny> |
re |
| [22:10:04] |
<ronny> |
Zenom: im wondering if i should try sqlalchemy-migrate on this project |
| [22:10:13] |
* |
EnTeQuAk has quit IRC |
| [22:19:26] |
* |
stifal has quit IRC |
| [22:29:15] |
<mardig> |
I have recently installed Werkzeug |
| [22:29:39] |
<mardig> |
and everytime I try to run my django development server |
| [ |