├── CODEOWNERS ├── .editorconfig ├── public ├── favicon.ico ├── favicon-16x16.png ├── favicon-32x32.png ├── mage-os-logo.png ├── mstile-70x70.png ├── apple-touch-icon.png ├── mstile-144x144.png ├── mstile-150x150.png ├── mstile-310x150.png ├── mstile-310x310.png ├── supporters │ └── tutanota.png ├── android-chrome-192x192.png ├── android-chrome-512x512.png ├── blog │ ├── 2022 │ │ ├── mage-os-founding.jpg │ │ ├── 2022-12-02-meetcommerce-mageos-2.jpg │ │ ├── 2022-07-21-founding-meeting-warsaw.png │ │ └── 2022-12-02-meetcommerce-mage-os-talk-bannner.jpg │ └── 2023 │ │ ├── 2023-02-28-nx-graph-demo.png │ │ ├── 2023-01-27-mageos-badge-preview.png │ │ └── 2023-02-28-new-website-preview.png ├── fonts │ ├── Montserrat-Regular.ttf │ ├── Montserrat-SemiBold.ttf │ ├── montserrat-400-v1.woff2 │ └── montserrat-600-v1.woff2 ├── social-preview-background.png ├── browserconfig.xml ├── site.webmanifest └── safari-pinned-tab.svg ├── src ├── assets │ └── styles │ │ └── global.css ├── pages │ ├── newsletter.astro │ ├── distribution │ │ ├── why-use-mage-os.md │ │ ├── index.md │ │ └── product-vision.md │ ├── imprint.md │ ├── blog │ │ ├── rss │ │ │ └── [...page].astro │ │ ├── 20221011-new-magento-release.md │ │ ├── [page].astro │ │ ├── mage-os-update-2022-week-19.md │ │ ├── 20221102-mageos-distro-repos-and-more.md │ │ ├── mage-os-update-2022-week-25.md │ │ ├── mage-os-update-2022-week-11.md │ │ ├── mage-os-update-2022-week-7.md │ │ ├── 20221202-meetcommerce.md │ │ ├── the-future-of-magento.md │ │ ├── mage-os-update-2022-week-30.md │ │ ├── mage-os-update-2022-week-9.md │ │ ├── 20230228-february-update.md │ │ ├── mage-os-update-2022-week-14.md │ │ ├── mage-os-update-2022-week-6.md │ │ ├── mage-os-update-2022-week-33.md │ │ ├── mage-os-update-2022-week-36-mage-os-assoc-announcement.md │ │ ├── introducing-mage-os.md │ │ ├── mage-os-update-2022-week-35.md │ │ ├── mage-os-update-2022-week-38-diversity-and-inclusion.md │ │ ├── 20221123-mageos-content-update.md │ │ ├── 20230127-january-update.md │ │ └── mage-os-update-january-2022.md │ ├── privacy-policy.md │ ├── get-involved.md │ ├── code-of-conduct.md │ ├── organization │ │ ├── about.md │ │ └── statutes.md │ ├── index.astro │ └── introducing-mage-os.md ├── components │ ├── Button.astro │ ├── Newsletter.astro │ ├── PostPreviewList.astro │ ├── Footer.astro │ ├── SignList.vue │ ├── SignForm.vue │ └── Header.astro ├── layouts │ ├── document.astro │ ├── post.astro │ ├── post-with-sign-form.astro │ └── default.astro └── utils │ └── MetaTags.astro ├── postcss.config.cjs ├── jsconfig.json ├── fonts.conf ├── astro.config.mjs ├── .gitignore ├── vercel.json ├── package.json ├── tailwind.config.cjs ├── api ├── subscribe.js └── subscribers-list.js ├── README.md └── inline-styles.mjs /CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @Mage-OS/content -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | [*] 2 | indent_size = 2 3 | indent_style = space 4 | -------------------------------------------------------------------------------- /public/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/favicon.ico -------------------------------------------------------------------------------- /src/assets/styles/global.css: -------------------------------------------------------------------------------- 1 | @tailwind base; 2 | @tailwind components; 3 | @tailwind utilities; 4 | -------------------------------------------------------------------------------- /public/favicon-16x16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/favicon-16x16.png -------------------------------------------------------------------------------- /public/favicon-32x32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/favicon-32x32.png -------------------------------------------------------------------------------- /public/mage-os-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/mage-os-logo.png -------------------------------------------------------------------------------- /public/mstile-70x70.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/mstile-70x70.png -------------------------------------------------------------------------------- /public/apple-touch-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/apple-touch-icon.png -------------------------------------------------------------------------------- /public/mstile-144x144.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/mstile-144x144.png -------------------------------------------------------------------------------- /public/mstile-150x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/mstile-150x150.png -------------------------------------------------------------------------------- /public/mstile-310x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/mstile-310x150.png -------------------------------------------------------------------------------- /public/mstile-310x310.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/mstile-310x310.png -------------------------------------------------------------------------------- /public/supporters/tutanota.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/supporters/tutanota.png -------------------------------------------------------------------------------- /postcss.config.cjs: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | plugins: { 3 | tailwindcss: {}, 4 | autoprefixer: {} 5 | } 6 | }; -------------------------------------------------------------------------------- /public/android-chrome-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/android-chrome-192x192.png -------------------------------------------------------------------------------- /public/android-chrome-512x512.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/android-chrome-512x512.png -------------------------------------------------------------------------------- /public/blog/2022/mage-os-founding.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2022/mage-os-founding.jpg -------------------------------------------------------------------------------- /public/fonts/Montserrat-Regular.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/fonts/Montserrat-Regular.ttf -------------------------------------------------------------------------------- /public/fonts/Montserrat-SemiBold.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/fonts/Montserrat-SemiBold.ttf -------------------------------------------------------------------------------- /public/fonts/montserrat-400-v1.woff2: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/fonts/montserrat-400-v1.woff2 -------------------------------------------------------------------------------- /public/fonts/montserrat-600-v1.woff2: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/fonts/montserrat-600-v1.woff2 -------------------------------------------------------------------------------- /public/social-preview-background.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/social-preview-background.png -------------------------------------------------------------------------------- /jsconfig.json: -------------------------------------------------------------------------------- 1 | { 2 | "compilerOptions": { 3 | "baseUrl": ".", 4 | "paths": { 5 | "@/*": ["src/*"] 6 | } 7 | } 8 | } -------------------------------------------------------------------------------- /public/blog/2023/2023-02-28-nx-graph-demo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2023/2023-02-28-nx-graph-demo.png -------------------------------------------------------------------------------- /fonts.conf: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | public/fonts 5 | 6 | -------------------------------------------------------------------------------- /public/blog/2023/2023-01-27-mageos-badge-preview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2023/2023-01-27-mageos-badge-preview.png -------------------------------------------------------------------------------- /public/blog/2023/2023-02-28-new-website-preview.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2023/2023-02-28-new-website-preview.png -------------------------------------------------------------------------------- /public/blog/2022/2022-12-02-meetcommerce-mageos-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2022/2022-12-02-meetcommerce-mageos-2.jpg -------------------------------------------------------------------------------- /public/blog/2022/2022-07-21-founding-meeting-warsaw.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2022/2022-07-21-founding-meeting-warsaw.png -------------------------------------------------------------------------------- /public/blog/2022/2022-12-02-meetcommerce-mage-os-talk-bannner.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/mage-os/mage-os-website/HEAD/public/blog/2022/2022-12-02-meetcommerce-mage-os-talk-bannner.jpg -------------------------------------------------------------------------------- /src/pages/newsletter.astro: -------------------------------------------------------------------------------- 1 | --- 2 | import Layout from '@/layouts/default.astro' 3 | import Newsletter from '@/components/Newsletter.astro' 4 | 5 | const content = { 6 | title: 'Newsletter', 7 | } 8 | 9 | --- 10 | 11 | 12 | 13 | -------------------------------------------------------------------------------- /astro.config.mjs: -------------------------------------------------------------------------------- 1 | import { defineConfig } from 'astro/config' 2 | import vue from '@astrojs/vue' 3 | import tailwind from '@astrojs/tailwind' 4 | 5 | export default defineConfig({ 6 | site: 'https://mage-os.org', 7 | integrations: [ 8 | vue(), 9 | tailwind() 10 | ] 11 | }) 12 | -------------------------------------------------------------------------------- /public/browserconfig.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | #ffc40d 7 | 8 | 9 | 10 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # build output 2 | dist 3 | 4 | # dependencies 5 | node_modules/ 6 | .snowpack/ 7 | .yarn/ 8 | .yarnrc.yml 9 | 10 | # logs 11 | npm-debug.log* 12 | yarn-debug.log* 13 | yarn-error.log* 14 | 15 | # environment variables 16 | .env 17 | .env.production 18 | 19 | # macOS-specific files 20 | .DS_Store 21 | 22 | # Vercel 23 | .vercel 24 | 25 | # Social sharing autogenerated images 26 | public/socials/ 27 | -------------------------------------------------------------------------------- /vercel.json: -------------------------------------------------------------------------------- 1 | { 2 | "headers": [ 3 | { 4 | "source": "/fonts/(.*)", 5 | "headers": [ 6 | { 7 | "key": "Cache-Control", 8 | "value": "public, max-age=31556952, immutable" 9 | } 10 | ] 11 | } 12 | ], 13 | "redirects": [ 14 | { 15 | "source": "/qr", 16 | "destination": "https://mage-os.org/", 17 | "permanent": false 18 | } 19 | ] 20 | } 21 | -------------------------------------------------------------------------------- /src/components/Button.astro: -------------------------------------------------------------------------------- 1 | --- 2 | const props = Astro.props 3 | const styles = ` 4 | py-2 px-4 5 | border border-primary 6 | font-bold text-primary 7 | hover:bg-primary hover:text-white 8 | transition rounded 9 | ` 10 | 11 | if (props.class) { 12 | props.class = props.class + ' ' + styles 13 | } 14 | else { 15 | props.class = styles 16 | } 17 | 18 | --- 19 | 22 | 23 | 24 | -------------------------------------------------------------------------------- /src/layouts/document.astro: -------------------------------------------------------------------------------- 1 | --- 2 | import Layout from './default.astro' 3 | 4 | const { content } = Astro.props 5 | --- 6 | 7 |
8 |

15 | { content.title } 16 |

17 |
18 | 19 |
20 | 21 |
22 | 23 | -------------------------------------------------------------------------------- /src/pages/distribution/why-use-mage-os.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Why use Mage-OS? 4 | description: Why use Mage-OS? 5 | draft: true 6 | --- 7 | 8 | 17 | -------------------------------------------------------------------------------- /public/site.webmanifest: -------------------------------------------------------------------------------- 1 | { 2 | "name": "Mage Open Source Community Alliance", 3 | "short_name": "Mage OS", 4 | "icons": [ 5 | { 6 | "src": "/android-chrome-192x192.png", 7 | "sizes": "192x192", 8 | "type": "image/png" 9 | }, 10 | { 11 | "src": "/android-chrome-512x512.png", 12 | "sizes": "512x512", 13 | "type": "image/png" 14 | } 15 | ], 16 | "theme_color": "#ffffff", 17 | "background_color": "#ffffff", 18 | "display": "standalone" 19 | } 20 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "mage-os.org", 3 | "private": true, 4 | "scripts": { 5 | "dev": "astro dev", 6 | "build": "astro build && node inline-styles.mjs && cp -R public/socials dist" 7 | }, 8 | "dependencies": { 9 | "@astrojs/tailwind": "^0.2.1", 10 | "@astrojs/vue": "^0.1.5", 11 | "@tailwindcss/typography": "^0.5.2", 12 | "astro": "^0.26.1", 13 | "astro-social-images": "^0.4.1", 14 | "globby": "^13.1.1", 15 | "got": "^11.8.5", 16 | "md5": "^2.3.0", 17 | "vue": "^3.2.37" 18 | }, 19 | "volta": { 20 | "node": "14.19.0" 21 | } 22 | } 23 | -------------------------------------------------------------------------------- /tailwind.config.cjs: -------------------------------------------------------------------------------- 1 | const { fontFamily } = require('tailwindcss/defaultTheme') 2 | const colors = require('tailwindcss/colors') 3 | 4 | module.exports = { 5 | content: [ 6 | './public/**/*.html', 7 | './src/**/*.{astro,js,ts,vue}' 8 | ], 9 | theme: { 10 | extend: { 11 | colors: { 12 | primary: '#F37121', 13 | secondary: '#FF9234', 14 | }, 15 | }, 16 | fontFamily: { 17 | sans: [ 18 | 'Montserrat', 19 | ...fontFamily.sans 20 | ], 21 | }, 22 | }, 23 | plugins: [ 24 | require('@tailwindcss/typography') 25 | ] 26 | }; 27 | -------------------------------------------------------------------------------- /src/pages/imprint.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Imprint 4 | description: Imprint 5 | --- 6 | 7 | The website mage-os.org is operated by the members and representatives of the Mage-OS Association, as registered in Poland according to the [statutes](/organization/statutes). 8 | 9 | Names of the current Mage-OS Board of Directors can be found on the [About page](/organization/about#board-of-directors). Contact info for each can be found on their respective websites. 10 | 11 | Representative contact regarding all matters of the website is Vinai Kopp. 12 | 13 | Email: info@mage-os.org 14 | Address: Reichensteinstr. 36, 69151 Neckargemünd, Germany 15 | 16 | -------------------------------------------------------------------------------- /src/layouts/post.astro: -------------------------------------------------------------------------------- 1 | --- 2 | import Layout from './default.astro' 3 | import Newsletter from '../components/Newsletter.astro' 4 | const { content } = Astro.props 5 | --- 6 | 7 |
8 |

15 | { content.title } 16 |

17 | 18 |
19 | { new Intl.DateTimeFormat('en-GB', { dateStyle: 'long', timeZone: 'UTC' }).format(new Date(content.date))} 20 |
21 |
22 | 23 |
24 | 25 |
26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /api/subscribe.js: -------------------------------------------------------------------------------- 1 | import got from 'got' 2 | 3 | export default async (request, response) => { 4 | const apiKey = process.env.MAILERLITE_API_KEY 5 | 6 | const { groupId, email, name, company } = JSON.parse(request.body) 7 | 8 | try { 9 | const reply = await got({ 10 | method: 'POST', 11 | url: `https://api.mailerlite.com/api/v2/groups/${groupId}/subscribers`, 12 | headers: { 13 | 'X-MailerLite-ApiKey': apiKey, 14 | }, 15 | json: { 16 | email, 17 | name, 18 | fields: { 19 | company 20 | } 21 | } 22 | }) 23 | 24 | response.send(reply.body) 25 | } 26 | catch (error) { 27 | response.status(500).send(error.response.body) 28 | } 29 | } 30 | -------------------------------------------------------------------------------- /src/components/Newsletter.astro: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | --- 4 | 5 | 6 | 15 | 16 | 17 |
22 |
23 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Mage-OS Website 2 | 3 | ![Mage-OS Association Logo](./public/mage-os-logo.png) 4 | 5 | ## Communication Guide 6 | 7 | 1. All writing must comply with the [code of conduct](./src/pages/code-of-conduct.md). 8 | 2. All writing must be localized to US English (en_US). 9 | 3. All images must have accessible alt tags. 10 | 4. Do your best to convey these tenets of the Mage-OS initiative: 11 | - Collaboration 12 | - Positivity 13 | - Stability 14 | 5. Do your best to write in simple words. Avoid idioms or references that global audiences might not know. 15 | 16 | ---- 17 | 18 | ## Local setup 19 | 20 | ### Requirements 21 | - Node.js >=14.19 <15 - Usage of volta.sh is recommended 22 | - Yarn >=1.22 <2 23 | 24 | ### Development 25 | To run the site locally for development purposes, clone the repository, then run in terminal at the repository base folder: 26 | 27 | ``` 28 | yarn 29 | yarn dev 30 | ``` 31 | 32 | You can then access your local site at http://127.0.0.1:3000/ (by default). 33 | -------------------------------------------------------------------------------- /src/pages/blog/rss/[...page].astro: -------------------------------------------------------------------------------- 1 | --- 2 | export async function getStaticPaths({rss}) { 3 | const allPosts = await Astro.glob('../*.md') 4 | const sortedPosts = allPosts 5 | .map(({ url, frontmatter }) => ({ url, ...frontmatter })) 6 | .sort((a, b) => new Date(b.date) - new Date(a.date)) 7 | 8 | rss({ 9 | // The RSS Feed title, description, and custom metadata. 10 | title: 'Mage-OS Blog', 11 | // See "Styling" section below 12 | stylesheet: true, 13 | description: 'The Mage-OS Association Blog', 14 | customData: `en-us`, 15 | // The list of items for your RSS feed, sorted. 16 | items: sortedPosts.map(item => ({ 17 | title: item.title, 18 | description: item.description, 19 | link: item.url, 20 | pubDate: item.date, 21 | })), 22 | // Optional: Customize where the file is written to. 23 | // Otherwise, defaults to "/rss.xml" 24 | dest: "/rss.xml", 25 | }) 26 | 27 | return [] 28 | } 29 | --- 30 | -------------------------------------------------------------------------------- /src/layouts/post-with-sign-form.astro: -------------------------------------------------------------------------------- 1 | --- 2 | import Layout from './default.astro' 3 | import SignList from '../components/SignList.vue' 4 | import Newsletter from '../components/Newsletter.astro' 5 | 6 | const { content } = Astro.props 7 | const { groupId } = content 8 | 9 | const subscribers = await fetch(`${Astro.site}/api/subscribers-list?groupId=${groupId}`).then(res => res.json()) 10 | --- 11 | 12 |
13 |

20 | { content.title } 21 |

22 | 23 |
24 | { new Intl.DateTimeFormat('en-GB', { dateStyle: 'long' }).format(new Date(content.date))} 25 |
26 |
27 | 28 |
29 | 30 |
31 | 32 | 36 | 37 | 38 | 39 | -------------------------------------------------------------------------------- /inline-styles.mjs: -------------------------------------------------------------------------------- 1 | import path from 'node:path' 2 | import fs from 'node:fs/promises' 3 | import { globby } from 'globby' 4 | 5 | const root = path.resolve('./dist') 6 | const files = await globby('./dist/**/index.html') 7 | 8 | await Promise.all( 9 | files.map(async htmlPath => { 10 | const pageStyles = [] 11 | const stylesPaths = [] 12 | 13 | let file = await fs.readFile(htmlPath, 'utf-8') 14 | 15 | file = file.replace( 16 | //g, 17 | (match, p1) => { 18 | stylesPaths.push(p1) 19 | return '' 20 | } 21 | ) 22 | 23 | await Promise.all( 24 | stylesPaths.map(async stylesPath => { 25 | const styles = await fs.readFile(path.join(root, stylesPath), 'utf-8') 26 | pageStyles.push(styles) 27 | }) 28 | ) 29 | 30 | file = file.replace( 31 | '', 32 | `\n` 33 | ) 34 | 35 | await fs.writeFile(htmlPath, file) 36 | }) 37 | ) 38 | -------------------------------------------------------------------------------- /api/subscribers-list.js: -------------------------------------------------------------------------------- 1 | import got from 'got' 2 | import md5 from 'md5' 3 | 4 | export default async (request, response) => { 5 | try { 6 | const apiKey = process.env.MAILERLITE_API_KEY 7 | 8 | const raw = await got({ 9 | method: 'GET', 10 | url: `https://api.mailerlite.com/api/v2/groups/${request.query.groupId}/subscribers/active?limit=5000`, 11 | headers: { 12 | 'X-MailerLite-ApiKey': apiKey, 13 | }, 14 | timeout: { 15 | request: 300000 16 | } 17 | }).json() 18 | 19 | const subsribers = raw 20 | .map(subscriber => ({ 21 | avatar: `https://www.gravatar.com/avatar/${md5(subscriber.email.toLowerCase())}`, 22 | name: subscriber.name, 23 | company: subscriber.fields.find(({ key }) => key === 'company')?.value || null 24 | })) 25 | .reverse() 26 | 27 | response.setHeader('Cache-Control', 's-maxage=86400, stale-while-revalidate=2592000') 28 | response.json(subsribers) 29 | 30 | } 31 | catch (error) { 32 | response.status(500).json(error) 33 | } 34 | } 35 | -------------------------------------------------------------------------------- /src/pages/blog/20221011-new-magento-release.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-10-11 4 | title: Magento 2.4.5-p1 release 5 | description: Now available on mirror.mage-os.org 6 | --- 7 | 8 | Adobe has released updates to Magento Open Source today, versions 2.4.5-p1 and 2.4.4-p2. 9 | 10 | Those same updates are now also available if you're using our Magento mirror composer repository, `mirror.mage-os.org`. Our validation has confirmed the mirror releases are installable and match the official releases. 11 | 12 | Thanks to Vinai Kopp and Damien Retzinger for managing the release process. 13 | 14 | If you're not yet using the Mage-OS Magento mirror, you can do that today by swapping `repo.magento.com` to `mirror.mage-os.org` in your composer.json (unless you require any Magento Marketplace packages). This is a public repository, built by our independent open source build process from the Magento 2 source code. For more info on the Mage-OS nightly and mirror repositories, see: https://mage-os.org/distribution 15 | 16 | We have plans to launch the Mage-OS Distribution and start accepting pull requests by the end of this year. Stay tuned for more! 17 | -------------------------------------------------------------------------------- /src/components/PostPreviewList.astro: -------------------------------------------------------------------------------- 1 | --- 2 | const { posts } = Astro.props 3 | function getMonthName(date) { 4 | return new Date(date).toLocaleString('en-US', { month: 'short', timeZone: 'UTC' }) 5 | } 6 | --- 7 |
8 | {posts.map(post => ( 9 |
10 |
11 |
12 | 13 | {new Date(post.date).getUTCDate()} 14 | 15 | 16 | 17 | {`${getMonthName(post.date)} ${new Date(post.date).getUTCFullYear()}`} 18 | 19 |
20 |
21 | 22 |
23 |

31 | 35 | {post.title} 36 | 37 |

38 | 39 |

40 | {post.description} 41 |

42 |
43 |
44 | ))} 45 |
46 | -------------------------------------------------------------------------------- /src/pages/blog/[page].astro: -------------------------------------------------------------------------------- 1 | --- 2 | export async function getStaticPaths({ paginate }) { 3 | const rawPosts = await Astro.glob('./*.md') 4 | 5 | const posts = rawPosts 6 | .map(({ url, frontmatter }) => ({ url, ...frontmatter })) 7 | .sort((a, b) => new Date(b.date) - new Date(a.date)) 8 | 9 | return paginate(posts, { pageSize: 10 }) 10 | } 11 | 12 | import Layout from '@/layouts/default.astro' 13 | import PostPreviewList from '@/components/PostPreviewList.astro' 14 | import Button from '@/components/Button.astro' 15 | 16 | const { page } = Astro.props 17 | 18 | const content = { 19 | title: 'Blog | Mage-OS', 20 | description: 'An overview of all Mage-OS blog posts.', 21 | socialTitle: 'The Mage-OS Blog', 22 | socialDescription: 'An overview of all Mage-OS blog posts.' 23 | } 24 | 25 | --- 26 | 27 | 28 |
29 |

30 | Blog 31 |

32 |
33 | 34 | 35 | 36 | {page.lastPage > 1 && 37 |
38 |
39 | {page.url.prev ? : null} 40 | {page.url.next ? : null} 41 |
42 |

43 | Page {page.currentPage} of {page.lastPage} 44 |

45 |
46 | } 47 | 48 | -------------------------------------------------------------------------------- /src/components/Footer.astro: -------------------------------------------------------------------------------- 1 | --- 2 | const year = new Date().getFullYear() 3 | --- 4 | 26 | -------------------------------------------------------------------------------- /src/components/SignList.vue: -------------------------------------------------------------------------------- 1 | 49 | 50 | 64 | -------------------------------------------------------------------------------- /src/utils/MetaTags.astro: -------------------------------------------------------------------------------- 1 | --- 2 | const { title, description, permalink, image } = Astro.props 3 | --- 4 | 5 | 6 | 7 | {title} 8 | 9 | {description && } 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | {permalink && } 26 | {description && } 27 | {image && } 28 | 29 | 30 | 31 | 32 | 33 | {permalink && } 34 | {description && } 35 | {image && } 36 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-19.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-05-19 4 | title: Week 15 - 19 of 2022 5 | description: An update on the last weeks of progress on Mage-OS 6 | --- 7 | 8 | We see a bright future for Magento Open Source. 9 | 10 | ## Technical topics 11 | 12 | Work was on hold a bit while some of the group were busy with HyväCmp, but expect news on this front soon! 13 | 14 | ## Organizational topics 15 | 16 | ### The Mage-OS Association 17 | 18 | In the last few days, we’ve been busy defining the final details to found the Mage-OS Association. 19 | It will collect and distribute the resources to make our vision come true. 20 | 21 | As mentioned in our [previous post](https://mage-os.org/blog/mage-os-update-2022-week-14), we defined the initial Board of Directors. 22 | It will include seven people (president, vice-president, treasurer, actuary, and three more members). 23 | 24 | A Business Control Committee of two more people will review the work of the Board of Directors. 25 | 26 | In addition, we already have committees set up and running such as: 27 | 28 | * Mage-OS Technical committee 29 | * Magento Content Resource committee 30 | 31 | Some more forming committees will also contribute to other necessary areas, like branding, marketing, and strategy. Planning, work, and discussion on those tasks are already taking place in our Discord chat. 32 | 33 | To set the initial board and committees, we chose people that devoted their time to the cause from the beginning. The following is an alphabetically-ordered list; we will disclose the assigned roles soon: 34 | 35 | * Peter Jaap Blaakmeer (NL) 36 | * Ryan Hoerr (US) 37 | * John Hughes (UK) 38 | * Maciej Kalkowski (PL) 39 | * Vinai Kopp (DE) 40 | * Ignacio Riesco (ES) 41 | * Alessandro Ronchi (IT) 42 | * Simon Sprankel (DE) 43 | * Wouter Steenmeijer (NL) 44 | * Thien-Lan Weber (FR) 45 | 46 | Anyone who wants to contribute can join us on Discord (https://discord.gg/nvZDVA2NdC). 47 | 48 | That's all for today! Stay safe and prosper, 49 | 50 | The Mage-OS folks 51 | -------------------------------------------------------------------------------- /src/pages/privacy-policy.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Privacy policy 4 | description: Privacy policy 5 | --- 6 | 7 | In this document, “We” refers to the group of original signers of the open letter to the Magento community. 8 | The purpose of this privacy policy is to clarify how the data that is collected by visiting this website is used and processed. 9 | 10 | The privacy and data of anybody visiting this site is very important to us. We track as little information about visitors as possible. 11 | 12 | By accessing this website, your IP address and browser information will be stored in the hosting providers logs. The website hosting is managed by Vercel who in turn use other rented infrastructure. For more information please visit https://vercel.com/legal/privacy-policy. 13 | 14 | We ourselves do not have access to those logs and do not collect any additional information. 15 | 16 | We use the services of the company mailerlite.com to allow visitors to add their name posts to signal support. The visitors, name, email and - if specified - company name will be sent to mailerlite.com via their API. 17 | They will store and process this information according to the mailerlite.com privacy policy which can be found at https://www.mailerlite.com/legal/privacy-policy. 18 | By confirming the signature through the double-opt-in email, a signing visitor might be sending additional data to mailerlite, like the IP address, mail agent and viewing preferences. 19 | Again, this data is also subject to the mailerlite privacy-policy. 20 | 21 | Beside mailerlite, we will not give any other third party access to the visitor name, email address and company name. 22 | We reserve the right to send an email to all signees in future to inform about significant developments in regards to the future of Magento Open Source. 23 | 24 | If requested by the owner of the email via a message to info@mage-os.org, we will remove their name from the signature list should someone choose to change their mind. 25 | 26 | For further questions regarding the collection and use of personal data, please contact info@mage-os.org. 27 | -------------------------------------------------------------------------------- /public/safari-pinned-tab.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | -------------------------------------------------------------------------------- /src/layouts/default.astro: -------------------------------------------------------------------------------- 1 | --- 2 | import { generateSocialImage } from 'astro-social-images' 3 | import MetaTags from '@/utils/MetaTags.astro' 4 | import Header from '@/components/Header.astro' 5 | import Footer from '@/components/Footer.astro' 6 | import "../assets/styles/global.css"; 7 | 8 | const { content } = Astro.props 9 | const title = content?.title || '' 10 | const description = content?.description || '' 11 | const permalink = Astro.canonicalURL.href 12 | 13 | const image = generateSocialImage({ 14 | backgroundColor: '#ffe9d6', 15 | images: [ 16 | { url: 'public/social-preview-background.png', attributes: { x: 0, y: 0 } } 17 | ], 18 | texts: [ 19 | { 20 | content: content?.socialTitle || content?.title || 'Community-Driven Commerce', 21 | attributes: { x: '25', y: '225', 'font-size': '50px', fill: '#15133c', style: 'font-family: Montserrat; z-index: 1000;' }, 22 | }, 23 | { 24 | content: content?.socialDescription || content?.description || '', 25 | attributes: { x: '25', y: '375', 'font-size': '24px', fill: '#15133c', style: 'font-family: Montserrat; z-index: 1000;' }, 26 | }, 27 | ] 28 | }, { 29 | hashLength: 12, 30 | urlPath: 'https://mage-os.org/' 31 | }) 32 | --- 33 | 34 | 35 | 36 | 52 | 53 | 54 | 55 | 61 | 62 | 63 | 69 |
73 |
74 | 75 |
76 | 77 |
78 | 79 |
80 |
81 | 82 | 83 | -------------------------------------------------------------------------------- /src/pages/blog/20221102-mageos-distro-repos-and-more.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-11-02 4 | title: Going beyond the Mirror - Mage-OS Nightlies 5 | description: Mage-OS Distribution nightly builds are now available on nightly.mage-os.org 6 | --- 7 | 8 | As we all are busy bees, a lot has been happening! 9 | 10 | ## The Mage-OS community is growing! 11 | 12 | New faces are joining the meetings and more and more people are eager to contribute. Very exciting! 13 | 14 | Please join the fun and chime in on [Discord](http://chat.mage-os.org). The volume of messages still is very manageable. 15 | 16 | ## Mage-OS Distribution Repositories 17 | 18 | The GitHub repositories forming the foundation of the independent Mage-OS distribution have been set up. 19 | 20 | GitHub workflows automatically merge upstream changes. In case of a merge conflict, notifications are sent out and the automatic merge process is paused until the conflict is resolved by a human. 21 | 22 | Special thanks to [Daniel Sloof](https://github.com/mage-os/mageos-magento2/pull/1) for creating the workflow, and [Damien Retzinger](https://github.com/damienwebdev) as well as [Vinai Kopp](https://github.com/vinai) for helping to set them up for all the repos! 23 | 24 | ## GitHub Permissions 25 | 26 | Mage-OS GitHub access permissions and PR review rules are now [enforced by Terraform](https://github.com/mage-os/terraform). This automation helps avoid human error and eases the overall maintenance burden on contributors. 27 | 28 | Thank you to [Simon Sprankel](https://github.com/sprankhub) for leading the effort, and also (in no particular order) [Jakub Pieńkowski](https://github.com/Jakski), [Vitaliy Golomoziy](https://github.com/vitaliy-golomoziy), [Andreas Mautz](https://twitter.com/mautz_et_tong), and [Alexander Buch](https://twitter.com/keen_code) ([cartware.de](https://www.cartware.de/)) for contributing! 29 | 30 | ## Roadmap 31 | 32 | The immediate next step is to finalize CI for the nightly builds for the distribution repositories, and to set up testing. 33 | 34 | We then are looking forward to starting accepting pull requests by the end of December 2022! Figuring out the best way to handle them will take time, so please be patient with us! 35 | 36 | If you are interested in helping with our work in setting up the Mage-OS Distribution, please review the [Path to PRs project](https://github.com/orgs/mage-os/projects/3), and join us in the [#tech channel on Discord](https://discord.com/channels/893449664093904936/950670671145467924). 37 | 38 | 39 | 40 | (Much) more soon, thanks for reading! 🙌🏻 41 | 42 | The Mage-OS folks 43 | -------------------------------------------------------------------------------- /src/pages/get-involved.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Get Involved 4 | description: Get Involved 5 | --- 6 | 7 | Want to help out with Mage-OS? We'd love to have you! Since the Mage-OS project is still relatively young, you have a tremendous opportunity to have a positive impact on the project and community by getting involved today. 8 | 9 | ## Join the discussion 10 | 11 | This is an open, positive, and inclusive community. Please read the [Code of Conduct](/code-of-conduct). 12 | 13 | Join Discord chat: http://chat.mage-os.org 14 | Browse Github: https://github.com/mage-os 15 | 16 | ## Spread the word 17 | 18 | Tell your friends the good news! Mage-OS is here to make your lives a little happier. The more people get excited and join in, the faster this distribution can grow. Help us reach the whole community around the world. 19 | 20 | ## Support Mage-OS 21 | 22 | If Mage-OS or Magento is important to you or your company, we encourage you to become a supporter! 23 | 24 | - Become a card-carrying member 25 | - Directly support ongoing development of the Mage-OS platform 26 | - Get a vote in Mage-OS elections, resolutions, and direction 27 | 28 | Rates and levels will be announced soon! Join [our email list](/newsletter) or [Discord](http://chat.mage-os.org) to get notified. 29 | 30 | ## Contribute 31 | 32 | Talk to us, clone the repository, then start submitting pull requests! All contributions must conform to the Code of Conduct and code standards. Contributions may not be accepted unless they are in line with the Mage-OS vision and direction. If you are unsure, please reach out to us on Discord in [#tech](https://discord.com/channels/893449664093904936/950670671145467924), we'd be happy to discuss it with you. 33 | 34 | Please note, even with the above, not all contributions will be accepted. That being said, we will do our best to process pull requests fairly, transparently, and in reasonable time. 35 | 36 | Github: https://github.com/mage-os/mageos-magento2 37 | 38 | ## Meetings 39 | 40 | We currently have two weekly meetings which are open for anyone to join and participate in. If you want to start helping with Mage-OS, joining our Discord and one or both of these meetings is the best way to do that. 41 | 42 | #### Content Meeting 43 | Each Monday at 4pm CET (10am EST), the content committee goes over progress and next steps for creating an informational site about Magento Open Source. Join the [Google Meet](https://meet.google.com/yiw-vfsk-dsm) at the scheduled time, or contact John Hughes in Discord to be added to the calendar event. 44 | 45 | #### Technical Meeting 46 | Each Tuesday at 3pm CET (9am EST), contributors meet to discuss the technical progress of the Mage-OS distribution. Join the [Discord Meeting Room](https://discordapp.com/channels/893449664093904936/900634980571557948) at the scheduled time, or contact Vinai in Discord to be added to the calendar event. 47 | -------------------------------------------------------------------------------- /src/pages/code-of-conduct.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Code of Conduct 4 | description: Code of Conduct 5 | --- 6 | 7 | All participants of Mage-OS are expected to abide by our Code of Conduct, both online and during in-person events that are hosted and/or associated with Mage-OS. 8 | 9 | ## The Pledge 10 | 11 | In the interest of fostering an open and welcoming environment, we pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 12 | 13 | ## The Standards 14 | 15 | Examples of behavior that contributes to creating a positive environment include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Referring to people by their preferred pronouns and using gender-neutral pronouns when uncertain 21 | 22 | Examples of unacceptable behavior by participants include: 23 | 24 | * Trolling, insulting/derogatory comments, public or private harassment 25 | * Publishing other’s private information, such as a physical or electronic address, without explicit permission 26 | * Not being respectful to reasonable communication boundaries, such as “leave me alone”, “go away”' or “I’m not discussing this with you.” 27 | * The usage of sexualized language or imagery and unwelcome sexual attention or advances 28 | * Swearing, usage of strong or disturbing language 29 | * Demonstrating the graphics or any other content you know may be considered disturbing 30 | * Starting and/or participating in arguments related to politics 31 | * Assuming or promoting any kind of inequality including but not limited to: age, body size, disability, ethnicity, gender identity and expression, nationality and race, personal appearance, religion, or sexual identity and orientation 32 | * Drug promotion of any kind 33 | * Attacking personal tastes 34 | * Other conduct which you know could reasonably be considered inappropriate in a professional setting. 35 | 36 | ## Enforcement 37 | 38 | Violations of the Code of Conduct may be reported by sending an email to conduct@mage-os.org. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Further details of specific enforcement policies may be posted separately. 39 | 40 | We hold the right and responsibility to remove comments or other contributions that are not aligned to this Code of Conduct or to ban temporarily or permanently any members for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 41 | 42 | ## Attribution 43 | 44 | This Code of Conduct is generated by https://miloslav.website/code-of-conduct/ and adapted from [dev.to](https://dev.to/code-of-conduct). 45 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-25.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-06-26 4 | title: Week 20 - 25 of 2022 5 | description: An update on the last weeks of progress on Mage-OS 6 | --- 7 | 8 | We see a bright future for Magento Open Source. 9 | 10 | ## Technical Topics 11 | 12 | We've been working on establishing nightly builds from the public Magento source repositories. This is an important stepping stone toward increased testability and community involvement. 13 | 14 | There are still details and parts of the process to be finalized. Ultimately you will be able to use the Mage-OS nightly repository to install Magento's latest published development progress for a given day, such as: 15 | 16 | composer create-project --stability alpha magento/product-community-edition:2.4-a20220624 17 | 18 | More to come. Please join us on Discord in [#tech](https://discord.com/channels/893449664093904936/950670671145467924) if you'd like to get involved. 19 | 20 | 21 | ## Organizational Topics 22 | 23 | ### The Mage-OS Association 24 | 25 | Our by-laws and founding process have all been finalized, and we are on track to form the Association in the next month or so. 26 | 27 | As mentioned in our [previous post](https://mage-os.org/blog/mage-os-update-2022-week-19), we nominated members of the Board of Directors and well as the Control Committee. 28 | 29 | Meet Magento UK gave many of us an opportunity to meet in real life, sign a couple of legal documents, and celebrate. 30 | 31 | ![Mage-OS Founding With Ignacio Riesco, Thien-Lan Weber, Maciej Kalkowski and John Hughes](/blog/2022/mage-os-founding.jpg "Mage-OS Founding With Ignacio Riesco, Thien-Lan Weber, Maciej Kalkowski and John Hughes") 32 | 33 | ### Mage-OS Brand Identity 34 | 35 | We confirmed our name, Mage-OS, that both stands for our Association and our distribution system, and brought it to life with a logo (see header above) that captures the vibrant spirit of the Magento Community, and, through the blocks emphasizes how everyone can rise, connect and contribute to building this bright future for Magento Open Source. 36 | 37 | ## Community Topics 38 | 39 | ### Getting the Pulse of the Magento Community 40 | 41 | The recent Meet Magento UK event allowed us to gather in London and reconnect in person with the Community. We shared ideas and discussed point of views with all parts of the Magento Community including Adobe staff, the UK Community, and people who flew from as far as Argentina or Canada to get those Magento hugs again. 42 | 43 | As we knew all along, Magento is alive and well, and there are many more merchants and agencies still using the platform and rooting for it than one may think. This lack of visibility is one challenge we hope to tackle. If you're interested in helping, whatever you can contribute, please join us on [Discord](https://discord.gg/nvZDVA2NdC)! 44 | 45 | https://twitter.com/wsakaren/status/1539918577272328198 46 | 47 | ## Social Media Channels 48 | 49 | You can connect with us, share ideas, or follow our progress on... 50 | 51 | * Twitter: [@mage_os](https://twitter.com/mage_os) 52 | * LinkedIn: [Company page](https://www.linkedin.com/company/mage-os/) and handle to tag us: @mage-os 53 | * [Discord](https://discord.gg/nvZDVA2NdC) 54 | 55 | That's all for today! Stay safe and prosper, 56 | 57 | The Mage-OS folks 58 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-11.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-03-18 4 | title: Week 10 and 11 of 2022 5 | description: An update on the last two weeks of progress on Mage-OS 6 | --- 7 | 8 | The ongoing horrific war in Ukraine means we continue to prioritize supporting our friends, family members and coworkers there. 9 | We nevertheless have managed to make progress with Mage-OS, too. 10 | 11 | ## Technical topics 12 | 13 | ### Mirror distribution 14 | 15 | The mirror distribution available at [mirror.mage-os.org](https://mirror.mage-os.org) is now fully functional. It can be used to install Magento Open Source versions 2.4.0 up to 2.4.3-p1 using independently built composer packages. 16 | 17 | Try it: 18 | ```bash 19 | mkdir mage-os-243p1 20 | composer create-project --repository-url=https://mirror.mage-os.org/ magento/project-community-edition mage-os-243p1 2.4.3-p1 21 | ``` 22 | 23 | Build your own mirror: 24 | 25 | It is easy to host your very own mirror with self-built packages using the mirror repository generator found at [github.com/mage-os/generate-mirror-repo-js](https://github.com/mage-os/generate-mirror-repo-js). 26 | 27 | The generation from scratch takes about 1.5 hours on a low-end server (2G RAM, no swap). We are actively improving the tool to make it faster and more usable, however, alternative implementations will be the primary tools in the future. The current JavaScript based implementation was started as a research project. 28 | 29 | If you have questions of ideas, please join our discord at [discord.gg/nvZDVA2NdC](https://discord.gg/nvZDVA2NdC) and say hi in the #tech channel. 30 | 31 | ### GitHub permissions 32 | 33 | No progress has been made on this topic because of real life matters. Work will continue in the coming week. 34 | 35 | 36 | ## Organizational topics 37 | 38 | ### Operations management 39 | 40 | We discussed two ways to bootstrap the organization behind Mage-OS: 41 | 42 | 1. Find a person to act as the COO, who's first task will be to create the organization and their own role. 43 | This would be a lot quicker, but it also would require someone who is able to work full time without immediately requiring compensation. 44 | 45 | 2. Found the organization ourselves, which then allows us to collect funds. Then hire a COO. 46 | 47 | We will take this second option as this allows us to make faster progress and deal with filling COO and other roles in near future. 48 | So far we have drafted by-laws which are being verified independently by two lawyers. 49 | 50 | We are very excited about the prospect that soon there will be an organization to provide a solid foundation for Mage-OS! 51 | 52 | 53 | ### Magento Association 54 | 55 | We do not see the supporting organization around Mage-OS in conflict with the Magento Association. 56 | Each is distinct. The Mage-OS organization moves quicker and brings a much-needed external point of view to the table, while the Association is able to work with Adobe through established channels and can rely on the support provided by a big company. 57 | 58 | Mage-OS future-proofs Magento Open Source by providing an independent distribution. 59 | We envision Mage-OS, the Magento Association STS and Adobe LTS/Commerce distributions collaborating closely. 60 | 61 | Should at one time in the future Mage-OS become obsolete because of the Magento Association STS distribution, they can be merged. 62 | 63 | We continue to believe speed is of an essence, so we will continue to move forward without being held back by established processes. 64 | 65 | 66 | That's all for today! Stay safe and prosper, 67 | 68 | The Mage-OS folks -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-7.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-02-20 4 | title: Week 7 of 2022 5 | description: An update on last week's progress on Mage-OS 6 | --- 7 | 8 | Welcome to an update fresh out of the Mage-OS kitchen. 9 | 10 | 11 | ## Technical topics 12 | 13 | ### Mirror distribution 14 | 15 | We are able to run a full local installation based on self-generated packages, but it doesn’t work remotely yet, because the package URLs in the packages.json file generated by satis still need to be prefixed with the repository URL. This should be fixed over the coming weekend. 16 | 17 | The JavaScript based build tool is bundled as a docker image which will be used to create a Mage-OS mirror repository on any server with docker (or podman). 18 | This will allow us to change the underlying implementation of the tool creating the packages without impacting the mirror provider - they only need to pull the latest version of the image. 19 | 20 | We agreed to host the initial mirror distribution on a server rented by us, because we don't want to favor a specific hosting provider. 21 | We hope many hosting providers will use the opportunity to provide fast local package mirrors to their customers. 22 | 23 | ### Opening up to the wider community 24 | 25 | We want to open up our Discord and the mage-os GitHub organization once we have a fully functioning self built package mirror running. We are looking forward to collaborating with many developers from all over the world in building up the Mage-OS distributions. 26 | Before we open things up, we decided to publish a Code of Conduct on our website and ask everyone to agree with our shared base values before joining. 27 | We also need to set up team based access rights in the GitHub organization. 28 | 29 | ## Organizational topics 30 | 31 | ### Magento Association 32 | 33 | We discussed our individual relationship with the Magento Association and agreed there is no conflict of interest if members of our group also fulfill tasks in the MA. 34 | We also agreed that by continuing to work independently of the MA as part of the Mage-OS community alliance, we also serve the community by helping move the status quo. 35 | 36 | ### Magento STS vs LTS 37 | 38 | We discussed how STS and LTS security updates might be handled, and who might be able to provide vendor based support. 39 | Since Adobe wants to hand ownership of Magento STS to the community, they might not be able to provide security patches. 40 | We are convinced there is a shared interest in collaboration on this topic, and that a way to coordinate the release of security related patches can be found. 41 | This will be a topic for further discussion in the Magento Open Source Task Force. 42 | 43 | ### Magento Open Source Content 44 | 45 | We assembled a content plan for the promotional, informational and branding related content for merchants about Magento Open Source. Several members of the community have agreed to help create this content. As soon as we have at least ten meaningful articles we will publish them on the to be created mage-os.org website. 46 | Should Adobe or the Magento Association also decide to provide such content, we will be happy to move content there. 47 | 48 | ### Magento and Adobe Commerce Support 49 | 50 | During the last Magento Open Source Task Force meeting we discussed the lack of publicly available long term support information for both Adobe Commerce and Magento Open Source. Adobe members of the task force agreed that should be made available and stated they would look into it. 51 | 52 | ### Docker Hub Username 53 | 54 | Sadly “mageos” is not available. Only characters and numbers are allowed, which means “mage-os” is not valid there. The next best free username we found on docker hub is “magece”. 55 | 56 | 57 | 58 | That's all for this week. 59 | More coming soon, 60 | 61 | *The whole Mage-OS team* -------------------------------------------------------------------------------- /src/pages/blog/20221202-meetcommerce.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-12-02 4 | title: Meet you soon in Madrid! 5 | description: Mage-OS will be at Meet Commerce Spain on December 13th, see you there! 6 | --- 7 | 8 | ![A banner of the Mage-OS talk Vinai Kopp will be giving at MeetCommerce.es.](/blog/2022/2022-12-02-meetcommerce-mage-os-talk-bannner.jpg) 9 | 10 | [Meet Commerce Spain](https://meetcommerce.es/) is taking place on Tuesday 13th December, in Madrid, Spain. 11 | 12 | For a couple of months, the team at Mage-OS has been preparing for this event with much enthusiasm and excitement. 13 | 14 | Why? Because it felt so good to catch up in person at Meet Magento New York 2022, we wanted to do it again. Also, this event is strongly connected with Mage-OS as Ignacio Riesco is CEO of the organizing agency Interactiv4, and also sits on the board of Mage-OS. 15 | 16 | ## Mage-OS at Meet Commerce 17 | ### Mage-OS Presentation 18 | 19 | Vinai Kopp, Board President and founding member of Mage-OS, will be presenting at Meet Commerce Spain: [“Mage-OS: Fork it, Own it, Grow it, Better”](https://www.linkedin.com/feed/update/urn:li:activity:6996423767186923520). 20 | 21 | This talk is inspired by all the conversations we've had with you, people and friends from the Magento Community, who have been expressing support, giving constructive feedback, and asking questions ([lots of questions](https://mage-os.org/frequently-asked-questions)). 22 | 23 | The talk will cover Mage-OS’s vision and goals, purpose, plans and progress. You won't want to miss it! 24 | 25 | Fun fact: Even the presentation title came up from Discord casual conversation with our community! 26 | 27 | ### Mage-OS Booth 28 | As a Silver Sponsor, we’ll have a nice booth at the conference. Come find us to chat Mage-OS, hang out, and get your Mage-OS button badge! 29 | 30 | Here is a list of Mage-OS board members and contributors who are confirmed at this stage. Some also have talks in their own fields of expertise (see the agenda). 31 | - Vinai Kopp 32 | - Ignacio Riesco 33 | - John Hughes 34 | - Maciej Kalkowski 35 | - Peter Jaap Blaakmeer 36 | - Willem Wigman 37 | 38 | As a nice thank-you gift, Interactiv4 has offered free tickets to individuals who are contributing to Mage-OS efforts, whether on the technical, content, or organizational side. If this is you and you're interested in attending, let us know! 39 | 40 | [Join our Mage-OS Discord](https://discord.gg/9xHBTTpa) to find and connect with other attendees! 41 | 42 | ![A photo of happy Magento people being happy about the happy organization Mage-OS is.](/blog/2022/2022-12-02-meetcommerce-mageos-2.jpg) 43 | 44 | ## Meet Commerce Spain: what else is different? 45 | This event is brand new and filling a gap. This conference is open to all eCommerce Platforms, not just Magento and Adobe Commerce, but also: 46 | 47 | - Shopware 48 | - Salesforce 49 | - BigCommerce 50 | - Shopify 51 | 52 | For merchants (who can attend for free), it’s a unique opportunity to get multiple perspectives on ecommerce. They will be able to compare Open Source and SaaS, different offerings and technologies, and see what platform works better for their life stages, size, organizational structure, industry verticals, and markets. 53 | 54 | Unlike massive multi-platform shows such as NRF, IRCE, eCommerce Berlin, or Paris Retail Week, this event will have a friendly feel with hundreds of participants, not thousands, and you will get quality time to catch up with old friends. We expect people from the Magento community to attend from all over Europe and the world, and we look forward to seeing you there. 55 | 56 | The weather should be nice and sunny, which might be a good change if you live in other parts of the Northern Hemisphere. 57 | 58 |
We can’t wait to see you. Try and arrive on Monday for the PreParty!
59 | 60 |
Get your tickets for Meet Commerce Spain here
61 | -------------------------------------------------------------------------------- /src/pages/blog/the-future-of-magento.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post-with-sign-form.astro' 3 | date: 2021-09-14 4 | title: The Future of Magento 5 | description: Open letter to the Magento Community 6 | groupId: 108619660 7 | --- 8 | ## Open letter to the Magento Community 9 | 10 | Dear Magento community, 11 | 12 | With this open announcement we are letting you know that there will be a community organization driven fork of Magento. The purpose is to secure Magento's long term viability for all the businesses depending on it. 13 | 14 | Why do we believe this is the right step? 15 | 16 | The Magento ecosystem is big. It’s been the dominant platform for eCommerce for a decade. It has driven innovation in eCommerce and empowered businesses of all sizes. Full of novel ideas born through a vibrant community, it is still unparalleled by any other eCommerce ecosystem out there. 17 | 18 | The eCommerce landscape has changed over the years, now offering a wealth of SaaS, PaaS, and other off-premise solutions. Magento under Adobe has determined to do the same. The community is still there, but the enterprise product - now called Adobe Commerce - is moving towards composable microservices hosted in the cloud, only suitable for the largest merchants. 19 | 20 | There has been talk about decomposition of the PHP Monolith by Adobe’s technical architects, meaning all parts of the PHP platform will be replaced by (Adobe) microservices. Ultimately, the entire Magento platform as we know it will be replaced. 21 | For reference, this was presented at [Adobe Summit 2021 in the talk “Extending Magento Commerce with Adobe I/O”](https://business.adobe.com/summit/2021/sessions/extending-magento-commerce-with-adobe-io-s604.html). 22 | 23 | This makes for a lot of unknown variables. There is no public roadmap for Magento Open Source, and this has left a lot of the community (who believe the monolith is a very valid approach in many cases) feeling uneasy about the future of Magento. 24 | 25 | So, we want to move forward. We believe we, the community, can maintain and evolve a fork in a way that will carry us into the future. 26 | 27 | We intend for this to be a collaborative effort, ideally together with the Magento Association, and (through them) with Adobe. We have already reached out to the Magento Association to work with them, but it will take time to build a common understanding of how to move forward. 28 | 29 | The fork will be upstream-compatible with Magento Open Source as long as it is supported by Adobe. That means, when the monolith is ultimately deprecated, all companies who want to remain on the monolith platform will be able to do so. 30 | 31 | We want to earn the trust of the Magento ecosystem. We truly believe we can not only keep Magento alive, we can give it a bright future by putting the focus on merchants, big AND small. 32 | 33 | This is only the beginning. Magento has a bright future ahead. We invite you to join us. 34 | 35 | 36 | *This initiative has been started by the companies and individuals signed below. If you want to publicly show your endorsement and be informed on future updates, please sign this open letter using the form below.* 37 | 38 | 39 | 40 | * *Willem Wigman, Hyvä Themes B.V.* 41 | * *Vinai Kopp, Hyvä Themes B.V.* 42 | * *Andreas von Studnitz, integer_net GmbH* 43 | * *Fabian Schmengler, integer_net GmbH* 44 | * *Ignacio Riesco, Interactiv4 S.L.* 45 | * *Óscar Recio, Interactiv4 S.L.* 46 | * *Peter Jaap Blaakmeer, elgentos* 47 | * *Wouter Steenmeijer, elgentos* 48 | * *Jeroen Boersma, elgentos* 49 | * *Kuba Zwolinski, snow.dog* 50 | * *Kamil Balwierz, snow.dog* 51 | * *Bartek Igielski, snow.dog* 52 | * *Simon Sprankel, CustomGento GmbH* 53 | * *Ryan Hoerr, ParadoxLabs, Inc* 54 | * *Thien-Lan Weber, OneStepCheckout* 55 | * *Alessandro Ronchi, Magento Community Maintainer* 56 | * *John Hughes, Fisheye Media Ltd.* 57 | * *Tomas Gerulaitis* 58 | 59 | *(Please note our [follow up post](https://www.mage-os.org/blog/introducing-mage-os) on 28. September 2021.)* -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-30.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-07-26 4 | title: New Website, Mirror Distribution, Nightly Builds, Content and Community Updates (Week 30) 5 | description: Version 2.3.7-p3 added to mirror; New nightly build versioning convention; Community updates. 6 | --- 7 | 8 | Lots is happening, folks! 9 | 10 | ## Milestones 11 | 12 | ### New website! 13 | 14 | You can find a lot of content beyond the blog now by visiting ! 15 | 16 | Many thanks to Ryan Hoerr who spent a lot of time massaging the previous blog into this shape. Content will continue to be updated. 17 | 18 | 19 | ## Technical topics 20 | 21 | ### Mage-OS Magento® Mirror Distribution 22 | 23 | Quite some work went into stabilizing older releases of the mirror distribution. All supported releases install cleanly and quickly now. 24 | 25 | Also, we added release 2.3.7-p3 to the list of supported releases because it is still being used in some CI pipelines to test modules against it. 26 | Now all relevant versions can be installed from the composer repository. 27 | 28 | Thank you to Daniel Sloof, Daniel Fahlke, and Damien Retzinger for helping to debug some of the issues! Your input was invaluable. 29 | 30 | Please join our [Discord](http://chat.mage-os.org), say hi in the #tech channel, and join the conversation! 31 | 32 | 33 | ### Mage-OS Magento® Mirror Nightly Builds 34 | 35 | So far we haven’t really made the nightly release repository public, and for good reason. Until now every package in a nightly release was given a new version built from the git branch prefix and the current date (YYYYMMDD) as a alpha package number, for example `2.4-a20220721`. 36 | 37 | This worked and resulted in an installable release, however, it breaks most composer version constraints of packages built for Magento. The primary use case for nightly builds is testing, and this is very cumbersome with this naming scheme. 38 | 39 | So we decided to change this, and instead use the last release version of a package, followed by a fourth part .1 version, followed by the date. For example, the last release for the `magento/framework` package is `103.0.4`. 40 | The nightly builds of this package will in future have the version `103.0.4.1-a20220721`. This satisfies commonly used composer version constraints like `^103.0.4`, and any package under test can simply be installed without any hassle. 41 | 42 | Thanks to Anton, Willem, Simon, Daniel F., and Daniel S. (and others whom we might have forgotten) for providing input on this topic. So far most of the implementation has been done by our own Vinai, but we're very open to helping hands. If you're interested in joining the effort, please don't hesitate to reach out! 43 | 44 | Once this change is implemented we will post details on how to install a build nightly release, and also how to build nightly releases yourself. 45 | 46 | 47 | ## Organizational topics 48 | 49 | ### Magento Open Source Content 50 | 51 | The content team continues to work on creating content for a Magento Open Source focused website. More content creators are very welcome! Every Monday at 4pm CET we meet to coordinate. Please join our [Discord](http://chat.mage-os.org) and visit the #content channel to participate. 52 | 53 | ### Community 54 | 55 | The [Mage-OS Discord](http://chat.mage-os.org) is becoming more lively, which is lovely. Please join and introduce yourself, it is great to see people are interested in an independent Magento Open Source. 56 | 57 | Also, we want to have online meetups or town hall hangouts, soon. These will be a great place to get to know each other, ask questions, and hear about what is happening. 58 | 59 | Finally, we are using Discord's audio and video channels to stream longer dev sessions about once a week. This usually is rather spontaneous, usually during the weekend. Keep an eye out for Vinai or others hanging out in the Watercooler chats, if you are interested to discuss technicalities, pair program, or just watch. 60 | 61 | 62 | That's all for today! 63 | Enjoy the week, and keep an eye on this blog - more news coming soon, 64 | 65 | The Mage-OS folks 66 | -------------------------------------------------------------------------------- /src/pages/distribution/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Mage-OS Distribution 4 | description: Mage-OS Distribution 5 | --- 6 | 7 | ## About the Mage-OS Distribution 8 | 9 | Mage-OS is an upstream compatible, lightweight composition of Magento Open Source packages. Some packages will contain changes, and some will be entirely new. We aim to keep the Mage-OS Distribution compatible with all existing Magento 2 extensions and integrations to the greatest extent possible. 10 | 11 | What differentiates Mage-OS from Magento Open Source and Adobe Commerce? 12 | 13 | * Independent and community-driven 14 | * More accessible to new users, developers, and contribution 15 | * Lightweight package selection by default 16 | * Simple migration to and from Magento Open Source 17 | 18 | [Read our product vision for the Mage-OS Distribution](/distribution/product-vision) 19 | 20 | ## Installation 21 | 22 | 23 | 24 | We have not yet published a Mage-OS distribution release, but we hope to soon. 25 | 26 | 34 | 35 | ---- 36 | 37 | ## Magento™ Nightly Builds 38 | 39 | For the first time ever, you can install a nightly build of Magento's latest published development source code, without having to wait for an official beta release. Mage-OS's `upstream-nightly` composer repository is updated each day with the latest code from the Magento github. 40 | 41 | - EU: [upstream-nightly.mage-os.org](https://upstream-nightly.mage-os.org) *(Mage-OS)* 42 | 43 | We hope this will be useful for vendors and extension providers to track compatibility of their products with upcoming releases. 44 | 45 | Keep in mind that the nightly release might be broken sometimes, depending on the state of the code in the upstream Magento git repositories. 46 | 47 | To install our latest nightly build of Magento Open Source in your working directory: 48 | 49 | ```bash 50 | composer create-project --stability alpha --repository-url=https://upstream-nightly.mage-os.org magento/project-community-edition . 51 | ``` 52 | 53 | ---- 54 | 55 | ## Magento™ Mirrors 56 | 57 | You can obtain Magento packages through these Mage-OS-built Magento mirror repositories for composer: 58 | 59 | - EU: [mirror.mage-os.org](https://mirror.mage-os.org) *(Mage-OS)* 60 | - EU: [mage-os.hypernode.com/mirror/](https://mage-os.hypernode.com/mirror/) *(Hypernode)* 61 | - EU: [mage-os.maxcluster.net/mirror/](https://mage-os.maxcluster.net/mirror/) *(maxcluster)* 62 | 63 | 64 | These can be used to install Magento Open Source 2.3.7 and 2.4.x without authentication. To install `magento/project-community-edition` 2.4.5 in your working directory: 65 | 66 | ```bash 67 | composer create-project --repository-url=https://mirror.mage-os.org/ magento/project-community-edition:2.4.5 . 68 | ``` 69 | 70 | ### Magento Mirror Repository Generation 71 | 72 | You can create your own Magento mirror with self-built packages, using the mirror repository generator found at [github.com/mage-os/generate-mirror-repo-js](https://github.com/mage-os/generate-mirror-repo-js). 73 | 74 | Generating from scratch takes about 1.5 hours on a low-end server (2G RAM, no swap). We are actively improving the tool to make it faster and more usable, however, we expect alternative implementations to be the primary tooling in the future for performance reasons. The current JavaScript-based implementation was started as a research project into minimizing dependencies. 75 | 76 | If you publish a mirror, please let us know to add it to the list above! 77 | 78 | ---- 79 | 80 | ## Roadmap 81 | 82 | Mage-OS is community maintained and community developed, so to some extent the direction depends on what people contribute. 83 | 84 | Our first priority is to get an independent distribution live, then iterate on that to improve simplicity and performance in a backwards-compatible way. 85 | 86 | Stay tuned, or [start contributing](/get-involved) to help set the roadmap! 87 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-9.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-03-04 4 | title: Week 8 and 9 of 2022 5 | description: An update on last week's progress on Mage-OS 6 | --- 7 | 8 | Because of the shock of Russia invading Ukraine there was no progress during week 8. 9 | Many friends, co-workers and employees and their families in the Ukraine are affected. 10 | It seems nothing we are doing matters compared to our dear ones fighting for their life and country. 11 | 12 | However, we have to continue to function, despite the crisis. 13 | Like a good friend said: "it’s business as usual, but we also have to do more, we have to help". 14 | 15 | ## Technical topics 16 | 17 | ### Mirror distribution 18 | 19 | The purpose of the mirror distribution is to provide an independent installation source for Magento Open Source, and to facilitate learning about building a Magento composer repository. 20 | The mirror repository can be used to install Magento Open Source independently of the Adobe owned repositories. 21 | Each new Magento Open Source release will be added when it becomes available. 22 | 23 | We are able to create a Magento Open Source composer package repository from our forked repositories at [github.com/mage-os](https://github.com/mage-os). 24 | All the forked repositories used to build the composer repository start with the name [mirror-*](https://github.com/mage-os?q=mirror-&type=all) (for example `mirror-magento2`). 25 | It is generated by a [docker image](https://hub.docker.com/r/magece/mirror-repo-js/tags), so everybody can create and host their own mirror repository if they want. 26 | We hope over time, hosters will use this to provide local mirrors to their customers. 27 | 28 | There are still two issues to solve, but in general an installation of 2.4.3-p1 is now possible if the `magento/composer-dependency-version-audit-plugin` is disabled (answer no when asked during the installation). 29 | These remaining issues should be fixed soon, too. 30 | 31 | The composer repository for our Mage-OS mirror distribution can be found at [mirror.mage-os.org](https://mirror.mage-os.org). 32 | At a later time we will be providing additional packages that go beyond Magento Open Source at [repo.mage-os.org](https://repo.mage-os.org). 33 | 34 | 35 | *Please note: currently they still are to be considered experimental. We will post an update here when they can be considered stable.* 36 | 37 | More details on how the composer repository is generated and how to install Magento Open Source from such a mirror repo can be found at [github.com/mage-os/generate-mirror-repo-js](https://github.com/mage-os/generate-mirror-repo-js). 38 | 39 | A big thank you to [Raffael Kassner](https://twitter.com/kassner)! The research he provided at [github.com/magefm/repository-generator](https://github.com/magefm/repository-generator) has been very helpful! 40 | 41 | 42 | ### GitHub permissions 43 | 44 | We have set up a plan and are in the process of learning how to use terraform to apply the desired set of permissions to all repositories at [github.com/mage-os](https://github.com/mage-os). 45 | 46 | ### Discord 47 | 48 | New members are now required to register with a verified email address and agree to the code of conduct hosted at [mage-os.org/code-of-conduct](https://mage-os.org/code-of-conduct). 49 | 50 | We now welcome anybody interested in our discord at [discord.gg/nvZDVA2NdC](https://discord.gg/nvZDVA2NdC). 51 | This is probably the best place to go if you are interested in helping to set up Mage-OS. 52 | 53 | 54 | ## Organizational topics 55 | 56 | ### Operations management 57 | 58 | We agreed we need to invest into the organization behind Mage-OS in order to be able to make this a sustainable long term project. 59 | For this, we developed the profile for a full time chief operating officer. 60 | 61 | 62 | ### Organizing documents 63 | 64 | The amount of both technical and organizational documents are growing, and we need to organize things. 65 | We decided to share Google Drive folders with everyone in the organization. Some of those folders will become public, so documents like for example the [product vision](https://docs.google.com/document/d/1dF60bw54ivdcH7IpEeWPCPXAW3Cx0ky_mKzv3v93uRc/edit?usp=sharing) can be easily linked to and discovered. -------------------------------------------------------------------------------- /src/pages/blog/20230228-february-update.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2023-02-28 4 | title: Dependency Graphs, Website, and more 5 | description: An update on Mage-OS NX dependency graphs and the upcoming website 6 | --- 7 | 8 | ## Product Update 9 | 10 | See [Adam Crossland](https://www.linkedin.com/in/ACoAABVdXVwBWm0JxapAOsPq629nbfblC5TKxhM)'s NX demo for a sneak peek of where Mage-OS tech is headed. 11 | 12 | Adam Crossland and Damien Retzinger have been working on using a tool called NX to build a dependency graph of all code in Mage-OS. This graph lets us use code or commands to trace the files and modules that each bit of code depends on. 13 | 14 | Using this, we can identify the exact modules that are affected by each contribution to Mage-OS. That means we can run only the code tests that are relevant to a pull request, which will make for a much faster contribution and testing cycle! The full testing suite takes many hours to complete, so being able to run only part of them will be a huge improvement for everyone. 15 | 16 | In the short term, we are creating GitHub Actions that use the graph to run fast unit and integration tests of all changes. 17 | 18 | Long-term, we intend to use this work to simplify the dependency graph by decreasing the dependencies between different modules in Mage-OS. That will have all sorts of benefits, especially for being able to only install the modules you need for a specific site. 19 | 20 | This is a big step toward enhancing Mage-OS for composable commerce. 21 | 22 | [Watch the Mage-OS NX graph demo](https://www.youtube.com/watch?v=seMz0iCs5Jo) 23 | [![A preview of the YouTube video demo showing NX usage with Mage-OS](/blog/2023/2023-02-28-nx-graph-demo.png)](https://www.youtube.com/watch?v=seMz0iCs5Jo) 24 | 25 | ## New Website 26 | 27 | We're making significant progress on the new website for [Mage-OS](https://www.linkedin.com/company/mage-os/) which includes essential information about Magento Open Source. This content has been sorely missing for many years, especially since [magento.com](http://magento.com/) was discontinued. 28 | 29 | This wouldn't have been possible without the help of so many great people in our community 🙌 30 | 31 | Thanks to the many who have contributed over the past few months to help get to a point where we are nearly ready to launch! 32 | 33 | * [Arron Moss](https://www.linkedin.com/in/ACoAAATSFqoBN1V9bIVbizRHk-_tOmWx8V_GNCs) 34 | * [Indraneil Khedekar](https://www.linkedin.com/in/ACoAACqTMmMBKWyikCW-la83TB30tCCxFUOmI2c) 35 | * [John Hughes](https://www.linkedin.com/in/johnhughes1984/) 36 | * [John Prendergast](https://www.linkedin.com/in/ACoAAAIKKTQBRsxSIqAIFG5ANnsMCO2U64tXIkM) 37 | * [Nicole Mentzen](https://www.linkedin.com/in/ACoAAARV5a0BDpADrwyrN7JhQA511uOzyW9Sqtk) 38 | * [Reuben Southall](https://www.linkedin.com/in/reuben-southall-1b95b5162/) 39 | * [Roland Haselager](https://www.linkedin.com/in/ACoAAANEB1YBd8wn7x88ltRzvcHTz2fnB0QurAY) 40 | * [Ryan Hoerr](https://www.linkedin.com/in/ACoAAAMP6kYBs22BgReRp1jseVbSNvFH79x592Y) 41 | * [Sergej Derzap](https://www.linkedin.com/in/ACoAAAOF4GABdf-dRxjOwjttBs7Wn0O0Y0osnKM) 42 | * [Thien-Lan Weber](https://www.linkedin.com/in/ACoAAAAHT_8Bn4rNTZL-Ff82Yi-RhBzlTOo2nDI) 43 | 44 | We plan to launch the new site before the end of March. 45 | 46 | ![A preview of the new Mage-OS website](/blog/2023/2023-02-28-new-website-preview.png) 47 | 48 | If you want to help out before it launches, head over and say hello on the content channel on our Discord server. 👋 49 | 50 | [http://chat.mage-os.org/](http://chat.mage-os.org/) 51 | 52 | We'd highly value additional case studies, community stories, and pictures, so that the website represents us all! 53 | 54 | 55 | ## Association Status 56 | 57 | As a follow-up from last month: our lawyers made the appeal, gathered signatures from all founding members in Poland, and resubmitted our case to the court. We hope to have great news to share next month. 58 | 59 | Again thank you everyone for your support in the various work streams and on social media. We've exceeded 1,000 followers on [LinkedIn](https://www.linkedin.com/company/81885701), and 700 members on the [Mage-OS Discord](http://chat.mage-os.org). Join us if you haven't already! 60 | 61 | 62 | That's all for now. Thanks for reading! 🙌🏻 63 | 64 | The Mage-OS folks 65 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-14.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-04-09 4 | title: Week 12 - 14 of 2022 5 | description: An update on the last three weeks of progress on Mage-OS 6 | --- 7 | 8 | Seeing the horror of the slaughter of Bucha in Ukraine took its toll on productivity. 9 | Keeping up the motivation despite everything going on was tough for some of us. 10 | At the same time, it feels very uplifting to be able to provide support to our friends and family in Ukraine. It also is wonderful to see others selflessly provide shelter, money, material and time to help those who managed to flee, and to those who stayed to fight. 11 | 12 | Here are the updates relating to Mage-OS we made over the last couple of weeks. 13 | 14 | ## Technical topics 15 | 16 | ### Mage-OS Magento® Mirror Repository 17 | 18 | Hypernode created the first Mage-OS mirror using the mirror-repo-generator image and [wrote about it](https://www.hypernode.com/blog/weve-created-the-worlds-first-mage-os-mirror/)! To our surprise they are already using their mirror to provision client instances, which means Mage-OS is already being used in the wild! 19 | 20 | Other hosting companies have also started to experiment with the mirror repo generator and plan on publishing their findings soon. 21 | Also, we have received some first PRs, which is wonderful. 22 | 23 | As soon as 2.4.4 will be released next Tuesday it should be possible to make it available in mirrors, too, by running the mirror generator again. 24 | 25 | If you have questions or ideas, please join our [discord](https://discord.gg/nvZDVA2NdC) and say hi in the #tech channel. 26 | 27 | ### Mage-OS Distributions 28 | 29 | Creating a mirror repository is not our main objective. That’s only the first step towards creating our own distribution. Now that the mirror repository is fully functional, we move our focus to the first steps in creating our first custom distribution. 30 | 31 | The first step for this is to figure out the automatic generation of the base package dependencies. First experiments have been done to get that information using static code analysis without the need for a full Magento installation. 32 | 33 | Figuring out this puzzle will allow the creation of nightly builds based on the current develop branch, which in turn will give us an opportunity to set up continuous integration. 34 | 35 | 36 | ### GitHub permissions 37 | 38 | We have now collected all the knowledge to implement Terraform to manage GitHub permissions for the Mage-OS organization repositories. We expect to complete this step soon. 39 | 40 | 41 | ## Organizational topics 42 | 43 | ### The Mage-OS Association 44 | 45 | The founding of the Mage-OS association is moving along swiftly. 46 | The initial board has been decided on and the last details of the bylaws are being cleared by lawyers. As soon as the association is founded, we will publish all details. 47 | 48 | Here is a sneak peek into part of the bylaws: 49 | 50 | > **Art. 3 - Purpose** 51 | > 52 | > The purpose of the Mage-OS Association is to enable the long-term success of the Magento ecosystem by empowering the community to maintain and develop the Mage-OS platform (based on Magento Open Source) through communication, coordination, and funding. 53 | > 54 | > In particular, the Mage-OS Association has the following goals: 55 | > * Increase the number of people involved 56 | > * Nurture good vibes and values 57 | > * Increase the market share 58 | > * Increase confidence in the Magento ecosystem 59 | > * Sustain Magento Open Source position as a leading platform for custom e-commerce development 60 | 61 | > **Art. 4 - Tasks** 62 | > * In particular, the Mage-OS Association has the following tasks: 63 | > * Coordinating and funding the Mage-OS development and long-term support 64 | > * Creating quality content that supports the long-term livelihood of the platform 65 | > * Providing documentation and education/certification paths 66 | > * Supporting organizations empowering the Magento Open Source ecosystem (both regional, like OpenGento and global, like the Magento Association) 67 | > * Provide insights, research, and materials to support those outcomes 68 | 69 | We look forward to seeing you soon, hopefully even at an in-person event! 70 | 71 | That's all for today! Stay safe and prosper, 72 | 73 | The Mage-OS folks -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-6.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-02-11 4 | title: Week 5 and 6 of 2022 5 | description: An update on last month's progress on Mage-OS 6 | --- 7 | 8 | Every Tuesday we have a meeting to discuss technical topics, and every Wednesday we have a meeting regarding organizational topics. 9 | 10 | This is the first post of the new bi-weekly status updates we will be publishing to be more transparent regarding the work we are doing. 11 | Please expect these updates will be less polished but more frequent than our prior posts. 12 | 13 | 14 | ## Technical topics 15 | 16 | ### Package generation 17 | 18 | We are continuing to work on the package splitting functionality. A reference implementation regarding the general package generation is complete. We are building multiple implementations using different languages in order to increase the bus-factor. Noteworthy is that all mage-os composer packages will have stable checksums. 19 | We are close to being able to create a mirror distribution, but are still missing: 20 | 21 | 1. The composer.json file for the magento/magento2-base package. The question of how to get a base package composer.json is solved, but not yet implemented. More information on why that isn’t straight forward and what is required can be found in a [google doc](https://docs.google.com/document/d/1VFFL7JbsUV0MUVZE_1ojCPRI9F4ZZtema1_cOgreNDo/edit?usp=sharing). 22 | A public repository with all relevant composer.json files can be found at 23 | [github.com/mage-os/magento2-base-composer-json](https://github.com/mage-os/magento2-base-composer-json) 24 | 25 | 2. The meta-package and project-package generation. 26 | 27 | 28 | We expect the meta- and project-package composer.json generation to be simpler than the base-package composer.json and intend to complete these tasks until the next meeting, at least with the JavaScript package splitter implementation. 29 | 30 | ### Preparing the GitHub organization for being open to the public 31 | 32 | We discussed how to handle write privileges to the repositories and who will implement the necessary configuration. 33 | 34 | ## Organizational topics 35 | 36 | ### Magento Open Source Marketing Content Creation 37 | 38 | * Since Adobe has effectively removed next to all content on the brand Magento and shut down the magento.com domain, we feel it is super urgent to provide an alternative portal where merchants can inform themselves about Magento Open Source. 39 | * Until that exists, a lot of companies who have built their business around Magento Open Source are suffering from Adobe's decision to redirect magento.com to their Adobe commerce landing page. 40 | * We decided to reach out to individuals in the community asking for help in creating content. Feature descriptions, key value propositions and case studies are the most important. 41 | * Once we have a reasonable amount of content compiled, we will set up a website. 42 | * We want to do this independently of the Magento Association and Adobe since they probably will take a lot more time to get it done. And we think time is of essence. 43 | * If a better website is set up later under a better domain, we will be happy to share or hand over any Magento Open Source marketing content that is relevant to merchants. We are very willing to collaborate, but do not want to wait idle. 44 | 45 | ### Magento Open Source STS 46 | 47 | The biggest topic was news shared by Adobe at the Open Source Task Force meeting that they intend to create a Magento Open Source Short Term Support (STS) distribution, which would run in parallel with a LTS version. 48 | 49 | This is amazing good news if it is realized. Adobe offered to share their build processes and tools as part of this. 50 | 51 | We welcome this wholeheartedly, but at the same time feel it is very important to continue on our path to create independent distributions, since we all have experienced the time it takes for things in big companies to happen. 52 | We want to move faster. 53 | 54 | Once the STS release exists, all the work we will have done can benefit it. 55 | 56 | Right now, the STS version of Magento is a proposal, and many things are still unclear or not yet decided on. It is a very positive outlook, but we’re cautious to celebrate too early. 57 | 58 | 59 | 60 | Thank you, 61 | 62 | *The whole Mage-OS team* -------------------------------------------------------------------------------- /src/pages/organization/about.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: About the Mage-OS Association 4 | description: About the Mage-OS Association 5 | --- 6 | 7 | The Mage-OS Association is a non-profit association formed by people within the Magento community to represent and further the interests of that community as a whole: Merchants, developers, agencies, and all of the many people supporting and supported by this ecosystem. 8 | 9 | The ideas behind Mage-OS were first shared in an [open letter about the future of Magento](/blog/the-future-of-magento). That letter prompted discussions and action across the community. The letter was signed by 1,641 people that use, develop, or otherwise depend on Magento for a living. Mage-OS brings the ideas of that letter to life. 10 | 11 | Mage-OS is incorporated in Poland, but is represented worldwide. 12 | 13 | ## Our Mission and Values 14 | 15 | **We want to see Magento prosper.** 16 | 17 | We have the following goals: 18 | - Grow the community 19 | - Nurture good vibes and values 20 | - Increase ecosystem market share 21 | - Increase confidence in the Magento ecosystem 22 | - Sustain Magento as a leading platform for custom ecommerce development 23 | 24 | We intend to accomplish those goals by: 25 | - Coordinating and funding the development and long-term support of Mage-OS 26 | - Creating quality content that supports the long-term livelihood of the platform 27 | - Funding and supporting events that align with the association goals 28 | - Providing documentation and education/certification paths 29 | - Supporting organizations empowering the Magento Open Source ecosystem 30 | - Providing leads and job opportunities for members 31 | - Provide insights, research, and materials to support those outcomes 32 | 33 | ## Vision 34 | 35 | Our intention is to foster the growth and long-term success of the community by taking steps to simplify and modernize the platform, encourage developer uptake, reinvigorate the supporting community, and give merchants the support and confidence they need to choose Mage-OS for their ecommerce needs. 36 | 37 | Our vision for the Mage-OS project starts with these key steps: 38 | 39 | 1. *[Build community interest](/blog/the-future-of-magento)* 40 | 2. *[Launch an independent public mirror of Magento Open Source](/blog/mage-os-update-2022-week-11)* 41 | 3. *[Form the supporting organization](/blog/mage-os-update-2022-week-36-mage-os-assoc-announcement)* 42 | 4. **Launch the Mage-OS distribution, for enhancements to the Magento Open Source platform** 👈 We are here 43 | 5. Hire a CEO or COO to further development of the Mage-OS association and distribution *(subject to availability of funds)* 44 | 6. Launch a grant program to sponsor development of specific improvements to the Mage-OS distribution *(subject to availability of funds)* 45 | 7. Create a business entity to provide merchant support services and bug fixes for the Mage-OS and Magento Open Source platforms 46 | 47 | ---- 48 | 49 | ## Who we are 50 | 51 | ### Board of Directors 52 | 53 | - Vinai Kopp (DE) - *President* 54 | - Thien-Lan Weber (FR) - *Vice President* 55 | - Alessandro Ronchi (IT) - *Treasurer* 56 | - Ryan Hoerr (US) - *Actuary* 57 | - Ignacio Riesco (ES) 58 | - John Hughes (UK) 59 | - Maciej Kalkowski (PL) 60 | - Peter Jaap Blaakmeer (NL) 61 | 62 | ### Committees 63 | 64 | #### Business Control Committee 65 | *Ensures accountability and transparency in Association operations.* 66 | - Laura Folco (US) 67 | - Simon Sprankel (DE) 68 | 69 | #### Magento Content Committee 70 | *Develops content to further the Magento Open Source platform and ecosystem.* 71 | - John Hughes (UK) - *Lead* 72 | - Arron Moss (UK) 73 | - Brent Peterson (US) 74 | - Damien Retzinger (US) 75 | - Maier Bianchi (US) 76 | - Thien-Lan Weber (FR) 77 | - Willem Wigman (NL) 78 | 79 | ---- 80 | 81 | ## Statutes 82 | 83 | As a non-profit organization, Mage-OS was founded with formal statutes that define how the association is structured and operates. 84 | 85 | [View the Mage-OS Association statutes](/organization/statutes) 86 | 87 | ---- 88 | 89 | ## Sponsors 90 | 91 | We are proud and grateful to be supported by: 92 | 93 | [![Tutanota, an Email Service Provider sponsoring Mage-OS](/supporters/tutanota.png)](https://tutanota.com/) 94 | 95 | Tutanota provides secure e-mail hosting to us free of charge. 96 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-33.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-08-15 4 | title: Mirror 2.4.5 release and many contributions 5 | description: The 2.4.5 and related releases have been added to the mirror repositories and a lot of progress has been made, thanks to many contributions. 6 | --- 7 | 8 | Work has been progressing nicely, and we celebrate that more people are getting involved! Here is an overview of what has been happening since the last blog post. 9 | 10 | ## Technical topics 11 | 12 | ### Mage-OS Magento® Mirror Distribution 13 | 14 | Adobe released Magento Open Source 2.3.7-p4, 2.4.3-p3, 2.4.4-p1 and 2.4.5 on the 9th of August! 15 | We are pleased to announce that these versions can now also be installed as independently built packages, using the [Mage-OS mirror](https://mirror.mage-os.org). 16 | 17 | While preparing the releases, we discovered (very few) inconsistencies in upstream composer.json files that broke our build process. 18 | We reported these inconsistencies upstream to Adobe (for example in the [security package](https://github.com/magento/security-package/issues/321) and [adobe-stock-integration](https://github.com/magento/adobe-stock-integration/pull/1872) repositories), and they are being addressed. At the same time, we have improved the [build tool](https://github.com/mage-os/generate-mirror-repo-js) to account for these issues allowing Mage-OS to become more independent. 19 | 20 | Finally, Damien Retzinger from [Graycore](https://www.graycore.io/) contributed GitHub actions to automate testing builds in parallel. This allowed us to move much, much faster, and we are very grateful for his participation! 21 | 22 | Daniel Sloof created GitHub actions to check the integrity of the Mage-OS packages against the upstream releases. This QA tooling is invaluable. 23 | 24 | Many thanks to [Damien](https://github.com/damienwebdev) and [Daniel](https://github.com/danslo), and to all others like [Anton](https://github.com/speedupmate), [Daniel Fahlke](https://github.com/flyingmana) and many others who participated in discussions and helped with good ideas in the #tech channel or joined a stream on Discord. 25 | 26 | 27 | ### Mage-OS Magento® Mirror Nightly Builds 28 | 29 | The new versioning scheme for the nightly build packages, as discussed in the [previous post](https://mage-os.org/blog/mage-os-update-2022-week-30), has been implemented, and is currently being evaluated, if it indeed serves the desired purpose. 30 | We expect the nightly builds to be available soon. 31 | 32 | 33 | ### Contributing 34 | 35 | People have been asking how to contribute. It is very encouraging to see that many people want to help, and so far we still don't have a good answer. 36 | 37 | Since we are currently "meta-building", instead of building Magento features and improvements, we are in a bit of a special situation. We expect this to change once the infrastructure for the mirror, nightly builds, and the Mage-OS distribution is closer to complete. 38 | 39 | The usual approach to encouraging contributions to open source projects is to do "Issue grooming" and then to choose tickets that are good first issues. This approach is not applicable (yet) to the Mage-OS project. 40 | 41 | At the moment, most people have started by joining [Discord](http://chat.mage-os.org), following the #tech channel, and joining streams in the #Watercooler channels, where problems are being discussed and solved together. 42 | 43 | It has been very valuable to interact in this way. 44 | 45 | Currently, this is the best way to get started, as it helps develop an understanding of what is required at a given moment in time, be it debugging, writing code, pairing or coming up with ideas. 46 | 47 | So if you are interested in helping, join a stream in Discord and get an idea what is happening. It is fun, too, if you like problem-solving and coding :) 48 | 49 | For those who simply wish to keep up, start by following the discord #tech channel. 50 | 51 | We are welcoming and inclusive at [chat.mage-os.org](http://chat.mage-os.org)! 52 | 53 | 54 | ## Organizational topics 55 | 56 | ### Mage-OS Association 57 | 58 | Vacation season is keeping us busy, but we are moving to complete the founding of the association. 59 | 60 | We will form a committee to set the price for members and supporting members (companies). 61 | If you would like to be involved, please join the [Mage-OS Discord](http://chat.mage-os.org) #membership channel and let us know! 62 | 63 | 64 | For now that’s all, more updates are coming soon. 65 | 66 | The Mage-OS folks -------------------------------------------------------------------------------- /src/components/SignForm.vue: -------------------------------------------------------------------------------- 1 | 105 | 106 | 161 | 162 | 173 | -------------------------------------------------------------------------------- /src/pages/index.astro: -------------------------------------------------------------------------------- 1 | --- 2 | import Layout from '@/layouts/default.astro' 3 | import PostPreviewList from '@/components/PostPreviewList.astro' 4 | import Button from '@/components/Button.astro' 5 | 6 | const content = { 7 | title: 'Mage-OS | Community-Driven Commerce', 8 | description: 'Mage-OS is an open initiative to sustain and enrich the Magento platform and ecosystem.', 9 | socialTitle: 'Community-Driven Commerce', 10 | socialDescription: 'Mage-OS is an open initiative to sustain and enrich the Magento platform and ecosystem.' 11 | } 12 | 13 | const rawPosts = await Astro.glob('./blog/*.md') 14 | const posts = rawPosts 15 | .map(({ url, frontmatter }) => ({ url, ...frontmatter })) 16 | .sort((a, b) => new Date(b.date) - new Date(a.date)) 17 | .slice(0, 5) 18 | --- 19 | 20 | 21 |
22 | Visiting us for the first time? Read what we're all about, stay informed, or start using a Mage-OS repository! 23 |
24 | 25 |
26 |

Mage-OS is an open initiative to ensure the accessibility, longevity, and success of the Magento® platform and ecosystem.

27 |

The Mage-OS Distribution is a backwards compatible, lightweight version of Magento Open Source packages. This includes changes and new features compared to Magento, as contributed by volunteers like you. We aim to stay compatible with all existing Magento 2 extensions and integrations as much as possible.

28 |

It takes a village! Join us, and help create the future of open source ecommerce.

29 |
30 | 31 |
32 | 33 | 34 |
35 |
36 |

Developers

37 | 42 |
43 | 44 |
45 |

Merchants

46 | 51 |
52 | 53 |
54 |

Agencies

55 | 59 |
60 |
61 | 62 |
63 | 64 |

Updates

65 | 66 | 67 | 73 | 74 | -------------------------------------------------------------------------------- /src/pages/distribution/product-vision.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Product Vision 4 | description: Our vision for the Mage-OS branded distributions 5 | --- 6 | 7 | This document describes the current short to mid-term desired state of the Mage-OS distributions. This is what we are working toward. 8 | 9 | Details are subject to change, but the gist should remain the same. 10 | 11 | Mage-OS is a collection of Magento distributions. Each distribution can be thought of as a different flavor of Magento, optimized for a specific set of requirements. 12 | 13 | ## The Magento mirror repository 14 | 15 | The mirror repository is a clean, unchanged copy of Magento Open Source. Whenever Magento publishes a release, we will rebuild the same release from sources for the mirror repository. 16 | 17 | The difference between the mirror repository and Magento Open Source are: 18 | 19 | * It is built based on git repositories mirroring the upstream Magento repositories. 20 | * The build scripts that create the individual composer packages and the meta-package are custom and open source. 21 | * It is distributed using an independent composer repository that can be accessed without authentication. 22 | 23 | Mirror repository packages are interchangeable with Magento Open Source packages. The only difference is the composer repository from which the packages are obtained. 24 | 25 | The purpose of the mirror repository is to ensure the independence of the upstream infrastructure. In the event that the Magento Open Source repository becomes unavailable or shut down, all the infrastructure is in place to ensure continued access and distribution. Learning to build and maintain the infrastructure is explicitly one of the goals of the mirror repository. 26 | 27 | This has been completed. [Mirror repository details](/distribution#magento-mirrors) 28 | 29 | ## The Mage-OS core distribution 30 | 31 | The Mage-OS core distribution will be an upstream compatible metapackage based on Magento Open Source. Think of it as an independent version of Magento--based on Magento source code, but including additional changes specific to Mage-OS. 32 | 33 | The core distribution will be built from a fork of the mirror git repositories. 34 | 35 | The difference between the Mage-OS core distribution and the Magento mirror repository is that the Mage-OS core distribution includes changes to the upstream. 36 | 37 | Every change will be carefully evaluated in terms of upstream compatibility. 38 | 39 | The purpose of the Mage-OS core distribution is to provide 40 | 41 | * Improved decoupling of packages 42 | * Improved developer experience while working with the product 43 | * Improved developer experience while contributing to the product 44 | * Full compatibility with Magento extensions 45 | * Focus on additional security 46 | * Reduced infrastructure stack dependencies 47 | * Low-level code improvements, for example in the areas of code generation and caching 48 | * Removal of most bundled extensions contained in upstream (they can still be independently installed if desired) 49 | * A simple documented migration path to Magento Open Source or Adobe Commerce 50 | 51 | Mage-OS core distribution releases are made independently of upstream releases. This enables it to move faster when desired, for example when enabling compatibility with new PHP versions. 52 | 53 | New upstream releases will trigger a new Mage-OS core release, once all changes have been rebased onto the new upstream release. Because the Magento mirror is constantly synchronized, this will be an ongoing process, not a big rebase when an upstream release happens. 54 | 55 | New functional features will be introduced only through independently installable modules, in other words, no new functional features will be introduced in the Mage-OS packages that are based on the upstream. This follows the same decoupling approach that Adobe Commerce is using, allowing for a more stable core and an independent feature module release schedule. 56 | 57 | The goal of the reduced infrastructure stack dependencies is to enable new developers to be onboarded more easily. The desired target is to be able to use a plain XAMPP stack on any machine, including Windows, to run and develop with Mage-OS. This requires making Elasticsearch optional, as well as ensuring services like Redis, RabbitMQ, Node.js and such remain optional. 58 | 59 | Mage-OS will maintain backward compatibility and the ability to migrate upstream at multiple levels: 60 | 61 | * Compatibility with third-party extensions 62 | * Database level compatibility (data and schema) 63 | * API stability 64 | 65 | ## The Mage-OS flavored distributions 66 | 67 | The Mage-OS flavored distributions will be composer metapackages that bundle packages of the Mage-OS core for specific purposes. For example: 68 | 69 | * The Mage-OS headless distribution might contain no storefront theme 70 | * The Mage-OS minimal distribution might contain only a minimal set of packages to enable building lightweight applications 71 | * The Mage-OS headfull distribution might contain no GraphQL packages 72 | 73 | Each will have pros and cons, to be considered by the developer choosing to use one. That being said, it will be relatively simple to switch from one 'flavor' to another, or to the full core distribution. 74 | -------------------------------------------------------------------------------- /src/pages/introducing-mage-os.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Introducing Mage-OS 4 | description: Introducing Mage-OS 5 | --- 6 | Since we posted the [initial open letter](/blog/the-future-of-magento) on September 14th a lot has happened. 7 | 8 | **Thank you** 9 | 10 | First, we would like to thank all the people who added their names to support the initiative and who have reached out personally to encourage. 11 | 12 | Thank you also to everyone who spent time with us at Meet Magento Poland. We came with the intention to listen, you came with the open-mindedness to share your point of view and many productive discussions came out of it! 13 | 14 | Because technically already thousands of forks exist for the Magento 2 project on GitHub, we decided to name our thing a "distribution". 15 | 16 | 17 | **Introducing the Mage-OS distribution** 18 | 19 | Mage-OS will be an upstream compatible, lightweight, composition of Magento Open Source packages. Some of those packages will contain changes, and some will be entirely new. 20 | It will be compatible with all existing Magento 2 extensions and integrations. 21 | 22 | What differentiates Mage-OS from Magento Open Source and Adobe Commerce? 23 | 24 | * It will be more accessible to developers 25 | * It will be composed of a default lightweight package selection 26 | * It will allow faster integration of PRs 27 | * It will allow simple migration to Magento Open Source and Adobe Commerce 28 | 29 | 30 | **Our Value Proposition** 31 | 32 | > If the cake gets bigger, the whole ecosystem wins. 33 | 34 | We see the following value propositions for the five key pillars of our Magento ecosystem: 35 | 36 | *Mage-OS for Merchants* 37 | * Faster time to market: our technology is simpler and more accessible to a majority of developers. 38 | * Provides a growth path from the small beginning up to Adobe Commerce and Experience Manager 39 | * Reduced hosting costs due to simpler environmental requirements 40 | * Access to the big pool of Integrations and Extensions for Magento and Adobe Commerce 41 | 42 | *Mage-OS for Agencies / Service Integrators* 43 | * Reduced build time and less complexity to optimize your project costs 44 | * Easier to onboard new talent thanks to a more accessible codebase 45 | * Ability to target the lower SMB market with attractive margins thanks to lower project cost 46 | * Developers happiness: less frustration, more wins to motivate your teams and boost your talent retention 47 | 48 | *Mage-OS for Technology Partners (Extension Vendors, Hosting, SaaS providers)* 49 | * Business growth as the Magento market share increases 50 | * Access to the lower end SMB market section of merchants and agencies 51 | * Bigger return on investment for existing products due to a longer Magento lifespan 52 | 53 | *Mage-OS for Developers* 54 | * Improved sense of ownership 55 | * Faster moving distribution 56 | * Easier to contribute 57 | * Simpler to set up a development environment 58 | * Good entry point for a developer career in the Magento / Adobe Commerce ecosystem 59 | * Bigger return on investment for acquired Magento development knowledge due to a longer Magento lifespan 60 | 61 | *Mage-OS for Adobe* 62 | * Reduced pressure on the Magento Open Source GitHub PR/Issue list. 63 | * Breeding ground for innovations: create a protective buffer between community contributions and Adobe Commerce to safeguard stability. 64 | Community contributions can be evaluated in production environments without the risk of introducing instability to Magento Open Source or, by extension, Adobe Commerce. 65 | * Create a funnel for merchants exhibiting the biggest growth from Mage-OS into Adobe Commerce and Adobe Experience Manager. 66 | * Protect and grow the lower-end Magento SMB market market share. 67 | * Competitive advantage vs other eCommerce platforms due to a vibrant and active community. 68 | 69 | **The next steps** 70 | 71 | The Magento Association is moving to take a larger role representing the whole community. We are hopeful that in time it will become the organization to take ownership of the Mage-OS distribution. 72 | As such, the next couple of weeks will be spent running conversations with the right people in the Association and within Adobe. 73 | 74 | In the meantime, we are engaged in the design and setup of the infrastructure and processes to make Mage-OS a sustainable long-term project. 75 | When we are satisfied with it, we will open it up to the public. 76 | 77 | We post the updates regulary [on the blog](/). You can also check [the Github](https://github.com/mage-os) for technical updates. 78 | 79 | Thank you, 80 | The Mage-OS Team 81 | 82 | * *Willem Wigman, Hyvä Themes B.V.* 83 | * *Vinai Kopp, Hyvä Themes B.V.* 84 | * *Andreas von Studnitz, integer_net GmbH* 85 | * *Fabian Schmengler, integer_net GmbH* 86 | * *Ignacio Riesco, Interactiv4 S.L.* 87 | * *Óscar Recio, Interactiv4 S.L.* 88 | * *Peter Jaap Blaakmeer, elgentos* 89 | * *Wouter Steenmeijer, elgentos* 90 | * *Jeroen Boersma, elgentos* 91 | * *Kuba Zwolinski, snow.dog* 92 | * *Kamil Balwierz, snow.dog* 93 | * *Bartek Igielski, snow.dog* 94 | * *Simon Sprankel, CustomGento GmbH* 95 | * *Ryan Hoerr, ParadoxLabs, Inc* 96 | * *Thien-Lan Weber, OneStepCheckout* 97 | * *Alessandro Ronchi* 98 | * *John Hughes, Fisheye Media Ltd.* 99 | * *Tomas Gerulaitis* 100 | * *Ivan Chepurnyi, EcomDev B.V.* 101 | * *Maciej Kalkowski, Centuria sp. z o.o.* 102 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-36-mage-os-assoc-announcement.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-09-02 4 | title: The Mage-OS Association has been founded! 5 | description: Read more about the board, the business control committee and the next steps. 6 | --- 7 | 8 | It finally happened! 9 | 10 | We have founded Mage-OS as an official association registered in Poland. Huge thanks to Maciej Kalkowski, who took care of the legal matters with the lawyers and organized everything, and also thank you to everyone who gathered in Warsaw as the initial signing members. Now Mage-OS can register a bank account, get members, and employ people. This is an important step toward much bigger things for this Magento-based open source project. 11 | 12 | ![A group picture of all the people present at the fouding of the Mage-OS Association.](/blog/2022/2022-07-21-founding-meeting-warsaw.png) 13 | 14 | Our goal is to strengthen the Magento ecosystem, and see it thrive for years to come! 15 | 16 | We intend to do that by giving everyone in the community the opportunity to get involved and make a difference. 17 | 18 | We believe that by providing the opportunity and resources for people to get started easily, we can revitalize the platform. We want to introduce a whole new generation of merchants and developers to their own journey with ecommerce's most powerful open source platform. 19 | 20 | Mage-OS is an independent, community-driven initiative, but we look forward to collaborating with Adobe and the Magento Association wherever possible to make this dream a reality. 21 | 22 | We look forward to getting to know you, too! Individuals like you getting involved is the most important of all. If you are interested, look at the [Get Involved](https://mage-os.org/get-involved) page to learn more. 23 | 24 | The founding board of Mage-OS consists of: 25 | 26 | ### Board of Directors 27 | 28 | * [Vinai Kopp](https://www.linkedin.com/in/vinai/) (DE) - President 29 | * [Thien-Lan Weber](https://www.linkedin.com/in/thienlan/) (FR) - Vice President 30 | * [Alessandro Ronchi](https://www.linkedin.com/in/alessandroronchi/) (IT) - Treasurer 31 | * [Ryan Hoerr](https://www.linkedin.com/in/rhoerr/) (US) - Actuary 32 | * [Ignacio Riesco](https://www.linkedin.com/in/ignacioriesco/) (ES) 33 | * [John Hughes](https://www.linkedin.com/in/johnhughes1984/) (UK) 34 | * [Maciej Kalkowski](https://www.linkedin.com/in/kalkos/) (PL) 35 | * [Peter Jaap Blaakmeer](https://www.linkedin.com/in/peterjaap/) (NL) 36 | 37 | ### Business Control Committee 38 | 39 | *Ensures accountability and transparency in Association operations.* 40 | 41 | * [Laura Folco](https://www.linkedin.com/in/laurafolco/) (US) 42 | * [Simon Sprankel](https://www.linkedin.com/in/simonsprankel/) (DE) 43 | 44 | ### Founding Members 45 | 46 | Many thanks to all individuals and companies present in person during the founding ceremony: 47 | 48 | [Borys Skraba](https://twitter.com/BorysSkraba) ([Strix](https://www.linkedin.com/company/strixcommerce/)), [Rafał Gadomski](https://twitter.com/GadomskiRafal) ([Advox](https://www.linkedin.com/company/advox-s.c/)), 49 | [Bartosz Zakręta](https://twitter.com/zakreta) ([Hatimeria](https://www.linkedin.com/company/hatimeria/)), [Marek Syrek](https://twitter.com/mareksyrek) ([Virtua](https://www.linkedin.com/company/virtuacodelab/)), [Tomasz Grzemski](https://twitter.com/Grzemski) ([Macopedia](https://www.linkedin.com/company/macopedia-sp-z-o-o-/)), [Krzysztof Ratajczyk](https://twitter.com/86rataj) ([Panda Group](https://www.linkedin.com/company/pandagroupdev/)), [Radosław Toczek](https://twitter.com/RadosawToczek) ([ClawRock](https://www.linkedin.com/company/clawrock/)), [Krzysztof Abram](https://twitter.com/chris_abraham1) ([Gate software](https://www.linkedin.com/company/gate-software/)), [Cezary Kożon](https://twitter.com/Cezary59949712) ([Spyro soft](https://www.linkedin.com/company/spyrosoft/)), [Łukasz Linczewski](https://twitter.com/llinczewski) ([Alekseon](https://www.linkedin.com/company/alekseon-sp.-z-o.o./)), [Mateusz Ogonowski](https://twitter.com/matogonowski) ([Growcode](https://www.linkedin.com/company/growcode/)), [Tomasz Piotr Lis](https://twitter.com/TomaszFox) and [Piotr Siejczuk](https://twitter.com/PiotrSiejczuk)! 50 | 51 | For more info, see [About the Mage-OS Association](https://mage-os.org/organization/about). 52 | 53 | ## More about Mage-OS 54 | 55 | We have not been standing still. In recent months we’ve: 56 | 57 | * Replicated Magento release packages with an independent build process from the source repositories; 58 | * Published a public Magento mirror composer repository using that independent process; 59 | * Released the first Magento updates since establishing the mirror (2.4.5 and related patches); 60 | * Had our first third-party mirror published by the same process; 61 | * Added validation and integrity checks to the mirror builds (thanks to Damien, Daniel, Anton, and others); 62 | * Created a nightly repository of Magento development builds, automatically generated each day from the latest Magento repositories; 63 | * Finalized the Mage-OS Code of Conduct and Association Statutes; 64 | * And more 65 | 66 | We have much more planned for the future! Our next technical focus will be on establishing the Mage-OS Distribution itself, to allow direct community contributions and releases of Mage-OS. 67 | 68 | You can already start using our Magento mirror repository or nightly repository today! Find more details and instructions at: [mage-os.org/distribution](https://mage-os.org/distribution#magento-mirrors) -------------------------------------------------------------------------------- /src/pages/blog/introducing-mage-os.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2021-09-28 4 | title: Status Update 2021-09-28 5 | description: The Future of Magento Open Source - Status Update 6 | groupId: 108619660 7 | --- 8 | ## The Future of Magento Open Source - Status Update 9 | 10 | Since we posted the [initial open letter](/blog/the-future-of-magento) on September 14th a lot has happened. 11 | 12 | **Thank you** 13 | 14 | First, we would like to thank all the people who added their names to support the initiative and who have reached out personally to encourage. 15 | 16 | Thank you also to everyone who spent time with us at Meet Magento Poland. We came with the intention to listen, you came with the open-mindedness to share your point of view and many productive discussions came out of it! 17 | 18 | Because technically already thousands of forks exist for the Magento 2 project on GitHub, we decided to name our thing a "distribution". 19 | 20 | 21 | **Introducing the Mage-OS distribution** 22 | 23 | Mage-OS will be an upstream compatible, lightweight, composition of Magento Open Source packages. Some of those packages will contain changes, and some will be entirely new. 24 | It will be compatible with all existing Magento 2 extensions and integrations. 25 | 26 | What differentiates Mage-OS from Magento Open Source and Adobe Commerce? 27 | 28 | * It will be more accessible to developers 29 | * It will be composed of a default lightweight package selection 30 | * It will allow faster integration of PRs 31 | * It will allow simple migration to Magento Open Source and Adobe Commerce 32 | 33 | 34 | **Our Value Proposition** 35 | 36 | > If the cake gets bigger, the whole ecosystem wins. 37 | 38 | We see the following value propositions for the five key pillars of our Magento ecosystem: 39 | 40 | *Mage-OS for Merchants* 41 | * Faster time to market: our technology is simpler and more accessible to a majority of developers. 42 | * Provides a growth path from the small beginning up to Adobe Commerce and Experience Manager 43 | * Reduced hosting costs due to simpler environmental requirements 44 | * Access to the big pool of Integrations and Extensions for Magento and Adobe Commerce 45 | 46 | *Mage-OS for Agencies / Service Integrators* 47 | * Reduced build time and less complexity to optimize your project costs 48 | * Easier to onboard new talent thanks to a more accessible codebase 49 | * Ability to target the lower SMB market with attractive margins thanks to lower project cost 50 | * Developers happiness: less frustration, more wins to motivate your teams and boost your talent retention 51 | 52 | *Mage-OS for Technology Partners (Extension Vendors, Hosting, SaaS providers)* 53 | * Business growth as the Magento market share increases 54 | * Access to the lower end SMB market section of merchants and agencies 55 | * Bigger return on investment for existing products due to a longer Magento lifespan 56 | 57 | *Mage-OS for Developers* 58 | * Improved sense of ownership 59 | * Faster moving distribution 60 | * Easier to contribute 61 | * Simpler to set up a development environment 62 | * Good entry point for a developer career in the Magento / Adobe Commerce ecosystem 63 | * Bigger return on investment for acquired Magento development knowledge due to a longer Magento lifespan 64 | 65 | *Mage-OS for Adobe* 66 | * Reduced pressure on the Magento Open Source GitHub PR/Issue list. 67 | * Breeding ground for innovations: create a protective buffer between community contributions and Adobe Commerce to safeguard stability. 68 | Community contributions can be evaluated in production environments without the risk of introducing instability to Magento Open Source or, by extension, Adobe Commerce. 69 | * Create a funnel for merchants exhibiting the biggest growth from Mage-OS into Adobe Commerce and Adobe Experience Manager. 70 | * Protect and grow the lower-end Magento SMB market market share. 71 | * Competitive advantage vs other eCommerce platforms due to a vibrant and active community. 72 | 73 | **The next steps** 74 | 75 | The Magento Association is moving to take a larger role representing the whole community. We are hopeful that in time it will become the organization to take ownership of the Mage-OS distribution. 76 | As such, the next couple of weeks will be spent running conversations with the right people in the Association and within Adobe. 77 | 78 | In the meantime, we are engaged in the design and setup of the infrastructure and processes to make Mage-OS a sustainable long-term project. 79 | When we are satisfied with it, we will open it up to the public. 80 | 81 | As soon as there are further newsworthy developments, we will communicate them timely. 82 | 83 | Thank you, 84 | The Mage Open Source Community Alliance (MOSCA) 85 | 86 | 87 | * *Willem Wigman, Hyvä Themes B.V.* 88 | * *Vinai Kopp, Hyvä Themes B.V.* 89 | * *Andreas von Studnitz, integer_net GmbH* 90 | * *Fabian Schmengler, integer_net GmbH* 91 | * *Ignacio Riesco, Interactiv4 S.L.* 92 | * *Óscar Recio, Interactiv4 S.L.* 93 | * *Peter Jaap Blaakmeer, elgentos* 94 | * *Wouter Steenmeijer, elgentos* 95 | * *Jeroen Boersma, elgentos* 96 | * *Kuba Zwolinski, snow.dog* 97 | * *Kamil Balwierz, snow.dog* 98 | * *Bartek Igielski, snow.dog* 99 | * *Simon Sprankel, CustomGento GmbH* 100 | * *Ryan Hoerr, ParadoxLabs, Inc* 101 | * *Thien-Lan Weber, OneStepCheckout* 102 | * *Alessandro Ronchi, Magento Community Maintainer* 103 | * *John Hughes, Fisheye Media Ltd.* 104 | * *Tomas Gerulaitis* 105 | * *Ivan Chepurnyi, EcomDev B.V.* 106 | * *Maciej Kalkowski, Centuria sp. z o.o.* 107 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-35.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-08-29 4 | title: Nightly repository now available; Mirror improvements; and more 5 | description: The Mage-OS mirror repository has been finalized, and nightly builds are published 6 | --- 7 | 8 | We are moving at a quick pace -- buckle up for a fresh batch of Mage-OS updates! 9 | 10 | ## Milestones 11 | 12 | We reached two milestones during the last week! 🎉🎉 13 | 14 | ### ✅ The Mage-OS Magento® Mirror Repository 15 | 16 | The first step towards an independent Magento Open Source distribution was the creation of an independently built mirror repository. 17 | 18 | We did this to learn what it takes to create an automated packaging system, and to provide an open alternative to the Adobe-managed `repo.magento.com` composer package repository. 19 | Even though we do not consider it a likely scenario, if something were to happen to the `repo.magento.com` composer repository, this ensures Magento Open Source will always be available to the public. 20 | 21 | Thanks to the QA tools created by [Damien Retzinger](https://github.com/damienwebdev) and [Daniel Sloof](https://github.com/danslo), which verify file parity and ability to install successfully, we are confident that our mirror packages are a drop-in replacement for the official Magento Open Source releases. 22 | At this time, the mirror includes all packages for Magento versions 2.3.7-p3 through 2.4.5. 23 | 24 | To install Magento Open Source from the mirror, change `repo.magento.com` to `mirror.mage-os.org` in the `composer create-project` command or your `composer.json` file. 25 | No composer authentication is required. For example: 26 | 27 | ``` 28 | composer create-project --repository-url=https://mirror.mage-os.org \ 29 | magento/project-community-edition install-dir 30 | ``` 31 | 32 | You can also create your own mirror repository using the Mage-OS tooling. This might be useful for hosters who want to provide a mirror for their customers, or offer their own open-access mirror to the public. 33 | For more information, please refer to the [readme of the repo-generator](https://github.com/mage-os/generate-mirror-repo-js#usage) project on github. 34 | 35 | We have a list of mirror composer repositories we are aware of at 36 | [mage-os.org/distribution#magento-mirrors](https://mage-os.org/distribution#magento-mirrors). 37 | 38 | If you have any questions or would like us to add your mirror, please join and ask in the #tech channel of our [Discord](http://chat.mage-os.org). 39 | 40 | 41 | ### ✅ The Mage-OS Magento® Nightly Upstream Repository 42 | 43 | In addition to recreating previous upstream releases of Magento Open Source, we have also started to publish a nightly release based on the current development branches of Magento Open Source. 44 | 45 | For the first time ever it is now possible to install a version close to the next upstream release with composer, matching the latest development code, without having to wait for an official beta release. 46 | 47 | ``` 48 | composer create-project --stability alpha \ 49 | --repository-url=https://upstream-nightly.mage-os.org \ 50 | magento/project-community-edition install-dir 51 | ``` 52 | 53 | Keep in mind that the nightly release might be broken sometimes, depending on the state of the code in the upstream Magento git repositories. 54 | 55 | We hope this will be useful for vendors and extension providers to track compatibility of their products with upcoming releases. 56 | 57 | It also was a great learning opportunity for us to figure out how to determine package dependencies and package versioning. 58 | 59 | The nightly builds are available now. We will be publishing a status page to show if the current upstream version is broken or not, soon. 60 | We will also continue to tweak the versioning and generation process as we learn more. 61 | 62 | Please join our [Discord](http://chat.mage-os-org) if you have feedback or if you are interested in the release process. 63 | 64 | ### Next Steps 65 | 66 | Now these two milestones are completed, we are focusing on the next steps towards a Mage-OS distribution that we can improve on while keeping compatibility intact. 67 | This will include: 68 | 69 | * Forking our mirror repositories 70 | * Automatically merging upstream changes 71 | * Exploring ways to handle merge conflicts as efficiently as possible 72 | * Running tests in a GitHub CI pipeline 73 | * Exploring ways to reduce the runtime for tests 74 | * Cleaning up the module dependency graph 75 | * Automating the permission setup on GitHub 76 | * Setting up a nightly build repository for the Mage-OS distribution 77 | * Choosing unmerged upstream PRs we want to introduce into Mage-OS 78 | * Figuring out how to make independent releases and consolidating them with upstream releases 79 | 80 | We look forward to working through these topics and many more over the next weeks and months. 81 | If you are interested in helping, please join the Mage-OS [Discord](http://chat.mage-os.org) and start chatting! We welcome any help! 82 | 83 | ## Organizational topics 84 | 85 | ### Mage-OS Association 86 | 87 | We will probably be using [Open Collective](https://opencollective.com/) as a platform to manage paid memberships for the Mage-OS Association. 88 | This is an important step to accomplish many of our goals for Mage-OS and the community as a whole. 89 | We expect the money raised through membership and donations to go to infrastructure and services, to hiring people to oversee and drive Mage-OS forward, and to directly funding development of the Mage-OS distribution through grants and other programs. 90 | 91 | The membership levels are currently being discussed in the #membership channel on [Discord](http://chat.mage-os.org). Please join and let us know your thoughts if this is of interest to you! 92 | 93 | As always, stay safe, and keep an eye on our blog. More news is coming soon! 94 | 95 | Best, 96 | 97 | The Mage-OS folks! -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-2022-week-38-diversity-and-inclusion.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-09-20 4 | title: Diversity and Inclusion! 5 | description: We strongly believe that a wide array of perspectives can only bring richer insights and fairer decisions. 6 | --- 7 | 8 | Diversity and Inclusion is an important and complex topic that is close to our heart. We strongly believe that a wide array of perspectives are a key factor in the success of any business, and can only bring richer insights and fairer decisions. 9 | 10 | Today we want to share our thoughts and address early feedback we received, in particular regarding the lack of geographical diversity in the governance of Mage-OS Association. 11 | 12 | Today, our board is made up of seven males and one female who serves as the Vice President with responsibilities to make decisions on behalf of the President. 13 | 14 | Our Business Control Committee has gender parity with one male and one female. 15 | 16 | The ten individuals are spread between seven countries in Europe and North America. It is not yet the role model for diversity and inclusion that we are aiming for. We need your help to get there. 17 | 18 | ### How did we get to this situation? 19 | When we decided to take an active role in the Magento Open Source ecosystem, the conversations happened to be between friends and business partners clustered in Europe. 20 | 21 | We felt an urgent need to move fast, and in order to do that we kept the group small and agile. 22 | 23 | We, the Mage-OS Association, do not believe we represent the whole 'Magento Community'. We are just one part of it. But we also believe we can grow that part. 24 | 25 | ### Where to now? 26 | The strategy of keeping the steering group small enabled us to move fast and create results. However, now that we have a solid foundation, we want to grow to represent more of the Magento Community, while continuing our momentum. 27 | 28 | The Mage-OS Association is founded, but still very young. We have technical processes and infrastructure, but they are far from complete. We have [Discord](http://chat.mage-os.org/) as a community hub, but it is still small. 29 | 30 | These foundational key stones will enable us to grow and evolve, and include everyone in the Magento Community that agrees with our core values and our purpose. 31 | 32 | ### Leadership & Board Membership 33 | Several times already we’ve heard that the Mage-OS Board should have representation from other geographic regions. And we agree, this would be ideal. 34 | 35 | However, it is not practical to have a board position only to represent. 36 | 37 | Being on the board right now means doing whatever work is required for Mage-OS, without compensation, in addition to a regular job. This commitment enables Mage-OS to achieve its goals. 38 | 39 | Anybody who takes it on themselves to do that work will naturally become influential within Mage-OS as it continues to take form. 40 | 41 | Even without a position on the board, the direction of Mage-OS can be influenced significantly by engaged individuals who take responsibility and put in the hours. 42 | 43 | **Aside:** *Board members are elected by the general assembly, which consists of all Mage-OS Association members. Half of the board member positions will be up for election in two years, the other half in three. After this initial cycle the term of office for all board members is two years.* 44 | 45 | ### Overcoming Privilege 46 | Putting in many hours into open source work for free is only possible when being in a privileged position. Creating a diverse and inclusive board with global representation, while also requiring work for free, is a dilemma. We believe it can be resolved over time through constant care and attention. 47 | 48 | In the ideal scenario, the Mage-OS Association is able to pay members from less privileged situations to work on Mage-OS, and allow them to gain influence and take on official roles. This will allow real diversity, and has been part of the vision for Mage-OS from the beginning. 49 | 50 | Right now we don't have funds to distribute for that purpose. Acquiring funds is the next step for the Mage-OS Association. Because one of the key values of Mage-OS is independence, the majority of funds will come through membership fees. (Join the discussion in [#membership](https://discord.com/channels/893449664093904936/1008574430563270697).) 51 | 52 | Soon we will be able to hire a Chief Operating Officer, who will work full time on running the association and grow it further. After that we can start funding members to work on Mage-OS. There is still a way to go, but by taking one step at a time, we will get there. 53 | 54 | We are aware that Diversity is not just about geography and culture, and we are eager to also hear your thoughts and ideas on how we can be improved further in other areas such as Gender Equality. 55 | 56 | We look forward to working with you on creating the future of Mage-OS! 57 | 58 | ### Local Representation 59 | The Magento family is a global network made up of business and friendship. 60 | 61 | The Mage-OS Association Board can’t travel to all events. Constant travel is unsustainable for individuals and for the environment. Even so, we feel local and physical representation of Mage-OS within the Magento Community is super important. 62 | 63 | This is why we need local Mage-OS representatives! 64 | 65 | Representatives would be people that attend Magento and eCommerce events in their region to give Mage-OS visibility, answer questions, and gather ideas and feedback from their local community (merchants, developers, agencies, and service providers). Then they share this information in the Mage-OS [Discord](http://chat.mage-os.org/) to raise awareness of their local situation. 66 | 67 | If time allows and if interested, representatives could also organize Magento meetups or give presentations about Mage-OS at events. 68 | 69 | Representatives from different regions can support each other by sharing slides, processes, and experiences. 70 | 71 | We invite you to become a Mage-OS representative for your local community! 72 | 73 | ### What you can do today 74 | 75 | Please help us: 76 | 1. Develop the Mage-OS local representation and global community by letting us know you are interested in [Discord](http://chat.mage-os.org/)! 77 | 2. Share best practices for tech companies and organizations to be more inclusive and diverse by highlighting the resources you've found useful, via [Discord](http://chat.mage-os.org/) or email: info@mage-os.org 78 | -------------------------------------------------------------------------------- /src/pages/blog/20221123-mageos-content-update.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-11-23 4 | title: Merchant Focused Content 5 | description: An update on the ongoing work to create a merchant focused content site 6 | --- 7 | 8 | While a lot of the focus of Mage-OS to date has been on forming our organization and moving things forward technically, there has also been work ongoing around content for Magento Open Source. In this update we want to share what we've been up to, why, what we're planning next, and finally, how you can get involved! 9 | 10 | ## Why does Mage-OS care about Magento content? 11 | 12 | Since acquiring Magento, Adobe has stopped publishing the magento.com domain, and now forwards that to information about their paid Adobe Commerce product, with no mention of Magento Open Source at all. In the process, they removed valuable information about Magento Open Source and made it difficult to learn about the platform or start using it. Our aim is to create a replacement site where merchants, developers, and other professionals can find out key information about the platform in one central location. 13 | 14 | Furthermore, with the inaccurate 'Magento is Now Adobe Commerce' marketing still being used by Adobe, we feel it's more important than ever that information about Magento Open Source is made publicly available. 15 | 16 | ## What is Mage-OS' vision for a Magento content site? 17 | 18 | In addition to creating a replacement for content from the old magento.com site, we want to make it a proper community portal. We want this content site to be a gateway and repository to everything you could want to know about Magento as a platform, product, and community. The website should allow you to discover the entire ecosystem. 19 | 20 | These are the areas we want this site to contain: 21 | 22 | * A strong landing page that explains what Magento Open Source is and helps direct visitors to the right place to learn more based on their needs (e.g. merchants, developers, etc.) 23 | * Multiple product pages with technical (but merchant friendly) details about the different features Magento Open Source offers, e.g. multistore, CMS/Page Builder, catalog and search, checkout, SEO, marketing, etc. 24 | * Platform comparison pages, e.g. how Magento Open Source compares against other eCommerce platforms, including an unbiased comparison with Adobe Commerce (the paid version of Magento that Adobe offers) 25 | * Multiple links for developers, merchants (such as documentation sites) and community resources (such as the various forums and chat groups) 26 | * A community directory where agencies, technology providers, and merchants can list their businesses, sites, and services 27 | * News and event listings 28 | * A blog with merchant case studies and industry best practice articles 29 | 30 | Note: we're also open to further suggestions! 31 | 32 | ## Our Journey So Far 33 | 34 | There's obviously a lot we want to achieve. So far we've focused on getting a development site set up that we can add content to, and have made progress in the following areas: 35 | 36 | * The main landing page 37 | 38 | * An initial draft of the site navigation, including many external resources 39 | 40 | * A number of product/functional pages 41 | 42 | * The community directory 43 | 44 | We certainly won't launch with all the above listed areas, and we will be taking an MVP (Minimum Viable Product) approach to ensure we can launch something useful, given the harm caused to the ecosystem by not having an informative magento.com site. 45 | 46 | ### On Adobe, the Magento Association, the Magento branding, and the magento.com domain 47 | 48 | Our initial intention was to create a non-Mage-OS-specific site that could replace magento.com, ideally on the same domain or a similar one such as magento.org, and utilize the Magento branding (e.g., the Magento logo) on that informational site. Additionally, we offered to hand over control of that site to the Magento Association (MA) or even Adobe, should they wish to maintain it. 49 | 50 | Many discussions were held during the Magento Association Task Force and Content Committee meetings over the past year, with Adobe representatives present on multiple occasions. However, after almost a year of attempting to make this happen, and due to the lack of movement, interest, and willingness (from Adobe, not the MA), we've unfortunately accepted this will probably never happen. As a result, we are putting the site fully under the Mage-OS brand rather than Magento (though references to Magento Open Source as a product will still remain). 51 | 52 | ## Next Steps 53 | 54 | Up until the past few weeks, we've only had a handful of people involved, focused on getting a site up and running and adding content. However, recently we've had additional help offered that should improve and accelerate our progression going forward. 55 | 56 | First, maxcluster (a Germany-based hosting company) have kindly offered their support. They are currently undertaking a strategic review of what we've done to date and how we can better move forward in terms of architecture, content, audience, and messaging. We hope to have the results of this in the coming weeks. 57 | 58 | Second, we've had assistance offered by Amasty to help organize and manage the content effort better! They’ve set up a Trello board and planned all the current tasks we have to work through, so we can better see progress and meet deadlines. 59 | 60 | After the strategic review, we'll further update the tasks and deadlines and have a much clearer roadmap to launch. 61 | 62 | ## How Can You Get Involved? 63 | 64 | If you want to help us create this Mage-OS/Magento ecosystem content site, there are many ways you can be involved, listed below. But first off, you’ll need to join the [Mage-OS’ Discord server](http://chat.mage-os.org/) (as this is used as our main communication method) and be in agreement with our [contribution guidelines](https://docs.google.com/document/d/1vUYJ7gPut-uefaSmOA8SzgoYh9fYBaFmSzKq9XTfujc/edit#). 65 | 66 | Here's how you can contribute: 67 | 68 | * Join the conversation and discussion on the #content channel on our Discord server 69 | * Share your views and input on our weekly meetings 70 | * These take place on Mondays at 15:00 UTC (07:00 PST, 10:00 EST, 15:00 GMT, 16:00 CET, 17:00 EET, 20:30 IST) on our Discord server 71 | * Help write or review content for pages on the site 72 | * Create/provide assets we can utilize on the site (e.g. screenshots, imagery, diagrams, and videos) 73 | * Contribute to the overall site structure and content required 74 | * Help with organizing and planning content and other tasks 75 | * Aid with the overall strategy and vision of the site 76 | * Undertake frontend development (theming) to help improve the look and feel of the site 77 | * Add your organization, site, or service offering to the community directory section of the site 78 | 79 | Alternatively, if you just want to keep up to date with the ongoing progress, then please ensure you are subscribed to the [Mage-OS newsletter](https://mage-os.org/newsletter). 80 | 81 | ## Thanks 82 | 83 | Finally, we wouldn’t have gotten this far without the help of many folks in the community. So, a big thank you to Arron Moss, Barbaros Selim Büyükelçi, Benno Lippert, Bernard Robbins, Brent Peterson, Damien Retzinger, Dominik Rammert, Nicole Mentzen, Sergej Derzap, Willem Wigman and many others (plus, of course, all the [Mage-OS Board](https://mage-os.org/organization/about) members who’ve been involved). 84 | 85 | Once again, we'll have more to share soon. Thanks for reading! 🙌🏻 86 | 87 | The Mage-OS folks 88 | -------------------------------------------------------------------------------- /src/pages/blog/20230127-january-update.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2023-01-27 4 | title: January 2023 Updates 5 | description: See the latest on the Mage-OS Distribution, content, community, and association 6 | --- 7 | 8 | Happy New Year, dear friends! 9 | 10 | Over the holidays we took some time to rest and reflect on all that we’ve achieved last year. We hope you found as much energy as we did to help reach your 2023 goals. 11 | 12 | While it was quiet on the outside, we still got a lot done, thanks to your contributions. 13 | 14 | 15 | ## Founding the Mage-OS Association 16 | 17 | In full transparency, we are still waiting for the Mage-OS Association foundation to be finalized. Our first application and appeal were returned by the court of Warsaw for statutory changes. We’ve been working with our lawyers and the court to resolve the situation. The latest word is the court and our lawyers are treating our case as a top priority, and we hope to have good news soon. 18 | 19 | This delay has prevented us from opening a bank account or conducting any business that requires a registered entity. Until then, we aren’t able to open our membership program, or collect or disburse funds to speed up the pace of our activities. 20 | 21 | The silver lining is that this has given us more time to prepare the membership program, budget, and plans for the coming year. Here’s a sneak preview of the Mage-OS supporter program badges: 22 | 23 | ![A preview of the Mage-OS Association's upcoming membership badges, courtesy of Amasty](/blog/2023/2023-01-27-mageos-badge-preview.png) 24 | 25 | A massive thank you to Sergej Derzap and the Amasty graphic team for their work designing these badges! 26 | 27 | 28 | ## Technical Update 29 | 30 | We have discovered that the nightly-mirror builds are an excellent way to be aware of what is happening inside Magento Open Source. 31 | 32 | Recently, an issue in the Magento Open Source repository caused the Mage-OS nightly builds to fail. Adobe implemented a workaround in the 2.4.6 beta builds (outside of the Magento repository), which we have also applied to the nightly builds until a proper and permanent solution is applied. 33 | 34 | In brief: A new [Magento_Elasticsearch8](https://github.com/mage-os/mirror-magento2/tree/2.4-develop/app/code/Magento/Elasticsearch8) module is added to Magento Open Source 2.4.6, and requires `elasticsearch/elasticsearch` library version 8. That directly conflicts with the existing `Magento_Elasticsearch7` module, which requires version 7 of the same library. Only one can be installed at a time, so this causes an unresolvable dependency failure and a broken build. 35 | 36 | In 2.4.6-beta1, Adobe resolved this by removing the requirement from `Magento_Elasticsearch8`. However, that makes the `Elasticsearch8` module non-functional, because composer will always install `elasticsearch/elasticsearch` version 7. Damien Retzinger opened [an issue](https://github.com/magento/magento2/issues/36687) on the Magento Open Source repository to track and discuss this problem. 37 | 38 | These kinds of issues can go undetected for a long time between releases, and this is another reason we are happy to have the nightly builds in place as an early warning system. 39 | 40 | During the holiday season most of us involved in the technical development of Mage-OS took a break, though some continued to power on (shout out to Adam Crossland!). Since the new year, momentum has picked up again. Work is progressing on the continuous integration pipeline, which is critical to us accepting contributions to the Mage-OS Distribution. 41 | 42 | There is also discussion ongoing about the first new feature we will add to the upcoming Mage-OS Distribution. 43 | 44 | We invite you to join our technical meetings every week on Tuesdays at 3 PM CET (9 AM EST) at [chat.mage-os.org](http://chat.mage-os.org)! 45 | 46 | 47 | ## Content Update 48 | 49 | Things have been moving along nicely on the new Mage-OS website. The new website will give vital information about Mage-OS and Magento Open Source to merchants and professionals, since such content no longer has a home at Magento.com. 50 | 51 | Since the last update, the content team has migrated all content from the existing Mage-OS site, decided on all the additional content we need for launch, added many content pages, and updated the navigation menu following a strategic review. 52 | 53 | We’re now working on the final content and design for our initial content site launch. We are hopeful to meet (if not exceed) our target of launching the new site by April. 54 | 55 | This has all been achieved thanks to our team of regular contributors. Special thanks to Sergej Derzap (and the Amasty team), Roland Haselager, Neil Khedekar, Aaron Moss, and John Prendergast for their recent contributions. We would not have gotten this far without them. 56 | 57 | If you want to get involved, please reach out in the #content room or join our weekly meetings on Mondays at 4 PM CET (10 AM EST) at [chat.mage-os.org](http://chat.mage-os.org). Right now we’re looking for help with: 58 | 59 | * Technical content writing about Magento Open Source as a platform/product, and platform comparisons 60 | * Non-technical content writing about the Magento community 61 | * Collating and populating useful resources for merchants, developers, and other Magento professionals 62 | * Creating/adding images, screenshots, and videos to pages to make them visually more appealing 63 | * Some small frontend development tasks to tidy up the theme and improve performance 64 | * 301 Redirects from the old site 65 | 66 | If there is something else you feel you can contribute with, please let us know! 67 | 68 | 69 | ## Community Update 70 | 71 | As of today, over 600 of you have joined our [Discord community](http://chat.mage-os.org), and nearly 900 are following us on [LinkedIn](https://www.linkedin.com/company/mage-os/). 72 | 73 | A number of localized channels have been created in Discord for the following communities: Netherlands, Ukraine, Poland, France, India, and Italy. If you have a local ecommerce community you're interested in giving a home in Mage-OS, let us know! 74 | 75 | The Dutch community has gone a step further, by founding a new Dutch Magento community organization under the name of Mage-OS: [Mage-OS Nederland](https://nl.mage-os.org/). This organization was formally created in December 2022. During the general meeting of Mage-OS Netherlands on January 19th 2023, its new board was installed and consists of Jisse Reitsma, Sanne Bolkestein, Sander de Graaf, Jeroen Boersma, Roland Haselager, Core de Reeper, and Michiel Gerritsen. We hope that the success of Mage-OS NL can serve as a blueprint for other regional groups going forward. 76 | 77 | 78 | ## Mage-OS in the World 79 | 80 | Community events and outreach have stepped up in a big way recently, and we thank you all for your interest! 81 | 82 | We were delighted to meet many of you at recent events, and thank you for all the great chats and feedback you've given us. Here are some happenings you may have missed: 83 | 84 | * [Meet Commerce Spain](https://drive.google.com/file/d/10m_Ni5gA6RyotI-5E1afJIPlGJ5q1vBe/view?usp=share_link) 85 | * JetRails podcast: [Mage-OS - A New Magento Non-Profit For a New Era](https://youtu.be/3b2wb9gioiE) 86 | * CenturiaLive: [A new way to connect with Magento Community: Mage-OS](https://www.linkedin.com/posts/centuria-s-a_centurialive-activity-7005823254049239040-9R8t) 87 | * [Magento Meetup Mainz](https://www.linkedin.com/posts/mage-os_mageos-magento-community-activity-7020451880921112576-_WhX/) 88 | * [Magento Meetup Poznan](https://www.linkedin.com/events/magentopozna-meetup7014236022452457472/comments/) 89 | * The first ever [Mage-OS Meetup, India](https://www.linkedin.com/feed/update/urn:li:activity:7020745173651341313/) 90 | * The foundation of [Mage-OS Nederland](https://www.yireo.com/blog/2023-01-14-quickly-choose-magento-association-or-mage-os) 91 | 92 | #### Where will we be next? 93 | 94 | * 3rd February 2023: [Meet Magento India](https://meetmagento.in/) – Vinai will give a remote talk about Mage-OS 95 | * 8th February 2023: [Magento Meetup Stuttgart, Germany](https://www.phoenix-media.eu/de/magento-stammtisch-stuttgart.html) 96 | * 1st April 2023: [MageTitans UK 2023, Manchester, UK](https://uk.magetitans.com/) 97 | 98 | 99 | That's all for now. Thanks for reading! 🙌🏻 100 | 101 | The Mage-OS folks 102 | -------------------------------------------------------------------------------- /src/components/Header.astro: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | --- 4 |
10 | 19 | 28 | Mage-OS 29 | 33 | 37 | 43 | 47 | 51 | 55 | 59 | 63 | 67 | 71 | 75 | 76 | 77 | 78 | 88 |
89 | -------------------------------------------------------------------------------- /src/pages/blog/mage-os-update-january-2022.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/post.astro' 3 | date: 2022-02-02 4 | title: Mage-OS update January 2022 5 | description: An update on last months progress on Mage-OS 6 | --- 7 | 8 | ## Mage-OS update January 2022 9 | 10 | Dear Magento community members, 11 | 12 | It has been a while since you last heard from us. Apart from updates on social media and conferences/discussion panels we haven’t communicated much publicly. 13 | 14 | This will finally change today. You may expect regular updates from us, in short or long form. Even if there is little to report on, we will let you know what is being worked on. 15 | 16 | There are a couple of things we would like to update you on, and tell you what happened over the course of the past four months. 17 | 18 | ### There was a lot of talking 19 | When we wrote our letter, it came from concerns around the future of Magento Open Source. There was no clear direction on the Open Source product, especially compared to the amount of communication and marketing around Adobe Commerce. 20 | 21 | The community seemed to be slipping away, vanishing into the dark. We believe, in retrospect, that this is the result of two things: 22 | 23 | * Leadership at Adobe changed and core members with strategic positions left. There was no replacement for these figures and a lack of business case for further investment into Open Source. 24 | * A growing disconnect between Adobe and the Community has risen, as a result of dissatisfaction around the Open Source contribution model, a lack of communication and a lack of a clear roadmap 25 | 26 | We very much believe these two factors played into each other and created a downward spiral. 27 | 28 | It seems the open letter broke that spiral. Adobe noticed the community still cared and had a real need for an open strategy around open source and a commitment to the long-term support of Magento Open Source. 29 | 30 | As a result, the Open Source Task Force was created by the Magento Association, where the community and Adobe get together to voice these concerns, discuss the future of Magento and find common ground on important issues, to make sure the community can get back on their feet and close the gap between Adobe and the Community. 31 | 32 | During a one hour meeting every second week, several topics are being discussed, with mixed results. So far eight calls have taken place, usually joined by about 10 people, of which almost half are Adobe employees. The rest consists of community members (those that are able to join) under which three of our Mage-OS members; Bartek Igielski, Vinai Kopp and Willem Wigman. 33 | 34 | Even though there is little publicly visible output coming from these efforts, we believe it has been extremely valuable just to get an alignment on what the community needs from Adobe, and what Adobe is willing to provide. 35 | 36 | * Commitment has been made by Adobe to keep investing into Magento Open Source, and ensure us there is no plan for deprecation of the monolith 37 | * The community engineering team will get more resources in the near future 38 | * Adobe has proposed a Community maintained “Short Term Support” (STS) version of Magento Open Source. The plans are still at a very early stage, but they look quite promising. This is a clear signal that awareness of the Community and the importance of Magento Open Source is growing inside Adobe, and - if followed through - would demonstrate Adobe's long term commitment to Open Source. There are many open questions which are being discussed in the task force. 39 | * Luma will be deprecated, but not on short term 40 | * Discussions are ongoing around the possibility of slimming down the core of the Magento Framework to allow multiple distributions in the future. 41 | * Adobe will not provide any marketing around Magento Open Source towards merchants from either magento.com, or the adobe.com website. The magento.com domain now redirects to a landing page at adobe.com with resources around Magento. 42 | 43 | It is much clearer now what Adobe’s strategy is regarding Open Source, and that is a big win. 44 | 45 | We now feel a lot more confident that Adobe will take care of the basic needs to be able to keep using Magento Open Source for the next couple of years. We can expect full vendor support for critical bugs, stability upgrades and security support. 46 | 47 | When Adobe follows through with their suggestion of a Community owned STS version of Magento Open Source, the power of the community and the backing of a large enterprise will enable innovation and growth of the Magento eco-system for many years into the future. 48 | 49 | This is all of great value, and an investment from Adobe we should not oversee or underestimate. We are thankful for this support. 50 | 51 | It is also now very clear that, even though Adobe takes care of the platform’s basic needs, it will not invest heavily in any innovation or feature development on it. The focus is very much on Adobe Commerce and it’s position in the Adobe ecosystem, building out integrations with other Adobe products and microservices, rather than building new features using Magento (PHP) extensions. 52 | 53 | If we want the platform and community to flourish and grow, it will have to come from the community. 54 | 55 | So now we know what we are planning for. 56 | 57 | ### The Fork 58 | A fork was indeed created. Which is not a big thing in itself, since many developers fork Magento on a daily basis. It is even a requirement to be able to contribute to the platform. 59 | 60 | What is special about this fork, is that it is tracking changes on the official Magento repositories and automatically updates, then creates meta-packages from the repository and puts these into a distributed repository that can be used with Composer. 61 | 62 | Figuring out how to split out the mono-repo from Magento’s repositories and creating packages out of those, mirroring exactly the same output as Magento’s official repository took some time to reverse engineer. And to find the most performant and efficient way to get this done. 63 | 64 | We will publish both the fork, the build scripts and all documentation on the process we went through publicly soon. Even though we’ve worked on this in the background, our goal is to be as transparent as possible about what we did and why. 65 | 66 | These processes will be up for discussion as soon as we’ve published it and invited anyone interested into our Discord (see “The Community” below). 67 | 68 | The Fork is just a contingency fallback for when the day comes when large deprecations might happen on the official Magento repository or when those would go away all at once. 69 | You might remember when Magento 1 was deprecated, not only the repository was gone, but also the merchant documentation. 70 | 71 | We want to be prepared for any scenario in the future, and have complete ownership over a copy of the product and have the knowledge to maintain such an infrastructure. 72 | 73 | This also includes the merchant documentation. 74 | 75 | ### The Distribution 76 | The interesting part will be the work on our own distribution. We imagine building a version of Magento that allows us a lot more flexibility to evolve. 77 | 78 | This would include: 79 | * Removing optional functionalities in core, such as a choice between MySQL search or Elasticsearch, or removing MSI (Multi Stock Inventory) by default 80 | * Implement bug fixes faster 81 | * Implement performance improvements faster 82 | * Include new features 83 | * Repackage Luma into an LTS version, removing Luma from core by default 84 | 85 | And many other things we can’t even think of at this stage. It should allow us to do experiments again, and bring back innovation to the platform. 86 | 87 | Since the proposed Magento Open Source STS version is not yet realized, we believe we need to move forward with Mage-OS. Any work we do will be able to flow back into Magento STS when it exists and is in the hands of the community. 88 | 89 | The community needs an initiative to keep the dialog with Adobe alive and growing. 90 | 91 | ### The Community 92 | The community needs a big shift. We’ve gotten caught up in negativity and got tired of the push back we got from those that got burned by the release of Magento 2. 93 | 94 | Yes, we can safely state that the initial release of Magento 2 was premature and caused damage to many members of our community. Merchants, agencies and developers all alike. 95 | 96 | Many of those that were hurt during that period are no longer part of our community, based on their experiences from that moment in time, which is understandable. 97 | 98 | Today however, Magento 2 is in fantastic shape, thanks to a lot of effort put in by both Adobe and the community. The platform has never been more flexible and stable, filling all merchants' needs. 99 | 100 | So what our community needs is a new sound that resonates with today's state. And leave the past behind us. 101 | 102 | We have a vibrant community with businesses, people and families that are building their livelihoods on Magento offering Integrations, Extensions, Hosting, Payments, Marketing services and so much more. 103 | 104 | We have everything we need, right in front of us. Positivity in our ecosystem will go a long way. 105 | New merchants are offered the choice for a platform every day, new students become professionals and new agencies grow out of those students every day. 106 | 107 | The eCommerce industry keeps growing, and every platform keeps growing. The only thing we need to do is to get together and start moving. 108 | 109 | We need Magento events to make a comeback, educate and welcome newcomers, celebrate our victories and help each other out, sharing solutions to our common problems as we’ve done for over a decade. 110 | 111 | Mage-OS will open up to the public using Discord.com as a communication platform, where we would like to welcome you and exchange ideas on how to start defining the future of Magento. 112 | 113 | We will publish the access information to this environment on our website and newsletter as soon as we’ve made it available. 114 | 115 | ### The Magento Brand 116 | Adobe owns the rights to the Magento brand. They also decided not to market the Magento brand any longer. 117 | The Magento Association owns the rights to a subset of the Magento brand, for a limited amount of time. This means that we have very limited control over the brand. 118 | 119 | And that is okay. We will make our best effort to provide the branding around the product and make it clear it is the same product without violating intellectual property. 120 | 121 | Mage-OS will be the name of our initiative, and the distribution we will build. Additionally, we’ve started working on a branding and content strategy. 122 | 123 | We will make sure merchants have a place to go to and learn about the Magento platform and its capabilities. 124 | 125 | ### The Mage-OS entity 126 | We’ve also set up a working group to focus on an official entity for Mage-OS. This will include the organization structure, strategy, funding, partnerships and all that comes with that. 127 | 128 | There are currently two weekly meetings: one technical meeting and one organizational. The form in which these meetings are being held is temporary until we’ve set up the basics and feel we have the capacity to expand more globally. When we open Discord up to everybody, we welcome new members to participate in these meetings, too. 129 | 130 | We are very much aware of the closed nature of our current organizational structure, which is absolutely not meant for the long term. It merely exists in this form because we tried to stay small and regional to be able to move fast and plan meetings in the same time zone. We’re implementing a code of conduct and will focus on diverse representation in the organization as soon as possible. 131 | 132 | ### Next steps 133 | We’re planning to start bringing out regular updates on progress. Please make sure you are on [our mailing list](#newsletter) if you want to be updated on our next steps, which will include: 134 | * Open access to Mage-OS Discord 135 | * Public access to the Mage-OS fork 136 | * A new website to replace the current mage-os.org site with background information, a blog and merchant information about Magento 137 | * Progress updates on the Mage-OS distribution 138 | 139 | [Sign up to our mailing list below](#newsletter) 140 | 141 | Thank you, 142 | 143 | The Mage-OS team, 144 | 145 | * Willem Wigman, Hyvä Themes B.V. 146 | * Vinai Kopp, Hyvä Themes B.V. 147 | * Andreas von Studnitz, integer_net GmbH 148 | * Fabian Schmengler, integer_net GmbH 149 | * Ignacio Riesco, Interactiv4 S.L. 150 | * Óscar Recio, Interactiv4 S.L. 151 | * Peter Jaap Blaakmeer, elgentos 152 | * Wouter Steenmeijer, elgentos 153 | * Jeroen Boersma, elgentos 154 | * Kuba Zwolinski, snow.dog 155 | * Kamil Balwierz, snow.dog 156 | * Bartek Igielski, snow.dog 157 | * Simon Sprankel, CustomGento GmbH 158 | * Ryan Hoerr, ParadoxLabs, Inc 159 | * Thien-Lan Weber, OneStepCheckout 160 | * Alessandro Ronchi, Magento Community Maintainer 161 | * John Hughes, Fisheye Media Ltd. 162 | * Tomas Gerulaitis 163 | * Ivan Chepurnyi, EcomDev B.V. 164 | * Maciej Kalkowski, Centuria sp. z o.o. 165 | -------------------------------------------------------------------------------- /src/pages/organization/statutes.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: '@/layouts/document.astro' 3 | title: Mage-OS Association Statutes 4 | description: Mage-OS Association Statutes 5 | --- 6 | 7 | ## Name, legal form, and registered office 8 | 9 | 10 | ### Art. 1 - Name and legal form 11 | 12 | Under the name Mage-OS Association there exists an association (“Association”). 13 | 14 | 15 | ### Art. 2 - Registered office 16 | 17 | The Association has its registered office in Poznań, Poland. The area of Association’s activity is the European Union and other countries using the Mage-OS platform. 18 | 19 | 20 | ## Purpose and Tasks 21 | 22 | 23 | ### Art. 3 - Purpose 24 | 25 | The purpose of the Mage-OS Association is to enable the long-term success of the Magento ecosystem by empowering the community to maintain and develop the Mage-OS platform (based on Magento Open Source) through communication, coordination, and funding. 26 | 27 | In particular, the Association has the following goals: 28 | 29 | * Maintain and develop the Mage-OS platform; 30 | * Increase the number of people involved in the Magento ecosystem and the Mage-OS platform; 31 | * Nurture good vibes and values; 32 | * Increase the share of the Magento ecosystem in the ecommerce market; 33 | * Increase confidence in the Magento ecosystem; 34 | * Position Mage-OS as a leading option for custom ecommerce development; 35 | * Facilitate access to Magento providers. 36 | 37 | The Association conducts business activity in the areas of: 38 | 39 | * 62.01 - Software services 40 | * 62.02 - IT consulting 41 | * 62.03 - Infrastructure management related services 42 | * 62.09 - Other IT and computer services 43 | * 58.29 - Publishing of software 44 | * 82.30 - Event (expo, conferences, etc) organization 45 | * 63.12 - Internet portals 46 | * 47.41 - Computers and software licenses b2c selling 47 | * 85.60 - Education support 48 | * 85.59 - Other education activities 49 | 50 | 51 | ### Art. 4 - Tasks 52 | 53 | The Mage-OS Association will achieve its purposes by: 54 | 55 | * Coordinating and funding the Mage-OS platform development and long-term support; 56 | * Creating quality content that supports the long-term livelihood of the platform and the Magento ecosystem; 57 | * Funding and supporting events that align with the Mage-OS Association purposes; 58 | * Providing documentation and education/certification paths; 59 | * Supporting organizations empowering the Magento Open Source ecosystem; 60 | * Providing insights, research, and materials to support these outcomes. 61 | 62 | 63 | ## Membership 64 | 65 | 66 | ### Art. 5 - Classes of members 67 | 68 | Membership in the Mage-OS Association shall be open to anybody adhering to the Association’s statutes and code of conduct. 69 | 70 | We distinguish three classes of members: regular members, honorary members, and supporting members, all having the same voting rights and obligations unless stated otherwise elsewhere in these statutes. 71 | 72 | 73 | #### A - Regular members 74 | 75 | Dues-paying natural persons are entitled to join the Association as regular members. Dues shall be determined annually by the Board of Directors. 76 | 77 | 78 | #### B - Honorary members 79 | 80 | Honorary members are people who have rendered a particular service to the Association or its objectives. Membership lasts one year after election by the General Assembly. Honorary members shall be exempt from the membership fee obligation. 81 | 82 | Nominations for honorary membership may be submitted either by the Board of Directors or by 10% of the members of the Association. Such nominations should be submitted to the President prior to the General Assembly. 83 | 84 | #### C - Supporting members 85 | 86 | Supporting members are dues-paying individuals or legal entities that have given financial assistance, in material or substance, to achieve the objectives of the Association. The Association reserves the right to review all prospective supporting members and contributions, and decline any considered contrary to the Association’s best interests. 87 | 88 | 89 | ### Art. 6 - Leaving the Association 90 | 91 | Any member with a formal role in the Mage-OS Association shall be entitled to leave the Association by giving one months' written notice to the Board of Directors. 92 | 93 | All other members may leave the Association at any time by giving notice to the Board of Directors, or by not renewing membership at the end of a membership year. Any dues paid prior to leaving the Association will be considered support for the Association’s activities, and will not be refunded. 94 | 95 | Membership shall also end upon dissolution of the legal person or the death of the member. 96 | 97 | 98 | ### Art. 7 - Suspension or termination of membership 99 | 100 | Any member that violates statutes, regulations, resolutions, code of conduct, or otherwise acts in a manner that is seriously contrary to the interests of the Association, can have their membership suspended or terminated by the Board of Directors. The Board of Directors must notify the person of the grounds for the action, and prepare a resolution for review at the next Board of Directors meeting. 101 | 102 | Before the resolution is voted on, the Board of Directors shall give the member an opportunity to state his/her position. The Board should inform the member about the planned date of resolution. The Board is not bound by the state of the member under review. 103 | 104 | Any person can report misconduct of a member to the Board of Directors. In such case, the Board shall investigate, and if unacceptable behavior is determined to have occurred, the Board of Directors will be entitled to terminate, suspend, or send written warning to the member to change their conduct. If warned, the Board is entitled to suspend a member if the member’s conduct has not improved during two weeks after being given a warning. 105 | 106 | Termination or suspension of membership shall require a majority decision by the Board of Directors. 107 | 108 | A member can be suspended for a fixed period of time, no longer than 12 months. 109 | 110 | Termination of a membership will be considered indefinite. A terminated member shall be entitled to appeal the decision with the Board of Directors no less than six months after their membership is terminated. The Board’s decision on the appeal is final. 111 | 112 | Terminated members may be reinstated only upon the affirmative vote of a majority of the Board of Directors then in office. Suspended members will be reinstated at the conclusion of their suspension term, or by the affirmative vote of a majority of the Board of Directors. 113 | 114 | Terminated or suspended members are deprived of any active or passive right to vote, and may not participate in any Association activities, until such a time as their membership is restored. 115 | 116 | Non-members of the Association may be disallowed from further participation in Association activities at any time, for violation of statutes, regulations, resolutions, code of conduct, or otherwise unacceptable behavior or actions. 117 | 118 | 119 | ## Organization 120 | 121 | 122 | ### Art. 8 - Governing bodies 123 | 124 | The organs of the Association shall be: 125 | 126 | 1. Assemblies 127 | 2. Board of Directors 128 | 3. Business Control Committee 129 | 130 | There may be other committees in the Association than those indicated above. 131 | 132 | 133 | ### Art. 9 - Assemblies 134 | 135 | The Board of Directors shall keep minutes of all Assembly resolutions. Votes that have been taken shall be summarized and recorded in the minutes. 136 | 137 | All General Assemblies and Special Assemblies will have a Chair appointed in advance by majority vote of the Board of Directors, or else the Actuary will act as Chair of the Assembly. 138 | 139 | 140 | #### A - General Assembly 141 | 142 | The General Assembly is the supreme governing body of the Association. The General Assembly is an annual meeting that all members of the Association may join. 143 | 144 | The General Assembly is convened by the Board of Directors and takes place in the first half of every year. 145 | 146 | The Board of Directors will invite Association members in writing at least 30 days before the meeting (via email), with the meeting location, time, and agenda items. 147 | 148 | Each member of the Association can submit requests or topics to the agenda of the General Assembly. Such requests must be submitted to the Chair at least 14 days prior to the General Assembly, in writing and with substantiation. The Chair may require a reasonable number of member signatures to be included with each agenda request for the General Assembly. The Chair of the General Assembly shall announce supplemental agenda items to the General Assembly at the beginning of the meeting. 149 | 150 | Standard business of the General Assembly will include: 151 | 152 | 153 | 154 | * Acceptance of the annual report drawn up by the Board of Directors 155 | * Acceptance of the annual financial statements, and the reports of the Business Control Committee 156 | * Granting of discharge to the Board of Directors 157 | * Granting of discharge separately to the Treasurer 158 | * Granting of discharge to the Business Control Committee 159 | * Review of the budget for the current year 160 | * Processing of applications for the Board of Directors and elected committees 161 | * Election of the Board of Directors and elected committees 162 | * Changes to the Association statutes 163 | * Appointment of honorary members 164 | 165 | Failure to discharge shall be tantamount to removal from the office held. 166 | 167 | 168 | #### B - Special Assembly 169 | 170 | A special meeting of the Association’s membership may be called by the President or by a majority of the Board of Directors. 171 | 172 | The Board of Directors must invite all members in writing at least 15 days prior to the Special Assembly (via email), with the meeting location, time, and agenda items. 173 | 174 | 175 | ### Art. 10 - Quorum and voting 176 | 177 | A quorum for any General Assembly or Special Assembly of the Mage-OS Association shall be the number of members in attendance. Unless otherwise specified in these statutes, decisions of the Association shall be made by a majority vote of those members present at the Assembly. 178 | 179 | Participation in a General Assembly or Special Assembly shall also be possible remotely without physical presence, via electronic transmission. 180 | 181 | All regular and honorary members in good standing shall have one vote each to be cast during attendance at any General or Special Assembly. Electronic participation and voting shall only apply as valid if the member can be clearly identified. 182 | 183 | Supporting members in good standing will have a number of votes determined by their supporting membership level. The supporting membership levels and the associated number of votes shall be determined by the Board of Directors annually. 184 | 185 | Each member may vote only on their own behalf. 186 | 187 | In the case of a tied vote during an Assembly, the Chair of the Assembly shall cast the deciding vote. 188 | 189 | 190 | ### Art. 11 - Board of Directors 191 | 192 | The Board of Directors (also referred to as the Board) consists of the President, Vice President, Actuary, Treasurer, and at least two other Board members. 193 | 194 | 195 | ### Art. 12 - Duties of the Board 196 | 197 | The Board of Directors shall manage the affairs of the Mage-OS Association, in compliance with these statutes. 198 | 199 | In particular, the Board shall be responsible for: 200 | 201 | 202 | 203 | * External representation of the Mage-OS Association 204 | * Preparation of the business of the General Assembly 205 | * Execution of the decisions of the General Assembly 206 | * Approval of the Association budget, as submitted by the Treasurer 207 | * Drawing up and reviewing the annual financial statement 208 | * Strategy of the Mage-OS Association 209 | * Staffing of the Board duties 210 | * Deployment of committees and individual persons without decision-making authority for special tasks 211 | * Definition of the application procedure for project contributions 212 | * Reviewing project applications, in line with Association statutes and interests 213 | * Verification of the approved projects 214 | * Handling matters of membership status 215 | * Deciding on other matters of particular significance 216 | 217 | The Board of Directors shall issue Rules of Procedure, and shall regulate its tasks and division of responsibility therein. 218 | 219 | Each year, the Board of Directors shall prepare an annual report concerning its activity for the General Assembly. 220 | 221 | 222 | ### Art. 13 - Duties of the Board members 223 | 224 | 225 | #### A - President 226 | 227 | The President shall prepare the agenda and preside at all Board meetings of the Mage-OS Association; shall chair the Board of Directors; shall appoint chairs of committees, with majority approval of the Board; and shall monitor the Association activity within the framework of resolutions of the General Assembly and of the Board of Directors. 228 | 229 | 230 | #### B - Vice President 231 | 232 | The Vice President shall assist the President, and preside at meetings in the absence of the President. 233 | 234 | 235 | #### C - Actuary 236 | 237 | The Actuary shall keep minutes and written records of majority and minority opinions expressed at all meetings; shall be responsible for all correspondence of the Mage-OS Association; and shall make records of the Association available for inspection for any proper purpose in a reasonable time. 238 | 239 | 240 | #### D - Treasurer 241 | 242 | The Treasurer shall be accountable for all funds, and shall give an accounting at each general assembly; shall receive, safe keep, and disburse the Mage-OS Association funds, in accordance with these statutes; shall maintain records of finances and expenditures for auditing and budgetary purposes; and shall prepare and present the annual budget to the Board. 243 | 244 | 245 | ### Art. 14 - Election of Board members and term of office 246 | 247 | Only regular and honorary members of the Mage-OS Association can be elected to the Board. Re-election is permitted. The Board shall have a minimum of six and a maximum of nine members. 248 | 249 | The term of office for the Board of Directors is two years, with each year starting July 1st. 250 | 251 | The inaugural Board of Directors is selected by the founding members. Four of the inaugural board members will be selected by the Board to have a term of three years. This will serve to ensure continuity via rolling board member replacement in the future. 252 | 253 | At the end of each term of office, elections for vacated seats of the Board of Directors will be held during the General Assembly. 254 | 255 | Every member of the Mage-OS Association may nominate themselves or another member for candidacy in the Board election. Nominees must confirm their candidacy in advance. Written notice of proposed Board candidates must be submitted to the Board no later than seven days before the General Assembly. Nominees may apply for a particular role in the Board of Directors. The Board of Directors may be elected during the General Assembly, or prior to the General Assembly by online voting. In this case, members must be granted a reasonable advance term for the announcement of Board candidates. 256 | 257 | The outcome of the election shall be decided by counting the votes received by the candidates. In case of tie votes for excess candidates, there shall be a second ballot; in case of another tie vote, the decision will be made by lot. 258 | 259 | The election and assignment of functions (president, vice president, actuary, and treasurer) shall be performed during or prior to the General Assembly, before the start of a new term of office, by a simple majority of the attending members. 260 | 261 | Candidates for the office of president must have held a position on the Board of Directors previously. 262 | 263 | Termination of Mage-OS Association membership also terminates the office of a Board of Directors member. 264 | 265 | In the case of by-elections during the term of office, the newly elected Board member completes the predecessor’s term of office. Instead of by-elections, the Board of Directors may also ask the next ranking candidate from the previous election whether they want to move up. If more than three Board members step down during a term of office, new elections must be held for all vacated positions via a Special Assembly. 266 | 267 | Intent to leave the Board of Directors must be declared in writing. In this case, the obligations to the Association for the current year of membership must be fulfilled. 268 | 269 | In the event that a Board of Directors member fails to uphold their duties or is otherwise absent from Board activities for a period of 30 consecutive days without notice, the Board may vote to remove the office and responsibilities of that member. In that event, the removed member’s position in the Board of Directors shall be considered vacant. 270 | 271 | If a member of the Board of Directors resigns during their term, or in the event a position in the Board of Directors is vacant, the other members of the Board of Directors take over the responsibilities until the position is filled. 272 | 273 | 274 | ### Art. 15 - Quorum, circular resolutions, decision of the President 275 | 276 | Meetings of the Board of Directors shall be convened by the President of the Board, as often as business matters may require. 277 | 278 | The Board of Directors shall have a quorum if at least four of the members of the Board are present for a meeting. 279 | 280 | The President can call for circular resolutions. A circular resolution shall be valid only with the unanimous vote of all members of the Board. 281 | 282 | The Board of Directors should strive for consensus in its decisions. The Board shall decide matters through a majority vote of the members of the Board present, unless otherwise specified in the statutes. If a vote is tied, the President shall cast the deciding vote. 283 | 284 | On request of a member of the Board of Directors, a vote may be conducted by secret ballot. Otherwise, all resolutions shall be recorded in the meeting minutes. Each member of the Board shall be entitled to provide a minority opinion to be included in the minutes. 285 | 286 | 287 | ### Art. 16 - Signature policy 288 | 289 | A joint signature of two members of the Board of Directors shall be required. 290 | 291 | The President, or Vice President, or Treasurer, together with an additional member of the Board, shall sign in each case. 292 | 293 | 294 | ### Art. 17 - Business Control Committee 295 | 296 | The Business Control Committee shall consist of two members. The term of office of the Business Control Committee shall be two years. Election shall occur through the General Assembly. Re-election is permitted. 297 | 298 | Only members of the Mage-OS Association can be elected to serve as members of the Business Control Committee. Members may not serve on the Business Control Committee while also serving on the Board or otherwise receiving Association funds. 299 | 300 | Termination of membership in the Mage-OS Association shall also terminate the office of a member of the Business Control Committee. 301 | 302 | In the case of by-elections during the term of office, the newly elected member of the Business Control Committee shall complete the term of office of the predecessor. In even years the first half of the members of the Business Control Committee shall be elected, in odd years the second half of the members shall be elected. 303 | 304 | The Business Control Committee shall be entitled to review all project loans for expenditure agreement with the loan application, achievement of the cited objectives, and cost-efficient project fulfillment. It shall report to the Board of Directors quarterly and shall report to the General Assembly annually in writing. 305 | 306 | The Business Control Committee supervises the activities of the Association. In particular, it can, depending on the needs, appoint an external auditing company to examine both the financial statements of the association and other accounting documents. The Business Control Committee also reviews the books of the Association and shall publish annually a report on the audit of those books. 307 | 308 | The Business Control Committee shall issue Rules of Procedure and shall regulate its tasks and division of responsibility therein. 309 | 310 | 311 | ### Art. 18 - Other committees 312 | 313 | The Board of Directors shall be entitled to use advisory committees or individual persons without decision-making authority for special tasks. 314 | 315 | Deployment of a new committee requires a written request of a Board member, including justification, scope of the committee's responsibilities, and proposed members of committee. This will be voted by resolution of the Board. The board may accept the proposed members or appoint its own from among members of the Association. 316 | 317 | A committee can request changes to its members and chair. This is subject to approval by the Board. 318 | 319 | 320 | ### Art. 19 - Conflicts of interest 321 | 322 | Any time a Board member has a financial or personal interest in a matter coming before the Board of Directors, the member and Board must ensure that: 323 | 324 | 1. The interest of that Board member is fully disclosed. 325 | 2. The interested Board member may not vote or lobby on the matter, or be counted in determining the existence of a quorum, at a meeting of the Board of Directors at which such matter is voted upon. 326 | 3. Any transaction in which a Board member has a financial or personal interest shall be voted on if determined to be in the best interests of the organization, by members of the Board who do not possess that financial or personal interest in the transaction. 327 | 4. Any payments to an interested Board member shall be reasonable and not exceed fair market value. 328 | 5. The minutes of meetings at which such votes are taken shall record the disclosure, abstention, and rationale for approval. 329 | 330 | All members of the Board, committees, and all persons employed directly or by grants or loans, must avoid any appearance of a conflict of interest with the Association in their behavior and actions. In the event of a significant or persistent conflict, the Board may rule that such person must take actions to mitigate or resolve that conflict. If the person does not do so within 30 days of notification, they must end their role with the Association. 331 | 332 | 333 | ## Finances 334 | 335 | 336 | ### Art. 20 - Fiscal year 337 | 338 | The fiscal year of the Association starts January 1st. 339 | 340 | 341 | ### Art. 21 - Membership year 342 | 343 | The membership year shall apply individually for each individual member. It shall start upon payment of the annual membership dues. 344 | 345 | 346 | ### Art. 22 - Funds 347 | 348 | The Mage-OS Association procures its funds from: 349 | 350 | 351 | 352 | * Membership fees, and other fees for joining the Association; 353 | * Donations, bequests and inheritances, and funds derived from public generosity; 354 | * Grants, subsidies, shares, and deposits; 355 | * Income from assets of the Association, and income from its own activities. 356 | 357 | Membership fees shall be determined annually by the Board of Directors, and such changes will be updated annually in the Mage-OS Association’s policies. 358 | 359 | In exceptional situations, the Board of Directors may exempt a member from fees, or postpone the date of their payment. 360 | 361 | At any time, members and third parties shall be entitled to inject funds that the Mage-OS Association can freely dispose of for the achievement of its objectives. 362 | 363 | The Mage-OS Association's expenditures shall be specified in the budget. The budget shall show the appropriated amounts per legal transaction. The budget shall be prepared by the Treasurer and decided on by the Board of Directors. Budget applications shall be formally reviewed by the Treasurer. 364 | 365 | In exceptional cases, the Board of Directors can decide on budget excesses of a maximum of 5% of the total budget amount. 366 | 367 | 368 | ### Art. 23 - Compensation 369 | 370 | Reasonable compensation can be granted to members of the Board of Directors and of the Business Control Committee. This must be specified in the budget and approved by the General Assembly. 371 | 372 | 373 | ### Art. 24 - Exclusive liability of the Mage-OS Association assets 374 | 375 | For liabilities on the part of the Mage-OS Association, its assets shall be exclusively liable. The individual member shall only be obligated to pay their annual membership fees. 376 | 377 | 378 | ### Art. 25 - Claims to assets 379 | 380 | Members who leave or are terminated from the Mage-OS Association shall lose any claim to Association assets. 381 | 382 | 383 | ### Art. 26 - Transfer of assets 384 | 385 | Mage-OS Association shall not transfer ownership of any non-financial assets, rights, or other intellectual property to the exclusive control of any entities or individuals, except by the affirmative vote of two-thirds of members present at a General or Special Assembly. The resolution must enumerate all specific assets or rights to be transferred by the vote, and any terms that the proposed transfer is subject to. 386 | 387 | 388 | ## Final provisions 389 | 390 | 391 | ### Art. 27 - Statutory obligation 392 | 393 | Each member shall be given a copy of these statutes. At admission to the Mage-OS Association, a member shall acknowledge these statutes and shall be obligated to comply with and honor the resolutions and directives of the responsible governing bodies of the Association. 394 | 395 | 396 | ### Art. 28 - Statutory amendments 397 | 398 | These statutes can be amended by resolution during a General Assembly. Such resolutions must be approved by the affirmative vote of two-thirds of the members present. 399 | 400 | 401 | ### Art. 29 - Dissolution or Merging of the Mage-OS Association 402 | 403 | To dissolve the Mage-OS Association, the action must first be proposed and approved by circular resolution of the Board of Directors. Thereafter, the board must convene a General or Special Assembly to present and vote on the action. Two-thirds of voting members must be present at the Assembly convened for this purpose. The dissolution shall be approved if three-fourths of the voting members present vote in favor of the action. 404 | 405 | If two-thirds of the voting members of the Mage-OS Association are not present, after 30 days a second Assembly shall be convened. The dissolution shall be approved if three-fourths of the voting members present vote in favor of the action. 406 | 407 | Unless otherwise decided by the Assembly, the President and the Treasurer shall be jointly authorized liquidators. Any assets remaining after liquidation and settlement of obligations shall be donated to a charitable organization determined by the Assembly. These provisions shall also apply if the Association is dissolved for a different reason or loses its legal capacity. 408 | 409 | Mergers shall follow the same procedure as for dissolution of the Association, without any liquidation of assets thereafter. The details of the proposed merge must be finalized and approved by circular resolution of the Board of Directors, prior to calling for an Assembly. 410 | 411 | 412 | ### Art. 30 - Place of jurisdiction 413 | 414 | The place of jurisdiction for all disputes affecting the membership shall be the court responsible for the registered office of the Association. 415 | 416 | ---- 417 | 418 | Last updated: June 1st, 2022 419 | Approved by founding members: Alessandro Ronchi, Ignacio Riesco, John Hughes, Laura Folco, Maciej Kalkowski, Peter Jaap Blaakmeer, Ryan Hoerr, Simon Sprankel, Thien-Lan Weber, Vinai Kopp, Wouter Steenmeijer 420 | 421 | *Credit: Much of the document and organizational structure are derived from the Typo3 Association bylaws, with permission. Article 19 uses materials published for non-profits by Hurwit & Associates.* 422 | --------------------------------------------------------------------------------