Open Stack

One of the challenges in the academic sector is the time from lightbulb moment to code commit. Many of the academic resource opportunities are short term (e.g. PhDs, student projects, government funded projects) and there is a latency in current system to onboard, get the appropriate recognition in the community (such as by reviewing other changes) and then get the code committed.  This is a particular problem for the larger projects where the patch is not in one of the project goal areas for that release.

Not sure what the solution is but I would agree that there is a significant opportunity.

Tim

-----Original Message-----
From: Thierry Carrez <thierry at openstack.org>
Organization: OpenStack
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Monday, 23 April 2018 at 18:11
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

    > Where else should we be looking for contributors?
    
    Like other large open source projects, OpenStack has a lot of visibility
    in the academic sector. I feel like we are less successful than others
    in attracting contributions from there, and we could do a lot better by
    engaging with them more directly.
    
    -- 
    Thierry Carrez (ttx)
    
    __________________________________________________________________________
    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