decidim-bulletin_board 0.13.0 → 0.16.0

data/CHANGELOG.md

@@ -1,230 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## Unreleased
-
-## [0.13.0] - 2021-02-23
-
-## [0.12.1] - 2021-02-22
-
-### Changed
-
-- The `VoteComponent` event names have been changed to more suitable ones.
-
-## [0.12.0] - 2021-02-19
-
-### Added
-
-- The `Voter` returns the ballot hash after encrpyting the plain vote and before auditing or casting it
-
-### Changed
-
-- The `create_election` command now expects objects representing the parts public keys.
-
-## [0.11.0] - 2021-02-18
-
-### Changed
-
-- Changed the name of some settings\* to improve the readability of the code:
-  - BB settings: `bulletin_board_server`\* and `bulletin_board_public_key`\*.
-  - Authority settings: `authority_api_key`\*, `authority_name` and `authority_private_key`\*.
-  - Elections settings: `scheme_name`, `number_of_trustees` and `quorum`.
-- `KeyCeremonyComponent` and `TallyComponent` now accepts a `trusteeWrapperAdapter` object.
-- The `processMessage` method from the `TrusteeWrapperAdapter` now accepts a `messageType` instead of a `messageIdentifier`.
-
-### Removed
-
-- The `TrusteeWrapper` for the "dummy" voting scheme has been removed from the project.
-
-### Added
-
-- The `TrusteeWrapperAdapter` abstract class can be used to implement any voting scheme wrapper adapter.
-
-## [0.10.1] - 2021-02-15
-
-### Fixed
-
-- The `TallyComponent` now uses the `key_ceremony` messages as well.
-
-## [0.10.0] - 2021-02-12
-
-## Added
-
-- A command to get decoded election results.
-- The (Bulletin Board) server public key is now included in the gem configuration.
-- The option to `audit` a vote.
-
-## Changed
-
-- The `get_election_log_entries_by_type` command got renamed to `get_election_results`.
-- The `create_election` command now receives all the information needed in a simple hash and builds the message to add to the election log. It only needs seven main keys: `trustees`, `default_locale`, `title`, `start_date`, `end_date`, `questions` and `answers`.
-- The `scheme` setting was replaced by the `scheme_name` and `quorum` settings.
-
-## [0.9.2] - 2021-02-02
-
-## [0.9.1] - 2021-02-02
-
-## Added
-
-- The `VoteComponent` has been added. It will be used as a glue code between the vote and the UI.
-- The ruby client now includes the `get_election_log_entries_by_types` method to get the election log entries filtered by type.
-
-## [0.9.0] - 2021-02-01
-
-## Changed
-
-- The `open_ballot_box` and `close_ballot_box` are now called `start_vote` and `end_vote` and return a pending message.
-- All the client operations yield the `message_id` before sending the request to the Bulletin Board.
-
-## Added
-
-- `start_key_ceremony` method to the `Decidim::BulletinBoard::Client`.
-- The `IdentificationKeys` class has been added to the JS library.
-- The `TallyComponent` has been added. It will be used as a glue code between the tally and the UI.
-
-## [0.8.2] - 2021-01-28
-
-## Changed
-
-- `encrypt` in `VoterWrapperDummy` has a TimeOut of 500ms.
-
-## [0.8.0] - 2021-01-27
-
-## Changed
-
-- `getPendingMessage` can get queried by `messageId` and by `id`.
-- `get_status` renamed to `get_election_status` in the `Decidim::BulletinBoard::Client`.
-
-## Added
-
-- `getPendingMessageStatus` method to the `Decidim::BulletinBoard::Client`.
-- `waitForPendingMessageToBeProcessed` method to the Voter class.
-- The `KeyCeremonyComponent` has been added. It will be used as a glue code between the key ceremony process and the UI.
-
-## [0.7.0] - 2021-01-26
-
-## Changed
-
-- The `Trustee` class now uses the `Election` class to interact with the log entries.
-- The `Trustee` class handles everything now when performing both the key ceremony and the tally process.
-- The `Trustee` class now includes a `setupKeyCeremony` generator function that must be called before starting the key ceremony process.
-- `checkRestoreNeeded` method has been renamed to `needsToBeRestored` for both the `Trustee` and the `TrusteeWrapper`.
-
-## Added
-
-- `start_tally` method to the `Decidim::BulletinBoard::Client`.
-- `publish_results` method to the `Decidim::BulletinBoard::Client`.
-- `Election` class in the JS package to handle the election state. An instance of this class will be used by the key ceremony and the trustee to check anything related to log entries.
-- The `Trustee` class now has a `teardown` method that is called automatically to clean a few things. It can be called early to avoid memory leaks if needed.
-- The `EventManager` class now handles the `events` stream and exports some useful constants.
-
-## Removed
-
-- The `KeyCeremony` class has been removed.
-- The `Trustee` backup method has been removed because it doesn't belong to the public API anymore.
-
-## [0.6.1] - 2021-01-12
-
-### Changed
-
-- Production file now is called `decidim-bulletin_board.js` and development file is called `decidim-bulletin_board.dev.js`.
-
-### Removed
-
-- The GraphQL client doesn't use subscriptions anymore.
-
-## [0.6.0] - 2021-01-12
-
-### Changed
-
-- Updated the app schema definition with the partial log entries list retrieval
-- Gem is an engine, the js assets can be imported in Decidim.
-
-## [0.5.3] - 2020-12-20
-
-### Fixed
-
-- Fix the schema definition folder when used inside an app
-
-## [0.5.2] - 2020-12-20
-
-### Fixed
-
-- Include the schema definition within the gem to avoid extra trips to the server
-
-## [0.5.1] - 2020-12-19
-
-### Fixed
-
-- Include the missing `close_ballot_box` method from the 0.4.0 release.
-- Fixes for the client methods
-
-## [0.5.0] - 2020-12-19
-
-### Changed
-
-- Renamed `setup_election` to `create_election` and moved `election_id` from the `election_data` to a separate argument.
-
-### Fixed
-
-- Include the missing `open_ballot_box` methods from the 0.4.0 release.
-- Added missing namespace on the seed task
-
-## [0.4.0] - 2020-12-18
-
-### Added
-
-- `content_hash` field for the `LogEntry` records with the hash of the `content` field, if included in the message.
-- `Command` base class for all the classes representing GraphQL queries or mutations sent to the Bulletin Board.
-- `open_ballot_box` and `close_ballot_box` methods to the `Decidim::BulletinBoard::Client`.
-
-### Changed
-
-- New format for the messages: `iat`, `message_id` and Bulletin Board fields in the root message, and `content` for the Voting Scheme messages.
-- Improved consistency between methods included by `Decidim::BulletinBoard::Client`.
-
-## [0.3.1] - 2020-12-10
-
-### Fixed
-
-- Uses the correct private key in the `sign_data` method.
-
-## [0.3.0] - 2020-12-10
-
-### Added
-
-- `Decidim::BulletinBoard::Authority` namespace that includes commands and forms to get the status of an election.
-
-### Changed
-
-- `Decidim::BulletinBoard::Client` now includes a `get_status` method to get the election status using the `Authority` namespace.
-
-### Fixed
-
-- `Decidim::BulletinBoard::Voter::CastVote` command uses the `encrypted_vote` as a `String` and not as a `Hash`.
-
-## [0.2.0] - 2020-12-08
-
-### Added
-
-- `Decidim::BulletinBoard::Voter` namespace that includes commands and forms to perform the cast vote action.
-
-### Changed
-
-- `Decidim::BulletinBoard::Client` now includes a `cast_vote` method to cast a vote using the `Voter` namespace.
-
-## [0.1.0] - 2020-12-07
-
-### Added
-
-- `Decidim::BulletinBoard::Client` class totally configurable using `ActiveSupport::Configurable`
-- The client now includes a `setup_election` method that creates the election in the bulletin board.
-
-[unreleased]: https://github.com/decidim/decidim-bulletin-board/compare/v0.3.0...HEAD
-[0.3.0]: https://github.com/decidim/decidim-bulletin-board/compare/v0.2.0...v0.3.0
-[0.2.0]: https://github.com/decidim/decidim-bulletin-board/compare/v0.1.0...v0.2.0
-[0.1.0]: https://github.com/decidim/decidim-bulletin-board/releases/tag/v0.1.0

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# 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, gender identity and expression, level of experience,
-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 david@codegram.com. 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://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/

data/bin/release

@@ -1,10 +0,0 @@
-#!/bin/bash
-
-cd ../decidim-bulletin_board-app && \
-bundle install && \
-npm run release && \
-cd ../decidim-bulletin_board-ruby && \
-bundle install && \
-git add .. && \
-git commit --amend --no-edit && \
-bundle exec rake release