hardcode username

.drone.yml

@@ -2,7 +2,6 @@ kind: pipeline
 name: default
 
 steps:
-  # stable site
   - name: build_stable
     image: klakegg/hugo:ext-alpine-ci
     environment:
@@ -13,7 +12,6 @@ steps:
       branch:
         - main
 
-  # staging site
   - name: build_staging
     image: klakegg/hugo:ext-alpine-ci
     environment:
@@ -64,19 +62,16 @@ steps:
         exclude:
         - pull_request
 
-#  - name: notify
-#    image: spotlightkid/drone-matrixchat-notify:latest
-#    settings:
-#      homeserver: https://data.coop
-#      roomid: '!plKSghHbepWeUEtbHE:data.coop'
-#      userid:
-#        from_secret: matrix_username
-#      password:
-#        from_secret: matrix_password
-#      markdown: 'yes'
-#      template: |
-#        `${DRONE_REPO}` build #${DRONE_BUILD_NUMBER} status: **${DRONE_BUILD_STATUS}**
-#
-#        ${DRONE_PULL_REQUEST_TITLE}](${DRONE_COMMIT_LINK})
+  - name: notify
+    image: spotlightkid/drone-matrixchat-notify:latest
+    settings:
+      homeserver: https://data.coop
+      roomid: '!plKSghHbepWeUEtbHE:data.coop'
+      userid: '@datacoop_bot:data.coop'
+      password:
+        from_secret: matrix_password
+      markdown: 'yes'
+      template: |
+        `${DRONE_REPO}` build #${DRONE_BUILD_NUMBER} status: **${DRONE_BUILD_STATUS}**
 
-# provoke build
+        ${DRONE_PULL_REQUEST_TITLE}](${DRONE_COMMIT_LINK})

config.yaml

@@ -17,15 +17,7 @@ markup:
 languages:
   da:
     title: data.coop
-    params:
-      description: "Et datakollektiv, der passer på dine data."
-    weight: 1    
-    # First Hugo looks in your post front matter for an images value (images: [""])
-    # Then Hugo searchs for image page resources with feature, cover or thumbnail in their name. These are images files under a directory that matches the post (e.g. content\posts\first-post)
-    # If not images are found, Hugo looks for images (images: [""]) in your site config
-    # If no image if found, then an image-less Twitter summary card is used instead of summary_large_image
-    # https://digitaldrummerj.me/hugo-preview-when-sharing-twitter/
-    images: ["/static/img/some_card_preview_large_da.png"]
+    weight: 1
     LanguageName: Dansk
     menu:
       nav:
@@ -43,10 +35,7 @@ languages:
         weight: 4
   en:
     title: data.coop
-    params:
-      description: "A data collective that takes care of your data."
     weight: 2
-    images: ["/static/img/some_card_preview_large_en.png"]
     LanguageName: English
     menu:
       nav:
@@ -63,3 +52,5 @@ languages:
         url: "en/rights/"
         weight: 4
 
+params:
+  description: "Et datakollektiv, der passer på dine data."

content/_index.da.md

@@ -38,4 +38,3 @@ Vores kerneprincipper er:
 </dl>
 
 Ud fra de kerneprincipper vil vi med tiden udbyde onlinetjenester til medlemmerne. Hovedtanken er, at vi som udgangspunkt stoler mere på hinanden end på "de store" som f.eks. Google, Microsoft eller Facebook.
-

content/assembly2024-1.da.md

@@ -1,32 +0,0 @@
----
-title: Ekstraordinær Generalforsamlingen 15. maj 2024
----
-
-
-
-Bestyrelsen indkalder hermed til en ekstraordinær generalforsamling, hvor vi ønsker at nå til en beslutning vedrørende den moderationspolitik, som det dertil nedsatte udvalg er nået frem til.
-
-Indkaldelsen til ekstraordinær GF kan måske virke underlig, taget i betragtning at vi har en ordinær generalforsamling blot 2 uger efter. Men vi havde allerede besluttet at tage dette spørgsmål op så hurtigt som muligt. Og vi indser også, at denne vigtige debat næppe får tilstrækkelig tid til en ordinær generalforsamling, og omvendt ville tage uforholdsmæssigt meget tid ved en sådan.
-
-Dagsorden ser således ud:
-
-1. Valg af dirigent og referent.
-2. Fremlæggelse og diskussion af Moderationspolitik
-3. Beslutning om Moderationspolitik
-
-Mødet finder sted via online videomøde:
-
-*fjernet fra offentlig indkaldelse*
-
-## 1. Valg af dirigent og referent
-
-## 2. Fremlæggelse og diskussion af Moderationspolitik
-
-Forslaget til en Moderationspolitik kan læses her: https://git.data.coop/data.coop/dokumenter/pulls/28
-
-## 3. Beslutning om Moderationspolitik
-
-Evt. ændringsforslag behandles først.
-
-Herefter går vi til afstemning.
-

content/assembly2024-2.da.md

@@ -1,51 +0,0 @@
----
-title: Indkaldelse til generalforsamling i data.coop, lørdag d. 1. juni 2024, kl. 13:00
----
-
-Kære data.coop medlem.
-
-Hermed indkaldes til ordinær 2024 generalforsamling for foreningen data.coop lørdag den 1. juni 2024 kl. 13:00.
-
-Generalforsamlingen vil blive afholdt online. Der bliver udsendt et link til det præcise sted i dagene op til.
-
-Man kan finde vedtægter samt tidligere referater her:<br>
-<https://git.data.coop/data.coop/dokumenter>
-
-Regnskab, budget og andre relevante dokumenter for generalforsamlingen kan findes på:<br>
-<https://git.data.coop/data.coop/dokumenter/src/branch/main/generalforsamlinger/2024>
-
-Hvis man har forslag til vedtægtsændringer må de meget gerne indsendes som "[Pull Request](https://git.data.coop/data.coop/dokumenter/pulls)" i Forgejo - spørg gerne om hjælp på [Matrix-kanalen](https://matrix.to/#/#data.coop:data.coop) eller på mail til forpersonen, Vidir, på <valberg@data.coop>. Husk at indsende senest syv dage før GF, så de er modtaget senest 24 maj 2024 kl 23:59.
-
-## Dagsorden
-
-1) Valg af dirigent og referent.
-2) Bestyrelsens beretning.
-3) Fremlæggelse af regnskab, budget og kontingent.
-4) Indkomne forslag.
-
-   - Forslag om vedtægtsændring: Separat afsnit for Tegningsret + ny regel for prokura: <https://git.data.coop/data.coop/dokumenter/pulls/35>
-   - Forslag om vedtægtsændring: Specificering af formalia i dagsordenen: <https://git.data.coop/data.coop/dokumenter/pulls/36>
-   - Omformuler fra specifikke kanaler til noget mere generelt: <https://git.data.coop/data.coop/dokumenter/pulls/41>
-   - Smårettelser til Moderationspolitik: <https://git.data.coop/data.coop/dokumenter/pulls/42>
-
-     **BEMÆRK! Forslag stillet via Pull Requests kan rettes frem til syv dage før generalforsamlingen jf. vedtægterne.**
-
-5) Godkendelse af vedtægtsændringer og [Acceptable Use Policy](https://git.data.coop/data.coop/dokumenter/src/branch/main/Acceptable%20Usage%20Policy.md) inklusive eventuelle vedtagede forslag til denne.
-6) Valg jf. §3 i vedtægterne.
-    Den nuværende bestyrelse består af:
-    - Bestyrelsesmedlemmer:
-        - Balder
-        - Halfdan
-        - Mikkel
-        - Reynir (på valg)
-        - Vidir (på valg)
-    - Suppleanter (på valg):
-        - Sam
-        - Sune
-7) Eventuelt.
-
-Det var alt! Hvis du har spørgsmål, så skriv gerne til <board@data.coop>.
-
-Med venlig hilsen<br>
-Bestyrelsen
-

content/membership.da.md

@@ -11,8 +11,8 @@ Du bør læse vores [vedtægter]({{< ref "/rights.md" >}}) og især vores [Accep
 Du bliver medlem ved at overføre penge til vores konto og sende en email til
 vores kasserer, [benjaoming@data.coop](mailto:benjaoming@data.coop), med dit navn.
 
- * Reg. 5444 (Arbejdernes Landsbank)
- * Kontonr. 0510901 
+ * Reg. 8401 (Merkur)
+ * Kontonr. 1016866 
  * Tekst på overførslen: Fornavn+efternavn
 
 Årligt kontingent: **300 kr** (dog gerne mere)\

content/membership.en.md

@@ -21,8 +21,8 @@ to our treasurer [benjaoming@data.coop](mailto:benjaoming@data.coop), containing
 
 Currently, the only option is to wire a bank payment to our Danish bank account:
 
-* Reg. 5444 (Arbejdernes Landsbank)
-* Kontonr. 0510901 
+* Reg. 8401 (Merkur)
+* Kontonr. 1016866 
 * Text: First name + last name
 
 Annual membership: **DKK 300** (or more)\

content/rights.en.md

@@ -2,163 +2,10 @@
 title: Legal statutes of data.coop
 ---
 
-> This translation is provided solely for the purpose of guidance. The [Danish version](/rights/) remains the official and legally binding version.
+data.coop does not have a translation of its Danish statutes.
 
-## § 1. Name and location
-The name of the association is: data.coop
+The reason is that we cannot guarantee that the democratic process that established the Danish statutes would understand an English translation in the same way.
 
-The association is based in the city of Copenhagen but (its activities are) primarily online.
-
-## § 2. Aim
-
-The main aims of the association is to provide digital infrastructure to its members, while keeping the core principles of the association — privacy, encryption, decentralization and zero knowledge — in focus.
-
-### § 2.1 Secondary aims
-
-* The association works to promote its core principles.
-* The association helps people act responsibly online.
-* The association collaborates with other data cooperatives and/or helps other start up similar initiatives.
-* The association may provide its services to other non-profits, grassroots movements and similar, working independently of the association with goals that match the aims and core principles of the association.
-
-## § 3. Governance
-Overriding power of the association lies with the General Assembly, consisting of members with a valid proof of membership.
-
-The General Assembly elects:
-
-- A board of 5 members
-- 2 alternate board members
-- 1 financial auditor
-- Optionally, 1 alternate financial auditor
-
-Board members are elected for a period of 2 years, so that at least 2 members are up for election every year. The auditor and alternates are up for election every year.
-
-## § 4. The General Assembly (GA)
-The board calls for meetings of the GA no less than 14 days prior through the website of the association and mailing lists. The GA meets every year before the end of September. The agenda of the annual meeting of the GA must include the following items:
-
-1. Formalities
-   1. Election of a meeting chair and notetaker
-   2. Legality of the meeting (was the meeting called in time)
-   3. Election of a notetaker
-2. Report from the board
-3. Presentation and approval of accounts, budget and membership fee
-4. Incoming motions
-5. Elections (as per §3)
-6. Any other business
-
-### § 4.1. Holding of meetings of the GA and the board
-Meetings of the GA and the board may take place online.
-
-### § 4.2. Incoming motions and statute amendments
-
-Motions and statute amendments must be received by the board no less than a week before the meeting of the GA and presented to members no less than 4 days before the the meeting of the GA.
-
-### § 4.3. Statute amendments
-
-Passing of statute amendments requires a three-quarters majority of members present at the meeting of the GA.
-
-### § 4.4. Motions
-Passing of motions requires a simple majority of members present at the meeting of the GA.
-
-## § 5. The board of the association
-The executive power of the association lies with the board (as per §3). The board itself elects its officers including a chair, a vice chair and a treasurer. The board delegates handling of daily business of the association to an executive committee consisting of the chair, vice chair and treasurer.
-
-The board is in charge of drafting the accounts and the budget.
-
-The board itself determines its own rules of procedure.
-
-The board may create ad-hoc working groups consisting of members, functioning as fora for developing ideas for the association.
-
-### §5.1 Legal authority
-
-The chair and treasurer have legal authority, but when it comes to purchasing, selling, or mortgaging real estate, making service agreements, or taking loans, the entire board must agree to bind the association.
-
-The entire board may assign power of attorney to individual members of the board.
-
-## § 6. Membership
-Any physical person who supports the aims of the association may become a member. Membership is binding for one year at a time.
-
-The board has the authority to remove members from the association if they act in violation of the Acceptable Use Policy (AUP).
-
-Membership is continuous from the payment of dues until the conclusion of the annual meeting of the GA.
-
-## § 7. Administrators
-The services offered by the associated are maintained by a team of administrators. Only members of the association can assume the role of administrator.
-
-Only administrators hold administrative access to the servers and services of the association.
-
-### § 7.1 Appointment of administrators
-The board appoints administrators.
-
-The appointment of administrators must be announced to the members of the association.
-
-### § 7.2 Mistrust of administrators
-Mistrust towards one or more administrators must be addressed at an extraordinary meeting of the GA.
-
-Mistrust towards administrators must be reported to the board. The board has the authority to temporarily suspend an administrator's administrative rights until the declaration of mistrust against them is addressed
-
-## § 8. Moderation policy
-The association maintains a moderation policy for its social services, approved by the GA. The moderation policy is enforced by a team of moderators.
-
-### § 8.1 Appointment of moderators
-The board appoints moderators.
-
-The appointment of moderators must be announced to the members of the association.
-
-Only members of the association can hold the position of moderator. Ideally, moderators should not be board members, however, at least one moderator must also be a board member.
-
- ### § 8.2 Mistrust of moderators
-Mistrust towards one or more moderators must be addressed at an extraordinary meeting of the GA.
-
-Mistrust towards moderators must be reported to the board. The board has the authority to temporarily suspend a moderator's moderator rights until the declaration of mistrust against them is addressed
-
-## § 9. Membership fees/funding
-Annual membership fees are decided by the GA.
-
-Additionally, the association can receive funding through sponsorships, advertising support, as well as contributions from public/private companies, foundations, other associations/institutions, and private individuals, as long as it does not impose conditions on the association's decisions.
-
-## § 10. Service fees
-
-The association provides services to its members who pay a service fee.
-
-The service fee is defined and determined by the board.
-
-### § 10.1 Terms of delivery and payment
-
-The board determines the terms of delivery and payment, such as terms, payment times and refunds.
-
-The board reserves the right to charge late fees or suspend services in case of lacking payments.
-
-### § 10.2 Change of service fees and payment terms
-
-Changes to service fees or payment terms must be announced to the members of the association no later than 30 days before taking effect.
-
-The addition of services or changes to service configurations are NOT considered changes requiring notice.
-
-### § 10.3 Disputing changes
-
-If one or more members disagree with changes in service fees or payment terms, they may file a dispute in writing to the board.
-
-The dispute must be received by the board no later than 14 days before the change would take effect.
-
-If the board receives disputes from at least 1/3 of the members of the association, the board must call for an extraordinary GA, at which the change must be presented as a motion to be approved by the GA.
-
-## § 11. Extraordinary General Assembly (GA)
-Extraordinary GAs may be called if desired by a majority of the board.
-
-Extraordinary GAs may be called if desired by one-third of the members.
-
-Extraordinary GAs are called following the same terms as in §4.
-
-The agenda must be substantiated.
-
-## § 12. Accounts
-The association's financial year is the calendar year.
-
-## § 13. Dissolution
-Dissolution of the association requires a majority vote of three-quarters of members present at the GA or extraordinary GA.
-
-The dissolution must then be approved at a subsequent extraordinary GA.
-
-In the event of the dissolution of the association, the association's assets shall be transferred to European Digital Rights (EDRi) and Free Software Foundation Europe (FSFE)
-
-The association data.coop was founded on June 24, 2014.
+While we work out this challenge,
+we encourage that you use some auto-generated translation of the [Danish statutes]({{< ref path="/rights.md" lang="da" >}})
+and ask us questions about anything that would seem unclear.

themes/datacoop2020/layouts/partials/head.html

@@ -17,9 +17,6 @@
         <meta name="msapplication-TileColor" content="#4b3aba">
         <meta name="theme-color" content="#4b3aba">
 
-        {{ template "_internal/twitter_cards.html" . }}
-        {{ template "_internal/opengraph.html" . }}
-
         {{ $style := resources.Get "static/css/style.scss" | resources.ToCSS | resources.Minify | resources.Fingerprint "sha512" }}
         <link rel="stylesheet" href="{{ $style.RelPermalink }}" integrity="{{ $style.Data.Integrity }}">