Authorisation processes

A page detailing the authorisation processes for various outgoing communications.

{{ConstitutionalNumbering|

Press releases
[Note 1: This section replaced the starting a press release standard.]

[Note 2: unless a writer has responsibilities in subsequent subsections, their responsibilities end once the requirements of subsection (3) have been met.]


 * 1) Press releases
 * 2) may be commenced and written by any member of the Pirate Party, and
 * 3) must adhere to the Press Release Guide.
 * 4) Press releases must address matters relevant to
 * 5)  any of the Pirate Party's primary policies, or
 * 6) any of the Pirate Party's secondary policies, or
 * 7) any issue that falls within the scope of the Pirate Party's activities.
 * 8) Prior to authorisation and issue, press releases must
 * 9) be made available using the Pirate Party's Etherpad instance (http://pad.pirateparty.org.au), and
 * 10) have the URL of the specific pad
 * 11) emailed to the Press Team ([mailto:pressteam@pirateparty.org.au pressteam@pirateparty.org.au]), and
 * 12) posted in #ppau-press on IRC.
 * 13) Completed draft press releases must be proofread and then authorised by
 * 14) the Press Officer and at least one Councillor, or
 * 15) at least two Councillors.
 * 16) For the purposes of subsection (4) if the Press Officer is a Councillor, press releases must also be proofread by another Councillor.
 * 17) A press release authorised for issue must
 * 18) only be issued by
 * 19) the Press Officer, or
 * 20) any Councillor, and
 * 21) be published on the Party's website by
 * 22) the issuing person if that person has sufficient access to the website, or
 * 23) another person with sufficient access to the website who is directed to do so by the issuing person.
 * 24) Nothing in this section obliges either the Press Officer or any Councillor to authorise or issue a press release.
 * 25) This section also applies as much as is appropriate to
 * 26) joint press releases, and
 * 27) endorsement of press releases written or issued by third parties.

Submissions to consultations, inquiries, reviews, etc
[Note: unless a writer has responsibilities in subsequent subsections, their responsibilities end once the requirements of subsection (5) have been met.]

}}
 * 1) Submissions:
 * 2) may be commenced and written by any member of the Pirate Party, and
 * 3) must adhere to the  submissions standard.
 * 4) Submissions must address matters relevant to
 * 5) any of the Pirate Party's primary policies, or
 * 6) any of the Pirate Party's secondary policies, or
 * 7) any issue that falls within the scope of the Pirate Party's activities.
 * 8) Prior to authorisation a submission must be written using any of the following as appropriate
 * 9) Overleaf (http//overleaf.com), or
 * 10) Google Docs http://docs.google.com, or
 * 11) the Pirate Party's Etherpad instance (http://pad.pirateparty.org.au).
 * 12) For the purposes of subsection (3)
 * 13) 'appropriate' shall be determined with reference to the requirements of the body receiving the submission and:
 * 14) if the body prefers PDF files Overleaf should be used, or
 * 15) if the body prefers Microsoft Word documents Google Docs should be used, or
 * 16) if the body prefers some other form of submission Etherpad should be used, and
 * 17) the Inquiries Officer may make their own determination of what is appropriate and make arrangements in accordance with that determination.
 * 18) Prior to authorisation a 'read and edit' URL of the submission must be
 * 19) emailed to the Policy Development Committee ([mailto:policydev@pirateparty.org.au policydev@pirateparty.org.au]), and
 * 20) posted in #ppau-pdc on IRC, and
 * 21) posted on the forum under the appropriate category (http://discuss.pirateparty.org.au).
 * 22) Completed draft submissions must be proofread by
 * 23) the Inquiries Officer and one Councillor, or
 * 24) the Inquiries Officer and one member of the Policy Development Committee, or
 * 25) one Councillor and one member of the Policy Development Committee, or
 * 26) two Councillors.
 * 27) Submissions must be explicitly authorised for submission to the relevant body
 * 28) only after being proofread in accordance with subsection (6), and
 * 29) only by
 * 30) the Inquiries Officer and one Councillor, or
 * 31) two Councillors.
 * 32) One person occupying multiple positions cannot alone satisfy the requirements of either subsection (6) or subsection (7).
 * 33) An authorised submission must
 * 34) only be submitted by
 * 35) the Inquiries Officer, or
 * 36) a Councillor, and
 * 37) be uploaded as a PDF file to an appropriate place on the website, and
 * 38) be listed on the appropriate page of the website (https://pirateparty.org.au/submissions).
 * 39) Nothing in this section obliges either the Inquiries Officer or any Councillor to authorise a submission.
 * 40) This section also applies as much as is appropriate to:
 * 41) joint submissions, and
 * 42) endorsement of submissions written or issued by third parties.
 * 43) Nothing in this section prohibits members of the Pirate Party from submitting their own personal submissions provided the submission does not purport to be written or endorsed by the Pirate Party without having first complied with the requirements of this section.