A Third Way for Open-Source Maintenance

A Third Way for Open-Source Maintenance

Ruby Central via YouTube Direct link

HOW IS THERE A MONOPOLY ON A COPYLEFT PIECE OF IP?

10 of 12

10 of 12

HOW IS THERE A MONOPOLY ON A COPYLEFT PIECE OF IP?

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

A Third Way for Open-Source Maintenance

Automatically move to the next video in the Classroom when playback concludes

  1. 1 A THIRD WAY FOR OPEN SOURCE
  2. 2 NOT APPLICABLE TO SERVICES, LIKE PACKAGE REPOSITORIES
  3. 3 AS USAGE INCREASES, DEMANDS ON MAINTAINER ATTENTION INCREASE
  4. 4 WRITING CODE: FIX BUGS, WRITE FEATURES, REFACTOR WRITE DOCS ISSUE TRIAGE CODE REVIEW REGULAR RELEASES GREEN BUTTON CONTROL
  5. 5 ISSUE TEAMS DOCS TEAMS NEW CONTRIBUTOR TEAMS RELEASE MANAGERS
  6. 6 #2 THE MOST VALUABLE WORK YOU CAN DO MAINTAINER IS TO RECRUIT OTHER MAINERS
  7. 7 LIBERALLY PASS OUT COMMIT BITS BUT NOT RELEASE PRIVILEGES
  8. 8 WHY DON'T PEOPLE CONTRIBUTE, OR WHY ARE THEIR CONTRIBUTIONS "BAD"?
  9. 9 MONOPOLY ON THE MAIN BRANCH
  10. 10 HOW IS THERE A MONOPOLY ON A COPYLEFT PIECE OF IP?
  11. 11 NO WAY TO BRING LEGITIMACY TO A FORK
  12. 12 DESIGN BY COMMITTEE, HOSTILE TAKEOVER, ETC.

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.