Open Stack

2018-04-24 1:26 GMT+08:00 Doug Hellmann <doug at doughellmann.com>:
>
> Excerpts from Rico Lin's message of 2018-04-24 00:54:14 +0800:
> > ** What aspects of our policies or culture make contributing to
> > OpenStackmore difficult than contributing to other open source
projects?To
> > fully understand the map of OpenStack services is a huge challenge,
> > especially for new join developers. And for project teams, might not
>
> This is an interesting point that I haven't heard raised before.
> Typically the number of projects is used as an example of something
> that is confusing to users or deployers, but can you elaborate on
> how it is confusing to contributors?
Because in some cases, users provide contributors and when a user feature
jump in,
to clarify which projects to might be part of that feature will cause time
when they weren't in
OpenStack for long (as a contributor working on cross communities).
And usually,  when he/she send out an ML for such a cross-projects
usecase won't get much replied (really depends on teams).
For other cases, user rely on what developers' report to decides where they
should put resource on,
but developers just provides the first match (and seems usable) project he
can find in repositories.

>
> > provide new contributors guidelines to be quicker to become part of the
> > team. Finally, the format or WG/SIG/Team might confuse contributors.*
Which
>
> Do you mean because it isn't clear what sort of group to start in order
> to accomplish something?
exactly
>
> > of those would you change, and how?IMO to provides clear landscape will
> > help on give people better view on the whole map and might get the
better
> > idea on how to fit in their plan without spending too much time on
finding
> > where to contribute. Also, we need provides better ways to communicate
to
> > new contributors to at least make them feel welcome. Which maybe we can
try
> > to add in PTL/TC's (or other possible position) duty and to provide
better
> > guidelines to new join contributors who seems got no clue on what's the
> > project been working on or where the project needs help. Only people we
>
> What role do you think the First Contact SIG might play in that?

I think in this specific scenario, First Contact SIG can help define the
scope and suggest
the guideline. Because new developers always reach to SIG/project team
directly, and if it's
not working,  they might just try to work around issues and skip the
chances to join
OpenStack community.
>
> > really understand that project can provide such judgment, and it seems
like
> > a duty to provide guidelines to others (Aka help people working with
you).
> > Finally, I personally think it's a good idea to have SIG in OpenStack,
but
> > I think we need to provide technical guidelines to SIGs, so they can
make a
> > clear decision on what's their mission, where are the resources they can
> > use, and how they might be able to use it. A clear vision makes clear
> > actions.* Where else should we be looking for contributors?IMO we
actually
> > got a bunch new contributors around OpenStack (mostly for nova and
neutron
> > of course) and trying to figure out what they can/should do. Also
possibly
> > from other projects which might be doing overlapping jobs. Also to form
SIG
> > might be a more productive way to collect contributors.*
> >
> >
> >
> > May The Force of OpenStack Be With You,
> >
> > *Rico Lin*irc: ricolin
> >
> > 2018-04-23 22:06 GMT+08:00 Doug Hellmann <doug at doughellmann.com>:
> >
> > > [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.]
> > >
> > > Over the last year we have seen some contraction in the number of
> > > companies and individuals contributing to OpenStack. At the same
> > > time we have started seeing contributions from other companies and
> > > individuals. To some degree this contraction and shift in contributor
> > > base is a natural outcome of changes in OpenStack itself along with
> > > the rest of the technology industry, but as with any change it
> > > raises questions about how and whether we can ensure a smooth
> > > transition to a new steady state.
> > >
> > > What aspects of our policies or culture make contributing to OpenStack
> > > more difficult than contributing to other open source projects?
> > >
> > > Which of those would you change, and how?
> > >
> > > Where else should we be looking for contributors?
> > >
> > > Doug
> > >
> > >
__________________________________________________________________________
> > > 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




--
May The Force of OpenStack Be With You,
Rico Lin
irc: ricolin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180424/34c6d1b1/attachment.html>