Open Stack

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 number of openstack libs outside of openstack to great effect
and have had no problems to speak of, so I don't really think this should
be a concern. I know it can be daunting to first enter the dev/review
process because it is so different from the workflow most people are used
to, but this is a problem that can be solved by having good docs (I think
the existing developer quickstart docs are very effective) and maintaining
an open and welcoming community.

    --Adam

On Thu, Oct 18, 2018, 16:32 Dmitry Tantsur <dtantsur at redhat.com> wrote:

> 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 option of moving taskflow out of the
> >>> openstack umbrella recently. This move would likely also include the
> >>> futurist and automaton libraries that are primarily used by taskflow.
> >>
> >> Just for completeness: futurist and automaton are also heavily relied on
> >> by ironic without using taskflow.
> >
> > When did futurist get used??? nice :)
> >
> > (I knew automaton was, but maybe I knew futurist was to and I forgot,
> lol).
>
> I'm pretty sure you did, it happened back in Mitaka :)
>
> >
> >>
> >>> The idea would be to just host them on github and use the regular
> >>> Github features for Issues, PRs, wiki, etc, in the hopes that this
> >>> would spur more development. Taskflow hasn't had any substantial
> >>> contributions in several years and it doesn't really seem that the
> >>> current openstack devs have a vested interest in moving it forward. I
> >>> would like to move it forward, but I don't have an interest in being
> >>> bound by the openstack workflow (this is why the project stagnated as
> >>> core reviewers were pulled on to other projects and couldn't keep up
> >>> with the review backlog, so contributions ground to a halt).
> >>>
> >>> 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 workflows?
> >>>
> >>> Or would it be preferable to just fork and rename the project so
> >>> openstack can continue to use the current taskflow version without
> >>> worry of us breaking features?
> >>>
> >>> Greg
> >>>
> >>>
> >>>
> __________________________________________________________________________
> >>>
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>
> >>
> >>
> __________________________________________________________________________
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181022/9c14992b/attachment.html>