Consider contributing your code: When, how and why
jerdavis
As a developer on a project, you're often faced with requirements that result in some amount of development. Maybe there's a core or contributed module that gets you part of the way there, or maybe there's nothing at all.
When tackling these projects, what can we do as developers to deliver the best solution? How can we ensure that the code we write will be solid and supportable by the client and future you?
In this session, we'll talk about solving these problems. Including when, how and why to consider contributing your code to Drupal.org - or as Open Source in general.
We'll work through how to decide when it might make sense to contribute your code and how thinking about contributing can change the way you architect a solution. We'll discuss ways of abstracting your code so it's more easily used by yourself and others on future projects.
Finally, we'll talk about why contributing is beneficial for you as a developer, not just in the sense of "giving back", but as a tool to further your own career, raise your profile within the community and even benefit your organization.
Learning Objectives
- Learn when it makes sense to contribute code.
- Know how to approach abstracting a project for contribution.
- Understand why contribution benefits their organization, client, and themselves.
Target Audience
Developers working on projects for their organization or on behalf of clients who are interested in learning why contributing code is beneficial and how to get started.
Prerequisites
Attendees will get the most from this session if they are or have been involved in creating custom code on behalf of their organization or a client.
Track
being human, contributions, & community
Experience Level
Beginner
If no timezone is set on your profile, time is displayed in UTC.
Update your profile's timezone
