Re: Mobile devices synchronization repository

Christopher Stender <[email protected]> Fri, 19 Jun 2009 17:01:27 +0200
Newsgroups gmane.linux.suse.laptop
Organization SUSE Linux Products GmbH
Message-ID <[email protected]>
--nextPart3079436.zpSJjiuCBv
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Friday 19 June 2009 14:40:36 schrieb Michal Hrusecky:
> Hi all,
>
> I've decided to continue this discussion somewhere more in public. For
> people who were not involved from the begining, let's repeat what's
> going on.
>
> We've got plan for opening openSUSE Factory development. And part of
> this plan is maintaining all openSUSE packages in some repositories in
> buildservice. What I was proposing was to create one repository for
> Palm/Windows Mobile/whatever your device use synchronization programs. I
> sent mails to SynCE maintainers and OpenSync maintainers and it seems
> like some maintainers agrees that common project for these stuff is a
> good idea.

Sounds good to me. Nevertheless I would like to keep subprojects (see below=
).

> What is left is the name of this project. I discussed it with darix and
> as we already have network:synchronization project, he proposed that we
> can maintain our packages in there. Feedback I've got from other
> maintainers suggest that we all would prefer something with name that
> would suggest that it's about mobile devices so users wouldn't need to
> know where to look and it may be obvious from project name. On the other
> hand I agree with darix that we should try to minimalize pollution of
> buildservice by creating other synchronization project. So I'm
> suggesting network:synchronization:mobile as a project name. This way we
> will have something with mobile and synchronization in it and we
> wouldn't polute buildservice much.

We should definitely use another repository because network:synchronization=
 is=20
IMHO for stuff like rsync or csync and has nothing todo with Mobile/PIM=20
synchronization. What about "Synchronization" as a new toplevel project?=20
=46urthermore, I would like to keep subprojects like:

Synchronization:OpenSync:Factory (devel project for factory)
Synchronization:OpenSync:SVN (svn snapshots)

and maybe for released versions which are still maintained:

Synchronization:OpenSync:$VERSION

What do you think?

Best regards,
Christopher
=2D-=20
Christopher Stender, R&D Team Mobile Devices
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N=C3=BCrnberg)
Maxfeldstra=C3=9Fe 5, 90409 N=C3=BCrnberg, Germany

--nextPart3079436.zpSJjiuCBv
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAko7qEcACgkQIGYPXCMC/zexhwCfcwoRaryQAW/hBl0ESRkLsPNK
zlMAoJluD4Obmjiq0IxspZZAZw/3hl+y
=taib
-----END PGP SIGNATURE-----

--nextPart3079436.zpSJjiuCBv--