community/pipermail-archives/sup-devel/2012-05.txt (3831B) - raw
1 From david.froger.ml@gmail.com Sun May 27 20:56:32 2012
2 From: david.froger.ml@gmail.com (David Froger)
3 Date: Sun, 27 May 2012 22:56:32 +0200
4 Subject: [sup-devel] helioptrop/turnsol or sup
5 Message-ID: <CANe92jcLjQxs-AwiAiPRaiQoR3YMzRsyrgnnFCW4gA0oh6e8cw@mail.gmail.com>
6
7 Hi,
8
9 I'm wondering what is recommanded today for a user, sup or turnsol/heliotrop?
10
11 Is sup still maintained ? (wiki vandalized, 0.13 not released).
12
13 Is there something one can do to prevent wiki vandalization? (someone
14 had spoken about git gollum).
15
16 I've tried turnsol/heliotrop. Really great, as sup was.
17 I've had some issue with utf-8 (ruby 1.8.7), but I think it can be
18 solved with ruby 1.9.3.
19
20 I'm also wondering what's the search syntax for turnsol? Are these
21 syntax possible, like with sup:
22 before:today, on:today, after:yesterday, after:(2 days ago), during:february
23
24 I've also had a look to notmuch, it looks active but not powerfull as sup.
25 Especially, I didn't find a notmuch frontend that suit to me, and the
26 syntax for time range
27 $(date +%s -d 2009-10-01)..$(date +%s) is really not convenient.
28
29 Best,
30 David
31
32 From wmorgan-sup@masanjin.net Tue May 29 03:51:53 2012
33 From: wmorgan-sup@masanjin.net (William Morgan)
34 Date: Mon, 28 May 2012 20:51:53 -0700
35 Subject: [sup-devel] helioptrop/turnsol or sup
36 In-Reply-To: <CANe92jcLjQxs-AwiAiPRaiQoR3YMzRsyrgnnFCW4gA0oh6e8cw@mail.gmail.com>
37 References: <CANe92jcLjQxs-AwiAiPRaiQoR3YMzRsyrgnnFCW4gA0oh6e8cw@mail.gmail.com>
38 Message-ID: <1338263304-turnsole-70458@typhon>
39
40 Excerpts from David Froger's message of 2012-05-27 13:56:32 -0700:
41 > I'm wondering what is recommanded today for a user, sup or turnsol/heliotrop?
42
43 Probably heliotrope/turnsole. Sup is essentially unmaintained at this
44 point (I'm not working on it, and the anointed maintainers are MIA).
45 Heliotrope is nominally under active development, though I haven't had
46 much time for it over the past few months.
47
48 > I've tried turnsol/heliotrop. Really great, as sup was.
49 > I've had some issue with utf-8 (ruby 1.8.7), but I think it can be
50 > solved with ruby 1.9.3.
51
52 Feel free to file a bug on the github issue tracker. There are certain
53 things we can't quite accomplish in 1.8, but I'd like to get as close as
54 possible.
55
56 > I'm also wondering what's the search syntax for turnsol? Are these
57 > syntax possible, like with sup:
58 > before:today, on:today, after:yesterday, after:(2 days ago), during:february
59
60 Unfortunately not. You can file a feature request with Whistlepig, but
61 I can tell you now there are many other things I would like to focus on
62 first.
63
64 --
65 William <wmorgan at masanjin.net>
66
67 From matthieu.rakotojaona@gmail.com Wed May 30 20:35:46 2012
68 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
69 Date: Wed, 30 May 2012 22:35:46 +0200
70 Subject: [sup-devel] Documentation of the heliotrope API
71 Message-ID: <CAMiZLn2ESrDxTFhfzLAH36-7gJy7oy6uCWAxKYxHD5M1A9Pe_A@mail.gmail.com>
72
73 Hello everyone,
74
75 While browsing the interwebs, I realized that many people are also
76 tired of the cumbersomeness of the IMAP protocol, and a few of them
77 has started some work on implementing what they would love to see. For
78 instance, you can find a thread talking about it in [0] which links to
79 a few other thoughts. What is interesting is that many people have the
80 same approach to use JSON-over-HTTP in a RESTful manner. I think each
81 of these implementations' problem is the same: they lack visibility to
82 gather improvements.
83
84 Seeing this, I thought that to give Heliotrope a little more
85 visibility, we should improve the documentation a little bit. I have
86 started [1] by the first step: the API. Feel free to comment back on
87 this, or fork/edit the pages yourself.
88
89
90 Cheers,
91
92 --
93 Matthieu RAKOTOJAONA
94
95
96 [0] http://blog.gaborcselle.com/2010/02/how-to-replace-imap.html
97 [1] https://github.com/rakoo/heliotrope/wiki/A-brief-overview-of-the-heliotrope-api
98