Public Lab Wiki documentation

(This template is for students applying to summer code programs with Public Lab. Use this link to start writing a post: https://publiclab.org/post?n=899&tags=soc,soc-2018,soc-2018-proposals You can delete this line once you've started filling it out.)

About me

Tell us about yourself!

Affiliation (organization/school, if any)

Location: (generally where you are)

Project description

Here, you don't have to have a complete proposal when you begin. Just tell us some of your ideas and we'll help you refine it into a full proposal gradually!

Abstract/summary (<20 words):

Problem

What problem(s) does your project solve?

Timeline/milestones

Break your project up into small projects -- one per week!

See this page for guidance on breaking your plan up into small, self-contained parts: https://publiclab.org/notes/warren/01-18-2018/software-outreach-modularity-is-great-for-collaboration

Needs

What resources will you need: people, documentation, literature, sample data, hardware if applicable

First-time contribution

_Have you looked over our welcome page and are you familiar with how to make your first contribution? Have you already made it? We're eager to see that you've had a good experience making a small initial contribution to our site. Please check out our welcoming page: _

https://publiclab.github.io/community-toolbox/#r=all

And paste in links to your initial contributions here so we can see!

Experience

Tell us how you've learned about writing software; what languages you've been learning, if you've worked on other projects, links to GitHub or other code repositories or samples.

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Passion

What about our projects, and Public Lab, interests you? What are you passionate about? Open science, environmental justice?

Audience

Whom do you want your work to help? We especially appreciate proposals which make technologies and techniques more welcoming and friendly to those who've often been excluded.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time summer job? Tell us how you'll structure your schedule from day to day!

(This template is for students applying to summer code programs with Public Lab. Use this link to start writing a post: https://publiclab.org/post?n=899&tags=gsoc,gsoc-2017-proposals You can delete this line once you've started filling it out.)

About me

Tell us about yourself!

Affiliation (organization/school, if any)

Location: (generally where you are)

Project description

Here, you don't have to have a complete proposal when you begin. Just tell us some of your ideas and we'll help you refine it into a full proposal gradually!

Abstract/summary (<20 words):

Problem

What problem does your project solve?

Timeline/milestones

Break your project up into small projects -- one per week!

Needs

What resources will you need: people, documentation, literature, sample data, hardware if applicable

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Tell us how you've learned about writing software; what languages you've been learning, if you've worked on other projects, links to GitHub or other code repositories or samples.

Have you looked over our welcome page and are you familiar with how to make your first contribution? Have you already?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Passion

What about our projects, and Public Lab, interests you? What are you passionate about? Open science, environmental justice?

Audience

Whom do you want your work to help? We especially appreciate proposals which make technologies and techniques more welcoming and friendly to those who've often been excluded.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time summer job? Tell us how you'll structure your schedule from day to day!

(This template is for students applying to summer code programs with Public Lab. Use this link to start writing a post: https://publiclab.org/post?n=899 You can delete this line once you've started filling it out.)

About me

Tell us about yourself!

Affiliation (organization/school, if any)

Location: (generally where you are)

Project description

Here, you don't have to have a complete proposal when you begin. Just tell us some of your ideas and we'll help you refine it into a full proposal gradually!

Abstract/summary (<20 words):

Problem

What problem does your project solve?

Timeline/milestones

Break your project up into small projects -- one per week!

Needs

What resources will you need: people, documentation, literature, sample data, hardware if applicable

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Tell us how you've learned about writing software; what languages you've been learning, if you've worked on other projects, links to GitHub or other code repositories or samples.

Have you looked over our welcome page and are you familiar with how to make your first contribution? Have you already?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Passion

What about our projects, and Public Lab, interests you? What are you passionate about? Open science, environmental justice?

Audience

Whom do you want your work to help? We especially appreciate proposals which make technologies and techniques more welcoming and friendly to those who've often been excluded.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time summer job? Tell us how you'll structure your schedule from day to day!

(This template is for students applying to summer code programs with Public Lab. Use this link to start writing a post: https://publiclab.org/post?n=899 You can delete this line once you've started filling it out.)

About me

Tell us about yourself!

Affiliation (organization/school, if any)

Location: (generally where you are)

Project description

Here, you don't have to have a complete proposal when you begin. Just tell us some of your ideas and we'll help you refine it into a full proposal gradually!

Abstract/summary (<20 words):

Problem

What problem does your project solve?

Timeline/milestones

Break your project up into small projects -- one per week!

Needs

What resources will you need: people, documentation, literature, sample data, hardware if applicable

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Tell us how you've learned about writing software; what languages you've been learning, if you've worked on other projects, links to GitHub or other code repositories or samples.

Have you looked over our welcome page and are you familiar with how to make your first contribution? Have you already?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Passion

What about our projects, and Public Lab, interests you? What are you passionate about? Open science, environmental justice?

Audience

Whom do you want your work to help? We especially appreciate proposals which make technologies and techniques more welcoming and friendly to those who've often been excluded.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time summer job? Tell us how you'll structure your schedule from day to day!

(This template is for students applying to the GSoC program with Public Lab.)

About me

Tell us about yourself!

Affiliation (organization/school, if any)

Location: (generally where you are)

Project description

Here, you don't have to have a complete proposal when you begin. Just tell us some of your ideas and we'll help you refine it into a full proposal gradually!

Abstract/summary (<20 words):

Problem

What problem does your project solve?

Timeline/milestones

Break your project up into small projects -- one per week!

Needs

What resources will you need: people, documentation, literature, sample data, hardware if applicable

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Tell us how you've learned about writing software; what languages you've been learning, if you've worked on other projects, links to GitHub or other code repositories or samples.

Have you looked over our welcome page and are you familiar with how to make your first contribution? Have you already?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Passion

What about our projects, and Public Lab, interests you? What are you passionate about? Open science, environmental justice?

Audience

Whom do you want your work to help? We especially appreciate proposals which make technologies and techniques more welcoming and friendly to those who've often been excluded.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time summer job? Tell us how you'll structure your schedule from day to day!

(This template is for students applying to the GSoC program with Public Lab.)

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to organizers@publiclab.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples. Have you read the Contributor Guidelines at https://publiclab.org/wiki/contributing-to-public-lab-software and are you comfortable submitting pull requests?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

(This template is for students applying to the GSoC program with Public Lab.)

View the markup here to copy into your post: https://publiclab.org/notes/raw/899

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to organizers@publiclab.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples. Have you read the Contributor Guidelines at https://publiclab.org/wiki/contributing-to-public-lab-software and are you comfortable submitting pull requests?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

This template is for students applying to the GSoC program with Public Lab. Please copy it in order to make your own proposals.

View the markup here to copy into your post: https://publiclab.org/notes/raw/899

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to organizers@publiclab.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Setup

Have you forked the relevant codebases? Installed them in a dev environment such as Cloud9.io? Need help doing so? Please provide a link to each of the above.

Experience

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples. Have you read the Contributor Guidelines at https://publiclab.org/wiki/contributing-to-public-lab-software and are you comfortable submitting pull requests?

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

This template is for students applying to the GSoC program with Public Lab. Please copy it in order to make your own proposals.

View the markup here to copy into your post: https://publiclab.org/notes/raw/899

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to organizers@publiclab.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Experience

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

This template is for students applying to the GSoC program with Public Lab. Please copy it in order to make your own proposals.

View the markup here to copy into your post: https://publiclab.org/notes/raw/899

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to organizers@publiclaboratory.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Experience

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

This template is for students applying to the GSoC program with Public Laboratory. Please copy it in order to make your own proposals.

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to organizers@publiclaboratory.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Experience:

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

This template is for students applying to the GSoC program with Public Laboratory. Please copy it in order to make your own proposals.

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone: (if you prefer not to post it here, please email it to team@publiclaboratory.org with a link to your application.)

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Experience:

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

This template is for students applying to the GSoC program with Public Laboratory. Please copy it in order to make your own proposals.

Template

Name:

Affiliation (school/degree)

Location (where you are):

Email:

Phone:

Project(s) you're working on or want to, i.e. Spectral Workbench or MapKnitter:

Project title -- the title of YOUR proposed project:

Project description

• Abstract/summary (<20 words):
• Describe the need your project fulfills:
• How will your project meet this need:
• Timeline/milestones:
• What broader goal is your project working towards?
• What resources will you need: people, documentation, literature, sample data, hardware if applicable:

Experience:

Describe your technical background; what languages you use, what projects you've contributed to before, links to GitHub or other code repositories or samples

Teamwork

Describe teams you've worked with before, whether open or closed source, and in what capacity you participated. Cite examples of how you were self-motivated and self-sufficient.

Expertise

Would you describe yourself as especially good at or interested in some aspect of coding or problem solving, or open source science? Provide examples and links. Are you particularly suited to this proposed project?

Interest

Do you have prior interest in or work towards open science or environmental justice goals?

Audience

Whom will your work serve? Lay users, other programmers, non-technical people or nerds? While exploring advanced techniques is great, we especially appreciate proposals which make technologies and techniques more legible and user-friendly to non-technical users.

Context

What motivates you to do the proposed work? Do you also have coursework or degree related reasons for pursuing it? This wouldn't necessarily be a bad thing - if you are for example looking to explore work related to a thesis topic.

Ongoing involvement

Explain how you intend to continue being an active member of your project and/or Public Laboratory AFTER the summer is over.

Commitment

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?