Octavia relies heavily on Taskflow and Futurist as well. Personally I agree
with basically everything Monty said earlier. The problem here really isn't
anything besides relaxing the social review policy, which is as simple as
just deciding it as a team and saying "well, ok then". :)
I also use a
On 10/17/18 5:59 PM, Joshua Harlow wrote:
Dmitry Tantsur wrote:
On 10/10/18 7:41 PM, Greg Hill wrote:
I've been out of the openstack loop for a few years, so I hope this
reaches the right folks.
Josh Harlow (original author of taskflow and related libraries) and I
have been discussing the
Dmitry Tantsur wrote:
On 10/10/18 7:41 PM, Greg Hill wrote:
I've been out of the openstack loop for a few years, so I hope this
reaches the right folks.
Josh Harlow (original author of taskflow and related libraries) and I
have been discussing the option of moving taskflow out of the
openstack
On Mon, Oct 15, 2018 at 04:27:00PM -0500, Monty Taylor wrote:
> On 10/15/2018 05:49 AM, Stephen Finucane wrote:
> > On Wed, 2018-10-10 at 18:51 +, Jeremy Stanley wrote:
> > > On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote:
> > > [...]
> > > > We plan to still have a CI gatekeeper,
On 10/10/2018 03:17 PM, Ben Nemec wrote:
On 10/10/18 1:35 PM, Greg Hill wrote:
I'm not sure how using pull requests instead of Gerrit changesets
would
help "core reviewers being pulled on to other projects"?
The 2 +2 requirement works for larger projects with a lot of
On 10/15/2018 05:49 AM, Stephen Finucane wrote:
On Wed, 2018-10-10 at 18:51 +, Jeremy Stanley wrote:
On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote:
[...]
We plan to still have a CI gatekeeper, probably Travis CI, to make sure PRs
past muster before being merged, so it's not like
I'm ok with trying this move out and seeing how it goes (maybe it will
be for the better, idk).
-Josh
On 10/10/2018 10:41 AM, Greg Hill wrote:
I've been out of the openstack loop for a few years, so I hope this
reaches the right folks.
Josh Harlow (original author of taskflow and related
On 10/10/18 7:41 PM, Greg Hill wrote:
I've been out of the openstack loop for a few years, so I hope this reaches the
right folks.
Josh Harlow (original author of taskflow and related libraries) and I have been
discussing the option of moving taskflow out of the openstack umbrella recently.
On Wed, 10 Oct 2018, Greg Hill wrote:
I guess I'm putting it forward to the larger community. Does anyone have
any objections to us doing this? Are there any non-obvious technicalities
that might make such a transition difficult? Who would need to be made
aware so they could adjust their own
On Wed, 2018-10-10 at 18:51 +, Jeremy Stanley wrote:
> On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote:
> [...]
> > We plan to still have a CI gatekeeper, probably Travis CI, to make sure PRs
> > past muster before being merged, so it's not like we're wanting to
> > circumvent good
On 10/10/18 1:35 PM, Greg Hill wrote:
I'm not sure how using pull requests instead of Gerrit changesets would
help "core reviewers being pulled on to other projects"?
The 2 +2 requirement works for larger projects with a lot of
contributors. When you have only 3 regular
On 10/10/2018 12:41 PM, Greg Hill wrote:
> I've been out of the openstack loop for a few years, so I hope this
> reaches the right folks.
>
> Josh Harlow (original author of taskflow and related libraries) and I
> have been discussing the option of moving taskflow out of the openstack
>
On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote:
[...]
> We plan to still have a CI gatekeeper, probably Travis CI, to make sure PRs
> past muster before being merged, so it's not like we're wanting to
> circumvent good contribution practices by committing whatever to HEAD.
Travis CI has
On Wed, Oct 10, 2018, at 11:35 AM, Greg Hill wrote:
> > I'm not sure how using pull requests instead of Gerrit changesets would
> > help "core reviewers being pulled on to other projects"?
> >
>
> The 2 +2 requirement works for larger projects with a lot of contributors.
> When you have only 3
On Wed, Oct 10, 2018 at 2:35 PM Greg Hill wrote:
>
> I'm not sure how using pull requests instead of Gerrit changesets would
>> help "core reviewers being pulled on to other projects"?
>>
>
> The 2 +2 requirement works for larger projects with a lot of contributors.
> When you have only 3
> I'm not sure how using pull requests instead of Gerrit changesets would
> help "core reviewers being pulled on to other projects"?
>
The 2 +2 requirement works for larger projects with a lot of contributors.
When you have only 3 regular contributors and 1 of them gets pulled on to a
project and
On 10/10/2018 01:41 PM, Greg Hill wrote:
I've been out of the openstack loop for a few years, so I hope this
reaches the right folks.
Josh Harlow (original author of taskflow and related libraries) and I
have been discussing the option of moving taskflow out of the openstack
umbrella
I've been out of the openstack loop for a few years, so I hope this reaches
the right folks.
Josh Harlow (original author of taskflow and related libraries) and I have
been discussing the option of moving taskflow out of the openstack umbrella
recently. This move would likely also include the
18 matches
Mail list logo
