From 33f3c7a57a42f273d9856c7be7b0945b45723ae7 Mon Sep 17 00:00:00 2001 From: x1y <23239177+x1y@users.noreply.github.com> Date: Wed, 9 Oct 2024 19:45:24 +0200 Subject: [PATCH] Converted adoc to md --- content/blog/{_index.adoc => _index.md} | 2 +- ...{Brand_and_logo.adoc => Brand_and_logo.md} | 32 +- content/community/Rules.adoc | 72 --- content/community/Rules.md | 72 +++ content/community/_index.adoc | 186 ------- content/community/_index.md | 100 ++++ ..._chat_notes.adoc => bridged_chat_notes.md} | 36 +- content/community/partner_projects.adoc | 63 --- content/community/partner_projects.md | 63 +++ .../{philosophy.adoc => philosophy.md} | 2 +- content/contests/{_index.adoc => _index.md} | 2 +- .../Accessories_Step_by_Step_Guides.adoc | 53 -- .../Accessories_Step_by_Step_Guides.md | 52 ++ .../Clusterboard/Further_information/FAQ.adoc | 23 - .../Clusterboard/Further_information/FAQ.md | 22 + .../{Revisions.adoc => Revisions.md} | 1 - .../documentation/QuartzPro64/Hardware.adoc | 1 + .../Unsorted/Discard/Project.txt | 456 ------------------ .../documentation/Unsorted/PhoenixCard.adoc | 2 +- themes/pinetheme/assets/css/style.css | 1 + 20 files changed, 349 insertions(+), 892 deletions(-) rename content/blog/{_index.adoc => _index.md} (92%) rename content/community/{Brand_and_logo.adoc => Brand_and_logo.md} (93%) delete mode 100644 content/community/Rules.adoc create mode 100644 content/community/Rules.md delete mode 100644 content/community/_index.adoc create mode 100644 content/community/_index.md rename content/community/{bridged_chat_notes.adoc => bridged_chat_notes.md} (61%) delete mode 100644 content/community/partner_projects.adoc create mode 100644 content/community/partner_projects.md rename content/community/{philosophy.adoc => philosophy.md} (97%) rename content/contests/{_index.adoc => _index.md} (94%) delete mode 100644 content/documentation/Accessories/Accessories_Step_by_Step_Guides.adoc create mode 100644 content/documentation/Accessories/Accessories_Step_by_Step_Guides.md delete mode 100644 content/documentation/Clusterboard/Further_information/FAQ.adoc create mode 100644 content/documentation/Clusterboard/Further_information/FAQ.md rename content/documentation/Clusterboard/Further_information/{Revisions.adoc => Revisions.md} (99%) delete mode 100644 content/documentation/Unsorted/Discard/Project.txt diff --git a/content/blog/_index.adoc b/content/blog/_index.md similarity index 92% rename from content/blog/_index.adoc rename to content/blog/_index.md index 6676df5e..479ab4fb 100644 --- a/content/blog/_index.adoc +++ b/content/blog/_index.md @@ -5,4 +5,4 @@ draft: false description: --- -The latest blog posts from the PINE64 community bringing the latest news. \ No newline at end of file +The latest blog posts from the PINE64 community bringing the latest news. diff --git a/content/community/Brand_and_logo.adoc b/content/community/Brand_and_logo.md similarity index 93% rename from content/community/Brand_and_logo.adoc rename to content/community/Brand_and_logo.md index 486a93d3..aecae3ff 100644 --- a/content/community/Brand_and_logo.adoc +++ b/content/community/Brand_and_logo.md @@ -15,9 +15,9 @@ The brand and logo were first trademarked in 2015 by then Pine Microsystems Inc. We are highly protective of our trademark and copyrights, and will seek any and all legal measures to enforce guidelines contained in this document. -image:/documentation/images/Pine64logowriting.jpg[PINE64 pinecone logo with brand name,title="PINE64 pinecone logo with brand name",width=500] +{{
}} -== 1. Presentation and typography +## 1. Presentation and typography The PINE64 project logotype is always capitalised: PINE64 The logotype always uses high tonal contrast, all capital letters and is preceded by the logo. @@ -35,7 +35,7 @@ PINE64 logo colors in HTML notation, top to bottom: Other variants, including all-white logo and typography on black or transparent background, are in use and permitted for non-commercial usage. Other colour variations are also permitted for non-commercial use. Other variants than the official logotype may be used for commercial use following an inquiry with PINE64 Community representatives and/ or designated Pine Store Ltd. staff members. -=== 1.1. Slogan(s), look and branding +### 1.1. Slogan(s), look and branding The PINE64 community slogan is “Open. Friendly. Community Driven”. PINE64 hardware packaging uses the tagline “Open Sesame”. @@ -43,14 +43,14 @@ PINE64 hardware packaging uses the tagline “Open Sesame”. PINE64 uses a distinct brand look which makes use of the original colour scheme of the pine cone logo (see section 1.) in conjunction with black, grey and white as background colours. The distinct look of PINE64 organization’s (pine64.org) website, the official forum (forum.pine64.org) and the Pine Store’s (pine64.com) website is restricted to official PINE64 portals and community services. It may not be copied or imitated by community run services such as forums or websites. -=== 1.2. PINE64 logo kit +### 1.2. PINE64 logo kit We provide a PINE64 logo media kit in .zip format containing a range of acceptable logo variations in SVG file format. The .zip file also contains a READ ME document with detailed information and instructions. -* https://wiki.pine64.org/wiki/File:Pine64-logos.zip[Media kit in .zip format] +* [Media kit in .zip format](https://wiki.pine64.org/wiki/File:Pine64-logos.zip) -=== 1.3. Branding on devices +### 1.3. Branding on devices We choose to keep PINE64 branding on our devices to a minimum. Our design follows our inherent ideology that devices we sell belong to the end-users, not to us. @@ -61,13 +61,13 @@ The PINE64 pinecone is also discreetly placed between the torch and camera on th Packaging of PINE64 devices varies in branding implementation, ranging from plain white boxes from recycled materials to the hallmark “Open Sesame” tagline alongside PINE64 logotype from recycled cardboard. The PinePhone also uses a distinct “PINEPHONE” logotype written in Good Times Regular font. -== 2. Non-commercial usage +## 2. Non-commercial usage Any and all derivatives of the PINE64 brand name and pinecone logo, including alterations to the original logo per bounds in section 1, are permitted for non-commercial use. Use of the logo and brand name is permitted in communities or projects, as long as it is clearly denoted that the software, community, portal, website, subreddit, etc., does not belong to and is not administered by PINE64 community nor Pine Store Ltd. -=== 2.1. Examples of appropriate non-commercial usage +### 2.1. Examples of appropriate non-commercial usage * Including PINE64 logo and brand name in open source software, offered freely and free of charge, written for PINE64 devices * Including PINE64 logo and brand name on publicly available 3D files offered freely and free of charge @@ -77,7 +77,7 @@ Use of the logo and brand name is permitted in communities or projects, as long * Any alterations to the logotype for private or community use - for example as freely distributed wallpapers, icons, emotes, etc. * Including PINE64 slogan and distinct brand look in freely distributed and royalty free software -=== 2.2. Restrictions to non-commercial usage +### 2.2. Restrictions to non-commercial usage The PINE64 logo and logotype may not, under any circumstances, be used or associated with any software or hardware projects not related to PINE64 hardware. Our brand name look and slogan (see section 1.1) are also restricted to use on official PINE64 websites, chats, forums and hardware (but allowed on freely distributed software for PINE64 devices). @@ -86,7 +86,7 @@ We reserve the right to request the PINE64 logo and logotype be removed if a non The PINE64 logo and logotype may not, under any circumstances, be used to mislead existing or prospectus PINE64 community members into believing that software, social media account, community service, website, forum, subreddit, chat, social media account, etc., is representative of or run by official spokespersons of the PINE64 community or the Pine Store Ltd. staff members. The PINE64 logo and brand name may not be used in a way that creates a false impression that a product or business is endorsed, sponsored by or associated with the PINE64 community or Pine Store Ltd. -== 3. Commercial, affiliate and sponsorship usage +## 3. Commercial, affiliate and sponsorship usage Commercial use of the logo, logotype or brand name, as well as any derivatives or alterade logotypes, is not permitted without prior consent of Pine Store Ltd. This means that any software project, merchandise vendor or community endeavour that seeks to turn a financial profit based on the PINE64 brand name needs to first acquire appropriate consent from Pine Store Ltd. @@ -96,7 +96,7 @@ Projects, events or other engagements sponsored by PINE64 Community need to clea We will seek any and all legal measures to enforce compliance with the use of all our copyrights and the PINE64 trademark. -=== 3.1. Commercial and affiliate use or as part of sponsorship +### 3.1. Commercial and affiliate use or as part of sponsorship Any use of the PINE64 logo and brand name in digital form should adhere to guidelines in section 1. PINE64 partner projects, business partners, affiliate programs, sponsored programs or events, etc. are welcome to reach out to PINE64 representatives and/ or Pine Store Ltd. staff members for graphical assets (e.g. the logo and logotype) and to consult usage. @@ -106,12 +106,12 @@ The PINE64 logo and brand name must appear less prominent than the business’ o In the case of sponsorship, sponsors are asked to include an identification of PINE64’s affinity with the said sponsored project. This includes, but is not limited to, placing PINE64 logo and/ logotype in a “Sponsors” section or being processed by “Sponsored by” to indicate sponsorship. -=== 3.2 Applying for inclusion of branding in commercial application or sponsorship +### 3.2 Applying for inclusion of branding in commercial application or sponsorship For business, partnership or sponsorship inquiries please email: info@pine64.org Applications are reviewed on a case-by-case basis. -=== 3.3 Examples of appropriate commercial, sponsorship or affiliate usage +### 3.3 Examples of appropriate commercial, sponsorship or affiliate usage * Including PINE64 logo and brand name on a dedicated “sponsors” page or in a designated “sponsors” section of a webpage * Including PINE64 logo and brand name on a partner project’s website, with preceding text to the effect of “in partnership with PINE64” or in a designated “partners” section @@ -120,12 +120,12 @@ Applications are reviewed on a case-by-case basis. * Including PINE64 logo and brand name in paid software and associated promotional materials (e.g. on business’ website), to indicate compatibility with PINE64 hardware * Including PINE64 logo as part of promotional materials by partner projects or affiliated businesses upon prior agreement -=== 3.4 Restrictions to commercial usage +### 3.4 Restrictions to commercial usage No business, sponsored project or affiliate may use the PINE64 logo and logotype to mislead existing or prospectus PINE64 community members into believing that software, community service, social media account, website, forum, subreddit, chat, social media account, etc., is representative of or run by official spokespersons of the PINE64 community or the Pine Store Ltd. staff members. We reserve the right to request a sponsored event, affiliate program, business or partner project to remove PINE64 branding under particular circumstances. -== 4. Creation of derivative logos and logotypes +## 4. Creation of derivative logos and logotypes Anyone is allowed to create PINE64 derivatives for personal or community usage. This extends to any form of artwork, community-made mockups or any other clearly identifiable community-activity that does not mislead existing or prospectus community members to believe it is PINE64 official material. @@ -133,4 +133,4 @@ Derivatives of the PINE64 logo and banding are permitted for non-commercial usag Derivatives of PINE64 branding may still be subject to our copyright and as such need to adhere to restrictions outlined in section 2.2. We may request the removal of PINE64 logo or logotype derivatives if we feel that they are misused, used for commercial purposes or result in damage to our brand name. -We strongly advise anyone willing to create a derivative of our logo or brand name to reach out to a PINE64 Community associate or a Pine Store Ltd. staff member. \ No newline at end of file +We strongly advise anyone willing to create a derivative of our logo or brand name to reach out to a PINE64 Community associate or a Pine Store Ltd. staff member. diff --git a/content/community/Rules.adoc b/content/community/Rules.adoc deleted file mode 100644 index 992bb39c..00000000 --- a/content/community/Rules.adoc +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: "PINE64 Community Rules and Code of Conduct" -draft: false -menu: - docs: - title: - parent: "General" - identifier: "General/Rules" - weight: ---- - -These rules apply to all official PINE64 platforms and protocols facilitating social interactions, and will be enforced by moderators at all times. Failure to comply with these rules may result in a temporary or permanent ban from all PINE64 community platforms. If deemed necessary, a permanent ban can be issued without a prior notice. In extreme circumstances - such as those involving threats or hate speech - the Pine Store reserves the right to deny service to the offending party and notify local or regional authorities. - -== Foreword - -We trust in people's common sense. There are intangible subtleties in human interactions that make a behaviour ‘OK’ at one time but not at others, and no artificial list of social-engagement rules, no matter how extensive, could capture this complexity accurately. To this end, we ask that you stay mindful of people’s sensitivities and address others respectfully at all times. -Moderators are tasked with facilitating discussion, maintaining order and keeping the debate on-topic. They also have the necessary tools to enforce these rules at their discretion. The official forum, subreddit(s) and some chat protocols have systems dedicated to issuing warnings. In the absence of a formal moderation system, a moderator may reach out to a user directly via PM/ DM to issue a warning. In extreme circumstances, moderation actions will be taken without issuing prior warnings. -Lastly, keep in mind that moderators have no power to make someone a friendly or nice human being (this was the said person's parents' job). Being an unsympathetic or crude person is not an actionable offense from a moderation standpoint. Hint: some chat protocols also give you the option to mute messages from select users. - -== 1) General Rules - -* *Read the rules* before posting on the forum, the subreddit(s) or engaging in the chat(s). -* *Be respectful to other community members.* Discourse is always a good thing, and sharing your opinions and insight is valuable to us and our user base. But how you engage with others is just as important as the ideas you share. We pride ourselves on this being a friendly community, and we will take measures to maintain it this way. -* *Stay on topic.* If a topic is set for a forum thread or discussion group/ channel then stick to it. Want to talk about something else? - there is an #offtopic chat on our Discord and IRC, and a Community and Events section on the forums. -* *Write in English.* Unless the subforum or chat specifies a different language, please stick to using English. There are numerous unofficial PINE64-product forums and chats catering to end-users who prefer communicating in a different language. If there isn’t a discussion group in your native tongue, why not start one? -* *Watch your language.* Some of our community members are younger than others; expletives are not necessary to communicate your viewpoints or experience. Please avoid using curse words, thank you. -* Use the search feature before posting or asking. The official PINE64 form and various chat protocols offer a search feature. If you’re looking for information, before you ask, try searching for the key words related to your query first - it is likely the topic you’re interested in has already been discussed. -* *Obey platform-specific rules.* Some communication platforms may have additional rules in place. For instance, you may not ping everyone in Discord chat using the @everyone function or paste lengthy log print-outs in Matrix. Where applicable, chat or forum-specific rules need to be followed. -* *Ask If you are unsure.* If you are unsure about where to best ask your question, or you are not sure if the topic is compliant with our rules and code of conduct, then please first reach out to someone on our moderation team. Moderators are always clearly demarcated on the various social interaction platforms. -* *Stay on-topic.* The chats and forum have clearly designated topics related to hardware and software. It is expected that you stay on-topic in the individual chats or forum sub-sections, and that you refrain from posting off-comments that divert the discussion towards an irrelevant subject (sometimes called 'hijacking'). Some chat platforms offer an 'off-topic' channel, and here on the forum there is a 'community' sub-section, where subjects not directly related to hardware and software can be discussed (granted it does not violate any of the rules contained within this post). - -== 2) Form and Content - -* *Use standard formatting.* You should adhere to platform standard formatting, such as default font, font-size, font-colour, line spacing, etc. Content written in all CAPS or in rainbow colours is at a risk of being permanently removed by moderators. Making your writing easily legible also helps with getting your query answered. -* *Describe your problem* and don’t ask if you may ask a question. When stating your query, make sure to describe the issues you’re experiencing and the trouble-shooting steps you already attempted. In the chat: don’t ask for permission to ask, just state your problem. If your question is directed at a particular person, make sure to use @ their username or handle to get their attention. -* *Do not post any knowingly false or inaccurate material.* This is self-explanatory. Posting information that is false may get you suspended or banned from our platforms. -* *Do not post or distribute copyrighted or stolen material.* Links to stolen material, be it images, video, plagiarized written content or pirated software will be removed immediately. Posting such content may result in a temporary or permanent suspension from all our PINE64 community platforms. -* *Signatures are allowed on the forum.* Please be mindful that your signature has to comply with all rules, just as any other content you submit on the official forum. You may, however, be asked by a member of the moderation team to alter your forum signature if it affects legibility of posted content. -* *No advertisements of non-FOSS and commercial products.* You are welcome to let people know about your FOSS project, as well as any FOSS/OSH hardware project, but other types of advertisements will be removed immediately. If deemed as spam, posting such content may result in a temporary or permanent ban on all our platforms. -* *Images and other media are best shared via links.* It is always best to upload your videos or images and link them on the forum or in the chats. While attachments can be uploaded on the forum, they are limited to 2MB total per post. The different chat protocols handle attachments differently, which may lead to the content not displaying across the chat protocol bridge. -* *No politics, religion or other sensitive topics* is permissible on any of our platforms. Simply put, there are better places to discuss such topics. This rule also applies to #OffTopic chat and Community and Events subforum. Posts referring to such subject matter will be removed and may result in a warning, and even a temporary ban if the activity does not cease. -* *No offensive nicknames, account names or online handles.* If your online handle includes curse words, inappropriate imagery, inappropriate or offensive mockery, or otherwise relates to sensitive subject matter you may be asked to change your handle (or the Admin may change it for you). Not complying with the request will be met with a warning, followed by a ban on all platforms. -* *Moderation of heated discussions.* In general, if a discussion is heated (and doesn’t violate any of our rules or general code of conduct) but productive, then the moderation team will not intervene. There are, however, instances where a heated discussion is either moot or likely to take a turn for the worse; in such an event a moderator may ask for a halt to the conversation. One moderator may deem a heated discussion to be in a good spirit, while another moderator may ask for the discussion to cease. The decision to stop the conversation is completely at the moderator’s discretion. - -== 3) Spam, Illegal and Inappropriate Content - -* *Automated spam (bots).* We employ an automated spam protection as well as other measures that prevent new accounts from spamming the official PINE64 forum. New user’s posts need to be manually approved by the moderation team for a period of 3 days. Automated spam in the chats needs to be reported to the moderation team. We always strive to remove the spam and the bots as soon as possible. An IP associated with spam bots will be IP-banned. -* *Spamming by end-users.* Accidental or uninformed ‘spam’ - such as, for instance, pastes of lengthy log print-outs - may be removed by moderators, if it affects legibility of the chat. Use pastebin or similar to share a link with logs. -* *Trolling.* Trolling is defined as posting inflammatory messages to cause havoc in the community. Posting such content will result in a temporary or permanent ban from all PINE64 community platforms. -* *Illegal* content of any kind will be removed immediately and lead to permanent ban on all our platforms. If you encounter any illegal content on the official forum, subreddit or in the chat please report it immediately to the moderation team. In instances where it is applicable, the content itself and the associated account which submitted the post will be reported to the relevant regulator or local authorities. -* *Sexual content.* Any form of sexual content - in written, video or photographic format - is not allowed on our platforms. Posting sexual content will result in an instant ban on all PINE64 platforms. - -== 4) Threats, Hate Speech, Bullying and Harassment - -* *Threats of any kind* will result in an instant ban from all PINE64 platforms. Threats made may also be reported to local or regional authorities by the moderation team, if they are deemed legitimate or/ and a cause of psychological distress. -* *Any form of hate speech* will result in an instantaneous ban on all our platforms and may be reported to local or regional authorities by the moderation team. Hate speech is a crime in most of the civilized world. -* *Discrimination of any kind.* Any forms or discrimination including, but not limited to, misogyny, sexism, racism, xeniophobia and agism will result in an instant ban across all of PINE64 platforms. -* *Bullying.* We will not stand for bullying of any kind on our community communication platforms. Every community member can rest assured that they can express themselves and their viewpoints without being made fun of or ridiculed. If you have been the subject of or witnessed to behaviour, please report it to the moderation team. Bullying will result in an instant ban on all PINE64 platforms. -* *Harassment*, defined as any behaviour aimed at intimidating or humiliating another community member, needs to be immediately reported to the moderation team. If moderators determine that the offending party’s actions were designed to purposefully humiliate and intimidate another community member, then a subsequent ban from all PINE64 platforms will be enforced. -* *Slander* of fellow community members, Pine Store contractors and moderation team members will result in warning and, if the situation is not rectified, a permanent ban spanning all PINE64 social platforms. Slander is defined as: a knowingly false statement designed to damage reputation. - -== 5) Privacy - -* *Private details.* Any materials made public on purpose or by accident which contains private or otherwise identifying information will be removed from our platform without prior notice. We define private details as information that includes, but is not limited to, phone numbers, emails, shipping addresses or IP address. For example: if you post a video of an unboxing where you inadvertently show your shipping address, the moderation team will pull the video down to preserve your privacy. If you encounter such content, please notify the moderation team. -* *Materials under NDA or Embargo.* Any confidential materials issued under an NDA are subject to removal from our community platforms without notifying the original poster. Such materials may include documents (e.g. schematics), schematics of unreleased devices, images of prototypes or written descriptions of unannounced devices. - -== 6) Software Feedback - -* *Software feedback.* We and our partner projects value your feedback, but this feedback needs to be communicated in a structured and respectful manner. When addressing developers on our platforms please make sure to formulate your feedback and criticism in a constructive manner. Everyone has their favorite distribution, desktop environment and software implementations. This, however, doesn’t mean that alternatives to your favorite software should be taunted or ridiculed; ultimately, everyone is working towards a common goal and everyone’s work ought to be respected. In short, stay respectful of people’s work. -* *Software feature requests*, similarly to feedback, should be relayed in a respectful and considerate manner. Keep in mind that many developers working on PINE64 hardware do so in their spare time, on limited resources and are offering their software as a service to this community. No user has ‘a right to demand’ inclusion of software features. -* *Reporting bugs.* The PINE64 official forum and chats aren’t the ideal place to report bugs or other software issues. You are, of course, welcome to notify developers of the issues you encountered on the forum or in the chats, but ultimately this should be accompanied by submission of a bug report on GitHub and the software project’s forum. -* *Adhere to partner project’s rules* when engaging with their community on their social interaction platforms. Partner project’s forums and chats may be subject to different communication rules than our own; we ask you to stay mindful of this when discussing software designed for our devices outside of the PINE64 community platform. \ No newline at end of file diff --git a/content/community/Rules.md b/content/community/Rules.md new file mode 100644 index 00000000..6dc40b5d --- /dev/null +++ b/content/community/Rules.md @@ -0,0 +1,72 @@ +--- +title: "PINE64 Community Rules and Code of Conduct" +draft: false +menu: + docs: + title: + parent: "General" + identifier: "General/Rules" + weight: +--- + +These rules apply to all official PINE64 platforms and protocols facilitating social interactions, and will be enforced by moderators at all times. Failure to comply with these rules may result in a temporary or permanent ban from all PINE64 community platforms. If deemed necessary, a permanent ban can be issued without a prior notice. In extreme circumstances - such as those involving threats or hate speech - the Pine Store reserves the right to deny service to the offending party and notify local or regional authorities. + +## Foreword + +We trust in people’s common sense. There are intangible subtleties in human interactions that make a behaviour ‘OK’ at one time but not at others, and no artificial list of social-engagement rules, no matter how extensive, could capture this complexity accurately. To this end, we ask that you stay mindful of people’s sensitivities and address others respectfully at all times. +Moderators are tasked with facilitating discussion, maintaining order and keeping the debate on-topic. They also have the necessary tools to enforce these rules at their discretion. The official forum, subreddit(s) and some chat protocols have systems dedicated to issuing warnings. In the absence of a formal moderation system, a moderator may reach out to a user directly via PM/ DM to issue a warning. In extreme circumstances, moderation actions will be taken without issuing prior warnings. +Lastly, keep in mind that moderators have no power to make someone a friendly or nice human being (this was the said person’s parents' job). Being an unsympathetic or crude person is not an actionable offense from a moderation standpoint. Hint: some chat protocols also give you the option to mute messages from select users. + +## 1) General Rules + +* **Read the rules** before posting on the forum, the subreddit(s) or engaging in the chat(s). +* **Be respectful to other community members.** Discourse is always a good thing, and sharing your opinions and insight is valuable to us and our user base. But how you engage with others is just as important as the ideas you share. We pride ourselves on this being a friendly community, and we will take measures to maintain it this way. +* **Stay on topic.** If a topic is set for a forum thread or discussion group/ channel then stick to it. Want to talk about something else? - there is an #offtopic chat on our Discord and IRC, and a Community and Events section on the forums. +* **Write in English.** Unless the subforum or chat specifies a different language, please stick to using English. There are numerous unofficial PINE64-product forums and chats catering to end-users who prefer communicating in a different language. If there isn’t a discussion group in your native tongue, why not start one? +* **Watch your language.** Some of our community members are younger than others; expletives are not necessary to communicate your viewpoints or experience. Please avoid using curse words, thank you. +* Use the search feature before posting or asking. The official PINE64 form and various chat protocols offer a search feature. If you’re looking for information, before you ask, try searching for the key words related to your query first - it is likely the topic you’re interested in has already been discussed. +* **Obey platform-specific rules.** Some communication platforms may have additional rules in place. For instance, you may not ping everyone in Discord chat using the @everyone function or paste lengthy log print-outs in Matrix. Where applicable, chat or forum-specific rules need to be followed. +* **Ask If you are unsure.** If you are unsure about where to best ask your question, or you are not sure if the topic is compliant with our rules and code of conduct, then please first reach out to someone on our moderation team. Moderators are always clearly demarcated on the various social interaction platforms. +* **Stay on-topic.** The chats and forum have clearly designated topics related to hardware and software. It is expected that you stay on-topic in the individual chats or forum sub-sections, and that you refrain from posting off-comments that divert the discussion towards an irrelevant subject (sometimes called 'hijacking'). Some chat platforms offer an 'off-topic' channel, and here on the forum there is a 'community' sub-section, where subjects not directly related to hardware and software can be discussed (granted it does not violate any of the rules contained within this post). + +## 2) Form and Content + +* **Use standard formatting.** You should adhere to platform standard formatting, such as default font, font-size, font-colour, line spacing, etc. Content written in all CAPS or in rainbow colours is at a risk of being permanently removed by moderators. Making your writing easily legible also helps with getting your query answered. +* **Describe your problem** and don’t ask if you may ask a question. When stating your query, make sure to describe the issues you’re experiencing and the trouble-shooting steps you already attempted. In the chat: don’t ask for permission to ask, just state your problem. If your question is directed at a particular person, make sure to use @ their username or handle to get their attention. +* **Do not post any knowingly false or inaccurate material.** This is self-explanatory. Posting information that is false may get you suspended or banned from our platforms. +* **Do not post or distribute copyrighted or stolen material.** Links to stolen material, be it images, video, plagiarized written content or pirated software will be removed immediately. Posting such content may result in a temporary or permanent suspension from all our PINE64 community platforms. +* **Signatures are allowed on the forum.** Please be mindful that your signature has to comply with all rules, just as any other content you submit on the official forum. You may, however, be asked by a member of the moderation team to alter your forum signature if it affects legibility of posted content. +* **No advertisements of non-FOSS and commercial products.** You are welcome to let people know about your FOSS project, as well as any FOSS/OSH hardware project, but other types of advertisements will be removed immediately. If deemed as spam, posting such content may result in a temporary or permanent ban on all our platforms. +* **Images and other media are best shared via links.** It is always best to upload your videos or images and link them on the forum or in the chats. While attachments can be uploaded on the forum, they are limited to 2MB total per post. The different chat protocols handle attachments differently, which may lead to the content not displaying across the chat protocol bridge. +* **No politics, religion or other sensitive topics** is permissible on any of our platforms. Simply put, there are better places to discuss such topics. This rule also applies to #OffTopic chat and Community and Events subforum. Posts referring to such subject matter will be removed and may result in a warning, and even a temporary ban if the activity does not cease. +* **No offensive nicknames, account names or online handles.** If your online handle includes curse words, inappropriate imagery, inappropriate or offensive mockery, or otherwise relates to sensitive subject matter you may be asked to change your handle (or the Admin may change it for you). Not complying with the request will be met with a warning, followed by a ban on all platforms. +* **Moderation of heated discussions.** In general, if a discussion is heated (and doesn’t violate any of our rules or general code of conduct) but productive, then the moderation team will not intervene. There are, however, instances where a heated discussion is either moot or likely to take a turn for the worse; in such an event a moderator may ask for a halt to the conversation. One moderator may deem a heated discussion to be in a good spirit, while another moderator may ask for the discussion to cease. The decision to stop the conversation is completely at the moderator’s discretion. + +## 3) Spam, Illegal and Inappropriate Content + +* **Automated spam (bots).** We employ an automated spam protection as well as other measures that prevent new accounts from spamming the official PINE64 forum. New user’s posts need to be manually approved by the moderation team for a period of 3 days. Automated spam in the chats needs to be reported to the moderation team. We always strive to remove the spam and the bots as soon as possible. An IP associated with spam bots will be IP-banned. +* **Spamming by end-users.** Accidental or uninformed ‘spam’ - such as, for instance, pastes of lengthy log print-outs - may be removed by moderators, if it affects legibility of the chat. Use pastebin or similar to share a link with logs. +* **Trolling.** Trolling is defined as posting inflammatory messages to cause havoc in the community. Posting such content will result in a temporary or permanent ban from all PINE64 community platforms. +* **Illegal** content of any kind will be removed immediately and lead to permanent ban on all our platforms. If you encounter any illegal content on the official forum, subreddit or in the chat please report it immediately to the moderation team. In instances where it is applicable, the content itself and the associated account which submitted the post will be reported to the relevant regulator or local authorities. +* **Sexual content.** Any form of sexual content - in written, video or photographic format - is not allowed on our platforms. Posting sexual content will result in an instant ban on all PINE64 platforms. + +## 4) Threats, Hate Speech, Bullying and Harassment + +* **Threats of any kind** will result in an instant ban from all PINE64 platforms. Threats made may also be reported to local or regional authorities by the moderation team, if they are deemed legitimate or/ and a cause of psychological distress. +* **Any form of hate speech** will result in an instantaneous ban on all our platforms and may be reported to local or regional authorities by the moderation team. Hate speech is a crime in most of the civilized world. +* **Discrimination of any kind.** Any forms or discrimination including, but not limited to, misogyny, sexism, racism, xeniophobia and agism will result in an instant ban across all of PINE64 platforms. +* **Bullying.** We will not stand for bullying of any kind on our community communication platforms. Every community member can rest assured that they can express themselves and their viewpoints without being made fun of or ridiculed. If you have been the subject of or witnessed to behaviour, please report it to the moderation team. Bullying will result in an instant ban on all PINE64 platforms. +* **Harassment**, defined as any behaviour aimed at intimidating or humiliating another community member, needs to be immediately reported to the moderation team. If moderators determine that the offending party’s actions were designed to purposefully humiliate and intimidate another community member, then a subsequent ban from all PINE64 platforms will be enforced. +* **Slander** of fellow community members, Pine Store contractors and moderation team members will result in warning and, if the situation is not rectified, a permanent ban spanning all PINE64 social platforms. Slander is defined as: a knowingly false statement designed to damage reputation. + +## 5) Privacy + +* **Private details.** Any materials made public on purpose or by accident which contains private or otherwise identifying information will be removed from our platform without prior notice. We define private details as information that includes, but is not limited to, phone numbers, emails, shipping addresses or IP address. For example: if you post a video of an unboxing where you inadvertently show your shipping address, the moderation team will pull the video down to preserve your privacy. If you encounter such content, please notify the moderation team. +* **Materials under NDA or Embargo.** Any confidential materials issued under an NDA are subject to removal from our community platforms without notifying the original poster. Such materials may include documents (e.g. schematics), schematics of unreleased devices, images of prototypes or written descriptions of unannounced devices. + +## 6) Software Feedback + +* **Software feedback.** We and our partner projects value your feedback, but this feedback needs to be communicated in a structured and respectful manner. When addressing developers on our platforms please make sure to formulate your feedback and criticism in a constructive manner. Everyone has their favorite distribution, desktop environment and software implementations. This, however, doesn’t mean that alternatives to your favorite software should be taunted or ridiculed; ultimately, everyone is working towards a common goal and everyone’s work ought to be respected. In short, stay respectful of people’s work. +* **Software feature requests**, similarly to feedback, should be relayed in a respectful and considerate manner. Keep in mind that many developers working on PINE64 hardware do so in their spare time, on limited resources and are offering their software as a service to this community. No user has ‘a right to demand’ inclusion of software features. +* **Reporting bugs.** The PINE64 official forum and chats aren’t the ideal place to report bugs or other software issues. You are, of course, welcome to notify developers of the issues you encountered on the forum or in the chats, but ultimately this should be accompanied by submission of a bug report on GitHub and the software project’s forum. +* **Adhere to partner project’s rules** when engaging with their community on their social interaction platforms. Partner project’s forums and chats may be subject to different communication rules than our own; we ask you to stay mindful of this when discussing software designed for our devices outside of the PINE64 community platform. diff --git a/content/community/_index.adoc b/content/community/_index.adoc deleted file mode 100644 index 4ae30e9d..00000000 --- a/content/community/_index.adoc +++ /dev/null @@ -1,186 +0,0 @@ ---- -title: "Community" -description: PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. -images: - - "/community/community_banner.png" -aliases: - - /web-irc/ # from pine64.com ---- - -{{< box style="themewhite pad" >}} - {{< box style="pad_s blueshadow" type="image" link="/img/slider_index_1.jpg" width="380" >}}{{}} - {{< box style="pad f50 rows" title="" content="markdown" >}} -**Welcome to the PINE64 community!** - -_PINE64_ has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. - -To become connected and involved with the community, please see the channel list below for a list of available channels and chat platforms. - {{}} -{{}} - - - -{{< box style="themewhite pad" >}} - {{< box style="pad f50 rows" title="" content="markdown" >}} -_PINE64_ is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [PINE A64](/documentation/Pine_A64) single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices. - -For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [article about our brand and logo](Brand_and_logo). - -The most important asset we have at our disposal is our community. We foster an active, friendly and large community of developers, contributors and end-users like yourself. Across our various community-ran chats and forums there are tens of thousands of people willing to help with any issues you may encounter. There are a wide range of communication protocols to choose from. - {{}} - - {{< box style="pad_s blueshadow" type="image" link="/img/philosophy.png" width="200" >}}{{}} -{{}} - - -== Chat platforms - -PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. - -Please read link:/community/Rules/[PINE64 Community Rules and Code of Conduct]. - -The community chat platforms are the following: - -* *Discord*: use this *https://discord.gg/pine64[Invite Link]*. All Pine64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below. -* *IRC*: the server is _irc.pine64.org_. Use `/list` command or the table below to see the full list of channels. -* *Matrix and Telegram*: See the table below. - -|=== -|Channel | Matrix |Telegram |IRC - -| General channel -| https://matrix.to/#/#pine64:matrix.org[#pine64:matrix.org] -| https://t.me/mtrx_pine64[@mtrx_pine64] -| #pine64 - -| News -| https://matrix.to/#/#pine64-announcements:matrix.org[#pine64-announcements:matrix.org] -| https://t.me/PINE64_News[@PINE64_News] -| Unavailable - -| PINE A64(+), A64-LTS & SOPine -| https://matrix.to/#/#pine64sopine:matrix.org[#pine64sopine:matrix.org] -| https://t.me/pine64sopine[@pine64sopine] -| #lts-sopine - -| ROCK64 / ROCKPro64 -| https://matrix.to/#/#rock64:matrix.org[#rock64:matrix.org] -| https://t.me/mtrx_rock64[@mtrx_rock64] -| #rock64 - -| Quartz64 -| https://matrix.to/#/#quartz64:matrix.org[#quartz64:matrix.org] -| https://t.me/joinchat/Vq50DXkH31e0_i-f[Quartz64] -| #quartz64 - -| Quartz64 Development -| https://matrix.to/#/#quartz64-dev:matrix.org[#quartz64-dev:matrix.org] -| https://t.me/q64dev[@q64dev] -| #quartz-dev - -| Star64 -| https://matrix.to/#/#star64:matrix.org[#star64:matrix.org] -| https://t.me/star64_sbc[@star64-sbc] -| Unavailable - -| Pinebook and Pinebook Pro -| https://matrix.to/#/#pinebook:matrix.org[#pinebook:matrix.org] -| https://t.me/mtx_pinebook[@mtx_pinebook] -| #pinebook - -| PinePhone -| https://matrix.to/#/#pinephone:matrix.org[#pinephone:matrix.org] -| https://t.me/pinephone[@pinephone] -| #pinephone - -| PineNote -| https://matrix.to/#/#pinenote:matrix.org[#pinenote:matrix.org] -| https://t.me/pinenote[@PineNote] -| #pinenote - -| PineTab -| https://matrix.to/#/#pinetab64:matrix.org[#pinetab64:matrix.org] -| https://t.me/PineTab[@PineTab] -| #pinetab - -| PineTime -| https://matrix.to/#/#pinetime:matrix.org[#pinetime:matrix.org] -| https://t.me/pinetime[@pinetime] -| #Pinetime - -| PineTime Development -| https://matrix.to/#/#pinetime-dev:matrix.org[#pinetime-dev:matrix.org] -| https://t.me/pinetime_dev[@pinetime_dev] -| #pinetime-dev - -| PineBuds Pro -| https://matrix.to/#/#pinebuds:matrix.org[#pinebuds:matrix.org] -| https://t.me/+nJVhM0mZ9KhlYmZl[@pinebuds] -| Unavailable - -| Pinecil -| https://matrix.to/#/#pinecil:matrix.org[#pinecil:matrix.org] -| https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ[Pinecil] -| #pinecil - -| Pinecil Development -| https://matrix.to/#/#pinecil-dev:matrix.org[#pinecil-dev:matrix.org] -| https://t.me/+8_pdKqXrVuQ4OTk1[Pinecil-dev] -| Unavailable - -| Pinetalk Podcast | Unavailable | Unavailable | Unavailable - -| PineCube -| https://matrix.to/#/#cube64:matrix.org[#cube64:matrix.org] -| https://t.me/pinecube[@pinecube] -| #cube - -| Nutcracker, Ox64, Oz64 -| https://matrix.to/#/#pine64-nutcracker:matrix.org[#pine64-nutcracker:matrix.org] -| https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g[Nutcracker] -| #nutcracker - -| LoRa -| https://matrix.to/#/#pinelora:matrix.org[#pinelora:matrix.org] -| https://t.me/pine64lora[@pine64lora] -| #lora - -| Off-topic -| https://matrix.to/#/#offtopic64:matrix.org[#offtopic64:matrix.org] -| https://t.me/pine64offtopic[@pine64offtopic] -| Unavailable -|=== - -There is also an unofficial Matrix Space at https://matrix.to/#/#pine64-space:matrix.org[#pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place. - -=== Notes regarding the chat - -PINE64 community is not some always responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently. - -* The activity of community members varies depending on the time of day and the number of active users. -* Whether your questions will be answered & whether the answers are right and definitive, depends on the information you provide, and, after all, difficulty of your questions & community members' ability. -* Read http://www.catb.org/~esr/faqs/smart-questions.html[How To Ask Questions The Smart Way] to learn more. -* PINE64 uses a bridge bot (_https://github.com/42wim/matterbridge[matterbridge]_ with some modifications), which allows Discord, IRC, Matrix, and Telegram users to see and participate in the community chat. -* The bot name is "Pine64 Protocol Droid" and if you see this, look in the message to see the actual author of the message. -* When the bot relays messages it will show the platform the user is using: _[D]_ for _Discord_, _[I]_ for _IRC_, _[M]_ for _Matrix_ and _[T]_ for _Telegram_. - - -== Forums - -PINE64 runs an official forum powered by the open-source forum server software _MyBB_. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members. - -The official PINE64 forum can be accessed here: - -* https://forum.pine64.org/[Official PINE64 Forum] - -Also, these are the official Subreddits: - -* https://www.reddit.com/r/PINE64official/[Official PINE64 Reddit] -* https://www.reddit.com/r/PinePhoneOfficial/[Official PinePhone Reddit] -* https://www.reddit.com/r/PinebookPro/[Pinebook Pro Offcial Subreddit] - -== Information - -link:partner_projects[Partner Projects] - -link:philosophy[Philosophy] \ No newline at end of file diff --git a/content/community/_index.md b/content/community/_index.md new file mode 100644 index 00000000..5e3488b5 --- /dev/null +++ b/content/community/_index.md @@ -0,0 +1,100 @@ +--- +title: "Community" +description: PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. +images: + - "/community/community_banner.png" +aliases: + - /web-irc/ # from pine64.com +--- + +{{< box style="themewhite pad" >}} + {{< box style="pad_s blueshadow" type="image" link="/img/slider_index_1.jpg" width="380" >}}{{}} + {{< box style="pad f50 rows" title="" content="markdown" >}} +***Welcome to the PINE64 community!*** + +_PINE64_ has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. + +To become connected and involved with the community, please see the channel list below for a list of available channels and chat platforms. + {{}} +{{}} + +{{< box style="themewhite pad" >}} + {{< box style="pad f50 rows" title="" content="markdown" >}} +_PINE64_ is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [PINE A64](/documentation/Pine_A64) single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices. + +For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [article about our brand and logo](Brand_and_logo). + +The most important asset we have at our disposal is our community. We foster an active, friendly and large community of developers, contributors and end-users like yourself. Across our various community-ran chats and forums there are tens of thousands of people willing to help with any issues you may encounter. There are a wide range of communication protocols to choose from. + {{}} + + {{< box style="pad_s blueshadow" type="image" link="/img/philosophy.png" width="200" >}}{{}} +{{}} + +## Chat platforms + +PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot. + +Please read [PINE64 Community Rules and Code of Conduct](/community/Rules/). + +The community chat platforms are the following: + +* **Discord**: use this **[Invite Link](https://discord.gg/pine64)**. All Pine64 discord channels are immediately viewable, do not need to join separate channels like the Telegram/Matrix table below. +* **IRC**: the server is _irc.pine64.org_. Use `/list` command or the table below to see the full list of channels. +* **Matrix and Telegram**: See the table below. + +| Channel | Matrix | Telegram | IRC | +| --- | --- | --- | --- | +| General channel | [#pine64:matrix.org](https://matrix.to/#/#pine64:matrix.org) | [@mtrx_pine64](https://t.me/mtrx_pine64) | #pine64 | +| News | [#pine64-announcements:matrix.org](https://matrix.to/#/#pine64-announcements:matrix.org) | [@PINE64_News](https://t.me/PINE64_News) | Unavailable | +| PINE A64(+), A64-LTS & SOPine | [#pine64sopine:matrix.org](https://matrix.to/#/#pine64sopine:matrix.org) | [@pine64sopine](https://t.me/pine64sopine) | #lts-sopine | +| ROCK64 / ROCKPro64 | [#rock64:matrix.org](https://matrix.to/#/#rock64:matrix.org) | [@mtrx_rock64](https://t.me/mtrx_rock64) | #rock64 | +| Quartz64 | [#quartz64:matrix.org](https://matrix.to/#/#quartz64:matrix.org) | [Quartz64](https://t.me/joinchat/Vq50DXkH31e0_i-f) | #quartz64 | +| Quartz64 Development | [#quartz64-dev:matrix.org](https://matrix.to/#/#quartz64-dev:matrix.org) | [@q64dev](https://t.me/q64dev) | #quartz-dev | +| Star64 | [#star64:matrix.org](https://matrix.to/#/#star64:matrix.org) | [@star64-sbc](https://t.me/star64_sbc) | Unavailable | +| Pinebook and Pinebook Pro | [#pinebook:matrix.org](https://matrix.to/#/#pinebook:matrix.org) | [@mtx_pinebook](https://t.me/mtx_pinebook) | #pinebook | +| PinePhone | [#pinephone:matrix.org](https://matrix.to/#/#pinephone:matrix.org) | [@pinephone](https://t.me/pinephone) | #pinephone | +| PineNote | [#pinenote:matrix.org](https://matrix.to/#/#pinenote:matrix.org) | [@PineNote](https://t.me/pinenote) | #pinenote | +| PineTab | [#pinetab64:matrix.org](https://matrix.to/#/#pinetab64:matrix.org) | [@PineTab](https://t.me/PineTab) | #pinetab | +| PineTime | [#pinetime:matrix.org](https://matrix.to/#/#pinetime:matrix.org) | [@pinetime](https://t.me/pinetime) | #Pinetime | +| PineTime Development | [#pinetime-dev:matrix.org](https://matrix.to/#/#pinetime-dev:matrix.org) | [@pinetime_dev](https://t.me/pinetime_dev) | #pinetime-dev | +| PineBuds Pro | [#pinebuds:matrix.org](https://matrix.to/#/#pinebuds:matrix.org) | [@pinebuds](https://t.me/+nJVhM0mZ9KhlYmZl) | Unavailable | +| Pinecil | [#pinecil:matrix.org](https://matrix.to/#/#pinecil:matrix.org) | [Pinecil](https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ) | #pinecil | +| Pinecil Development | [#pinecil-dev:matrix.org](https://matrix.to/#/#pinecil-dev:matrix.org) | [Pinecil-dev](https://t.me/+8_pdKqXrVuQ4OTk1) | Unavailable | +| Pinetalk Podcast | Unavailable | Unavailable | Unavailable | +| PineCube | [#cube64:matrix.org](https://matrix.to/#/#cube64:matrix.org) | [@pinecube](https://t.me/pinecube) | #cube | +| Nutcracker, Ox64, Oz64 | [#pine64-nutcracker:matrix.org](https://matrix.to/#/#pine64-nutcracker:matrix.org) | [Nutcracker](https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g) | #nutcracker | +| LoRa | [#pinelora:matrix.org](https://matrix.to/#/#pinelora:matrix.org) | [@pine64lora](https://t.me/pine64lora) | #lora | +| Off-topic | [#offtopic64:matrix.org](https://matrix.to/#/#offtopic64:matrix.org) | [@pine64offtopic](https://t.me/pine64offtopic) | Unavailable | + +There is also an unofficial Matrix Space at [#pine64-space:matrix.org](https://matrix.to/#/#pine64-space:matrix.org) for supported clients that organizes all of the above matrix channels into one place. + +### Notes regarding the chat + +PINE64 community is not some always responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently. + +* The activity of community members varies depending on the time of day and the number of active users. +* Whether your questions will be answered & whether the answers are right and definitive, depends on the information you provide, and, after all, difficulty of your questions & community members' ability. +* Read [How To Ask Questions The Smart Way](http://www.catb.org/~esr/faqs/smart-questions.html) to learn more. +* PINE64 uses a bridge bot (_[matterbridge](https://github.com/42wim/matterbridge)_ with some modifications), which allows Discord, IRC, Matrix, and Telegram users to see and participate in the community chat. +* The bot name is "Pine64 Protocol Droid" and if you see this, look in the message to see the actual author of the message. +* When the bot relays messages it will show the platform the user is using: _[D]_ for _Discord_, _[I]_ for _IRC_, _[M]_ for _Matrix_ and _[T]_ for _Telegram_. + +## Forums + +PINE64 runs an official forum powered by the open-source forum server software _MyBB_. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members. + +The official PINE64 forum can be accessed here: + +* [Official PINE64 Forum](https://forum.pine64.org/) + +Also, these are the official Subreddits: + +* [Official PINE64 Reddit](https://www.reddit.com/r/PINE64official/) +* [Official PinePhone Reddit](https://www.reddit.com/r/PinePhoneOfficial/) +* [Pinebook Pro Offcial Subreddit](https://www.reddit.com/r/PinebookPro/) + +## Information + +[Partner Projects](partner_projects) + +[Philosophy](philosophy) diff --git a/content/community/bridged_chat_notes.adoc b/content/community/bridged_chat_notes.md similarity index 61% rename from content/community/bridged_chat_notes.adoc rename to content/community/bridged_chat_notes.md index 8298c306..543e0156 100644 --- a/content/community/bridged_chat_notes.adoc +++ b/content/community/bridged_chat_notes.md @@ -4,60 +4,60 @@ date: draft: false --- -The PINE64 community chat is connected across multiple platforms: *IRC*, *Telegram*, *Discord*, and *Matrix*. Each platform has its own unique user base and interface, however they interact with each other through the bot account bridging all platforms. +The PINE64 community chat is connected across multiple platforms: **IRC**, **Telegram**, **Discord**, and **Matrix**. Each platform has its own unique user base and interface, however they interact with each other through the bot account bridging all platforms. -The software to bring all platforms together is called https://github.com/42wim/matterbridge[*Matterbridge*]. It acts as the bridge that connects these platforms. It facilitates seamless communication by relaying messages between them. When a user sends a message on any platform (such as IRC), the bot account picks it up. The bot then relays the message to all other connected platforms (such as Telegram, Discord, Matrix). This ensures that users on different platforms can communicate with each other. +The software to bring all platforms together is called [**Matterbridge**](https://github.com/42wim/matterbridge). It acts as the bridge that connects these platforms. It facilitates seamless communication by relaying messages between them. When a user sends a message on any platform (such as IRC), the bot account picks it up. The bot then relays the message to all other connected platforms (such as Telegram, Discord, Matrix). This ensures that users on different platforms can communicate with each other. Users can choose their preferred platform while staying connected to the community. -== A short explanation on how to read the messages +## A short explanation on how to read the messages The following example can be used to illustrate the use of the bridged community chat: - [D] Hey everyone! Just got my new PinePhone. Loving it so far! 📱 - [T] Welcome, Dave! We’re discussing the upcoming application updates. - [M] Hey folks! I’m here from Matrix. Any tips on optimizing battery life? - [I] Greetings! 🌲 I wonder about the same, Frank. - [I] Also, kudos to the PINE64 community for the software progress so far! + [D] Hey everyone! Just got my new PinePhone. Loving it so far! 📱 + [T] Welcome, Dave! We’re discussing the upcoming application updates. + [M] Hey folks! I’m here from Matrix. Any tips on optimizing battery life? + [I] Greetings! 🌲 I wonder about the same, Frank. + [I] Also, kudos to the PINE64 community for the software progress so far! -In this example, the part in the square brackets at the beginning shows the platform, from which each user is writing, **[D]**iscord, **[I]**RC, **[M]**atrix and **[T]**elegram. The part in the angle brackets contains the name of each user: in this example, Dave, Eve, Frank and Ingrid are chatting with each other. +In this example, the part in the square brackets at the beginning shows the platform, from which each user is writing, [**D**]iscord, [**I**]RC, [**M**]atrix and [**T**]elegram. The part in the angle brackets contains the name of each user: in this example, Dave, Eve, Frank and Ingrid are chatting with each other. The bot account relaying the message can have a name such as _Pine64 Protocol Droid_. Mind that this is not the name of the user, who wrote the message. -== Things to consider when using the bridged community chat +## Things to consider when using the bridged community chat In the bridged community chat that spans across Discord, Matrix, Element, and IRC, there are several important considerations to keep in mind. These guidelines help ensure smooth communication and prevent unintended issues. Let’s explore each of these aspects: -=== Avoid editing messages +### Avoid editing messages Editing messages may lead to repeated broadcasts across platforms. To maintain clarity and prevent confusion, refrain from editing your messages after they have been sent. -=== Be cautious with the Discord and Matrix reply function +### Be cautious with the Discord and Matrix reply function While Discord and Matrix allows users to reply directly to specific messages, this feature does not translate to other platforms. When responding to messages, avoid using Discord and Matrix reply function, as it does not display properly on the other platforms. Instead mention the name of the user you are replying to in your message. -=== Use paste services for code and log data +### Use paste services for code and log data Code snippets and log data may not display correctly due to formatting limitations on the bridged community platforms. To share code or logs effectively, consider using paste services (such as Pastebin or GitHub Gists) and provide a link to the content. By adhering to these best practices, you can contribute to a seamless and harmonious experience within the bridged community chat. Happy chatting! -=== Telegram images do not appear in IRC +### Telegram images do not appear in IRC When sending images via Telegram, be aware that they do not appear in the IRC channel. If visual content is crucial, consider alternative methods of sharing, such as providing a link to an image hosting service. -=== Mind file size limits for uploaded files +### Mind file size limits for uploaded files Keep in mind that uploaded files, especially videos, have maximum size limits. If sharing files, verify that they fall within the acceptable size range to ensure successful transmission across all platforms. -=== Avoid manual line breaks and long messages +### Avoid manual line breaks and long messages Messages with manual line breaks (hard returns) are interpreted as separate messages. To prevent fragmentation, avoid lengthy messages with excessive line breaks. Long messages get cut off. To ensure complete communication, keep your messages concise and within reasonable length. -=== Underscores can cause formatting issues +### Underscores can cause formatting issues -Underscores (_) in texts (for example as part of web links) can cause formatting issues due to being interpreted as command to write a text in italic. This sometimes causes links to not properly display and work across the bridge. \ No newline at end of file +Underscores (_) in texts (for example as part of web links) can cause formatting issues due to being interpreted as command to write a text in italic. This sometimes causes links to not properly display and work across the bridge. diff --git a/content/community/partner_projects.adoc b/content/community/partner_projects.adoc deleted file mode 100644 index 99cfa810..00000000 --- a/content/community/partner_projects.adoc +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "Partner projects" -date: -draft: false ---- - -link:https://aosc.io[AOSC OS] - -link:https://www.armbian.com/[Armbian] - -link:http://batocera-linux.xorhub.com/[Batocera Linux] - -link:https://dietpi.com/[DietPi] - -link:https://hardenedbsd.org/[HardenedBSD] - -link:https://kde.org/[KDE Community] - -link:https://neon.kde.org/[KDE Neon] - -link:https://elementary.io/[elementary] - -link:http://www.lakka.tv/[Lakka] - -link:https://en.wikipedia.org/wiki/LuneOS[LuneOS] - -link:https://libreelec.tv/[LibreELEC] - -link:https://maemo-leste.github.io/[Maemo Leste] - -link:https://manjaro.org/[Manjaro] - -link:https://mobian-project.org/[Mobian] - -link:https://nemslinux.com/[NEMS Linux] - -link:https://www.netbsd.org/[NetBSD] - -link:https://ownyourbits.com/nextcloudpi/[NextCloudPi] - -link:https://nixos.org/[NixOS] - -link:https://www.openbsd.org/[OpenBSD] - -link:https://www.openhab.org/[OpenHAB] - -link:https://www.openmediavault.org/[Open Media Vault] - -link:https://www.plasma-mobile.org/[Plasma Mobile] - -link:https://postmarketos.org/[PostmarketOS] - -link:https://q4os.org/[Q4OS] - -link:https://www.recalbox.com/[Recalbox] - -link:https://odroidarena.com/[Retro Arena] - -link:https://sailfishos.org/[SailfishOS] - -link:https://ubports.com/[UBPorts Foundation] - -link:https://volumio.org/[Volumio] diff --git a/content/community/partner_projects.md b/content/community/partner_projects.md new file mode 100644 index 00000000..b8fadccd --- /dev/null +++ b/content/community/partner_projects.md @@ -0,0 +1,63 @@ +--- +title: "Partner projects" +date: +draft: false +--- + +[AOSC OS](https://aosc.io) + +[Armbian](https://www.armbian.com/) + +[Batocera Linux](http://batocera-linux.xorhub.com/) + +[DietPi](https://dietpi.com/) + +[HardenedBSD](https://hardenedbsd.org/) + +[KDE Community](https://kde.org/) + +[KDE Neon](https://neon.kde.org/) + +[elementary](https://elementary.io/) + +[Lakka](http://www.lakka.tv/) + +[LuneOS](https://en.wikipedia.org/wiki/LuneOS) + +[LibreELEC](https://libreelec.tv/) + +[Maemo Leste](https://maemo-leste.github.io/) + +[Manjaro](https://manjaro.org/) + +[Mobian](https://mobian-project.org/) + +[NEMS Linux](https://nemslinux.com/) + +[NetBSD](https://www.netbsd.org/) + +[NextCloudPi](https://ownyourbits.com/nextcloudpi/) + +[NixOS](https://nixos.org/) + +[OpenBSD](https://www.openbsd.org/) + +[OpenHAB](https://www.openhab.org/) + +[Open Media Vault](https://www.openmediavault.org/) + +[Plasma Mobile](https://www.plasma-mobile.org/) + +[PostmarketOS](https://postmarketos.org/) + +[Q4OS](https://q4os.org/) + +[Recalbox](https://www.recalbox.com/) + +[Retro Arena](https://odroidarena.com/) + +[SailfishOS](https://sailfishos.org/) + +[UBPorts Foundation](https://ubports.com/) + +[Volumio](https://volumio.org/) diff --git a/content/community/philosophy.adoc b/content/community/philosophy.md similarity index 97% rename from content/community/philosophy.adoc rename to content/community/philosophy.md index d1d4895d..967bc700 100644 --- a/content/community/philosophy.adoc +++ b/content/community/philosophy.md @@ -4,7 +4,7 @@ date: draft: false --- -**`None of us is as smart as all of us` - Ken H. Blanchard** +***`None of us is as smart as all of us` – Ken H. Blanchard*** At the core of our philosophy is the notion that PINE64 is a community platform. A simplistic point of view, often offered up and referenced online, is that ‘PINE64 does hardware while the community does the software’. While this depiction is not inaccurate, it is also a gross oversimplification. The fact that PINE64 is community driven doesn’t simply entail a one-way reliance on the community or partner projects for software support; it means that the community gets to actively shape the devices, as well as the social platform, of PINE64 from the ground up. The goal is to deliver ARM64 devices that you really wish to engage with and a platform that you want to be a part of. As such, the community – PINE64 – and the Pine Store company are interlocked and intertwined, but separate entities. diff --git a/content/contests/_index.adoc b/content/contests/_index.md similarity index 94% rename from content/contests/_index.adoc rename to content/contests/_index.md index b6720037..701f0651 100644 --- a/content/contests/_index.adoc +++ b/content/contests/_index.md @@ -3,4 +3,4 @@ title: "Community contests" date: draft: false description: ---- \ No newline at end of file +--- diff --git a/content/documentation/Accessories/Accessories_Step_by_Step_Guides.adoc b/content/documentation/Accessories/Accessories_Step_by_Step_Guides.adoc deleted file mode 100644 index 334cd2b1..00000000 --- a/content/documentation/Accessories/Accessories_Step_by_Step_Guides.adoc +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: "Accessories Step by Step Guides" -draft: false -menu: - docs: - title: - parent: "Unsorted" - identifier: "Accessories/Accessories_Step_by_Step_Guides" - weight: ---- - -Accessories Step by Step Guides - -== Wifi/Bluetooth module: - -* http://files.pine64.org/doc/guide/PINE64_Wi-Fi_Bluetooth_Installation_Guide.pdf[Step by Step Installation Guide] - -== Acrylic Open Enclosure: - -* http://files.pine64.org/doc/guide/PINE64_Acrylic_Open_Enclosure_Installation_Guide.pdf[Step by Step Installation Guide] - -If you wish to stack two or more of these enclosures, the screws that serve as feet can be replaced by M8-1.25x16mm grub screws. - ----- -1.25mm is the pitch between threads, and for the M8 (8mm outer diameter) that's the default pitch, and most are advertised as M8x16mm screws. 16mm is really the minimum workable length to catch both the bottom and top aluminium standoffs, with both washers and the acrylic sheet in between. It's workable, but if you can get 20mm it's probably for the best. ----- - -Images: https://imgur.com/a/Zka1qfb - -== Simple 3D Printed Case by Harlandraka - -* http://www.thingiverse.com/thing:1831345[3D printing schematics] - -== Sliding 3D Printed Case by Harlandraka - -* http://www.thingiverse.com/thing:1694943[3D printing schematics] - -== C4 Labs Case for the Pine - -* http://forum.pine64.org/showthread.php?tid=2277[Forum thread including instructions] - -== 7" LCD Touch Screen Panel: - -* http://files.pine64.org/doc/guide/PINE64_7_inches_LCD_Touch_Screen_Panel_Installation_Guide.pdf[Step by Step Installation Guide] - -== Real Time Clock (RTC) battery holder (AAA battery type): - -* http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_AAA_Installation_Guide.pdf[Step by Step Installation Guide] - -== Real Time Clock (RTC) battery holder (CR-2032 Coin Cell battery type): - -* http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_CR2032_Installation_Guide.pdf[Step by Step Installation Guide] - diff --git a/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md b/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md new file mode 100644 index 00000000..46559c6d --- /dev/null +++ b/content/documentation/Accessories/Accessories_Step_by_Step_Guides.md @@ -0,0 +1,52 @@ +--- +title: "Accessories Step by Step Guides" +draft: false +menu: + docs: + title: + parent: "Unsorted" + identifier: "Accessories/Accessories_Step_by_Step_Guides" + weight: +--- + +Accessories Step by Step Guides + +## Wi-Fi/Bluetooth module: + +* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_Wi-Fi_Bluetooth_Installation_Guide.pdf) + +## Acrylic Open Enclosure: + +* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_Acrylic_Open_Enclosure_Installation_Guide.pdf) + +If you wish to stack two or more of these enclosures, the screws that serve as feet can be replaced by M8-1.25x16mm grub screws. + +``` +1.25mm is the pitch between threads, and for the M8 (8mm outer diameter) that's the default pitch, and most are advertised as M8x16mm screws. 16mm is really the minimum workable length to catch both the bottom and top aluminium standoffs, with both washers and the acrylic sheet in between. It's workable, but if you can get 20mm it's probably for the best. +``` + +Images: https://imgur.com/a/Zka1qfb + +## Simple 3D Printed Case by Harlandraka + +* [3D printing schematics](http://www.thingiverse.com/thing:1831345) + +## Sliding 3D Printed Case by Harlandraka + +* [3D printing schematics](http://www.thingiverse.com/thing:1694943) + +## C4 Labs Case for the Pine + +* [Forum thread including instructions](http://forum.pine64.org/showthread.php?tid=2277) + +## 7" LCD Touch Screen Panel: + +* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_7_inches_LCD_Touch_Screen_Panel_Installation_Guide.pdf) + +## Real Time Clock (RTC) battery holder (AAA battery type): + +* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_AAA_Installation_Guide.pdf) + +## Real Time Clock (RTC) battery holder (CR-2032 Coin Cell battery type): + +* [Step by Step Installation Guide](http://files.pine64.org/doc/guide/PINE64_RTC_Backup_Battery_CR2032_Installation_Guide.pdf) diff --git a/content/documentation/Clusterboard/Further_information/FAQ.adoc b/content/documentation/Clusterboard/Further_information/FAQ.adoc deleted file mode 100644 index dce96d0c..00000000 --- a/content/documentation/Clusterboard/Further_information/FAQ.adoc +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: "FAQ" -draft: false -menu: - docs: - title: - parent: "Clusterboard/Further_information" - identifier: "Clusterboard/Further_information/FAQ" - weight: 2 ---- - -*Q*: Are the individual MAC addresses linked to the PHY chips, or the module? - -*A*: The MAC address is specific to the SOPINE module; swapping modules within the Clusterboard does not change the MAC address of the module. - -*Q*: Why will SOPINE modules not reboot when installed on a Clusterboard, but will when installed on a link:/documentation/SOPINE_Baseboard[SOPINE Baseboard]? - -*A*: The cause has been determined to be back-EMF, and can be resolved with some relatively easy hardware modifications, thanks to excellent troubleshooting performed by Eric. Please, have a look at the https://ericdraken.com/a64-reset-problem/[extensive article] he wrote to find out how to resolve this issue. See also https://forum.pine64.org/showthread.php?tid=5849&page=2[this forum thread] for further information. - -*Q*: Do I need heatsinks on any of the components on the Clusterboard? - -*A*: According to the datasheets for the RTL8370N switch ASIC and the RTL8211E PHYs, they consume and thus dissipate up to about 3 W each. As a result, it would be advisable to properly affix passive aluminum heatsinks onto each of these components. Please note that this explanation does not cover the SOPINE and SOEDGE modules. - diff --git a/content/documentation/Clusterboard/Further_information/FAQ.md b/content/documentation/Clusterboard/Further_information/FAQ.md new file mode 100644 index 00000000..fba497bb --- /dev/null +++ b/content/documentation/Clusterboard/Further_information/FAQ.md @@ -0,0 +1,22 @@ +--- +title: "FAQ" +draft: false +menu: + docs: + title: + parent: "Clusterboard/Further_information" + identifier: "Clusterboard/Further_information/FAQ" + weight: 2 +--- + +**Q**: Are the individual MAC addresses linked to the PHY chips, or the module? + +**A**: The MAC address is specific to the SOPINE module; swapping modules within the Clusterboard does not change the MAC address of the module. + +**Q**: Why will SOPINE modules not reboot when installed on a Clusterboard, but will when installed on a [SOPINE Baseboard](/documentation/SOPINE_Baseboard)? + +**A**: The cause has been determined to be back-EMF, and can be resolved with some relatively easy hardware modifications, thanks to excellent troubleshooting performed by Eric. Please, have a look at the [extensive article](https://ericdraken.com/a64-reset-problem/) he wrote to find out how to resolve this issue. See also [this forum thread](https://forum.pine64.org/showthread.php?tid=5849&page=2) for further information. + +**Q**: Do I need heatsinks on any of the components on the Clusterboard? + +**A**: According to the datasheets for the RTL8370N switch ASIC and the RTL8211E PHYs, they consume and thus dissipate up to about 3 W each. As a result, it would be advisable to properly affix passive aluminum heatsinks onto each of these components. Please note that this explanation does not cover the SOPINE and SOEDGE modules. diff --git a/content/documentation/Clusterboard/Further_information/Revisions.adoc b/content/documentation/Clusterboard/Further_information/Revisions.md similarity index 99% rename from content/documentation/Clusterboard/Further_information/Revisions.adoc rename to content/documentation/Clusterboard/Further_information/Revisions.md index b5c0fb93..143dfc68 100644 --- a/content/documentation/Clusterboard/Further_information/Revisions.adoc +++ b/content/documentation/Clusterboard/Further_information/Revisions.md @@ -12,4 +12,3 @@ menu: As of April 2021, current revision of the Clusterboard is 2.3. Compared with the previous revision, 2.2, it removes the PCB components required for using lithium-polymer batteries for powering each of the modules. Besides the 2.2 revision, there was also an early revision (TODO: which exactly?) that required a hardware fix for the eMMC module to work properly. - diff --git a/content/documentation/QuartzPro64/Hardware.adoc b/content/documentation/QuartzPro64/Hardware.adoc index ff25fe03..2c05be4d 100644 --- a/content/documentation/QuartzPro64/Hardware.adoc +++ b/content/documentation/QuartzPro64/Hardware.adoc @@ -49,6 +49,7 @@ RK3588 is slightly (<1mm?) taller than the DRAM chips, use a thick enough therma Plug in the USB-C port labelled "**DEBUG PORT**" on the QP64 board to another computer with a USB-A-to-C cable. It will show up as a FT232 USB Serial adapter in `lsusb`: + ``` $ lsusb [...] diff --git a/content/documentation/Unsorted/Discard/Project.txt b/content/documentation/Unsorted/Discard/Project.txt deleted file mode 100644 index 7f69ba04..00000000 --- a/content/documentation/Unsorted/Discard/Project.txt +++ /dev/null @@ -1,456 +0,0 @@ ---- -title: "Project" -draft: true -menu: - docs: - title: - parent: "Unsorted" - identifier: "Unsorted/Project" - weight: ---- - -== Introduction and Instructions - -This Wiki section offers a variety of projects for PINE64 devices. It is co-created and driven by users like yourself, so feel free to browse the listed projects or even submit your own. If you are interested in contributing a project then *please first read* though the following two sub-sections (on Contributing New Projects and Authorship) before entering your submission. - -*All submissions are welcome. You can submit hardware-based projects, software-based projects or a mix of the two*. For example, you could build an NAS server enclosure for your PINE64 SBC and then create a software-based tutorial on how to take advantage of the setup you built. - -If you feel that a particular theme or project type is not represented on the Wiki then please create a post about it in the relevant section on the https://forum.pine64.org/[PINE64 forum]. - -=== Contributing New Projects - -There are a number of ways in which you can contribute new projects to this Wiki section. Projects can be submitted by: - -* Adding a link to a post on the forum, blog, git instructions, etc., -* Adding a link to an article (please read about authorship in 1.2) -* Adding a link to a video or audio file with project instructions -* Adding links to documents (e.g. Google docs, PDFs, etc,.) of images hosted on Google Drive, Imgur, etc,. -* A combination of two or more of the above - -The preferable way of submitting a new project is by *creating a new Wiki entry* as this assures that it will be *easy to locate* by other users. Wiki entries can include attachments in the form of photos, videos, documents and external links (e.g. to formatted code); making them ideal for storing complex and lengthy tutorials and instructions. - -That said, if you do not wish to migrate your project tutorial from another place (e.g. the forums) then a link to the complete write-up, code, video or another medium will suffice. - -=== Authorship - -If you are the author of the submitted project, be sure to credit yourself accordingly. You are also welcome to remain anonymous if you prefer. -However, if you are linking or referencing an external project or source code that has been written up/ recorded/ created *by someone else* then you *must credit the person or organisation* that the project and/or related resources belong to. - -== Gaming Projects - -|=== -| | PINE64 Retro Gaming Projects - -| -image:/documentation/images/Retrogame_icon.png[Most PINE64 devices are capable of emulating old computer and video game consoles such as the Nintendo Entertainment System. ,title="Most PINE64 devices are capable of emulating old computer and video game consoles such as the Nintendo Entertainment System. "] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_| -image: -image: -image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/PinebookMain.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | PINEBOOK | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| HeadShot | LTS/A64 | https://forum.pine64.org/archive/index.php?thread-496.html[Pine A64 in a Playstation] | Pine A64 in a Playstation Case using original controllers - -| Luke | A64/LTS | https://forum.pine64.org/archive/index.php?thread-5202.html[Arcade Cabinet]| A custom built min-arcade cabinet using the Pine A64 + LCD screen - -| Luke/Pfeerick| LTS/A64 | https://forum.pine64.org/showthread.php?tid=4800[Retroarch] | Install a dedicated Retroarch build on a minimal xenial image - -| spoonerdee | LTS/A64/Pinebook | https://www.youtube.com/watch?v=VM4AvsBKfMo[Emulation on Android] | Video showing emulation on Pine A64 running android. - -| rtissera | Rock64 | https://github.com/rtissera/RetroPie-Setup/releases/[RetroPie Early build]| An early build of RetroPie for Rock64 - -| Seph | Rock64 | https://forum.gimx.fr/viewtopic.php?f=21&t=2470[GIMX on Rock64]| GIMX allows you to use peripherals, such as mice and keyboards, on consoles using a SBC like the Rock64 - -|=== -|=== - -== Desktop Computer Projects - -|=== -| | Desktop Applications of PINE64 SBCs - -3+| -image:/documentation/images/Computer_icon.png[All PINE64 Single Board Computers are capable of acting as destkop computers. This includes a variety of Linux destkop environments (such as Mate or XFCE) as well as different types of Android. ,title="All PINE64 Single Board Computers are capable of acting as destkop computers. This includes a variety of Linux destkop environments (such as Mate or XFCE) as well as different types of Android. "] -|=== -image: -image: -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| Swapnil Bhartiya| A64 | https://www.linux.com/news/build-20-computer-pine64[Debian desktop on Pine64] | Installing Debian Mate on simple image - -| AKINWALE| A64/LTS | https://nanite.co/2016/08/07/building-monodevelop-for-the-pine64/[MonoDevelop] | Install MonoDevelop integrated development environment and forward it via SSH - -| Ray Hightower | A64/LTS | https://rayhightower.com/blog/2016/04/04/pine64-quick-start-guide-using-mac-os-x/[Destkop Quick Start Guide] | A desktop environment quick start guide for Pine A64 - -|=== -|=== - -== Network Attached Storage (NAS) Projects - -|=== -| | NAS Projects - -3+| -image: -image: -image:/documentation/images/NAS_icon.png[Most PINE64 Single Board Computers feature Gigabit Ethernet connections and multiple USB 2.0 / 3.0 ports, and are therefore well suited for domestic NAS applications.,title="Most PINE64 Single Board Computers feature Gigabit Ethernet connections and multiple USB 2.0 / 3.0 ports, and are therefore well suited for domestic NAS applications."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| Ptheven | A64/LTS/Rock64 | https://forum.pine64.org/showthread.php?tid=5231[RAID 0] | A RAID 0 setup for you PINE64 SBC - -| Ptheven | A64/LTS/Rock64 | https://forum.pine64.org/showthread.php?tid=5177[SMB setup] | Instructions to set up shares on your PINE64 SBC - -| Ptheven | A64/LTS/Rock64 | https://forum.pine64.org/showthread.php?tid=4971[NFS share] | Instructions on how to set up an NFS share on the Rock64 - -| Ptheven | A64/LTS/Rock64 | https://forum.pine64.org/showthread.php?tid=4925[Adding USB Storage] | Adding USB Storage, Linux Formatting and Permissions -|=== -|=== - -== Media Server and Player Projects - -|=== -| | Media Server and Player Projects -image: -image: - -3+| -image:/documentation/images/Mediaplayer_icon.png[All PINE64 Single Board Computers are capable of acting at media servers as well as playback devices. Dedicated Linux destributions such as LibreELEC as well as Android TV make for great couch media consumption experiences. Your device may also perform the role of a media server.,title="All PINE64 Single Board Computers are capable of acting at media servers as well as playback devices. Dedicated Linux destributions such as LibreELEC as well as Android TV make for great couch media consumption experiences. Your device may also perform the role of a media server."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| JulianM | A64 | https://forum.pine64.org/archive/index.php?thread-1563-2.html[MDP Server + Speakers] | A custom build of MDP Server and speakers using a Pine A64 - -| Jeremy Graham | A64/LTS | https://jez.me/article/plex-server-on-a-pine64-how-to[Manual Plex Server Installation] | Manual Plex Server installation on Pine A64 - -| Learnincurve | A64/LTS | https://forum.pine64.org/showthread.php?tid=3482[Squeezebox] | Squeezbox on Pine A64 + LCD - -| Ronnie Bailey | A64/LTS | https://hmongbuy.net/video/59_SfaBLGdk[EMBY ] | EMBY server on the Pine A64 -|=== -|=== - -== Projects Utilising General Purpose Input/Output (GPIO) Pins - -image: -image: -image: -|=== -| | GPIO Projects - -3+| -image:/documentation/images/GPIO_icon.png[All PINE64 Single Board Computers have a set of GPIO pins that you can use in your project. The PINEBOOK can also make use GPIO using different means ... you can read about them in this section.,title="All PINE64 Single Board Computers have a set of GPIO pins that you can use in your project. The PINEBOOK can also make use GPIO using different means ... you can read about them in this section."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/PinebookMain.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | PINEBOOK | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| machinehum and MarkHaysHarris777| PINEBOOK | https://forum.pine64.org/showthread.php?tid=5055[uSD Breakout] | This project allows 6 GPIO pins to be accessed via SD card slot - -| MarkHaysHarris777 | Pinebook/A64/LTS | https://forum.pine64.org/showthread.php?tid=4418[PADI GPIO expansion] | PADI IoT Dongle used for GPIO Expansion - -| pfeerick | A64/LTS | https://forum.pine64.org/archive/index.php?thread-2088.html[GPIO Basics] | Controlling Pine64 GPIO via the filesystem (sysfs) on linux - -| NANITE | A64/LTS | https://nanite.co/[Controlling an Arduino] | Controlling an Arduino connected to the PINE64 over I2C with C and C# - -| Rieul Techer | A64/LTS | https://hackaday.io/project/10879/instructions[Ethereum & CitizenWat]| Ethereum and CitizenWat Installation on a Pine64+ board - -| TARINGA|| A64/LTSI | https://www.taringa.net/posts/ebooks-tutoriales/19673288/Server-web-gpio-Pine64.html[GPIO over web Server] | Web server for Pine A64 GPIO setup instructions - -|=== -|=== -image: -image: - -== Server Projects - -|=== -| | Server/Docker Projects - -3+| -image:/documentation/images/server_icon.png[All PINE64 Single Board Computers can be used as a wide variety of servers. Common applications include LAMP and Docker servers, but a there is nearly a limitless amount of plausible server applications.,title="All PINE64 Single Board Computers can be used as a wide variety of servers. Common applications include LAMP and Docker servers, but a there is nearly a limitless amount of plausible server applications."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| Hypriot OS | PINE A64/A64+/A64-LTS/SOPine | https://blog.hypriot.com/post/the-pine-a64-is-about-to-become=the-cheapest-ARM-64-bit-platform-to-run-Docker/[Pine A64 Docker] | Docker on Pine A64, applies to other PINE64 devices - -| doertepn | A64/LTS/Rock64 | https://www.youtube.com/watch?v=K6ZFws2x3qE[OwnCloud tutorial] | Tutorial on manually installing OwnCloud on the Pine A64 - -| wahdooyah | Rock64/LTS/A64 | https://forum.pine64.org/showthread.php?tid=1167[Deluge server] | Deluged Torrent Server on the Pine A64 - -| tomd | Rock64/A64/LTS | https://forum.pine64.org/showthread.php?tid=829[Pi-Hole] | Pi-Hole DNS server on a Pine A64 - -| rallar8 | A64/LTS | https://www.reddit.com/r/pine64/comments/4xhhfr/ssh_and_pine64_as_a_server_a_guide_part_1/[Server Operation, OpenVPN, SSH] | Remotely setting up your Pine A64 Server and using using OpenVPN. - -| PiVPN| Rock64/A64/LTS | https://www.pivpn.io/[PiVPN] | Tutorial on how to set up PiVPN on a Debian-based distribution - -| pine64nutz | Rock64/A64/LTS | https://forum.pine64.org/showthread.php?tid=794[VNC Server] | Install and setup a VNC server for remote destkop access - -| Michael Greene| A64/LTS | https://blog.mike-greene.com/pine64-octoprint-part-1/[Octoprint Server] | Octroprint Server on the Pine A64 installation tutorial - -| Michael Lenardson | Rock64/A64/LTS | https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-nextcloud-on-ubuntu-16-04[Next Cloud] | Installation procedure that works on Pine A64/LTS and Rock64 running Ubuntu 16.04 - -| Jose Fierro | Rock64/A64/LTS | https://devandadmin.com/rock64-lamp-wordpress-lets-encrypt-ssl-part-1/[WordPress/Web Server] | Rock64: LAMP + WordPress + Let’s Encrypt SSL - -| Yuan Gao | Rock64/A64/LTS | https://ee-fans.com/pi-dashboard[Status Monitor] | Rock64: Monitor Rock64 status, like CPU usage, RAM usage, network traffic, etc. on webpage. - -image: -image: -| Yuan Gao | Rock64/A64/LTS | https://ee-fans.com / https://ee-fans.com/how-to-install-lamp-lnmp-on-rock64-with-aapanel-2/[Web Server] | Install LAMP/LNMP on Rock64 and easily to add SSL and other things. -|=== - -== Cluster/Docker Computing Projects - -|=== -| | Cluster Projects - -3+| -image:/documentation/images/Cluster_icon.png[Have you got two or more PINE64 Single Board Computer board? Consider building a cluster. Clutering of two or more PINE64 boards presents as a fantastic oportunity to explore and learn about node failure management, task scheduling, debuggin, data sharing and much more.,title="Have you got two or more PINE64 Single Board Computer board? Consider building a cluster. Clutering of two or more PINE64 boards presents as a fantastic oportunity to explore and learn about node failure management, task scheduling, debuggin, data sharing and much more."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| Climbers.net| PINE A64/A64+/A64-LTS/SOPine | https://climbers.net/sbc/bargain-pine-a64-cluster/[ 5 Node Cluster with PINE A64+] | Cluster in a dedicated acrylic case - -| Quantum Cannibal| A64/LTS | https://www.youtube.com/watch?v=ZCl3kZqbp3w[Docker Cluster Build] | Videos detailing Docker on a Pine A64 cluster - -| Vivek Juneja | A64/LTS | https://www.vivekjuneja.in/2016/08/29/arm-cloud-cluster/[Swarm Cluster] | Instructions to build a swarm cluster using Pine A64/LTS - -| Kurt Stam | LTS | https://medium.com/@kurt.stam/docker-on-pine64-centos-7-arm64-b4606632f28d[Docker CentOS] | Docker on a Pine A64 cluster running CentOS - -| DiversITEurope | A64/LTS | https://www.diversit.eu/post/2016/07/13/running-docker-on-pine64.html[Docker Installation] | Docker installation instructions for Pine A64 - -image: -image: -| Mimuni | Rock64 | https://github.com/docker/compose/issues/5198[Rock64 Docker-compose] | Build docker-compose on Rock64 Board - -|=== -|=== - -== Home Automation Projects - -|=== -| | Home Automation Projects - -3+| -image:/documentation/images/Homeautomation_icon.png[PINE64 Single Board Computers - all equipped with milti-core SOCs and GPIO - can become an adition to, or the basis for, your home automation project. Use an existing platform like OpenHAB which is compatible with commercially available devices, add aditional functionality to MotionEye, or just hack away and make things your own.,title="PINE64 Single Board Computers - all equipped with milti-core SOCs and GPIO - can become an adition to, or the basis for, your home automation project. Use an existing platform like OpenHAB which is compatible with commercially available devices, add aditional functionality to MotionEye, or just hack away and make things your own."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| FrankA2 | A64 | https://www.instructables.com/id/Inexpensive-Touchscreen-Life-Command-Center-Using-/[Life Command Center]| Display weather, email and information about home using a Pine A64 - -| Sytone | A64/LTS | https://www.sytone.com/2016/08/running-home-assistant-on-pine64/[Home Assistant] | Running home assistant on Pine A64 - -| Pineadmin | LTS/A64 | https://forum.pine64.org/showthread.php?tid=2395[Node-RED] | Install Node-RED for for wiering together hardware devices on the Pine A64/LTS - -| Moustage | LTS/A64 | https://www.domoticz.com/forum/viewtopic.php?t=13142[Domoticz setup instructions] | Domoticz on Pine64 using some cheap I2C modules - -| Andrew Klimovski | A64/LTS | https://andrew-klimovski.blogspot.co.uk/2017/03/home-automation-openhab2-on-pine64.html[OpenHAB Basics] | Basic installation and setup of OPneHAB on Pine A64 running Ubuntu - -image: -image: -| Jewgeni R | A64/LTS | https://www.youtube.com/watch?v=j19QPLnZRcc[ioBroker] | Video about ioBroker on Pine A64 N.B. In German - -| Deviant Engineer | A64/LTS/Rock64 | https://deviantengineer.com/2016/09/hass-dietpi/[Z-Wave bindings DietPi] | Z-Wave Bindings + Home Assistant installation from DietPi - -|=== -|=== - -== Robotics Projects - -|=== -| | Robotics Projects - -3+| -image:/documentation/images/Robotic_icon.png[Use your PINE64 Single Board Computer featuring a milti-core SOCs and GPIO to have a go at robotics. Download an existing Open Source robotics project from Github or start your own; browse this section for inspiration and resources.,title="Use your PINE64 Single Board Computer featuring a milti-core SOCs and GPIO to have a go at robotics. Download an existing Open Source robotics project from Github or start your own; browse this section for inspiration and resources."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| Name | Device | Link to project | Notes about the project - -|=== -|=== - -== PADI IoT Stamps Projects - -|=== -| | PADI Projects - -3+| -image:/documentation/images/PADIstamp_icon.png[PADI is a tiny microcontroller that can be used in conjunction with your PINE64 SBC or the Pinebook ,title="PADI is a tiny microcontroller that can be used in conjunction with your PINE64 SBC or the Pinebook "] -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes -image: -image: -image: - -| thomash | PADI | https://forum.pine64.org/showthread.php?tid=4586[Programming via IDE] | Programming PADI with Arduino IDE - -| MarkHaysHarris777 | PADI | https://forum.pine64.org/showthread.php?tid=2482[Programming PADI] | Programming PADI basics - -|=== -|=== - -== Other Projects - -|=== -| | Other Projects - -3+| -image:/documentation/images/Otherproject_icon.png[You have no doubt come up with something that we didn't think about, and that is truly great. Perhaps your project is interesting enough that it will be granted its own section. After all if you have imagination then sky is the limit.,title="You have no doubt come up with something that we didn't think about, and that is truly great. Perhaps your project is interesting enough that it will be granted its own section. After all if you have imagination then sky is the limit."] -|=== -|+*Suitable Devices for this Project* - -| | image:/documentation/images/PINEA64_sideimg.jpg[width=160]_|_|_image:/documentation/images/PINEA64_LTS_sideimg.jpg[width=160]_|_|_image:/documentation/images/PinebookMain.jpg[width=160]_|_|_image:/documentation/images/Rock64.jpg[width=160] - -| PINE A64/A64+ | PINE A64-LTS/SoPine | PINEBOOK | ROCK64 -[cols="1,1,1,1,1"] -|=== -[cols="1,1,1,1"] -|=== - | Project Author(s) - | Device(s) - | Project Link - | Notes - -| bits_and_wires | Pinebook | https://forum.pine64.org/showthread.php?tid=5302[case mod] | Pinebook Case modification - -| MarkHaysHarris777 | Pinebook | https://forum.pine64.org/showthread.php?tid=5026[Serial Console Cable] | Serial over 3.5 jack plug on the Pinebook - -| MarkHaysHarris777 | Pinebook | https://forum.pine64.org/showthread.php?tid=5013[Case mod Serial Console] | Case mod to access serial console switch inside the case - -| doertepn | A64/LTS | https://www.youtube.com/watch?v=gDcEWgvO7NA[Picture frame] | A Pine A64 picture frame using an old Apple computer - -| vovakurz | A64/LTS | https://ishwestscriptwault.wordpress.com/2016/12/29/running-unifi-controller-5-on-pine64-en/[Ubiquiti UAPs rely on a UniFi] | CA UniFi relay for better/Smoother WiFi roaming. - -| iPhyse | A64/LTS | https://www.instructables.com/id/Holodock-Pine64/[Holodoc Project] | Instructions on creating a holographic doc using the Pine A64 - -| carlosviansi | A64/LTS | https://forum.pine64.org/archive/index.php?thread-423.html[Weather station] | Weather Station using Pine A64 + I2C POT - -| KnReLe | Pine A64 | https://forum.pine64.org/showthread.php?tid=142&pid=18238#pid18238[RTL-SDR] | RTL-SDR software that works out-of-the-box on the Pine A64 - -| sgjava | Pine A64/LTS | https://forum.pine64.org/showthread.php?tid=4468[Pine64 with small OLED] | Adding a small OLED screen to Pine A64 - -| Dmoreno | Pine A64/LTS | https://forum.pine64.org/showthread.php?tid=3078[Karaoke]| Karaoke software running on Pine A64 - -| wahdooyah | A64/LTS | https://forum.pine64.org/showthread.php?tid=1219[Phone Notifications] | Pushing notifications from home network to cell phone - -| rontant | Rock64/A64/LTS | https://forum.pine64.org/showthread.php?tid=4971[migrating rootfs to HDD/SSD] | Tutorial for migrating rootfs to an external diver - -| Ron Kamphuis | Rock64 | https://medium.com/@perfectstormtd/deploying-full-iota-node-on-a-rock64-4gb-arm64-board-34d3f6cb473a[IOTA Node] | Deploying full IOTA node on a ROCK64 4GB - -| Lior Pachter | Rock64 | https://liorpachter.wordpress.com/2018/01/29/bioinformatics-on-a-rock64/[ Bioinformatics on a Rock64] | Kallisto bioinformatics for computational biologists - -| evilbunny | Rock64 | https://forum.pine64.org/showthread.php?tid=5723&pid=35580#pid35580/[ WiFi with WebGUI] | A DIY WiFI AC AP / Router with WebGUI - -| rmbusy | Rock64 | https://forum.pine64.org/showthread.php?tid=5166[Survaillance system] | A DIY surveillance system using the Rock64 running Motion -|=== -|=== \ No newline at end of file diff --git a/content/documentation/Unsorted/PhoenixCard.adoc b/content/documentation/Unsorted/PhoenixCard.adoc index 65d7fb47..37086838 100644 --- a/content/documentation/Unsorted/PhoenixCard.adoc +++ b/content/documentation/Unsorted/PhoenixCard.adoc @@ -22,7 +22,7 @@ menu: === Step to create the SD-Card - image:/documentation/images/PCard_Main.jpg[width=750] +image:/documentation/images/PCard_Main.jpg[width=750] . Extract the PhonixCard-xx.rar file into an empty directory. . Navigate into the directory where you installed PhoenixCard and start PhoenixCard.exe. diff --git a/themes/pinetheme/assets/css/style.css b/themes/pinetheme/assets/css/style.css index c5f0ca5b..9c0b157c 100644 --- a/themes/pinetheme/assets/css/style.css +++ b/themes/pinetheme/assets/css/style.css @@ -848,6 +848,7 @@ table { margin-top: 1rem; margin-bottom: 1rem; border: 1px solid #dee2e6; + table-layout: fixed; } table td,