From frederik.elwert at web.de Sun May 16 14:33:03 2010 From: frederik.elwert at web.de (Frederik Elwert) Date: Sun, 16 May 2010 16:33:03 +0200 Subject: [Genesis-devs] Genesis' future Message-ID: <1274020383.1644.38.camel@frederik-laptop> Hello everybody, I?m crossposting this on SyncEvolution and Genesis mailing lists, as it might be interesting for all. I am currently thinking about the future direction of Genesis development. Genesis started with very limited aims: I didn?t want to open a terminal window in order to execute syncevolution, so Genesis provided a notification area icon which could start syncs and informed about the results using libnotify. Since syncevolution didn?t have a GUI, a simple setup assistant was added to make it easier to get started with SyncEvolution. And Genesis allowed for automated syncs. The situation has changed, though. SyncEvolution now ships its own GUI, sync-ui. Automated syncs are in the syncevolution core. And SyncEvolution grows quite fast feature-wise, e.g. Bluetooth sync, HTTP-Server support, etc. This leads to a situation where I want to think about the future of Genesis. I can think of two possible directions: 1. Make Genesis a full SyncEvolution GUI, which can serve as a replacement for sync-ui. Since sync-ui is tailored towards Netbooks and looks a bit awkward in a standard GNOME environment, having a more desktop-like alternative might be appreciated. David?s current work on an Account Manager for Genesis leads in this direction, but quite a lot of effort would be needed in order to make Genesis nearly as complete as sync-ui. (Most visible: Bluetooh support, mostly invisible, but important: Error handling.) 2. Go back to the roots and leave everything else to sync-ui. Genesis could limit itself to providing a status icon for quick access and provide notifications. It should then integrate tighter with sync-ui (e.g., show notifications also for sync-ui triggered syncs, open sync-ui for configuration tasks, etc.). First work is done by switching to D-Bus for SE session handling. I currently tend towards the second option. My time for working on Genesis is limited, and so it makes sense not to duplicate the work that already was made for sync-ui. But it would also be possible to split Genesis? current features into two separate components: A small status +notification app and a stand-alone application with account management and all. Before I definitely decide on this, I would like to hear your opinion: As developers, but even more as users. What would be your favorite Genesis? And if anyone wants to work on Genesis, in one direction or the other, help is always appreciated. Cheers, Frederik _______________________________________________ Mailing list: https://launchpad.net/~genesis-devs Post to : genesis-devs at lists.launchpad.net Unsubscribe : https://launchpad.net/~genesis-devs More help : https://help.launchpad.net/ListHelp From frederik.elwert at web.de Sun May 30 20:40:17 2010 From: frederik.elwert at web.de (Frederik Elwert) Date: Sun, 30 May 2010 22:40:17 +0200 Subject: [Genesis-devs] Genesis' future In-Reply-To: <1274020383.1644.38.camel@frederik-laptop> References: <1274020383.1644.38.camel@frederik-laptop> Message-ID: <1275252018.2274.8.camel@frederik-laptop> Just a short update: A first test release for a new, rewritten Genesis is available for Ubuntu 10.04 users. Other platforms will follow as the rewrite matures. For background information, please read https://launchpad.net/genesis-sync/+announcement/5958 I?ll stop spamming the syncevolution list with messages like this, so if you are interested in Genesis? development, I suggest subscribing to the announcements or joining the team. Frederik _______________________________________________ Mailing list: https://launchpad.net/~genesis-devs Post to : genesis-devs at lists.launchpad.net Unsubscribe : https://launchpad.net/~genesis-devs More help : https://help.launchpad.net/ListHelp From patrick.ohly at gmx.de Thu May 20 07:14:59 2010 From: patrick.ohly at gmx.de (Patrick Ohly) Date: Thu, 20 May 2010 09:14:59 +0200 Subject: migration of git repository Message-ID: <1274339697.22741.319.camel@pohly-mobl1.ikn.intel.com> Hello! The intention is to move the git repositories for SyncEvolution and our branch of libsynthesis from git.moblin.org to meego.gitorious.org. git can mirror repositories, so moving the data is easy. I already copied a current snapshot: http://meego.gitorious.org/meego-middleware/syncevolution http://meego.gitorious.org/meego-middleware/libsynthesis Right now, the repos on moblin.org are still the ones where changes are made first. We need to coordinate the switch a bit: * I need to change translate.moblin.org so that it pushes into the new repos. * Developers need to change the URL in their .git/config file: replace "git.moblin.org:" with "gitorious.org:meego-middleware/". The old repos will stay around, which may become confusing when people go there and only find old code. Should we set up a mirror script or request that the repos be removed? I'd like switch fairly soon, perhaps even today. The reason for the haste is that our nightly build server has issues checking out the sources from moblin.org. gitorious.org seems to work better. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.