Public Lab software, including this website, is written collaboratively by a community of contrib...
Public Lab is an open community which collaboratively develops accessible, open source, Do-It-Yourself technologies for investigating local environmental health and justice issues.
| 84 CURRENT | ruthnwaiganjo |
May 20, 2021 11:37
| over 3 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of the various Public Lab software projects We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] ProjectsFor an in-depth overview of all PL software projects, see https://publiclab.org/software-overview
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 83 | ruthnwaiganjo |
May 20, 2021 11:35
| over 3 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of the various Public Lab software projects We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] ProjectsFor an in-depth overview of all PL software projects, see https://publiclab.org/software-overview
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 82 | ruthnwaiganjo |
May 20, 2021 11:18
| over 3 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of the various Public Lab software projects We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] ProjectsFor an in-depth overview of all PL software projects, see https://publiclab.org/software-overview
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 81 | warren |
November 24, 2020 20:47
| about 4 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of the various Public Lab software projects We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] ProjectsFor an in-depth overview of all PL software projects, see https://publiclab.org/software-overview
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 80 | warren |
September 22, 2020 18:39
| over 4 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of the various Public Lab software projects We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 79 | warren |
June 30, 2020 18:35
| over 4 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 78 | warren |
December 13, 2019 22:18
| about 5 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 77 | warren |
July 03, 2019 16:23
| over 5 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 76 | warren |
January 04, 2019 19:22
| almost 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 75 | warren |
January 04, 2019 19:20
| almost 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 74 | warren |
October 02, 2018 13:25
| about 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: https://code.publiclab.org#r=all ResourcesGetting started
Setup
Pull requests
Git
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 73 | warren |
October 01, 2018 20:18
| about 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 72 | warren |
September 21, 2018 20:33
| over 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page. If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 71 | gauravano |
June 13, 2018 17:05
| over 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our Code of Conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 70 | warren |
June 03, 2018 23:08
| over 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our [Code of Conduct](/conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 69 | warren |
June 03, 2018 23:06
| over 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our [Code of Conduct](/conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Summer of Code Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. |
Revert | ||||||||||||||||||||||||||||||||||
| 68 | warren |
June 03, 2018 23:05
| over 6 years ago
Public Lab software, including this website, is written collaboratively by a community of contributors. Above: a diagram of this website's data model We're so happy to meet you! This page is to welcome new contributors. We especially welcome contributions from people from groups under-represented in free and open source software! Our community aspires to be a respectful place. Please read and abide by our [Code of Conduct](/conduct. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. MapKnitter |
Revert | ||||||||||||||||||||||||||||||||||
| 67 | warren |
May 14, 2018 21:48
| over 6 years ago
Above: a diagram of our data model Public Lab software, including this website, is written collaboratively by a community of contributors. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! MiscellaneousNote that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution. MapKnitter |
Revert | ||||||||||||||||||||||||||||||||||
| 66 | warren |
March 17, 2018 11:39
| almost 7 years ago
Above: a diagram of our data model Public Lab software, including this website, is written collaboratively by a community of contributors. How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! Installation videosMapKnitter |
Revert | ||||||||||||||||||||||||||||||||||
| 65 | warren |
March 17, 2018 11:36
| almost 7 years ago
Above: a diagram of our data model The Public Lab Developers group is open to any Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! See what's happening:https://github.com/publiclab/plots2/pulse/monthly How to contributeWe are actively seeking contributors, so please visit our welcome page and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! First-timers onlyIf this is your first time, welcome! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab. We especially welcome contributions from people from groups underrepresented in free and open source software! Please see our welcome page If you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: Read more about our software outreach work here! Activities[activities:software] Questions[questions:software] Public Lab Software projects
Public Lab is on Github at: https://github.com/publiclab First time contributorsNew to open source/free software? Here are some resources to get you started: Our welcome page for newcomers looking to get involved in coding: http://publiclab.github.io/community-toolbox
Resources
Contributing for non-codersNot interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it? You can still help out; in fact, helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself. When creating or editing an issue, try to:
Once an issue is well documented, we can tag it with Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the plots-dev discussion list to get the word out. Preparing issues for newcomersRelated to the above, even if you are a coder, we need help "rolling out the red carpet" (as the Hoodie project calls it) for new contributors, to grow our contributor base. The steps in Contributing for non-coders are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general! Learn more about how to make a good ReviewersMentoring for Summer of Code programs has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
Some specific things you can do:
Here are some guides to different ways to help others contribute: Activities[activities:soc] Summer of CodeLots of development on Public Lab software happens as part of the Rails Girls Summer of Code and Google Summer of Code programs, that latter supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program. Read more at our Summer of Code page! Installation videosMapKnitter |
Revert |