1 2014-05-19T01:19:05 *** magu_cic_
2 2014-05-19T01:21:54 *** magu_cic
3 2014-05-19T08:16:09 <ThomasWaldmann> moin
4 2014-05-19T08:17:48 <dimazest> morning
5 2014-05-19T08:20:12 <ThomasWaldmann> today is first day of coding phase
6 2014-05-19T08:20:37 <ThomasWaldmann> dimazest: did you discuss with your student already? I didn't see much communication.
7 2014-05-19T08:22:23 <dimazest> we discussed a bit
8 2014-05-19T08:22:50 <dimazest> we discuss here and on the etherpad http://etherpad.osuosl.org/moin-ticket-blog
9 2014-05-19T08:27:25 <dimazest> ThomasWaldmann: If I undersdand correctly, on update the name of an item is reset to None. So the original name is lost. Is this desired behaviour?
10 2014-05-19T08:42:38 <ThomasWaldmann> https://dudle.inf.tu-dresden.de/moin_gsoc2014_weekly/
11 2014-05-19T08:43:01 <ThomasWaldmann> dimazest: waldi: ^
12 2014-05-19T08:43:36 <ThomasWaldmann> RogerHaase also needs the url, so please give it to him when he returns.
13 2014-05-19T08:43:54 * ThomasWaldmann wanted to try a doodle alternative
14 2014-05-19T08:45:11 <ThomasWaldmann> dimazest: please give the line number on the EP you are referring to
15 2014-05-19T08:48:39 <ThomasWaldmann> dimazest: it is unclear whether you refer to blog posts, tickets or items in general
16 2014-05-19T08:49:07 <dimazest> it's about tickets
17 2014-05-19T08:49:30 <ThomasWaldmann> as a general answer, items are not expected to lose any metadata on update
18 2014-05-19T08:49:51 <ThomasWaldmann> but also items are not required to have name(s)
19 2014-05-19T08:53:09 <dimazest> ok, then we need to check this two usecases
20 2014-05-19T08:53:25 <ThomasWaldmann> (that's at least the goal, the code might have bugs so it does not yet work that way)
21 2014-05-19T08:53:36 <ThomasWaldmann> (or missing api refactoring)
22 2014-05-19T08:55:06 <dimazest> knowing a goal is a good beginning, so we change the code that should be changed, instead of breaking code that works
23 2014-05-19T08:56:23 <dimazest> should we ask skathpalia to be connected to irc all the time, so he doesn't miss any conversation?
24 2014-05-19T08:57:34 <dimazest> is there a server, where he could run irssi. i personally use, irccloud.com, but it's a paid service
25 2014-05-19T08:58:56 <ThomasWaldmann> every gsoc participant should be connected frequently to irc
26 2014-05-19T08:59:19 <ThomasWaldmann> either always-online at work times (if possible)
27 2014-05-19T08:59:39 <ThomasWaldmann> or using a screen session on a always-on server (I can provide that on request)
28 2014-05-19T09:00:03 <dimazest> screen session would be the best :)
29 2014-05-19T09:00:03 <ThomasWaldmann> or at least reading the logs of this channel posted on the moin wiki
30 2014-05-19T09:00:50 <dimazest> right, that also an option, though if a person is not on the channel, it's hard to refer to him/her
31 2014-05-19T09:00:54 <ThomasWaldmann> everybody needing a shell account just sends me an email
32 2014-05-19T09:01:16 <dimazest> i'll discuss this with skathpalia
33 2014-05-19T09:13:02 *** greg_f
34 2014-05-19T09:15:00 <ThomasWaldmann> i added some conceptual stuff on EP 125
35 2014-05-19T09:16:46 * ThomasWaldmann gtg
36 2014-05-19T09:23:20 <ananasova> @item_modified.connect_via(ANY)
37 2014-05-19T09:23:20 <moinBot> ananasova: Error: "item_modified.connect_via(ANY)" is not a valid command.
38 2014-05-19T09:23:29 <ananasova> moin
39 2014-05-19T09:23:42 <ananasova> that was accidental :)
40 2014-05-19T09:42:41 <dimazest> hey, a completely out of topic question
41 2014-05-19T09:43:12 <dimazest> i might be involved with the university web development course, and I proposed to use python instead of php
42 2014-05-19T09:43:22 <dimazest> do you think it's a good idea?
43 2014-05-19T09:47:37 <ananasova> it always depends on so many factors... it might be simply a matter of preference
44 2014-05-19T09:49:30 <ananasova> or it might be*
45 2014-05-19T09:50:00 <dimazest> since i'm lobbing for python, my preference is clear :) some people say that python might be too difficult for students
46 2014-05-19T09:53:23 <ananasova> many times it becomes the starting point for some students, so i doubt it is difficult to learn
47 2014-05-19T09:55:02 <ananasova> and since this is a community that likes and uses python a lot, it is clear everybody sees lots of benefits of choosing python over php
48 2014-05-19T10:08:01 *** randomax
49 2014-05-19T10:47:20 *** derdon
50 2014-05-19T10:49:59 *** randomax
51 2014-05-19T10:50:25 *** randomax
52 2014-05-19T10:59:39 *** derdon
53 2014-05-19T11:03:46 *** skathpalia
54 2014-05-19T11:03:50 <skathpalia> moin
55 2014-05-19T11:05:05 <dimazest> hello
56 2014-05-19T11:05:22 <skathpalia> dimazest, hi
57 2014-05-19T11:05:44 <dimazest> skathpalia: it would be cool if you manage to be connected to irc all the time
58 2014-05-19T11:06:03 <dimazest> then you don't need to check logs and won't miss any important conversation
59 2014-05-19T11:06:10 <skathpalia> Ok will try to do that
60 2014-05-19T11:06:23 <dimazest> ThomasWaldmann can setup a shell access for you
61 2014-05-19T11:06:41 <dimazest> when you can run irsii inside of screen
62 2014-05-19T11:06:58 <dimazest> so you can reconnect to it whenever you want
63 2014-05-19T11:08:25 <dimazest> it's the first day of the coding summer, right :)
64 2014-05-19T11:08:50 <skathpalia> Yeah
65 2014-05-19T11:09:22 <skathpalia> one thing we can do regarding that assert statement "name is not None" we can send fqname instead of name and then fetch ITEMID from this fqname and in this line https://bitbucket.org/thomaswaldmann/moin-2.0/src/4a997d9f5e26515b90c744582be8aa7393bb57d1/MoinMoin/util/notifications.py?at=default#cl-187 we will use that fetched ITEMID from fqname
66 2014-05-19T11:09:52 <ananasova> skathpalia: moin
67 2014-05-19T11:10:01 <ananasova> skathpalia: did you check my response?
68 2014-05-19T11:11:35 <dimazest> is it true that on update name is lost (reset)
69 2014-05-19T11:11:55 <skathpalia> Then it won't matter even if name is None
70 2014-05-19T11:11:55 <skathpalia> ananasova, Hi
71 2014-05-19T11:11:56 <skathpalia> And also notifications will be sent using fqname
72 2014-05-19T11:12:09 <skathpalia> Yeah
73 2014-05-19T11:12:11 <dimazest> if it is, then we need to fix it, as the metadata should not change (see ThomasWaldmann reply)
74 2014-05-19T11:12:41 <skathpalia> I have discussed the same with him.
75 2014-05-19T11:12:47 <dimazest> sending fqname is good
76 2014-05-19T11:13:02 <skathpalia> He also said that there should not be any name field in the tickets
77 2014-05-19T11:13:18 <skathpalia> name is just used for one time creation
78 2014-05-19T11:13:31 <dimazest> (we need to be sure that we fix the bug, not build a workaround)
79 2014-05-19T11:13:52 <dimazest> what do you mean by one time creation?
80 2014-05-19T11:14:57 <skathpalia> Oh I thought that you wrote that part didn't see the colo
81 2014-05-19T11:15:01 <skathpalia> *color
82 2014-05-19T11:15:37 <skathpalia> I mean that we create items by 127.0.0.1/"name of item"
83 2014-05-19T11:15:51 <skathpalia> then that name os given to the item
84 2014-05-19T11:16:05 <skathpalia> In case of tickets this name is used only for creation
85 2014-05-19T11:16:23 <skathpalia> I asked xiaq also regarding this part
86 2014-05-19T11:17:11 <skathpalia> ananasova, Yeah I saw that
87 2014-05-19T11:21:03 <dimazest> ok, now i got it
88 2014-05-19T11:23:58 <skathpalia> dimazest, if we want that there should not be any change in meta data on updation then we have to see some other method to create Ticket items
89 2014-05-19T11:24:28 <skathpalia> I mean not by just adding some name after 127.0.0.1/
90 2014-05-19T11:24:54 <dimazest> i mean changes in metadata are ok
91 2014-05-19T11:26:06 <dimazest> but if you change the content of a ticket, and then the name is set to None (without user saying so), then this is rather strange behavior
92 2014-05-19T11:27:08 <skathpalia> Yeah choosing a different method for creating new items also would be strange
93 2014-05-19T11:27:23 <skathpalia> for ticket items
94 2014-05-19T11:28:15 <skathpalia> Also we can add some instructions to create a ticket item(just 2-3 line on ticket page)
95 2014-05-19T11:28:46 <skathpalia> so that user knows how to handle
96 2014-05-19T11:29:39 <dimazest> sounds reasonable
97 2014-05-19T11:33:19 *** skathpalia
98 2014-05-19T11:46:35 *** skathpalia
99 2014-05-19T11:54:46 <skathpalia> dimazest, Now I am now working on making ticket "update" and "update and close" work properly
100 2014-05-19T11:55:23 <skathpalia> Also in the dropdown lists of Superseded by and depends on we will have ITEMIDS displayed
101 2014-05-19T11:59:41 *** randomax
102 2014-05-19T12:15:10 *** randomax
103 2014-05-19T12:55:01 *** skathpalia
104 2014-05-19T12:57:53 *** randomax
105 2014-05-19T13:06:43 *** dave_largo
106 2014-05-19T13:10:54 *** skathpalia
107 2014-05-19T14:13:56 *** randomax
108 2014-05-19T14:28:49 *** randomax
109 2014-05-19T14:52:25 *** skathpalia
110 2014-05-19T15:07:36 *** RogerHaase
111 2014-05-19T15:41:57 *** skathpalia
112 2014-05-19T15:58:05 <skathpalia> moin
113 2014-05-19T15:59:56 *** randomax
114 2014-05-19T16:28:46 *** skathpalia
115 2014-05-19T16:34:25 *** skathpalia
116 2014-05-19T16:39:51 <RogerHaase> skathpalia: randomax you should update https://dudle.inf.tu-dresden.de/moin_gsoc2014_weekly/
117 2014-05-19T16:42:46 <skathpalia> RogerHaase, the time mentioned here is UTC or of some other time zone?
118 2014-05-19T16:43:27 <RogerHaase> utc +- 30 minutes
119 2014-05-19T16:43:38 <skathpalia> Ok thanks :)
120 2014-05-19T17:26:10 *** RogerHaase
121 2014-05-19T17:29:25 *** randomax
122 2014-05-19T17:35:30 *** dreimark
123 2014-05-19T17:35:38 *** dreimark
124 2014-05-19T17:50:29 *** greg_f
125 2014-05-19T17:51:10 *** xjjk
126 2014-05-19T18:26:59 *** skathpalia
127 2014-05-19T18:44:12 * ThomasWaldmann at first didn't consider timezones, but now updated everything to utc
128 2014-05-19T18:44:18 <ThomasWaldmann> https://dudle.inf.tu-dresden.de/moin_gsoc2014_weekly/
129 2014-05-19T18:44:37 <ThomasWaldmann> that site has quite some usability issues compared to doodle.com
130 2014-05-19T19:16:26 * ThomasWaldmann sent feedback to dudle author
131 2014-05-19T19:29:34 *** RogerHaase
132 2014-05-19T19:38:02 <RogerHaase> ThomasWaldmann: markdown parser fixes https://codereview.appspot.com/97350046/
133 2014-05-19T19:38:53 <ThomasWaldmann> i still have that open in my browser window :)
134 2014-05-19T19:42:28 <RogerHaase> ThomasWaldmann: OK, sorry to bug you. But also ready to do another update to serialized/items.moin based on these items: http://www.digitalrockart.org/moin2/
135 2014-05-19T19:44:03 <ThomasWaldmann> no problem :) looking at it right now...
136 2014-05-19T19:47:57 <RogerHaase> ThomasWaldmann: also thought about syntax for adding thead and tfoot to moinwiki tables. I rather like the markdown syntax: http://www.digitalrockart.org/moin2/markdown#tables If we want tfoot, maybe add a second line of ----'s.
137 2014-05-19T19:49:16 <RogerHaase> following normal html5 that would be:
138 2014-05-19T19:49:19 <RogerHaase> thead
139 2014-05-19T19:49:22 <RogerHaase> -----------
140 2014-05-19T19:49:24 <RogerHaase> tfoot
141 2014-05-19T19:49:27 <RogerHaase> -------------
142 2014-05-19T19:49:31 <RogerHaase> tbody 1
143 2014-05-19T19:49:35 <RogerHaase> tbody 2
144 2014-05-19T19:50:54 <RogerHaase> less confusing for existing users would be to keep the || rather than markdowns |
145 2014-05-19T19:51:13 <RogerHaase> less/least
146 2014-05-19T19:52:03 <RogerHaase> a variation of that could also work for csv tables
147 2014-05-19T19:53:38 *** jek
148 2014-05-19T19:58:03 *** jek
149 2014-05-19T20:05:49 <ThomasWaldmann> RogerHaase: so for moinwiki, you mean that?:
150 2014-05-19T20:05:56 <ThomasWaldmann> ||foo||bar||
151 2014-05-19T20:06:04 <ThomasWaldmann> ||---||---||
152 2014-05-19T20:08:15 <RogerHaase> yes, (but doing markdown version is OK with me if you prefer that)
153 2014-05-19T20:11:07 <ThomasWaldmann> sometimes stuff gets filled up with blanks to align
154 2014-05-19T20:11:23 <ThomasWaldmann> ||foo||bar ||
155 2014-05-19T20:11:41 <ThomasWaldmann> ||---||--- ||
156 2014-05-19T20:11:49 <ThomasWaldmann> or rather all -------------- ?
157 2014-05-19T20:12:04 <ThomasWaldmann> maybe looks cleaner
158 2014-05-19T20:13:36 <ThomasWaldmann> could be also ========== to be consistent with the ||
159 2014-05-19T20:14:44 * ThomasWaldmann looks at table markup docs
160 2014-05-19T20:15:11 <RogerHaase> a line of all ='s would be easy to type
161 2014-05-19T20:16:53 <RogerHaase> have not written much re stuff, not sure if that is easier or harder to parse
162 2014-05-19T20:18:12 <ThomasWaldmann> what's in general maybe a bit of a problem is that the interpretation of a table row changes depending on another (preceeding or following) row
163 2014-05-19T20:19:11 <ThomasWaldmann> ||foo||
164 2014-05-19T20:19:18 <ThomasWaldmann> =======
165 2014-05-19T20:19:22 <ThomasWaldmann> ||bar||
166 2014-05-19T20:19:24 <ThomasWaldmann> =======
167 2014-05-19T20:19:29 <ThomasWaldmann> ||baz||
168 2014-05-19T20:19:40 <ThomasWaldmann> foo would be thead then, baz tfoot?
169 2014-05-19T20:19:51 <ThomasWaldmann> and bar simple tr
170 2014-05-19T20:21:33 <RogerHaase> no, I would do bar as tfoot.
171 2014-05-19T20:21:58 <ThomasWaldmann> not very visual then, why?
172 2014-05-19T20:23:08 <RogerHaase> I thought that was std html5, but right now haven't found a source that says that.
173 2014-05-19T20:24:09 <ThomasWaldmann> well, the moinwiki markup order is not necessarily related to html(5)
174 2014-05-19T20:26:52 <RogerHaase> yes, putting tfoot at bottom would be better visually, and would be easy to place it at top to please html5 http://www.w3schools.com/tags/tag_tfoot.asp (although I have never found a browser that objected to tfoot at bottom of table
175 2014-05-19T20:30:31 <ThomasWaldmann> they only (verbally) state that thead must be first
176 2014-05-19T20:32:18 <RogerHaase> I am outdated, looks like it was thead > tfoot under html4, but for html5 it can be tbody > tfoot http://www.w3.org/TR/html5/tabular-data.html#the-tfoot-element
177 2014-05-19T20:33:22 <ThomasWaldmann> As a child of a table element, after any caption, colgroup, and thead elements and before any tbody and tr elements, but only if there are no other tfoot elements that are children of the table element.
178 2014-05-19T20:34:13 <RogerHaase> agree, so baz is tfoot, no issues
179 2014-05-19T20:35:07 <ThomasWaldmann> As a child of a table element, after any caption, colgroup, thead, tbody, and tr elements, but only if there are no other tfoot elements that are children of the table element.
180 2014-05-19T20:35:23 <ThomasWaldmann> i somehow don't really understand what they are really saying.
181 2014-05-19T20:36:18 <ThomasWaldmann> and what is IF there are multiple tfoot elements? can there be multiple?
182 2014-05-19T20:37:40 <RogerHaase> there can be only one tfoot within a table == but only if there are no other tfoot elements that are children of the table element.
183 2014-05-19T20:40:48 <ThomasWaldmann> hmm, somehow it rather sounds to me like there could be multiple. but as we generate that html5, we'll only have one anyway.
184 2014-05-19T20:43:03 <RogerHaase> OK, will try to put your foo bar baz syntax into moinwiki_in
185 2014-05-19T20:44:26 <ThomasWaldmann> separate cs please :)
186 2014-05-19T20:44:50 <RogerHaase> ok
187 2014-05-19T20:44:52 <ThomasWaldmann> (and we need to stay compatible with old wiki pages, but i guess this is ok)
188 2014-05-19T20:45:38 <RogerHaase> right, if there are no lines of ==='s, it is all tbody as it is now
189 2014-05-19T20:46:10 <ThomasWaldmann> yup, in 1.9 ===== would interrupt a table and split it into 2
190 2014-05-19T20:46:53 <ThomasWaldmann> but i guess there is no such data as ====== at such a place didn't have any functionality or use case
191 2014-05-19T20:47:29 <ThomasWaldmann> maybe be careful that it doesn't somehow interfere with headings
192 2014-05-19T21:10:34 *** dave_largo
193 2014-05-19T21:33:47 <RogerHaase> ThomasWaldmann: markdown again: https://codereview.appspot.com/97350046/
194 2014-05-19T22:11:10 *** RogerHaase
195 2014-05-19T23:48:49 *** derdon
196
