On Wed, 2007-12-05 at 16:29 +0000, John Carr wrote: > Lo all > > On 12/5/07, Jonny Lamb <[EMAIL PROTECTED]> wrote: > Hi everyone. > > A fairly long email with some various thoughts on several > things. This > is meant to spark up discussion, so please do reply! > > 0.11 > ==== > > I think this needs to be released pretty soon. However, there > are some > things that need to be sorted first: > > * Documentation -- yes this is the obvious one. Nothing really > to say > about this. > > I tried to start discussion about this earlier - mainly the best way > to structure the new wiki stuff and specifically how to deal with > distrubtuion specific bits without the duplication getting crazy.
The ideal way i think is to have a small team, of 2 or 3 individuals working on the documentation, a small team working closely together on this should be able to bring the documentation up to date in no time, even a one man team should be able to do it in little time. > * Various fixes -- known bugs in the software that don't > require a > whole new rewrite should really be fixed before the > release. Please > can you all reply with problems that spring to mind when I > speak > about this, so I can keep track of the progress. > > Rather a general "what needs to be done" list. Please do reply > with > specifics! I suppose I'm suggesting we put in a freeze now > and > concentrate on bugs, for the release. > > Stuff I had wanted to see before 0.11: > > * Data loss bug on WM6 phones when partnership is deleted - jagow is > close on that > * Mess with wbxml. I have some basic pure python wbxml that we could > think about using, but i'm almost ashamed to admit it right now - not > really had time for it and code is a messy port of some PHP > * HAL integration - a HAL callout that: > * dhcp-ifies a device > * starts odccm with the ips that dhcp sorted out (if not running) > * starts sync-engine (if not running) > > If this doesn't make it for 0.11, any objections to a 0.12 closely > following when these bits are ready? I like the HAL idea alot, but i don't know if HAL reacts to eg a bluetooth device connecting to the PC > 0.10.0 to 0.11 (There's no point in an extra ".0" in "0.11" as > there's > not going to be a "0.11.1" -- "0.10.0" was perhaps a little > optimistic!) > isn't going to be the biggest update ever, but there are > several nice > new features or fixes. Things that come to my mind now: > > * Samsung SC* phones fixed with usb-rndis-lite. > * odccm now supports legacy devices. > * WM6 support. > * Various other fixes in SyncEngine. > > Again, please fill the gaps here. > > I think a new release will be very good for the project. It > will provide > milestones that will be acceptable and doable for developers. > It will > show SynCE as still being active and the new docs will make > the project > more usable. The docs are currently what is stopping me > pursuing > actually getting packages into Debian (and then perhaps > Ubuntu), so that > would be started again. > > Have been in talks with Ubuntu (wrt Conduit and sync that "just works" > - you plug it in and it says "where sync to.. k thx bye") and its > likely that we'll see some support into pulling the latest and > greatest into the next release (probably more in terms of acceptance > rather than actual man hours)... I wrote that initial draft, conduit seems like an excellent 'glue' to tie synce and eg gnokii together. > Further goals > ============= > > After 0.11 there will be some other features and fixes that > will be > worth investing time in. Two I can think of now are: > > * Simplifying the installation process, significantly. > > Helping main distros get everything packaged and the hal callout i > mentioned should do this. > > I'd like to see odccm be per device if its possible. And use HAL to > close each odccm when its own device is removed.. Any device > properties should be stashed in HAL rather than apps having to talk to > odccm. It seems a large chunk of odccm is boilerplate :-( > > In terms of supporting device passwords, blackberry also works in a > similar way and i'm pushing for some freedesktop-ish hook for storing > passwords in the keyring so that they can be automatically unlocked - > where we share as much as possible with barry (which is effectively > the synce of blackberry) Using keyrings sounds like a good idea. > * Removing the libwbxml dependency. > > If you have any other ideas, please state them here. If the > idea has not > previously been aired, please give some information about it. > > There is no "modern" way to sync 2003 devices. You seem to have to use > ancient programs like a pre-opensync version of multisync. About 1 in > 5 #synce requests is WM2003 related... That was a guess. Enough for it > to bother me that we don't offer support any more :P You want to drop WM2003? > Other talking points > ==================== > > vdccm: It seems to me that the only advantage of vdccm is its > multiple > device support. Therefore, I am suggesting dropping vdccm as a > proper > SynCE module. I'm not saying it should be deleted from SVN, > but just > left out of releases. Thoughts? > > I presume vdcccm won't support WM6? It also doesn't work with > sync-engine. Unfortunately dropping it hurts KDE users, who often ask > about RAKI. I have no idea what exactly that is, but seems not to work > with odccm. Yet. I am strongly in favor of having just one *dccm. > Either RAKI support in odccm or another standalone proggy, or vdccm > needs to be extended for WM6 and needs to be made to work with > sync-engine? vdccm also works with the ancient multisync for wm2003 devices With kind regards, ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
