About
We are a team of developer advocates who work to make data simple and accessible on the IBM Cloud.
Team
-
Abdullah Alger
Break. Build. Cloud. Database.
-
G. Adam Cox
Physicist, Data Scientist and Developer Advocate
-
Brad Noble
n00b
-
Bradley Holt
Offline First FTW.
-
David Taieb
Passionate about data science, machine learning, and meeting developers.
-
Dj Walker-Morgan
Writes code and words.
-
Glynn Bird
Making it easier to work with JSON.
-
John O'Connor
Entrepreneur, engineer, educator.
-
Lorna Mitchell
Incurable open source fanatic
-
Margriet Groenendijk
Weather makes the world go round.
-
Mark Watson
Welcome to my data lab.
-
Maureen McElaney
Everybody's favorite community ambassador.
-
Mike Broberg
I edit everything.
-
Patrick Titzler
Swiss Army Knife of technology, but German.
-
Raj Singh
Partners are my jam.
-
Teri Chadbourne
Crafting developer communities through events.
-
va barbosa
crioulo de cova rodela
Get Involved
So, you’ve found an interesting project and want to contribute, but you’ve got a lot of questions: How do I get started? Is there a process I need to follow to give back? Is there a license that I need to sign before I make my contributions? If I use this code, is there a forum where I can get support? Is there a wiki that will help me set up my environment to make those changes?
You have the questions, and we have the answers. Let’s dive in and guide you through the process for making a contribution to a project. You’ll be an open source expert in no time.
How do I get started?
Well, you’ve already started — you’ve explored Watson Data Lab and have found a project that you want to delve into further.
The first thing you should do is learn how to get started with GitHub. Learn how to create a GitHub account if you don’t already have one. Next, you’ll need to set up Git on your machine. Fortunately, GitHub has a really useful “bootcamp” that has a whole section on setting up Git for your machine. Once you’ve completed the set-up, you can begin to do more advanced tasks like cloning a project to your local machine so that you can start to dig in to the code, make changes, and contribute to the community.
Can I easily give back to the project?
The answer to that question is “yes … with some prep work.” After you’ve spent time digging into the code, extending functionality, and making improvements, it’s natural to want to contribute your work back to the project. To do that, you need to make a pull request, a way of telling others about suggested improvements or fixes for their code.
Note: Before you submit your pull request:
- Make sure the automated tests (if they exist for the project) pass before submitting the PR.
- Please check for a Contribute topic in the project’s repo or docs in the project’s repository on GitHub. Some projects may require that you sign a Contributor’s License Agreement (CLA) before submitting your changes.
For other projects that don’t require a signed CLA, we ask that you include a line similar to the following as part of your pull request comments: “DCO 1.1 Signed-off-by: Random J Developer”. “DCO” stands for “Developer Certificate of Origin,” and refers to the same text used in the Linux Kernel community. By adding this simple comment, you tell the community that you wrote the code you are contributing, or you have the right to pass on the code that you are contributing.
Where can I find help if I need it?
Each project in Watson Data Lab includes a set of helpful links on the project page, including links to deploy the project on Bluemix and a link to the repo on GitHub. You can also find contact info for each of our team members via their individual GitHub profiles.
Communtity Guidelines
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
For more information on our community guidelines, please refer to: