22
“Growing a Large, Collaborative Plone Site” J Cameron Cooper [email protected]

“Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

“Growing a Large, Collaborative Plone Site”

J Cameron [email protected]

Page 2: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Connexions

Page 3: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Module

Page 4: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Collection

Page 5: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Browsing

Page 6: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Popularity

Page 7: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Feedback

Page 8: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Author Info

Page 9: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Stats

Page 10: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Even more stats

Page 11: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Featured Content

Page 12: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Featured Author

Page 13: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Lenses

Page 14: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Lenses

Page 15: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Lenses – on content

Page 16: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Usability testing

Page 17: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Flashy stuff

Page 18: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Organizational

Keep complexity down

Keep changes well controlled

code tracking

no TTW! (except emergencies)

Test hard

Try to upstream everything you can

Good bug tracking worth its weight in gold

Page 19: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Upstreaming

Bug reports, at least

When you fix, fix upstream, even if you can't wait

Put features into existing projects, if they want it

Spin off everything you can

Yes, it's hard when your hair's on fire

If you don't start open source, it's hard to get there

But, yes, it works

Page 20: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Scaling

Standard stuff

Caching... no really

Hardware may be cheaper

Specifically

Be sure to test with load for things that scale badly

Design around conflict errors

Sessions can be trouble

Page 21: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Upgrading

Templates are biggest problem

Note in each template/monkeypatch everything you do

Going off the rails may work better

Make install scripts idempotent

including upgrade bits

Page 22: “Growing a Large, Collaborative Plone Site” · Upstreaming Bug reports, at least When you fix, fix upstream, even if you can't wait Put features into existing projects, if they

Future

More open sourcing

You will be able to install it!

Print on demand

Distributed repository

Plug: come work with us!