SyncEvolution 0.4
TCP/IP SyncML and CalDAV/CardDAV client
SyncEvolution allows you to sync your contacts and calendar with SyncML
and CalDAV/CardDAV servers on the Internet, such as Funambol, Ovi,
Google Contacts, and Google Calendar.
The GUI in this package is custom-made for Maemo 5.
Section:
user/office
Repository:
Depends:
Size:
19914 bytes
MD5sum:
1205f6f18f73c315a8e7de7f256d49b3
Source:
Status:
Old version cleaned by repository management
Bugtracker:
QA Quarantine ends:
ENDED 2010-03-06 18:38
Changes
| Version | Changes | Author | Date |
| 0.4 | * Detect stale sync locks. * Deleting services work again. | ovek@arcticnet.no | 2010-03-03 09:53 UTC |
Package events
| Event type | User | Timestamp |
| Old version cleaned by repository management | System | 2010-04-07 15:23 UTC |
| Package imported | System | 2010-03-06 18:38 UTC |

Comments:
I was trying to be helpful in providing feedback. When I encountered my first bug with the syncevolution-frontend, I didn't find this component on http://bugzilla.moblin.org/. I also didn't find your name in any of the "Assign To:"/"QA Contact:"-fields on the SyncML product page. Therefore I was absolutely certain that http://bugzilla.moblin.org/ is the wrong place to search for or report bugs about the Maemo frontend. I chose to comment about it in the forum instead.
Giving http://bugzilla.moblin.org/enter_bug.cgi?product=SyncEvolution&component=SyncEvolution as the bug tracker URL would have been more helpful for me. Maybe for others too.
You seem to have a strong opinion about this bug tracker thing, which I didn't know. Sorry for bringing it up again. There's other places where this question is actively discussed. Better not continue here.
Use the SyncEvolution product on Moblin. Bugs about the frontend gets assigned to me.
Bugzilla is admittedly a bit of an annoying type of bugtracker, in that there's no "home page" for each product, but I probably can't tell Moblin to switch bug trackers simply because of some Maemo policy.
I refuse to make the bugtracker link a direct link to an "enter new bug" page like the policy suggests, that's pure idiocy. Browsing existing bugs is infinitely more useful than being able to blindly enter new ones, and even with the current generic link, browsing is harder than entering new bugs. Users should be encouraged to browse bugs. The last thing anyone needs is to make it easier to enter new bugs without browsing existing bugs first. Having a direct link to the enter-bug page only makes sense if there's also another control fields, with an url to browse bugs. Currently, there's only one field available, so I'm stuck with a generic link to allow you to do both.
(Perhaps I could make it a link to a simple query of existing SyncEvolution bugs, but that's not ideal either, and probably isn't something your policy would accept anyway, as the Bugzilla search result page doesn't make it easier to enter a new bug than the generic Bugzilla link does.)
If that means my package won't make it out of Extras-testing, well, suit yourself. I made this package because it was useful to me, and I uploaded it here thinking it might be useful to others. If the package is considered useless because of issues with Bugzilla, then well, that's up to them. I don't need it to be in Extras, it's still useful to me.
Ove: Again, the "bug tracker" you provided as a link wont let anyone report bugs against syncevolution-frontend.
Which component of syncevolution do you expect users to select if reporting bugs against the Maemo GUI? And if you have anything particular in mind - why not set it in the bugtracker link instead of pointing to http://bugzilla.moblin.org/ only?
Comments:
You must be logged in to make comments.