Gerrit server migration

Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]

All,

The Gerrit server is now ready for use.  All of the repositories except
for the ones listed below are migrated to it.  We therefore no longer
accept pull requests on Github, but instead need commits to go through
Gerrit.

For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
and documentation can be found in this outstanding pull request
https://github.com/openbmc/docs/pull/30 .

The Gerrit server automatically replicates all merged commits back to
Github, so Github is still considered the canonical location for our source.

Not [yet] migrated repositories:
    * Waiting on a few pull requests to be closed.
        * openbmc / openbmc
        * openbmc / skeleton
        * openbmc / phosphor-host-ipmid
        * openbmc / ipmi-fru-parser
        * openbmc / openpower-host-ipmi-oem
        * openbmc / phosphor-rest-server
        * openbmc / openbmc-test-automation
    * To be migrated later this week.
        * openbmc / docs
        * openbmc / openbmc-build-scripts
    * Never to be migrated (use mailing list for commits).
        * openbmc / linux
        * openbmc / ipmitool
        * openbmc / u-boot
        * openbmc / qemu
--
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Gerrit server migration

[Joel Stanley]

Hi Patrick,

A few questions on how we should use gerrit.

On Tue, Jun 28, 2016 at 7:45 AM, Patrick Williams <patrick@stwcx.xyz> wrote:
> All,
>
> The Gerrit server is now ready for use.  All of the repositories except
> for the ones listed below are migrated to it.  We therefore no longer
> accept pull requests on Github, but instead need commits to go through
> Gerrit.

How do we get notifications when a patch is proposed for review?

Do we have owners of each component that must review before a patch
can be merged?

Cheers,

Joel

>
> For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
> and documentation can be found in this outstanding pull request
> https://github.com/openbmc/docs/pull/30 .
>
> The Gerrit server automatically replicates all merged commits back to
> Github, so Github is still considered the canonical location for our source.
>
> Not [yet] migrated repositories:
>     * Waiting on a few pull requests to be closed.
>         * openbmc / openbmc
>         * openbmc / skeleton
>         * openbmc / phosphor-host-ipmid
>         * openbmc / ipmi-fru-parser
>         * openbmc / openpower-host-ipmi-oem
>         * openbmc / phosphor-rest-server
>         * openbmc / openbmc-test-automation
>     * To be migrated later this week.
>         * openbmc / docs
>         * openbmc / openbmc-build-scripts
>     * Never to be migrated (use mailing list for commits).
>         * openbmc / linux
>         * openbmc / ipmitool
>         * openbmc / u-boot
>         * openbmc / qemu
> --
> Patrick Williams
>
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
>

Re: Gerrit server migration

[Vishwanatha Subbanna]

[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

I would vote for maintainer of the repository to give a +1 before the code
gets merged.

"openbmc" <openbmc-bounces+vishwanath=in.ibm.com@lists.ozlabs.org> wrote on
06/28/2016 09:22:57 AM:

> From: Joel Stanley <joel@jms.id.au>
> To: Patrick Williams <patrick@stwcx.xyz>
> Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> Date: 06/28/2016 09:23 AM
> Subject: Re: Gerrit server migration
> Sent by: "openbmc" <openbmc-bounces
+vishwanath=in.ibm.com@lists.ozlabs.org>
>
> Hi Patrick,
>
> A few questions on how we should use gerrit.
>
> On Tue, Jun 28, 2016 at 7:45 AM, Patrick Williams <patrick@stwcx.xyz>
wrote:
> > All,
> >
> > The Gerrit server is now ready for use.  All of the repositories except
> > for the ones listed below are migrated to it.  We therefore no longer
> > accept pull requests on Github, but instead need commits to go through
> > Gerrit.
>
> How do we get notifications when a patch is proposed for review?
>
> Do we have owners of each component that must review before a patch
> can be merged?
>
> Cheers,
>
> Joel
>
> >
> > For a reminder, the Gerrit server is at
https://gerrit.openbmc-project.xyz
> > and documentation can be found in this outstanding pull request
> > https://github.com/openbmc/docs/pull/30 .
> >
> > The Gerrit server automatically replicates all merged commits back to
> > Github, so Github is still considered the canonical location for our
source.
> >
> > Not [yet] migrated repositories:
> >     * Waiting on a few pull requests to be closed.
> >         * openbmc / openbmc
> >         * openbmc / skeleton
> >         * openbmc / phosphor-host-ipmid
> >         * openbmc / ipmi-fru-parser
> >         * openbmc / openpower-host-ipmi-oem
> >         * openbmc / phosphor-rest-server
> >         * openbmc / openbmc-test-automation
> >     * To be migrated later this week.
> >         * openbmc / docs
> >         * openbmc / openbmc-build-scripts
> >     * Never to be migrated (use mailing list for commits).
> >         * openbmc / linux
> >         * openbmc / ipmitool
> >         * openbmc / u-boot
> >         * openbmc / qemu
> > --
> > Patrick Williams
> >
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
> >
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc

[-- Attachment #2: Type: text/html, Size: 3618 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 2971 bytes --]

Joel,

Both of these questions make me realize we should add the "answers" to
the documentation.  I'll get it added after Adriana's initial Gerrit
documentation is in.

On Tue, Jun 28, 2016 at 01:22:57PM +0930, Joel Stanley wrote:
> How do we get notifications when a patch is proposed for review?

The overall documentation for it can be found here:
    https://gerrit-review.googlesource.com/Documentation/user-notify.html#user

Also, you can view the documentation directly on our Gerrit server:
    https://gerrit.openbmc-project.xyz/Documentation/user-notify.html#user

The net is that you probably want to go to "Settings > Watched Projects"
and add All-Projects to your subscription.  You can otherwise subscribe
to individual repositories.

Direct link:
    https://gerrit.openbmc-project.xyz/#/settings/projects

> Do we have owners of each component that must review before a patch
> can be merged?

Yes.  We should document the code-review process now that we can have
one.

Here are the current settings and what has worked well for us in the
past with Gerrit.  Open to suggestions.

    1. All users are able to +1 / -1 code.
    2. A set of "maintainers" are able to +2 / -2 and submit code.
    3. All commits should have (at least) two +1 reviews.
        3a. Ideally the maintainer is not one of the +1.
    4. Commits should not be merged with a -1 (or -2) unless there has
       been a discussion by the maintainer to justify the merge.
    5. The maintainer should ensure that all past -1 review comments
       have been addressed in a follow-up patch set.  This is usually
       handled by having the original -1 reviewer now give a +1.

What I did initially was divide the repositories up based on their
primary language and assign a maintainer group in Github.  Maybe I
should make these groups public?

    a. Bitbake recipes.
        * Brad Bishop, Patrick Williams
    b. Python repositories.
        * Brad Bishop, Patrick Williams
    c. C repositories.
        * Joel Stanley, Jeremy Kerr
    d. C++ repositories.
        * Patrick Williams

Over time I expect the repositories to be grouped more along functional
lines and subsystem-style maintainers to come about based on their
contributions.  (I know next to nothing about Python, so I'd be
especially willing to add someone else in my place there to work with
Brad.)

You can see the current "maintainer group" assigned to a repository by
going to "Projects > List > (select repo) > Access" and seeing the
"Rights Inherit From" line.  By direct link, you can see 'obmc-console'
is maintained by the 'openbmc-c-repos' group:
https://gerrit.openbmc-project.xyz/#/admin/projects/openbmc/obmc-console,access

That 'openbmc-c-repos' group corresponds to the 'openbmc/c-maintainers' group
on Github as evidenced by this:
https://gerrit.openbmc-project.xyz/#/admin/projects/openbmc-c-repos,access

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Gerrit server migration

[Rick Altherr]

[-- Attachment #1: Type: text/plain, Size: 3393 bytes --]

I'm willing to help with reviews in any of those groups.  I've had a career
that's plunged me into all of those languages quite deeply.

On Tue, Jun 28, 2016 at 9:39 AM, Patrick Williams <patrick@stwcx.xyz> wrote:

> Joel,
>
> Both of these questions make me realize we should add the "answers" to
> the documentation.  I'll get it added after Adriana's initial Gerrit
> documentation is in.
>
> On Tue, Jun 28, 2016 at 01:22:57PM +0930, Joel Stanley wrote:
> > How do we get notifications when a patch is proposed for review?
>
> The overall documentation for it can be found here:
>
> https://gerrit-review.googlesource.com/Documentation/user-notify.html#user
>
> Also, you can view the documentation directly on our Gerrit server:
>     https://gerrit.openbmc-project.xyz/Documentation/user-notify.html#user
>
> The net is that you probably want to go to "Settings > Watched Projects"
> and add All-Projects to your subscription.  You can otherwise subscribe
> to individual repositories.
>
> Direct link:
>     https://gerrit.openbmc-project.xyz/#/settings/projects
>
> > Do we have owners of each component that must review before a patch
> > can be merged?
>
> Yes.  We should document the code-review process now that we can have
> one.
>
> Here are the current settings and what has worked well for us in the
> past with Gerrit.  Open to suggestions.
>
>     1. All users are able to +1 / -1 code.
>     2. A set of "maintainers" are able to +2 / -2 and submit code.
>     3. All commits should have (at least) two +1 reviews.
>         3a. Ideally the maintainer is not one of the +1.
>     4. Commits should not be merged with a -1 (or -2) unless there has
>        been a discussion by the maintainer to justify the merge.
>     5. The maintainer should ensure that all past -1 review comments
>        have been addressed in a follow-up patch set.  This is usually
>        handled by having the original -1 reviewer now give a +1.
>
> What I did initially was divide the repositories up based on their
> primary language and assign a maintainer group in Github.  Maybe I
> should make these groups public?
>
>     a. Bitbake recipes.
>         * Brad Bishop, Patrick Williams
>     b. Python repositories.
>         * Brad Bishop, Patrick Williams
>     c. C repositories.
>         * Joel Stanley, Jeremy Kerr
>     d. C++ repositories.
>         * Patrick Williams
>
> Over time I expect the repositories to be grouped more along functional
> lines and subsystem-style maintainers to come about based on their
> contributions.  (I know next to nothing about Python, so I'd be
> especially willing to add someone else in my place there to work with
> Brad.)
>
> You can see the current "maintainer group" assigned to a repository by
> going to "Projects > List > (select repo) > Access" and seeing the
> "Rights Inherit From" line.  By direct link, you can see 'obmc-console'
> is maintained by the 'openbmc-c-repos' group:
>
> https://gerrit.openbmc-project.xyz/#/admin/projects/openbmc/obmc-console,access
>
> That 'openbmc-c-repos' group corresponds to the 'openbmc/c-maintainers'
> group
> on Github as evidenced by this:
> https://gerrit.openbmc-project.xyz/#/admin/projects/openbmc-c-repos,access
>
> --
> Patrick Williams
>
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
>
>

[-- Attachment #2: Type: text/html, Size: 4958 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]

These repos are now also migrated:
         * openbmc / phosphor-rest-server
         * openbmc / openbmc-test-automation

On Mon, Jun 27, 2016 at 05:15:01PM -0500, Patrick Williams wrote:
> All,
> 
> The Gerrit server is now ready for use.  All of the repositories except
> for the ones listed below are migrated to it.  We therefore no longer
> accept pull requests on Github, but instead need commits to go through
> Gerrit.
> 
> For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
> and documentation can be found in this outstanding pull request
> https://github.com/openbmc/docs/pull/30 .
> 
> The Gerrit server automatically replicates all merged commits back to
> Github, so Github is still considered the canonical location for our source.
> 
> Not [yet] migrated repositories:
>     * Waiting on a few pull requests to be closed.
>         * openbmc / openbmc
>         * openbmc / skeleton
>         * openbmc / phosphor-host-ipmid
>         * openbmc / ipmi-fru-parser
>         * openbmc / openpower-host-ipmi-oem
>     * To be migrated later this week.
>         * openbmc / docs
>         * openbmc / openbmc-build-scripts
>     * Never to be migrated (use mailing list for commits).
>         * openbmc / linux
>         * openbmc / ipmitool
>         * openbmc / u-boot
>         * openbmc / qemu
> --
> Patrick Williams



> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc


-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

On Tue, Jun 28, 2016 at 10:09:58AM -0700, Rick Altherr wrote:
> I'm willing to help with reviews in any of those groups.  I've had a career
> that's plunged me into all of those languages quite deeply.

Rick,

Please feel free for you and your team to subscribe to any of the
repositories in Gerrit that you find interesting and provide review
feedback.  We would certainly rather have more eyes on the commits than
less.

I don't want to see too much emphasis on the 'maintainer' position.
Ideally the only purpose of this role is an extra gate to ensure the
rest of the processes have been followed.

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Gerrit server migration

[Yi TZ Li]

[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]

Hi,

I have a patch to fix issue: https://github.com/openbmc/skeleton/issues/64
This patch will change skeleton (in github), and openbmc/pyphosphor (in
gerrit).

So I think I should wait for skeleton being migrated to Gerrit to submit
the patch. Do we have an expected time
when all the migration be finished?

Thanks,
-Yi

"openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org> wrote on
06/30/2016 02:21:50 AM:

> From: Patrick Williams <patrick@stwcx.xyz>
> To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> Date: 06/30/2016 02:22 AM
> Subject: Re: Gerrit server migration
> Sent by: "openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org>
>
> These repos are now also migrated:
>          * openbmc / phosphor-rest-server
>          * openbmc / openbmc-test-automation
>
> On Mon, Jun 27, 2016 at 05:15:01PM -0500, Patrick Williams wrote:
> > All,
> >
> > The Gerrit server is now ready for use.  All of the repositories except
> > for the ones listed below are migrated to it.  We therefore no longer
> > accept pull requests on Github, but instead need commits to go through
> > Gerrit.
> >
> > For a reminder, the Gerrit server is at
https://gerrit.openbmc-project.xyz
> > and documentation can be found in this outstanding pull request
> > https://github.com/openbmc/docs/pull/30 .
> >
> > The Gerrit server automatically replicates all merged commits back to
> > Github, so Github is still considered the canonical location for our
source.
> >
> > Not [yet] migrated repositories:
> >     * Waiting on a few pull requests to be closed.
> >         * openbmc / openbmc
> >         * openbmc / skeleton
> >         * openbmc / phosphor-host-ipmid
> >         * openbmc / ipmi-fru-parser
> >         * openbmc / openpower-host-ipmi-oem
> >     * To be migrated later this week.
> >         * openbmc / docs
> >         * openbmc / openbmc-build-scripts
> >     * Never to be migrated (use mailing list for commits).
> >         * openbmc / linux
> >         * openbmc / ipmitool
> >         * openbmc / u-boot
> >         * openbmc / qemu
> > --
> > Patrick Williams
>
>
>
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
>
>
> --
> Patrick Williams
> [attachment "signature.asc" deleted by Yi TZ Li/China/IBM]
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc

[-- Attachment #2: Type: text/html, Size: 3713 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 3176 bytes --]

You can submit the one in Gerrit and the other in Github. 

Skeleton will be moved later this week or early next week. There are a few major pieces of work going through that repository for the next 1.0.x tag. 

Patrick
Sent from my iPhone

> On Jun 30, 2016, at 2:30 AM, Yi TZ Li <shliyi@cn.ibm.com> wrote:
> 
> Hi,
> 
> I have a patch to fix issue: https://github.com/openbmc/skeleton/issues/64
> This patch will change skeleton (in github), and openbmc/pyphosphor (in gerrit).
> 
> So I think I should wait for skeleton being migrated to Gerrit to submit the patch. Do we have an expected time
> when all the migration be finished?
> 
> Thanks,
> -Yi
> 
> "openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org> wrote on 06/30/2016 02:21:50 AM:
> 
> > From: Patrick Williams <patrick@stwcx.xyz>
> > To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> > Date: 06/30/2016 02:22 AM
> > Subject: Re: Gerrit server migration
> > Sent by: "openbmc" <openbmc-bounces+shliyi=cn.ibm.com@lists.ozlabs.org>
> > 
> > These repos are now also migrated:
> >          * openbmc / phosphor-rest-server
> >          * openbmc / openbmc-test-automation
> > 
> > On Mon, Jun 27, 2016 at 05:15:01PM -0500, Patrick Williams wrote:
> > > All,
> > > 
> > > The Gerrit server is now ready for use.  All of the repositories except
> > > for the ones listed below are migrated to it.  We therefore no longer
> > > accept pull requests on Github, but instead need commits to go through
> > > Gerrit.
> > > 
> > > For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
> > > and documentation can be found in this outstanding pull request
> > > https://github.com/openbmc/docs/pull/30 .
> > > 
> > > The Gerrit server automatically replicates all merged commits back to
> > > Github, so Github is still considered the canonical location for our source.
> > > 
> > > Not [yet] migrated repositories:
> > >     * Waiting on a few pull requests to be closed.
> > >         * openbmc / openbmc
> > >         * openbmc / skeleton
> > >         * openbmc / phosphor-host-ipmid
> > >         * openbmc / ipmi-fru-parser
> > >         * openbmc / openpower-host-ipmi-oem
> > >     * To be migrated later this week.
> > >         * openbmc / docs
> > >         * openbmc / openbmc-build-scripts
> > >     * Never to be migrated (use mailing list for commits).
> > >         * openbmc / linux
> > >         * openbmc / ipmitool
> > >         * openbmc / u-boot
> > >         * openbmc / qemu
> > > --
> > > Patrick Williams
> > 
> > 
> > 
> > > _______________________________________________
> > > openbmc mailing list
> > > openbmc@lists.ozlabs.org
> > > https://lists.ozlabs.org/listinfo/openbmc
> > 
> > 
> > -- 
> > Patrick Williams
> > [attachment "signature.asc" deleted by Yi TZ Li/China/IBM] 
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
> 
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc

[-- Attachment #2: Type: text/html, Size: 4977 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 2241 bytes --]

These repos are now also migrated:
          * openbmc / skeleton
          * openbmc / phosphor-host-ipmid
          * openbmc / ipmi-fru-parser
          * openbmc / openpower-host-ipmi-oem
          * openbmc / openbmc-build-scripts

openbmc/openbmc - We are waiting for a Jenkins connection to be made to
the Gerrit server before we migrate this one, since it is doing our CI
testing.

openbmc/docs - I have a few changes I want done in Github so that they
get broadcast on the mailing list.  Moving out to next week.

On Wed, Jun 29, 2016 at 01:21:50PM -0500, Patrick Williams wrote:
> These repos are now also migrated:
>          * openbmc / phosphor-rest-server
>          * openbmc / openbmc-test-automation
> 
> On Mon, Jun 27, 2016 at 05:15:01PM -0500, Patrick Williams wrote:
> > All,
> > 
> > The Gerrit server is now ready for use.  All of the repositories except
> > for the ones listed below are migrated to it.  We therefore no longer
> > accept pull requests on Github, but instead need commits to go through
> > Gerrit.
> > 
> > For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
> > and documentation can be found in this outstanding pull request
> > https://github.com/openbmc/docs/pull/30 .
> > 
> > The Gerrit server automatically replicates all merged commits back to
> > Github, so Github is still considered the canonical location for our source.
> > 
> > Not [yet] migrated repositories:
> >     * Waiting on a few pull requests to be closed.
> >         * openbmc / openbmc
> >     * To be migrated later this week.
> >         * openbmc / docs
> >     * Never to be migrated (use mailing list for commits).
> >         * openbmc / linux
> >         * openbmc / ipmitool
> >         * openbmc / u-boot
> >         * openbmc / qemu
> > --
> > Patrick Williams
> 
> 
> 
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
> 
> 
> -- 
> Patrick Williams



> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc


-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]

openbmc/openbmc is now migrated and ready for use on the Gerrit server.

On Fri, Jul 01, 2016 at 02:05:46PM -0500, Patrick Williams wrote:
> These repos are now also migrated:
>           * openbmc / skeleton
>           * openbmc / phosphor-host-ipmid
>           * openbmc / ipmi-fru-parser
>           * openbmc / openpower-host-ipmi-oem
>           * openbmc / openbmc-build-scripts
> 
> openbmc/openbmc - We are waiting for a Jenkins connection to be made to
> the Gerrit server before we migrate this one, since it is doing our CI
> testing.
> 
> openbmc/docs - I have a few changes I want done in Github so that they
> get broadcast on the mailing list.  Moving out to next week.
> 
> On Wed, Jun 29, 2016 at 01:21:50PM -0500, Patrick Williams wrote:
> > These repos are now also migrated:
> >          * openbmc / phosphor-rest-server
> >          * openbmc / openbmc-test-automation
> > 
> > On Mon, Jun 27, 2016 at 05:15:01PM -0500, Patrick Williams wrote:
> > > All,
> > > 
> > > The Gerrit server is now ready for use.  All of the repositories except
> > > for the ones listed below are migrated to it.  We therefore no longer
> > > accept pull requests on Github, but instead need commits to go through
> > > Gerrit.
> > > 
> > > For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
> > > and documentation can be found in this outstanding pull request
> > > https://github.com/openbmc/docs/pull/30 .
> > > 
> > > The Gerrit server automatically replicates all merged commits back to
> > > Github, so Github is still considered the canonical location for our source.
> > > 
> > > Not [yet] migrated repositories:
> > >     * To be migrated later this week.
> > >         * openbmc / docs
> > >     * Never to be migrated (use mailing list for commits).
> > >         * openbmc / linux
> > >         * openbmc / ipmitool
> > >         * openbmc / u-boot
> > >         * openbmc / qemu
> > > --
> > > Patrick Williams
> > 
> > 
> > 
> > > _______________________________________________
> > > openbmc mailing list
> > > openbmc@lists.ozlabs.org
> > > https://lists.ozlabs.org/listinfo/openbmc
> > 
> > 
> > -- 
> > Patrick Williams
> 
> 
> 
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
> 
> 
> -- 
> Patrick Williams



> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc


-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Gerrit server migration

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 3144 bytes --]

openbmc/docs is now migrated.  All repositories that are suppose to be
migrated should be migrated to the Gerrit server now.

On Sun, Jul 17, 2016 at 06:07:17AM -0500, Patrick Williams wrote:
> openbmc/openbmc is now migrated and ready for use on the Gerrit server.
> 
> On Fri, Jul 01, 2016 at 02:05:46PM -0500, Patrick Williams wrote:
> > These repos are now also migrated:
> >           * openbmc / skeleton
> >           * openbmc / phosphor-host-ipmid
> >           * openbmc / ipmi-fru-parser
> >           * openbmc / openpower-host-ipmi-oem
> >           * openbmc / openbmc-build-scripts
> > 
> > openbmc/openbmc - We are waiting for a Jenkins connection to be made to
> > the Gerrit server before we migrate this one, since it is doing our CI
> > testing.
> > 
> > openbmc/docs - I have a few changes I want done in Github so that they
> > get broadcast on the mailing list.  Moving out to next week.
> > 
> > On Wed, Jun 29, 2016 at 01:21:50PM -0500, Patrick Williams wrote:
> > > These repos are now also migrated:
> > >          * openbmc / phosphor-rest-server
> > >          * openbmc / openbmc-test-automation
> > > 
> > > On Mon, Jun 27, 2016 at 05:15:01PM -0500, Patrick Williams wrote:
> > > > All,
> > > > 
> > > > The Gerrit server is now ready for use.  All of the repositories except
> > > > for the ones listed below are migrated to it.  We therefore no longer
> > > > accept pull requests on Github, but instead need commits to go through
> > > > Gerrit.
> > > > 
> > > > For a reminder, the Gerrit server is at https://gerrit.openbmc-project.xyz
> > > > and documentation can be found in this outstanding pull request
> > > > https://github.com/openbmc/docs/pull/30 .
> > > > 
> > > > The Gerrit server automatically replicates all merged commits back to
> > > > Github, so Github is still considered the canonical location for our source.
> > > > 
> > > > Not [yet] migrated repositories:
> > > >     * To be migrated later this week.
> > > >         * openbmc / docs
> > > >     * Never to be migrated (use mailing list for commits).
> > > >         * openbmc / linux
> > > >         * openbmc / ipmitool
> > > >         * openbmc / u-boot
> > > >         * openbmc / qemu
> > > > --
> > > > Patrick Williams
> > > 
> > > 
> > > 
> > > > _______________________________________________
> > > > openbmc mailing list
> > > > openbmc@lists.ozlabs.org
> > > > https://lists.ozlabs.org/listinfo/openbmc
> > > 
> > > 
> > > -- 
> > > Patrick Williams
> > 
> > 
> > 
> > > _______________________________________________
> > > openbmc mailing list
> > > openbmc@lists.ozlabs.org
> > > https://lists.ozlabs.org/listinfo/openbmc
> > 
> > 
> > -- 
> > Patrick Williams
> 
> 
> 
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
> 
> 
> -- 
> Patrick Williams



> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc


-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]