KEY, PPTX863 views

Future of Collaboration

Daniel Greenfeld discusses the future of collaboration in the Python community, highlighting the risks of critical packages disappearing and the resultant failure of build scripts. He proposes solutions including sponsorships and community management to improve collaboration and trust among developers. The document emphasizes the need for structured support to maintain and grow Python projects for sustainability.

Technology◦

Daniel Greenfeld
@pydanny

Who am I?

Daniel Greenfeld (@pydanny)
Cartwheel Web / Revsys
http://djangopackages.com
https://whitespacejobs.org
Fiancé of Audrey Roy

http://www.ﬂickr.com/photos/pydanny/4442245488

Daniel Greenfeld
@pydanny

Mark Pilgrim
is
Gone

Daniel Greenfeld
@pydanny

Mark Pilgrim

• feedparser

Daniel Greenfeld
@pydanny

Mark Pilgrim

• feedparser
• conbtributed to httplib2

Daniel Greenfeld
@pydanny

Mark Pilgrim

• feedparser
• conbtributed to httplib2
• Dive into Python

Daniel Greenfeld
@pydanny

Mark Pilgrim

• feedparser
• conbtributed to httplib2
• Dive into Python
• Dive into HTML5

Daniel Greenfeld
@pydanny

Mark’s Projects?

Daniel Greenfeld
@pydanny

Mark’s Projects?

• What is the copyright on his material?

Daniel Greenfeld
@pydanny

Mark’s Projects?

• What is the copyright on his material?
• What about his code?

Daniel Greenfeld
@pydanny

httplib2

• Mark wasn’t lead, but outage anyway...

Daniel Greenfeld
@pydanny

httplib2

• Mark wasn’t lead, but outage anyway...
• PyPI?

Daniel Greenfeld
@pydanny

httplib2

• Mark wasn’t lead, but outage anyway...
• PyPI?
• http://code.google.com/p/httplib2 was down

Daniel Greenfeld
@pydanny

httplib2

• Mark wasn’t lead, but outage anyway...
• PyPI?
• http://code.google.com/p/httplib2 was down
• Had to ﬁnd a cached download

Daniel Greenfeld
@pydanny

httplib2

• Mark wasn’t lead, but outage anyway...
• PyPI?
• http://code.google.com/p/httplib2 was down
• Had to ﬁnd a cached download
• A lot of libraries depend on httplib2

Daniel Greenfeld
@pydanny

PyPI Issues?
• Packages are too easily deleted

Daniel Greenfeld
@pydanny

PyPI Issues?
• Packages are too easily deleted
• Dependency checks for that package

Daniel Greenfeld
@pydanny

PyPI Issues?
• Packages are too easily deleted
• Dependency checks for that package
• Request a project hand-off?

Daniel Greenfeld
@pydanny

PyPI Issues?
• Packages are too easily deleted
• Dependency checks for that package
• Request a project hand-off?
• Other projects need to be notiﬁed

Daniel Greenfeld
@pydanny

Repeating History?

• http://pypants(.com|.org|.net) is gone
• http://djangolint.com is here today

Daniel Greenfeld
@pydanny

Repeating History?

• django-piston

Daniel Greenfeld
@pydanny

Repeating History?

• django-piston
• python.org

Daniel Greenfeld
@pydanny

Repeating History?

• django-piston
• python.org
• http://opencomparison.org

Daniel Greenfeld
@pydanny

A Dark Future

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
Dark Future

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
Dark Future
• A number of critical Python Packages vanish

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
Dark Future
• A number of critical Python Packages vanish
• Various build scripts fail

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
Dark Future
• A number of critical Python Packages vanish
• Various build scripts fail
• Replace from caches/backups

Daniel Greenfeld
@pydanny

Repercussions
Dark Future

Daniel Greenfeld
@pydanny

Repercussions
Dark Future

• Annoyance

Daniel Greenfeld
@pydanny

Repercussions
Dark Future

• Annoyance
• Ability for Python to move forward HALTS

Daniel Greenfeld
@pydanny

Repercussions
Dark Future

• Annoyance
• Ability for Python to move forward HALTS
• Social Issues

Daniel Greenfeld
@pydanny

Not the Future

Daniel Greenfeld
@pydanny

TODAY

• Legacy code tries to install legacy packages

Daniel Greenfeld
@pydanny

TODAY

• Legacy code tries to install legacy packages
• Various build scripts fail

Daniel Greenfeld
@pydanny

TODAY

• Legacy code tries to install legacy packages
• Various build scripts fail
• Replace from caches/backups MAYBE!

Daniel Greenfeld
@pydanny

TODAY

• Legacy code tries to install legacy packages
• Various build scripts fail
• Replace from caches/backups MAYBE!
• Domain Knowledge is gone

Daniel Greenfeld
@pydanny

Library of Alexandria

http://en.wikipedia.org/wiki/File:Ancientlibraryalex.jpg

Daniel Greenfeld
@pydanny

Stuff we make today

Daniel Greenfeld
@pydanny

Stuff we make today

Is legacy within 5 years

Daniel Greenfeld
@pydanny

Lack of trust makes
collaboration hard

Daniel Greenfeld
@pydanny

No collaboration
causes the
NIH
plague

Daniel Greenfeld
@pydanny

http://en.wikipedia.org/wiki/File:Zombie-walk-kids.JPG

Daniel Greenfeld
@pydanny

Repercussions
TODAY

Daniel Greenfeld
@pydanny

Repercussions
TODAY

• Annoyance

Daniel Greenfeld
@pydanny

Repercussions
TODAY

• Annoyance
• Ability for Python to move forward HALTS

Daniel Greenfeld
@pydanny

Repercussions
TODAY

• Annoyance
• Ability for Python to move forward HALTS
• Social issues

Daniel Greenfeld
@pydanny

Solution?

Sponsorships!

Daniel Greenfeld
@pydanny

Sponsorships

• Individual, Corporate, Academic, GSOC
• Advance an open source project forward!

Daniel Greenfeld
@pydanny

Sponsorships
• Python core
• Django
• Plone Tons more
• Twisted I’m missing!

• Read the Docs (PSF)
• WebOb (PSF)

Daniel Greenfeld
@pydanny

Problems

• Application process

Daniel Greenfeld
@pydanny

Problems

• Application process
• Seems focused on short-term development

Daniel Greenfeld
@pydanny

Problems

• Application process
• Seems focused on short-term development
• Interns often produce unusable code

Daniel Greenfeld
@pydanny

Problems

• Application process
• Seems focused on short-term development
• Interns often produce unusable code
• Ongoing maintenance?

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
• Legacy code tries to install legacy packages
• Various build scripts fail
• Replace from caches/backups MAYBE!
• Domain Knowledge is gone

Daniel Greenfeld

Critical Packages
@pydanny

ES
Breakdown

G
AN
• Legacy code tries to install legacy packages
• Various build scripts fail
H
• Replace from caches/backups MAYBE!
C
• Domain Knowledge is gone
O
N

Daniel Greenfeld
@pydanny

Repercussions

• Annoyance
• Ability for Python to move forward HALTS
• Social issues

Daniel Greenfeld
@pydanny

Repercussions

ES
G
AN
• Annoyance
H
• Ability for Python to move forward HALTS
C
• Social issues
O
N

Daniel Greenfeld
@pydanny

Same as before

Daniel Greenfeld
@pydanny

Still have
Trust Issues

Daniel Greenfeld
@pydanny

Why should I
collaborate with you?

Daniel Greenfeld
@pydanny

Future still
looks dark

Daniel Greenfeld
@pydanny

Solution?

Community Managers

Daniel Greenfeld
@pydanny

Community Managers

Daniel Greenfeld
@pydanny

Community Managers

• David Eaves DjangoCon 2011 Keynote
• http://bit.ly/djangocon-keynote-2011-1
• Makes sure packages are maintained!

Daniel Greenfeld
@pydanny

Problems

• Need core/senior developers

Daniel Greenfeld
@pydanny

Problems

• Need core/senior developers
• They are already busy

Daniel Greenfeld
@pydanny

Problems

• Need core/senior developers
• They are already busy
• Who assigns authority?

Daniel Greenfeld

Solution Reconsidered
@pydanny

PSF Paid Community Manager

Daniel Greenfeld

Solution Reconsidered
@pydanny

PSF Paid Community Manager

• Reasonable pay

Daniel Greenfeld

Solution Reconsidered
@pydanny

PSF Paid Community Manager

• Reasonable pay
• Works with PyPI team to do package curation

Daniel Greenfeld

Solution Reconsidered
@pydanny

PSF Paid Community Manager

• Reasonable pay
• Works with PyPI team to do package curation
• Helps project leads if they need to hand off

Daniel Greenfeld

Solution Reconsidered
@pydanny

PSF Paid Community Manager

• Performance reviews
• Term limits
• Great resume material
• Volunteers have different priorities

Daniel Greenfeld
@pydanny

Increase
of
Trust

Daniel Greenfeld
@pydanny

This makes
collaboration easier

Daniel Greenfeld
@pydanny

The Brighter Future

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
Today
• A number of critical Python Packages vanish
• Various build scripts fail
• Replace from caches/backups
• Domain Knowledge is gone

Daniel Greenfeld

Critical Packages
@pydanny

Breakdown
Future

• A number of critical Python Packages vanish
• Various build scripts continue
• Domain Knowledge is at risk

Daniel Greenfeld
@pydanny

Repercussions
Future

• Annoyance
• Ability for Python to move forward slows
• Mitigated Social Issues

Daniel Greenfeld
@pydanny

Precedents

• Ubuntu Community Manager

Daniel Greenfeld
@pydanny

Precedents

• Ubuntu Community Manager
• Isn’t there a Fedora Community Manager?

Daniel Greenfeld
@pydanny

Precedents

• Ubuntu Community Manager
• Isn’t there a Fedora Community Manager?
• Twilio Community Managers

Daniel Greenfeld
@pydanny

More reasons to trust

Daniel Greenfeld
@pydanny

More incentives
to collaborate

Future of Collaboration

1.
Daniel Greenfeld @pydanny The Future of Collaboration by Daniel Greenfeld
2.
Daniel Greenfeld @pydanny Who am I? Daniel Greenfeld (@pydanny) Cartwheel Web / Revsys http://djangopackages.com https://whitespacejobs.org Fiancé of Audrey Roy http://www.ﬂickr.com/photos/pydanny/4442245488
3.
Daniel Greenfeld @pydanny Mark Pilgrim is Gone
4.
Daniel Greenfeld @pydanny Mark Pilgrim
5.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser
6.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser • conbtributed to httplib2
7.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser • conbtributed to httplib2 • Dive into Python
8.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser • conbtributed to httplib2 • Dive into Python • Dive into HTML5
9.
Daniel Greenfeld @pydanny Mark’s Projects?
10.
Daniel Greenfeld @pydanny Mark’s Projects? • What is the copyright on his material?
11.
Daniel Greenfeld @pydanny Mark’s Projects? • What is the copyright on his material? • What about his code?
12.
Daniel Greenfeld @pydanny httplib2
13.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway...
14.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI?
15.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI? • http://code.google.com/p/httplib2 was down
16.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI? • http://code.google.com/p/httplib2 was down • Had to ﬁnd a cached download
17.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI? • http://code.google.com/p/httplib2 was down • Had to ﬁnd a cached download • A lot of libraries depend on httplib2
18.
Daniel Greenfeld @pydanny PyPI Issues?
19.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted
20.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package
21.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off?
22.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off? • Other projects need to be notiﬁed
23.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off? • Other projects need to be notiﬁed • RSS feed of these things
24.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off? • Other projects need to be notiﬁed • RSS feed of these things • Needs moderation but PyPI busy
25.
Daniel Greenfeld @pydanny Repeating History? • http://pypants(.com|.org|.net) is gone • http://djangolint.com is here today
26.
Daniel Greenfeld @pydanny Repeating History? • django-piston
27.
Daniel Greenfeld @pydanny Repeating History? • django-piston • python.org
28.
Daniel Greenfeld @pydanny Repeating History? • django-piston • python.org • http://opencomparison.org
29.
Daniel Greenfeld @pydanny A Dark Future
30.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future
31.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish
32.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish • Various build scripts fail
33.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish • Various build scripts fail • Replace from caches/backups
34.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish • Various build scripts fail • Replace from caches/backups • Domain Knowledge is gone
35.
Daniel Greenfeld @pydanny Repercussions Dark Future
36.
Daniel Greenfeld @pydanny Repercussions Dark Future • Annoyance
37.
Daniel Greenfeld @pydanny Repercussions Dark Future • Annoyance • Ability for Python to move forward HALTS
38.
Daniel Greenfeld @pydanny Repercussions Dark Future • Annoyance • Ability for Python to move forward HALTS • Social Issues
39.
Daniel Greenfeld @pydanny Not the Future
40.
Daniel Greenfeld @pydanny TODAY
41.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages
42.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages • Various build scripts fail
43.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages • Various build scripts fail • Replace from caches/backups MAYBE!
44.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages • Various build scripts fail • Replace from caches/backups MAYBE! • Domain Knowledge is gone
45.
Daniel Greenfeld @pydanny Library of Alexandria http://en.wikipedia.org/wiki/File:Ancientlibraryalex.jpg
46.
Daniel Greenfeld @pydanny Stuff we make today
47.
Daniel Greenfeld @pydanny Stuff we make today Is legacy within 5 years
48.
Daniel Greenfeld @pydanny Trust Issues
49.
Daniel Greenfeld @pydanny Lack of trust makes collaboration hard
50.
Daniel Greenfeld @pydanny No collaboration causes the NIH plague
51.
Daniel Greenfeld @pydanny http://en.wikipedia.org/wiki/File:Zombie-walk-kids.JPG
52.
Daniel Greenfeld @pydanny Repercussions TODAY
53.
Daniel Greenfeld @pydanny Repercussions TODAY • Annoyance
54.
Daniel Greenfeld @pydanny Repercussions TODAY • Annoyance • Ability for Python to move forward HALTS
55.
Daniel Greenfeld @pydanny Repercussions TODAY • Annoyance • Ability for Python to move forward HALTS • Social issues
56.
Daniel Greenfeld @pydanny Solution? Sponsorships!
57.
Daniel Greenfeld @pydanny Sponsorships • Individual, Corporate, Academic, GSOC • Advance an open source project forward!
58.
Daniel Greenfeld @pydanny Sponsorships • Python core • Django • Plone Tons more • Twisted I’m missing! • Read the Docs (PSF) • WebOb (PSF)
59.
Daniel Greenfeld @pydanny Problems
60.
Daniel Greenfeld @pydanny Problems • Application process
61.
Daniel Greenfeld @pydanny Problems • Application process • Seems focused on short-term development
62.
Daniel Greenfeld @pydanny Problems • Application process • Seems focused on short-term development • Interns often produce unusable code
63.
Daniel Greenfeld @pydanny Problems • Application process • Seems focused on short-term development • Interns often produce unusable code • Ongoing maintenance?
64.
Daniel Greenfeld Critical Packages @pydanny Breakdown • Legacy code tries to install legacy packages • Various build scripts fail • Replace from caches/backups MAYBE! • Domain Knowledge is gone
65.
Daniel Greenfeld Critical Packages @pydanny ES Breakdown G AN • Legacy code tries to install legacy packages • Various build scripts fail H • Replace from caches/backups MAYBE! C • Domain Knowledge is gone O N
66.
Daniel Greenfeld @pydanny Repercussions • Annoyance • Ability for Python to move forward HALTS • Social issues
67.
Daniel Greenfeld @pydanny Repercussions ES G AN • Annoyance H • Ability for Python to move forward HALTS C • Social issues O N
68.
Daniel Greenfeld @pydanny Same as before
69.
Daniel Greenfeld @pydanny Still have Trust Issues
70.
Daniel Greenfeld @pydanny Why should I collaborate with you?
71.
Daniel Greenfeld @pydanny Future still looks dark
72.
Daniel Greenfeld @pydanny So now what?
73.
Daniel Greenfeld @pydanny Solution? Community Managers
74.
Daniel Greenfeld @pydanny Community Managers
75.
Daniel Greenfeld @pydanny Community Managers • David Eaves DjangoCon 2011 Keynote • http://bit.ly/djangocon-keynote-2011-1 • Makes sure packages are maintained!
76.
Daniel Greenfeld @pydanny Problems
77.
Daniel Greenfeld @pydanny Problems • Need core/senior developers
78.
Daniel Greenfeld @pydanny Problems • Need core/senior developers • They are already busy
79.
Daniel Greenfeld @pydanny Problems • Need core/senior developers • They are already busy • Who assigns authority?
80.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager
81.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay
82.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay • Works with PyPI team to do package curation
83.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay • Works with PyPI team to do package curation • Helps project leads if they need to hand off
84.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay • Works with PyPI team to do package curation • Helps project leads if they need to hand off • Broadcasts so the community knows about it
85.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Performance reviews • Term limits • Great resume material • Volunteers have different priorities
86.
Daniel Greenfeld @pydanny Increase of Trust
87.
Daniel Greenfeld @pydanny This makes collaboration easier
88.
Daniel Greenfeld @pydanny The Brighter Future
89.
Daniel Greenfeld Critical Packages @pydanny Breakdown Today • A number of critical Python Packages vanish • Various build scripts fail • Replace from caches/backups • Domain Knowledge is gone
90.
Daniel Greenfeld Critical Packages @pydanny Breakdown Future • A number of critical Python Packages vanish • Various build scripts continue • Domain Knowledge is at risk
91.
Daniel Greenfeld @pydanny Repercussions Today • Annoyance • Ability for Python to move forward HALTS • Social Issues
92.
Daniel Greenfeld @pydanny Repercussions Future • Annoyance • Ability for Python to move forward slows • Mitigated Social Issues
93.
Daniel Greenfeld @pydanny Precedents
94.
Daniel Greenfeld @pydanny Precedents • Ubuntu Community Manager
95.
Daniel Greenfeld @pydanny Precedents • Ubuntu Community Manager • Isn’t there a Fedora Community Manager?
96.
Daniel Greenfeld @pydanny Precedents • Ubuntu Community Manager • Isn’t there a Fedora Community Manager? • Twilio Community Managers
97.
Daniel Greenfeld @pydanny But...
98.
Daniel Greenfeld @pydanny I want more
99.
Daniel Greenfeld @pydanny More reasons to trust
100.
Daniel Greenfeld @pydanny More incentives to collaborate

Editor's Notes

#2 \n
#3 \n
#4 \n
#5 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#6 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#7 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#8 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#9 \n
#10 \n
#11 This is how I found out Mark Pilgrim was gone\n
#12 This is how I found out Mark Pilgrim was gone\n
#13 This is how I found out Mark Pilgrim was gone\n
#14 This is how I found out Mark Pilgrim was gone\n
#15 This is how I found out Mark Pilgrim was gone\n
#16 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#17 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#18 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#19 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#20 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#21 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#22 What lesser known projects have died? What don&#x2019;t I know about but you do? We lost pypants because the developers were too busy. djangolint is awesome, but will it be maintained? Do the developers have time to port it to general Python?\n
#23 *django-piston was great, but the maintainer got busy running his startup. Jesper handed off the project, and it was really big of him. But he did it because he was nudged to do so.\n*python.org needs a serious reboot - did anyone get the work? When will they have the time?\n\n
#24 *django-piston was great, but the maintainer got busy running his startup. Jesper handed off the project, and it was really big of him. But he did it because he was nudged to do so.\n*python.org needs a serious reboot - did anyone get the work? When will they have the time?\n\n
#25 *django-piston was great, but the maintainer got busy running his startup. Jesper handed off the project, and it was really big of him. But he did it because he was nudged to do so.\n*python.org needs a serious reboot - did anyone get the work? When will they have the time?\n\n
#26 Jesse Noller bit\n
#27 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#28 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#29 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#30 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#31 Third party community as critical as Python core\n
#32 Third party community as critical as Python core\n
#33 Third party community as critical as Python core\n
#34 \n
#35 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#36 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#37 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#38 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#39 We&#x2019;ve lost works in antiquity. Who was behind it&#x2019;s destruction is now moot, but the loss of critical data in our history hurts us even today. \n
#40 \n
#41 When you can&#x2019;t find packages...\nWhen you can&#x2019;t find documentation\nWhen you are trying to decompile source code, you worry about the source. You don&#x2019;t trust it anymore\n
#42 Why should I work with you when I can&#x2019;y rely on you?\n
#43 Also know as NIH, this doesn&#x2019;t just create misery in developers and impossible to maintain projects, it also causes the Zombie Apocolypse\n
#44 \n
#45 Contention: Third party community as critical as Python core\n
#46 Contention: Third party community as critical as Python core\n
#47 Contention: Third party community as critical as Python core\n
#48 Some of you are probably wondering about the sponsorship angle...\n
#49 Google Summer of Code\n
#50 \n
#51 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#52 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#53 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#54 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#55 Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#56 Contention: Third party community as critical as Python core\n
#57 \n
#58 Still have trust issues\nSprints are great but if the generated code isn&#x2019;t maintained...\n
#59 Still have trust issues\nSprints are great but if the generated code isn&#x2019;t maintained...\n
#60 the future still looks dark\n
#61 \n
#62 \n
#63 \n
#64 Didn&#x2019;t answer the question about getting qualified people to do the work consistently.\nWorks Mozilla, a 700 person org, might paying people to do community management\nVolunteers are great but often have life get in the way. Who assigns the authority? The PSF?\n\n
#65 Didn&#x2019;t answer the question about getting qualified people to do the work consistently.\nWorks Mozilla, a 700 person org, might paying people to do community management\nVolunteers are great but often have life get in the way. Who assigns the authority? The PSF?\n\n
#66 Didn&#x2019;t answer the question about getting qualified people to do the work consistently.\nWorks Mozilla, a 700 person org, might paying people to do community management\nVolunteers are great but often have life get in the way. Who assigns the authority? The PSF?\n\n
#67 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#68 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#69 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#70 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#71 performance reviews by the PSF and PyPI team\nTerm limits cause eternal curation can be rough\nNeeds to be paid job because this is hard, grueling work, and volunteers get busy\n
#72 \n
#73 \n
#74 \n
#75 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#76 Build scripts continue\nDomain knowledge is easier to track cause we know what we lost.\n
#77 Third party community as critical as Python core\n
#78 Third party community as critical as Python core\n
#79 Contention: Third party community as critical as Python core\nGood community managers really make a difference regardless of if it&#x2019;s open source or not\n
#80 Contention: Third party community as critical as Python core\nGood community managers really make a difference regardless of if it&#x2019;s open source or not\n
#81 Contention: Third party community as critical as Python core\nGood community managers really make a difference regardless of if it&#x2019;s open source or not\n
#82 \n
#83 \n
#84 \n
#85 \n
#86 \n
#87 We have PyPI and other things, how do we continue them?\nIf we&#x2019;re Guido, I think we get hired by Google to do whatever we want.\n
#88 \n
#89 \n
#90 \n
#91 \n
#92 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#93 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#94 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#95 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#96 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#97 \n
#98 \n
#99 \n
#100 This isn&#x2019;t about hosting costs\nDon&#x2019;t just throw money at Django core, seed a project that uses Python\nNot a way for people to skim off the top.\n\n\n
#101 This isn&#x2019;t about hosting costs\nDon&#x2019;t just throw money at Django core, seed a project that uses Python\nNot a way for people to skim off the top.\n\n\n

Future of Collaboration

1.
Daniel Greenfeld @pydanny The Future of Collaboration by Daniel Greenfeld
2.
Daniel Greenfeld @pydanny Who am I? Daniel Greenfeld (@pydanny) Cartwheel Web / Revsys http://djangopackages.com https://whitespacejobs.org Fiancé of Audrey Roy http://www.ﬂickr.com/photos/pydanny/4442245488
3.
Daniel Greenfeld @pydanny Mark Pilgrim is Gone
4.
Daniel Greenfeld @pydanny Mark Pilgrim
5.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser
6.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser • conbtributed to httplib2
7.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser • conbtributed to httplib2 • Dive into Python
8.
Daniel Greenfeld @pydanny Mark Pilgrim • feedparser • conbtributed to httplib2 • Dive into Python • Dive into HTML5
9.
Daniel Greenfeld @pydanny Mark’s Projects?
10.
Daniel Greenfeld @pydanny Mark’s Projects? • What is the copyright on his material?
11.
Daniel Greenfeld @pydanny Mark’s Projects? • What is the copyright on his material? • What about his code?
12.
Daniel Greenfeld @pydanny httplib2
13.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway...
14.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI?
15.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI? • http://code.google.com/p/httplib2 was down
16.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI? • http://code.google.com/p/httplib2 was down • Had to ﬁnd a cached download
17.
Daniel Greenfeld @pydanny httplib2 • Mark wasn’t lead, but outage anyway... • PyPI? • http://code.google.com/p/httplib2 was down • Had to ﬁnd a cached download • A lot of libraries depend on httplib2
18.
Daniel Greenfeld @pydanny PyPI Issues?
19.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted
20.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package
21.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off?
22.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off? • Other projects need to be notiﬁed
23.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off? • Other projects need to be notiﬁed • RSS feed of these things
24.
Daniel Greenfeld @pydanny PyPI Issues? • Packages are too easily deleted • Dependency checks for that package • Request a project hand-off? • Other projects need to be notiﬁed • RSS feed of these things • Needs moderation but PyPI busy
25.
Daniel Greenfeld @pydanny Repeating History? • http://pypants(.com|.org|.net) is gone • http://djangolint.com is here today
26.
Daniel Greenfeld @pydanny Repeating History? • django-piston
27.
Daniel Greenfeld @pydanny Repeating History? • django-piston • python.org
28.
Daniel Greenfeld @pydanny Repeating History? • django-piston • python.org • http://opencomparison.org
29.
Daniel Greenfeld @pydanny A Dark Future
30.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future
31.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish
32.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish • Various build scripts fail
33.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish • Various build scripts fail • Replace from caches/backups
34.
Daniel Greenfeld Critical Packages @pydanny Breakdown Dark Future • A number of critical Python Packages vanish • Various build scripts fail • Replace from caches/backups • Domain Knowledge is gone
35.
Daniel Greenfeld @pydanny Repercussions Dark Future
36.
Daniel Greenfeld @pydanny Repercussions Dark Future • Annoyance
37.
Daniel Greenfeld @pydanny Repercussions Dark Future • Annoyance • Ability for Python to move forward HALTS
38.
Daniel Greenfeld @pydanny Repercussions Dark Future • Annoyance • Ability for Python to move forward HALTS • Social Issues
39.
Daniel Greenfeld @pydanny Not the Future
40.
Daniel Greenfeld @pydanny TODAY
41.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages
42.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages • Various build scripts fail
43.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages • Various build scripts fail • Replace from caches/backups MAYBE!
44.
Daniel Greenfeld @pydanny TODAY • Legacy code tries to install legacy packages • Various build scripts fail • Replace from caches/backups MAYBE! • Domain Knowledge is gone
45.
Daniel Greenfeld @pydanny Library of Alexandria http://en.wikipedia.org/wiki/File:Ancientlibraryalex.jpg
46.
Daniel Greenfeld @pydanny Stuff we make today
47.
Daniel Greenfeld @pydanny Stuff we make today Is legacy within 5 years
48.
Daniel Greenfeld @pydanny Trust Issues
49.
Daniel Greenfeld @pydanny Lack of trust makes collaboration hard
50.
Daniel Greenfeld @pydanny No collaboration causes the NIH plague
51.
Daniel Greenfeld @pydanny http://en.wikipedia.org/wiki/File:Zombie-walk-kids.JPG
52.
Daniel Greenfeld @pydanny Repercussions TODAY
53.
Daniel Greenfeld @pydanny Repercussions TODAY • Annoyance
54.
Daniel Greenfeld @pydanny Repercussions TODAY • Annoyance • Ability for Python to move forward HALTS
55.
Daniel Greenfeld @pydanny Repercussions TODAY • Annoyance • Ability for Python to move forward HALTS • Social issues
56.
Daniel Greenfeld @pydanny Solution? Sponsorships!
57.
Daniel Greenfeld @pydanny Sponsorships • Individual, Corporate, Academic, GSOC • Advance an open source project forward!
58.
Daniel Greenfeld @pydanny Sponsorships • Python core • Django • Plone Tons more • Twisted I’m missing! • Read the Docs (PSF) • WebOb (PSF)
59.
Daniel Greenfeld @pydanny Problems
60.
Daniel Greenfeld @pydanny Problems • Application process
61.
Daniel Greenfeld @pydanny Problems • Application process • Seems focused on short-term development
62.
Daniel Greenfeld @pydanny Problems • Application process • Seems focused on short-term development • Interns often produce unusable code
63.
Daniel Greenfeld @pydanny Problems • Application process • Seems focused on short-term development • Interns often produce unusable code • Ongoing maintenance?
64.
Daniel Greenfeld Critical Packages @pydanny Breakdown • Legacy code tries to install legacy packages • Various build scripts fail • Replace from caches/backups MAYBE! • Domain Knowledge is gone
65.
Daniel Greenfeld Critical Packages @pydanny ES Breakdown G AN • Legacy code tries to install legacy packages • Various build scripts fail H • Replace from caches/backups MAYBE! C • Domain Knowledge is gone O N
66.
Daniel Greenfeld @pydanny Repercussions • Annoyance • Ability for Python to move forward HALTS • Social issues
67.
Daniel Greenfeld @pydanny Repercussions ES G AN • Annoyance H • Ability for Python to move forward HALTS C • Social issues O N
68.
Daniel Greenfeld @pydanny Same as before
69.
Daniel Greenfeld @pydanny Still have Trust Issues
70.
Daniel Greenfeld @pydanny Why should I collaborate with you?
71.
Daniel Greenfeld @pydanny Future still looks dark
72.
Daniel Greenfeld @pydanny So now what?
73.
Daniel Greenfeld @pydanny Solution? Community Managers
74.
Daniel Greenfeld @pydanny Community Managers
75.
Daniel Greenfeld @pydanny Community Managers • David Eaves DjangoCon 2011 Keynote • http://bit.ly/djangocon-keynote-2011-1 • Makes sure packages are maintained!
76.
Daniel Greenfeld @pydanny Problems
77.
Daniel Greenfeld @pydanny Problems • Need core/senior developers
78.
Daniel Greenfeld @pydanny Problems • Need core/senior developers • They are already busy
79.
Daniel Greenfeld @pydanny Problems • Need core/senior developers • They are already busy • Who assigns authority?
80.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager
81.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay
82.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay • Works with PyPI team to do package curation
83.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay • Works with PyPI team to do package curation • Helps project leads if they need to hand off
84.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Reasonable pay • Works with PyPI team to do package curation • Helps project leads if they need to hand off • Broadcasts so the community knows about it
85.
Daniel Greenfeld Solution Reconsidered @pydanny PSF Paid Community Manager • Performance reviews • Term limits • Great resume material • Volunteers have different priorities
86.
Daniel Greenfeld @pydanny Increase of Trust
87.
Daniel Greenfeld @pydanny This makes collaboration easier
88.
Daniel Greenfeld @pydanny The Brighter Future
89.
Daniel Greenfeld Critical Packages @pydanny Breakdown Today • A number of critical Python Packages vanish • Various build scripts fail • Replace from caches/backups • Domain Knowledge is gone
90.
Daniel Greenfeld Critical Packages @pydanny Breakdown Future • A number of critical Python Packages vanish • Various build scripts continue • Domain Knowledge is at risk
91.
Daniel Greenfeld @pydanny Repercussions Today • Annoyance • Ability for Python to move forward HALTS • Social Issues
92.
Daniel Greenfeld @pydanny Repercussions Future • Annoyance • Ability for Python to move forward slows • Mitigated Social Issues
93.
Daniel Greenfeld @pydanny Precedents
94.
Daniel Greenfeld @pydanny Precedents • Ubuntu Community Manager
95.
Daniel Greenfeld @pydanny Precedents • Ubuntu Community Manager • Isn’t there a Fedora Community Manager?
96.
Daniel Greenfeld @pydanny Precedents • Ubuntu Community Manager • Isn’t there a Fedora Community Manager? • Twilio Community Managers
97.
Daniel Greenfeld @pydanny But...
98.
Daniel Greenfeld @pydanny I want more
99.
Daniel Greenfeld @pydanny More reasons to trust
100.
Daniel Greenfeld @pydanny More incentives to collaborate

Editor's Notes

#2 \n
#3 \n
#4 \n
#5 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#6 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#7 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#8 Gave so much to the community. Really sad to see him go. While I really prefer other resources than his Dive into Python, his Dive into HTML5 is a GOTO for me. I know I&#x2019;m missing other stuff he did.\n
#9 \n
#10 \n
#11 This is how I found out Mark Pilgrim was gone\n
#12 This is how I found out Mark Pilgrim was gone\n
#13 This is how I found out Mark Pilgrim was gone\n
#14 This is how I found out Mark Pilgrim was gone\n
#15 This is how I found out Mark Pilgrim was gone\n
#16 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#17 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#18 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#19 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#20 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#21 There needs to be human moderated process for someone taking over a project. And expecting the PyPI team to manage this sort of thing is unrealistic and unfair. PyPI and other resource leaders are overwhelmed with maintenance, enhancements, and life.\n
#22 What lesser known projects have died? What don&#x2019;t I know about but you do? We lost pypants because the developers were too busy. djangolint is awesome, but will it be maintained? Do the developers have time to port it to general Python?\n
#23 *django-piston was great, but the maintainer got busy running his startup. Jesper handed off the project, and it was really big of him. But he did it because he was nudged to do so.\n*python.org needs a serious reboot - did anyone get the work? When will they have the time?\n\n
#24 *django-piston was great, but the maintainer got busy running his startup. Jesper handed off the project, and it was really big of him. But he did it because he was nudged to do so.\n*python.org needs a serious reboot - did anyone get the work? When will they have the time?\n\n
#25 *django-piston was great, but the maintainer got busy running his startup. Jesper handed off the project, and it was really big of him. But he did it because he was nudged to do so.\n*python.org needs a serious reboot - did anyone get the work? When will they have the time?\n\n
#26 Jesse Noller bit\n
#27 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#28 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#29 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#30 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#31 Third party community as critical as Python core\n
#32 Third party community as critical as Python core\n
#33 Third party community as critical as Python core\n
#34 \n
#35 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#36 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#37 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#38 Oh wait! It&#x2019;s not the future! It&#x2019;s today!\nThe domain knowledge, maybe the precompiled source is done.\nIt&#x2019;s like the architecture record has been wiped from existence by illiterate mobs\n\n
#39 We&#x2019;ve lost works in antiquity. Who was behind it&#x2019;s destruction is now moot, but the loss of critical data in our history hurts us even today. \n
#40 \n
#41 When you can&#x2019;t find packages...\nWhen you can&#x2019;t find documentation\nWhen you are trying to decompile source code, you worry about the source. You don&#x2019;t trust it anymore\n
#42 Why should I work with you when I can&#x2019;y rely on you?\n
#43 Also know as NIH, this doesn&#x2019;t just create misery in developers and impossible to maintain projects, it also causes the Zombie Apocolypse\n
#44 \n
#45 Contention: Third party community as critical as Python core\n
#46 Contention: Third party community as critical as Python core\n
#47 Contention: Third party community as critical as Python core\n
#48 Some of you are probably wondering about the sponsorship angle...\n
#49 Google Summer of Code\n
#50 \n
#51 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#52 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#53 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#54 Applications process is tedious. Email me! Find obscure link! Requires a lot of recruiting/negotiating\nFocus seems to be on short term, sprinty kind of stuff\nNot enough money, server costs are not the issue\n
#55 Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#56 Contention: Third party community as critical as Python core\n
#57 \n
#58 Still have trust issues\nSprints are great but if the generated code isn&#x2019;t maintained...\n
#59 Still have trust issues\nSprints are great but if the generated code isn&#x2019;t maintained...\n
#60 the future still looks dark\n
#61 \n
#62 \n
#63 \n
#64 Didn&#x2019;t answer the question about getting qualified people to do the work consistently.\nWorks Mozilla, a 700 person org, might paying people to do community management\nVolunteers are great but often have life get in the way. Who assigns the authority? The PSF?\n\n
#65 Didn&#x2019;t answer the question about getting qualified people to do the work consistently.\nWorks Mozilla, a 700 person org, might paying people to do community management\nVolunteers are great but often have life get in the way. Who assigns the authority? The PSF?\n\n
#66 Didn&#x2019;t answer the question about getting qualified people to do the work consistently.\nWorks Mozilla, a 700 person org, might paying people to do community management\nVolunteers are great but often have life get in the way. Who assigns the authority? The PSF?\n\n
#67 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#68 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#69 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#70 If the PSF can afford an office administrator, what about a Paid Community Manager?\nPings project leads in a friendly way if pull requests and bug tickets aren't happening\n
#71 performance reviews by the PSF and PyPI team\nTerm limits cause eternal curation can be rough\nNeeds to be paid job because this is hard, grueling work, and volunteers get busy\n
#72 \n
#73 \n
#74 \n
#75 Have to find caches of old code. That part is easy. Finding those capable, willing, and with the time to maintain critical domain is really hard. \n
#76 Build scripts continue\nDomain knowledge is easier to track cause we know what we lost.\n
#77 Third party community as critical as Python core\n
#78 Third party community as critical as Python core\n
#79 Contention: Third party community as critical as Python core\nGood community managers really make a difference regardless of if it&#x2019;s open source or not\n
#80 Contention: Third party community as critical as Python core\nGood community managers really make a difference regardless of if it&#x2019;s open source or not\n
#81 Contention: Third party community as critical as Python core\nGood community managers really make a difference regardless of if it&#x2019;s open source or not\n
#82 \n
#83 \n
#84 \n
#85 \n
#86 \n
#87 We have PyPI and other things, how do we continue them?\nIf we&#x2019;re Guido, I think we get hired by Google to do whatever we want.\n
#88 \n
#89 \n
#90 \n
#91 \n
#92 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#93 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#94 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#95 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#96 Contests to help find applicants\nYCombinator is one way to do it\nAfter launch, provide advice but don&#x2019;t bikeshed!!!\n
#97 \n
#98 \n
#99 \n
#100 This isn&#x2019;t about hosting costs\nDon&#x2019;t just throw money at Django core, seed a project that uses Python\nNot a way for people to skim off the top.\n\n\n
#101 This isn&#x2019;t about hosting costs\nDon&#x2019;t just throw money at Django core, seed a project that uses Python\nNot a way for people to skim off the top.\n\n\n

Future of Collaboration

Future of Collaboration

Editor's Notes

More Related Content

Similar to Future of Collaboration

More from Daniel Greenfeld

Recently uploaded

Future of Collaboration

Editor's Notes