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". :)<div><br><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto"> --Adam<br><div dir="auto"><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 18, 2018, 16:32 Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com">dtantsur@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/17/18 5:59 PM, Joshua Harlow wrote:<br>
> Dmitry Tantsur wrote:<br>
>> On 10/10/18 7:41 PM, Greg Hill wrote:<br>
>>> I've been out of the openstack loop for a few years, so I hope this<br>
>>> reaches the right folks.<br>
>>><br>
>>> Josh Harlow (original author of taskflow and related libraries) and I<br>
>>> have been discussing the option of moving taskflow out of the<br>
>>> openstack umbrella recently. This move would likely also include the<br>
>>> futurist and automaton libraries that are primarily used by taskflow.<br>
>><br>
>> Just for completeness: futurist and automaton are also heavily relied on<br>
>> by ironic without using taskflow.<br>
> <br>
> When did futurist get used??? nice :)<br>
> <br>
> (I knew automaton was, but maybe I knew futurist was to and I forgot, lol).<br>
<br>
I'm pretty sure you did, it happened back in Mitaka :)<br>
<br>
> <br>
>><br>
>>> The idea would be to just host them on github and use the regular<br>
>>> Github features for Issues, PRs, wiki, etc, in the hopes that this<br>
>>> would spur more development. Taskflow hasn't had any substantial<br>
>>> contributions in several years and it doesn't really seem that the<br>
>>> current openstack devs have a vested interest in moving it forward. I<br>
>>> would like to move it forward, but I don't have an interest in being<br>
>>> bound by the openstack workflow (this is why the project stagnated as<br>
>>> core reviewers were pulled on to other projects and couldn't keep up<br>
>>> with the review backlog, so contributions ground to a halt).<br>
>>><br>
>>> I guess I'm putting it forward to the larger community. Does anyone<br>
>>> have any objections to us doing this? Are there any non-obvious<br>
>>> technicalities that might make such a transition difficult? Who would<br>
>>> need to be made aware so they could adjust their own workflows?<br>
>>><br>
>>> Or would it be preferable to just fork and rename the project so<br>
>>> openstack can continue to use the current taskflow version without<br>
>>> worry of us breaking features?<br>
>>><br>
>>> Greg<br>
>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>><br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
> <br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div></div>