Database Info

[Q] Honeycomb question - don't shoot me

This isn't a request about getting the Honeycomb on the G-Tab, so lighten up, Francis.
My question is more about the source code for Android 3.0 and how Google goes about releasing that to the public. I don't really understand their processes in developing a new OS and releasing it for the world to use.
Do they typically only provide it to hardware developers like Motorola, then after a period of time give it to anyone else that wants it?

When they post it, it will be available to anyone to download...
http://source.android.com/index.html

Sooo, my question was more about the processes they go through to get to that point. I know it'll be on the source code page "when it's ready"...but I'm looking for maybe an overview of what it is that they're doing from a business perspective to get it to the masses.

anyone call me francis, and I'll kill ya...

gingerberry said:
anyone call me francis, and I'll kill ya...
Click to expand...
Click to collapse
LOL. Any of you guys touch my stuff...and I'll kill ya.

gingerberry said:
anyone call me francis, and I'll kill ya...
Click to expand...
Click to collapse
How about Ginger?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I just want you guys to know, when Honeycomb development starts, I'll be right behind you every step of the way.
On a more serious note, here's their explanation of their release process:
"What is involved in releasing the source code for a new Android version?
Releasing the source code for a new version of the Android platform is a significant process. First, the software gets built into a system image for a device, and put through various forms of certification, including government regulatory certification for the regions the phones will be deployed. It also goes through operator testing. This is an important phase of the process, since it helps shake out a lot of software bugs.
Once the release is approved by the regulators and operators, the manufacturer begins mass producing devices, and we turn to releasing the source code.
Simultaneous to mass production the Google team kicks off several efforts to prepare the open source release. These efforts include final API changes and documentation (to reflect any changes that were made during qualification testing, for example), preparing an SDK for the new version, and launching the platform compatibility information.
Also included is a final legal sign-off to release the code into open source. Just as open source contributors are required to sign a Contributors License Agreement attesting to their IP ownership of their contribution, Google too must verify that it is clear to make contributions.
Starting at the time mass production begins, the software release process usually takes around a month, which often roughly places source code releases around the same time that the devices reach users."
http://source.android.com/faqs.html
So it sounds like they go through the regulatory and operator process, then release it to the manufacturers while at the same time going through their own preparations. But it's a different process, which is why manufacturers can end up releasing their products before the source code is made available to the public.

Too Funny!
[email protected] pic of "Francis Sawyer" aka Phsyco!
Too Funny!!

Closing thread to avoid inevitable flaming war due to post being about Honeycomb. Good overall question though.

[Mandatory] XDA- Developers and the GPL

XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Tizen operating system are licensed. The majority of Tizen is licensed under the Apache license, but the Linux Kernel (which is present in every running Tizen ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Tizen exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL complaint is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL complaint under XDA rules.
1. If you are using a stock kernel you MUST have a link leading to where the manufacture has uploaded their source.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL complaint.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Mandatory] XDA- Developers and the GPL

XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Tizen operating system are licensed. The majority of Tizen is licensed under the Apache license, but the Linux Kernel (which is present in every running Tizen ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Tizen exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL complaint is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL complaint under XDA rules.
1. If you are using a stock kernel you MUST have a link leading to where the manufacture has uploaded their source.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL complaint.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Mandatory] XDA-Developers and the GPL

XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Android exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under XDA rules.
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacture has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Mandatory] XDA-Developers and the GPL

XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Android exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL compliant is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL compliant under XDA rules.
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacture has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}