From: Jonathan Lassoff <jof@thejof.com>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: Hamish D <dmishd@gmail.com>, sup-talk <sup-talk@rubyforge.org>,
Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] sup: Fix for an UndefinedMethodError
Date: Sat, 13 Apr 2013 12:19:17 -0700 [thread overview]
Message-ID: <CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com> (raw)
In-Reply-To: <516997BD.7010409@gaute.vetsj.com>
On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> If we go sup2 I would suggest the following plan:
>
> - Release the best we can get with the current code for 1.9.3 as a last
> community release of sup-0.12, say.. sup-0.13.
>
> For sup2:
> - Fork a new repo: sup2
> - Go for Mail in stead of RMail (index breakage)
> - Go for only Psych (config breakage), requires psych gem in 1.8
> - Integrate the IMAP / label sync back stuff (personally this is what I
> miss the most)
> - Go for ruby 2.0.0 and maybe 1.8
> - Get rid of all dependencies that are abandoned or deprecated (ncurses
> gem..)
And target ncursesw?
> - Try to do tests on most stuff for different encodings
> - Try to get UTF-8 / encoding right
> - Move all the rest of the infrastructure to something the project is in
> control of
>
> Would be very nice:
> - Index migration
> - Config migration
>
> For the web page (eventually):
> - note about the original project
> - note about the last sup-0.13 release
> - wiki and project page for sup2
>
> This plan more or less holds whether we go sup2 or not, but I think it
> is easier to get rid of the hopeless dependencies.
I agree that it's worth it to drop unmaintained dependencies and just
fix what breaks.
It would be unfortunate to have to fork the project and make a
different name. I wonder if Morgan has lost interest or is just busy
with other things.
Cheers,
jof
> @sup-devel readers: discussion is currently at sup-talk, please send any
> responses there.
>
> Regards, Gaute
>
> On 13. april 2013 19:14, Gaute Hope wrote:
>>
>>
>> On 13. april 2013 18:35, Jonathan Lassoff wrote:
>>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Jonathan: I put your commit into a pull request at:
>>>>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>>>>
>>>>>> Also, re-branding and updating to web-references:
>>>>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>>>>
>>>>>> any comments on this? You can see the changes I made. I have absolutely
>>>>>> no intentions of stepping on any toes, but this is a suggestion.
>>>>>
>>>>> No, thank you very much! That looks great!
>>>>>
>>>>>> It is a pity that the official home page and probably first search
>>>>>> results direct to the abandoned home and gem of sup.
>>>>>
>>>>> It is too bad. Hopefully William could hand off access or at least
>>>>> push updates somehow.
>>>>>
>>>>> If not, maybe we could stand up another domain pointing to github pages?
>>>>> Looks like supmua.org and supm.ua are available. :p
>>>>>
>>>>> --j
>>>>
>>>> Yeah.. I think some web page is pretty essential, perhaps just the
>>>> standard github-pages domain for a start. Anyone feel up for the task,
>>>> I'd be happy to add you to the github-organization.
>>>
>>> Agreed. I snagged supmua.org for a year, and have it pointing at
>>> sup-heliotrope.github.io for pages.
>>>
>>> Stick me on the org, and I'll see about getting a simple site started.
>>
>> Nice. You're on.
>>
>> Cheers, Gaute
>>
next prev parent reply other threads:[~2013-04-13 19:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:09 Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 13:17 ` Gaute Hope
2013-04-13 16:35 ` Jonathan Lassoff
2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff [this message]
2013-04-13 20:48 ` Jonathan Lassoff
2013-04-13 22:17 ` Gaute Hope
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 8:51 ` Gaute Hope
2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2013-08-15 13:35 ` [sup-talk] " Steven Schmeiser
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
2013-04-13 19:15 ` Jonathan Lassoff
2013-04-13 22:20 ` Gaute Hope
2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 13:29 ` Gaute Hope
2013-04-13 15:42 ` Steven Hum
2013-04-13 10:06 ` Jonathan Lassoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHsqw9tM6-S7DGWAVUU_qHa-db=maaBSUL1mD2Tg5Yu=dLj-oQ@mail.gmail.com' \
--to=jof@thejof.com \
--cc=dmishd@gmail.com \
--cc=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox