community/pipermail-archives/sup-devel/2013-04.txt (15568B) - raw
1 From eg@gaute.vetsj.com Sat Apr 13 17:37:01 2013
2 From: eg@gaute.vetsj.com (Gaute Hope)
3 Date: Sat, 13 Apr 2013 19:37:01 +0200
4 Subject: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
5 In-Reply-To: <5169925C.1060701@gaute.vetsj.com>
6 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
7 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
8 <51692285.8000709@gaute.vetsj.com>
9 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
10 <51695AF1.2070701@gaute.vetsj.com>
11 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
12 <5169925C.1060701@gaute.vetsj.com>
13 Message-ID: <516997BD.7010409@gaute.vetsj.com>
14
15 If we go sup2 I would suggest the following plan:
16
17 - Release the best we can get with the current code for 1.9.3 as a last
18 community release of sup-0.12, say.. sup-0.13.
19
20 For sup2:
21 - Fork a new repo: sup2
22 - Go for Mail in stead of RMail (index breakage)
23 - Go for only Psych (config breakage), requires psych gem in 1.8
24 - Integrate the IMAP / label sync back stuff (personally this is what I
25 miss the most)
26 - Go for ruby 2.0.0 and maybe 1.8
27 - Get rid of all dependencies that are abandoned or deprecated (ncurses
28 gem..)
29 - Try to do tests on most stuff for different encodings
30 - Try to get UTF-8 / encoding right
31 - Move all the rest of the infrastructure to something the project is in
32 control of
33
34 Would be very nice:
35 - Index migration
36 - Config migration
37
38 For the web page (eventually):
39 - note about the original project
40 - note about the last sup-0.13 release
41 - wiki and project page for sup2
42
43 This plan more or less holds whether we go sup2 or not, but I think it
44 is easier to get rid of the hopeless dependencies.
45
46 @sup-devel readers: discussion is currently at sup-talk, please send any
47 responses there.
48
49 Regards, Gaute
50
51 On 13. april 2013 19:14, Gaute Hope wrote:
52 >
53 >
54 > On 13. april 2013 18:35, Jonathan Lassoff wrote:
55 >> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
56 >>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
57 >>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
58 >>>>> Hi,
59 >>>>>
60 >>>>> Jonathan: I put your commit into a pull request at:
61 >>>>> - https://github.com/sup-heliotrope/sup/pull/19
62 >>>>>
63 >>>>> Also, re-branding and updating to web-references:
64 >>>>> - https://github.com/sup-heliotrope/sup/pull/20
65 >>>>>
66 >>>>> any comments on this? You can see the changes I made. I have absolutely
67 >>>>> no intentions of stepping on any toes, but this is a suggestion.
68 >>>>
69 >>>> No, thank you very much! That looks great!
70 >>>>
71 >>>>> It is a pity that the official home page and probably first search
72 >>>>> results direct to the abandoned home and gem of sup.
73 >>>>
74 >>>> It is too bad. Hopefully William could hand off access or at least
75 >>>> push updates somehow.
76 >>>>
77 >>>> If not, maybe we could stand up another domain pointing to github pages?
78 >>>> Looks like supmua.org and supm.ua are available. :p
79 >>>>
80 >>>> --j
81 >>>
82 >>> Yeah.. I think some web page is pretty essential, perhaps just the
83 >>> standard github-pages domain for a start. Anyone feel up for the task,
84 >>> I'd be happy to add you to the github-organization.
85 >>
86 >> Agreed. I snagged supmua.org for a year, and have it pointing at
87 >> sup-heliotrope.github.io for pages.
88 >>
89 >> Stick me on the org, and I'll see about getting a simple site started.
90 >
91 > Nice. You're on.
92 >
93 > Cheers, Gaute
94 >
95
96 From jof@thejof.com Sat Apr 13 20:48:55 2013
97 From: jof@thejof.com (Jonathan Lassoff)
98 Date: Sat, 13 Apr 2013 13:48:55 -0700
99 Subject: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
100 In-Reply-To: <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
101 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
102 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
103 <51692285.8000709@gaute.vetsj.com>
104 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
105 <51695AF1.2070701@gaute.vetsj.com>
106 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
107 <5169925C.1060701@gaute.vetsj.com>
108 <516997BD.7010409@gaute.vetsj.com>
109 <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
110 Message-ID: <CAHsqw9u6pYeh-y3RLHNRqF5qsMLsdfoku8ZS6SC+f___ptNL1g@mail.gmail.com>
111
112 Maybe William can help out?
113 https://twitter.com/wm/status/323175493367119873
114
115 On Sat, Apr 13, 2013 at 12:19 PM, Jonathan Lassoff <jof at thejof.com> wrote:
116 > On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
117 >> If we go sup2 I would suggest the following plan:
118 >>
119 >> - Release the best we can get with the current code for 1.9.3 as a last
120 >> community release of sup-0.12, say.. sup-0.13.
121 >>
122 >> For sup2:
123 >> - Fork a new repo: sup2
124 >> - Go for Mail in stead of RMail (index breakage)
125 >> - Go for only Psych (config breakage), requires psych gem in 1.8
126 >> - Integrate the IMAP / label sync back stuff (personally this is what I
127 >> miss the most)
128 >> - Go for ruby 2.0.0 and maybe 1.8
129 >> - Get rid of all dependencies that are abandoned or deprecated (ncurses
130 >> gem..)
131 >
132 > And target ncursesw?
133 >
134 >> - Try to do tests on most stuff for different encodings
135 >> - Try to get UTF-8 / encoding right
136 >> - Move all the rest of the infrastructure to something the project is in
137 >> control of
138 >>
139 >> Would be very nice:
140 >> - Index migration
141 >> - Config migration
142 >>
143 >> For the web page (eventually):
144 >> - note about the original project
145 >> - note about the last sup-0.13 release
146 >> - wiki and project page for sup2
147 >>
148 >> This plan more or less holds whether we go sup2 or not, but I think it
149 >> is easier to get rid of the hopeless dependencies.
150 >
151 > I agree that it's worth it to drop unmaintained dependencies and just
152 > fix what breaks.
153 > It would be unfortunate to have to fork the project and make a
154 > different name. I wonder if Morgan has lost interest or is just busy
155 > with other things.
156 >
157 > Cheers,
158 > jof
159 >> @sup-devel readers: discussion is currently at sup-talk, please send any
160 >> responses there.
161 >>
162 >> Regards, Gaute
163 >>
164 >> On 13. april 2013 19:14, Gaute Hope wrote:
165 >>>
166 >>>
167 >>> On 13. april 2013 18:35, Jonathan Lassoff wrote:
168 >>>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
169 >>>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
170 >>>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
171 >>>>>>> Hi,
172 >>>>>>>
173 >>>>>>> Jonathan: I put your commit into a pull request at:
174 >>>>>>> - https://github.com/sup-heliotrope/sup/pull/19
175 >>>>>>>
176 >>>>>>> Also, re-branding and updating to web-references:
177 >>>>>>> - https://github.com/sup-heliotrope/sup/pull/20
178 >>>>>>>
179 >>>>>>> any comments on this? You can see the changes I made. I have absolutely
180 >>>>>>> no intentions of stepping on any toes, but this is a suggestion.
181 >>>>>>
182 >>>>>> No, thank you very much! That looks great!
183 >>>>>>
184 >>>>>>> It is a pity that the official home page and probably first search
185 >>>>>>> results direct to the abandoned home and gem of sup.
186 >>>>>>
187 >>>>>> It is too bad. Hopefully William could hand off access or at least
188 >>>>>> push updates somehow.
189 >>>>>>
190 >>>>>> If not, maybe we could stand up another domain pointing to github pages?
191 >>>>>> Looks like supmua.org and supm.ua are available. :p
192 >>>>>>
193 >>>>>> --j
194 >>>>>
195 >>>>> Yeah.. I think some web page is pretty essential, perhaps just the
196 >>>>> standard github-pages domain for a start. Anyone feel up for the task,
197 >>>>> I'd be happy to add you to the github-organization.
198 >>>>
199 >>>> Agreed. I snagged supmua.org for a year, and have it pointing at
200 >>>> sup-heliotrope.github.io for pages.
201 >>>>
202 >>>> Stick me on the org, and I'll see about getting a simple site started.
203 >>>
204 >>> Nice. You're on.
205 >>>
206 >>> Cheers, Gaute
207 >>>
208
209 From eg@gaute.vetsj.com Sat Apr 13 22:17:32 2013
210 From: eg@gaute.vetsj.com (Gaute Hope)
211 Date: Sun, 14 Apr 2013 00:17:32 +0200
212 Subject: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
213 In-Reply-To: <CAHsqw9u6pYeh-y3RLHNRqF5qsMLsdfoku8ZS6SC+f___ptNL1g@mail.gmail.com>
214 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
215 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
216 <51692285.8000709@gaute.vetsj.com>
217 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
218 <51695AF1.2070701@gaute.vetsj.com>
219 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
220 <5169925C.1060701@gaute.vetsj.com>
221 <516997BD.7010409@gaute.vetsj.com>
222 <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
223 <CAHsqw9u6pYeh-y3RLHNRqF5qsMLsdfoku8ZS6SC+f___ptNL1g@mail.gmail.com>
224 Message-ID: <5169D97C.6020909@gaute.vetsj.com>
225
226 On la. 13. april 2013 kl. 22.48 +0200, Jonathan Lassoff wrote:
227 > Maybe William can help out?
228 > https://twitter.com/wm/status/323175493367119873
229
230 That would be the best ;)
231
232 But I still think we need to get rid of the deprecated and abandoned
233 stuff.
234
235 - gaute
236
237 From dmishd@gmail.com Sun Apr 28 20:32:08 2013
238 From: dmishd@gmail.com (Hamish D)
239 Date: Sun, 28 Apr 2013 21:32:08 +0100
240 Subject: [sup-devel] sup 0.13
241 Message-ID: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
242
243 We'd like to get version 0.13 of sup out soon. There's a fair bit of
244 work gone into sup since 0.12 was released (in January 2011) that it
245 would be good to get out there. Once that is done we can then work on
246 the bigger goals we have for 0.14 - see
247 https://github.com/sup-heliotrope/sup/wiki/Development#roadmap for
248 those plans.
249
250 So the question is, are there any serious bugs that we should fix
251 before releasing 0.13? In particular are there any regressions from
252 0.12. I'm not aware of any at the moment. Looking at the issue list on
253 github, there is:
254
255 Invalid date in ncursesw gemspec for Ruby 1.8
256 https://github.com/sup-heliotrope/sup/issues/18
257
258 This is causing issues for gem installs. #30 is a possible fix that
259 requires testing (by using ncurses-ruby instead of ncursesw). Could
260 people try testing this branch on your own set up?
261
262 Unable to add sources
263 https://github.com/sup-heliotrope/sup/issues/33
264
265 This is another issue we should at least look into before a release.
266 Any testing etc appreciated.
267
268 If you have a burning issue that you think should be fixed in 0.13,
269 please add it to the issue tracker now so we can decide.
270
271 I've also lost track of what's gone on to the develop branch. Should
272 0.13 be based on the master branch or develop?
273
274 Here's hoping we can get 0.13 out soon
275
276 Hamish
277
278 From eg@gaute.vetsj.com Sun Apr 28 20:54:23 2013
279 From: eg@gaute.vetsj.com (Gaute Hope)
280 Date: Sun, 28 Apr 2013 22:54:23 +0200
281 Subject: [sup-devel] sup 0.13
282 In-Reply-To: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
283 References: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
284 Message-ID: <517D8C7F.8050603@gaute.vetsj.com>
285
286 On 28. april 2013 22:32, Hamish D wrote:
287 > I've also lost track of what's gone on to the develop branch. Should
288 > 0.13 be based on the master branch or develop?
289
290 develop should be ready for 0.13.
291
292 I don't know if it is useful; but I set up a few milestones in the tracker.
293
294
295 Cheers, Gaute
296
297 From isra@herraiz.org Mon Apr 29 11:02:36 2013
298 From: isra@herraiz.org (Israel Herraiz)
299 Date: Mon, 29 Apr 2013 13:02:36 +0200
300 Subject: [sup-devel] sup 0.13
301 In-Reply-To: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
302 References: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
303 Message-ID: <1367233230-sup-3593@tesla>
304
305 Excerpts from Hamish D's message of Sun Apr 28 22:32:08 +0200 2013:
306 > So the question is, are there any serious bugs that we should fix
307 > before releasing 0.13? In particular are there any regressions from
308 > 0.12. I'm not aware of any at the moment.
309
310 I read the following in the roadmap:
311
312 "Release sup-0.13 very soon: will not include maildir support or
313 work on Ruby 2."
314
315 Does that mean that maildir support will be dropped? Or is it related
316 to maildir syncback? Will I be able to read maildirs using Sup 0.13?
317
318 Cheers,
319 Israel
320
321 From eg@gaute.vetsj.com Mon Apr 29 11:39:04 2013
322 From: eg@gaute.vetsj.com (Gaute Hope)
323 Date: Mon, 29 Apr 2013 13:39:04 +0200
324 Subject: [sup-devel] sup 0.13
325 In-Reply-To: <1367233230-sup-3593@tesla>
326 References: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
327 <1367233230-sup-3593@tesla>
328 Message-ID: <517E5BD8.6030803@gaute.vetsj.com>
329
330
331
332 On 29. april 2013 13:02, Israel Herraiz wrote:
333 > Excerpts from Hamish D's message of Sun Apr 28 22:32:08 +0200 2013:
334 >> So the question is, are there any serious bugs that we should fix
335 >> before releasing 0.13? In particular are there any regressions from
336 >> 0.12. I'm not aware of any at the moment.
337 >
338 > I read the following in the roadmap:
339 >
340 > "Release sup-0.13 very soon: will not include maildir support or
341 > work on Ruby 2."
342 >
343 > Does that mean that maildir support will be dropped? Or is it related
344 > to maildir syncback? Will I be able to read maildirs using Sup 0.13?
345
346 err.. that should have been syncback. maildir support will stay as it is.
347
348 Cheers, Gaute
349
350 From hsanson@gmail.com Tue Apr 30 09:44:56 2013
351 From: hsanson@gmail.com (Horacio Sanson)
352 Date: Tue, 30 Apr 2013 18:44:56 +0900
353 Subject: [sup-devel] sup 0.13
354 In-Reply-To: <517E5BD8.6030803@gaute.vetsj.com>
355 References: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
356 <1367233230-sup-3593@tesla> <517E5BD8.6030803@gaute.vetsj.com>
357 Message-ID: <CAHWBo_aKjp__dkjuJ-tYHpKJuv2G=k_jxTWMo0QyyUtvxZbGXA@mail.gmail.com>
358
359 Great to see Sup getting back on track again..
360
361 I submitted some patches for the Gmail dumper of Heliotrope some time ago
362 but the lack of non alphabet languages (Japanese, Chinese) made it
363 impossible for me to keep using heliotrope/turnesole.
364
365 The main issue to support Japanese/Chinese with heliotrope was that
366 whistlepig (indexer) lacked the ability to tokenize these languages. Also
367 the half baked UTF-8 support caused several issues with these languages.
368
369 I would like to help in testing/implementing support for these languages,
370 starting with Japanese, but I would require some guidance. First I would
371 like to know is there is a way to configure the Xapian tokenizer
372 (segmenter) within sup? Please consider that I am new to both sup and to
373 Xapian.
374
375 Also considering that development of ruby 1.8.x is going to be discontinued
376 on June 2013 I don't find necessary to keep compatibility with it. This
377 would improve UTF-8 support and eliminate the hacks required to support
378 UTF-8 on ruby 1.8.x installations.
379
380 regards,
381 Horacio
382
383
384
385 On Mon, Apr 29, 2013 at 8:39 PM, Gaute Hope <eg at gaute.vetsj.com> wrote:
386
387 >
388 >
389 > On 29. april 2013 13:02, Israel Herraiz wrote:
390 > > Excerpts from Hamish D's message of Sun Apr 28 22:32:08 +0200 2013:
391 > >> So the question is, are there any serious bugs that we should fix
392 > >> before releasing 0.13? In particular are there any regressions from
393 > >> 0.12. I'm not aware of any at the moment.
394 > >
395 > > I read the following in the roadmap:
396 > >
397 > > "Release sup-0.13 very soon: will not include maildir support or
398 > > work on Ruby 2."
399 > >
400 > > Does that mean that maildir support will be dropped? Or is it related
401 > > to maildir syncback? Will I be able to read maildirs using Sup 0.13?
402 >
403 > err.. that should have been syncback. maildir support will stay as it is.
404 >
405 > Cheers, Gaute
406 > _______________________________________________
407 > Sup-devel mailing list
408 > Sup-devel at rubyforge.org
409 > http://rubyforge.org/mailman/listinfo/sup-devel
410 >
411 -------------- next part --------------
412 An HTML attachment was scrubbed...
413 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20130430/22c4fa84/attachment.html>
414