Summary of the changes on the repo

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Summary of the changes on the repo

Julien Cassignol
Hi everyone,

In order for all of you to keep in touch with the recent changes I
made on the repository, I'd like to sum up some things:

1) We recently applied the OE name change: recipes are now stored in
openembedded/recipes instead of openembedded/packages. Please check
your conf files for "packages" in your build tree and replace it with
recipes.
2) As planned a long time ago, all the openmoko-*3 packages have been
renamed to shr-*. We now have shr-contacts, shr-dialer, shr-messages
instead of their openmoko equivalent.
3) All the configuration files, themes, and specific settings have
been removed from the overlay, in order to separate things in a
cleaner way. They are now where they are supposed to be, that is the
shr-themes repository.
4) All the SHR-specific recipes have been migrated to a recipes/shr
subdirectory, in order to group them for the soon to come OE commit.
5) Testing has been merged with unstable. The two of them are currently equal.

What we'll do in the next few days:
1) Devise a specific distro.conf in order to be compliant with OE
policies, and to be able to ship "our" distro.
2) Migrate all the patches we currently have on top of OE in our
overlay in either specific recipes, or commit them upstream
3) Review, modify according to OE policies, and commit all our recipes to OE.

There is a lot of work currently, and the face of unstable might
change a lot (with the upcoming integration of opimd and ophonekitd
vala, notably), so be wary and check the commit logs.

Please keep in mind the following: the target date for the stable
release is May 22nd, for FSOSHRUDCON. So meanwhile, please flash
testing, whine/complain/help us as much as you can :-)

Do not hesitate to comment!

--
Julien Cassignol
http://www.ainulindale.net

_______________________________________________
Shr-devel mailing list
[hidden email]
http://lists.projects.openmoko.org/mailman/listinfo/shr-devel
Reply | Threaded
Open this post in threaded view
|

Re: Summary of the changes on the repo

Nicola Mfb
2009/4/16 Julien Cassignol <[hidden email]>:
[...]
> There is a lot of work currently, and the face of unstable might
> change a lot (with the upcoming integration of opimd and ophonekitd
> vala, notably), so be wary and check the commit logs.
>
> Please keep in mind the following: the target date for the stable
> release is May 22nd, for FSOSHRUDCON. So meanwhile, please flash
> testing, whine/complain/help us as much as you can :-)
>
> Do not hesitate to comment!

Great! thanks for your effort.
So we'll have the first release of SHR without opimd support?
Was this decided only to beat OM in releasing the first stable FSO
based distro? :)))

     Nicola

_______________________________________________
Shr-devel mailing list
[hidden email]
http://lists.projects.openmoko.org/mailman/listinfo/shr-devel
Reply | Threaded
Open this post in threaded view
|

Re: Summary of the changes on the repo

spaetz
In reply to this post by Julien Cassignol
Julien Cassignol wrote:
> Hi everyone,
>
> In order for all of you to keep in touch with the recent changes I
> made on the repository, I'd like to sum up some things:

Also if you notice big changes or other issues you like to have in the
release notes of an eventual first release, please let me refer again to
the draft release notes on:

http://trac.shr-project.org/trac/wiki/Draft%3AMS1-relnotes

They are on a wiki for a reason.

spaetz

_______________________________________________
Shr-devel mailing list
[hidden email]
http://lists.projects.openmoko.org/mailman/listinfo/shr-devel
Reply | Threaded
Open this post in threaded view
|

Re: Summary of the changes on the repo

spaetz
In reply to this post by Nicola Mfb
Nicola Mfb wrote:

> Great! thanks for your effort.
> So we'll have the first release of SHR without opimd support?
> Was this decided only to beat OM in releasing the first stable FSO
> based distro? :)))

I really don't get why people ask about opimd integration all the time.

I'm not saying that it won't be useful, but in its current state, I
think there much more low-hanging fruit to focus on.  For all that I
know it is basically still vaporware, moreover, opimd development has
come basically to a halt with FSO not being funded to work on it.

spaetz

_______________________________________________
Shr-devel mailing list
[hidden email]
http://lists.projects.openmoko.org/mailman/listinfo/shr-devel
Reply | Threaded
Open this post in threaded view
|

Re: Summary of the changes on the repo

Nicola Mfb
2009/4/17 Sebastian Spaeth <[hidden email]>:
> Nicola Mfb wrote:
>
>> Great! thanks for your effort.
>> So we'll have the first release of SHR without opimd support?
>> Was this decided only to beat OM in releasing the first stable FSO
>> based distro? :)))
>
> I really don't get why people ask about opimd integration all the time.

I do not know why other peoples asks for it, but according to me, and
I suppose to every developer, we need a dbus standard infrastructure
to store/retrieve contacts.
This is to save time and avoid duplicate work.
Suppose for example that in the next months will come up a voip app
and a bt app that retrieve/store/send/receive contact/vcard from
opimd. Suppose that om2009 will have a opimd compliant paroli, how
many weeks will survive shr-stable-1.0?
This may be real, I'm personally working on Asterisk GUI fso based and
a full bluetooth manager, screenshots at http://noko.sourceforge.net
:)
According to me opimd is so important that shr stable may be delayed a
bit more as happened in the past, to wait for opimd and finally for
the stable 2.6.29 kernel!
That's the reason of my not serious answer, joking on the fact that it
seems that shr wants to beat an "imaginary" war with OM :)
Of course you may decide to adopt opimd based contacts/dialer and so
on, later on shr 1.0 with opkg upgrade, but this is not a good thing
on a "stable" labeled distro.

About SHR 1.0, we really need it, a lot of people prefers using om
2008.12 only to be sure that things are stable and there are around
well working opkg version of external packages.

I want SHR 1.0 not only for this, I need it desperately to have an
updated stable development target, as I'm not able to release my tools
becouse having few time to code is incompatible with a so fast
changing os, and I have to flash/reflash/patch/repatch/test slowing
down development (you may see on the list for example my answer about
bluez 3/4 entering and outing from shr-unstable).

But Mickey confirmed that the main opimd developer left, so all my
thoughts are unuseful :(, I'll try if possible to use the opimd api to
familiarize with it hoping developing will be resumed soon!
I'm sorry I cannot partecipate in FSOSHRUDCON, we could just speak
about all this with some beers :)

Regards and thanks for all your effort in SHR, let's wait for the
first stable release :)

    Nicola

_______________________________________________
Shr-devel mailing list
[hidden email]
http://lists.projects.openmoko.org/mailman/listinfo/shr-devel
Reply | Threaded
Open this post in threaded view
|

Re: Summary of the changes on the repo

spaetz
Nicola Mfb wrote:
>> I really don't get why people ask about opimd integration all the time.
>
> I do not know why other peoples asks for it, but according to me, and
> I suppose to every developer, we need a dbus standard infrastructure
> to store/retrieve contacts.

Ohh, I fully understand why opimd is important, no disagreement there. I
am just wondering - given the fact, that opimd is basically vaporware
and unmaintained by FSO (understandably due to non-funding) -- I don't
understand what improvements people expect from using it NOW.

> According to me opimd is so important that shr stable may be delayed a
> bit more as happened in the past, to wait for opimd and finally for
> the stable 2.6.29 kernel!

That might be a long wait, given that no one develops opimd currently.
Well not true, mrmoku did some work that was committed just now, but if
you want to wait for opimd to be finished before you release, we might
get a nice easter present next year.

Again, I understand and agree that it's an important piece if
infrastructure. It's just that people have unrealistic expectations of
what it will be able to do - if integrated now - and misunderestimate
the manpower that goes into its development. Just my personal opinion.

spaetz

_______________________________________________
Shr-devel mailing list
[hidden email]
http://lists.projects.openmoko.org/mailman/listinfo/shr-devel