Gerrit Site Down?
mhorn
https://review.source.android.com/
Is there some known issue?
Dan Morrill
eren
Is there a mirror that we can use to do repo init and repo sync while the servers are offline? (Github uses a different path configuration for the repositories, so it would require quite a manual work to update the manifest file, if all the repositories used by android are mirrored at github, that is.)
BR,
Eren
Michael Zoech
Any news to when gerrit/git will be up again?
thanks,
Michael
naresh tanniru
Jean-Baptiste Queru
there are no official mirrors anywhere.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Jean-Baptiste Queru
József Király
Jean-Baptiste Queru
http://groups.google.com/group/repo-discuss/msg/06ce4bb4b70b5b52
Thanks,
JBQ
2011/9/8 József Király <foni...@gmail.com>:
Adam
online at another location, ie an official github mirror, surely you
have copies of the repositories that was stored at kernel.org that
would not have been compromised.
Android 2.3.6 has been released and we can not even browse GPL based
material ie up to date kernel sources, this is obviously a concern to
myself and many others in the community.
I sincerely hope that something can be done in a timely fashion as
this is a huge loss to the open-source community that is working on
Android.
Myself and I'm sure others would appreciate a more in-depth update on
the situation rather than the one line sentence quoted in the post JBQ
referred to.
Jean-Baptiste Queru
complex enough that there's nothing new to announce at this point.
We have plans to make sure that the GPL source files for Gingerbread
and Honeycomb can be distributed independently, in case we decide to
make releases beyond 2.3.5 and 3.2.
JBQ
--
Matt Oakes
Jean-Baptiste Queru
JBQ
--
Mark Murphy
> That is correct.
Does that mean that https://github.com/android is not an official mirror?
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_The Busy Coder's Guide to Android Development_ Version 3.6 Available!
Jean-Baptiste Queru
JBQ
--
Matt Oakes
Adam
You have already made a release beyond 2.3.5, it seems my whole question has been avoided.
Jean-Baptiste Queru
distributed to a handful of users. I'm on it. Sorry for the delay.
JBQ
Dan Morrill
József Király
Jean-Baptiste Queru
which being the lack of Gerrit code reviews, which I'm sure is quite
relevant to this specific group.
JBQ
2011/9/12 József Király <foni...@gmail.com>:
József Király
Adam
cyanogenmod repositories to know that,
regards
On Sep 12, 8:32 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Actually that would cause some significant difficulties, the first of
> which being the lack of Gerrit code reviews, which I'm sure is quite
> relevant to this specific group.
>
> JBQ
>
>
>
>
>
>
>
>
>
> > The best solution would be to make github the main host, and mirror their
> > repos back to kernel.org, gitorious, etc.. This all could be done, and even
> > if one goes down, you got backup servers where you can push changes, and
> > with some help of the site owners, you can make it automatically sync
> > between each host.
>
> >> We're working on getting the copyleft source online. As kernel.org was our
> >> distribution infrastructure for this, we are unfortunately without hosting
> >> entirely at the moment. We still prefer to use git to host source as it's a
> >> friendlier tool, but until we get git infrastructure back up, we are working
> >> on a temporary distribution method.
> >> - Dan
>
>
> >>> You have already made a release beyond 2.3.5, it seems my whole question
> >>> has been avoided.
>
> >>> On Sep 12, 2011 3:40 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
>
> >>> > We are working on restoring git access, but the whole process is
> >>> > complex enough that there's nothing new to announce at this point.
>
> >>> > We have plans to make sure that the GPL source files for Gingerbread
> >>> > and Honeycomb can be distributed independently, in case we decide to
> >>> > make releases beyond 2.3.5 and 3.2.
>
> >>> > JBQ
>
Jean-Baptiste Queru
a separate server, such that GitHub isn't the primary copy.
JBQ
József Király
Github is the primary copy while they run gerrit on their own server.
Jean-Baptiste Queru
AOSP: for AOSP Gerrit is the primary copy and kernel.org is a mirror:
if we were to make a change directly on kernel.org, it would get
overwritten when replicating from Gerrit.
JBQ
2011/9/12 József Király <foni...@gmail.com>:
Al Sutton
hasn't been used as the repository. Seems like a good home to tie it
up with the bug database and now that Google Code handles git
repositories there would seem to be few (if any) obstacles.
Al.
Jean-Baptiste Queru
JBQ
József Király
AFAIK on CM Gerrit is really Just a overview tool, and it manages the Github repos.
Gergely Kis
Just for the record: As far as I know Gerrit requires direct
filesystem access to its primary git repositories containing both the
committed and the proposed changes, so Cyanogen is probably running
Gerrit on its own server like AOSP does / did, and uses github as the
distribution mirror the same way AOSP used kernel.org.
So theoretically it should be possible to migrate to github for the
source mirrors. However, after the kernel.org fiasco, I would totally
understand if Google wanted to keep the whole infrastructure inhouse.
Best Regards,
Gergely
2011/9/12 Jean-Baptiste Queru <j...@android.com>:
--
Kis Gergely
ügyvezető / CEO
MattaKis Consulting
Email: gerge...@mattakis.com
Web: http://www.mattakis.com
Phone: +36 70 408 1723
Fax: +36 27 998 622
--
Kis Gergely
ügyvezető / CEO
MattaKis Consulting
Email: gerge...@mattakis.com
Web: http://www.mattakis.com
Phone: +36 70 408 1723
Fax: +36 27 998 622
Suryandaru Triandana
back online.
On Sep 13, 12:10 am, Dan Morrill <morri...@google.com> wrote:
> We're working on getting the copyleft source online. As kernel.org was our
> distribution infrastructure for this, we are unfortunately without hosting
> entirely at the moment. We still prefer to use git to host source as it's a
> friendlier tool, but until we get git infrastructure back up, we are working
> on a temporary distribution method.
>
> - Dan
>
>
>
>
>
>
>
> On Mon, Sep 12, 2011 at 8:08 AM, Adam <green...@gmail.com> wrote:
> > You have already made a release beyond 2.3.5, it seems my whole question
> > has been avoided.
>
> > On Sep 12, 2011 3:40 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
>
> > > We are working on restoring git access, but the whole process is
> > > complex enough that there's nothing new to announce at this point.
>
> > > We have plans to make sure that the GPL source files for Gingerbread
> > > and Honeycomb can be distributed independently, in case we decide to
> > > make releases beyond 2.3.5 and 3.2.
>
> > > JBQ
>
Jean-Baptiste Queru
at this point there's nothing to announce.
We're working on getting back online, and we'll let everyone know as
soon as we have something that people can use.
JBQ
Adam
few days later, if other sites are able to obtain this code how come
the general public can't?
**We're working on getting back online, and we'll let everyone know
as
soon as we have something that people can use. **
Can you elaborate on this please?
Surely it doesn't take 6+ weeks to setup a git instance so everybody
can browse and clone the code again, this is pretty shocking how long
it has been offline now.
Jean-Baptiste Queru
Joke aside, we're working on it, but I can't provide any additional
details at the moment.
JBQ
József Király
Jean-Baptiste Queru
JBQ
2011/10/7 József Király <foni...@gmail.com>:
Daniel Callaghan
Jean-Baptiste Queru
Mountain View: http://www.google.com/intl/en/jobs/uslocations/mountain-view/swe/index.html
JBQ
Leif Andersen
Thank you.
Jean-Baptiste Queru
this post short.
You're looking for Software Engineering Intern position for Mountain
View (listed under North America). I can't possibly make any promise
that there'd be an internship position open in my team, or that you'd
get it, but if you apply be sure to mention AOSP in whichever part of
the process would be the most appropriate (I don't now what that would
be).
JBQ
Adam
much longer the Android source is going to be unavailable for? days/
weeks/months?
On Oct 7, 7:49 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Sorry everyone, we're getting deeply off-topic, so I'll try to keep
> this post short.
>
> You're looking for Software Engineering Intern position for Mountain
> View (listed under North America). I can't possibly make any promise
> that there'd be an internship position open in my team, or that you'd
> get it, but if you apply be sure to mention AOSP in whichever part of
> the process would be the most appropriate (I don't now what that would
> be).
>
> JBQ
>
>
>
>
>
>
>
>
>
> On Fri, Oct 7, 2011 at 11:16 AM, Leif Andersen <l...@leifandersen.net> wrote:
> > How about Student Intern positions? Would the Software Engineer, Software
> > Developer, or a different position be more appropriate?
> >http://www.google.com/intl/en/jobs/students/us/internships/eng/
>
> > Thank you.
>
> > On Fri, Oct 7, 2011 at 07:31, Jean-Baptiste Queru <j...@android.com> wrote:
>
> >> Mountain View:
> >>http://www.google.com/intl/en/jobs/uslocations/mountain-view/swe/inde...
> >> JBQ
>
> >> On Fri, Oct 7, 2011 at 6:16 AM, Daniel Callaghan
> >> <linuxboxsoluti...@gmail.com> wrote:
> >> > Ha Ha please hire me ild love to work for google :-)
>
> >> >www.LinuxBoxSolution.com
>
> >> > On Oct 7, 2011 8:46 AM, "Jean-Baptiste Queru" <j...@android.com> wrote:
> >> >> I could tell you, but first I'd have to hire you.
>
> >> >> Joke aside, we're working on it, but I can't provide any additional
> >> >> details at the moment.
>
> >> >> JBQ
>
Mark Murphy
> 2 months down now, still looking at the electric sheep, any idea how
> much longer the Android source is going to be unavailable for? days/
> weeks/months?
http://groups.google.com/group/android-building/msg/c73c14f9b0dcd15a
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_Android Programming Tutorials_ Version 4.0 Available!
Jean-Baptiste Queru
question before the re-launch... and you question was stuck in the
moderation queue while we were double-checking that everything was
fine with the servers.
Our next step is now to get Gerrit back online, and there's nothing
specific to announce on that other than "we're working on it".
JBQ
Adam
Leonardo Kim
AOSP is back. (http://groups.google.com/group/android-building/msg/c73c14f9b0dcd15a)
But it would seem Gerrit is not able to use yet. manifest.xml file
doesn't have a proper review uri.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="aosp"
fetch=".." />
<default revision="master"
remote="aosp"
sync-j="4" />
Regards,
Leonardo YongUk KIM
Jean-Baptiste Queru
We focused on restoring first what we thought would be the most
useful.
That being said, all the releases mentioned on
http://source.android.com/source/build-numbers.html are there, along
with the froyo, gingerbread and master branches.
JBQ
Jean-Baptiste Queru
JBQ
--
József Király
Mike Reid
Is there any better time estimate after almost 4 months down ?
I am doubting it will ever come back.
Jean-Baptiste Queru
Gerrit is now self-hosted, and the Gerrit engineers have been using it
as their day-to-day tool. At this point, they're in the process of
hunting the last few bugs, and (like you know) once you're down to a
handful of bugs it's very hard to give any kind of precise estimates.
After we lost all the AOSP servers, the top priority was to get some
git hosting again, to restore the proper files there, and to release
ICS. That took us into mid-November. Since then, the efforts on that
side have been focused on Gerrit, but it's really only been 6 weeks.
AOSP will have a Gerrit server again, hopefully soon, but there's
simply no way to give any kind of reliable estimate at this point.
JBQ
--
Shachar Shemesh
Software doesn't write itself. Worse, it doesn't debug itself. Gerrit is now self-hosted, and the Gerrit engineers have been using it as their day-to-day tool. At this point, they're in the process of hunting the last few bugs, and (like you know) once you're down to a handful of bugs it's very hard to give any kind of precise estimates. After we lost all the AOSP servers, the top priority was to get some git hosting again, to restore the proper files there, and to release ICS. That took us into mid-November. Since then, the efforts on that side have been focused on Gerrit, but it's really only been 6 weeks. AOSP will have a Gerrit server again, hopefully soon, but there's simply no way to give any kind of reliable estimate at this point. JBQ
I understand everything you say, and you are, of course, correct. However, if you look at Android as a community, rather than a Google owned project, it is now close to a year since community participation in AOSP in the form of patch submittal was practically possible. Gingerbread was released Dec 2010, and Honeycomb Feb 2011. By January 2011 submitting patches against AOSP became difficult.
I completely accept the decision not to release Honeycomb. I do not understand it. I think it was a mistake on Google's part, but I accept it. I also realize that the kernel.org hack was an unexpected event, and that you had to work around it, and that repo was of higher priority than gerrit. All I'm asking is for you to understand that people are frustrated, and have every right to be so.
Personally, I'm not even sure I'll resume my Android work once Gerrit is back up. My professional focus shifted elsewhere, and my personal interest is not enough to justify the significant upgrade required for my hardware in order to even get ICS to compile. I like the platform, so I'll do my best, but judging from past FOSS projects I participated in, in all likelihood, you've lost me as a developer.
Shachar
-- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com
Jean-Baptiste Queru
because it's my job, so you can probably imagine how frustrated I am.
2011 has had some highs and lows in AOSP, and the difficulties in
accepting external contributions has been one of the lows.
I am surprised though that the decision to not Open-Source Honeycomb
is still not understood after 10 months. Google has explained it many
times already, it's really simple: Honeycomb wasn't shippable on
phones as-is. The apps had a mix-and-match of the Gingerbread look and
the Honeycomb look, the system UI for phones was missing elements
that'd have been necessary for compatibility (e.g. the action bar). We
release code when it's ready for all OEMs to use and ship, and
Honeycomb never was. That's it. There's no longer explanation, that's
really all there is to it.
I hope we see you contribute again once Gerrit is running again, but I
understand that life flows and will take contributors to other places.
Android and AOSP are still here and they're not going away.
JBQ
--
Mike Reid
There is code I want to access that is not available anywhere else, AFAICT. It's now been unavailable for about 4 months, and the project associated with this code is now going nowhere. That's a HUGE amount of time in the fast paced mobile software development world. And nobody at the 208 billion dollar market cap Google Corp can even post backed up copies of this code somewhere ??
And nobody at Google can even postulate an ETA after 4 months ?
Call me impatient or pushy if you wish, but from a business perspective, I have to assume at this point that Google may never restore Gerrit and that the project I am interested in is effectively dead.
Jean-Baptiste Queru
it'd be vulnerable to the same attacks, which history has just shown
aren't just theoretical.
The whole Android platform code has been available on googlesource.com
since mid-October, and the git downtime was only about 7 weeks (i.e. 4
releases). Please ask on android-platform which exact code you're
looking for and I'll try to help you find it. As far as I know I've
restored everything all the way back to donut.
Would you feel better if I gave you an estimate from /dev/random?
I don't need to tell you that Android isn't dead, you can see it for
yourself. Look at the number of changes from Gingerbread to ICS to get
convinced.
JBQ
--
Mike Reid
I understand that providing reasonably accurate time estimates for software development is real work and can take some time. I've done S/W design and development professionally for over 20 years and have done estimates for just about every one of the 20+ companies I've worked for. Very few companies just say "Start work and let us know when you are done".
If a development project is happening I can't imagine there aren't internal time estimates. I would feel better if somebody at Google could at least give a rough estimate, even if it's "Between 1 and 12 months". Even a commitment to do the research needed for a time estimate would be helpful. As in "We will announce estimated ETAs within 1 month".
As it is now, assuming Google IS planning to bring Gerrit back, and not drop it, the impression conveyed is that Google refuses to share whatever internal time estimates they have. I just can NOT imagine a project is underway and nobody inside Google has any idea of when it might be done.
So I presume all we can do is wait, and hope, and one day it will magically be up again, or it's demise will be announced.
Whatever. Whenever.
Thanks for your replies. Please tell your manager(s) that "the natives are getting restless" for better answers 4 months after a "server outage".
Jean-Baptiste Queru
every now and then for which no fix could be found for amazingly long
periods of time. I could tell my own war stories but that'd be
off-topic here.
We're hitting one such bug on Gerrit. The development phase completed
on schedule a while ago, but there's a very annoying bug that makes
Gerrit impossible to deploy in public at the moment and that we can't
manage to pinpoint. There's simply no way to provide any estimate for
a bugfix for such a bug. No amount of wanting that bug fixed today or
yesterday or 3 months ago will fix that bug.
Google is not trying to hide anything here, we're just as frustrated
with the current situation as everyone else.
JBQ
--
Al Sutton
As for Gerrit; I'd rather see things done right than done to a timetable.
Al.
--
T: @alsutton W: www.funkyandroid.com
The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.
Dan Morrill
I AM the manager. Unfortunately we have no ETA to provide.
It is your prerogative to disbelieve what we (and specifically I and JBQ) have said to date, of course. But we aren't going to give half-baked estimates that would be misleading.
I apologize for the continued downtime of the AOSP gerrit instance. It will be restored as soon as we have it working reasonably bug-free.
- Dan
David Kohen
Considering Gerrit is open source (in the assumption that it is,
still), have you considered releasing the current version and perhaps
one of the contributors could look at the issue you are facing from a
different perspective?
I know the claims that with software "adding people to a late project
only makes it later", but if there are only a few issues and the
purpose is not writing new code, I think it has the potential to save
time rather than wasting it.
These are just my two cents on the matter.
David Kohen
On Jan 3, 6:33 pm, Dan Morrill <morri...@google.com> wrote:
> I AM the manager. Unfortunately we have no ETA to provide.
>
> It is your prerogative to disbelieve what we (and specifically I and JBQ)
> have said to date, of course. But we aren't going to give half-baked
> estimates that would be misleading.
>
> I apologize for the continued downtime of the AOSP gerrit instance. It will
> be restored as soon as we have it working reasonably bug-free.
>
> - Dan
>
>
>
>
>
>
>
> > I'm looking for the "ST-Ericsson originated, proposed Android FM Radio
> > API". This was one of the URLs:
Jean-Baptiste Queru
and Google's internal server infrastructure, so the only people who
can actually look at the issue are Google engineers. We're looking for
such a different perspective internally, from someone familiar with
the part of the code we're having issues with.
JBQ
--