Hi Chris & Dick,
Thank you very much to solve the issue quickly.
I do see the reasons to scan projects hosted
in google code to ensure it only serves
open source projects. :)
However, the way should be more modest and polite.
For example, notify the project admin what rules are
violated and give them a chance to explain and fix
before just ban it.
So far we didn't receive any notification from Google.
We only got many complaints from our users that
they cannot download the files.
Android-x86 does NOT use Google code to release
our source code. We use our own git server
http://git.android-x86.org because of historical reasons.
When we began the project three years ago,
Google code didn't offer git repo yet.
So we have to set up our own server to
release the source code.
I know Google code offers git repo now.
If release code via Google code is a must,
I'll try it in the near future.
> From: rbg.h...@comcast.net > Sent: Tuesday, January 1, 2013 8:03 PM
> To: Chris Smith
> Subject: Re:
> //groups.google.com/group/android-x86/browse_thread/thread/042d236c9c6b9e0b# >
> ok...thanks for the heads up Chris...will pass the info on up to the powers
> that be...
> thanks again
> From: Chris Smith
> Sent: Tuesday, January 1, 2013 6:13 PM
> To: dick gordon
> Subject: Re:
> http://groups.google.com/group/android-x86/browse_thread/thread/042d236c9c6b9e0b# >
> Hey Dick,
> Sorry for the confusion. I have unbanned your project.
> The underlying issue is that many people abuse our service. (Setting up
> repositories for hosting personal files, malware, etc.) We have automated
> processes which ban projects that host downloads but don't have any source
> code. This is why android-x86 was banned. It doesn't immediately appear to
> be an open-source project since it just hosts downloads and
> http://code.google.com/p/android-x86/source/list is empty.
> Given that this isn't the first legitimate project that has been banned by
> our tool, we might need to improve our heuristics for determining if a
> project is legitimate or not. However, in the mean time I would suggest you
> check something into the android-x86 repository so you don't get tripped up
> by this again.
> On Tue, Jan 1, 2013 at 11:38 AM, dick gordon <rbg.hp...@gmail.com> wrote:
>> Hi Chris...
>> could you offer any insight to this issue???