text:
> [Go to French version](/fr/Règlements/Décrets,%20ordonnances%20et%20règlements%20statutaires/2006/254.md)

# First Nations Oil and Gas and Moneys Management Voting Regulations

**SOR/2006-254**

Enabling authorities:
- [FIRST NATIONS OIL AND GAS AND MONEYS MANAGEMENT ACT](/en/Acts/Statutes%20of%20Canada/2005/c.%2048.md)

Date registered: 19 October 2006

----------

Her Excellency the Governor General in Council, on the recommendation of the Minister of Indian Affairs and Northern Development, pursuant to paragraph 62(a) of the [First Nations Oil and Gas and Moneys Management Act](/en/Acts/Statutes%20of%20Canada/2005/c.%2048.md)[a], hereby makes the annexed First Nations Oil and Gas and Moneys Management Voting Regulations.

a: S.C. 2005, c. 48

## Interpretation

**Definitions**

**1** The following definitions apply in these Regulations.

***Act*** means the [First Nations Oil and Gas and Moneys Management Act](/en/Acts/Statutes%20of%20Canada/2005/c.%2048.md). (*Loi*)

***Assistant Deputy Minister*** means the Assistant Deputy Minister, Lands and Trusts Services, Department of Indian Affairs and Northern Development. (*sous-ministre adjoint*)

***deputy electoral officer*** means a person so designated by the electoral officer under subsection 3(2) for the purpose of a vote. (*président du scrutin*)

***electoral officer*** means the person so designated by the council of a first nation under paragraph 3(1)(a) for the purpose of a vote. (*président d’élection*)

***eligible voter***[Repealed, SOR/2009-150, s. 1]

***first nation membership number*** means the number assigned to a first nation member on the Band List of the first nation. (*numéro de membre de la première nation*)

***legal adviser*** means any person qualified, in accordance with the laws of a province, to give legal advice. (*conseiller juridique*)

***mail-in ballot*** means a ballot delivered or mailed in accordance with section 7. (*bulletin de vote postal*)

***registry number*** means the number assigned to a person registered under section 5 of the [Indian Act](/en/Acts/Revised%20Statutes%20of%20Canada/I/I-5.md). (*numéro de registre*)

***reserve***, in respect of a vote, means a reserve of the first nation that is conducting the vote. (*réserve*)

***voter declaration form*** means a form that, when completed, sets out the information required by section 8. (*formulaire de déclaration de l’électeur*)
> SOR/2009-150, s. 1.

## Application

**Vote under s. 17 or 18 of the Act**

**2** These Regulations apply to a vote held under section 17 or 18 of the Act.

## Duties

**Duties of council**

**3**

- **(1)** The council of a first nation that intends to conduct a vote must
	- **(a)** designate a person to be the electoral officer for the purpose of the vote; and
	- **(b)** forward a written resolution to the Minister notifying the Minister of its intention to hold the vote and identifying the electoral officer.

**Designation of deputy electoral officer**

- **(2)** The electoral officer must designate one or more persons to be deputy electoral officers for the purpose of the vote.

**Duties of officers**

- **(3)** The electoral officer and the deputy electoral officers must
	- **(a)** supervise the conduct of the vote in accordance with these Regulations;
	- **(b)** act with fairness and impartiality in the administration of these Regulations; and
	- **(c)** perform the duties and functions that are necessary for the administration of these Regulations.

## The Question for the Vote

**Content of the question**

**4** The question to be put to the eligible voters is set out
- **(a)** in Part 1 of the schedule, in the case of the ratification of an oil and gas code and a financial code referred to in section 10 of the Act and the approval of the transfer to a first nation of the management and regulation of oil and gas exploration and exploitation;
- **(b)** in Part 2 of the schedule, in the case of the ratification of a financial code referred to in section 11 of the Act and the approval of the payment of moneys to a first nation in accordance with the code; and
- **(c)** in Part 3 of the schedule, in the case of a single vote on the ratification of an oil and gas code and a financial code referred to in section 10 of the Act, the approval of the transfer to a first nation of the management and regulation of oil and gas exploration and exploitation, the ratification of a financial code referred to in section 11 of the Act and the approval of the payment of moneys to the first nation in accordance with the code.

## Voters List

**Duty to provide names**

**5**

- **(1)** At least 49 days before the day on which a vote is to be held, a list of all eligible voters must be provided to the electoral officer
	- **(a)** by the first nation, if the first nation has assumed control of its own membership under section 10 of the [Indian Act](/en/Acts/Revised%20Statutes%20of%20Canada/I/I-5.md); and
	- **(b)** by the Registrar, if the Band List of the first nation is maintained in the Department of Indian Affairs and Northern Development under section 11 of the [Indian Act](/en/Acts/Revised%20Statutes%20of%20Canada/I/I-5.md).

**Content of list**

- **(2)** A voters list must set out
	- **(a)** the names of all eligible voters, in alphabetical order; and
	- **(b)** the first nation membership number or registry number of each eligible voter or, if the eligible voter does not have a first nation membership number or registry number, the date of birth of the eligible voter.

**Confirmation of name on list**

- **(3)** On request, the electoral officer or a deputy electoral officer must confirm whether the name of a person is on the voters list.

**Revision of list**

- **(4)** The electoral officer must revise the voters list if it is demonstrated that
	- **(a)** the name of an eligible voter has been omitted from the list;
	- **(b)** the name of an eligible voter is incorrectly set out on the list; or
	- **(c)** the name of a person not qualified to vote is included on the list.

**Proof required for revision**

- **(5)** For the purpose of subsection (4), a person may demonstrate that
	- **(a)** the name of an eligible voter has been omitted from, or incorrectly set out on, the voters list by presenting to the electoral officer evidence from the Registrar or from the first nation that the eligible voter is on the Band List and has reached the eligible age for participation in the vote; or
	- **(b)** the name of a person not qualified to vote has been included on the voters list by presenting to the electoral officer evidence that the person is not on the Band List or has not reached the eligible age for participation in the vote.

## Addresses of Eligible Voters

**Duty to provide addresses**

**6** At least 49 days before the day on which a vote is to be held, the latest known addresses, if any, of the eligible voters who do not reside on the reserve must be provided to the electoral officer
- **(a)** by the first nation, if the first nation has assumed control of its own membership under section 10 of the [Indian Act](/en/Acts/Revised%20Statutes%20of%20Canada/I/I-5.md); and
- **(b)** by the Registrar, if the Band List of the first nation is maintained in the Department of Indian Affairs and Northern Development under section 11 of the [Indian Act](/en/Acts/Revised%20Statutes%20of%20Canada/I/I-5.md).

## Notification of Vote

**Duties of officers**

**7**

- **(1)** On the earlier of 14 days before the day on which the information meeting for a vote is to be held and 42 days before the day of the vote, the electoral officer or a deputy electoral officer must
	- **(a)** post a notice of the vote and a list of the eligible voters in at least one conspicuous place on the reserve;
	- **(b)** mail or deliver to every eligible voter of the first nation who does not reside on the reserve and for whom an address has been provided
		- **(i)** a notice of the vote,
		- **(ii)** a mail-in ballot, initialled on the back by the electoral officer or a deputy electoral officer,
		- **(iii)** an outer, postage-paid return envelope, pre-addressed to the electoral officer,
		- **(iv)** a second, inner envelope marked “Ballot” for insertion of the completed ballot,
		- **(v)** a voter declaration form,
		- **(vi)** a letter of instruction regarding voting by mail-in ballot, and
		- **(vii)** an information package regarding the vote.

**Content of notice**

- **(2)** A notice of a vote must state
	- **(a)** the question to be submitted to the eligible voters;
	- **(b)** the date on which the vote will be held;
	- **(c)** the location of each polling station and the hours that it will be open for voting;
	- **(d)** the fact that eligible voters may vote either in person at a polling station in accordance with subsection 17(3) or by mail-in ballot;
	- **(e)** the name and telephone number of the electoral officer; and
	- **(f)** the date, time and location of the information meeting.

**Provision of material on request**

- **(3)** If an eligible voter makes a request to the electoral officer, at least seven days before the vote, for the material referred to in paragraph (1)(b), the electoral officer must provide the material to the eligible voter.

**Records about mail-in ballots**

- **(4)** The electoral officer must indicate on the voters list that a ballot has been provided to each eligible voter to whom a mail-in ballot was mailed, delivered or otherwise provided, and keep a record of the date on which, and the address, if any, to which, each mail-in ballot was mailed or delivered.

**Restriction on voting in person**

- **(5)** An eligible voter to whom a mail-in ballot was mailed, delivered or provided under subsection (1) or (3) is not entitled to vote in person at a polling station other than in accordance with subsection 17(3).

## Voter Declaration

**Content of declaration**

**8** An eligible voter’s completed voter declaration form must set out
- **(a)** the name of the eligible voter;
- **(b)** the first nation membership number or registry number of the eligible voter or, if the eligible voter does not have a first nation membership number or registry number, the date of birth of the eligible voter;
- **(c)** a statement that the eligible voter has read the information in the information package regarding the question that is the subject of the vote, or that the information was read to the eligible voter, and that the eligible voter understood the information;
- **(d)** a statement that the eligible voter has voted freely and without compulsion; and
- **(e)** the name, address and telephone number of a witness to the signature of the eligible voter.

## Information Meeting

**Duty to hold meeting**

**9**

- **(1)** Before the day on which a vote is to be held, the council of the first nation must ensure that an information meeting is held to provide the eligible voters with information regarding the vote.

**Persons to be present**

- **(2)** A legal adviser and a financial adviser, designated by the council of the first nation, must be present at the information meeting and an interpreter must also be present to interpret between those advisers and the eligible voters.

**Information to be provided by the advisers**

- **(3)** The legal adviser and the financial adviser who are present at the information meeting must advise the eligible voters about the following subjects, according to their respective expertise:
	- **(a)** the processes for the implementation of the Act, including the voting process;
	- **(b)** in the case of a vote on the ratification of an oil and gas code and a financial code referred to in section 10 of the Act and the approval of the transfer to the first nation of the management and regulation of oil and gas exploration and exploitation, the possible legal and financial consequences of the ratification of the oil and gas code, the financial code and the transfer;
	- **(c)** in the case of a vote on the ratification of a financial code referred to in section 11 of the Act and the approval of the payment of moneys to the first nation in accordance with the code, the possible legal and financial consequences of the ratification of the financial code and the payment; and
	- **(d)** the content of the question that is the subject of the vote and the possible legal and financial consequences of an affirmative vote or a negative vote.

**Questions**

- **(4)** The legal adviser and the financial adviser who are present at the information meeting must, according to their respective expertise, answer the questions of the eligible voters concerning the vote, including any questions about the subjects referred to in subsection (3).

## Notice to Minister

**Notice to Minister**

**10** The council of the first nation must send to the Minister after the information meeting is held, but before the vote, the following information and documents about the information meeting:
- **(a)** the time when the meeting was held and the place where it was held;
- **(b)** the names and addresses of the legal adviser and the financial adviser who were present; and
- **(c)** written confirmation, signed by the legal adviser and the financial adviser, that they advised the eligible voters about the subjects referred to in subsection 9(3).

## Preparation for Vote

**Duties of electoral officer**

**11** The electoral officer or the deputy electoral officers must
- **(a)** prepare sufficient ballots stating the question to be submitted to the eligible voters and ensure that the initials of the electoral officer or a deputy electoral officer are placed on the back of each ballot;
- **(b)** procure a sufficient number of ballot boxes; and
- **(c)** before the polls are opened, cause the ballots and a sufficient number of lead pencils for marking the ballots to be delivered to the polls.

## Voting by Mail-in Ballot

**How to vote**

**12**

- **(1)** An eligible voter may vote by mail-in ballot by
	- **(a)** marking the ballot by placing a cross, check mark or other mark, clearly indicating the eligible voter’s response to the question that is the subject of the vote;
	- **(b)** folding the ballot in a manner that conceals the question and any marks but exposes the initials on the back;
	- **(c)** placing the ballot in the inner envelope and sealing that envelope;
	- **(d)** completing the voter declaration form and signing the completed form in the presence of a witness who is at least 18 years of age;
	- **(e)** placing the inner envelope and the completed, signed and witnessed voter declaration form in the outer envelope; and
	- **(f)** delivering or, subject to subsection (6), mailing the outer envelope to the electoral officer before the time at which the polls close on the day of the vote.

**Assistance if required**

- **(2)** An eligible voter who is unable to vote in the manner set out in subsection (1) may enlist the assistance of another person to mark the ballot and complete and sign the voter declaration form in accordance with subsection (1).

**Matters to be witnessed**

- **(3)** A witness referred to in paragraph (1)(d) must attest to
	- **(a)** the fact that the person signing the voter declaration form is the person whose name is set out on the form; or
	- **(b)** if the eligible voter enlisted the assistance of another person under subsection (2), the fact that the eligible voter is the person whose name is set out on the form and that the ballot was marked according to the directions of the eligible voter.

**Replacing spoiled ballot**

- **(4)** An eligible voter who inadvertently spoils a mail-in ballot may obtain another ballot by returning the spoiled ballot to the electoral officer.

**Replacing ballot lost or not received**

- **(5)** An eligible voter who loses or has not received a mail-in ballot may obtain another ballot by delivering to the electoral officer a written affirmation that the eligible voter has lost or has not received the mail-in ballot, signed by the eligible voter in the presence of the electoral officer, a justice of the peace, a notary public or a commissioner for oaths.

**Deadline**

- **(6)** Mail-in ballots that are not received by the electoral officer before the time at which the polls close on the day of the vote are void and must not be counted as votes cast.

## Voting at Polling Stations

**Requirement for polling station**

**13** The electoral officer must establish at least one polling station on the reserve.

**Privacy for voting**

**14** The electoral officer or a deputy electoral officer must provide a compartment at each polling place where the eligible voter can mark his or her ballot free from observation.

**Ballot box**

**15** The electoral officer or a deputy electoral officer must, immediately before the opening of the poll, open the ballot box and call on those persons who are present to witness that it is empty and must then lock the ballot box and seal it — so as to ensure that any opening of the ballot box will be made obvious by a disturbance to the seal — using one of the following:
- **(a)** a mechanical device;
- **(b)** adhesive tape or seal; or
- **(c)** any other method that achieves the same result.
> SOR/2009-150, s. 2.

**Hours for polling stations**

**16**

- **(1)** Polling stations must be kept open from 9:00 a.m., local time, until 8:00 p.m., local time, on the day of the vote.

**Presence at closing time**

- **(2)** An eligible voter who is inside a polling station at the time that the polling station is to close is entitled to vote.

**Provision of ballot**

**17**

- **(1)** Subject to subsection 7(5), if a person whose name is set out on the voters list attends at a polling station for the purpose of voting, the electoral officer or a deputy electoral officer must provide the person with a ballot.

**Marking voters list**

- **(2)** The electoral officer or a deputy electoral officer must place on the voters list a mark opposite the name of every eligible voter receiving a ballot.

**Change in voting method**

- **(3)** An eligible voter to whom a mail-in ballot was mailed, delivered or provided under subsection 7(1) or (3) may obtain a ballot and vote in person at a polling station if
	- **(a)** the eligible voter returns the mail-in ballot to the electoral officer or a deputy electoral officer; or
	- **(b)** if the eligible voter has lost or has not received the mail-in ballot, the eligible voter provides the electoral officer or a deputy electoral officer with a written affirmation that the eligible voter has lost or has not received the mail-in ballot, signed by the eligible voter in the presence of the electoral officer, a deputy electoral officer, a justice of the peace, a notary public or a commissioner for oaths.

**Explanation of mode of voting**

**18**

- **(1)** The electoral officer or a deputy electoral officer must explain the mode of voting to an eligible voter when requested to do so by the eligible voter.

**Assistance in voting**

- **(2)** At the request of an eligible voter who is not able to read or who is incapacitated by blindness or other physical cause, the electoral officer or a deputy electoral officer must assist the eligible voter by marking the eligible voter’s ballot in the manner directed by the eligible voter and must place the ballot in the ballot box.

**Record of assistance**

- **(3)** The electoral officer or a deputy electoral officer must make an entry on the voters list opposite the name of the eligible voter indicating that the ballot was marked by him or her at the request of the eligible voter and the reasons for the request.

**Voting procedure**

**19** Except as provided in subsection 18(2), every eligible voter receiving a ballot must
- **(a)** proceed immediately to the compartment provided for marking the ballot;
- **(b)** mark the ballot by placing a cross, check mark or other mark, clearly indicating the eligible voter’s response to the question that is the subject of the vote;
- **(c)** fold the ballot in a manner that conceals the question and any marks but exposes the initials on the back; and
- **(d)** deliver it without delay to the electoral officer or a deputy electoral officer for deposit in the ballot box.

**Replacement ballot**

**20**

- **(1)** An eligible voter who receives a soiled or improperly printed ballot, or who inadvertently spoils his or her ballot in marking it, and who returns the ballot to the electoral officer or a deputy electoral officer is entitled to another ballot.

**Forfeiting right to vote**

- **(2)** An eligible voter who receives a ballot forfeits his or her right to vote if he or she
	- **(a)** leaves the compartment for marking ballots without delivering the ballot to the electoral officer or a deputy electoral officer in the manner provided; or
	- **(b)** refuses to vote.

**Recording the event**

- **(3)** In a case described in subsection (2), the electoral officer or a deputy electoral officer must make an entry on the voters list opposite the name of the eligible voter indicating that the eligible voter did not return the ballot or refused to vote, as the case may be.

**Voting compartment**

**21** The electoral officer or a deputy electoral officer must allow only one eligible voter in the compartment for marking ballots at any one time.

**Prohibition on interference**

**22**

- **(1)** No person may interfere or attempt to interfere with an eligible voter when the eligible voter is marking his or her ballot.

**Prohibition on obtaining information**

- **(2)** No person may obtain or attempt to obtain at the polling place information as to how an eligible voter is about to vote or has voted.

**Interpreter**

**23** If the electoral officer or a deputy electoral officer does not understand the language spoken by an eligible voter, the electoral officer or the deputy electoral officer must enlist the aid of an interpreter to communicate with respect to all matters required to enable that eligible voter to vote.

## Counting Votes

**Mail-in ballots**

**24** After the close of the polls, the electoral officer must, in the presence of a deputy electoral officer and any members of the council of the first nation who are present, open each envelope containing a mail-in ballot that was received before the close of the polls and, without unfolding the ballot,
- **(a)** set aside the ballot if
	- **(i)** it is not accompanied by a voter declaration form or the voter declaration form is not signed or witnessed,
	- **(ii)** the name of the eligible voter set out in the voter declaration form is not on the voters list, or
	- **(iii)** the voters list shows that the eligible voter has already voted; or
- **(b)** place a mark on the voters list opposite the name of the eligible voter set out on the voter declaration form and deposit the ballot in a ballot box.

**Procedure on opening ballot boxes**

**25**

- **(1)** After the mail-in ballots have been deposited under section 24, the electoral officer must, in the presence of a deputy electoral officer and any members of the council of the first nation who are present, open all ballot boxes and
	- **(a)** examine the ballots;
	- **(b)** set aside any ballot that does not have the initials of the electoral officer or a deputy electoral officer on the back;
	- **(c)** reject all ballots
		- **(i)** that have been marked incorrectly, or
		- **(ii)** on which anything appears by which an eligible voter can be identified;
	- **(d)** count the votes cast in favour of and against the question submitted in the vote; and
	- **(e)** prepare a statement in writing of the number of votes so cast and of the number of ballots rejected.

**Signing and filing statement**

- **(2)** The statement referred to in paragraph (1)(e) must be
	- **(a)** signed by the electoral officer and by the chief or a member of the council of the first nation; and
	- **(b)** filed in the regional office of the Department of Indian Affairs and Northern Development.

**Void ballots**

**26** A ballot set aside under paragraph 24(a) or 25(1)(b) or rejected under paragraph 25(1)(c) is void and must not be counted as a vote cast.

**Statement of results**

**27** When the results of the voting are known, the electoral officer must
- **(a)** prepare a statement in triplicate, signed by the electoral officer and by the chief or a member of the council of the first nation, that confirms that the vote was conducted in accordance with these Regulations and indicates the number of
	- **(i)** eligible voters who were entitled to vote,
	- **(ii)** eligible voters who voted,
	- **(iii)** votes cast in favour of and against the question submitted in the vote, and
	- **(iv)** rejected ballots; and
- **(b)** deliver a copy of the statement to
	- **(i)** the Assistant Deputy Minister,
	- **(ii)** the person in charge of the regional office of the Department of Indian Affairs and Northern Development, and
	- **(iii)** the chief of the first nation.

**Retention of ballots**

**28**

- **(1)** The electoral officer must deposit the ballots used in the voting, together with all supporting documents, in a sealed envelope and retain them.

**Destruction of ballots**

- **(2)** If no review has been requested within 60 days after the day of the vote, the electoral officer must destroy the ballots used in the voting.

## Review Procedure

**Request for review**

**29**

- **(1)** An eligible voter may, in the manner set out in subsection (2), request a review of the vote by the Minister if the eligible voter believes that there was
	- **(a)** a contravention of these Regulations that may affect the results of the vote; or
	- **(b)** a corrupt practice in connection with the vote.

**Procedure for request**

- **(2)** A request for a review of a vote must be forwarded to the Minister, by registered mail addressed to the Assistant Deputy Minister, within 30 days after the day of the vote. The request must be accompanied by a declaration containing the grounds for requesting the review and any other relevant information and must be signed in the presence of a witness who is at least 18 years of age.

**Minister to advise Governor in Council**

**30** If the material referred to in subsection 29(2) or any other information in the possession of the Minister is sufficient to call into question the validity of a vote on the ratification of an oil and gas code and a financial code referred to in section 10 of the Act and the approval of the transfer to the first nation of the management and regulation of oil and gas exploration and exploitation, the Minister must advise the Governor in Council accordingly.

## Coming into Force

**Coming into force**

**31** These Regulations come into force on the day on which they are registered.

### **SCHEDULE**
**(Section 4)**

**PART 1**
## Oil and Gas

*This is the question to be put to the eligible voters:*

Do you approve of the oil and gas code and financial code developed by [*insert the name of the first nation*] and the transfer to [*insert the name of the first nation*] of the management and regulation of oil and gas exploration and exploitation in the reserve lands of [*insert the name of the first nation*]?

Yes ☐    No ☐

**PART 2**
## Moneys

*This is the question to be put to the eligible voters:*

Do you approve of the financial code of [*insert the name of the first nation*], dated [*insert the date of the financial code*], and the payment to the [*insert the name of the first nation*], in accordance with the financial code, of all moneys held today, and all moneys to be collected or received in future, by Her Majesty for the use and benefit of the [*insert the name of the first nation*]?

Yes ☐    No ☐

**PART 3**
## Oil and Gas and Moneys

*This is the question to be put to the eligible voters:*

Do you approve of both

**(a)** the oil and gas code and the financial code dated [*insert the date of the financial code*], developed by [*insert the name of the first nation*], and the transfer to [*insert the name of the first nation*] of the management and regulation of oil and gas exploration and exploitation in the reserve lands of [*insert the name of the first nation*], and

**(b)** the financial code dated [*insert the date of the financial code*] developed by [*insert the name of the first nation*] and the payment to the [*insert the name of the first nation*], in accordance with that financial code, of all moneys held today, and all moneys to be collected or received in future, by Her Majesty for the use and benefit of the [*insert the name of the first nation*]?

Yes ☐    No ☐

repository: TravisMadill/CanadianLaws

path: /en/Regulations/Statutory Orders and Regulations/2006/254.md

repo_name: TravisMadill/CanadianLaws


text:
the Rider-Waite-Smith deck was drawn by [Pamela Coleman
Smith](https://en.wikipedia.org/wiki/Pamela_Colman_Smith). this is the original
version, free of US Games's revisions. the interpretations are by [Mark
McElroy](http://www.madebymark.com/2014/07/06/my-latest-book-belongs-to-you/).
both the art and the interpretations are public domain (the former by age, the
latter by the author's graces).

the Silicon Dawn deck is by [Egypt Urnash](http://egypt.urnash.com/tarot/), and
is used here with her explicit permission. it's a good deck (especially if
you're queer, furry, transhuman, or a queer furry transhuman), though sadly out
of print at the moment (mid-september 2018). the interpretations are also used
with her permission, as Silicon Dawn deviates significantly from
Rider-Waite-Smith interpretations.

the Neon Moon deck is by [Pixel Occult](http://www.neonmoontarot.com/), and is
also used with explicit permission. the colors work *really* well with the
asciifier, and i'm happy that the creator was cool enough to let me use them :)

the asciifying process is done using [a program i wrote
myself](https://github.com/deifactor/ascender). it's done entirely
automatically; i'm sure that you could hand-tune the characters to produce
vastly more intelligible output.

[the code itself](https://github.com/deifactor/lost-purpose) is all me (Ash),
but relies on more libraries than i can count.

license: MIT

repository: deifactor/lost-purpose

branch_name: refs/heads/master

extension: md

gha_language: TypeScript

gha_license_id: MIT

license_type: permissive

repo_name: deifactor/lost-purpose


text:
---
layout: post
title: Dispatch 000
---

Monday, March 7,2016

## Articles

[Cybercrime and the Deep Web](https://www.trendmicro.com/vinfo/us/security/news/cybercrime-and-digital-threats/cybercrime-and-the-deep-web?utm_source=trendlabs-social&utm_medium=socal&utm_campaign=cybercimeandthedeepweb-032016 "Cybercrime and the Deep Web") - TrendMicro has published a paper [(pdf)](http://www.trendmicro.com/cloud-content/us/pdfs/security-intelligence/white-papers/wp-cybercrime-and-the-deep-web.pdf "(pdf)") that outlines the cybercriminal underground and regional characteristics. It's a fascinating read.
>Thinking of a unique “global” underground ecosystem is an error, every community has its own characteristics, the criminal crews that compose it are specialized in the provisioning of specific product and services. - [Pierluigi Paganini](http://securityaffairs.co/wordpress/45068/cyber-crime/criminal-underground-deep-web.html "Pierluigi Paganini")

## Guides and Wikis

[READ ME NOOB](https://www.reddit.com/r/deepweb/comments/472coe/read_me_noob/ "READ ME NOOB") - A reddit post that attempts to dispel some of the myths regarding the darkweb.

[Clandestine Shipping](http://pastebin.com/Hxv48hwk "Clandestine Shipping") - **Use for educational purposes only** An exhaustive analysis of how darknet market consumers should approach shipping.

## Resources
and to close here is my [list of "How To" bookmarks](http://bit.ly/EncryptionGuides "list of "How To" bookmarks") on configuring and using encryption. Mostly focused on GPG at this time.

-'till next time, I'm Oscar Alpha Oscar.


text:
# Hand Me Down Marketplace

Hand Me Down Marketplace is an e-commerce web application written in the Laravel 5.3 framework.

In this applications users can buy and sell gently used and secondhand baby, toddler, kids, and teen clothes and toys.

## Contributing
This application was created by Jyrone Parker with help from
* Dillon Li

## Starting The App

Download the repository, run composer, run gulp, run migrations.
Run php vendor/bin/homestead make to install homestead files. Run vagrant up

## License

The Laravel framework is open-sourced software licensed under the [MIT license](http://opensource.org/licenses/MIT).


text:
# Online Labour Index

This Live Data case study is the result of a collaboration between the Live Data project team and both Otto Kässi and Vili Lehdonvirta from the Oxford Internet Institue to visualise data collected from various "online gig economies" for the [iLabour Project](http://ilabour.oii.ox.ac.uk/).

The visualisation was developed using Shiny and will be made available here shortly, note that the underlying data is available here: https://dx.doi.org/10.6084/m9.figshare.3761562.v3

Should you have questions about the project or wish to find out more about this dataset, please contact the [project team](http://ilabour.oii.ox.ac.uk/project-team/)

# Attribution

Code is made available subject to a MIT license, the following copyright and attribution should be respected when reusing the code

- Copyright Owner: University of Oxford
- Date of Authorship: 2016
- Developer: Martin John Hadley (orcid.org/0000-0002-3039-6849)
- Academic Contact: Otto Kässi and Vili Lehdonvirta (http://orcid.org/0000-0002-6509-1703)

repository: okassi/onlinelabourindex

gha_language: R

repo_name: okassi/onlinelabourindex


text:
[![Go Report Card](https://goreportcard.com/badge/github.com/ablox/replicat)](https://goreportcard.com/report/github.com/ablox/replicat)

# replicat
rsync for the cloud

usage:
directory=/tmp/foo go run replicat

Start Replicat with my custom key

1. Ray:    replicat --clusterKey aa88aa88aa88 --directory /tmp/foo

2. Jacob:  replicat --clusterKey aa88aa88aa88 --directory /tmp/foo (this uses machine's hostname:port as the name)

3. James:  replicat --clusterKey aa88aa88aa88 --directory /tmp/foo

// Instances are using tmp folder for testing. Switch to a permanant folder for production or long term use.


text:
# TI_FuelGaugeProgrammer
Programs firmware into a TI Lithium-ion fuel gauge such as the BQ27542.  Status information is sent over serial port.  The user must send 'f' to start programming.

# Instructions
First, use TI's Battery Management Studio to develop firmware settings for your
fuel gauge.  Export BQ.FS or DQ.FS files.

Choose either the BQ.FS or the DQ.FS file to use for programming.  Rename the
desired file "firmware.fs".

Use the FuelGaugeProgrammer.py Python script, which will convert "firmware.fs" to "data.h", which is used by the Arduino/Energia sketch.

Use the FuelGaugeProgrammer.ino sketch in Arduino or Energia to compile and upload to a suitable Arduino or Energia board.

Connect the Arduino or Energia board to the target fuel gauge (if using a pack-side gauge, a battery must be connected as well), as well as a serial port (which is used to control and monitor the programming process).

Using a PC terminal program, connect to the Arduino/Energia's serial port at a baud rate of 115200.  If the board is reset, you should see the text "Press 'f' to program fuel gauge...".

Press 'f'.  The programming progress will be shown on the serial port, followed by a success or fail message.

If the program fails, the fuel gauge will be unresponsive.  You can use TI's EV2400 along with TI's Battery Management Studio to attempt to recover the gauge by reprogramming.


text:
# Secure Socket Funneling (SSF)

## How to build

### Requirements

  * Winrar >= 5.2.1 (Third party builds on windows)
  * Boost >= 1.56.0
  * OpenSSL >= 1.0.2
  * Google Test >= 1.7.0
  * CMake >= 2.8.11
  * nasm (openssl build on windows)
  * Perl | Active Perl >= 5.20 (openssl build on windows)
  * C++11 compiler (Visual Studio 2013, Clang, g++, etc.)

SSF_SECURITY:

* **STANDARD**: the project will be build with standard security features
* **FORCE_TCP_ONLY**: the project will be built without security features to facilitate debugging

### Build SSF on Windows

* Go in project directory

```bash
cd PROJECT_PATH
```

* Copy [Boost archive](http://www.boost.org/users/download/) in ``third_party/boost``

```bash
cp boost_1_XX_Y.tar.bz2 PROJECT_PATH/third_party/boost
```

* Copy [OpenSSL archive](https://www.openssl.org/source/) in ``third_party/openssl``

```bash
cp openssl-1.0.XY.tar.gz PROJECT_PATH/third_party/openssl
```

If you are using *openssl-1.0.2a*, you need to fix the file ``crypto/x509v3/v3_scts.c``. It contains an incorrect ``#include`` line.
Copy [the diff from OpenSSL Github](https://github.com/openssl/openssl/commit/77b1f87214224689a84db21d2eb54e9497186d93.diff)
(ignore the 2 first lines) and put it in ``PROJECT_PATH/third_party/openssl/patches``. The build script will then patch the sources.

* Copy [GTest archive](http://code.google.com/p/googletest/downloads/list) in ``third_party/gtest``

 ```bash
 cp gtest-1.X.Y.zip PROJECT_PATH/third_party/gtest
 ```

* Generate project

 ```bash
 mkdir PROJECT_PATH/build
 cd PROJECT_PATH/build
 cmake -DSSF_SECURITY:STRING="STANDARD|FORCE_TCP_ONLY" ../
 ```

 * Build project

 ```bash
 cd PROJECT_PATH/build
 cmake --build `pwd` --config Debug|Release
 ```

### Build SSF on Linux

* Go in project directory

```bash
cd PROJECT_PATH
```

* Copy [Boost archive](http://www.boost.org/users/download/) in ``third_party/boost``

```bash
cp boost_1_XX_Y.tar.bz2 PROJECT_PATH/third_party/boost
```

* Copy [OpenSSL archive](https://www.openssl.org/source/) in ``third_party/openssl``

```bash
cp openssl-1.0.XY.tar.gz PROJECT_PATH/third_party/openssl
```

* Copy [GTest archive](http://code.google.com/p/googletest/downloads/list) in ``third_party/gtest``

```bash
cp gtest-1.X.Y.zip PROJECT_PATH/third_party/gtest
```

* Generate project

```bash
mkdir PROJECT_PATH/build
cd PROJECT_PATH/build
cmake -DCMAKE_BUILD_TYPE=Release|Debug -DSSF_SECURITY:STRING="STANDARD|FORCE_TCP_ONLY" ../
```

* Build project

```bash
cmake --build PROJECT_PATH/build -- -j
```

### Build SSF on Mac OS X

* Go in project directory

```bash
cd PROJECT_PATH
```

* Copy [Boost archive](http://www.boost.org/users/download/) in ``third_party/boost``

```bash
cp boost_1_XX_Y.tar.bz2 PROJECT_PATH/third_party/boost
```

* Copy [OpenSSL archive](https://www.openssl.org/source/) in ``third_party/openssl``

```bash
cp openssl-1.0.XY.tar.gz PROJECT_PATH/third_party/openssl
```

* Copy [GTest archive](http://code.google.com/p/googletest/downloads/list) in ``third_party/gtest``

```bash
cp gtest-1.X.Y.zip PROJECT_PATH/third_party/gtest
```

* Generate project

```bash
mkdir PROJECT_PATH/build
cd PROJECT_PATH/build
cmake -DCMAKE_BUILD_TYPE=Release|Debug -DSSF_SECURITY:STRING="STANDARD|FORCE_TCP_ONLY" ../
```

* Build project

```bash
cmake --build PROJECT_PATH/build -- -j
```

## How to configure

### Generating certificates for TLS connections

#### With tool script

```bash
./tools/generate_cert.sh /path/to/store/certs
```

The first argument should be the directory where the CA and certificates will be generated

#### Manually

##### Generating Diffie-Hellman parameters

```bash
openssl dhparam 4096 -outform PEM -out dh4096.pem
```

##### Generating a self-signed Certification Authority (CA)
First of all, create a file named *extfile.txt* containing the following lines:

```plaintext
[ v3_req_p ]
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
```

Then, generate a self-signed certificate (the CA) *ca.crt* and its private key *ca.key*:

```bash
openssl req -x509 -nodes -newkey rsa:4096 -keyout ca.key -out ca.crt -days 3650
```

##### Generating a certificate (signed with the CA) and its private key

Generate a private key *private.key* and signing request *certificate.csr*:

```bash
openssl req -newkey rsa:4096 -nodes -keyout private.key -out certificate.csr
```

Sign with the CA (*ca.crt*, *ca.key*) the signing request to get the certificate *certificate.pem* :

```bash
openssl x509 -extfile extfile.txt -extensions v3_req_p -req -sha1 -days 3650 -CA ca.crt -CAkey ca.key -CAcreateserial -in certificate.csr -out certificate.pem
```

### Configuration file

With default options, the following files and folders should be in the directory of execution of a client or a server:

* ./certs/dh4096.pem
* ./certs/certificate.crt
* ./certs/private.key
* ./certs/trusted/ca.crt

Where:

* *dh4096.pem* contains the Diffie-Hellman parameters (see above for how to generate the file)
* *certificate.crt* and *private.key* are the certificate and the private key of the ssf server or client
* *ca.crt* is the concatenated list of certificates trusted by the ssf server or client

However, if you want those files at different paths, it is possible to customize them with the configuration file option *-c*.

An example is given in the file example section.

### Relay chain file

This file will contain the bounce servers and ports which will be used to establish the connection.
They will be listed as follow :

```plaintext
SERVER1:PORT1
SERVER2:PORT2
SERVER3:PORT3
```

The chain will be CLIENT -> SERVER1:PORT1 -> SERVER2:PORT2 -> SERVER3:PORT3 -> TARGET

## How to use

### Standard command line

```plaintext
ssf<c|s>[.exe] [-h] [-L loc:ip:dest] [-R rem:ip:dest] [-D port] [-F port] [-U loc:ip:dest] [-V rem:ip:dest] [-b bounce_file] [-c config_file] [-p port] [host]
```

* host : the IP address or the name of the remote server to connect to.
* -p : *port* is the port on which to listen (for the server) or to connect (for the client). The default value is 8011.
* -L : TCP port forwarding with *loc* as the local TCP port, *ip* and *dest* as destination toward which the forward should be done from the server.
* -R : TCP remote port forwarding with *rem* as the TCP port to forward from the remote host, *ip* and *dest* as destination toward which the forward should be done from the client.
* -D : open a port (*port*) on the client to connect to a SOCKS server on the server from the client.
* -F : open a port (*port*) on the server to connect to a SOCKS server on the client from the server.
* -U : UDP port forwarding with *loc* as the UDP port to forward from the client, *ip* and *dest* as destination toward which the forward should be done from the server.
* -V : UDP remote port forwarding with *rem* as the UDP port to forward from the server, *ip* and *dest* as destination toward which the forward should be done from the client.
* -b : *bounce_file* is the file containing the list of relays to use.
* -c : *config_file* is the config file containing configuration for SSF (TLS configuration).

### Copy command line

```plaintext
ssfcp[.exe] [-h] [-b bounce_file] [-c config_file] [-p port] [-t] [host@]path [[host@]path]
```

* -b : *bounce_file* is the file containing the list of relays to use.
* -c : *config_file* is the config file containing configuration for SSF (TLS configuration).
* -t : input from stdin

#### Copy from local to remote destination :

```plaintext
ssfcp[.exe] [-b bounce_file] [-c config_file] [-p port] path/to/file host@absolute/path/directory_destination
```

```plaintext
ssfcp[.exe] [-b bounce_file] [-c config_file] [-p port] path/to/file* host@absolute/path/directory_destination
```

#### From stdin to remote destination

```plaintext
data_in_stdin | ssfcp[.exe] [-b bounce_file] [-c config_file] [-p port] -t host@path/to/destination/file_destination
```

#### Copy remote files to local destination :

```plaintext
ssfcp[.exe] [-b bounce_file] [-c config_file] [-p port] remote_host@path/to/file absolute/path/directory_destination
```

```plaintext
ssfcp[.exe] [-b bounce_file] [-c config_file] [-p port] remote_host@path/to/file* absolute/path/directory_destination
```

### File example

#### Bounce file (relay servers)

```plaintext
<IP_ADDRESS>:8002
<IP_ADDRESS>:8003
```

#### Config file

```plaintext
{
    "ssf": {
        "tls": {
            "ca_cert_path": "./certs/trusted/ca.crt",
            "cert_path": "./certs/certificate.crt",
            "key_path": "./certs/private.key",
            "dh_path": "./certs/dh4096.pem",
            "cipher_alg": "DHE-RSA-AES256-GCM-SHA384"
        }
    }
}
```

* *tls.ca_cert_path* : relative or absolute path to the CA certificate file
* *tls.cert_path*    : relative or absolute path to the instance certificate file
* *tls.key_path*     : relative or absolute path to the private key file
* *tls.dh_path*      : relative or absolute path to the Diffie-Hellman file
* *tls.cipher_alg*   : cypher algorithm

repository: chrisaljoudi/ssf

branch_name: refs/heads/develop

repo_name: chrisaljoudi/ssf


text:
# Contributing to KubeDL

Welcome to KubeDL!
We encourage you to help out by reporting issues, improving documentation, fixing bugs, or adding new features.
Please also take a look at our code of conduct, which details how contributors are expected to conduct themselves as part of the KubeDL community.

## Reporting issues

To be honest, we regard every user of KubeDL as a very kind contributor.
After experiencing KubeDL, you may have some feedback for the project.
Then feel free to open an issue.

There are lot of cases when you could open an issue:

- bug report
- feature request
- performance issues
- feature proposal
- feature design
- help wanted
- doc incomplete
- test improvement
- any questions on project
- and so on

Also we must remind that when filing a new issue, please remember to remove the sensitive data from your post.
Sensitive data could be password, secret key, network locations, private business data and so on.

## Code and doc contribution

Every action to make KubeDL better is encouraged.
On GitHub, every improvement for KubeDL could be via a PR (short for pull request).

- If you find a typo, try to fix it!
- If you find a bug, try to fix it!
- If you find some redundant codes, try to remove them!
- If you find some test cases missing, try to add them!
- If you could enhance a feature, please DO NOT hesitate!
- If you find code implicit, try to add comments to make it clear!
- If you find code ugly, try to refactor that!
- If you can help to improve documents, it could not be better!
- If you find document incorrect, just do it and fix that!
- ...

### Workspace Preparation

To put forward a PR, we assume you have registered a GitHub ID.
Then you could finish the preparation in the following steps:

1. **Fork** Fork the repository you wish to work on. You just need to click the button Fork in right-left of project repository main page. Then you will end up with your repository in your GitHub username.
2. **Clone** your own repository to develop locally. Use `git clone https://github.com/<your-username>/kubedl.git` to clone repository to your local machine. Then you can create new branches to finish the change you wish to make.
3. **Set remote** upstream to be `https://github.com/alibaba/kubedl.git` using the following two commands:

```bash
git remote add upstream https://github.com/alibaba/kubedl.git
git remote set-url --push upstream no-pushing
```

Adding this, we can easily synchronize local branches with upstream branches.

4. **Create a branch** to add a new feature or fix issues

Update local working directory:

```bash
cd <project>
git fetch upstream
git checkout master
git rebase upstream/master
```

Create a new branch:

```bash
git checkout -b <new-branch>
```

Make any change on the new-branch then build and test your codes.

### PR Description

PR is the only way to make change to KubeDL project files.
To help reviewers better get your purpose, PR description could not be too detailed.

### Developing Environment

As a contributor, if you want to make any contribution to KubeDL project, we should reach an agreement on the version of tools used in the development environment.
Here are some dependents with specific version:

- Golang : v1.13+ (1.14 is best)
- Kubernetes: v1.12+

### Developing guide

There's a `Makefile` in the root folder which describes the options to build and install. Here are some common ones:

```bash
# Build the controller manager binary
make manager

# Run the tests
make test

# Generate manifests e.g. CRD, RBAC YAML files etc
make manifests
```

If you want to start kubedl locally to work with a Kubernetes cluster, you should follow the [debug guide](./docs/debug_guide.md).

## Engage to help anything

We choose GitHub as the primary place for KubeDL to collaborate.
So the latest updates of KubeDL are always here.
Although contributions via PR is an explicit way to help, we still call for any other ways.

- reply to other's issues if you could;
- help solve other user's problems;
- help review other's PR design;
- help review other's codes in PR;
- discuss about KubeDL to make things clearer;
- advocate KubeDL technology beyond GitHub;
- write blogs on KubeDL and so on.

In a word, **ANY HELP IS CONTRIBUTION**.

## Join KubeDL as a member

It is also welcomed to join KubeDL team if you are willing to participate in KubeDL community continuously and keep active.

### Requirements

- Have read the [Contributing to KubeDL](./CONTRIBUTING.md) carefully
- Have read the [Contributor Covenant Code of Conduct](./CODE_OF_CONDUCT.md)
- Have submitted multi PRs to the community
- Be active in the community, may including but not limited
    - Submitting or commenting on issues
    - Contributing PRs to the community
    - Reviewing PRs in the community

### How to do it

You can do it in either of two ways:

- Submit a PR in the project repo
- Contact via the [community](./README.md#community) channels offline

repository: yhalpha/kubedl

repo_name: yhalpha/kubedl


text:
### About the Wallpapers

Here you will find a collection of wallpapers for Masari. To add you own, upload the file and start a pull request.

## Preview

![Masari Wallpaper](https://github.com/masari-project/Masari-Marketing/blob/master/Wallpapers/Masari_Green_Wallpaper.png)

repository: masari-project/Masari-Marketing

gha_language: HTML

repo_name: masari-project/Masari-Marketing


text:
# react-controls
React bits and bobs

#QHDatePicker

Simple inline date picker using React

![qh-datepicker screenshot](https://github.com/quangas/react-controls/blob/master/qh-datepicker.png)

####QHDatePicker.jsx

To use this in React.net, rails and as a standalone single component, just reference the QHDatePicker.jsx in your javascript references and then include <QHDatePicker year={2016} month={10} day={21} /> in your render method.

```
<body>
  <div id="content" />

  <script src="react libary" />
  <script src="/path/to/QHDatePicker.js" />
</body>
```

####QHDatePicker.js

To use this control, you will need to do something like this:

```
var QHDatePicker = require('/path/to/QHDatePicker.js');
```

Then somehwere in your render method declare

```
<QHDatePicker year={2016} month={10} day={21} />
```

#####Options

If you want to use today's date, use can make a call to the javascript's new Date() then set the props to use this date.

e.g

```
var d = new Date();

year: d.getFullYear(),
month: d.getMonth() + 1,
day: d.getDate()
```

For React Native component, you would replace a **div** with **View** and for **table** you could use a **ListView** and apply the same logic.

repository: quangas/react-controls

repo_name: quangas/react-controls


text:
# Rocky Extension to The Rockstar Language Specification

Rockstars need freedom. Sometimes for necessities, sometimes just for fun, but a rocker always revolting against the rules or at least breaking some boundaries. So, Rocky offers some features that are not available in [the supported Rockstar specification](spec.md).

By default, Rocky recognises whether strict or extension mode should be allowed (from the presence of `import` or `album` statements). To explicitly enable Rocky features, add `-X` or `--rocky` as a command-line parameter.

## Object Oriented Programming extension

There is a separate page to introduce [Rockstar Object-Oriented Programming](OOP.md).

## Native Java support

There is a separate page about [Native Java support](native_java.md) in Rocky. Shortly: it is possible to call native Java methods from Rockstar and using a `FunctionalInterface` Java classes can call back to Rockstar. Values are automatically converted to and from Java.

## Array extensions

### Iteration

Array iteration is the extension of the `while` loop. There are two similar statements for list iteration (`while ... alike ...`) and associative array iteration (`while ... alike ... for ...`).
Aliases: `while ... as ...` and `while ... as ... for ...`

```
('the army' is an integer-indexed array)
While the army alike my warrior
  ('my warrior' is the current value)
```
The cycle traverses through all array elements in increasing index order.

```
('the members' is an associative array)
While the members alike the man for the role
  ('the role' is the key, 'the man' is the value)
```
The cycle traverses through all key-value elements in increasing key order. Keys are compared according to the default comparison rules (e.g. string are alphabetically increasing, numbers are arithmetically increasing, etc).

### Array sorting

The built-in function `sorted` creates a new array, that contains all the elements of the original array, ordered. Can be used in prefix or postfix format.

The following lines are identical:
```
('the colors' is an integer-indexed array)
Let the rainbow be sorted the colors
Let the rainbow be the colors sorted
```

### Array size

The built-in function `count of` returns the number of elements in an array. Aliases: `length of`, `height of`.

```
Say height of the rainbow
```

### Last element of an array ("peek")

The built-in function `last of` returns the last element in an array.

```
Say last of the colors
```

## DEC64 Arithmetics

As per the original Rockstar specification, Rocky fully supports DEC64 arithmetic with `--dec64` command line option (including rounding functions).

## BigDecimal Arithmetics

Rocky supports infinite-precision arithmetics using Java BigDecimal type with `--bigdecimal` command line option (including rounding functions).

## Aliasing

If you want to express yourself as you want, you can redefine many language elements using the `means` keyword:
```
Growl means Say
growl "Hello there!"
```

Aliasing operates on whole keyword level only. For example `throw back means give back` works, but `throw means give` does not.
All keywords in statements can be aliased. From expressions, it only works for the keyword `taking` currently (but may be extended).

It's possible to define the same alias for different keywords, if their lexical position is different. For example:
```
telling means say
telling means taking
telling "Hello!" ("say")
Desire telling my love ("taking")
```

It is also allowed to redefine keywords (though not recommended), but it's not possible to redefine other aliases.

repository: gaborsch/rocky

gha_language: Java

repo_name: gaborsch/rocky


text:
# Mocap loader and VR KNN motion baseline

# Dependencies:
 - [N-dimensional KDTree](https://github.com/eregina92/Supercluster.KDTree)
 - [bvh parser](https://assetstore.unity.com/packages/tools/animation/bvh-tools-144728)
 - [oculus integration](https://assetstore.unity.com/packages/tools/integration/oculus-integration-82022)

gha_language: C#


text:
Icinga Status for Google Chrome™
================================

**THIS PROJECT IS NOT UPDATED AND MAINTAINED ANY MORE, PLEASE CONSIDER TO SWITCH TO DIFFERENT ALTERNATIVES**

Icinga Status is simple open source extension for Google Chrome™ that helps you watch over your Icinga or Nagios instance.

[![Flattr this git repo](http://api.flattr.com/button/flattr-badge-large.png)](https://flattr.com/thing/381395)

Features
--------

- support Icinga and Nagios
- show overview of number of hosts and services in different states
- list of hosts with some troubles
- list of services with some troubles
- ability to quickly re-check service or host
- link to acknowledge service or host problem
- tabs with host and service list
- ability to set data refresh interval
- ability to ignore some services and/or hosts based on regular expression

Contributors
------------
- kepi
- slawekp (regexp ignoring of hosts/services)

License
-------

This extension is released under [MIT License](http://github.com/kepi/IcingaChromedStatus/blob/master/MIT-LICENSE.txt).

repository: kepi/IcingaChromedStatus

gha_language: JavaScript

repo_name: kepi/IcingaChromedStatus


text:
# Pull request general verifications

## Branch naming convention

Example:  *feature/LUSTEF-Zad12*

# Every file

## Remove commented out lines of code and empty lines

Remove ```// Commented lines``` and empty lines

## Enable file formatting

By default, file formatting should be already uploaded to Eclipse.

* Eclipse -> Preferences -> Java -> Code Style -> Formatter -> Import [eclipse_format_code_standards.xml](https://bitbucket.org/capntc/selenium_workshop/src/cc4f1840dd7b2831907526c47bdf247ab74903a2/README/eclipse_format_code_standards.xml?at=develop)

* How to use: Ctrl + Shift + F

## Name of java package. Always small letters

The prefix of a unique package name is always written in all-lowercase ASCII letters.

Example   com.example.selenium.cmu.cs.bovik.cheese

## Name of java class

Class names should be nouns, in mixed case with the first letter of each internal word capitalized. Try to keep your class names simple and descriptive. Use whole words-avoid acronyms and abbreviations (unless the abbreviation is much more widely used than the long form, such as URL or HTML).

Example:

* class Raster;

* class ImageSprite;

## Name of methods

Methods should be verbs, in mixed case with the first letter lowercase, with the first letter of each internal word capitalized.

Example:

* run();

* runFast();

* getBackground();

# Inside Test file

List of rules during code review for file structure - Test class files

## Test business steps

Validate all business test case steps

## No Selenium operations in Test Classes

Test Class file can only execute methods/actions from Page class.

As the result of this, Test class can use only *asserts* against this Page methods

## Test method naming convention

# Inside Page file

List of rules during code review for file structure - Page class files

## No junit/test operation in file

As Page class file mimics actions on web page, therefore no "test" operation can be done here.

For any test action, Test class with test methods can be used.

## Method/actions naming convention.

Method convention described in details, link: [Naming convention](https://bitbucket.org/capntc/selenium_workshop/src/e229eba16f7915c6bb52838c9a9b9923be46d2a3/README/namingConvention.docx?at=develop)

## Method/actions can exit when all tasks are finished

Some actions such as *click* might need to:

* wait to load page```getDriver().waitForPageLoaded();```

* return new Page object.

## No explicitly *sleep* steps

It is not allowed to use Thread.sleep steps.

Instead of this pleas use *waitUntil*

List available *waitUntils*:

* getDriver().waitForPageLoaded();

* getDriver().waitForElement(selector);

* getDriver().waitForElementVisible(selector);

* getDriver().waitUntilElementIsClickable(selector);

## Selector variable - CSS , id, class

Type of selector: every type ( `By.cssSelector` , `By.className` , ... )  *except* `By.xpath`

`private static final By selectorResultBanner = By.cssSelector("#hdtb-msb-vis");`

Link to css selector [tutorial](https://bitbucket.org/capntc/selenium_workshop/src/e229eba16f7915c6bb52838c9a9b9923be46d2a3/README/cssSelector.docx?at=develop)

## Selector variable type convention

Type of variable: *private static final*

`private static final By selectorResultBanner = By.cssSelector("#hdtb-msb-vis");`

## Selector variable naming convention

Naming: selector[ElementName]

`private static final By selectorResultBanner = By.cssSelector("#hdtb-msb-vis");`

repository: devonfw-forge/mrchecker-source

repo_name: devonfw-forge/mrchecker-source


text:
# Angular Shop

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.3.0.

This small project demos an ecommerce application setup with Angular, using local data(could be replaced with a remote data source).

![Screen Shot](screenshots/photo.jpg)

[![Netlify Status](https://api.netlify.com/api/v1/badges/1ea90267-656f-4cc1-99ae-4710ed71f8f4/deploy-status)](https://app.netlify.com/sites/angular-shop/deploys)

## Build Setup

```bash
# install dependencies
$ npm install

# serve with hot reload at localhost
$ ng serve

# build for production
$ ng build --prod
```

## Todo

- Add logic for duplicate cart items
- Migrate to remote data source
- Integrate payment

## License

    Copyright 2019 Precious Keyz

    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

## Disclaimer

- CSS stylesheet was taken from [https://github.com/sdras/sample-vue-shop](https://github.com/sdras/sample-vue-shop)
- i do not have any affiliation with person's afore mentioned.

repository: codekeyz/angular-shop

repo_name: codekeyz/angular-shop


text:
---
sidebar: auto
---

# Glossary

## Actuator

The operation that can be invoked on a unit/module/class/etc that executes its principle objective and responsibility.

## Applicative

Applicative is similar to "application", as in "application logic". Because _services_ are not _applications_, the term "application logic" is out of place when talking about service implementation. The term "applicative", as in "applicative logic" is more appropriately used in this case.

## Autonomy

Autonomy is arguably the most critical quality of service design. It's the thing that can dictate whether you end up with a service architecture, or a web of web services organized as a _distributed monolith_. Autonomy is the quality that allows services to remain online when services that they communicate with become unavailable. Autonomy has the most profound influence on the design of services, the things that are inside of a service, and the things that are outside of a service. Without autonomy, services arguably aren't services at all.

## Cardinal ID

The _cardinal ID_ is the first ID that appears in an [entity stream's](#entity-stream) [compound ID](#compound-id). If the stream name has only a single ID, then the cardinal ID is that single ID.

## Category

A category is a group of streams all related to the same type of [entity](/glossary.md#entity). An analogy would be a class in an object-oriented system.

## Category Stream

A [stream](/glossary.md#stream) that contains the messages for every individual, identified stream in the category. For example, given the streams `account-123`, and `account-456`, the category stream, `account`, contains messages from both individual streams in the account category.

## Category Type

A [category type](/user-guide/stream-names/#category-types) is a qualifier added to a category name that is used to differentiate between categories used for various specific purposes.

## Command

A command is a [message](/glossary.md#message) that represents an instruction sent to a [component](/glossary.md#component). A command is an input message. Commands are sent directly to components. They are a unidirectional transmission from one [endpoint](/glossary.md#endpoint) directly to another.

## Command Stream

A [stream](/glossary.md#stream) that contains only [command](/glossary.md#command) messages. Command streams are effectively the _input queues_ that services read their commands from.

## Component

A package of code that represents a single business concern and/or business process, such as an account, a sale, and so forth. It's all the code wrapped around that concern to operationalize it. It has one or more [entities](/glossary.md#entity), but very few. A component is often packaged as a RubyGem. A component is hosted either by itself or with other components in a [service](/glossary.md#service).

## Component Host

The component host is the outermost surface of an Eventide service. It runs right next to the operating system. It is the physical "service". It loads components into itself. It coordinates the threads that the [consumers](/glossary.md#consumer) run on. It provides graceful shutdown for the components hosted in a service.

## Compound ID

A [compound ID](/user-guide/stream-names/#compound-entity-ids) is the ID part of an [entity stream](#entity-stream) name that is composed of multiple values.

## Compound Category Type

A [compound category type](/user-guide/stream-names/#compound-category-types) is a [category type](#category-type) that is composed of multiple values to indicate the category's multiple purposes.

## Consumer

The consumer is the infrastructure that runs a subscription [reader](/glossary.md#message-reader) over streams, and plugs-in the [handlers](/glossary.md#handler) to those subscriptions to receive the messages they subscribe to.

## Endpoint

An endpoint is the source process that a message comes from or the destination process where it is sent. The term _endpoint_ is often used informally as a substitute for _service_.

## Entity

The entity is the core logic of the [component](/glossary.md#component). It's the _domain model_. It's analogous to a Rails model, but that's only an analogy. One entity's data is contained in a single, individual [event stream](/glossary.md#event-stream). An entity collects any important information from the events in the entity's stream. It's also a data object. An entity has a corresponding [projection](/glossary.md#entity-projection), which is used to copy data from the events to the entity object, either by setting the entity's attributes or by invoking its methods. The data that an entity has collected is also used in [handler](/glossary.md#handler) code to determine whether a [command](/glossary.md#command) should be processed.

## Entity Cache

When entities are retrieved via the [entity store](/glossary.md#entity-store), they are cached in-memory, and, optionally on disk.

## Entity Projection

An [entity's](/glossary.md#entity) data comes from [events](/glossary.md#event). An event is a thing that has happened in a process, or it's a change that has been made to an entity's state. Often, these two are one and the same. The projection is a mechanism that receives events as inputs, and modifies the state of an entity. When an entity is "retrieved", its events are _applied_ to it by the entity projection.

## Entity Snapshot

An entity snapshot is saved to disk (typically, in the message store) by the [entity store](/glossary.md#entity-store) as a performance optimization for warm-up time of the [entity cache](/glossary.md#entity-cache). The store saves a snapshot based on an assignable interval of events. For example, if the interval is set to 100, the store will save an entity's snapshot every 100 events that the store reads and projects onto the entity.

## Entity Stream

A [stream](/glossary.md#stream) that contains the messages for a single, identified entity. For example, a single account with the ID `123` has all of its events in its own stream, and that stream contains only the events for account 123.

## Entity Store

The entity store is used to do the retrieval of entities. It coordinates a [reader](/glossary.md#message-reader), an entity projection, and an entity cache. In reads only new events for an entity, projects them on to the cached entity, and updates the cache with the result of the projection. It may optionally record cached [snapshots](/glossary.md#snapshot) of entities to disk once every _n_ events read and projected.

## Event

A message that represents the results and effects of some command having been processed. It's a record of something that has happened or that has been processed. An [entity's](/glossary.md#entity) state is gathered from the events that have been written about the entity. Each activity of an entity's life is recorded as an event, and written to the entity's stream.

## Event Sourcing

Event sourcing is a style of [entity](/glossary.md#entity) storage that relies on reading entity data from a series of [events](/glossary.md#event) that are recorded in a [stream](/glossary.md#stream) that holds the events for a single entity. An entity's data is stored by writing events to its stream. When the entity is "retrieved" from the [entity store](/glossary.md#entity-store), the events are passed through an [entity projection](/glossary.md#entity-projection), which populates the entity's attributes.

## Event Stream

A [stream](/glossary.md#stream) that contains only [event](/glossary.md#event) messages. Each entity instance maps to a single, individual event stream. An entity's data is collected from the events in its stream.

## EventStore (Database)

One of the databases supported by Eventide. Event Store is an open source, special-purpose database designed specifically for high-availability event storage and event processing.

## Event Store (Pattern)

A database specifically structured for the storage and retrieval of [events](/glossary.md#event). See also: [message store](/glossary.md#message-store).

## Handler

Handlers have the business logic for processing the messages that are inputs to a [component's](/glossary.md#component) [consumers](/glossary.md#consumer). Handlers are loosely analogous to _controllers_ in a web MVC app.

## Message

A message is a data structure that represents either an instruction to be passed to a process ([command](/glossary.md#command)), or a record of something that has happened ([event](/glossary.md#event)) - typically in response to the processing of a command. Messages are written to the [message store](/glossary.md#message-store), and then read by [consumers](/glossary.md#consumer) that then dispatch messages to [handlers](/glossary.md#handler).

## Message Queue and Message Bus

A form of message transport that relies on more elaborate mechanisms and protocols for moving messages through a system and keeping track of which messages have already been processed. These technologies are notably failure-prone and can cause subtle errors where messages are not delivered and the delivery failure can go undetected by operators, developers, and testers.

## Message Reader

Retrieves ordered batches of messages from a single [stream](/glossary.md#stream), processing each message, one-by-one, into a block that can be passed to the reader's [actuator](/glossary.md#actuator).

## Message Store

Unlike a message broker, a message store acts not only as a message transport, but also a durable store of messages that have been written. A service receives commands by reading _new_ messages that have been written to the message store. Events are written to the message store in response to handling the inbound commands. Entity state is gathered from the event data that is written to the message store's message streams.

## Message Transport

Any technology that is used to send (_transport_) messages from one process to another. For example: a queue, a broker, or a raw network transport protocol like TCP or HTTP.

## Message Writer

Writes a message, or a batch of messages, to a single stream.

## Provenance

Provenance is the chronology of the custody or location of a historical object. It's used in the context of messaging workflows to describe metadata of preceding messages in a sequence of messages in a causal chain of messages.

## Pub/Sub

Pub/Sub is a messaging pattern where publishers produce events and subscribers consumer them. In Pub/Sub, events are written without the publisher's knowledge of the subscribers.

## Service

In its strictest sense, a service is an autonomous unit of system operations that is made up of [components](/glossary.md#component) that the service hosts.

## Stream

A stream is the fundamental unit of storage that a [message](/glossary.md#message) is stored in. When a message is written to the store, the [writer](/glossary.md#writer) must also be given the [stream name](/glossary.md#stream-name) that the event will be stored in. A stream is only stored in a single [message store](/glossary.md#message-store).

## Stream Name

A stream's name not only identifies the stream, but also its purpose. A stream name is a string that optionally includes an ID that is prefixed by a dash (-) character. The part of the stream preceding the dash is the _[category](/glossary.md#category)_, and the part following the dash is the ID. A stream with an ID is typically an [event stream](/glossary.md#event-stream) containing the events for the entity with that ID. For example: `account-123` is a stream for the account entity with an ID of 123. The `account` stream name is the [category stream](/glossary.md#category-stream) name that contains all of the aggregated messages from all individual, identified account streams. See the [overview of stream names](/user-guide/stream-names/#overview) in the user guide for more information.

repository: eventide-project/docs

repo_name: eventide-project/docs


text:
---
id: delete-button
title: Delete
---

import deleteButton from<EMAIL_ADDRESS>import confirmation from<EMAIL_ADDRESS>
`<DeleteButton>` uses Ant Design's [`<Button>`](https://ant.design/components/button/) and [`<Popconfirm>`](https://ant.design/components/popconfirm/) components.
When you try to delete something, a pop-up shows up and asks for confirmation. When confirmed it executes the [`useDelete`](api-references/hooks/data/useDelete.md) method provided by your [`dataProvider`](api-references/providers/data-provider.md).

## Usage

```tsx
import {
    // highlight-next-line
    DeleteButton,
    List,
    Table,
    useTable,
} from "@pankod/refine";

export const PostList: React.FC = () => {
    const { tableProps } = useTable<IPost>();

    return (
        <List>
            <Table {...tableProps} rowKey="id">
                <Table.Column dataIndex="id" title="ID" />
                <Table.Column dataIndex="title" title="Title" />
                <Table.Column<IPost>
                    title="Actions"
                    dataIndex="actions"
                    render={(_, record) => (
                        // highlight-next-line
                        <DeleteButton size="small" recordItemId={record.id} />
                    )}
                />
            </Table>
        </List>
    );
};

interface IPost {
    id: string;
    title: string;
}
```

Will look like this:

When clicked, it opens the confirmation window like this:

## Properties

### `recordItemId`

`recordItemId` allows us to manage which record will be deleted.

```tsx
import { DeleteButton } from "@pankod/refine";

export const MyDeleteComponent = () => {
    return <DeleteButton resourceName="posts" recordItemId="1" />;
};
```

Clicking the button will trigger the [`useDelete`](api-references/hooks/data/useDelete.md) method and then the record whose resource is "post" and whose id is "1" gets deleted.

:::note
**`<DeleteButton>`** component reads the id information from the route by default.
:::

### `resourceName`

`resourceName` allows us to manage which resource's record is going to be deleted.

```tsx
import { DeleteButton } from "@pankod/refine";

export const MyDeleteComponent = () => {
    return <DeleteButton resourceName="categories" recordItemId="2" />;
};
```

Clicking the button will trigger the [`useDelete`](api-references/hooks/data/useDelete.md) method and then the record whose resource is "categories" and whose id is "2" gets deleted.

:::note
**`<DeleteButton>`** component reads the resource name from the route by default.
:::

### `onSuccess`

`onSuccess` can be used if you want to do anything on the result returned after the delete request.

For example, let's `console.log` after deletion:

```tsx
import { List, Table, DeleteButton, useTable } from "@pankod/refine";

export const PostList: React.FC = () => {
    const { tableProps } = useTable<IPost>();

    return (
        <List>
            <Table {...tableProps} rowKey="id">
                <Table.Column dataIndex="id" title="ID" />
                <Table.Column dataIndex="title" title="Title" />
                <Table.Column<IPost>
                    title="Actions"
                    dataIndex="actions"
                    render={(_, record) => (
                        // highlight-start
                        <DeleteButton
                            size="small"
                            recordItemId={record.id}
                            onSuccess={(value) => {
                                console.log(value);
                            }}
                        />
                        // highlight-end
                    )}
                />
            </Table>
        </List>
    );
};
```

### `mutationMode`

Determines which mode mutation will have while executing `<DeleteButton>`.

[Refer to the mutation mode docs for further information. &#8594](guides-and-concepts/mutation-mode.md)

```tsx
import { List, Table, DeleteButton, useTable } from "@pankod/refine";

export const PostList: React.FC = () => {
    const { tableProps } = useTable<IPost>();

    return (
        <List>
            <Table {...tableProps} rowKey="id">
                <Table.Column dataIndex="id" title="ID" />
                <Table.Column dataIndex="title" title="Title" />
                <Table.Column<IPost>
                    title="Actions"
                    dataIndex="actions"
                    render={(_, record) => (
                        <DeleteButton
                            size="small"
                            recordItemId={record.id}
                            // highlight-next-line
                            mutationMode="undoable"
                        />
                    )}
                />
            </Table>
        </List>
    );
};
```

### `hideText`

It is used to show and not show the text of the button. When `true`, only the button icon is visible.

```tsx
import { DeleteButton } from "@pankod/refine";

export const MyDeleteComponent = () => {
    return <DeleteButton hideText />;
};
```

## API Reference

### Properties

| Property     | Description                                                                                | Type                                                                                | Default                                                                              |
| ------------ | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| props        | Ant Design button properties                                                                 | [`ButtonProps`](https://ant.design/components/button/#API) & [`DeleteButtonProps`](../../interfaces.md#delete-button-props) |                                                                                |
| resourceName | Determines which resource to use for deletion                                                | `string`                                                                                | Resource name that it reads from route                                               |
| recordItemId | Determines which id to use for deletion                                                      | `string`                                                                                | Record id that it reads from route                                                   |
| onSuccess    | Called when [mutation](https://react-query.tanstack.com/reference/useMutation) is successful | `(value: DeleteOneResponse) => void`                                                                                |                                                                                |
| mutationMode | Determines when mutations are executed.                                                      | `"pessimistic"` \| `"optimistic"` \| `"undoable"`                                                                           |                                                                                |
| hideText     | Allows to hide button text                                                                   | `boolean`                                                                                | `false`                                                                              |
| children     | Sets the button text                                                                         | `ReactNode`                                                                                | `"Delete"`                                                                           |
| icon         | Sets the icon component of the button                                                        | `ReactNode`                                                                                | [`<DeleteOutlined />`](https://ant.design/components/icon/)                          |
| danger       | Sets the danger status of the button                                                         | `boolean`                                                                                | `true`                                                                               |
| loading      | Sets the loading status of the button                                                        | `boolean`                                                                                | When the request is not completed, loading is `true`, when it completes it's `false` |
| metaData     | Metadata query for `dataProvider`                                                            | [`MetaDataQuery`](/api-references/interfaces.md#metadataquery)                                                            | {}                                                                                |

repository: kevinlabory/refine

repo_name: kevinlabory/refine


text:
# Semantic Breadcrumbs

[![Build Status](https://travis-ci.org/pagespeed-io/semantic-breadcrumbs.svg?branch=master)](https://travis-ci.org/pagespeed-io/semantic-breadcrumbs)

**Semantic Breadcrumbs** creates HTML markup for breadcrumbs.
See the Google Developers article for more detail:
https://developers.google.com/structured-data/breadcrumbs

The output format is **RDFa**.

## Usage

```ruby
require 'semantic-breadcrumbs'

@b = SemanticBreadcrumbs.new

breadcrumbs = @b.breadcrumbs(
  [
    { href: 'https://example.com/arts',
      name: 'Arts' },
    { href: 'https://example.com/arts/books',
      name: 'Books' },
    { href: 'https://example.com/arts/books/poetry',
      name: 'Poetry' }
  ]
)

puts breadcrumbs

# <ol vocab="http://schema.org/" typeof="BreadcrumbList">
#   <li property="itemListElement" typeof="ListItem">
#     <a property="item" typeof="WebPage"
#         href="https://example.com/arts">
#       <span property="name">Arts</span></a>
#     <meta property="position" content="1">
#   </li>
#   ›
#   <li property="itemListElement" typeof="ListItem">
#     <a property="item" typeof="WebPage"
#         href="https://example.com/arts/books">
#       <span property="name">Books</span></a>
#     <meta property="position" content="2">
#   </li>
#   ›
#   <li property="itemListElement" typeof="ListItem">
#     <a property="item" typeof="WebPage"
#         href="https://example.com/arts/books/poetry">
#       <span property="name">Poetry</span></a>
#     <meta property="position" content="3">
#   </li>
# </ol>
```

### Styling

The generated markup has a single CSS class on the outer most wrapper:
`<ol class='breadcrumbs'>`. We suggest to start with the following CSS
and adjust it to your needs:

```css
.breadcrumbs li {
  display: inline-block;
  list-style-type: none;
}

```

### Custom Divider

The divider is placed between the breadcrumbs as you can see in the example
above. The default is `›`.

You can override it when instantiating the `SemanticBreadcrumbs` object:

```ruby
SemanticBreadcrumbs.new(divider: '//')
```

## Contributing

It would be nice to support some more formats in addition to RDFA.

1. Fork the repository
2. Create a feature branch: `git checkout -b your-feature`
3. Add your changes
4. Push changes: `git push -u origin your-feature`
5. Submit a pull request

## License

This project is licensed under the **MIT license**. See the `LICENSE` file
for details.

repository: pagespeed-io/semantic-breadcrumbs

gha_language: Ruby

repo_name: pagespeed-io/semantic-breadcrumbs


text:
# Samples

This folder can be used to store example projects etc.
This folder is ignored for NPM in [.npmignore file](../.npmignore).

# Running package tests

You can store sample project here to run your packages tests on,
since Unity does not provide standalone package testing solution.

1. Create new Unity project
2. Import your package in manifest.json and mark it as testable:
```json
{
  "dependencies": {
    "com.3d-group.unity-simple-notifications": "https://github.com/3d-group/unity-simple-notifications.git"
  },
  "testables": [ "com.3d-group.unity-simple-notifications" ]
}
```

branch_name: refs/heads/main


text:
# rpi-swarm

Raspberry Pi compatible Docker image with [Docker Swarm](https://github.com/docker/swarm).

Run all the commands from within the project root directory.

### Build Details
- [Source Project Page](https://github.com/hypriot)
- [Source Repository](https://github.com/hypriot/rpi-swarm)
- [Dockerfile](https://github.com/hypriot/rpi-swarm/blob/master/Dockerfile)
- [DockerHub] (https://registry.hub.docker.com/u/hypriot/rpi-swarm/)

#### Build the Docker Image
```bash
make build
```

#### Run the Docker Image and get the version of the installed `Docker Swarm`
```bash
make version
```

#### Push the Docker Image to the Docker Hub
* First use a `docker login` with username, password and email address
* Second push the Docker Image to the official Docker Hub

```bash
make push
```

## License

The MIT License (MIT)

Copyright (c) 2015 Hypriot

repository: alexellis/rpi-swarm

repo_name: alexellis/rpi-swarm