Promoting new members

[Dougie Richardson]

> The discussions recently about improving (and clarifying) our
> processes are part of helping newcomers to the team to see how we work
> in a transparent way, and hopefully show people that it is easy and
> rewarding to contribute. There is a reason behind those sorts of
> discussions, they are positive discussions, and they will lead to
> improvements.

How does the current proposal show the process is rewarding?

These discussions are perhaps positive in regard to streamlining our
structure but we are assuming that is going to bring more volunteers.
I don't think it will and in any case the proposed structure isn't
very different from the current one!

> I don't think it's true at all to say that people are requesting to
> join the team each week. While it may be true that people join the
> ubuntu-doc-students team on a relatively regular basis, it is not
> often that someone sends a few patches and can be considered to join
> the ubuntu-core-doc team. Nathan and Connor have recently started the
> process, and as far as I'm concerned they are contributing good
> patches, but in the past 6 months I personally haven't seen that many
> regular contributors of patches. Your email is entitled "Promoting new
> members": did you have anyone in particular in mind? If so, perhaps
> this is a good time to test drive the application process!

You know I'm talking about people joining students and not applying to
join the commit team? There can't be people to test your new process
if we don't have new students joining.

As for Nathan and Connor, while I've seen patches and contributions to
the mailing list (which are both strong) I don't know what level of
guidance they are receiving and with whom they are communicating for
help. We still haven't defined a set of criteria for commit access.

>> I for one am not happy working in this team at the moment
>
> I'm sorry to hear that, and I would like to do what I can to help, but
> it's difficult for me to understand the reasons you are unhappy. Could
> you explain them in more detail?

1. Ideas that are suggested are not met with improvement suggestions
or discussions on workability but with a list of reasons why it won't
work.

2. Suggested alterations to the frontpage of HUC - worked on it and
there's no change at all.

3. There are large areas of the team that only you understand and are
not documented - such as the website integration.

4. Whenever I venture an opinion on the Wiki, well that's guaranteed a
snipe from someone.

5. This doesn't feel like a meritocracy - I refrain from suggesting
how it feels on the grounds that hyperbole should be saved for when
you really need it.

> If it's because you are seeing a lot of discussion about process on
> the mailing list at the moment? I personally think that those
> discussions are very positive, and will lead to improvements for new
> and existing contributors to the team. It's also a very appropriate
> time in the release cycle to be having those discussions.

That's preposterous and frankly I'm insulted that you would think
that. The problem I have with these sort of discussions is that they
are focussing energy on a perceived problem rather than finding out
what the issues are.

> If it's because there are few people committing to the branches at the
> moment, well we're working on improving that. Other suggestions that
> you have for attracting contributors are definitely very welcome.

Are they? Really? I've suggested hug days and bug drives repeatedly
but after no response, well banging your head on a brick wall is
likely to cause headaches.

> I think it's worth contacting people in the team who haven't been
> heard from for a while to ask why they haven't contributed and whether
> they would be interested in getting involved again. Would you
> volunteer to do so?

Yes but woud it not be best coming from you (who is for all intents
and purposes the team leader)? Would that not show their value?

> But please remember that in open source volunteer projects, a certain
> amount of coming and going is a natural part of the project's life.
> People's lives become busier, they adopt other hobbies, start using
> different operating systems, etc etc.

Yes but if there is a strong sense of identity and team, then they
don't tend to fade away without a mention.

-- 
Regards,

Dougie Richardson
http://www.lynxworks.eu/
dougierichardson at ubuntu.com