Skip to content

Latest commit

 

History

History
40 lines (24 loc) · 3.84 KB

README.md

File metadata and controls

40 lines (24 loc) · 3.84 KB

One Boston Day

The source code for One Boston Day, the official site of the City of Boston's holiday, One Boston Day. One Boston Day is static site built with harpjs, gulp, sass, and browser sync.

One Boston Day is a special moment in our city. It’s a day we honor those we lost on April 15th, 2013 by being at our very best. Everyone participates in their own way. We’ve released the code for OneBostonDay.org in the public domain to give developers and designers like you the chance to get involved. We welcome and encourage your contributions to improve the website and our city. We look forward to sharing what we create together with the public.

— Mayor Martin J. Walsh

There’s a large, civic-minded ecosystem of software developers out there in Boston, and we’re hoping they’re willing to lend a hand and help One Boston Day grow, in order to bring our great designer/developer community together.

Contributions

If you're interested in helping One Boston Day, there are three ways to help. Be sure to checkout our Guide to Contributing.

Developers

Get started with our developer guide. Each contributor should fork the primary Boston.gov repo. All developers should then checkout a local copy of the develop branch to begin work.

Public domain

This project is in the worldwide public domain. As stated in LICENSE:

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.

Staying organized

All projects, open source or not, need some way to stay organized. Whether reporting a bug (check out the template), suggesting a feature another template, filing a pull request yay, templates, or even just seeing what's next in the queue, here are some ways we keep things clear on the Digital Team:

Use the templates