>
> Our current policy regarding Open Development is that a project
> should cooperate with existing projects "rather than gratuitously
> competing or reinventing the wheel." [1] The flexibility provided
> by the use of the term "gratuitously" has allowed us to support
> multiple solutions in the
Rico Lin wrote:
> I think we have a start now with providing a decent map to show services
> in OpenStack and fill in with projects. What we should have and will be
> nice is to ask projects to search through the map (with a brief
> introduction of services) when they're registering. To prevent
>
*Thanks, Doug for bringing out this campaign questionI think we have a
start now with providing a decent map to show services in OpenStack and
fill in with projects. What we should have and will be nice is to ask
projects to search through the map (with a brief introduction of services)
when
On 23/04/18 09:50, Doug Hellmann wrote:
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
In the course of evaluating new
On 23/04/18 14:50, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> In the course of
On Mon, 23 Apr 2018, Doug Hellmann wrote:
Where do you draw the line at "gratuitous"?
What benefits and drawbacks do you see in supporting multiple tools
with similar features?
How would our community be different, in positive and negative ways,
if we were more strict about avoiding such
Doug Hellmann wrote:
> Where do you draw the line at "gratuitous"?
The way I interpret "gratuitous" here is: is the new project using a
technically-different approach to the same problem, or is it just
another group working at the same problem in the same way ? Is the new
project just a way to
I think this depends on the nature of the project.
For deployment tools, as we also have witnessed in OPNFV, it tends to have
multiple solutions. So it is normal to have multiple such projects although
they are solving the same problem generally speaking.
For projects that has a clear definition
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
In the course of evaluating new projects that have asked to join
as official
