Mobile devices synchronization repository
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. 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. Last thing to add, I think that we can use mobile@opensuse.org to discuss things about this repository and about development of packages there. I think that traffic here is quite low so it can handle it without problems and it's mailing list already focused on supporting mobile devices... -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
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 IMHO for stuff like rsync or csync and has nothing todo with Mobile/PIM synchronization. What about "Synchronization" as a new toplevel project? Furthermore, 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 -- Christopher Stender, R&D Team Mobile Devices SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
Christopher Stender - 17:01 19.06.09 wrote:
We should definitely use another repository because network:synchronization is IMHO for stuff like rsync or csync and has nothing todo with Mobile/PIM synchronization. What about "Synchronization" as a new toplevel project?
Well, things like rsync already has subproject network:synchronization:files and they are using it for some time already I guess, so moving them somewhere else is out of question. We can create another synchronization repository, but toplevel synchronization directory will be confusing for users searching for rsync and such. I agree, that network:synchronization isn't the best name for this kind of project, although for example opensync can be used to synchronize network stuff as well (Gmail, LDAP, ...) and pilot-link can be used to synchronize your PDA over network too... I would vote for mobile:synchronization too as suggested as it possibly can contain in future other mobile stuff as well - for example ringtone editors, mobile java, maybe even openSUSE Mobile Edition (I guess it would be nice top-level repository for things like Maemo or Moblin, but they already has their own top-level repositories) darix: Do you think that mobile:synchronization would be too much polluting the namespace?
Furthermore, 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?
I agree that several versions of the same package can be certainly useful for users. But I would suggest to keep all our packages in same project to make it easier for users. OpenSync is again great example. If we split packages under subrepositories then with new PDA I as a user would need to add SMT:OpenSync repository and ROOT:Palm/ROOT:WinCE/ROOT:Whatever repository. I would suggest to have something like ROOT:STABLE for package from last released openSUSE (well tested package available even for older distributions if possible), ROOT:FACTORY for factory devel version and ROOT:UNSTABLE for SVN builds, alpha version testing and such. But this can be probably achieved by linking/agregating from other subproject if you need/want them anyway. -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
Michal Hrusecky - 12:28 22.06.09 wrote:
Christopher Stender - 17:01 19.06.09 wrote:
We should definitely use another repository because network:synchronization is IMHO for stuff like rsync or csync and has nothing todo with Mobile/PIM synchronization. What about "Synchronization" as a new toplevel project?
Well, things like rsync already has subproject network:synchronization:files and they are using it for some time already I guess, so moving them somewhere else is out of question. We can create another synchronization repository, but toplevel synchronization directory will be confusing for users searching for rsync and such. I agree, that network:synchronization isn't the best name for this kind of project, although for example opensync can be used to synchronize network stuff as well (Gmail, LDAP, ...) and pilot-link can be used to synchronize your PDA over network too... I would vote for mobile:synchronization too as suggested as it possibly can contain in future other mobile stuff as well - for example ringtone editors, mobile java, maybe even openSUSE Mobile Edition (I guess it would be nice top-level repository for things like Maemo or Moblin, but they already has their own top-level repositories)
darix: Do you think that mobile:synchronization would be too much polluting the namespace?
I spoked with my co-worker and there already some packages which would fit nicely into mobile but wouldn't fit into network:synchronization. For example wammu, gammu which are currently in hardware project or palm-db-tools. Maybe to avoid polution hardware:mobile:{synchronization,utils} doesn't sound bad either... -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
Am Monday 22 June 2009 12:28:15 schrieb Michal Hrusecky:
Christopher Stender - 17:01 19.06.09 wrote:
We should definitely use another repository because network:synchronization is IMHO for stuff like rsync or csync and has nothing todo with Mobile/PIM synchronization. What about "Synchronization" as a new toplevel project?
Well, things like rsync already has subproject network:synchronization:files and they are using it for some time already I guess, so moving them somewhere else is out of question. We can create another synchronization repository, but toplevel synchronization directory will be confusing for users searching for rsync and such. I agree, that network:synchronization isn't the best name for this kind of project, although for example opensync can be used to synchronize network stuff as well (Gmail, LDAP, ...) and pilot-link can be used to synchronize your PDA over network too... I would vote for mobile:synchronization too as suggested as it possibly can contain in future other mobile stuff as well - for example ringtone editors, mobile java, maybe even openSUSE Mobile Edition (I guess it would be nice top-level repository for things like Maemo or Moblin, but they already has their own top-level repositories)
darix: Do you think that mobile:synchronization would be too much polluting the namespace?
We can drop the OpenSync toplevel project as soon as we have mobile:synchronization. So we don't increase the number of toplevel projects.
Furthermore, 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?
I agree that several versions of the same package can be certainly useful for users. But I would suggest to keep all our packages in same project to make it easier for users. OpenSync is again great example. If we split packages under subrepositories then with new PDA I as a user would need to add SMT:OpenSync repository and ROOT:Palm/ROOT:WinCE/ROOT:Whatever repository. I would suggest to have something like ROOT:STABLE for package from last released openSUSE (well tested package available even for older distributions if possible), ROOT:FACTORY for factory devel version and ROOT:UNSTABLE for SVN builds, alpha version testing and such. But this can be probably achieved by linking/agregating from other subproject if you need/want them anyway.
Okay, I can live with that. Best regards, Christopher -- Christopher Stender, R&D Team Mobile Devices SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany
Quoting Michal Hrusecky, On 06/19/2009 02:40 PM:
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.
To my mind in that case synchronization should be moved to something like Office:Synchronization. Because this is not a networking subproject, most people would not find it there. Cheers, Johannes -- To unsubscribe, e-mail: opensuse-mobile+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mobile+help@opensuse.org
participants (3)
-
Christopher Stender -
Johannes Engel -
Michal Hrusecky