2014-04-13 14:14 GMT+02:00 Marko Saukko <marko.sau...@gmail.com>: > On 04/13/2014 01:55 PM, Carsten Munk wrote: > ... > >> * Updated Systemd to 208 >> >> (Primary maintainer, Pekka Lundstroem) >> >> http://github.com/mer-packages/systemd >> https://github.com/mer-packages/kmod.git >> https://github.com/nemomobile/systemd-user-session-targets.git (new) > > > Should be noted that this will drop support for hw adaptations that have > kernel older than 3.0 by default. There might be way to backport some > patches to the respective hw adaptation kernels to maintain those > adaptations. > > >> * Project config enablers to make X11-less builds in Mer, which will >> be default off (i.e. X11 enabled) in Mer QA builds and general package >> updates/build system adjustments: >> > > Will this mean that libX* packages and dependencies will be dropped from mer > core? Inverse, what I meant was that we add enablers for doing X11-less builds, but we don't drop X11 in default Mer builds.
> >> https://github.com/mer-packages/boardname.git > > > boardname should be dropped in favor of ssu and oneshot. There is already > ongoing work to do this but not sure if it was finalized properly yet. > > ... > >> >> Package Management daemon and bindings: >> >> https://github.com/nemomobile-packages/PackageKit-Qt.git >> https://github.com/nemomobile-packages/PackageKit.git >> https://github.com/nemomobile-packages/polkit-qt-1.git >> >> (Primary maintainer: Thomas Perl) > > > Will we continue supporting zypper in the future? Yes, zypper is a frontend to libzypp in practice. > > >> >> Synchronization framework: (not obligatory) >> >> https://github.com/nemomobile/buteo-mtp.git >> https://github.com/nemomobile/buteo-sync-plugins-google-simple.git >> https://github.com/nemomobile/buteo-sync-plugins-google.git >> https://github.com/nemomobile/buteo-sync-plugins.git >> https://github.com/nemomobile/buteo-syncfw.git >> https://github.com/nemomobile/buteo-syncml.git > > > I would say we should get these in as synchronization is one of the main > features in any mobile device. > > ... > >> Primary maintainer: Thomas Perl (thp) >> >> Media indexing framework (optional): >> https://github.com/nemomobile/libqtsparql.git >> https://github.com/nemomobile-packages/tracker.git >> https://github.com/nemomobile/tumbler.git >> [and likely a boatload of the dependencies below] > > > I think most of the deps are already listed after the rest of the things > would be merged. I would propose that we evaluate this after everything else > is merged to see how much it actually takes as maintenance load. In the end > I don't think it is much if we just limit it to media indexing. > > ... > >> Additional packages for discussion if they're alive or not and if >> other packages above depend on them and if they are not more part of >> UI. > > > From this list I would mainly pick the ones that are dependencies for > everything else. Couple of comments though: > > ... >> >> >> https://github.com/nemomobile/profiled.git > > > Maybe this should be taken as part of mer? I'm unsure if it's even used at all. But I'd like to be proven wrong. > > ... >> >> https://github.com/nemomobile/sd-utils.git > > > We are missing sd card and mass storage handling in general from Mer. > > ... > >> >> If you claim meritocratic maintainership to any of these packages, >> please let me know and we'll set up access rights for merging and >> review rights accordingily after 1st of May 2014 if proposal holds. > > > I can take some maintainership of some of the generic packages that I've > done general updates in the past as well. But lets see what is left, we > should probably collect wiki page about all the packages with primary > maintainer listed. > > >> Protesting to the architectural and location move of your component is >> perfectly valid to do, as well. >> >> I believe from an architectural and project point of view that this >> move will strengthen Mer and related Nemo middleware components as a >> open source mobile platform in it's own right and make contribution >> and participation easier to understand, explain and do. >> >> With best regards, >> Carsten Munk >> Mer project architect >> > > Very nicely put. Thank you for the effort. > > Best Regards, > Marko "Sage" Saukko > One of the Mer maintainers that just stopped having enough free time :/ > > >
