Closed Bug 681124 Opened 13 years ago Closed 13 years ago

fun: generate a humans.txt file

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

Product:
developer.mozilla.org Graveyard
Component:
Wiki pages
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: groovecoder, Assigned: buddy)

References

Details

(Whiteboard: c=fun u=contributors p=1) 

See humanstxt.org

Suggest using github repos authors and/or bugzilla users for source data, and making it a re-usable app for other mozilla sites. Then mozillians.org could scoop the humans.txt data for every mozilla site.
Create the file by hand for now.

Create an investigate: automate humans.txt bug
Whiteboard: c=fun u=contributors p= → c=fun u=contributors p=1
Target Milestone: 1.1 → 1.2
Don't forget the localizers. Maybe scoop those names up from Verbatim or SVN commits to locale/
Also, do we want to include just the people behind the code, or all the authors participating in docs? That could produce a pretty huge list :)
(In reply to l.m.orchard [:lorchard] from comment #3)
> Also, do we want to include just the people behind the code, or all the
> authors participating in docs? That could produce a pretty huge list :)

I think our dev team, localizers from Verbatim and the top docs contributors (via MindTouch stats and our Doc Sprint rosters that Janet can provide) will make a good list of folks too include this first time around.
All-hands de-reailed 1.2. Bumping to 1.3.
Target Milestone: 1.2 → 1.3
Bumping
Target Milestone: 1.3 → 1.4
github:
https://github.com/api/v2/json/repos/show/mozilla/kuma/contributors

verbatim:
https://localize.mozilla.org/projects/mdn/ 
foreach table#stats tr.item td.stats-name a[href]
    foreach table.topcontributors td.stats-name as contributor

MindTouch:
Not sure. Sheppy?
This is hard. Not everyone that makes a change warrants actually showing up in something like this (for example, if someone adds spam, they'd get added to the list if you automated it). Might be something we could do based on some sort of frecency type of algorithm, but realistically unless webdev wants to delve into it, it's going to be a while before we have time to make something so low priority happen, at least until the documentation bandwidth improves. Maybe once we get another writer added on-staff.
Fair enough. I wouldn't mind just making a hard-coded file listing out some hand-picked doc contributors.
for the localizers, discovered this trick:

svn log --quiet http://svn.mozilla.org/projects/mdn/trunk/locale/ | grep '^r' | awk '{print $3}' | sort | uniq > committers.txt
Assignee: nobody → buddy
Target Milestone: 1.4 → 1.3
Blocks: 693294
https://developer-stage9.mozilla.org/humans.txt
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Commits pushed to https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/633a65def5b404d4bb8572cc1f5748aa432cf374
Merge pull request #15 from buddylindsey/mdn

Humans.txt Start based on bugzilla Bug 681124

https://github.com/mozilla/kuma/commit/398e9a878246b6525a0ddc509b0f61d4306522c2
Bug 681124 move humans.txt file to media root
verified fixed https://developer.mozilla.org/humans.txt
Status: RESOLVED → VERIFIED
Version: MDN → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.