community/pipermail-archives/sup-talk/2013-04.txt (88748B) - raw
1 From jof@thejof.com Fri Apr 12 18:09:33 2013
2 From: jof@thejof.com (Jonathan Lassoff)
3 Date: Fri, 12 Apr 2013 11:09:33 -0700
4 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
5 Message-ID: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
6
7 I kept hitting this bug that was driving me nuts.
8
9 While editing a message, I'd go to add a recipient that I don't usually email.
10
11 So, I'd leave my draft in a buffer, find a mail from them, and go to
12 update their contact, only to get hit with an undefined method error.
13 This seems to get triggered if you ever set a new alias for a contact
14 that already exists in the contacts list.
15
16 I made a fix on my branch on gitorious.
17 https://gitorious.org/~jofathan/sup/jofathan-sup/commit/7754799bc186833371c7839142270fe65b942ee6
18
19
20 Is anyone still monitoring the sup/mainline repo on gitorious?
21 William Morgan? Are you still active with sup? Does sup need a new maintainer?
22
23 I still use sup every day for my work email, and its my favorite client ever.
24 Maybe it would be useful to have a sup hackers meetup in San Francisco?
25
26
27 The crash was like:
28 [Fri Apr 12 10:04:55 -0700 2013] ERROR: oh crap, an exception
29 ----------------------------------------------------------------
30 I'm very sorry. It seems that an error occurred in Sup. Please
31 accept my sincere apologies. Please submit the contents of
32 /home/jof/.sup/exception-log.txt and a brief report of the
33 circumstances to http://masanjin.net/sup-bugs/ so that I might
34 address this problem. Thank you!
35
36 Sincerely,
37 William
38 ----------------------------------------------------------------
39 --- NoMethodError from thread: main
40 undefined method `email' for "THE_PERSONS_ALIAS_NAME":String
41 /usr/lib/ruby/1.8/sup/contact.rb:33:in `update_alias'
42 (eval):1:in `send'
43 (eval):1:in `update_alias'
44 /usr/lib/ruby/1.8/sup/modes/contact-list-mode.rb:13:in `alias_contact'
45 /usr/lib/ruby/1.8/sup/modes/thread-view-mode.rb:259:in `alias'
46 /usr/lib/ruby/1.8/sup/mode.rb:59:in `send'
47 /usr/lib/ruby/1.8/sup/mode.rb:59:in `handle_input'
48 /usr/lib/ruby/1.8/sup/buffer.rb:278:in `handle_input'
49 /usr/bin/sup-mail:273
50
51 From sdothum@gmail.com Fri Apr 12 18:46:59 2013
52 From: sdothum@gmail.com (Steven Hum)
53 Date: Fri, 12 Apr 2013 14:46:59 -0400
54 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
55 In-Reply-To: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
56 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
57 Message-ID: <1365791858-sup-2898@luna>
58
59
60 There was some activity not long ago by some sup users who are trying to
61 keep sup afloat -- by attempting to rebuild a sup wiki (the original one
62 had degraded horribly w/o a moderator) and look at current state of sup
63 (and its forks?).
64
65 Unfortunately, I don't have those mailing list messages in my archives
66 anymore -- I don't hang onto list mail long. But you should be able to
67 comb the list mail to identify a few people who are trying to spear head
68 this.
69
70 I need to investigate this too.. as I currently use ezyang's fork for
71 imap maildir handling and would be interested if all the good things
72 people have added to sup can be rolled back into an official sup master.
73
74 Regards,
75 Steven
76
77
78 Excerpts from Jonathan Lassoff's message of 2013-04-12 14:09:33 -0400:
79 > I kept hitting this bug that was driving me nuts.
80 >
81 > While editing a message, I'd go to add a recipient that I don't usually email.
82 >
83 > So, I'd leave my draft in a buffer, find a mail from them, and go to
84 > update their contact, only to get hit with an undefined method error.
85 > This seems to get triggered if you ever set a new alias for a contact
86 > that already exists in the contacts list.
87 >
88 > I made a fix on my branch on gitorious.
89 > https://gitorious.org/~jofathan/sup/jofathan-sup/commit/7754799bc186833371c7839142270fe65b942ee6
90 >
91 >
92 > Is anyone still monitoring the sup/mainline repo on gitorious?
93 > William Morgan? Are you still active with sup? Does sup need a new maintainer?
94 >
95 > I still use sup every day for my work email, and its my favorite client ever.
96 > Maybe it would be useful to have a sup hackers meetup in San Francisco?
97 >
98 >
99 > The crash was like:
100 > [Fri Apr 12 10:04:55 -0700 2013] ERROR: oh crap, an exception
101 > ----------------------------------------------------------------
102 > I'm very sorry. It seems that an error occurred in Sup. Please
103 > accept my sincere apologies. Please submit the contents of
104 > /home/jof/.sup/exception-log.txt and a brief report of the
105 > circumstances to http://masanjin.net/sup-bugs/ so that I might
106 > address this problem. Thank you!
107 >
108 > Sincerely,
109 > William
110 > ----------------------------------------------------------------
111 > --- NoMethodError from thread: main
112 > undefined method `email' for "THE_PERSONS_ALIAS_NAME":String
113 > /usr/lib/ruby/1.8/sup/contact.rb:33:in `update_alias'
114 > (eval):1:in `send'
115 > (eval):1:in `update_alias'
116 > /usr/lib/ruby/1.8/sup/modes/contact-list-mode.rb:13:in `alias_contact'
117 > /usr/lib/ruby/1.8/sup/modes/thread-view-mode.rb:259:in `alias'
118 > /usr/lib/ruby/1.8/sup/mode.rb:59:in `send'
119 > /usr/lib/ruby/1.8/sup/mode.rb:59:in `handle_input'
120 > /usr/lib/ruby/1.8/sup/buffer.rb:278:in `handle_input'
121 > /usr/bin/sup-mail:273
122 --
123 "Truth or die."
124
125 Steven Hum
126 5 - 28 Gilmour St
127 Ottawa, ON K2P 0N3
128 email sdothum at gmail.com
129 tel 613.237.9058
130
131 From dmishd@gmail.com Fri Apr 12 19:46:54 2013
132 From: dmishd@gmail.com (Hamish D)
133 Date: Fri, 12 Apr 2013 20:46:54 +0100
134 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
135 In-Reply-To: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
136 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
137 Message-ID: <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
138
139 We've set up https://github.com/sup-heliotrope/sup
140
141 Please feel free to put pull requests up there. And contributions to the
142 new wiki are also very welcome. We have lots of missing pages ...
143
144 https://github.com/sup-heliotrope/sup/wiki
145
146 We have emailed William about this but have had no response. So currently
147 we have no access to publishing gems under the sup name.
148
149 As to a meet up, I'm in England so won't be coming to San Francisco :-P
150
151 > I'm very sorry. It seems that an error occurred in Sup. Please
152 > accept my sincere apologies. Please submit the contents of
153 > /home/jof/.sup/exception-log.txt and a brief report of the
154 > circumstances to http://masanjin.net/sup-bugs/ so that I might
155 > address this problem. Thank you!
156 >
157 > Sincerely,
158 > William
159
160 We should update this text ...
161
162 Hamish
163 -------------- next part --------------
164 An HTML attachment was scrubbed...
165 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130412/ea9c04d4/attachment.html>
166
167 From eg@gaute.vetsj.com Sat Apr 13 09:16:53 2013
168 From: eg@gaute.vetsj.com (Gaute Hope)
169 Date: Sat, 13 Apr 2013 11:16:53 +0200
170 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
171 In-Reply-To: <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
172 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
173 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
174 Message-ID: <51692285.8000709@gaute.vetsj.com>
175
176 Hi,
177
178 Jonathan: I put your commit into a pull request at:
179 - https://github.com/sup-heliotrope/sup/pull/19
180
181 Also, re-branding and updating to web-references:
182 - https://github.com/sup-heliotrope/sup/pull/20
183
184 any comments on this? You can see the changes I made. I have absolutely
185 no intentions of stepping on any toes, but this is a suggestion.
186
187 It is a pity that the official home page and probably first search
188 results direct to the abandoned home and gem of sup.
189
190 Regards, Gaute
191
192 On 12. april 2013 21:46, Hamish D wrote:
193 > We've set up https://github.com/sup-heliotrope/sup
194 >
195 > Please feel free to put pull requests up there. And contributions to the
196 > new wiki are also very welcome. We have lots of missing pages ...
197 >
198 > https://github.com/sup-heliotrope/sup/wiki
199 >
200 > We have emailed William about this but have had no response. So currently
201 > we have no access to publishing gems under the sup name.
202 >
203 > As to a meet up, I'm in England so won't be coming to San Francisco :-P
204 >
205 >> I'm very sorry. It seems that an error occurred in Sup. Please
206 >> accept my sincere apologies. Please submit the contents of
207 >> /home/jof/.sup/exception-log.txt and a brief report of the
208 >> circumstances to http://masanjin.net/sup-bugs/ so that I might
209 >> address this problem. Thank you!
210 >>
211 >> Sincerely,
212 >> William
213 >
214 > We should update this text ...
215 >
216 > Hamish
217 >
218 >
219 >
220 > _______________________________________________
221 > sup-talk mailing list
222 > sup-talk at rubyforge.org
223 > http://rubyforge.org/mailman/listinfo/sup-talk
224 >
225
226 From jof@thejof.com Sat Apr 13 10:09:55 2013
227 From: jof@thejof.com (Jonathan Lassoff)
228 Date: Sat, 13 Apr 2013 03:09:55 -0700
229 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
230 In-Reply-To: <51692285.8000709@gaute.vetsj.com>
231 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
232 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
233 <51692285.8000709@gaute.vetsj.com>
234 Message-ID: <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
235
236 On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
237 > Hi,
238 >
239 > Jonathan: I put your commit into a pull request at:
240 > - https://github.com/sup-heliotrope/sup/pull/19
241 >
242 > Also, re-branding and updating to web-references:
243 > - https://github.com/sup-heliotrope/sup/pull/20
244 >
245 > any comments on this? You can see the changes I made. I have absolutely
246 > no intentions of stepping on any toes, but this is a suggestion.
247
248 No, thank you very much! That looks great!
249
250 > It is a pity that the official home page and probably first search
251 > results direct to the abandoned home and gem of sup.
252
253 It is too bad. Hopefully William could hand off access or at least
254 push updates somehow.
255
256 If not, maybe we could stand up another domain pointing to github pages?
257 Looks like supmua.org and supm.ua are available. :p
258
259 --j
260
261 From jof@thejof.com Sat Apr 13 10:06:21 2013
262 From: jof@thejof.com (Jonathan Lassoff)
263 Date: Sat, 13 Apr 2013 03:06:21 -0700
264 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
265 In-Reply-To: <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
266 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
267 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
268 Message-ID: <CAHsqw9vwUsq6AmT9FUanxWuDgoAgHTdq-29cMN8hseZwEyN=6g@mail.gmail.com>
269
270 On Fri, Apr 12, 2013 at 12:46 PM, Hamish D <dmishd at gmail.com> wrote:
271 > We've set up https://github.com/sup-heliotrope/sup
272 >
273 > Please feel free to put pull requests up there. And contributions to the new
274 > wiki are also very welcome. We have lots of missing pages ...
275 >
276 > https://github.com/sup-heliotrope/sup/wiki
277
278 Hey -- that's a most excellent place to put a wiki up. Glad to find
279 where the action's at.
280
281 > We have emailed William about this but have had no response. So currently we
282 > have no access to publishing gems under the sup name.
283 >
284 > As to a meet up, I'm in England so won't be coming to San Francisco :-P
285
286 Oh no worries, I just mention it because I know WIlliam is from
287 somewhere around here. I think he's working in SF now.
288
289 >> I'm very sorry. It seems that an error occurred in Sup. Please
290 >> accept my sincere apologies. Please submit the contents of
291 >> /home/jof/.sup/exception-log.txt and a brief report of the
292 >> circumstances to http://masanjin.net/sup-bugs/ so that I might
293 >> address this problem. Thank you!
294 >>
295 >> Sincerely,
296 >> William
297 >
298 > We should update this text ...
299 >
300 > Hamish
301
302 From matthieu.rakotojaona@gmail.com Sat Apr 13 12:49:46 2013
303 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
304 Date: Sat, 13 Apr 2013 14:49:46 +0200
305 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
306 In-Reply-To: <51692285.8000709@gaute.vetsj.com>
307 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
308 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
309 <51692285.8000709@gaute.vetsj.com>
310 Message-ID: <20130413124946.GA22905@kpad.otokar.looc2011.eu>
311
312 On 04/13, Gaute Hope wrote:
313 > Hi,
314 >
315 > Jonathan: I put your commit into a pull request at:
316 > - https://github.com/sup-heliotrope/sup/pull/19
317 >
318 > Also, re-branding and updating to web-references:
319 > - https://github.com/sup-heliotrope/sup/pull/20
320 >
321 > any comments on this? You can see the changes I made. I have absolutely
322 > no intentions of stepping on any toes, but this is a suggestion.
323 >
324 > It is a pity that the official home page and probably first search
325 > results direct to the abandoned home and gem of sup.
326 >
327 > Regards, Gaute
328
329 I guess it's also the occasion to think about the mailing list. I guess
330 no one has the rights on this one ? I don't see anything in github for
331 this functionality.
332
333 --
334 Matthieu Rakotojaona
335
336 From eg@gaute.vetsj.com Sat Apr 13 13:17:37 2013
337 From: eg@gaute.vetsj.com (Gaute Hope)
338 Date: Sat, 13 Apr 2013 15:17:37 +0200
339 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
340 In-Reply-To: <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
341 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
342 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
343 <51692285.8000709@gaute.vetsj.com>
344 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
345 Message-ID: <51695AF1.2070701@gaute.vetsj.com>
346
347 On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
348 > On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
349 >> Hi,
350 >>
351 >> Jonathan: I put your commit into a pull request at:
352 >> - https://github.com/sup-heliotrope/sup/pull/19
353 >>
354 >> Also, re-branding and updating to web-references:
355 >> - https://github.com/sup-heliotrope/sup/pull/20
356 >>
357 >> any comments on this? You can see the changes I made. I have absolutely
358 >> no intentions of stepping on any toes, but this is a suggestion.
359 >
360 > No, thank you very much! That looks great!
361 >
362 >> It is a pity that the official home page and probably first search
363 >> results direct to the abandoned home and gem of sup.
364 >
365 > It is too bad. Hopefully William could hand off access or at least
366 > push updates somehow.
367 >
368 > If not, maybe we could stand up another domain pointing to github pages?
369 > Looks like supmua.org and supm.ua are available. :p
370 >
371 > --j
372
373 Yeah.. I think some web page is pretty essential, perhaps just the
374 standard github-pages domain for a start. Anyone feel up for the task,
375 I'd be happy to add you to the github-organization.
376
377 Regards, Gaute
378
379
380 From eg@gaute.vetsj.com Sat Apr 13 13:29:08 2013
381 From: eg@gaute.vetsj.com (Gaute Hope)
382 Date: Sat, 13 Apr 2013 15:29:08 +0200
383 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
384 In-Reply-To: <20130413124946.GA22905@kpad.otokar.looc2011.eu>
385 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
386 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
387 <51692285.8000709@gaute.vetsj.com>
388 <20130413124946.GA22905@kpad.otokar.looc2011.eu>
389 Message-ID: <51695DA4.4030906@gaute.vetsj.com>
390
391 On 13. april 2013 14:49, Matthieu Rakotojaona wrote:
392 > I guess it's also the occasion to think about the mailing list. I guess
393 > no one has the rights on this one ? I don't see anything in github for
394 > this functionality.
395
396
397 Yup - maybe its time for 'sup2' - from rubyforge:
398
399 http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned
400
401 Project xyz seems to be abandoned. Can you pass it to me?
402
403 This comes up occasionally - a well-named or positioned project gets
404 started, then the project admin falls out of sight and can't be reached.
405 Patches pile up, people start wondering what's going on, and it seems a
406 shame to lose the project name by forking it. So someone will ask if we
407 as RubyForge admins will pass over control of the project to them.
408
409 We really, really, hesitate to transfer admin privileges from one person
410 to another, even if the original admin has completely disappeared. I
411 suspect there are legal complications, and we don't have the budget to
412 deal with those. Furthermore, suppose the original admin has been off on
413 furlough for a year and comes back to find that his project has been
414 moved away from him. Not a pleasant situation.
415
416 In situations where the project admin can't be reached for a long time
417 and folks want to move forward, I suggest forking the project. You're
418 welcome to host a xyz2 version of project xyz on RubyForge, and if the
419 original admin ever shows up again and wants to hand over the project to
420 you, we can help facilitate that.
421
422 From sdothum@gmail.com Sat Apr 13 15:42:45 2013
423 From: sdothum@gmail.com (Steven Hum)
424 Date: Sat, 13 Apr 2013 11:42:45 -0400
425 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
426 In-Reply-To: <51695DA4.4030906@gaute.vetsj.com>
427 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
428 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
429 <51692285.8000709@gaute.vetsj.com>
430 <20130413124946.GA22905@kpad.otokar.looc2011.eu>
431 <51695DA4.4030906@gaute.vetsj.com>
432 Message-ID: <1365867255-sup-1309@luna>
433
434
435 I was thinking the same, that it may be time for a sup2 repository.
436
437 This is very premature, but are there any thoughts to integrate some of
438 the work done in the sup forks. I am thinking in particular of the imap
439 work ezyang did -- I adopted his fork as he seemed to be the most active
440 with regards to imap folder handling, notably propagating updates.
441
442 It would be nice to consolidate the features many of these forks
443 addressed.. though, I have no idea how this can be easily facilitated.
444
445 Regards,
446 Steven
447
448 Excerpts from Gaute Hope's message of 2013-04-13 09:29:08 -0400:
449 > On 13. april 2013 14:49, Matthieu Rakotojaona wrote:
450 > > I guess it's also the occasion to think about the mailing list. I guess
451 > > no one has the rights on this one ? I don't see anything in github for
452 > > this functionality.
453 >
454 >
455 > Yup - maybe its time for 'sup2' - from rubyforge:
456 >
457 > http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned
458 >
459 > Project xyz seems to be abandoned. Can you pass it to me?
460 >
461 > This comes up occasionally - a well-named or positioned project gets
462 > started, then the project admin falls out of sight and can't be reached.
463 > Patches pile up, people start wondering what's going on, and it seems a
464 > shame to lose the project name by forking it. So someone will ask if we
465 > as RubyForge admins will pass over control of the project to them.
466 >
467 > We really, really, hesitate to transfer admin privileges from one person
468 > to another, even if the original admin has completely disappeared. I
469 > suspect there are legal complications, and we don't have the budget to
470 > deal with those. Furthermore, suppose the original admin has been off on
471 > furlough for a year and comes back to find that his project has been
472 > moved away from him. Not a pleasant situation.
473 >
474 > In situations where the project admin can't be reached for a long time
475 > and folks want to move forward, I suggest forking the project. You're
476 > welcome to host a xyz2 version of project xyz on RubyForge, and if the
477 > original admin ever shows up again and wants to hand over the project to
478 > you, we can help facilitate that.
479 --
480 "Truth or die."
481
482 Steven Hum
483 5 - 28 Gilmour St
484 Ottawa, ON K2P 0N3
485 email sdothum at gmail.com
486 tel 613.237.9058
487
488 From jof@thejof.com Sat Apr 13 16:35:53 2013
489 From: jof@thejof.com (Jonathan Lassoff)
490 Date: Sat, 13 Apr 2013 09:35:53 -0700
491 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
492 In-Reply-To: <51695AF1.2070701@gaute.vetsj.com>
493 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
494 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
495 <51692285.8000709@gaute.vetsj.com>
496 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
497 <51695AF1.2070701@gaute.vetsj.com>
498 Message-ID: <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
499
500 On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
501 > On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
502 >> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
503 >>> Hi,
504 >>>
505 >>> Jonathan: I put your commit into a pull request at:
506 >>> - https://github.com/sup-heliotrope/sup/pull/19
507 >>>
508 >>> Also, re-branding and updating to web-references:
509 >>> - https://github.com/sup-heliotrope/sup/pull/20
510 >>>
511 >>> any comments on this? You can see the changes I made. I have absolutely
512 >>> no intentions of stepping on any toes, but this is a suggestion.
513 >>
514 >> No, thank you very much! That looks great!
515 >>
516 >>> It is a pity that the official home page and probably first search
517 >>> results direct to the abandoned home and gem of sup.
518 >>
519 >> It is too bad. Hopefully William could hand off access or at least
520 >> push updates somehow.
521 >>
522 >> If not, maybe we could stand up another domain pointing to github pages?
523 >> Looks like supmua.org and supm.ua are available. :p
524 >>
525 >> --j
526 >
527 > Yeah.. I think some web page is pretty essential, perhaps just the
528 > standard github-pages domain for a start. Anyone feel up for the task,
529 > I'd be happy to add you to the github-organization.
530
531 Agreed. I snagged supmua.org for a year, and have it pointing at
532 sup-heliotrope.github.io for pages.
533
534 Stick me on the org, and I'll see about getting a simple site started.
535
536 Cheers,
537 jof
538
539 From eg@gaute.vetsj.com Sat Apr 13 17:14:04 2013
540 From: eg@gaute.vetsj.com (Gaute Hope)
541 Date: Sat, 13 Apr 2013 19:14:04 +0200
542 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
543 In-Reply-To: <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
544 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
545 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
546 <51692285.8000709@gaute.vetsj.com>
547 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
548 <51695AF1.2070701@gaute.vetsj.com>
549 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
550 Message-ID: <5169925C.1060701@gaute.vetsj.com>
551
552
553
554 On 13. april 2013 18:35, Jonathan Lassoff wrote:
555 > On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
556 >> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
557 >>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
558 >>>> Hi,
559 >>>>
560 >>>> Jonathan: I put your commit into a pull request at:
561 >>>> - https://github.com/sup-heliotrope/sup/pull/19
562 >>>>
563 >>>> Also, re-branding and updating to web-references:
564 >>>> - https://github.com/sup-heliotrope/sup/pull/20
565 >>>>
566 >>>> any comments on this? You can see the changes I made. I have absolutely
567 >>>> no intentions of stepping on any toes, but this is a suggestion.
568 >>>
569 >>> No, thank you very much! That looks great!
570 >>>
571 >>>> It is a pity that the official home page and probably first search
572 >>>> results direct to the abandoned home and gem of sup.
573 >>>
574 >>> It is too bad. Hopefully William could hand off access or at least
575 >>> push updates somehow.
576 >>>
577 >>> If not, maybe we could stand up another domain pointing to github pages?
578 >>> Looks like supmua.org and supm.ua are available. :p
579 >>>
580 >>> --j
581 >>
582 >> Yeah.. I think some web page is pretty essential, perhaps just the
583 >> standard github-pages domain for a start. Anyone feel up for the task,
584 >> I'd be happy to add you to the github-organization.
585 >
586 > Agreed. I snagged supmua.org for a year, and have it pointing at
587 > sup-heliotrope.github.io for pages.
588 >
589 > Stick me on the org, and I'll see about getting a simple site started.
590
591 Nice. You're on.
592
593 Cheers, Gaute
594
595 From eg@gaute.vetsj.com Sat Apr 13 17:37:01 2013
596 From: eg@gaute.vetsj.com (Gaute Hope)
597 Date: Sat, 13 Apr 2013 19:37:01 +0200
598 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
599 In-Reply-To: <5169925C.1060701@gaute.vetsj.com>
600 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
601 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
602 <51692285.8000709@gaute.vetsj.com>
603 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
604 <51695AF1.2070701@gaute.vetsj.com>
605 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
606 <5169925C.1060701@gaute.vetsj.com>
607 Message-ID: <516997BD.7010409@gaute.vetsj.com>
608
609 If we go sup2 I would suggest the following plan:
610
611 - Release the best we can get with the current code for 1.9.3 as a last
612 community release of sup-0.12, say.. sup-0.13.
613
614 For sup2:
615 - Fork a new repo: sup2
616 - Go for Mail in stead of RMail (index breakage)
617 - Go for only Psych (config breakage), requires psych gem in 1.8
618 - Integrate the IMAP / label sync back stuff (personally this is what I
619 miss the most)
620 - Go for ruby 2.0.0 and maybe 1.8
621 - Get rid of all dependencies that are abandoned or deprecated (ncurses
622 gem..)
623 - Try to do tests on most stuff for different encodings
624 - Try to get UTF-8 / encoding right
625 - Move all the rest of the infrastructure to something the project is in
626 control of
627
628 Would be very nice:
629 - Index migration
630 - Config migration
631
632 For the web page (eventually):
633 - note about the original project
634 - note about the last sup-0.13 release
635 - wiki and project page for sup2
636
637 This plan more or less holds whether we go sup2 or not, but I think it
638 is easier to get rid of the hopeless dependencies.
639
640 @sup-devel readers: discussion is currently at sup-talk, please send any
641 responses there.
642
643 Regards, Gaute
644
645 On 13. april 2013 19:14, Gaute Hope wrote:
646 >
647 >
648 > On 13. april 2013 18:35, Jonathan Lassoff wrote:
649 >> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
650 >>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
651 >>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
652 >>>>> Hi,
653 >>>>>
654 >>>>> Jonathan: I put your commit into a pull request at:
655 >>>>> - https://github.com/sup-heliotrope/sup/pull/19
656 >>>>>
657 >>>>> Also, re-branding and updating to web-references:
658 >>>>> - https://github.com/sup-heliotrope/sup/pull/20
659 >>>>>
660 >>>>> any comments on this? You can see the changes I made. I have absolutely
661 >>>>> no intentions of stepping on any toes, but this is a suggestion.
662 >>>>
663 >>>> No, thank you very much! That looks great!
664 >>>>
665 >>>>> It is a pity that the official home page and probably first search
666 >>>>> results direct to the abandoned home and gem of sup.
667 >>>>
668 >>>> It is too bad. Hopefully William could hand off access or at least
669 >>>> push updates somehow.
670 >>>>
671 >>>> If not, maybe we could stand up another domain pointing to github pages?
672 >>>> Looks like supmua.org and supm.ua are available. :p
673 >>>>
674 >>>> --j
675 >>>
676 >>> Yeah.. I think some web page is pretty essential, perhaps just the
677 >>> standard github-pages domain for a start. Anyone feel up for the task,
678 >>> I'd be happy to add you to the github-organization.
679 >>
680 >> Agreed. I snagged supmua.org for a year, and have it pointing at
681 >> sup-heliotrope.github.io for pages.
682 >>
683 >> Stick me on the org, and I'll see about getting a simple site started.
684 >
685 > Nice. You're on.
686 >
687 > Cheers, Gaute
688 >
689
690 From jof@thejof.com Sat Apr 13 19:15:10 2013
691 From: jof@thejof.com (Jonathan Lassoff)
692 Date: Sat, 13 Apr 2013 12:15:10 -0700
693 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
694 In-Reply-To: <5169925C.1060701@gaute.vetsj.com>
695 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
696 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
697 <51692285.8000709@gaute.vetsj.com>
698 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
699 <51695AF1.2070701@gaute.vetsj.com>
700 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
701 <5169925C.1060701@gaute.vetsj.com>
702 Message-ID: <CAHsqw9s4GkmVZucuAd6pep_db-jr73QhRqBqEyZ6rudyR+pzGQ@mail.gmail.com>
703
704 http://supmua.org/
705
706 Just tossed this, up but it's mostly stuff from the old rubyforge page.
707
708 On Sat, Apr 13, 2013 at 10:14 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
709 >
710 >
711 > On 13. april 2013 18:35, Jonathan Lassoff wrote:
712 >> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
713 >>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
714 >>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
715 >>>>> Hi,
716 >>>>>
717 >>>>> Jonathan: I put your commit into a pull request at:
718 >>>>> - https://github.com/sup-heliotrope/sup/pull/19
719 >>>>>
720 >>>>> Also, re-branding and updating to web-references:
721 >>>>> - https://github.com/sup-heliotrope/sup/pull/20
722 >>>>>
723 >>>>> any comments on this? You can see the changes I made. I have absolutely
724 >>>>> no intentions of stepping on any toes, but this is a suggestion.
725 >>>>
726 >>>> No, thank you very much! That looks great!
727 >>>>
728 >>>>> It is a pity that the official home page and probably first search
729 >>>>> results direct to the abandoned home and gem of sup.
730 >>>>
731 >>>> It is too bad. Hopefully William could hand off access or at least
732 >>>> push updates somehow.
733 >>>>
734 >>>> If not, maybe we could stand up another domain pointing to github pages?
735 >>>> Looks like supmua.org and supm.ua are available. :p
736 >>>>
737 >>>> --j
738 >>>
739 >>> Yeah.. I think some web page is pretty essential, perhaps just the
740 >>> standard github-pages domain for a start. Anyone feel up for the task,
741 >>> I'd be happy to add you to the github-organization.
742 >>
743 >> Agreed. I snagged supmua.org for a year, and have it pointing at
744 >> sup-heliotrope.github.io for pages.
745 >>
746 >> Stick me on the org, and I'll see about getting a simple site started.
747 >
748 > Nice. You're on.
749 >
750 > Cheers, Gaute
751
752 From jof@thejof.com Sat Apr 13 19:19:17 2013
753 From: jof@thejof.com (Jonathan Lassoff)
754 Date: Sat, 13 Apr 2013 12:19:17 -0700
755 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
756 In-Reply-To: <516997BD.7010409@gaute.vetsj.com>
757 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
758 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
759 <51692285.8000709@gaute.vetsj.com>
760 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
761 <51695AF1.2070701@gaute.vetsj.com>
762 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
763 <5169925C.1060701@gaute.vetsj.com>
764 <516997BD.7010409@gaute.vetsj.com>
765 Message-ID: <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
766
767 On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
768 > If we go sup2 I would suggest the following plan:
769 >
770 > - Release the best we can get with the current code for 1.9.3 as a last
771 > community release of sup-0.12, say.. sup-0.13.
772 >
773 > For sup2:
774 > - Fork a new repo: sup2
775 > - Go for Mail in stead of RMail (index breakage)
776 > - Go for only Psych (config breakage), requires psych gem in 1.8
777 > - Integrate the IMAP / label sync back stuff (personally this is what I
778 > miss the most)
779 > - Go for ruby 2.0.0 and maybe 1.8
780 > - Get rid of all dependencies that are abandoned or deprecated (ncurses
781 > gem..)
782
783 And target ncursesw?
784
785 > - Try to do tests on most stuff for different encodings
786 > - Try to get UTF-8 / encoding right
787 > - Move all the rest of the infrastructure to something the project is in
788 > control of
789 >
790 > Would be very nice:
791 > - Index migration
792 > - Config migration
793 >
794 > For the web page (eventually):
795 > - note about the original project
796 > - note about the last sup-0.13 release
797 > - wiki and project page for sup2
798 >
799 > This plan more or less holds whether we go sup2 or not, but I think it
800 > is easier to get rid of the hopeless dependencies.
801
802 I agree that it's worth it to drop unmaintained dependencies and just
803 fix what breaks.
804 It would be unfortunate to have to fork the project and make a
805 different name. I wonder if Morgan has lost interest or is just busy
806 with other things.
807
808 Cheers,
809 jof
810 > @sup-devel readers: discussion is currently at sup-talk, please send any
811 > responses there.
812 >
813 > Regards, Gaute
814 >
815 > On 13. april 2013 19:14, Gaute Hope wrote:
816 >>
817 >>
818 >> On 13. april 2013 18:35, Jonathan Lassoff wrote:
819 >>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
820 >>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
821 >>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
822 >>>>>> Hi,
823 >>>>>>
824 >>>>>> Jonathan: I put your commit into a pull request at:
825 >>>>>> - https://github.com/sup-heliotrope/sup/pull/19
826 >>>>>>
827 >>>>>> Also, re-branding and updating to web-references:
828 >>>>>> - https://github.com/sup-heliotrope/sup/pull/20
829 >>>>>>
830 >>>>>> any comments on this? You can see the changes I made. I have absolutely
831 >>>>>> no intentions of stepping on any toes, but this is a suggestion.
832 >>>>>
833 >>>>> No, thank you very much! That looks great!
834 >>>>>
835 >>>>>> It is a pity that the official home page and probably first search
836 >>>>>> results direct to the abandoned home and gem of sup.
837 >>>>>
838 >>>>> It is too bad. Hopefully William could hand off access or at least
839 >>>>> push updates somehow.
840 >>>>>
841 >>>>> If not, maybe we could stand up another domain pointing to github pages?
842 >>>>> Looks like supmua.org and supm.ua are available. :p
843 >>>>>
844 >>>>> --j
845 >>>>
846 >>>> Yeah.. I think some web page is pretty essential, perhaps just the
847 >>>> standard github-pages domain for a start. Anyone feel up for the task,
848 >>>> I'd be happy to add you to the github-organization.
849 >>>
850 >>> Agreed. I snagged supmua.org for a year, and have it pointing at
851 >>> sup-heliotrope.github.io for pages.
852 >>>
853 >>> Stick me on the org, and I'll see about getting a simple site started.
854 >>
855 >> Nice. You're on.
856 >>
857 >> Cheers, Gaute
858 >>
859
860 From jof@thejof.com Sat Apr 13 20:48:55 2013
861 From: jof@thejof.com (Jonathan Lassoff)
862 Date: Sat, 13 Apr 2013 13:48:55 -0700
863 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
864 In-Reply-To: <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
865 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
866 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
867 <51692285.8000709@gaute.vetsj.com>
868 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
869 <51695AF1.2070701@gaute.vetsj.com>
870 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
871 <5169925C.1060701@gaute.vetsj.com>
872 <516997BD.7010409@gaute.vetsj.com>
873 <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
874 Message-ID: <CAHsqw9u6pYeh-y3RLHNRqF5qsMLsdfoku8ZS6SC+f___ptNL1g@mail.gmail.com>
875
876 Maybe William can help out?
877 https://twitter.com/wm/status/323175493367119873
878
879 On Sat, Apr 13, 2013 at 12:19 PM, Jonathan Lassoff <jof at thejof.com> wrote:
880 > On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
881 >> If we go sup2 I would suggest the following plan:
882 >>
883 >> - Release the best we can get with the current code for 1.9.3 as a last
884 >> community release of sup-0.12, say.. sup-0.13.
885 >>
886 >> For sup2:
887 >> - Fork a new repo: sup2
888 >> - Go for Mail in stead of RMail (index breakage)
889 >> - Go for only Psych (config breakage), requires psych gem in 1.8
890 >> - Integrate the IMAP / label sync back stuff (personally this is what I
891 >> miss the most)
892 >> - Go for ruby 2.0.0 and maybe 1.8
893 >> - Get rid of all dependencies that are abandoned or deprecated (ncurses
894 >> gem..)
895 >
896 > And target ncursesw?
897 >
898 >> - Try to do tests on most stuff for different encodings
899 >> - Try to get UTF-8 / encoding right
900 >> - Move all the rest of the infrastructure to something the project is in
901 >> control of
902 >>
903 >> Would be very nice:
904 >> - Index migration
905 >> - Config migration
906 >>
907 >> For the web page (eventually):
908 >> - note about the original project
909 >> - note about the last sup-0.13 release
910 >> - wiki and project page for sup2
911 >>
912 >> This plan more or less holds whether we go sup2 or not, but I think it
913 >> is easier to get rid of the hopeless dependencies.
914 >
915 > I agree that it's worth it to drop unmaintained dependencies and just
916 > fix what breaks.
917 > It would be unfortunate to have to fork the project and make a
918 > different name. I wonder if Morgan has lost interest or is just busy
919 > with other things.
920 >
921 > Cheers,
922 > jof
923 >> @sup-devel readers: discussion is currently at sup-talk, please send any
924 >> responses there.
925 >>
926 >> Regards, Gaute
927 >>
928 >> On 13. april 2013 19:14, Gaute Hope wrote:
929 >>>
930 >>>
931 >>> On 13. april 2013 18:35, Jonathan Lassoff wrote:
932 >>>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
933 >>>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
934 >>>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
935 >>>>>>> Hi,
936 >>>>>>>
937 >>>>>>> Jonathan: I put your commit into a pull request at:
938 >>>>>>> - https://github.com/sup-heliotrope/sup/pull/19
939 >>>>>>>
940 >>>>>>> Also, re-branding and updating to web-references:
941 >>>>>>> - https://github.com/sup-heliotrope/sup/pull/20
942 >>>>>>>
943 >>>>>>> any comments on this? You can see the changes I made. I have absolutely
944 >>>>>>> no intentions of stepping on any toes, but this is a suggestion.
945 >>>>>>
946 >>>>>> No, thank you very much! That looks great!
947 >>>>>>
948 >>>>>>> It is a pity that the official home page and probably first search
949 >>>>>>> results direct to the abandoned home and gem of sup.
950 >>>>>>
951 >>>>>> It is too bad. Hopefully William could hand off access or at least
952 >>>>>> push updates somehow.
953 >>>>>>
954 >>>>>> If not, maybe we could stand up another domain pointing to github pages?
955 >>>>>> Looks like supmua.org and supm.ua are available. :p
956 >>>>>>
957 >>>>>> --j
958 >>>>>
959 >>>>> Yeah.. I think some web page is pretty essential, perhaps just the
960 >>>>> standard github-pages domain for a start. Anyone feel up for the task,
961 >>>>> I'd be happy to add you to the github-organization.
962 >>>>
963 >>>> Agreed. I snagged supmua.org for a year, and have it pointing at
964 >>>> sup-heliotrope.github.io for pages.
965 >>>>
966 >>>> Stick me on the org, and I'll see about getting a simple site started.
967 >>>
968 >>> Nice. You're on.
969 >>>
970 >>> Cheers, Gaute
971 >>>
972
973 From eg@gaute.vetsj.com Sat Apr 13 22:17:32 2013
974 From: eg@gaute.vetsj.com (Gaute Hope)
975 Date: Sun, 14 Apr 2013 00:17:32 +0200
976 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
977 In-Reply-To: <CAHsqw9u6pYeh-y3RLHNRqF5qsMLsdfoku8ZS6SC+f___ptNL1g@mail.gmail.com>
978 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
979 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
980 <51692285.8000709@gaute.vetsj.com>
981 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
982 <51695AF1.2070701@gaute.vetsj.com>
983 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
984 <5169925C.1060701@gaute.vetsj.com>
985 <516997BD.7010409@gaute.vetsj.com>
986 <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com>
987 <CAHsqw9u6pYeh-y3RLHNRqF5qsMLsdfoku8ZS6SC+f___ptNL1g@mail.gmail.com>
988 Message-ID: <5169D97C.6020909@gaute.vetsj.com>
989
990 On la. 13. april 2013 kl. 22.48 +0200, Jonathan Lassoff wrote:
991 > Maybe William can help out?
992 > https://twitter.com/wm/status/323175493367119873
993
994 That would be the best ;)
995
996 But I still think we need to get rid of the deprecated and abandoned
997 stuff.
998
999 - gaute
1000
1001 From eg@gaute.vetsj.com Sat Apr 13 22:20:55 2013
1002 From: eg@gaute.vetsj.com (Gaute Hope)
1003 Date: Sun, 14 Apr 2013 00:20:55 +0200
1004 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
1005 In-Reply-To: <CAHsqw9s4GkmVZucuAd6pep_db-jr73QhRqBqEyZ6rudyR+pzGQ@mail.gmail.com>
1006 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1007 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1008 <51692285.8000709@gaute.vetsj.com>
1009 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1010 <51695AF1.2070701@gaute.vetsj.com>
1011 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1012 <5169925C.1060701@gaute.vetsj.com>
1013 <CAHsqw9s4GkmVZucuAd6pep_db-jr73QhRqBqEyZ6rudyR+pzGQ@mail.gmail.com>
1014 Message-ID: <5169DA47.7010706@gaute.vetsj.com>
1015
1016 On 13. april 2013 21:15, Jonathan Lassoff wrote:
1017 > http://supmua.org/
1018 >
1019 > Just tossed this, up but it's mostly stuff from the old rubyforge page.
1020
1021 Thats a good start, nice work!
1022
1023 - gaute
1024
1025 From eric.weikl@gmx.net Sun Apr 14 11:31:14 2013
1026 From: eric.weikl@gmx.net (Eric Weikl)
1027 Date: Sun, 14 Apr 2013 13:31:14 +0200
1028 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1029 In-Reply-To: <516997BD.7010409@gaute.vetsj.com>
1030 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1031 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1032 <51692285.8000709@gaute.vetsj.com>
1033 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1034 <51695AF1.2070701@gaute.vetsj.com>
1035 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1036 <5169925C.1060701@gaute.vetsj.com>
1037 <516997BD.7010409@gaute.vetsj.com>
1038 Message-ID: <1365938152-sup-6420@mint>
1039
1040 Hi Gaute,
1041
1042 That sounds like a plan of action :-)
1043
1044 Excerpts from Gaute Hope's message of 2013-04-13 19:37:01 +0200:
1045 > - Go for Mail in stead of RMail (index breakage)
1046
1047 Is this related to getting rid of Iconv for Ruby 2.0.0, or is it a
1048 separate issue? Otherwise, I would favor lumping it in the same release
1049 together with IMAP syncback, since both require a migration step by the
1050 user.
1051
1052 > - Integrate the IMAP / label sync back stuff (personally this is what I
1053 > miss the most)
1054
1055 I've been using the imap syncback code by Damien Leone from ezyang's
1056 branch for quite a while now (> 1 year) without any issues. It should be
1057 fairly easy to cherry-pick the relevant commits into the development
1058 branch.
1059
1060 > - Get rid of all dependencies that are abandoned or deprecated (ncurses
1061 > gem..)
1062
1063 +1 I'd also add deleting all unused code and other stuff (server code,
1064 website, Redwood protocol stuff, etc.).
1065
1066 > - Try to do tests on most stuff for different encodings
1067
1068 I thought about adding some functional tests (through the UI or
1069 otherwise), since retrofitting unit tests is probably too much of a pain.
1070 I need to figure out how the parts fit together some more, though.
1071 Do you think that makes sense?
1072
1073 > Would be very nice:
1074 > - Index migration
1075
1076 We could do the index migration like the imap syncback code does - it
1077 recognizes that it wasn't done yet and asks you to run a command-line
1078 tool.
1079
1080 > - Config migration
1081
1082 How exactly will the config change? Possibly it easy to detect via
1083 regular expressions or something?
1084
1085 Cheers,
1086 Eric
1087
1088 From eg@gaute.vetsj.com Sun Apr 14 12:05:52 2013
1089 From: eg@gaute.vetsj.com (Gaute Hope)
1090 Date: Sun, 14 Apr 2013 14:05:52 +0200
1091 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1092 In-Reply-To: <1365938152-sup-6420@mint>
1093 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1094 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1095 <51692285.8000709@gaute.vetsj.com>
1096 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1097 <51695AF1.2070701@gaute.vetsj.com>
1098 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1099 <5169925C.1060701@gaute.vetsj.com>
1100 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
1101 Message-ID: <516A9BA0.7040906@gaute.vetsj.com>
1102
1103 On 14. april 2013 13:31, Eric Weikl wrote:
1104 > Hi Gaute,
1105 >
1106 > That sounds like a plan of action :-)
1107 >
1108 > Excerpts from Gaute Hope's message of 2013-04-13 19:37:01 +0200:
1109 >> - Go for Mail in stead of RMail (index breakage)
1110 >
1111 > Is this related to getting rid of Iconv for Ruby 2.0.0, or is it a
1112 > separate issue? Otherwise, I would favor lumping it in the same release
1113 > together with IMAP syncback, since both require a migration step by the
1114 > user.
1115
1116 No, RMail and Iconv are separate issues.
1117
1118 Yes, that was my thinking as well - since both config and index need a
1119 migration step. Iconv deprecation should be seamless (syncback as well).
1120
1121 >> - Integrate the IMAP / label sync back stuff (personally this is what I
1122 >> miss the most)
1123 >
1124 > I've been using the imap syncback code by Damien Leone from ezyang's
1125 > branch for quite a while now (> 1 year) without any issues. It should be
1126 > fairly easy to cherry-pick the relevant commits into the development
1127 > branch.
1128
1129 Cool. I would really like to see this in main sup, any other objections?
1130 In my view the main arguments are:
1131
1132 - Manipulating IMAP could mess up user mail (potentially new bugs could
1133 mess up)
1134 - Maintaining this functionality requires some long-term (at least
1135 minor) effort
1136 - It modifies the mail store (could be solved with disabled-by-default)
1137 which I think is a big plus for many
1138
1139 I would suggest creating a official branch for this now, if you are
1140 interested I could add you as commiter or owner.
1141
1142 >> - Get rid of all dependencies that are abandoned or deprecated (ncurses
1143 >> gem..)
1144 >
1145 > +1 I'd also add deleting all unused code and other stuff (server code,
1146 > website, Redwood protocol stuff, etc.).
1147
1148 Yes, you could put Iconv in this category as well.
1149
1150 >> - Try to do tests on most stuff for different encodings
1151 >
1152 > I thought about adding some functional tests (through the UI or
1153 > otherwise), since retrofitting unit tests is probably too much of a pain.
1154 > I need to figure out how the parts fit together some more, though.
1155 > Do you think that makes sense?
1156 >
1157 >> Would be very nice:
1158 >> - Index migration
1159 >
1160 > We could do the index migration like the imap syncback code does - it
1161 > recognizes that it wasn't done yet and asks you to run a command-line
1162 > tool.
1163
1164 Not entirely sure how things are built up, but migration probably
1165 requires to map ids between Mail and RMail (it's going to be messy).
1166 Matthieu had some insight here, see:
1167 https://github.com/sup-heliotrope/sup/issues/22
1168
1169 >> - Config migration
1170 >
1171 > How exactly will the config change? Possibly it easy to detect via
1172 > regular expressions or something?
1173
1174 The YAML output from Syck (deprecated and removed) and Psych is
1175 incompatible. So the old config files are not readable by Psych. An
1176 approach could possibly be: install syck as a gem (if it exists), load
1177 the file with Syck, re-write it with Psych. There exists a Psych gem for
1178 1.8 (which could be conditionally loaded).
1179
1180 Also might be worth taking a look at sup inspired stuff; notmuch /
1181 mutt-kz which I don't think provides the same as sup, but are less buggy
1182 atm.
1183
1184 Cheers,
1185 Gaute
1186
1187 From eric.weikl@gmx.net Sun Apr 14 17:39:53 2013
1188 From: eric.weikl@gmx.net (Eric Weikl)
1189 Date: Sun, 14 Apr 2013 19:39:53 +0200
1190 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1191 In-Reply-To: <516A9BA0.7040906@gaute.vetsj.com>
1192 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1193 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1194 <51692285.8000709@gaute.vetsj.com>
1195 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1196 <51695AF1.2070701@gaute.vetsj.com>
1197 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1198 <5169925C.1060701@gaute.vetsj.com>
1199 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
1200 <516A9BA0.7040906@gaute.vetsj.com>
1201 Message-ID: <1365960274-sup-7139@mint>
1202
1203 Hi Gaute,
1204
1205 Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
1206 > In my view the main arguments are:
1207 >
1208 > - Manipulating IMAP could mess up user mail (potentially new bugs could
1209 > mess up)
1210
1211 Yes. Although my experience was positive until now, this definitely needs
1212 extensive testing (especially when disabled). Volunteers, anyone? :-)
1213
1214 > I would suggest creating a official branch for this now, if you are
1215 > interested I could add you as commiter or owner.
1216
1217 Sure, I can give it a spin.
1218
1219 Cheers,
1220 Eric
1221
1222 From dmishd@gmail.com Sun Apr 14 17:45:57 2013
1223 From: dmishd@gmail.com (Hamish D)
1224 Date: Sun, 14 Apr 2013 18:45:57 +0100
1225 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
1226 In-Reply-To: <516997BD.7010409@gaute.vetsj.com>
1227 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1228 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1229 <51692285.8000709@gaute.vetsj.com>
1230 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1231 <51695AF1.2070701@gaute.vetsj.com>
1232 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1233 <5169925C.1060701@gaute.vetsj.com> <516997BD.7010409@gaute.vetsj.com>
1234 Message-ID: <CAOxvSbfTY3oVttPbZSC85oBvW+7xH5xeVCWeJc66UbdKJ=8mbw@mail.gmail.com>
1235
1236 > For sup2:
1237 > - Fork a new repo: sup2
1238 > - Go for Mail in stead of RMail (index breakage)
1239 > - Go for only Psych (config breakage), requires psych gem in 1.8
1240 > - Integrate the IMAP / label sync back stuff (personally this is what I
1241 > miss the most)
1242 > - Go for ruby 2.0.0 and maybe 1.8
1243 > - Get rid of all dependencies that are abandoned or deprecated (ncurses
1244 > gem..)
1245 > - Try to do tests on most stuff for different encodings
1246 > - Try to get UTF-8 / encoding right
1247 > - Move all the rest of the infrastructure to something the project is in
1248 > control of
1249
1250 Another one for the list would be to update the GPG code to use
1251 version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8
1252
1253 Maybe we should move this list to the wiki.
1254
1255 Hamish
1256
1257 From eg@gaute.vetsj.com Sun Apr 14 22:32:43 2013
1258 From: eg@gaute.vetsj.com (Gaute Hope)
1259 Date: Mon, 15 Apr 2013 00:32:43 +0200
1260 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
1261 In-Reply-To: <CAOxvSbfTY3oVttPbZSC85oBvW+7xH5xeVCWeJc66UbdKJ=8mbw@mail.gmail.com>
1262 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1263 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1264 <51692285.8000709@gaute.vetsj.com>
1265 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1266 <51695AF1.2070701@gaute.vetsj.com>
1267 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1268 <5169925C.1060701@gaute.vetsj.com>
1269 <516997BD.7010409@gaute.vetsj.com>
1270 <CAOxvSbfTY3oVttPbZSC85oBvW+7xH5xeVCWeJc66UbdKJ=8mbw@mail.gmail.com>
1271 Message-ID: <516B2E8B.2080203@gaute.vetsj.com>
1272
1273
1274
1275 On 14. april 2013 19:45, Hamish D wrote:
1276 >> For sup2:
1277 >> - Fork a new repo: sup2
1278 >> - Go for Mail in stead of RMail (index breakage)
1279 >> - Go for only Psych (config breakage), requires psych gem in 1.8
1280 >> - Integrate the IMAP / label sync back stuff (personally this is what I
1281 >> miss the most)
1282 >> - Go for ruby 2.0.0 and maybe 1.8
1283 >> - Get rid of all dependencies that are abandoned or deprecated (ncurses
1284 >> gem..)
1285 >> - Try to do tests on most stuff for different encodings
1286 >> - Try to get UTF-8 / encoding right
1287 >> - Move all the rest of the infrastructure to something the project is in
1288 >> control of
1289 >
1290 > Another one for the list would be to update the GPG code to use
1291 > version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8
1292 >
1293 > Maybe we should move this list to the wiki.
1294
1295 Definitely: A roadmap for the next sup.
1296
1297 Cheers,
1298 Gaute
1299
1300 From eg@gaute.vetsj.com Mon Apr 15 11:42:28 2013
1301 From: eg@gaute.vetsj.com (Gaute Hope)
1302 Date: Mon, 15 Apr 2013 13:42:28 +0200
1303 Subject: [sup-talk] sup: Fix for an UndefinedMethodError
1304 In-Reply-To: <CAOxvSbfTY3oVttPbZSC85oBvW+7xH5xeVCWeJc66UbdKJ=8mbw@mail.gmail.com>
1305 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1306 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1307 <51692285.8000709@gaute.vetsj.com>
1308 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1309 <51695AF1.2070701@gaute.vetsj.com>
1310 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1311 <5169925C.1060701@gaute.vetsj.com>
1312 <516997BD.7010409@gaute.vetsj.com>
1313 <CAOxvSbfTY3oVttPbZSC85oBvW+7xH5xeVCWeJc66UbdKJ=8mbw@mail.gmail.com>
1314 Message-ID: <516BE7A4.90305@gaute.vetsj.com>
1315
1316
1317
1318 On 14. april 2013 19:45, Hamish D wrote:
1319 >> For sup2:
1320 >> - Fork a new repo: sup2
1321 >> - Go for Mail in stead of RMail (index breakage)
1322 >> - Go for only Psych (config breakage), requires psych gem in 1.8
1323 >> - Integrate the IMAP / label sync back stuff (personally this is what I
1324 >> miss the most)
1325 >> - Go for ruby 2.0.0 and maybe 1.8
1326 >> - Get rid of all dependencies that are abandoned or deprecated (ncurses
1327 >> gem..)
1328 >> - Try to do tests on most stuff for different encodings
1329 >> - Try to get UTF-8 / encoding right
1330 >> - Move all the rest of the infrastructure to something the project is in
1331 >> control of
1332 >
1333 > Another one for the list would be to update the GPG code to use
1334 > version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8
1335 >
1336 > Maybe we should move this list to the wiki.
1337
1338 https://github.com/sup-heliotrope/sup/wiki/Development
1339
1340 Please edit and comment - this was done quickly.
1341
1342 - Gaute
1343
1344 From marka@pobox.com Mon Apr 15 14:01:11 2013
1345 From: marka@pobox.com (Mark Alexander)
1346 Date: Mon, 15 Apr 2013 10:01:11 -0400
1347 Subject: [sup-talk] [PATCH] Fix problem with account selector
1348 Message-ID: <1366034093-sup-2478@x200s>
1349
1350 Here is the commit on my fork (I also did a pull request)
1351 for something that I found useful when using the same
1352 inbox for both personal and work email:
1353
1354 https://github.com/bloovis/sup/commit/4f843f53feac2cc7e1f7d8f5a32043878b398ace
1355
1356 When sending a message, the account selector was ignoring
1357 the account set by the before-edit hook. Fix this
1358 by running the hook before setting up the account selector.
1359 ---
1360 lib/sup/modes/edit-message-mode.rb | 3 ++-
1361 1 file changed, 2 insertions(+), 1 deletion(-)
1362
1363 diff --git a/lib/sup/modes/edit-message-mode.rb b/lib/sup/modes/edit-message-mode.rb
1364 index 464d935..1ed5969 100644
1365 --- a/lib/sup/modes/edit-message-mode.rb
1366 +++ b/lib/sup/modes/edit-message-mode.rb
1367 @@ -116,6 +116,8 @@ EOS
1368 @selector_label_width = 0
1369 @async_mode = nil
1370
1371 + HookManager.run "before-edit", :header => @header, :body => @body
1372 +
1373 @account_selector = nil
1374 # only show account selector if there is more than one email address
1375 if $config[:account_selector] && AccountManager.user_emails.length > 1
1376 @@ -145,7 +147,6 @@ EOS
1377 end
1378 add_selector @crypto_selector if @crypto_selector
1379
1380 - HookManager.run "before-edit", :header => @header, :body => @body
1381 if @crypto_selector
1382 HookManager.run "crypto-mode", :header => @header, :body => @body, :crypto_selector => @crypto_selector
1383 end
1384 --
1385 1.7.9.5
1386
1387 From eric.weikl@gmx.net Tue Apr 16 20:30:26 2013
1388 From: eric.weikl@gmx.net (Eric Weikl)
1389 Date: Tue, 16 Apr 2013 22:30:26 +0200
1390 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1391 In-Reply-To: <516A9BA0.7040906@gaute.vetsj.com>
1392 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1393 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1394 <51692285.8000709@gaute.vetsj.com>
1395 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1396 <51695AF1.2070701@gaute.vetsj.com>
1397 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1398 <5169925C.1060701@gaute.vetsj.com>
1399 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
1400 <516A9BA0.7040906@gaute.vetsj.com>
1401 Message-ID: <1366143381-sup-8459@mint>
1402
1403 Hi everyone,
1404
1405 I created a new branch with all the commits from Damien Leone and Edward
1406 Yang related to maildir syncback and put it here:
1407
1408 https://github.com/sup-heliotrope/sup/tree/maildir-sync
1409
1410 I skipped some advanced stuff like Edward's inotify support for now. We
1411 can add that later.
1412
1413 I performed some basic testing, but it would be great if some more people
1414 could give it a try. There's some documentation in the wiki:
1415
1416 https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
1417
1418 Cheers,
1419 Eric
1420
1421 Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
1422 > Cool. I would really like to see this in main sup, any other
1423 > objections? In my view the main arguments are:
1424 >
1425 > - Manipulating IMAP could mess up user mail (potentially new bugs could
1426 > mess up)
1427 > - Maintaining this functionality requires some long-term (at least
1428 > minor) effort
1429 > - It modifies the mail store (could be solved with disabled-by-default)
1430 > which I think is a big plus for many
1431 >
1432 > I would suggest creating a official branch for this now, if you are
1433 > interested I could add you as commiter or owner.
1434
1435 From matthieu.rakotojaona@gmail.com Tue Apr 16 21:21:45 2013
1436 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
1437 Date: Tue, 16 Apr 2013 23:21:45 +0200
1438 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1439 In-Reply-To: <1366143381-sup-8459@mint>
1440 References: <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1441 <51692285.8000709@gaute.vetsj.com>
1442 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1443 <51695AF1.2070701@gaute.vetsj.com>
1444 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1445 <5169925C.1060701@gaute.vetsj.com>
1446 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
1447 <516A9BA0.7040906@gaute.vetsj.com> <1366143381-sup-8459@mint>
1448 Message-ID: <20130416212145.GB2339@kpad.otokar.looc2011.eu>
1449
1450 On 04/16, Eric Weikl wrote:
1451 > Hi everyone,
1452 >
1453 > I created a new branch with all the commits from Damien Leone and Edward
1454 > Yang related to maildir syncback and put it here:
1455 >
1456 > https://github.com/sup-heliotrope/sup/tree/maildir-sync
1457 >
1458 > I skipped some advanced stuff like Edward's inotify support for now. We
1459 > can add that later.
1460 >
1461 > I performed some basic testing, but it would be great if some more people
1462 > could give it a try. There's some documentation in the wiki:
1463 >
1464 > https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
1465 >
1466 > Cheers,
1467 > Eric
1468
1469 Fantastic. Not being able to sync back was what prevented me from using
1470 it. After much work and discouragement with heliotrope, I will gladly
1471 try this !
1472
1473 On a longer-term note, syncing back to maildir has the limitation that
1474 non-standard flags (i.e labels) will not be handled, unless we start
1475 defining some custom way of storing them or modifying the original
1476 emails, which I highly dislike (this is how mu[0] works). But that's
1477 just something to keep in mind for future times, when we have a stable,
1478 up-to-date sup release. Let's do this ! =]
1479
1480 [0] http://www.djcbsoftware.nl/code/mu/
1481
1482 --
1483 Matthieu Rakotojaona
1484
1485 From sdothum@gmail.com Wed Apr 17 03:31:33 2013
1486 From: sdothum@gmail.com (Steven Hum)
1487 Date: Tue, 16 Apr 2013 23:31:33 -0400
1488 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1489 In-Reply-To: <1366143381-sup-8459@mint>
1490 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
1491 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1492 <51692285.8000709@gaute.vetsj.com>
1493 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1494 <51695AF1.2070701@gaute.vetsj.com>
1495 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1496 <5169925C.1060701@gaute.vetsj.com>
1497 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
1498 <516A9BA0.7040906@gaute.vetsj.com> <1366143381-sup-8459@mint>
1499 Message-ID: <1366169414-sup-1740@luna>
1500
1501
1502 Beautiful! I will begin using this in place of my copy of ezyang's fork
1503 immediately.
1504
1505 Thanks for all your hard work,
1506 Steven
1507
1508
1509 Excerpts from Eric Weikl's message of 2013-04-16 16:30:26 -0400:
1510 > Hi everyone,
1511 >
1512 > I created a new branch with all the commits from Damien Leone and Edward
1513 > Yang related to maildir syncback and put it here:
1514 >
1515 > https://github.com/sup-heliotrope/sup/tree/maildir-sync
1516 >
1517 > I skipped some advanced stuff like Edward's inotify support for now. We
1518 > can add that later.
1519 >
1520 > I performed some basic testing, but it would be great if some more people
1521 > could give it a try. There's some documentation in the wiki:
1522 >
1523 > https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
1524 >
1525 > Cheers,
1526 > Eric
1527 >
1528 > Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
1529 > > Cool. I would really like to see this in main sup, any other
1530 > > objections? In my view the main arguments are:
1531 > >
1532 > > - Manipulating IMAP could mess up user mail (potentially new bugs could
1533 > > mess up)
1534 > > - Maintaining this functionality requires some long-term (at least
1535 > > minor) effort
1536 > > - It modifies the mail store (could be solved with disabled-by-default)
1537 > > which I think is a big plus for many
1538 > >
1539 > > I would suggest creating a official branch for this now, if you are
1540 > > interested I could add you as commiter or owner.
1541 --
1542 "Truth or die."
1543
1544 Steven Hum
1545 5 - 28 Gilmour St
1546 Ottawa, ON K2P 0N3
1547 email sdothum at gmail.com
1548 tel 613.237.9058
1549
1550 From eg@gaute.vetsj.com Wed Apr 17 08:51:29 2013
1551 From: eg@gaute.vetsj.com (Gaute Hope)
1552 Date: Wed, 17 Apr 2013 10:51:29 +0200
1553 Subject: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
1554 In-Reply-To: <20130416212145.GB2339@kpad.otokar.looc2011.eu>
1555 References: <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
1556 <51692285.8000709@gaute.vetsj.com>
1557 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
1558 <51695AF1.2070701@gaute.vetsj.com>
1559 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
1560 <5169925C.1060701@gaute.vetsj.com>
1561 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
1562 <516A9BA0.7040906@gaute.vetsj.com> <1366143381-sup-8459@mint>
1563 <20130416212145.GB2339@kpad.otokar.looc2011.eu>
1564 Message-ID: <516E6291.2010307@gaute.vetsj.com>
1565
1566
1567
1568 On 16. april 2013 23:21, Matthieu Rakotojaona wrote:
1569 > On 04/16, Eric Weikl wrote:
1570 >> Hi everyone,
1571 >>
1572 >> I created a new branch with all the commits from Damien Leone and Edward
1573 >> Yang related to maildir syncback and put it here:
1574 >>
1575 >> https://github.com/sup-heliotrope/sup/tree/maildir-sync
1576 >>
1577 >> I skipped some advanced stuff like Edward's inotify support for now. We
1578 >> can add that later.
1579 >>
1580 >> I performed some basic testing, but it would be great if some more people
1581 >> could give it a try. There's some documentation in the wiki:
1582 >>
1583 >> https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
1584 >>
1585 >> Cheers,
1586 >> Eric
1587 >
1588 > Fantastic. Not being able to sync back was what prevented me from using
1589 > it. After much work and discouragement with heliotrope, I will gladly
1590 > try this !
1591 >
1592 > On a longer-term note, syncing back to maildir has the limitation that
1593 > non-standard flags (i.e labels) will not be handled, unless we start
1594 > defining some custom way of storing them or modifying the original
1595 > emails, which I highly dislike (this is how mu[0] works). But that's
1596 > just something to keep in mind for future times, when we have a stable,
1597 > up-to-date sup release. Let's do this ! =]
1598 >
1599 > [0] http://www.djcbsoftware.nl/code/mu/
1600 >
1601
1602 Great!
1603
1604 Put up a wikipage for collecting some resources on this:
1605 https://github.com/sup-heliotrope/sup/wiki/Development:-Maildir-syncback
1606
1607 Also a notmuch user created a script for syncing labels to maildir
1608 folders:
1609 https://github.com/altercation/es-bin/blob/master/maildir-notmuch-sync
1610
1611 Cheers, Gaute
1612
1613 From marka@pobox.com Wed Apr 17 10:22:08 2013
1614 From: marka@pobox.com (Mark Alexander)
1615 Date: Wed, 17 Apr 2013 06:22:08 -0400
1616 Subject: [sup-talk] [PATCH] Fix problem with account selector
1617 In-Reply-To: <1366034093-sup-2478@x200s>
1618 References: <1366034093-sup-2478@x200s>
1619 Message-ID: <1366193674-sup-848@x200s>
1620
1621 I should probably explain the rationale behind this patch.
1622
1623 For a couple of years I used a single instance of sup to handle email
1624 for two different accounts: one for personal email, and the other for
1625 work email. When I sent a message to somebody at work, I wanted the
1626 From: address to be set automatically to my work email address.
1627 Otherwise I wanted the From: address to be set to my personal email
1628 address. To do this I wrote a before-edit hook that looked like this
1629 (with my company name changed to "widgets"):
1630
1631 unless header["In-reply-to"]
1632 if header["To"] =~ /widgets/
1633 to = header["To"]
1634 info "Sending as widgets, to = #{to}"
1635 header["From"] = "Mark Alexander <marka at widgets.com>"
1636 else
1637 to = header["To"]
1638 info "Sending as pobox, to = #{to}"
1639 header["From"] = "Mark Alexander <marka at pobox.com>"
1640 end
1641 end
1642
1643 But the hook didn't work; the account selector was changing the From:
1644 address back to marka at pobox.com even after the hook had set it to
1645 marka at widgets.com. The fix was to run the hook before the account
1646 selector was initialized.
1647
1648 From eg@gaute.vetsj.com Wed Apr 17 13:53:06 2013
1649 From: eg@gaute.vetsj.com (Gaute Hope)
1650 Date: Wed, 17 Apr 2013 15:53:06 +0200
1651 Subject: [sup-talk] Encoding: UTF-8
1652 Message-ID: <CABKe4Mu-8FDU+QrX-o3+57AuqNjcAd4AO2h2cHvdF5m3pLPZ0w@mail.gmail.com>
1653
1654 Hi,
1655
1656 I set up a wiki page about UTF-8, if-when Iconv gets deprecated it's an
1657 excellent time to get UTF-8 right. Please modify or comment. I intended the
1658 page as a sort of coding-guide, but there are (as part of Iconv
1659 deprecation) several parts that need to be re-written.
1660
1661 https://github.com/sup-heliotrope/sup/wiki/Development:-UTF-8
1662
1663 Cheers,
1664 Gaute
1665 -------------- next part --------------
1666 An HTML attachment was scrubbed...
1667 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130417/7b3629df/attachment.html>
1668
1669 From wmorgan-sup@masanjin.net Sun Apr 21 03:31:35 2013
1670 From: wmorgan-sup@masanjin.net (William Morgan)
1671 Date: Sat, 20 Apr 2013 20:31:35 -0700
1672 Subject: [sup-talk] what can i help with?
1673 Message-ID: <1366514503-turnsole-37382@cugel>
1674
1675 Hi folks,
1676
1677 My sincere apologies for the complete and utter abandonment of Sup and
1678 Heliotrope. It's a constant source of emotional distress to me, but I do
1679 not have time to do anything with these projects any more. (Including
1680 monitoring this mailing list, which long ago fell victim to an
1681 overly-aggressive filtering rule.) I apologize.
1682
1683 But I'm thrilled to see that there is enough community momentum to keep
1684 things going. I'd love to enable this as best I can. What is the list of
1685 things you need from me to take over maintenance of Sup?
1686
1687 1. Add some new owners to the sup gem. (Who?)
1688 2. Add some administrators to the Rubyforge page. (Who?)
1689 3. What else?
1690
1691 -w
1692
1693 From dmishd@gmail.com Sun Apr 21 09:16:05 2013
1694 From: dmishd@gmail.com (Hamish D)
1695 Date: Sun, 21 Apr 2013 10:16:05 +0100
1696 Subject: [sup-talk] what can i help with?
1697 In-Reply-To: <1366514503-turnsole-37382@cugel>
1698 References: <1366514503-turnsole-37382@cugel>
1699 Message-ID: <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1700
1701 Hello William
1702
1703 Nice to hear from you again.
1704
1705 > My sincere apologies for the complete and utter abandonment of Sup and
1706 > Heliotrope.... I apologize.
1707
1708 Life happens.
1709
1710 > But I'm thrilled to see that there is enough community momentum to keep
1711 > things going. I'd love to enable this as best I can. What is the list of
1712 > things you need from me to take over maintenance of Sup?
1713 >
1714 > 1. Add some new owners to the sup gem. (Who?)
1715 > 2. Add some administrators to the Rubyforge page. (Who?)
1716 > 3. What else?
1717
1718 Does the rubyforge page manage these email lists? It would be good to
1719 be able to admin them.
1720
1721 It's a long shot, but any chance you have some back ups of the old
1722 wiki before it got spammed into oblivion? We've recovered what we can
1723 and started re-writing what we can't, but it would be lovely to get a
1724 dump of the old wiki (in whatever format).
1725
1726 As to who - Gaute Hope appears to have been the most active in the
1727 recent renaissance, so I would definitely give him access. Then as we
1728 sort ourselves out Gaute can give others access. (Not that I'd oppose
1729 others, but it would be good to get at least one person on quickly).
1730
1731 Hamish
1732
1733 From eg@gaute.vetsj.com Sun Apr 21 10:11:23 2013
1734 From: eg@gaute.vetsj.com (Gaute Hope)
1735 Date: Sun, 21 Apr 2013 12:11:23 +0200
1736 Subject: [sup-talk] what can i help with?
1737 In-Reply-To: <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1738 References: <1366514503-turnsole-37382@cugel>
1739 <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1740 Message-ID: <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com>
1741
1742 Hi William and list,
1743
1744 No stress and its nice to hear from you again.
1745
1746 I would be happy to take over that responsibility (and share it with for instance Hamish and Matthieu for starters, which I can fix afterwards of course).
1747
1748 I will most likely stay interested in the project for a long time, but it will definitely vary how much time I can spend - so lets quickly get someone else on the admin part as well.
1749
1750 Den 21. apr. 2013 kl. 11.16 skrev Hamish D:
1751
1752 > Hello William
1753 >
1754 > Nice to hear from you again.
1755 >
1756 >> My sincere apologies for the complete and utter abandonment of Sup and
1757 >> Heliotrope.... I apologize.
1758 >
1759 > Life happens.
1760 >
1761 >> But I'm thrilled to see that there is enough community momentum to keep
1762 >> things going. I'd love to enable this as best I can. What is the list of
1763 >> things you need from me to take over maintenance of Sup?
1764 >>
1765 >> 1. Add some new owners to the sup gem. (Who?)
1766 >> 2. Add some administrators to the Rubyforge page. (Who?)
1767 >> 3. What else?
1768 > Does the rubyforge page manage these email lists? It would be good to
1769 > be able to admin them.
1770 >
1771
1772 Perhaps put a note up on the Gitorious sup organization (to avoid confusion)?
1773
1774 As you may know we have put up an organization on GitHub we would be happy to add you there (if for nothing else than as an honorary member).
1775
1776 It is great to be able to continue the original project and not fork it off which definitely would loose some of the original community. Thanks for sharing it!
1777
1778 Cheers, Gaute
1779
1780
1781 From eg@gaute.vetsj.com Sun Apr 21 10:18:01 2013
1782 From: eg@gaute.vetsj.com (Gaute Hope)
1783 Date: Sun, 21 Apr 2013 12:18:01 +0200
1784 Subject: [sup-talk] what can i help with?
1785 In-Reply-To: <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com>
1786 References: <1366514503-turnsole-37382@cugel>
1787 <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1788 <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com>
1789 Message-ID: <0155E8B0-C6A9-43B2-8D64-B6643E34CDD0@gaute.vetsj.com>
1790
1791
1792 Den 21. apr. 2013 kl. 12.11 skrev Gaute Hope:
1793 >>> 3. What else?
1794 >> Does the rubyforge page manage these email lists? It would be good to
1795 >> be able to admin them.
1796 >>
1797 >
1798 > Perhaps put a note up on the Gitorious sup organization (to avoid confusion)?
1799
1800 Is #sup @ freenode something that is in sup control? Not very important perhaps, but just to make sure it doesnt get spammed..
1801
1802 Gaute
1803
1804 From wmorgan-sup@masanjin.net Sun Apr 21 16:41:38 2013
1805 From: wmorgan-sup@masanjin.net (William Morgan)
1806 Date: Sun, 21 Apr 2013 09:41:38 -0700
1807 Subject: [sup-talk] what can i help with?
1808 In-Reply-To: <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com>
1809 References: <1366514503-turnsole-37382@cugel>
1810 <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1811 <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com>
1812 Message-ID: <1366561995-turnsole-65603@cugel>
1813
1814 Ok, Gaute, I've added you as an admin of the Rubyforge page, and admin
1815 of the Gitorious project, and as an owner of the gem. Let me know if for
1816 some reason I've screwed any of that up. Rubyforge adminship should
1817 allow you to change the contents of sup.rubyforge.org and administer the
1818 mailing lists.
1819
1820 The freenode channel was set up by someone else... I don't remember who.
1821 I only used it once.
1822
1823 Let me know what else I can do.
1824
1825 Excerpts from Gaute Hope's message of 2013-04-21 03:11:23 -0700:
1826 > Hi William and list,
1827 >
1828 > No stress and its nice to hear from you again.
1829 >
1830 > I would be happy to take over that responsibility (and share it with for instance Hamish and Matthieu for starters, which I can fix afterwards of course).
1831 >
1832 > I will most likely stay interested in the project for a long time, but it will definitely vary how much time I can spend - so lets quickly get someone else on the admin part as well.
1833 >
1834 > Den 21. apr. 2013 kl. 11.16 skrev Hamish D:
1835 >
1836 > > Hello William
1837 > >
1838 > > Nice to hear from you again.
1839 > >
1840 > >> My sincere apologies for the complete and utter abandonment of Sup and
1841 > >> Heliotrope.... I apologize.
1842 > >
1843 > > Life happens.
1844 > >
1845 > >> But I'm thrilled to see that there is enough community momentum to keep
1846 > >> things going. I'd love to enable this as best I can. What is the list of
1847 > >> things you need from me to take over maintenance of Sup?
1848 > >>
1849 > >> 1. Add some new owners to the sup gem. (Who?)
1850 > >> 2. Add some administrators to the Rubyforge page. (Who?)
1851 > >> 3. What else?
1852 > > Does the rubyforge page manage these email lists? It would be good to
1853 > > be able to admin them.
1854 > >
1855 >
1856 > Perhaps put a note up on the Gitorious sup organization (to avoid confusion)?
1857 >
1858 > As you may know we have put up an organization on GitHub we would be happy to add you there (if for nothing else than as an honorary member).
1859 >
1860 > It is great to be able to continue the original project and not fork it off which definitely would loose some of the original community. Thanks for sharing it!
1861 >
1862 > Cheers, Gaute
1863
1864 From wmorgan-sup@masanjin.net Sun Apr 21 16:43:34 2013
1865 From: wmorgan-sup@masanjin.net (William Morgan)
1866 Date: Sun, 21 Apr 2013 09:43:34 -0700
1867 Subject: [sup-talk] what can i help with?
1868 In-Reply-To: <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1869 References: <1366514503-turnsole-37382@cugel>
1870 <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1871 Message-ID: <1366562512-turnsole-94955@cugel>
1872
1873 Excerpts from Hamish D's message of 2013-04-21 02:16:05 -0700:
1874 > It's a long shot, but any chance you have some back ups of the old
1875 > wiki before it got spammed into oblivion? We've recovered what we can
1876 > and started re-writing what we can't, but it would be lovely to get a
1877 > dump of the old wiki (in whatever format).
1878
1879 Unfortunately, I do not. I didn't save any myself, and the Rubyforge admin
1880 pages don't give you anything magical here.
1881
1882 --
1883 William <wmorgan-sup at masanjin.net>
1884
1885 From eg@gaute.vetsj.com Sun Apr 21 17:53:38 2013
1886 From: eg@gaute.vetsj.com (Gaute Hope)
1887 Date: Sun, 21 Apr 2013 19:53:38 +0200
1888 Subject: [sup-talk] what can i help with?
1889 In-Reply-To: <1366561995-turnsole-65603@cugel>
1890 References: <1366514503-turnsole-37382@cugel>
1891 <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1892 <B23FC9D5-7ACE-44A0-813E-AB4C1ACF0EFF@gaute.vetsj.com>
1893 <1366561995-turnsole-65603@cugel>
1894 Message-ID: <517427A2.5050003@gaute.vetsj.com>
1895
1896 Hi William,
1897
1898 Thanks, this looks good. I will add Hamish and Matthieu as
1899 administrators as well.
1900
1901 Regards, Gaute
1902
1903 On 21. april 2013 18:41, William Morgan wrote:
1904 > Ok, Gaute, I've added you as an admin of the Rubyforge page, and admin
1905 > of the Gitorious project, and as an owner of the gem. Let me know if for
1906 > some reason I've screwed any of that up. Rubyforge adminship should
1907 > allow you to change the contents of sup.rubyforge.org and administer the
1908 > mailing lists.
1909 >
1910 > The freenode channel was set up by someone else... I don't remember who.
1911 > I only used it once.
1912 >
1913 > Let me know what else I can do.
1914 >
1915 > Excerpts from Gaute Hope's message of 2013-04-21 03:11:23 -0700:
1916 >> Hi William and list,
1917 >>
1918 >> No stress and its nice to hear from you again.
1919 >>
1920 >> I would be happy to take over that responsibility (and share it with for instance Hamish and Matthieu for starters, which I can fix afterwards of course).
1921 >>
1922 >> I will most likely stay interested in the project for a long time, but it will definitely vary how much time I can spend - so lets quickly get someone else on the admin part as well.
1923 >>
1924 >> Den 21. apr. 2013 kl. 11.16 skrev Hamish D:
1925 >>
1926 >>> Hello William
1927 >>>
1928 >>> Nice to hear from you again.
1929 >>>
1930 >>>> My sincere apologies for the complete and utter abandonment of Sup and
1931 >>>> Heliotrope.... I apologize.
1932 >>>
1933 >>> Life happens.
1934 >>>
1935 >>>> But I'm thrilled to see that there is enough community momentum to keep
1936 >>>> things going. I'd love to enable this as best I can. What is the list of
1937 >>>> things you need from me to take over maintenance of Sup?
1938 >>>>
1939 >>>> 1. Add some new owners to the sup gem. (Who?)
1940 >>>> 2. Add some administrators to the Rubyforge page. (Who?)
1941 >>>> 3. What else?
1942 >>> Does the rubyforge page manage these email lists? It would be good to
1943 >>> be able to admin them.
1944 >>>
1945 >>
1946 >> Perhaps put a note up on the Gitorious sup organization (to avoid confusion)?
1947 >>
1948 >> As you may know we have put up an organization on GitHub we would be happy to add you there (if for nothing else than as an honorary member).
1949 >>
1950 >> It is great to be able to continue the original project and not fork it off which definitely would loose some of the original community. Thanks for sharing it!
1951 >>
1952 >> Cheers, Gaute
1953
1954 From matthieu.rakotojaona@gmail.com Sun Apr 21 18:16:32 2013
1955 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
1956 Date: Sun, 21 Apr 2013 20:16:32 +0200
1957 Subject: [sup-talk] what can i help with?
1958 In-Reply-To: <1366514503-turnsole-37382@cugel>
1959 References: <1366514503-turnsole-37382@cugel>
1960 Message-ID: <CAMiZLn1Rqn=kVT30dmiCQvtdPo4j8EmvGyndtqG7SdQDaBxOUA@mail.gmail.com>
1961
1962 Hi William,
1963
1964 It's a sad thing you do not have time to spare on a project in which
1965 you have put so much attention. Don't worry, we will take good care of
1966 your code for you =]
1967
1968 I don't have much to add to the discussion, just a big thank you for
1969 sup, heliotrope and the other gems (haha !) you have come up with.
1970 Sometimes I wish other projects would read your code and take some
1971 inspiration of the readability you have.
1972
1973 Anyway, see you around !
1974
1975 --
1976 Matthieu RAKOTOJAONA
1977
1978 From dmishd@gmail.com Sun Apr 21 19:22:12 2013
1979 From: dmishd@gmail.com (Hamish D)
1980 Date: Sun, 21 Apr 2013 20:22:12 +0100
1981 Subject: [sup-talk] what can i help with?
1982 In-Reply-To: <1366562512-turnsole-94955@cugel>
1983 References: <1366514503-turnsole-37382@cugel>
1984 <CAOxvSbcGss0r7c8BLfXQ6nPehBsPc7wz_Wo21KDifhZ+fFs7Bg@mail.gmail.com>
1985 <1366562512-turnsole-94955@cugel>
1986 Message-ID: <CAOxvSbfKZ1GSZd32V3k_Vg+Q30OGHLUCmFx4Tx3g2t+zUtZMOQ@mail.gmail.com>
1987
1988 > Excerpts from Hamish D's message of 2013-04-21 02:16:05 -0700:
1989 >> It's a long shot, but any chance you have some back ups of the old
1990 >> wiki before it got spammed into oblivion? We've recovered what we can
1991 >> and started re-writing what we can't, but it would be lovely to get a
1992 >> dump of the old wiki (in whatever format).
1993 >
1994 > Unfortunately, I do not. I didn't save any myself, and the Rubyforge admin
1995 > pages don't give you anything magical here.
1996
1997 Ah, I thought maybe you had more control over the wiki. Now we have
1998 access to rubyforge I've opened a support request about it -
1999 https://rubyforge.org/tracker/index.php?func=detail&aid=29744&group_id=5&atid=102
2000
2001 Fingers crossed ...
2002
2003 Hamish
2004
2005 From wmorgan-sup@masanjin.net Sun Apr 21 22:52:54 2013
2006 From: wmorgan-sup@masanjin.net (William Morgan)
2007 Date: Sun, 21 Apr 2013 15:52:54 -0700
2008 Subject: [sup-talk] what can i help with?
2009 In-Reply-To: <CAMiZLn1Rqn=kVT30dmiCQvtdPo4j8EmvGyndtqG7SdQDaBxOUA@mail.gmail.com>
2010 References: <1366514503-turnsole-37382@cugel>
2011 <CAMiZLn1Rqn=kVT30dmiCQvtdPo4j8EmvGyndtqG7SdQDaBxOUA@mail.gmail.com>
2012 Message-ID: <1366584614-turnsole-75136@cugel>
2013
2014 Thanks very much for the kind words. I appreciate it.
2015
2016 Excerpts from Matthieu Rakotojaona's message of 2013-04-21 11:16:32 -0700:
2017 > Hi William,
2018 >
2019 > It's a sad thing you do not have time to spare on a project in which
2020 > you have put so much attention. Don't worry, we will take good care of
2021 > your code for you =]
2022 >
2023 > I don't have much to add to the discussion, just a big thank you for
2024 > sup, heliotrope and the other gems (haha !) you have come up with.
2025 > Sometimes I wish other projects would read your code and take some
2026 > inspiration of the readability you have.
2027 >
2028 > Anyway, see you around !
2029 >
2030
2031 From jm@jmason.org Mon Apr 22 09:32:43 2013
2032 From: jm@jmason.org (Justin Mason)
2033 Date: Mon, 22 Apr 2013 10:32:43 +0100
2034 Subject: [sup-talk] what can i help with?
2035 In-Reply-To: <1366514503-turnsole-37382@cugel>
2036 References: <1366514503-turnsole-37382@cugel>
2037 Message-ID: <CAM8D7KT2Z765PN9CCX8XD4L089jX7JYaPyJWR=+uM_YiaUtd7w@mail.gmail.com>
2038
2039 hey William -- as a happy sup user, let me add my voice to the 'thanks
2040 and no worries' list. Life happens! ;)
2041
2042 --j.
2043
2044 On Sun, Apr 21, 2013 at 4:31 AM, William Morgan
2045 <wmorgan-sup at masanjin.net> wrote:
2046 > Hi folks,
2047 >
2048 > My sincere apologies for the complete and utter abandonment of Sup and
2049 > Heliotrope. It's a constant source of emotional distress to me, but I do
2050 > not have time to do anything with these projects any more. (Including
2051 > monitoring this mailing list, which long ago fell victim to an
2052 > overly-aggressive filtering rule.) I apologize.
2053 >
2054 > But I'm thrilled to see that there is enough community momentum to keep
2055 > things going. I'd love to enable this as best I can. What is the list of
2056 > things you need from me to take over maintenance of Sup?
2057 >
2058 > 1. Add some new owners to the sup gem. (Who?)
2059 > 2. Add some administrators to the Rubyforge page. (Who?)
2060 > 3. What else?
2061 >
2062 > -w
2063 > _______________________________________________
2064 > sup-talk mailing list
2065 > sup-talk at rubyforge.org
2066 > http://rubyforge.org/mailman/listinfo/sup-talk
2067
2068 From eg@gaute.vetsj.com Sun Apr 28 18:23:29 2013
2069 From: eg@gaute.vetsj.com (Gaute Hope)
2070 Date: Sun, 28 Apr 2013 20:23:29 +0200
2071 Subject: [sup-talk] Getting ready for sup-0.13
2072 Message-ID: <517D6921.3050006@gaute.vetsj.com>
2073
2074 Greetings list,
2075
2076 William has graciously given us access to the rest of the Sup
2077 infrastructure and the plan is to move as much as possible to GitHub.
2078
2079 At the moment we are three maintainers: Hamish Downer, Matthieu
2080 Rakotojaona and myself.
2081
2082 There are three categories for the sup repository team:
2083 Owner, Commiter, Contributor. Pretty much any kind of contribution would
2084 mean we would add you to the contributor team if you asked to be.
2085
2086 The plan for sup is:
2087 Release sup-0.13 relatively soon:
2088 - including the last bugfixes otherwise leave out the major changes
2089 that have been discussed lately
2090
2091 And the proposed roadmap for sup-0.14:
2092 - support ruby 2.0.0
2093 - migrate to psych
2094 - remove all deprecated and abandoned dependencies (e.g. switch from
2095 RMail to Mail)
2096 - implement IMAP syncback support
2097 - get uft-8 encoding right
2098
2099 We have documented this setup and the roadmap in the wiki at:
2100 -
2101 https://github.com/sup-heliotrope/sup/wiki/Development%3A-Administration-and-Team
2102 - https://github.com/sup-heliotrope/sup/wiki/Development
2103
2104 Please see https://github.com/sup-heliotrope/sup/wiki/Contributing on
2105 how to submit changes or contribute.
2106
2107 There are a few tasks and roles that need some love, among them:
2108 maintaining the web site and maintaining the maildir feature branch.
2109
2110 Regards, Fellow Suppers
2111
2112 From jof@thejof.com Sun Apr 28 18:47:41 2013
2113 From: jof@thejof.com (Jonathan Lassoff)
2114 Date: Sun, 28 Apr 2013 11:47:41 -0700
2115 Subject: [sup-talk] Getting ready for sup-0.13
2116 In-Reply-To: <517D6921.3050006@gaute.vetsj.com>
2117 References: <517D6921.3050006@gaute.vetsj.com>
2118 Message-ID: <CAHsqw9s-98p_JfOkN6h7X6_mxn8HucnJjx-ruSapyNHtba0g_A@mail.gmail.com>
2119
2120 Gaute -- thank you so much for organizing and calling out what needs to get
2121 done.
2122
2123 It's great to see sup getting some love again!
2124
2125 On Sun, Apr 28, 2013 at 11:23 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
2126
2127 > Greetings list,
2128 >
2129 > William has graciously given us access to the rest of the Sup
2130 > infrastructure and the plan is to move as much as possible to GitHub.
2131 >
2132 > At the moment we are three maintainers: Hamish Downer, Matthieu
2133 > Rakotojaona and myself.
2134 >
2135 > There are three categories for the sup repository team:
2136 > Owner, Commiter, Contributor. Pretty much any kind of contribution would
2137 > mean we would add you to the contributor team if you asked to be.
2138 >
2139 > The plan for sup is:
2140 > Release sup-0.13 relatively soon:
2141 > - including the last bugfixes otherwise leave out the major changes
2142 > that have been discussed lately
2143 >
2144 > And the proposed roadmap for sup-0.14:
2145 > - support ruby 2.0.0
2146 > - migrate to psych
2147 > - remove all deprecated and abandoned dependencies (e.g. switch from
2148 > RMail to Mail)
2149 > - implement IMAP syncback support
2150 > - get uft-8 encoding right
2151 >
2152 > We have documented this setup and the roadmap in the wiki at:
2153 > -
2154 >
2155 > https://github.com/sup-heliotrope/sup/wiki/Development%3A-Administration-and-Team
2156 > - https://github.com/sup-heliotrope/sup/wiki/Development
2157 >
2158 > Please see https://github.com/sup-heliotrope/sup/wiki/Contributing on
2159 > how to submit changes or contribute.
2160 >
2161 > There are a few tasks and roles that need some love, among them:
2162 > maintaining the web site and maintaining the maildir feature branch.
2163 >
2164
2165 I'd love to help contribute to testing, but am short on time these days.
2166 However, I setup the site, and will work to fix up the content on there.
2167 Please file requests here:
2168 https://github.com/sup-heliotrope/sup-heliotrope.github.io/issues
2169
2170 Cheers,
2171 jof
2172
2173 >
2174 > Regards, Fellow Suppers
2175 > _______________________________________________
2176 > sup-talk mailing list
2177 > sup-talk at rubyforge.org
2178 > http://rubyforge.org/mailman/listinfo/sup-talk
2179 >
2180 -------------- next part --------------
2181 An HTML attachment was scrubbed...
2182 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130428/9e73b557/attachment-0001.html>
2183
2184 From eg@gaute.vetsj.com Sun Apr 28 19:01:28 2013
2185 From: eg@gaute.vetsj.com (Gaute Hope)
2186 Date: Sun, 28 Apr 2013 21:01:28 +0200
2187 Subject: [sup-talk] Getting ready for sup-0.13
2188 In-Reply-To: <CAHsqw9s-98p_JfOkN6h7X6_mxn8HucnJjx-ruSapyNHtba0g_A@mail.gmail.com>
2189 References: <517D6921.3050006@gaute.vetsj.com>
2190 <CAHsqw9s-98p_JfOkN6h7X6_mxn8HucnJjx-ruSapyNHtba0g_A@mail.gmail.com>
2191 Message-ID: <517D7208.2040907@gaute.vetsj.com>
2192
2193 On 28. april 2013 20:47, Jonathan Lassoff wrote:
2194 >> There are a few tasks and roles that need some love, among them:
2195 >> maintaining the web site and maintaining the maildir feature branch.
2196 >>
2197 >
2198 > I'd love to help contribute to testing, but am short on time these days.
2199 > However, I setup the site, and will work to fix up the content on there.
2200 > Please file requests here:
2201 > https://github.com/sup-heliotrope/sup-heliotrope.github.io/issues
2202
2203 thanks, I am not at all alone.
2204
2205 That'd be great. Don't hesitate to add yourself to homepage/webpage
2206 responsible:
2207 https://github.com/sup-heliotrope/sup/wiki/Development#roles-and-tasks
2208 if you wish to.
2209
2210 @ericweikl: you already did some work to keep the maildir branch up to
2211 date so if you wish you could add yourself to the maildir-sync branch
2212 responsible at the same wikipage.
2213
2214 neither of you will be alone of course.
2215
2216 when we get around to it sup.rubyforge.org should redirect to the new site.
2217
2218 Regards, Gaute
2219
2220 From sdothum@gmail.com Sun Apr 28 19:05:31 2013
2221 From: sdothum@gmail.com (Steven Hum)
2222 Date: Sun, 28 Apr 2013 15:05:31 -0400
2223 Subject: [sup-talk] Getting ready for sup-0.13
2224 In-Reply-To: <517D6921.3050006@gaute.vetsj.com>
2225 References: <517D6921.3050006@gaute.vetsj.com>
2226 Message-ID: <1367175691-sup-3315@luna>
2227
2228
2229 Kudos and thanks to all the sup maintainers and contributors. It is
2230 really exciting to see sup get the attention it deserves.
2231
2232 I will definitely stay on top of the develop branch to assist in any way
2233 possible.
2234
2235 Regards,
2236 Steven
2237
2238 Excerpts from Gaute Hope's message of 2013-04-28 14:23:29 -0400:
2239 > Greetings list,
2240 >
2241 > William has graciously given us access to the rest of the Sup
2242 > infrastructure and the plan is to move as much as possible to GitHub.
2243 >
2244 > At the moment we are three maintainers: Hamish Downer, Matthieu
2245 > Rakotojaona and myself.
2246 >
2247 > There are three categories for the sup repository team:
2248 > Owner, Commiter, Contributor. Pretty much any kind of contribution would
2249 > mean we would add you to the contributor team if you asked to be.
2250 >
2251 > The plan for sup is:
2252 > Release sup-0.13 relatively soon:
2253 > - including the last bugfixes otherwise leave out the major changes
2254 > that have been discussed lately
2255 >
2256 > And the proposed roadmap for sup-0.14:
2257 > - support ruby 2.0.0
2258 > - migrate to psych
2259 > - remove all deprecated and abandoned dependencies (e.g. switch from
2260 > RMail to Mail)
2261 > - implement IMAP syncback support
2262 > - get uft-8 encoding right
2263 >
2264 > We have documented this setup and the roadmap in the wiki at:
2265 > -
2266 > https://github.com/sup-heliotrope/sup/wiki/Development%3A-Administration-and-Team
2267 > - https://github.com/sup-heliotrope/sup/wiki/Development
2268 >
2269 > Please see https://github.com/sup-heliotrope/sup/wiki/Contributing on
2270 > how to submit changes or contribute.
2271 >
2272 > There are a few tasks and roles that need some love, among them:
2273 > maintaining the web site and maintaining the maildir feature branch.
2274 >
2275 > Regards, Fellow Suppers
2276 --
2277 "Truth or die."
2278
2279 Steven Hum
2280 5 - 28 Gilmour St
2281 Ottawa, ON K2P 0N3
2282 email sdothum at gmail.com
2283 tel 613.237.9058
2284
2285 From eric.weikl@gmx.net Sun Apr 28 19:59:56 2013
2286 From: eric.weikl@gmx.net (Eric Weikl)
2287 Date: Sun, 28 Apr 2013 21:59:56 +0200
2288 Subject: [sup-talk] Getting ready for sup-0.13
2289 In-Reply-To: <517D7208.2040907@gaute.vetsj.com>
2290 References: <517D6921.3050006@gaute.vetsj.com>
2291 <CAHsqw9s-98p_JfOkN6h7X6_mxn8HucnJjx-ruSapyNHtba0g_A@mail.gmail.com>
2292 <517D7208.2040907@gaute.vetsj.com>
2293 Message-ID: <1367178536-sup-1766@mint>
2294
2295 Hi Gaute,
2296
2297 thanks to you guys for giving some focus - I'm very happy that sup
2298 development is gaining some traction again!
2299
2300 Excerpts from Gaute Hope's message of 2013-04-28 21:01:28 +0200:
2301 > @ericweikl: you already did some work to keep the maildir branch up to
2302 > date so if you wish you could add yourself to the maildir-sync branch
2303 > responsible at the same wikipage.
2304
2305 Sure, I definitely want to finish what I started :-) I just added myself.
2306
2307 Cheers,
2308 Eric
2309
2310 From sup@zevv.nl Sun Apr 28 20:33:03 2013
2311 From: sup@zevv.nl (Ico Doornekamp)
2312 Date: Sun, 28 Apr 2013 22:33:03 +0200
2313 Subject: [sup-talk] Getting ready for sup-0.13
2314 In-Reply-To: <517D6921.3050006@gaute.vetsj.com>
2315 References: <517D6921.3050006@gaute.vetsj.com>
2316 Message-ID: <1367181127-sup-5301@pruts.nl>
2317
2318 * On Sun Apr 28 20:23:29 +0200 2013, Gaute Hope wrote:
2319
2320 > The plan for sup is:
2321 > Release sup-0.13 relatively soon:
2322 > - including the last bugfixes otherwise leave out the major changes
2323 > that have been discussed lately
2324
2325 Yay, this makes my day, Thanks to all involved!
2326
2327
2328 --
2329 :wq
2330 ^X^Cy^K^X^C^C^C^C
2331