Merge pull request #33 from 10up/release/0.4.0

Release 0.4.0

CHANGELOG.md

@@ -0,0 +1,53 @@
+# Changelog
+
+All notable changes to this project will be documented in this file, per [the Keep a Changelog standard](http://keepachangelog.com/), and will adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased] - TBD
+
+## [0.4.0] - 2020-08-06
+### Added
+- Added `CustomEvent` and associated IE11 polyfill to listen for changes outside of the plugin (props [@jaredrethman](https://github.com/jaredrethman) via [#32](https://github.com/10up/post-finder/pull/32))
+- Documentation updates (props [@jeffpaul](https://github.com/jeffpaul) via [#33](https://github.com/10up/post-finder/pull/33))
+
+### Changed
+- Moved saved connections above the search field (props [@gthayer](https://github.com/gthayer) via [#30](https://github.com/10up/post-finder/pull/30))
+- Only loading the plugin if on WordPress context (props [@nicholasio](https://github.com/nicholasio) via [#29](https://github.com/10up/post-finder/pull/29))
+- Update `grunt-sass` package version to v2.1 (props [@jaredrethman](https://github.com/jaredrethman) via [#32](https://github.com/10up/post-finder/pull/32))
+- Versioning to follow SemVer (props [@daveross](https://github.com/daveross) via [#27](https://github.com/10up/post-finder/pull/27))
+
+## [0.3.0] - 2017-07-05
+### Added
+- Pagination to search results (props [@dkotter](https://github.com/dkotter) via [#21](https://github.com/10up/post-finder/pull/21))
+- Allow the option to turn off the display of the Recent Posts dropdown (props [@dkotter](https://github.com/dkotter) via [#22](https://github.com/10up/post-finder/pull/22))
+- Use Grunt for compiling (props [@dkotter](https://github.com/dkotter) via [#18](https://github.com/10up/post-finder/pull/18))
+- Internationalization support (props [@dkotter](https://github.com/dkotter) via [#19](https://github.com/10up/post-finder/pull/19))
+
+### Changed
+- Localization updates (props [@eugene-manuilov](https://github.com/eugene-manuilov) via [#24](https://github.com/10up/post-finder/pull/24))
+- Adjust styling to better match WordPress (props [@dkotter](https://github.com/dkotter) via [#17](https://github.com/10up/post-finder/pull/17))
+- Code formatting and cosmetic fixes (props [@dkotter](https://github.com/dkotter), [@eugene-manuilov](https://github.com/eugene-manuilov) via [#20](https://github.com/10up/post-finder/pull/20), [#25](https://github.com/10up/post-finder/pull/25))
+- `composer.json` properties updates (props [@eugene-manuilov](https://github.com/eugene-manuilov) via [#23](https://github.com/10up/post-finder/pull/23))
+
+## [0.2.0] - 2017-07-05
+### Added
+- Ability to add posts when none exist yet
+- Proper namespacing, serialization, sanitization
+- Support for limits, query args, multiple post types, template filtering
+- Select works on change or click
+- `composer.json` file
+
+### Changed
+- Major updates to CSS and styles
+- Overlay markup, JS improvements, issue with JS and CSS paths
+
+### Fixed
+- Undefined variable reference, form submission denial
+
+## [0.1.0] - 2013-08-07
+- Initial release of Post Finder plugin.
+
+[Unreleased]: https://github.com/10up/post-finder/compare/trunk...develop
+[0.4.0]: https://github.com/10up/post-finder/compare/0.3.0...0.4.0
+[0.3.0]: https://github.com/10up/post-finder/compare/0.2.0...0.3.0
+[0.2.0]: https://github.com/10up/post-finder/compare/cac1515...0.2.0
+[0.1.0]: https://github.com/10up/post-finder/tree/cac1515fd654ac1bbb2c5528bf8f967417f1d473

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing and Maintaining
+
+First, thank you for taking the time to contribute!
+
+The following is a set of guidelines for contributors as well as information and instructions around our maintenance process.  The two are closely tied together in terms of how we all work together and set expectations, so while you may not need to know everything in here to submit an issue or pull request, it's best to keep them in the same document.
+
+## Ways to contribute
+
+Contributing isn't just writing code - it's anything that improves the project.  All contributions are managed right here on GitHub. Here are some ways you can help:
+
+### Reporting bugs
+
+If you're running into an issue with the plugin, please take a look through [existing issues](https://github.com/10up/post-finder/issues) and [open a new one](https://github.com/10up/post-finder/issues/new) if needed.  If you're able, include steps to reproduce, environment information, and screenshots/screencasts as relevant.
+
+### Suggesting enhancements
+
+New features and enhancements are also managed via [issues](https://github.com/10up/post-finder/issues).
+
+### Pull requests
+
+Pull requests represent a proposed solution to a specified problem.  They should always reference an issue that describes the problem and contains discussion about the problem itself.  Discussion on pull requests should be limited to the pull request itself, i.e. code review.
+
+For more on how 10up writes and manages code, check out our [10up Engineering Best Practices](https://10up.github.io/Engineering-Best-Practices/).
+
+## Workflow
+
+The `develop` branch is the development branch which means it contains the next version to be released.  `trunk` contains the latest released version as reflected in the WordPress.org plugin repository.  Always work on the `develop` branch and open up PRs against `develop`.
+
+## Release instructions
+
+1. Branch: Starting from `develop`, cut a release branch named `release/X.Y.Z` for your changes.
+2. Version bump: Bump the version number in `languages/post-finder.pot`, `post-finder.php`, and `package.json` if it does not already reflect the version being released.  Update both the plugin "Version:" property and the plugin `POST_FINDER_VERSION` constant in `post-finder.php`.
+3. Changelog: Add/update the changelog in `CHANGELOG.md`.
+4. Props: update `CREDITS.md` with any new contributors, confirm maintainers are accurate.
+5. Readme updates: Make any other `README.md` changes as necessary.
+6. Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the pull request), then do the same for `develop` into `trunk` (`git checkout trunk && git merge --no-ff develop`). `trunk` contains the stable development version.
+7. Push: Push your `trunk` branch to GitHub (e.g. `git push origin trunk`).
+8. Release: Create a [new release](https://github.com/10up/post-finder/releases/new), naming the tag and the release with the new version number, and targeting the `trunk` branch. Paste the changelog from `CHANGELOG.md` into the body of the release and include a link to the [closed issues on the milestone](https://github.com/10up/post-finder/milestone/3?closed=1).
+9. Close the milestone: Edit the [X.Y.Z milestone](https://github.com/10up/post-finder/milestone/#) with release date (in the `Due date (optional)` field) and link to GitHub release (in the `Description` field), then close the milestone.
+10. Punt incomplete items: If any open issues or PRs which were milestoned for `X.Y.Z` do not make it into the release, update their milestone to `X+1.0.0`, `X.Y+1.0`, `X.Y.Z+1`, or `Future Release`

CREDITS.md

@@ -0,0 +1,19 @@
+The following acknowledges the Maintainers for this repository, those who have Contributed to this repository (via bug reports, code, design, ideas, project management, translation, testing, etc.), and any Libraries utilized.
+
+## Maintainers
+
+The following individuals are responsible for curating the list of issues, responding to pull requests, and ensuring regular releases happen.
+
+[Nícholas André (@nicholasio)](https://github.com/nicholasio), [Eugene Manuilov (@eugene-manuilov)](https://github.com/eugene-manuilov), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul).
+
+## Contributors
+
+Thank you to all the people who have already contributed to this repository via bug reports, code, design, ideas, project management, translation, testing, etc.
+
+[@micahwave](https://github.com/micahwave), [John Troynousky (@jtroynousky)](https://github.com/jtroynousky), [Joseph Chagan (@lupos)](https://github.com/lupos), [Helen Hou-Sandi (@helen)](https://github.com/helen), [Chris Marslender (@cmmarslender)](https://github.com/cmmarslender), [John Eckman (@jeckman)](https://github.com/jeckman), [Matt Gross (@mattonomics)](https://github.com/mattonomics), [Steve Grunwell (@stevegrunwell)](https://github.com/stevegrunwell), [Joey Blake (@joeyblake)](https://github.com/joeyblake), [Michael Phillips (@mphillips)](https://github.com/mphillips), [Adam Silverstein (@adamsilverstein)](https://github.com/adamsilverstein), [Ayebare (@ayebare)](https://github.com/ayebare), [Ryan Welcher (@ryanwelcher)](https://github.com/ryanwelcher), [Darin Kotter (@dkotter)](https://github.com/dkotter), [Eugene Manuilov (@eugene-manuilov)](https://github.com/eugene-manuilov), [Dave Ross (@daveross)](https://github.com/daveross), [Nícholas André (@nicholasio)](https://github.com/nicholasio), [Gary Thayer (@gthayer)](https://github.com/gthayer), [Jared Rethman (@jaredrethman)](https://github.com/jaredrethman), [Jeffrey Paul (@jeffpaul)](https://github.com/jeffpaul), [Tyler Cherpak (@tylercherpak)](https://github.com/tylercherpak).
+
+## Libraries
+
+The following software libraries are utilized in this repository.
+
+Forked from [Post Finder](https://github.com/micahwave/post-finder) by [@micahwave](https://github.com/micahwave).