Re: [sup-talk] sup: Fix for an UndefinedMethodError
On 14. april 2013 19:45, Hamish D wrote: 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..) - 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 Another one for the list would be to update the GPG code to use version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8 Maybe we should move this list to the wiki. https://github.com/sup-heliotrope/sup/wiki/Development Please edit and comment - this was done quickly. - Gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
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..) - 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 Another one for the list would be to update the GPG code to use version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8 Maybe we should move this list to the wiki. Hamish ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On 14. april 2013 19:45, Hamish D wrote: 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..) - 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 Another one for the list would be to update the GPG code to use version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8 Maybe we should move this list to the wiki. Definitely: A roadmap for the next sup. Cheers, Gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope e...@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 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On Fri, Apr 12, 2013 at 12:46 PM, Hamish D dmi...@gmail.com wrote: We've set up https://github.com/sup-heliotrope/sup Please feel free to put pull requests up there. And contributions to the new wiki are also very welcome. We have lots of missing pages ... https://github.com/sup-heliotrope/sup/wiki Hey -- that's a most excellent place to put a wiki up. Glad to find where the action's at. We have emailed William about this but have had no response. So currently we have no access to publishing gems under the sup name. As to a meet up, I'm in England so won't be coming to San Francisco :-P Oh no worries, I just mention it because I know WIlliam is from somewhere around here. I think he's working in SF now. I'm very sorry. It seems that an error occurred in Sup. Please accept my sincere apologies. Please submit the contents of /home/jof/.sup/exception-log.txt and a brief report of the circumstances to http://masanjin.net/sup-bugs/ so that I might address this problem. Thank you! Sincerely, William We should update this text ... Hamish ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On 04/13, Gaute Hope 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. It is a pity that the official home page and probably first search results direct to the abandoned home and gem of sup. Regards, Gaute I guess it's also the occasion to think about the mailing list. I guess no one has the rights on this one ? I don't see anything in github for this functionality. -- Matthieu Rakotojaona ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On 13. april 2013 14:49, Matthieu Rakotojaona wrote: I guess it's also the occasion to think about the mailing list. I guess no one has the rights on this one ? I don't see anything in github for this functionality. Yup - maybe its time for 'sup2' - from rubyforge: http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned Project xyz seems to be abandoned. Can you pass it to me? This comes up occasionally - a well-named or positioned project gets started, then the project admin falls out of sight and can't be reached. Patches pile up, people start wondering what's going on, and it seems a shame to lose the project name by forking it. So someone will ask if we as RubyForge admins will pass over control of the project to them. We really, really, hesitate to transfer admin privileges from one person to another, even if the original admin has completely disappeared. I suspect there are legal complications, and we don't have the budget to deal with those. Furthermore, suppose the original admin has been off on furlough for a year and comes back to find that his project has been moved away from him. Not a pleasant situation. In situations where the project admin can't be reached for a long time and folks want to move forward, I suggest forking the project. You're welcome to host a xyz2 version of project xyz on RubyForge, and if the original admin ever shows up again and wants to hand over the project to you, we can help facilitate that. ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote: On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope e...@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. Regards, Gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
I was thinking the same, that it may be time for a sup2 repository. This is very premature, but are there any thoughts to integrate some of the work done in the sup forks. I am thinking in particular of the imap work ezyang did -- I adopted his fork as he seemed to be the most active with regards to imap folder handling, notably propagating updates. It would be nice to consolidate the features many of these forks addressed.. though, I have no idea how this can be easily facilitated. Regards, Steven Excerpts from Gaute Hope's message of 2013-04-13 09:29:08 -0400: On 13. april 2013 14:49, Matthieu Rakotojaona wrote: I guess it's also the occasion to think about the mailing list. I guess no one has the rights on this one ? I don't see anything in github for this functionality. Yup - maybe its time for 'sup2' - from rubyforge: http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned Project xyz seems to be abandoned. Can you pass it to me? This comes up occasionally - a well-named or positioned project gets started, then the project admin falls out of sight and can't be reached. Patches pile up, people start wondering what's going on, and it seems a shame to lose the project name by forking it. So someone will ask if we as RubyForge admins will pass over control of the project to them. We really, really, hesitate to transfer admin privileges from one person to another, even if the original admin has completely disappeared. I suspect there are legal complications, and we don't have the budget to deal with those. Furthermore, suppose the original admin has been off on furlough for a year and comes back to find that his project has been moved away from him. Not a pleasant situation. In situations where the project admin can't be reached for a long time and folks want to move forward, I suggest forking the project. You're welcome to host a xyz2 version of project xyz on RubyForge, and if the original admin ever shows up again and wants to hand over the project to you, we can help facilitate that. -- Truth or die. Steven Hum 5 - 28 Gilmour St Ottawa, ON K2P 0N3 email sdot...@gmail.com tel 613.237.9058 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
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..) - 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. @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 e...@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 e...@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 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
http://supmua.org/ Just tossed this, up but it's mostly stuff from the old rubyforge page. On Sat, Apr 13, 2013 at 10:14 AM, Gaute Hope e...@gaute.vetsj.com wrote: On 13. april 2013 18:35, Jonathan Lassoff wrote: On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope e...@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 e...@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 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
Maybe William can help out? https://twitter.com/wm/status/323175493367119873 On Sat, Apr 13, 2013 at 12:19 PM, Jonathan Lassoff j...@thejof.com wrote: On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope e...@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 e...@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 e...@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 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On la. 13. april 2013 kl. 22.48 +0200, Jonathan Lassoff wrote: Maybe William can help out? https://twitter.com/wm/status/323175493367119873 That would be the best ;) But I still think we need to get rid of the deprecated and abandoned stuff. - gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On 13. april 2013 21:15, Jonathan Lassoff wrote: http://supmua.org/ Just tossed this, up but it's mostly stuff from the old rubyforge page. Thats a good start, nice work! - gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
There was some activity not long ago by some sup users who are trying to keep sup afloat -- by attempting to rebuild a sup wiki (the original one had degraded horribly w/o a moderator) and look at current state of sup (and its forks?). Unfortunately, I don't have those mailing list messages in my archives anymore -- I don't hang onto list mail long. But you should be able to comb the list mail to identify a few people who are trying to spear head this. I need to investigate this too.. as I currently use ezyang's fork for imap maildir handling and would be interested if all the good things people have added to sup can be rolled back into an official sup master. Regards, Steven Excerpts from Jonathan Lassoff's message of 2013-04-12 14:09:33 -0400: I kept hitting this bug that was driving me nuts. While editing a message, I'd go to add a recipient that I don't usually email. So, I'd leave my draft in a buffer, find a mail from them, and go to update their contact, only to get hit with an undefined method error. This seems to get triggered if you ever set a new alias for a contact that already exists in the contacts list. I made a fix on my branch on gitorious. https://gitorious.org/~jofathan/sup/jofathan-sup/commit/7754799bc186833371c7839142270fe65b942ee6 Is anyone still monitoring the sup/mainline repo on gitorious? William Morgan? Are you still active with sup? Does sup need a new maintainer? I still use sup every day for my work email, and its my favorite client ever. Maybe it would be useful to have a sup hackers meetup in San Francisco? The crash was like: [Fri Apr 12 10:04:55 -0700 2013] ERROR: oh crap, an exception I'm very sorry. It seems that an error occurred in Sup. Please accept my sincere apologies. Please submit the contents of /home/jof/.sup/exception-log.txt and a brief report of the circumstances to http://masanjin.net/sup-bugs/ so that I might address this problem. Thank you! Sincerely, William --- NoMethodError from thread: main undefined method `email' for THE_PERSONS_ALIAS_NAME:String /usr/lib/ruby/1.8/sup/contact.rb:33:in `update_alias' (eval):1:in `send' (eval):1:in `update_alias' /usr/lib/ruby/1.8/sup/modes/contact-list-mode.rb:13:in `alias_contact' /usr/lib/ruby/1.8/sup/modes/thread-view-mode.rb:259:in `alias' /usr/lib/ruby/1.8/sup/mode.rb:59:in `send' /usr/lib/ruby/1.8/sup/mode.rb:59:in `handle_input' /usr/lib/ruby/1.8/sup/buffer.rb:278:in `handle_input' /usr/bin/sup-mail:273 -- Truth or die. Steven Hum 5 - 28 Gilmour St Ottawa, ON K2P 0N3 email sdot...@gmail.com tel 613.237.9058 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
We've set up https://github.com/sup-heliotrope/sup Please feel free to put pull requests up there. And contributions to the new wiki are also very welcome. We have lots of missing pages ... https://github.com/sup-heliotrope/sup/wiki We have emailed William about this but have had no response. So currently we have no access to publishing gems under the sup name. As to a meet up, I'm in England so won't be coming to San Francisco :-P I'm very sorry. It seems that an error occurred in Sup. Please accept my sincere apologies. Please submit the contents of /home/jof/.sup/exception-log.txt and a brief report of the circumstances to http://masanjin.net/sup-bugs/ so that I might address this problem. Thank you! Sincerely, William We should update this text ... Hamish ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
