Re: [mer-general] Nemo/Mer merge update

[Andrea Bernabei]

2015-07-29 19:09 GMT+01:00 Carsten Munk :

> Those have always been considered as part of middleware (lipstick is a
> framework), Nemo UI/Glacier still sits on top outside mer core
>
>
how much is missing until we'll be able to build the old nemo setup? i.e.
releases, patterns, webhooks to updated repos ?

Or is that all done and just waiting for someone to actually set up the
patterns and webhooks?

2015-07-29 18:10 GMT+02:00 Timur Kristóf :
>
>> Hi,
>>
>> Just one question: how (if at all) does this change affect Nemo's UI and
>> its UI-related libraries (such as lipstick, mlite, ... etc)?
>>
>> Best regards,
>> Timur
>>
>> On Tue, 2015-07-28 at 15:22 +0100, David Greaves wrote:
>>
>> Hi all
>>
>> We've been working on the Nemo/Mer merge on and off for some time now and 
>> wanted
>> to provide an update.
>>
>> There's tl;dr; job if you're a maintainer: login to git.merproject.org so the
>> system 'sees' you and can grant permissions.
>>
>> The goal of this task is to merge the middleware packages from Nemo into Mer
>> Core and to move the git hosting from various Nemo and Mer repositories
>> scattered around github and other services into mer-core on 
>> git.merproject.org
>> (g.m.o)
>>
>> These are the main tasks:
>> * provide a mechanism to manage maintainer access rights
>> * create git repos on git.merproject.org
>> * ensure Mer OBS / webhooks point to g.m.o
>> * Improve visibility of Mer source/packages/maintainers
>>
>> Improving Visibility
>>
>> So, tackling the last point first there's a new "dashboard" here:
>>http://www.merproject.org/dash/index.html
>>
>> (That url may well change)
>>
>> The data shown is taken from :
>> * Maintainer file (see below) is the master for who has owner/master roles on
>> the git repos (when they move to Mer git)
>> * OBS _service files and other OBS data
>> * Mer gitlab
>> * Mer LDAP maps usernames to emails/real names
>> I'll add webhook data soon and it will master the mapping from git repo to 
>> OBS
>> packages
>>
>> There are still some issues but it's best to get a first draft out.
>>
>>
>> Managing Maintainership
>>
>> The approach taken for the maintainer rights is to create a text (yaml) file
>> that describes the access rights (developer/owner) for all the mer-core 
>> packages.
>> https://git.merproject.org/mer-core/Maintainers/blob/master/maintainers.yaml
>>
>> This allows anyone to quickly find out who maintains a particular package and
>> also allows automation systems to apply these permissions to g.m.o
>>
>> The commnity manages this file: anyone can submit a MR to it to change the
>> maintainership and if it's accepted by the mer-core maintainers the 
>> permission
>> changes will automatically be applied (well, eventually).
>>
>> Purely for ease of management/comprehension the file format supports the 
>> notion
>> of teams and package-groups but these are not reflected in gitlab for various
>> reasons. The team/group names are pretty arbitrary and can be changed 
>> trivially
>> - they just provide some context for the grouping.
>>
>> Creating git repos
>>
>> We've replicated about 170 repos from github projects:
>>   https://github.com/[nemomobile, nemomobile-packages, mer-packages]
>>
>> What I've done (hopefully!) is to take the current/old Mer master branch and
>> rename it to master-premerge. Then I've set mer/master to be the github 
>> master.
>>
>> In some cases where we've moved on from the old 'tarballs in git' there may 
>> be
>> no commits in common and we'll end up with an 'orphan' branch (google it)
>>
>> Maintainers should check the repos to make sure I've not messed up :)
>>
>> OBS
>> We'll be setting up webhooks for mer-core which should never need modifying. 
>> I
>> suspect that the OBS mer-core project will just have a few caretakers to 
>> handle
>> new packages on request.
>>
>>
>> Next Steps
>>
>> * These maintainers should login to https://git.merproject.org/ :
>>amccarthy antseppa blam chriadam giucam hmallat jpetrell mikkoh monich 
>> mvogt
>>pgerdt phdeswer rbraakman rozhkov sletta spiiroin VDVsx Venemo Vesuri
>>
>> * As development moves from github to mer-core the github repos should have a
>> redirection commit added (ie delete all files and create a README that sends
>> people to g.m.o)
>>
>>
>> David/lbt
>>
>>
>>
>>
>

Re: [mer-general] Nemo/Mer merge update

[Andrea Bernabei]

Great,

keep it going and thanks for the hard work!

2015-07-28 15:22 GMT+01:00 David Greaves :

> Hi all
>
> We've been working on the Nemo/Mer merge on and off for some time now and
> wanted to provide an update.
>
> There's tl;dr; job if you're a maintainer: login to git.merproject.org so
> the system 'sees' you and can grant permissions.
>
> The goal of this task is to merge the middleware packages from Nemo into
> Mer Core and to move the git hosting from various Nemo and Mer repositories
> scattered around github and other services into mer-core on
> git.merproject.org (g.m.o)
>
> These are the main tasks:
> * provide a mechanism to manage maintainer access rights
> * create git repos on git.merproject.org
> * ensure Mer OBS / webhooks point to g.m.o
> * Improve visibility of Mer source/packages/maintainers
>
> Improving Visibility
>
> So, tackling the last point first there's a new "dashboard" here:
>   http://www.merproject.org/dash/index.html
>
> (That url may well change)
>
> The data shown is taken from :
> * Maintainer file (see below) is the master for who has owner/master roles
> on the git repos (when they move to Mer git)
> * OBS _service files and other OBS data
> * Mer gitlab
> * Mer LDAP maps usernames to emails/real names
> I'll add webhook data soon and it will master the mapping from git repo to
> OBS packages
>
> There are still some issues but it's best to get a first draft out.
>
>
> Managing Maintainership
>
> The approach taken for the maintainer rights is to create a text (yaml)
> file that describes the access rights (developer/owner) for all the
> mer-core packages.
>
>
> https://git.merproject.org/mer-core/Maintainers/blob/master/maintainers.yaml
>
> This allows anyone to quickly find out who maintains a particular package
> and also allows automation systems to apply these permissions to g.m.o
>
> The commnity manages this file: anyone can submit a MR to it to change the
> maintainership and if it's accepted by the mer-core maintainers the
> permission changes will automatically be applied (well, eventually).
>
> Purely for ease of management/comprehension the file format supports the
> notion of teams and package-groups but these are not reflected in gitlab
> for various reasons. The team/group names are pretty arbitrary and can be
> changed trivially - they just provide some context for the grouping.
>
> Creating git repos
>
> We've replicated about 170 repos from github projects:
>  https://github.com/[nemomobile, nemomobile-packages, mer-packages]
>
> What I've done (hopefully!) is to take the current/old Mer master branch
> and rename it to master-premerge. Then I've set mer/master to be the github
> master.
>
> In some cases where we've moved on from the old 'tarballs in git' there
> may be no commits in common and we'll end up with an 'orphan' branch
> (google it)
>
> Maintainers should check the repos to make sure I've not messed up :)
>
> OBS
> We'll be setting up webhooks for mer-core which should never need
> modifying. I suspect that the OBS mer-core project will just have a few
> caretakers to handle new packages on request.
>
>
> Next Steps
>
> * These maintainers should login to https://git.merproject.org/ :
>   amccarthy antseppa blam chriadam giucam hmallat jpetrell mikkoh monich
> mvogt
>   pgerdt phdeswer rbraakman rozhkov sletta spiiroin VDVsx Venemo Vesuri
>
> * As development moves from github to mer-core the github repos should
> have a redirection commit added (ie delete all files and create a README
> that sends people to g.m.o)
>
>
> David/lbt
>
>
> --
> "Don't worry, you'll be fine; I saw it work in a cartoon once..."
>
>
> --
> To unsubscribe send a mail to :  mer-general+unsubscr...@lists.merproject.org>
>
>

Re: [mer-general] Mailing list restored

[Andrea Bernabei]

one problem could be that your message was in my spam folder :D

2015-07-06 15:21 GMT+01:00 David Greaves :

> Hi all
>
> First a "Thanks" to smoku for hosting the list for so long :)
>
> We've had a problem with the mailing list over the past few days which
> should now be resolved and it's been moved over to the mer core
> infrastructure.
>
> Please contact me if you have any problems from now on.
>
> Thanks
>
> David
>
> --
> "Don't worry, you'll be fine; I saw it work in a cartoon once..."
>
>
> --
> To unsubscribe send a mail to :  mer-general+unsubscr...@lists.merproject.org>
>
>

Re: [mer-general] community stand FOSDEM 2014

[Andrea Bernabei]

thanks for the wiki!

Let's set up something together! I'm still not sure I'll be able to attend
though :)

2014-10-08 19:16 GMT+02:00 Julius-Paul Jann :

> Hi,
>
> as we deiced yesterday during the SFOS-Meeting the community plans to have
> a stand at FOSDEM 2015.
>
> To organise the stand I created a wiki page. Fell free to add your self if
> you wanted.
>
> All details are --> https://wiki.merproject.org/wiki/FOSDEM_2015
>
> cheers
>
> Nokius
>

Re: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform

[Andrea Bernabei]

I think option 1) included moving repos to Mer GitLab, btw :P


2014-06-25 17:04 GMT+02:00 :

> (top post etc.)
>
> I don't know what's the state of the vote currently, but it seems that
> we didn't reached a consensus. However, I would like to add something to
> the topic (and change my mind).
>
> Actually, I'm wondering if what we are discussing makes sense. Well, of
> course
> the Nemo UI is a project that now (kinda) have it's own life, but I wonder
> why
> we shouldn't profit from the full Mer infra power: more a discussion about
> the
> hosting of the whole project instead of just the fate of the bugtracking
> system.
>
> We already compiles on mer buildservice, why just not use mer gitlab as
> well instead
> (or in complement) of github ? The bugtracking system can be decided
> later. We can
> see if devs prefer gitlab's bug tracking system, or if they still want a
> bz. And
> if devs want a bz, it might be better to use Mer bz as well, instead of
> having two
> bz instances.
>
> So the Nemo UI project would live as a subproject, directly inside Mer
> infra, a bit
> like Android Qt lived inside KDE infrastructure (before being attached to
> Digia).
>
> Of course, we still have to know if people of the Mer project are willing
> to provide a
> space for Nemo UI inside their infra (a category in BZ, a section in
> gitlab etc.)
>
> What do you think ?
>
>
>
> - Mail original -
> De: "Andrea Bernabei" 
> À: mer-general@lists.merproject.org
> Envoyé: Mardi 24 Juin 2014 23:39:59
> Objet: Re: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting
> platform
>
>
> From Aard on IRC:
>
>
> " faenil: when considering dropping bz in favour of github -- we're
> working on getting our CI infrastructure in shape that we can offer
> mer/nemo to set up their own like we're using for proper issue tracking
> over releases and stuff. if you move to github you won't be able to benefit
> from that"
>
>
> he also specified that he doesn't make any promise about how long that
> update is going to take, as it's a lot of work
>
>
> (also consider holidays are starting soon)
>
>
>
> 2014-06-24 22:26 GMT+02:00 Michael Demetriou < qwa...@gmail.com > :
>
>
> I'll vote for number 1 so that everyone votes for something different :P
>
> Jokes aside, I find gitlab to be a very nice system and I have come to
> trust third party providers very little (and incidentally, I just now
> received a message from one of my hosting providers that I have
> exactly one month to move my VPS away - not enough time to migrate
> properly).
>
> I don't mind github repos as migrating somewhere else is just a clone
> away, but issues aren't so portable (though there is a way to export).
>
> As a plus Gitlab allows you to see all issues (or all group issues) in
> one place.
>
>
>
>
>
>

Re: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform

[Andrea Bernabei]

>From Aard on IRC:

" faenil: when considering dropping bz in favour of github -- we're
working on getting our CI infrastructure in shape that we can offer
mer/nemo to set up their own like we're using for proper issue tracking
over releases and stuff. if you move to github you won't be able to benefit
from that"

he also specified that he doesn't make any promise about how long that
update is going to take, as it's a lot of work

(also consider holidays are starting soon)


2014-06-24 22:26 GMT+02:00 Michael Demetriou :

> I'll vote for number 1 so that everyone votes for something different :P
>
> Jokes aside, I find gitlab to be a very nice system and I have come to
> trust third party providers very little (and incidentally, I just now
> received a message from one of my hosting providers that I have
> exactly one month to move my VPS away - not enough time to migrate
> properly).
>
> I don't mind github repos as migrating somewhere else is just a clone
> away, but issues aren't so portable (though there is a way to export).
>
> As a plus Gitlab allows you to see all issues (or all group issues) in
> one place.
>
>
>

Re: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform

[Andrea Bernabei]

I'm still more inclined to vote 2 as I'm familiar with BZ and I like that
it's detailed. And also using buzilla means having a website which has only
one purpose, bug reporting. I like that I can visit sections and see bugs
for each piece of software, instead of having to visit repo URLs one by one
and click on their "issues" subpage...

But since I don't have much experience with GitLab and GitHub issues, don't
take my vote too seriously.

Whatever is okay to me.



2014-06-24 16:01 GMT+02:00 :

> Hi !
>
> (Mandatory: "Sorry for top posting, webmail")
> As I already said on IRC, I prefer not using bz, because it's heavy and
> hard to use.
> Not saying it's a bad tool, but for our developement, I would prefer
> having github
> issue tracking, that is much simpler to use, and have some other bonuses
> (integration
> in commit messages etc.)
>
> qwazix said that gitlab have an even better issue tracking. And we also
> have Mer gitlab, that
> might be even more integrated to the mer project (for example webhooks),
> so I would vote for
> 1. move to gitlab (have a specific Nemo UI section if it's possible)
> 2. stay on github
>
> - Mail original -
> De: "Andrea Bernabei" 
> À: mer-general@lists.merproject.org
> Envoyé: Mardi 24 Juin 2014 15:51:25
> Objet: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform
>
>
> Hello people :)
>
>
> Since Nemo Middleware is being folded into Mer Core, it's not clear what
> it will be of Nemo bugzilla instance.
>
>
> We either:
> 1) move Nemo UI repos to Mer Gitlab, and use gitlab as the bug reporting
> tool
> or 2) rename Nemo bugzilla to something and keep using that
> or 3) use github issues
>
>
> Please reply to this post expressing your opinion ;)
>
>
> The voting closes in 1 week! :)
>
>
>

[mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform

[Andrea Bernabei]

Hello people :)

Since Nemo Middleware is being folded into Mer Core, it's not clear what it
will be of Nemo bugzilla instance.

We either:
1) move Nemo UI repos to Mer Gitlab, and use gitlab as the bug reporting
tool
or 2) rename Nemo bugzilla to something and keep using that
or 3) use github issues

Please reply to this post expressing your opinion ;)

The voting closes in 1 week! :)

Re: [mer-general] [NEMO] Font replacement

[Andrea Bernabei]

Let's see if Nemo's design lead (nickname: qwazix) finds the time to reply
and see if he has already taken those fonts into account :) or if we're
about to replace Nemo's font with one of those you just suggested :D

thanks for the ideas! :)


2014-03-31 9:26 GMT+02:00 Alex Tenie :

> Alexandru Tenie/Deformat here.
>
> I've been searching for some alternate fonts, since the original font
> (Open Sans) didn't have extended language support.
> I've fount out about Intel's Clear Sans: https://01.org/clear-sans
> I've noticed that for normal text Clear Sans Medium could work rather well
> for various text (as you may test it here:
> http://www.fontsquirrel.com/fonts/clear-sans). For lockscreen, a more
> light version could work, or maybe the current font could work as well.
>
> I'd like to point out that there are also various other fonts with
> extended language support, such as Ubuntu's font and Firefox' Fira (Firo?)
> Font.
>
> Alexandru/Deformat
>

Re: [mer-general] n900 wayland

[Andrea Bernabei]

not right now*, I meant


2013/8/29 Andrea Bernabei 

> not right, someone has to make a proper .ks file for it :)
>
> it's not difficult, it should be able to start from but I don't have an
> N900 so I can't do that..
>
> but I can provide help on #nemomobile if anyone wants to try ;)
>
>
> 2013/8/29 Jukka Eklund 
>
>> Right, is there a Wayland image for N900 somewhere?
>>
>> -Jukka
>>
>>
>> On Thu, Aug 29, 2013 at 1:06 PM,  wrote:
>>
>>> Hi,
>>> i have n900, tell me thing i must try and i try it.
>>>  N.
>>> > Hi,
>>> >
>>> > On 29. aug. 2013, at 11:29, nic...@nicoladefilippo.it wrote:
>>> >> is expected nemo wayland for the N900?
>>> >
>>> > It might work. It might not. I don't have an N900 in serviceable
>>> condition
>>> > anymore (and too many other devices to work with, so please, no offers
>>> :P)
>>> > - so I wasn't able to test, but Carsten's original prototype ran on the
>>> > N900.
>>> >
>>> > Give it a shot, and give feedback!
>>> >
>>> > BR,
>>> >
>>> > RObin
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>>
>>>
>>
>

Re: [mer-general] n900 wayland

[Andrea Bernabei]

not right, someone has to make a proper .ks file for it :)

it's not difficult, it should be able to start from but I don't have an
N900 so I can't do that..

but I can provide help on #nemomobile if anyone wants to try ;)


2013/8/29 Jukka Eklund 

> Right, is there a Wayland image for N900 somewhere?
>
> -Jukka
>
>
> On Thu, Aug 29, 2013 at 1:06 PM,  wrote:
>
>> Hi,
>> i have n900, tell me thing i must try and i try it.
>>  N.
>> > Hi,
>> >
>> > On 29. aug. 2013, at 11:29, nic...@nicoladefilippo.it wrote:
>> >> is expected nemo wayland for the N900?
>> >
>> > It might work. It might not. I don't have an N900 in serviceable
>> condition
>> > anymore (and too many other devices to work with, so please, no offers
>> :P)
>> > - so I wasn't able to test, but Carsten's original prototype ran on the
>> > N900.
>> >
>> > Give it a shot, and give feedback!
>> >
>> > BR,
>> >
>> > RObin
>> >
>> >
>> >
>> >
>>
>>
>>
>>
>>
>

[mer-general] Re: [SailfishDevel] [WIP] Wayland Nemo VM Image (and new Nemo UI)

[Andrea Bernabei]

Hello people!
Here are some news for you, I wrote few paragraphs, with titles to help you
skim through the email in case you don't have much time to read it ;)


WAYLAND VM IMAGE UPDATE:

I didn't know anything about systemd, I didn't know anything about RPM
packaging, but I studied some stuff during last days, and now we have a
working Nemo Wayland image for VM!
The VM image boots to a QtQuick2/Qt5 homescreen (lipstick-colorful-home-qt5
package), and uses a Wayland QML compositor!
So now we have a VM image with a working homescreen (in early stages) and a
Wayland compositor!
Now that the we have something to base the rest of our work on, we need to
do some planning.



NEMO RESTYLING PLAN:

I'll share here the results of few chats with other Nemomobile guys
(qwazix, Sfiet_Konstantin, Hurrian, sorry if I'm forgetting anyone here)
and Jolla guys (Stskeeps, special, w00t,...):
1) First of all, we decided it was a good idea to port all Nemo QML apps to
Qt5/QtQuick2 and have them working on the new Wayland-based VM image;

2) Once all the core apps are ported to Qt5, we can start building the new
components sets (which will likely be QtQuickControls + custom controls)
which will be used to bring to life the new Glacier UI (if you don't know
what Glacier UI is, ---> http://play.qwazix.com/grog/?p=344 )

3) Once we have a working components set, we can port all Nemo QML apps to
the new components set created in step 2.

4) Test and bugfix

5) Enjoy the new Nemo with Glacier UI :D




CURRENT STATUS:

We're at step 1! We're porting all Nemo apps to QtQuick2/Qt5 using
com.nokia.meego components which have already been brought to QtQuick2 by
w00t.
I'll tell you what I know about the current porting status of the apps:
- special has already partially ported fingerterm (terminal emulator), and
qmlmessages
- I (faenil) have ported qmlcalc, the calculator, probably the easiest app
to port, which will be used as an example for those who want to know what
it means to port Nemo apps to QtQuick2
- the rest of the apps needs porting!




HOW CAN I HELP?

We're at step 1, so we need help porting all Nemo apps to Qt5/QtQuick2!
It's not much work! Don't feel like you're not expert enough do that,
anyone with some QML experience can help! :)
Here's an example of Qt5 port
https://github.com/nemomobile/qmlcalc/pull/11

As you can see it's mostly about renaming classes, changing few calls, and
then adapting the packaging files to the changes.


WHAT IF I DECIDED I WANT TO HELP?
Contact me, I'm faenil on #nemomobile IRC channel (freenode server).
I'll help you setup the wayland environment, so you can start hacking right
away! :)


This is all people!
Have a nice day! :)


2013/7/18 Dmitry 

> As i understand Sailfish OS in based on Mer, difference is very small ~10
> rpm packages.
> Why we can`t just use same packages that will be in Sailfish Emulator of
> Beta SDK?
>
>
> On 18 July 2013 19:03, Andrea Bernabei  wrote:
>
>> Hello guys :)
>>
>> We all know Sailfish has moved to Wayland and will use Wayland by default
>> in its first phone :)
>>
>> The time has come for us to start moving Nemo to Wayland as well!
>>
>> This will give us the opportunity to use the same middleware Jolla is
>> currently using, and it's our chance to switch to Qt5 and be as connected
>> to Sailfish OS development as possible!
>>
>> For the N9/N950 users: if you want to have the chance of seeing Sailfish
>> OS on your phone, please note that THIS is the way to go! No Wayland on
>> Nemo, no chance of having Sailfish on your phone! ;) Just to make things
>> clear :D
>>
>> So...what's the plan?
>>
>> Yesterday I started working on making a Nemo VM i486 image which is as
>> Qt4-free as possible, and uses Wayland by default.
>>
>> You can see the current status of this transition to Wayland here
>> https://wiki.merproject.org/wiki/Wayland_Nemo_VM_Image
>>
>> Stskeeps suggested starting from the VM as it has a stable hardware
>> adaptation, we can do Wayland images for the other platforms later on
>> (n9/n950 anyone? :D)
>>
>> Also, this whole Wayland/Qt5 thing is needed before we start implementing
>> stuff for the new Nemo UI (which is Glacier UI, at the moment), as it
>> wouldn't make sense to implement stuff in Qt4/X11 now and then port
>> everything to Qt5/Wayland shortly after that, right? :D
>>
>> After fixing all the needed bits on the wiki page (i.e. look for all the
>> Qt4 and Qt4-dependent packages we can get rid of, and write down which of
>> those can be replaced with their Qt5 ports) we have to change stuff in
>> Nemo's boot process (which is using systemd) so that the new qt5 services
>>

[mer-general] [WIP] Wayland Nemo VM Image (and new Nemo UI)

[Andrea Bernabei]

Hello guys :)

We all know Sailfish has moved to Wayland and will use Wayland by default
in its first phone :)

The time has come for us to start moving Nemo to Wayland as well!

This will give us the opportunity to use the same middleware Jolla is
currently using, and it's our chance to switch to Qt5 and be as connected
to Sailfish OS development as possible!

For the N9/N950 users: if you want to have the chance of seeing Sailfish OS
on your phone, please note that THIS is the way to go! No Wayland on Nemo,
no chance of having Sailfish on your phone! ;) Just to make things clear :D

So...what's the plan?

Yesterday I started working on making a Nemo VM i486 image which is as
Qt4-free as possible, and uses Wayland by default.

You can see the current status of this transition to Wayland here
https://wiki.merproject.org/wiki/Wayland_Nemo_VM_Image

Stskeeps suggested starting from the VM as it has a stable hardware
adaptation, we can do Wayland images for the other platforms later on
(n9/n950 anyone? :D)

Also, this whole Wayland/Qt5 thing is needed before we start implementing
stuff for the new Nemo UI (which is Glacier UI, at the moment), as it
wouldn't make sense to implement stuff in Qt4/X11 now and then port
everything to Qt5/Wayland shortly after that, right? :D

After fixing all the needed bits on the wiki page (i.e. look for all the
Qt4 and Qt4-dependent packages we can get rid of, and write down which of
those can be replaced with their Qt5 ports) we have to change stuff in
Nemo's boot process (which is using systemd) so that the new qt5 services
are used, and the Wayland compositor is run at startup, instead of the
current X11 compositor.

I know little about systemd at the moment, I'll start researching as I'm
done with the packages stuff...If you can help with systemd or can boost my
systemd knowledge, please contact me! :)

People from Jolla are already helping me, but they're often busy with other
stuff, and I can't waste too much of their time on this, I want them to
focus on Sailfish :D

So please bookmark the page I created, and if you want to help please come
talk to me at #nemomobile on IRC :)

This is all,
have a nice evening people!


faenil

Re: [mer-general] [Nemo] Moving forward with the user interface

[Andrea Bernabei]

Take your time,

I'm sure you won't disappoint :D


2013/6/25 Michael Demetriou 

> Hi all,
>
> I'm a bit late to this thread as this week has been ultra busy. I
> don't think I will have a real bunch of free time in the near future,
> however, drawing mockups is something I enjoy doing even in my little
> free time, so I happily accept being the design lead of nemo. I will
> present you the ideas described above soon, I just want to have a few
> more screens ready.
>
> Thank you all for the confidence, I believe we can make an awesome
> experience together.
>
> Michalis
>
>
>

Re: [mer-general] Re: [Nemo] Moving forward with the user interface

[Andrea Bernabei]

Hey people :)
I am finally able to express my opinions on this thread :)

First of all, I'm so sad I couldn't be part of such discussions on the
public chat, unfortunately I will be very busy until half July or some more
:(

Anyway...
Simply put: I'm with Venemo, I'm one of the guys who's been discussing with
him at Devaamo Summit about new homescreen ideas, and I, as him, would love
to move forward.

Let's face it, it's not like we have many people who are attracted by
current Nemo-Harmattan's swipeish interface, so I don't see anything wrong
in changing everything.

I think we can do much better, and I'd love to start the homescreen UI from
scratch (not talking about lipstick middleware of course, just the UI).

I see Nemo as a playfield for us who care about it and care about keeping a
fully open OS (from core to UI) alive, and I think experimenting with new
UXes can only make Nemo better.

I've been trying hard to come up with completely new ideas about a new
homescreen, but as you may imagine, it's no easy task :D

But still, I think we need something completely new, unique, and fresh.

Let's create a new interaction model, we can do this in Nemo! It's not like
we're tied to what we have, in fact there's none even actually using Nemo
daily, as it's not ready for that yet (though it's getting better and
better :) ).

About the graphical design:

I've seen what qwazix was sketching on his laptop at Devaamo Summit:
It's AWESOME stuff guys :D and I hope you'll be able to see it soon :D
I also agree about keeping discussions about the UI/UX in the mailing list,
so that all people who really care about the project can contribute their
ideas/opinions and help shape the future Nemomobile :)

About the components:
We have to keep compatibility with MeeGo components, but hey! Those
components look so old!
So, yeah, on one hand we HAVE TO keep compatibility and maintain them, but
on the other hand, let's start moving to QtQuick Controls as soon as
possible, as that is the future of Qt, in those regards.
New Qt5 mobile applications will use QQControls, so it surely makes sense
to start shaping them for Nemo, as applications will start popping up like
crazy as soon as Qt 5.2 hits iOS and Android with QQControls!





2013/6/24 Filip Kłębczyk 

> W dniu 24.06.2013 13:48, Timur Kristóf pisze:
>
>  Hi guys,
>>
>> Some discussion happened on IRC a few hours ago.
>> We discussed about things and in light of his knowledge and experience,
>> we are suggesting Michael /qwazix/ for the role of leading the creation
>> of the new design. Nobody was against this. I hope everyone agrees.
>>
>
> Yep that is what has happened today in the morning and during intensive
> and fruitful discussion, many  interesting links popped up thanks to Venemo:
> http://www.smashingmagazine.**com/2010/06/29/why-design-by-**
> commitee-should-die/
> http://en.wikipedia.org/wiki/**Design_by_committee
> http://www.thousandtyone.com/**blog/**CommitteeDrivenDevelopmentIsNo**
> tJustLameItsDangerous.aspx
> https://mail.gnome.org/**archives/desktop-devel-list/**
> 2006-February/msg00115.html
>
> And cause everyone loves videos here also good one found by Lucien:
> http://www.youtube.com/watch?**v=Wac3aGn5twc
>
> Pasted by Stskeeps:
> http://en.wikipedia.org/wiki/**Participatory_design
>
> So in general idea of choosing a design lead appeared and we got to the
> point that the right man for that task would be qwazix as he probably has
> the biggest experience here when it comes to design.
>
> Regards,
> Filip
>
> PS. Since last Devaamo, Micheal /qwazix/ is also known as Michalis (that
> is how his name sounds nicely in the Greek language).
>
>
>

Re: [mer-general] [NEMO] Twitter account reborn!

[Andrea Bernabei]

awesome! :D


2013/5/1 Simonas Leleiva 

> Dear all,
>
> We've resuscitated @nemomobile in Twitter [1]. Everyone's welcome to
> follow!
>
> The followers of previously inactive account have been sadly lost, please
> re-follow.
> I'm working with Twitter, who initially promised to bring those 19 folks
> back :)
>
>
> [1] https://twitter.com/nemomobile
>
> Cheers,
> Simonas
>

Re: [mer-general] N9 kernel update project news

[Andrea Bernabei]

cool! Keep rocking :)


2012/11/9 Kalle Jokiniemi 

> Hello,
>
> Some news on the N9 kernel update project. There has been quite a lot of
> activity and we have now more working stuff on 3.5.3 kernel:
> - WLAN working (needs new firmware, but that is on the way ;)
> - USB networking
> - PowerVR 3D drivers
> - Display drivers
> - Touch drivers
> - BT (at least scanning works now)
>
> Effectively you can now run the UI with the new kernel and use the
> device for development. The rpm for kernel can be found here:
>
>
> https://build.pub.meego.com/package/binaries?package=kernel-adaptation-n950&project=home%3Akjokinie%3AN9update&repository=CE_Adaptation_N9xx-common_armv7hl
>
> And git web home here:
> https://github.com/nemomobile/kernel-adaptation-n950-n9
>
> Happy hacking :) and as always, use at your own risk.
>
> See the wiki for more details:
> https://wiki.merproject.org/wiki/N9_Kernel_update_project
>
> For those interested, I did some changes to the packaging also to make
> it work same way as the PR 1.3 based old kernel.
>
> - Kalle
>
>
>
>

Re: [mer-general] [NEMO] Social presence and branding

[Andrea Bernabei]

I like the logo, but it actually looks like a "lock" to me :)
which isn't exactly the kind of message we want to deliver...

I don't know, I keep seeing a lock in that image :)

2012/10/12 Ross Kendall 

>  +1
>
>
> On 12/10/12 12:48, Timur Kristóf wrote:
>
>
>  If everyone likes it, why not just make it the official Nemo logo? If
> there are issues, let the author know and give him a chance to fix.
>
> I personally think that it's both elegant and stylish - I would vote for
> making it the official Nemo logo right now.
>
>
>
>