Revisions for Developers
| 84 | warren |
October 16, 2017 03:05
| over 6 years ago
Above: a diagram of our data model The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard: First-timers onlyIf this is your first time, and you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: If there are no issues available, please see https://github.com/publiclab/plots2/labels/help-wanted Activities[activities: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:
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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc, specifically https://publiclab.org/notes/warren/05-04-2017/google-summer-of-code-2017-and-a-call-for-community-mentors 2017 projects:
Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 83 | warren |
October 16, 2017 03:05
| over 6 years ago
Above: a diagram of our data model The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard: First-timers onlyIf this is your first time, and you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: If there are no issues available, please see https://github.com/publiclab/plots2/labels/help-wanted Activities[activities: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:
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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc, specifically https://publiclab.org/notes/warren/05-04-2017/google-summer-of-code-2017-and-a-call-for-community-mentors 2017 projects:
Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 82 | warren |
October 16, 2017 03:03
| over 6 years ago
Above: a diagram of our data model The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard: First-timers onlyIf this is your first time, and you'd like to quickly jump into an issue, see the following list for any available first-timers-only issues: https://jywarren.github.io/community-toolbox/examples/embed.html#l=first-timers-only&r=plots2&o=publiclab If there are no issues available, please see https://github.com/publiclab/plots2/labels/help-wanted Activities: software[activities: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:
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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc, specifically https://publiclab.org/notes/warren/05-04-2017/google-summer-of-code-2017-and-a-call-for-community-mentors 2017 projects:
Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 81 | liz |
June 28, 2017 13:23
| almost 7 years ago
Above: a diagram of our data model The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard:
Activities: software[activities: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:
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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc, specifically https://publiclab.org/notes/warren/05-04-2017/google-summer-of-code-2017-and-a-call-for-community-mentors 2017 projects:
Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 80 | liz |
January 03, 2017 22:45
| over 7 years ago
Above: a diagram of our data model The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard:
Activities: software[activities: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:
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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 79 | liz |
November 30, 2016 17:01
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard:
Activities: software[activities: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:
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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 78 | liz |
November 30, 2016 16:59
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard:
Activities: software[activities: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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitter |
Revert | |||||||||||||||||||||||||||||||
| 77 | liz |
November 30, 2016 16:41
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard:
Activities: software[activities: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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
|
Revert | |||||||||||||||||||||||||||||||
| 76 | liz |
November 30, 2016 16:37
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Subscribe at left: How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines, then visit our github dashboard:
Activities: software[activities: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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
|
Revert | |||||||||||||||||||||||||||||||
| 75 | liz |
November 30, 2016 16:36
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Subscribe at left: How to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines
Activities: software[activities: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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
|
Revert | |||||||||||||||||||||||||||||||
| 74 | liz |
November 02, 2016 19:12
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Activities: software[activities: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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
|
Revert | |||||||||||||||||||||||||||||||
| 73 | liz |
November 02, 2016 18:48
| over 7 years ago
The Public Lab Developers group is an open mailing list for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. Github has a really great tutorial on this, but we've reproduced the most basic workflow here: You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 72 | warren |
October 31, 2016 03:46
| over 7 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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 https://publiclab.org/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. Github has a really great tutorial on this, but we've reproduced the most basic workflow here: You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 71 | warren |
October 30, 2016 20:56
| over 7 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. It's also important that the bug or feature be relatively self-contained, so it's easier to tackle. Not every issue is a good fit for first-time coders. If you go the extra mile to prep your issue for first timers, consider tagging your issue with You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. Github has a really great tutorial on this, but we've reproduced the most basic workflow here: You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 70 | warren |
April 21, 2016 16:51
| about 8 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. It's also important that the bug or feature be relatively self-contained, so it's easier to tackle. Not every issue is a good fit for first-time coders. If you go the extra mile to prep your issue for first timers, consider tagging your issue with You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. Github has a really great tutorial on this, but we've reproduced the most basic workflow here: You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 69 | warren |
March 28, 2016 15:47
| about 8 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. It's also important that the bug or feature be relatively self-contained, so it's easier to tackle. Not every issue is a good fit for first-time coders. If you go the extra mile to prep your issue for first timers, consider tagging your issue with You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. Github has a really great tutorial on this, but we've reproduced the most basic workflow here: You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 68 | warren |
March 21, 2016 17:32
| about 8 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. It's also important that the bug or feature be relatively self-contained, so it's easier to tackle. Not every issue is a good fit for first-time coders. If you go the extra mile to prep your issue for first timers, consider tagging your issue with You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. Github has a really great tutorial on this, but we've reproduced the most basic workflow here: You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 67 | warren |
March 17, 2016 20:59
| about 8 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. It's also important that the bug or feature be relatively self-contained, so it's easier to tackle. Not every issue is a good fit for first-time coders. If you go the extra mile to prep your issue for first timers, consider tagging your issue with You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 66 | warren |
March 17, 2016 20:54
| about 8 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert | |||||||||||||||||||||||||||||||
| 65 | warren |
March 17, 2016 20:54
| about 8 years ago
The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own! Sign upHow to contributeWe are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members! Start by reading our contribution guidelines Public Lab Software
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: http://www.firsttimersonly.com/ http://www.charlotteis.co.uk/making-your-first-pull-request/ A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github https://guides.github.com/activities/contributing-to-open-source/ On our PublicLab.org GitHub repository, we've listed some "good for first timers" bugs to fix here: https://github.com/publiclab/plots2/labels/first-timers-only We also have a slightly larger list of easy-ish but small and self contained issues: https://github.com/publiclab/plots2/labels/help-wanted Google Summer of CodeLots of development on Public Lab software happens as part of the GSoC program, 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 http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc 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 contribtors, 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! Again, please look to this as a good example of a For first time contributors, another thing you can add, shown in that issue, is a checklist outlining each step they'll need to do. This can be really helpful to someone who hasn't contributed to open source code before. You can also take a look at this post on the Hoodie project for some tips about what makes a great issue description for new coding contributors. What if someone else created the issue, but you want to post a "tidied up" version with more clear documentation? Try creating a new issue and leaving a comment on the old one, something like "moving to #343 for a cleaner presentation of the issue". Then the old issue can be closed. Installation videosMapKnitterSimple installation with Cloud9Cloud9, at http://c9.io, can be used to set up a complete development environment, for free, in the cloud -- including Git and a test suite, so you can make changes and create pull requests. These instructions are for PublicLab.org, but there are similar instructions available for Spectral Workbench and MapKnitter (coming soon). Each is listed in that project's README file:
Really basic Github contributionThere is a way to contribute to Public Lab software without using a command line or having any special computer or setup, as long as your changes are simple -- this works best for just changes to text or HTML, not executable code. You'll need a Github account:
At this point, we'll see your pull request, provide feedback, test it out, and hopefully integrate it. Things may get more complex, but this is a great starting point. |
Revert |
