community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lefty Leverenz <>
Subject Re: Overlapping role descriptions
Date Fri, 25 Sep 2015 07:13:51 GMT
Pierre, although your new descriptions make sense I still prefer the
originals.  Projects have separate mailing lists for developers and users,
so people need to understand the difference.  And users can contribute too.

Perhaps a third description for "contributor" could clarify the overlap.

-- Lefty

On Fri, Sep 25, 2015 at 2:57 AM, Pierre Smits <>

> Hi All,
> At we have
> descriptions for the user and the developer roles. But the descriptions are
> overlapping.
> For *user* we have:
> A *user* is someone that uses our software. They contribute to the Apache
> projects by providing feedback to developers in the form of bug reports and
> feature suggestions. Users participate in the Apache community by helping
> other users on mailing lists and user support forums.
> And for *developer* we have:
> A *developer* is a user who contributes to a project in the form of code or
> documentation. They take extra steps to participate in a project, are
> active on the developer mailing list, participate in discussions, provide
> patches, documentation, suggestions, and criticism. Developers are also
> known as *contributors* .
> Better would be to change the *user* definition to:
> A user is a person or organisation experiencing a benefit from
> the contributions made to the ASF in general or a project in particular.
> And the *developer* definition should be removed and replaced with a
> *contributor* definition:
> A contributor is a person who contributes to a project of the ASF and
> therefore to the ASF. Contributions are (but not limited to) participations
> in mailing lists, conferences, providing improvements to code,
> documentation, supplying suggestions and criticism to further the project
> in particular and the ASF in general.
> Recognised contributors are contributors who have also a signed Contributor
> License Agreement (CLA) <> on file.
> Both new descriptions remove the ambiguity regarding using and contributing
> from the old descriptions, and the new one for contributor feeds into the
> diversity aspect.
> What do you think?
> Best regards,
> Pierre Smits
> *OFBiz Extensions Marketplace*

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message