[Bf-committers] Visibility of attribution

Campbell Barton ideasman42 at gmail.com
Fri Sep 2 05:51:39 CEST 2011


Committed https://svn.blender.org/svnroot/bf-blender/trunk/blender/intern/tools/credits_svn_gen.py

Does basic commit stats as well as finding patches and attributing the
patch authors.

And added a link to the credits page from the splash.

  http://www.blender.org/development/credits

Remaining todo's are:
* Possibly some text on the credits page, none came to mind but easy to add.
* I didn't find everyones real names (26 usernames left to find, falls
back to the ID's they commit under)
* Theres a section for companies and organizations, added 2 that
sponsored features in blender but sure there are more.


On Thu, Sep 1, 2011 at 7:59 PM, Ton Roosendaal <ton at blender.org> wrote:
> Hi Campbell,
>
> Sure, proper crediting of our contributors is always cool!
> Let's do this as you propose for now, and investigate other methods
> later.
>
> -Ton-
>
> ------------------------------------------------------------------------
> Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>
> On 31 Aug, 2011, at 7:59, Campbell Barton wrote:
>
>> On Wed, Aug 31, 2011 at 3:29 PM, Alex Fraser <adfries at vpac.org> wrote:
>>> ----- Original Message -----
>>>> From: "Alex Fraser" <adfries at vpac.org>
>>>>
>>>> For now it might be easiest to add all the 2.5x credits pages to the
>>>> page mentioned above. But as suggested by Campbell, we could move
>>>> to a
>>>> more scalable format that shows each developer and the number of
>>>> commits they have made, like this:
>>>>
>>>> http://www.libreoffice.org/about-us/credits/
>>>
>>> ... except that it would be great if we could show companies that
>>> sponsor development there too. In my case, I would be happy for the
>>> commits I make on behalf of a client be listed as a commit by that
>>> company, rather than by me.
>>>
>>> Cheers,
>>> Alex
>>
>> Credits link from splash seems reasonable, or link from help menu, or
>> prominent link from download page - I'm not that fussed as long as its
>> not getting in the way too much.
>>
>> As for how to maintain this list - I doubt maintaining by hand will
>> work, developers already don't add themselves to the `Contributors`
>> section in the header much, so if this page is only to allow people to
>> add themselves who like being credited - then I suppose it serves that
>> purpose but wont end up crediting people who don't make the effort to
>> add themselves there.
>>
>> Mostly I see this as being an extra wiki document to maintain, we
>> already barely manage to keep lists of module owners, changelogs,
>> release logs, py api changelogs, regression files.... etc. Up to date,
>> so I'd be surprised if this page ends up being properly maintained.
>>
>>
>> So I'll propose to parse svn logs, do some basic regex to get patch
>> numbers and find the patch author names so we credit them too. The
>> script can have some hard coded remappings to credit companies rather
>> than the committers - think this wont be too hard to manage.
>> If Ton's ok with it, I can look into this, think its only a few hrs
>> work.
>>
>> --
>> - Campbell
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
- Campbell


More information about the Bf-committers mailing list