← Back to team overview

gtg team mailing list archive

[Bug 614523] [NEW] Personal (teamwork?) organizer suite / interoperability standards

 

Public bug reported:

>From http://www.mail-archive.com/gtg-
contributors@xxxxxxxxxxxxxxxxxxx/msg00109.html :

"""
Personally, I'm dreaming of a "Personal organizer suite" with stuffs
like gtg, hamster, a calendar and tomboy (or equivalent), everything
working together. (I don't mind seeing the "gtg" brand disappearing from
user sight if needed).
"""

Perhaps the best way to achieve this is to work with particular sibling
projects to come up with interoperability standards:

 * Commonality in date formats (i.e. respect 'soon', 'now', etc.)

 * D-BUS API design consistency

 * Standardized data structures for common data objects (tasks, notes,
contacts, ...)

We can consider this particular bug report complete once we have held a
session on this topic at a Linux conference that includes at least 3
other sibling projects, and come up with some action items to improve
interoperability between organizer tools.

** Affects: gtg
     Importance: Undecided
         Status: New

-- 
Personal (teamwork?) organizer suite / interoperability standards
https://bugs.launchpad.net/bugs/614523
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: New

Bug description:
>From http://www.mail-archive.com/gtg-contributors@xxxxxxxxxxxxxxxxxxx/msg00109.html :

"""
Personally, I'm dreaming of a "Personal organizer suite" with stuffs
like gtg, hamster, a calendar and tomboy (or equivalent), everything
working together. (I don't mind seeing the "gtg" brand disappearing from
user sight if needed).
"""

Perhaps the best way to achieve this is to work with particular sibling projects to come up with interoperability standards:

 * Commonality in date formats (i.e. respect 'soon', 'now', etc.)

 * D-BUS API design consistency 

 * Standardized data structures for common data objects (tasks, notes, contacts, ...)

We can consider this particular bug report complete once we have held a session on this topic at a Linux conference that includes at least 3 other sibling projects, and come up with some action items to improve interoperability between organizer tools.





Follow ups

References