![]() |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
are you also going to push it to extra-dev repository?
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
The fact is that the upcoming release is not feature-complete (it will miss recurrent events synchronization and birthday calendars support), so I don't feel comfortable with submitting it to extras-devel in this state... |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Lack of features is not a reason to reject an app in the testing qa process, so long as the app summary is not creating wrong expectations. If the next release will be in a week or two, it's probably not worth going through the qa process twice. Still, getting a version in devel may increase the amount of testers you get. If the next release will be in months, then an incomplete app may be better than nothing for a lot of people. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Hi Lorelei,
Glad to see that you're coming forward with the implementation. I have no problems if you change the format of the database. I can hardly await the new version :-) |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
I may go with a two-step process:
release the upcoming and feature-incomplete in extras-devel (and only there), so that I can also test out the auto-build process. That release will live for a few weeks (and won't be pushed to extras-testing), after that a new release with last few missing features will be added to extras-devel. It will be that release that will go to extras-testing for the QA beating :) As you said, expected timelines are difficult to deal with (especially with developments done in spare time), but once the big features are done, everything will go more smoothly, at least that's my hope. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Thanks for great program. This is exactly what I was looking for. I have a question though. What is the challenge for not being able to sync repeating events? Is there an incompatibility/conversion issue?
Maybe I can spare sometime to help you fix this. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
The only problem I can foresee: the N900 calendar program is very limited with recurring events: you cannot insert exceptions in a recurring rule, so recurring events with exceptions transferred from Google to the N900 will not reflect the real state of the calendar. This is the only issue I see so far. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
GPE Calendar can do that (and exceptions). Does Erminig-NG support GPE Calendar, or do you plan to do so in the future? |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Quote:
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
I am having an issue that I don't know if it is something I am missing or if something has a problem somewhere. This is my first time trying Erminig-NG. I made sure I had the dependencies covered and installed it per the instructions. I am able to do the initial sync in which it goes through the prompts to create Main locally, N900 on Google, cal_ti_calendar_private on Google, and Main on Google (there already is a Main though). I put a test event on the phone's calendar, and one in each of the Google calendar's (Main, N900, cal_ti_calendar_private, Main (second one)). When I do a sync (python2.5 erminig-ng), it looks like it is doing stuff, but there are no updated entries in the phone calendar or on Google calendars.
What am I doing wrong? This is the output: Code:
Nokia-N900-02-8:/home/user/erminig-ng-0.1.2# python2.5 erminig-ng |
All times are GMT. The time now is 15:33. |
vBulletin® Version 3.8.8