<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jan Dvorak IV. on Medium]]></title>
        <description><![CDATA[Stories by Jan Dvorak IV. on Medium]]></description>
        <link>https://medium.com/@storytellercz?source=rss-480ffd4d4c95------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ERBIIeyeCfnnVKX-xMKqQg.jpeg</url>
            <title>Stories by Jan Dvorak IV. on Medium</title>
            <link>https://medium.com/@storytellercz?source=rss-480ffd4d4c95------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:55:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@storytellercz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing Meteor Work Groups]]></title>
            <link>https://blog.meteor.com/introducing-meteor-work-groups-fb307413245a?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb307413245a</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[meteorjs-development]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Wed, 11 Sep 2024 18:46:15 GMT</pubDate>
            <atom:updated>2024-09-11T18:52:02.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*-YhHtlDXaI71X4GWnVxpDg.png" /></figure><p>Meteor Software is thrilled to announce the formation of work groups within the Meteor.js community to help drive the platform&#39;s future, focus on key features, and ensure long-term improvements. These groups will consist of community leaders, contributors, and stakeholders committed to enhancing Meteor.</p><h3>Two Types of Work Groups</h3><p>To better address both ongoing needs and specific goals, we are introducing two types of work groups:</p><p><strong>Standing Work Groups</strong></p><p>These groups focus on overarching themes or sets of features that require ongoing maintenance and improvements. Examples of topics they will cover include:</p><ul><li>Security</li><li>User Accounts</li><li>Build Tool</li><li>Testing</li></ul><p>Standing work groups will operate continuously to ensure their areas of responsibility remain stable, secure, and up to date. Their work may include adding new features, patching issues, and improving existing systems over multiple releases.</p><p><strong>Goal-Oriented Work Groups</strong></p><p>These groups are created with specific goals in mind, usually tied to items on the Meteor roadmap. They will work toward achieving a defined goal with a clear deadline, typically aligned with a specific release. Once their goal is accomplished, these work groups will be dissolved, and responsibility for maintaining their contributions will be transitioned to a standing group. Examples of potential tasks include:</p><ul><li>Adding roles and permissions systems</li><li>Implementing MongoDB change streams</li><li>Enabling database migrations</li><li>Integrating new bundlers such as Vite</li></ul><h3>Group Structure and Participation</h3><p>Each work group will consist of:</p><ul><li><strong>A Meteor Software (MS) representative</strong>: A developer from MS will be an active coding member of each group. They will have merge permissions for PRs and oversee releases in goal-oriented groups. This role underscores MS’s hands-on commitment to the project’s success.</li><li><strong>Critical stakeholders</strong>: These include original package owners (if integrating community packages), creators of alternative solutions, and key community members who have made notable contributions in the given field. Their involvement ensures the integration of the best possible version of the solution.</li><li><strong>Contributors</strong>: Reliable, recognized community members who will work on major parts of the project, such as documentation, tests, and core feature development.</li><li><strong>Stakeholders from relevant companies</strong>: Organizations that depend on specific features and can offer critical feedback and testing support may also join.</li></ul><p>It’s important to note that <strong>everyone is still encouraged to contribute</strong>. The creation of these work groups is meant to provide leadership and focus on topics crucial to Meteor’s future without restricting broader community involvement.</p><h3>Work Group Leadership and Public Involvement</h3><p>Each group will have a designated leader responsible for coordinating meetings and communicating progress to the wider community. With the exception of security-related discussions, all work group meetings will be <strong>public</strong>. This ensures community members can observe the decision-making process, offer feedback, and contribute ideas.</p><h3>Announcing the first Work Groups</h3><p><strong>Goal-Oriented Work Group: Roles (Meteor 3.1)</strong></p><ul><li>Task: Integrate the community-developed alanning:roles package into Meteor core.</li><li>Expected Release: Meteor 3.1</li><li>Key Members: Denilson Silva, Jan Dvorak, Jan Kuester</li><li>Transition: Once the goal is met, this work group will evolve into a standing group: <strong>Accounts</strong>.</li></ul><p><strong>Standing Work Group: Accounts (after Meteor 3.1 release)</strong></p><ul><li>Task: Maintain and enhance Meteor’s accounts system, ensuring it remains secure, user-friendly, and feature-rich. Possible future features include support for Passkeys and Apple OAuth.</li><li>Ongoing maintenance: The Accounts group will be responsible for future improvements and new feature development related to user authentication.</li></ul><p><strong>Standing Work Group: Build Tool</strong></p><ul><li>Headed by: Nacho Codoner</li><li>Task: Continuously enhance Meteor’s build tools to improve developer experience and performance.</li></ul><p><strong>Goal-Oriented Work Group: MongoDB Change Streams</strong></p><ul><li>Headed by: Leonardo Venturini</li><li>Task: Add support for MongoDB change streams in Meteor, targeting a future major release.</li></ul><h3>Get Involved</h3><p>In the near future, we will release a sign-up form for volunteers who are interested in contributing to these work groups. Whether you want to help shape the future of Meteor or just keep tabs on key developments, we encourage everyone to participate.</p><p>Note that we will be choosing people to join these work groups so it is good if you have some work history that we can reference. Note that there are also non-programming tasks like helping improving documentation. For company representatives and important determination will be if your company supports open source developers in the Meteor ecosystem.</p><p>This initiative will help streamline decision-making, prioritize important features, and ensure that each release brings exciting new advancements to Meteor.js. We look forward to seeing the positive impact these groups will bring!</p><p>Stay tuned for more updates and ways to get involved!</p><p>PS: Join us on <a href="https://youtube.com/live/wTGcp-eqCh4?feature=share">Meteor Dispatches this Friday</a> for a Q&amp;A session!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb307413245a" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/introducing-meteor-work-groups-fb307413245a">Introducing Meteor Work Groups</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The why and the vision of Literary Universe]]></title>
            <link>https://medium.com/@storytellercz/the-why-and-the-vision-of-literary-universe-4da73d8ed0fd?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/4da73d8ed0fd</guid>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Mon, 11 Sep 2023 06:55:36 GMT</pubDate>
            <atom:updated>2023-09-11T06:55:36.533Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2010, I entered university with a primary focus, I wanted to learn all the stuff that I needed to build a community website for writers. This was based on my experience with a site where young people like me started writing, shared their work and created a fun community. Few years earlier the website shut down and I wanted to recreate it and make it even better.</p><p>There were additional motivations that crystallized during my studies and as the first iterations of the website were built. These were primarily technical aspects with which I won’t bore you here. At that time I was already dissatisfied with the quality of content that traditional power houses of Western culture were producing. This dissatisfaction has only increased since then. As a technical person I turned my attention towards the technical aspects. As a science fiction and fantasy fan my focus was always on large story universes. Think <em>Star Gate</em>, <em>Star Wars</em>, <em>The Expanse</em>, <em>The Lord of the Rings</em>, <em>Dune</em>, <em>Gundam</em> and so on. But when reading and writing the details, the encyclopedia of the universe lives completely separately. This was the first realization I had and at that moment my desire to create a publication website where writers just publish their content and create community evolved into something greater and it didn’t stop there.</p><p>After a few iterations on how to bring the universe encyclopedia together with the stories I had a working demo and could focus on other things. Back in 2016 the publishing industry was already adjusting to the rise of e-books and audio books were coming on the scene. In East Asia the Light Novel format manifested itself on the Internet as Web Novels and became the first step for many aspiring authors. <em>Patreon</em> platform showed a new model for people to support their favorite creators and many inventions were coming, but at the cost of increasing challenges and overhead.</p><p>Even if there was a solution for a new challenge like <em>Patreon</em> in the end one ends with multiple tools and websites to use. For writers who should be primarily focused on creating great stories, the bar for entry keeps on rising unless they get lucky and get a solid publishing deal or get noticed on mass platforms like <em>Wattpad</em>. From my first internship I became passionate about small businesses and creators and my vision became to create a platform where even the small writers can make something if they create a good story. It might not be enough to go full-time (maybe over time), but at least it might be something to make life easier and motivate me to write better stories. And don’t even get me started on the legal issues, revenue splitting and other aspects of what is essentially a business (after all those creating stories, art and music also need to eat). As such the all-in-one platform concept was born with the name Literary Universe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*2eMsMaEazrY-KShs4kio5A.png" /><figcaption>Literary Universe logo</figcaption></figure><p>Now to the present day, as sadly I was able to return to it in a larger capacity only recently. As I’m toiling away on the Literary Universe and preparing it for introduction to a wider audience a major new challenge arises, Artificial Intelligence. At first a fun toy that many laughed at and said it would take decades before it was any good, but these voices are growing more silent. Even domains which seemed untouchable a few years ago like programming and the creative fields are now feeling endangered. From what I already talked with writers it already has had a negative impact on literary contests where submissions were swarmed by AI generated stories and publishers have to contend with these as well. Many things to talk about in this area (already <a href="https://www.literaryuniverse.com/blog/storyteller/post/Yh3EPe55YyXwcvGbP">started</a> a bit, but more to come), but I believe that in this crisis there is tremendous opportunity. Even AI will need human input or it will start on a deadly spiral at which end it will generate garbled nonsense like we have <a href="https://www.cnet.com/tech/services-and-software/what-happens-when-ai-bots-invent-their-own-language/">seen in the past</a> as it only has its own content to draw new content from.</p><p>The opportunity here is that AI can provide assistance to writers. While the technology can be used even today to already generate impressive works, human editing is often required, but that too will decrease as the technology evolves. But at the end of the day we will need human generated creative works. Not just for the AI not to degenerate, but for us as a species, less we degenerate as well. With this the demand for high quality content is going to increase. That is going to make it harder for new authors to make it, but this is where AI can help them the most. As an assistant AI will be able to point out issues with things like dialog flow, plot holes and even offer suggestions based on analysis of similar works, in the most extreme scenario I can imagine it writing some some encyclopedia entries from based on the story that the author has written to save author some time. Due to the interconnection of all the tools in the Literary Universe the AI will have all the necessary data to go beyond general suggestions that can be already provided these days and will be able to offer assistance through the entire creative process. But at the end of the day it needs to stay as an assistant, or authors will become nothing more than glorified AI query writers.</p><p>The vision of Literary Universe has evolved from an all-in-one platform for creative writing, publishing and community building to include all the other tools needed in the publishing business like legal arrangements, more revenue to writers and sharing it with everyone involved, translations, author blogs, fan clubs, education and now looking towards the future with harnessing the power of AI without losing the human element and creativity.</p><p>So where are things now? Literary Universe has the basic things down. Next major feature on our to-do list are Fan Clubs, followed by selling stories. In the meantime a new theme is being implemented. We are a small and at this point still bootstrap operation (would like to keep it that way if you would support us). If this is something that interests you, <a href="https://www.literaryuniverse.com/">take a look</a>, give us <a href="https://www.literaryuniverse.com/feedback">feedback</a>, <a href="https://www.literaryuniverse.com/roadmap">check out our roadmap</a> and <a href="https://www.literaryuniverse.com/plans">please subscribe</a> to one of our plans to support us so that we can reach our vision faster. Feel free to use promo code STORYTELLERSTART to get one month free on any of the plans.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4da73d8ed0fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Impact new keynotes, sponsors & trade show]]></title>
            <link>https://medium.com/@storytellercz/impact-new-keynotes-sponsors-trade-show-a2c37ca743d1?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2c37ca743d1</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Wed, 14 Sep 2022 12:13:26 GMT</pubDate>
            <atom:updated>2022-09-14T12:18:04.457Z</atom:updated>
            <content:encoded><![CDATA[<p>Impact is quickly approaching and with that we have more announcements to share!</p><h3>Keynotes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/112/0*DUwI8JUh_VQJP_4p.png" /></figure><h3>Alim Gafar</h3><p>Alim is most recently known as <em>Vice President of Strategy &amp; Community Growth</em> at Meteor Software, but he has a long history with Meteor as being the main organizer of the Meteor NYC meetups among other involvement. For Impact, Alim will <a href="https://impact.meteor.com/meetings/virtual/vD5gz3HtED5tutSJz">speak about building up the Ambassador program</a> and what is next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/112/0*7jG6nJJq3Dn9DNMR.png" /></figure><h3>Gabriel Engel</h3><p>Gabriel is the founder and CEO fo Rocket.chat, first major Meteor FOSS projects. He will give a <a href="https://impact.meteor.com/meetings/virtual/ooefhCSHHzah5op5d">keynote</a> about how Rocket.chat has grown with Meteor over the seven years since it was originally conceived in 2015.</p><h3>New Gold sponsor</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*LVNF2NyyxEeUCFKw.png" /></figure><h3>Vazco</h3><p>If you have been around Meteor for while you have no doubt heard about <a href="https://vazco.eu/">Vazco</a>. The Polish company that builds amazing products with Meteor and gives back to the community. Vazco is back this year as a Gold sponsor of Impact.</p><h3>Trade show</h3><p>Finally the last addition that I will talk about in this post are trade shows. In many conferences there are some sorts of area where vendors, sponsors or sellers get to setup their booth and interact with the attendees, be it to sell their wares, scout for talent or spread awareness for their project. At Impact we will be doing two virtual <a href="https://impact.meteor.com/trade-show/organizations">trade shows</a>.<br>One on Thursday and one on Friday where attendees can visit the booths of companies and interact with company representatives. Following that there will be period of 4 hours for additional one on one meetings.</p><p>That is it for today! Stay tuned for more updates soon!</p><p>In the meantime, there is still time to <a href="https://impact.meteor.com/host-a-talk">host a talk at Impact</a> or have your company <a href="https://impact.meteor.com/sponsor">become a sponsor</a>!</p><p>In any case, you should definitely <a href="https://impact.meteor.com/sign-up">sign-up for Impact</a>!</p><p>If you like my work, please support me on <a href="https://github.com/sponsors/StorytellerCZ">GitHub Sponsors ❤️</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2c37ca743d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Meteor 2.5 with Cordova 10, accounts-passwordless, and much more!]]></title>
            <link>https://blog.meteor.com/announcing-meteor-2-5-with-cordova-10-accounts-passwordless-and-much-more-1848fa61e313?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/1848fa61e313</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[meteor]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Tue, 26 Oct 2021 17:19:01 GMT</pubDate>
            <atom:updated>2021-10-26T17:19:01.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUFmWO9eT5TlaCiXEwyQ1Q.png" /></figure><p>With <a href="https://impact.meteor.com/">Meteor Impact</a> we also have for you a new Meteor release!</p><h3>Cordova 10</h3><p>Users of Cordova can now enjoy the latest Cordova v10 for Android, which now enables AndroidX. Be aware that if you use any Cordova-plugin that depends on or uses any old support library, you need to include the Cordova-plugin-androidx-adapter for Cordova-plugin; otherwise, you will get build errors.</p><p>In addition to the Cordova upgrade, you’ll find that mobile packages like mdg:camera and mdg:geolocation have been updated with new features and are compatible with this Cordova upgrade.</p><h3>accounts-passwordless</h3><p>Ongoing work on the accounts system brings us a new package in this release, accounts-passwordless. As the name suggests, this package adds the ability for the user to sign-up/in without the need for a password. Only an e-mail address is needed, which receives a code that the user can enter on the sign-in page or use a link to get signed in without that hassle. It’s straightforward to tap into this package and change instead of sending codes to a phone number. Check out <a href="https://www.youtube.com/watch?v=M1H7p03kQcw">Filipe’s &amp; Renan’s stream</a> that covers these two topics in detail.</p><p>Other packages have been updated to be aware of this package as well like accounts-ui.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*EHssB0zC_EG22Mm3.png" /></figure><p>And new packages were created like <a href="https://atmospherejs.com/quave/accounts-passwordless-react">quave:accounts-passwordless-react</a>, with this package you can add password less authentication with a few lines of code:</p><pre>import React from &#39;react&#39;;<br>import { useHistory } from &#39;react-router-dom&#39;;<br>import { Passwordless } from &#39;meteor/quave:accounts-passwordless-react&#39;;<br><br>export const Access = () =&gt; {<br>  const history = useHistory();<br><br>  const onEnterToken = () =&gt; {<br>    history.push(&#39;/&#39;);<br>    openAlert(&#39;Welcome!&#39;);<br>  };<br>  <br>  return (<br>    &lt;Passwordless<br>      onEnterToken={onEnterToken}<br>    /&gt;<br>  );<br>};</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*MJTUuHlGHntj71RBYTD8Ug.png" /></figure><p>It’s possible to use this package with SMTP configuration in Meteor. Still, if you prefer to use Postmark as a provider using their API, there is a new package <a href="https://github.com/quavedev/email-postmark">quave:email-postmark</a> that replaces the transport layer of Meteor by Postmark API.</p><p>If you prefer Text messages (SMS) instead of emails, there is also a new package for that <a href="https://github.com/quavedev/accounts-passwordless-sms-twilio">quave:accounts-passwordless-SMS-Twilio</a> using Twilio.</p><p>These last three packages are community packages; feel free to use their code as an inspiration to create new integrations, for example, password-less UI for Vue.js or Svelte. Or new provider implementations for SMS or Email.</p><h3>Accounts configs</h3><p>Continuing on accounts improvements new way of setting config options has been added. Till now, you had to set Accounts manually.config, now you can define these settings in your Meteor config for them to be automatically set. You can do that under Meteor.settings.packages.accounts-base; the same applies for service configuration. You can define OAuth service options in Meteor settings. They will be added to the database automatically without manually creating upsert functions like you had to till now. A sample config for Weibo would look like this:</p><pre>{<br>  &quot;packages&quot;: {<br>    &quot;service-configuration&quot;: {<br>      &quot;weibo&quot;: {<br>        &quot;loginStyle&quot;: &quot;popup&quot;,<br>        &quot;clientId&quot;: &quot;1292962797&quot;,<br>        &quot;secret&quot;: &quot;75a730b58f5691de5522789070c319bc&quot;<br>      }<br>    }<br>  }<br>}</pre><p>Make sure to check out the documentation of the OAuth package for the correct keys to use.</p><h3>HMR updates</h3><p>Per our usual round of updates, we have some significant updates related to hot module replacement! HMR is now available on all architectures and in legacy browsers.</p><p>Also, we fixed a delay that we had in the first change detection; it could take up to 5 seconds to detect the first change, but this is now resolved, and the detection will be immediate.</p><h3>Node 14.18.1</h3><p>Node has been updated to the latest v14, featuring <a href="https://nodejs.org/en/blog/vulnerability/oct-2021-security-releases/">October 12th 2021 security release</a>. This means that since Meteor 2.5 this includes Node <a href="https://nodejs.org/en/blog/release/v14.18.0/">14.18.0</a> and <a href="https://nodejs.org/en/blog/release/v14.18.1/">v14.18.1</a>.</p><h3>Documentation and Guide in Meteor repository</h3><p>Along with all these updates, we have been hard at work re-organizing Meteor repositories. The most notable is that Documentation and Guide are now part of the <a href="https://www.github.com/meteor/meteor">main Meteor GitHub repository</a>. This will make it easier to make complete Pull Requests with documentation and Guide changes.</p><p>We have also unified many NPM packages repos, as they are used in Meteor it makes more sense to keep them in the same repository. Update today!</p><p>You can update to Meteor 2.5 today by running</p><pre>meteor update --release 2.5</pre><p>to enjoy these and other improvements and fixes in the latest addition to Meteor!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1848fa61e313" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/announcing-meteor-2-5-with-cordova-10-accounts-passwordless-and-much-more-1848fa61e313">Announcing Meteor 2.5 with Cordova 10, accounts-passwordless, and much more!</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meteor Community Survey 2021 is open!]]></title>
            <link>https://medium.com/@storytellercz/meteor-community-survey-2021-is-open-edacfb429338?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/edacfb429338</guid>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[meteorjs]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Fri, 24 Sep 2021 09:00:10 GMT</pubDate>
            <atom:updated>2021-09-24T09:00:10.864Z</atom:updated>
            <content:encoded><![CDATA[<p>It is that time of the year again! Meteor Community Survey has been open!</p><p>This is the third survey in the series. This year there has been improvement to questions like location to list countries rather than allow write-in which requires a lot of clean-up to generate a map.</p><p>The biggest and most noticeably addition is the increase of questions related to Galaxy. While centered on Galaxy this is to get a general idea of what people are interested in hosting and what they are missing on Galaxy.</p><p>The survey is not open until October 20th. The results will be presented at <a href="https://impact.meteor.com/">Meteor Impact</a> and afterwards the data will be open for everyone to explore (after anonymizing them of course).</p><p>Please share the survey with all the Meteor developers you know so that we can get as many responses as possible!</p><p><a href="https://docs.google.com/forms/d/e/1FAIpQLSdafmJJhxpOprNttcRJVwzmrZlSbwYktxCCO0yBijgEP9GvoA/viewform?usp=sf_link">Take the survey</a></p><p><a href="https://forums.meteor.com/t/meteor-community-survey-2021/56677?u=storyteller">Meteor forums topic</a></p><p>If you like my work, please support me on <a href="https://github.com/sponsors/StorytellerCZ">GitHub Sponsors ❤️</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edacfb429338" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Meteor 2.4 And The New Installer]]></title>
            <link>https://blog.meteor.com/announcing-meteor-2-4-and-the-new-installer-254c5f8f39f?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/254c5f8f39f</guid>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[apollo-server]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[meteorjs]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Mon, 20 Sep 2021 19:15:18 GMT</pubDate>
            <atom:updated>2021-09-20T19:15:18.400Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Announcing Meteor 2.4" src="https://cdn-images-1.medium.com/max/1024/1*ACjCB7iSB59ZGrf3ksxoMA.png" /></figure><p>Version 2.4 brings you new features, performance improvements, and a new installer.</p><p>You probably know that Meteor has had a few different installers during the years. Our most recent update allowed Meteor users on Windows to use NPM to install Meteor.</p><p>Now we are enabling this option for Unix &amp; macOS, and we’re happy to announce the new way to install Meteor:</p><pre>npm install -g meteor </pre><p>Yes, it’s that simple. Just an easy npm install and you are ready to go. Read more about this installer in our <a href="https://docs.meteor.com/install.html">docs</a>.</p><p>Continue reading for other news in Meteor 2.4.</p><h3>Windows improvements</h3><p>Some Meteor commands were hanging on Windows and we finally isolated the problem. This problem was caused by the native file watcher library that we’re using, but in many cases, this watcher was not necessary.</p><p>One case that was happening very often was in the meteor create command, specifically after the first install. Now, this command is not using this library and meteor create shouldn’t hang anymore in Windows.</p><p>We’re researching another library to fix this problem in the long term but for now, we should be good with this workaround.</p><h3>New Collection method: createIndex</h3><p>Following the deprecation and <a href="https://docs.mongodb.com/manual/reference/method/db.collection.ensureIndex/#mongodb-method-db.collection.ensureIndex">removal of </a><a href="https://docs.mongodb.com/manual/reference/method/db.collection.ensureIndex/#mongodb-method-db.collection.ensureIndex">ensureIndex method in MongoDB 5</a>, we are making the first step towards this MongoDB release by deprecating our own _ensureIndex method on collections and replacing it with createIndex.</p><p>There are no changes in the behavior so you can use createIndex as you were using _ensureIndex before. Behind the scenes Collection _ensureIndex is using the same implementation as createIndex so both are safe to use.</p><h3>Email: custom transport and known services</h3><p>In version 2.2 of the <a href="https://atmospherejs.com/meteor/email">email</a> package, we are adding two new features.</p><p>First Email.customTransport, which allows you to override the sending functionality with your own handling. This way you can stop sending emails via SMTP that you set in MAIL_URL env var and instead use API provided specifically by the service you use. See how to use this with <a href="https://postmarkapp.com/">Postmark</a> below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2gpFYiKltKc0Lqbcbitizg.png" /></figure><p>As you have informed a customTransport Meteor is going to send all the emails using it. <a href="https://docs.meteor.com/api/email.html#Email-customTransport">Read the docs</a> for more details.</p><p>Second is the option to use Meteor.settings.packages.email to set options for sending using <a href="https://nodemailer.com/smtp/well-known/">known services</a> of <a href="https://nodemailer.com/">Nodemailer</a>. You just need to provide the name of the known service, user, and password in the settings and the package is going to take care of the rest.</p><p>Make sure to check over the updated <a href="https://docs.meteor.com/api/email.html">email documentation</a> for all the implementation details.</p><p>The MAIL_URL env var is still going to work and we have no plans to deprecate it.</p><h3>Runtime Performance Improvements</h3><p>The latest version of reify reduces the overhead of import statements and some uses of export ... from, especially when a module is imported a large number of times or re-exports a large number of exports from other modules.</p><p>The benefits are clear when working with huge libraries like @material-ui/icons, you can read more details in the PRs. <a href="https://github.com/benjamn/reify/pull/246">1</a>, <a href="https://github.com/benjamn/reify/pull/291">2</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2bEq7uvKHGQP_NnHsKnQuA.png" /></figure><p>This optimization opens the door for us to resume the work in <a href="https://github.com/meteor/meteor/pull/11164">Tree-shaking</a> as huge libraries are not a big problem for us in development anymore and Tree-shaking can now be enabled only for production builds.</p><h3>Publications Fine Tune</h3><p>Publications can now use different strategies in the way it uses the mergebox. You can tune the behavior so that you can better manage bandwidth usage and server-side memory. There are 3 strategies available SERVER_MERGE, NO_MERGE and NO_MERGE_NO_HISTORY to choose from.</p><p>Keeping it simple:</p><p>SERVER_MERGE: Default Meteor behavior, nothing new here.</p><p>NO_MERGE_NO_HISTORY: Should only be chosen for special use cases like send-and-forget queues.</p><p>NO_MERGE: Remembers only the IDs sent to the client and applies new rules when adding, updating, and removing documents into Minimongo.</p><p>These strategies are selected for each publication so you can have a mix of them in your app, choosing the best strategy for each scenario. It will be nice to see new ways to combine Publications emerging from the community now that we have different options available. Read all the details in <a href="https://docs.meteor.com/api/pubsub.html#Publication-strategies">the docs</a>.</p><h3>Vue 3 integration</h3><p>Since July we started to use GitHub <a href="https://github.com/meteor/meteor/discussions">Discussions</a> to discuss ideas and feature requests for Meteor.</p><p>At this moment the #1 discussion is the discussion about <a href="https://github.com/meteor/meteor/discussions/11521">Vue 3 integration</a> and we are happy to announce the first version of this integration!</p><p>If you want to help with testing the integration you can install the package, read the <a href="https://github.com/meteor-vue/meteor-vue3/tree/main/packages/vue3">docs</a> and give it a try:</p><pre>meteor add vuejs:vue3</pre><p>This release was possible because of our <a href="https://forums.meteor.com/t/team-up-to-create-the-new-vue-3-integration/53089/">amazing community</a>, led by <a href="https://github.com/Akryum/">Guillaume Chau</a>.</p><h3>Apollo server 3</h3><p><a href="https://www.apollographql.com/blog/announcement/backend/its-here-introducing-apollo-server-3/">New major version of Apollo server</a> has been released. For those starting a new project, we have upgraded our Apollo skeleton with the necessary changes so you can start your new Meteor Apollo project easily.</p><p>For those who are already running on Apollo server v2 and would like to quickly know how to upgrade, there is an <a href="https://dev.to/storytellercz/upgrading-to-apollo-3-in-meteor-in-3-steps-28pl">article how to</a> do so, but keep in mind that based on what features you are using, you might need to do much more work and as such you should consult the <a href="https://www.apollographql.com/docs/apollo-server/migration/">Apollo upgrade guide</a>.</p><h3>Runtime configuration hooks</h3><p>The latest webapp package now allows you to create a runtime config hooks that get called when runtime config is set or changes.</p><p>For example, in some cases, it is valuable to be able to control the __meteor_runtime_config__ variable that initializes Meteor at runtime.</p><p>There are occasions when a single Meteor server would like to serve multiple Cordova applications that each have a unique ROOT_URL. But there are two problems:<br>1. Meteor server can only be configured to serve a single ROOT_URL.<br>2. Cordova applications are build-time configured with a specific ROOT_URL.</p><p>These two conditions break autoupdate for Cordova applications. cordova-plugin-meteor-webapp will fail the update if the ROOT_URL from the server does not match the build time configured ROOT_URL of the Cordova application.</p><p>To remedy this problem webapp has now a few hooks for dynamically configuring __meteor_runtime_config__ on the server.</p><p>These are:</p><ul><li>WebApp.addRuntimeConfigHook</li><li>WebApp.addUpdatedConfigHook</li><li>WebApp.decodeRuntimeConfig</li><li>WebApp.encodeRuntimeConfig</li></ul><p>Read more in the <a href="https://docs.meteor.com/packages/webapp.html">docs</a>.</p><h3>Facebook OAuth login handler</h3><p>facebook-oauth now features a new login handler hook same as the one for Google package which should make it easier for you to retrieve data if you are using React Native and similar tools. <a href="https://github.com/meteor/meteor/pull/11603">Read more</a>.</p><h3>Typescript Upgrade</h3><p>Typescript upgrade to <a href="https://github.com/Microsoft/TypeScript/releases/tag/v4.3.5">v4.3.5</a> is a patch release with a bug fix for auto-imports in JSX components.</p><h3>And much more!</h3><p>There were many other smaller improvements and updates made for this release like updated dependencies for minifiers and bug fixes that are either part of this release or were released independently in their respective packages. Make sure to read the full <a href="https://docs.meteor.com/changelog.html">changelog</a> for a list of all the details and upgrade to Meteor 2.4 by running meteor update in your app directory!</p><p>If you have any questions for us, feel free to reach out in the Forums, or to support@meteor.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=254c5f8f39f" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/announcing-meteor-2-4-and-the-new-installer-254c5f8f39f">Announcing Meteor 2.4 And The New Installer</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meteor 2.3 has been released!]]></title>
            <link>https://blog.meteor.com/meteor-2-3-has-been-released-f9971464ed1e?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9971464ed1e</guid>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[meteorjs]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 13:10:03 GMT</pubDate>
            <atom:updated>2021-07-13T20:02:32.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Meteor 2.3.1" src="https://cdn-images-1.medium.com/max/1024/1*KZJia42_r4MBXEaWnpY1JA.png" /><figcaption>Announcing Meteor 2.3.1</figcaption></figure><h3>Announcing Meteor 2.3.1: Node 14, removal of deprecated APIs, improved HMR, and much more</h3><p>Meteor 2.3 &amp; 2.3.1 bring a lot of long-expected upgrades and improvements. It also has a small diet with the removal of long deprecated code in packages which allows us to more focus on the future.</p><h3>Node 14 upgrade</h3><p>The first major change in Meteor 2.3 is Node version upgrade to Node 14.17.3 from 12.22.1. This gets Meteor to the current LTS version of Node bringing updates in V8. Read the <a href="https://nodejs.medium.com/node-js-version-14-available-now-8170d384567e">release article of Node 14</a> for more information. Some of the improvements that are present in Node 14 like new JavaScript features (like <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining">optional chaining</a>) have been already available in Meteor.</p><p>Like with any Node upgrade this will require you to review your apps to see if your dependencies are compatible with the new version. You should remove your node_modules folder and install your dependencies via meteor npm install<em>.</em></p><p>As with any Node update, meteor-tool dependencies also got updated, with the most notably:</p><ul><li>npm updated to 6.14.13 to correlate with the Node update</li><li>fibers v5.0.0</li><li>promise v8.1.0</li><li>node-gyp v8.0.0</li><li>@babel/runtime v7.14.0</li><li>request v2.88.2</li><li>tar v2.2.2</li><li>sqlite3 v5.0.2</li><li>moment v2.29.1</li><li>underscore v1.13.1</li><li>optimism v0.16.1</li><li>@wry/context v0.6.0</li></ul><h3>Improved reload and HMR</h3><p>Zodern has been hard at work making incremental improvements and fixes for HMR, most notably improving tracking of which files are used by building plugins to know when it should do a complete rebuild, a faster client-only rebuild, or completely skip rebuilding after a file is modified. This should work with any file in any directory and for both files in the app and files in packages.</p><p>The most noticeable improvement is when modifying a file only used on the client. Meteor will only rebuild the client, even if the file is not inside imports or a <em>client</em> folder. This now removed the need to have an imports folder so that changes in the UI don’t restart the server. This was a bug introduced after the addition of meteor mainModule option in the package.json, and now it’s fixed!</p><p>On the experimental side, we are testing reducing time spent by the server (re)start in development by adding a cache for Reify. This optimization is on by default in development, if you want to have it in production you can enable it by setting the METEOR_REIFY_CACHE_DIR environment variable.</p><h3>Accounts packages breaking changes</h3><p>Accounts packages got many improvements in this release cycle. While most are minor improvements or changes there are few that required a major version bump for some of the packages. This major version bump will require action from all package maintainers that depend on accounts-base, accounts-password, and oauth packages to include the new range like this: api.versionsFrom([‘1.12’, ‘2.3’]) or api.use(‘accounts-base@1.0.1 || 2.0.0’) .</p><p>This is due to the removal of old APIs as described below, breaking of the enrollment workflow, and removal of SRP style password, all as described below.</p><p>Enroll account workflow has been separated from reset password workflow (the enrollment token records are now stored in a separate db field services.password.enroll instead of services.password.reset). If have been doing any operations related to enrollment flow you will most likely need to change your DB queries.</p><p>Finally, the old SRP-style password mechanisms from before Meteor 1.0 have been now completely removed. Other API calls from before Meteor 1.0 that have been deprecated (and now for the most part just pointing to their current equivalents) met their end in this release. See <a href="https://github.com/meteor/meteor/blob/devel/History.md#breaking-changes">history</a> for the full details.</p><h3>Removal of deprecated APIs in packages</h3><p>With the release of Meteor 2.0 it was only a matter of time until old deprecated APIs from before Meteor 1.0 would be removed. This release takes the first step focusing on removal of deprecated APIs around packages. Starting with packages API itself the old underscore style calls have been removed. So ancient calls like api.add_files will no longer work and you should used the camel case variant (api.add_files =&gt; api.addFiles).</p><p>Across the entirety of core packages, any deprecated API endpoints from before Meteor 1.0 have been removed, see history for the full details. This should affect only packages and apps that have been with us since the very beginning and failed to migrate to the new API calls.</p><h3><em>Deprecated flag for packages</em></h3><p>Among all these removals we have a new addition for the package life cycle. In a life cycle of a package, there might come a time to end the development for various reasons, or it gets superseded. In either case, Meteor now allows you to easily notify the users of the package by setting the deprecated flag to true: deprecated: true in the package description. In addition, you can replace it with a string that tells the users where to find a replacement or what to do.</p><p>The notice and instructions will display in the console when the deprecated package is added or updated.</p><p>If you want to see example usage, check out the <a href="https://github.com/meteor/meteor/tree/devel/packages/deprecated">deprecated packages</a> in Meteor.</p><h3>Typescript 4.3.2</h3><p>For fans of strongly typed JavaScript we are upgrading Typescript to <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/">4.3.2</a>. Check out the needed goodies:</p><ul><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#separate-write-types">Separate Write Types on Properties</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#override">override and the </a><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#override">--noImplicitOverride Flag</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#template-string-improvements">Template String Type Improvements</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#private-elements">ECMAScript </a><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#private-elements">#private Class Elements</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#constructor-parameters">ConstructorParameters Works on Abstract Classes</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#contextual-narrowing">Contextual Narrowing for Generics</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#truthy-promise-checks">Always-Truthy Promise Checks</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#static-index-signatures">static Index Signatures</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#lazier-incremental">Lazier Calculations in </a><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#lazier-incremental">--incremental and </a><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#lazier-incremental">--watch Compilations</a></li><li><a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-3/#import-statement-completions">Import Statement Completions</a></li></ul><h3>WebApp responses</h3><p>Webapp will respond appropriately to unsupported requests instead of sending content, including handling for new HTTP verbs like OPTIONS, to improve compliance in the following way:</p><p>GET</p><ul><li>Respond with the requested resource; static asset, boilerplate etc.</li></ul><p>HEAD</p><ul><li>Return headers identical to GET request</li><li>Do not send content (It’s ignored by user agents anyway)</li></ul><p>OPTIONS</p><ul><li>Respond with 200</li><li>Send an Allow Header listing acceptable request methods</li><li>Do not send content</li></ul><p>CONNECT, DELETE, PATCH, POST, PUT, TRACE, etc.</p><ul><li>Respond with 405 Method Not Allowed</li><li>Send an Allow Header listing acceptable request methods</li><li>Do not send content</li></ul><h3>DDP_DEFAULT_CONNECTION_URL behavior changed</h3><p>The undocumented environment variable DDP_DEFAULT_CONNECTION_URL behavior has changed. Setting DDP_DEFAULT_CONNECTION_URL when running the server (development: meteor run or production: node main.js) sets the default DDP server value for meteor. But this did not work for Cordova apps. Now you can define the Cordova app default DDP server value by setting DDP_DEFAULT_CONNECTION_URL when building.</p><h3>New platforms flag</h3><p>A new flag <em>--platforms</em> have been added to the <em>meteor build</em> command to specify the platform you want to build for. meteor build . —-platforms=android. This is useful for example when you are not using a MacOS and you want to build your app only for Android. Or you can use this to save time on CI not building all the platforms all the time.</p><h3>New deploy option</h3><p><em>--build-only </em>is a new deploy option. This is helpful if you want to build first and after some validations proceed with the upload and deploy. <a href="https://cloud-guide.meteor.com/deploy-guide.html#cache-only">More about this on Cloud docs</a>.</p><h3>http@2.0.0</h3><p>Thanks to <a href="https://github.com/jankapunkt">Jan Küster</a>, the http package got a complete rewrite to use fetch internally. This is to aid you toward migration to fetch. This will allow you to use the current http API that you are used to and will continue to work. This will remove issues with deprecation of http. Though this is the end of the package and it will be now completely deprecated.</p><h3><strong>New default format for Android builds</strong></h3><p>In 2.3.1 there has been a change in the default output for Android Cordova apps. The new default format is .aab, following the <a href="https://android-developers.googleblog.com/2021/06/the-future-of-android-app-bundles-is.html">announcement from Google</a> that starting in August new apps will have to use this new format.</p><p>If you still want to use the old apk format use the following flag in the build command:<em>--packageType=apk</em></p><h3>And much more!</h3><p>And this is just the beginning, there are many other smaller fixes and improvements. Please give the <a href="https://docs.meteor.com/changelog.html">changelog</a> for Meteor 2.3 a look for a detailed list of all changes.</p><p>You can update to Meteor 2.3.2 today as usual with</p><p>meteor update --release 2.3.2</p><blockquote>We had some issues with Windows and webapp package on Meteor 2.3 final version and that is why we are recommending the upgrade directly to 2.3.2.</blockquote><p>If you want to contribute for beta releases of Meteor with your feedback and testing your apps go ahead and Sign Up in our <a href="https://join.slack.com/t/meteor-community/shared_invite/enQtODA0NTU2Nzk5MTA3LWY5NGMxMWRjZDgzYWMyMTEyYTQ3MTcwZmU2YjM5MTY3MjJkZjQ0NWRjOGZlYmIxZjFlYTA5Mjg4OTk3ODRiOTc">Community Slack</a> and join our #beta-feedback channel.</p><p><strong>UPDATE 07/13/2021 — </strong>We have identified an issue when running android projects with the new bundle format. It was fixed on 2.3.2, so we recommend going directly to this version</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9971464ed1e" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/meteor-2-3-has-been-released-f9971464ed1e">Meteor 2.3 has been released!</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Meteor Meetups]]></title>
            <link>https://blog.meteor.com/new-meteor-meetups-b1fca07b49c3?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1fca07b49c3</guid>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Tue, 06 Apr 2021 18:02:16 GMT</pubDate>
            <atom:updated>2021-04-06T18:59:19.832Z</atom:updated>
            <content:encoded><![CDATA[<p>Meteor Meetups has a new home!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86dFGHXF9rrkSMmShDyPIg.png" /><figcaption>Author: Chris Montgomery</figcaption></figure><p>With the on-going lockdowns, restrictions, and uncertainty, Alim Gafar approached me about establishing online Meteor Meetups in the same way we did <a href="https://imapct.meteor.com/">Meteor Impact</a>. The thought here is to help consolidate all groups, and allow easy sharing between them, and have the opportunity and flexibility to do more exciting things. We have support from <a href="https://www.meteor.com/">Meteor Software</a> and <a href="https://www.pathable.com/">Pathable</a> and with that, a new home for Meteor meetups was born: <a href="https://meetups.meteor.com/">Meteor Meetups!</a></p><p>So what do meetups look like so far?</p><p>First off, we have dedicated pages to each <a href="https://meetups.meteor.com/groups">local group</a> so you can share information about yourself and additional information on companies using Meteor in your area. This will become more interesting once we’re able to transition to meeting people offline and connecting with Meteor users in person. In the meantime, you can at least scout out users in your general area.</p><p>How do the meetups work?</p><p>Each group can use the Pathable platform to schedule online meetings and hangouts. With meetings recorded, it will benefit other members of the community as well, as they can see great stuff from other meetups in other communities.</p><p>Once you sign-up, please go and edit your profile. Add your location (there is already plenty of options to choose from, but you can add your own as well) and if it exists select your Meteor group.</p><p>We will kick-off the meetups with Meteor New York with an introductory <a href="https://meetups.meteor.com/meetings/virtual/BfQpAkwGywcCrsTit">presentation</a> about Meteor Community, our new meetup platform, and some announcements about Meteor Impact 2021.</p><p>We are now looking for group organizers and speakers. If you are interested in one of those, please don’t hesitate to <a href="/service/mailto:storytellercz@protonmail.com">contact me</a>! Our goal is to have each meetup group meet at least once a quarter.</p><p>I hope to see you there!</p><p>If you like Jan’s work, please consider sponsoring him on <a href="https://github.com/sponsors/StorytellerCZ">GitHub Sponsors ❤️</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1fca07b49c3" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/new-meteor-meetups-b1fca07b49c3">New Meteor Meetups</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meteor Impact 2020 is this week!]]></title>
            <link>https://blog.meteor.com/meteor-impact-2020-is-this-week-db3a1ee1e0cd?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/db3a1ee1e0cd</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Tue, 20 Oct 2020 19:19:42 GMT</pubDate>
            <atom:updated>2020-10-20T19:19:42.452Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HGLUY922D_f7ii_L.png" /></figure><p>The time has finally come! After weeks of hasty preparations we have reached the finish line and Meteor Impact starts in few days.</p><p>In total there are 33 talks/meetings planned for Thursday and Friday. These are all spread out so that people across all the timezones can take part.</p><p>There are 3 keynotes:</p><ul><li>Filipe Névola<br>The well known community evangelist from Meteor Software will share with us <a href="https://impact.meteor.com/meetings/virtual/uhxNMfLq2ikFKxeBD">the latest and greatest news from the company and Meteor development</a> (Meteor 2.0 😉).</li><li>Scott Tolinski<br>Host of Syntax podcast and creator of Level-Up tutorials will share will offer his thoughts about why he still uses Meteor and <a href="https://impact.meteor.com/meetings/virtual/w4FLkSRsTDhrYjimv">loves Meteor today</a>. Great for new people to Meteor or for those who are discovering it for the first time.</li><li>Abigail Watson<br>Known for her Clinical Meteor track Abigail will share with the community <a href="https://impact.meteor.com/meetings/virtual/hzzKzrRsTaywATyBo">how she is using Meteor to help authorities combat COVID19</a>.</li></ul><p>These three are just the top of the iceberg! You will find many more talks from members of the Meteor community and famous Meteor contributors. Talks range from basic topics like <a href="https://impact.meteor.com/meetings/virtual/8mkJqR8wrDFXc3TN9">securing Meteor application</a>, <a href="https://impact.meteor.com/meetings/virtual/HTa4hbfohFPgW3hFz">PWA setup</a> to <a href="https://impact.meteor.com/meetings/virtual/He7TTgNYzny87Giaj">performance monitoring</a> and <a href="https://impact.meteor.com/meetings/virtual/bvTyApaSiqDzCaMi8">user authentication across multiple servers</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*qunWB8SY99h8tAgg.png" /></figure><p>Beside technical talks there are talks about other topics that affect Meteor community like <a href="https://impact.meteor.com/meetings/virtual/72voqP4oPXqYqkh8N">Meteor marketing</a> or introduction for new community members to <a href="https://impact.meteor.com/meetings/virtual/YCE2rLiqJMMA7kFij">get themselves oriented in the community space</a>.</p><p>You also get to enjoy guest panels about hot topics in the Meteor community:</p><p>Another category we have are showcases where you’ll get to learn about <a href="https://impact.meteor.com/meetings/virtual/iqidJxjjDvX8sASgo">companies growing with Meteor</a>, <a href="https://impact.meteor.com/meetings/virtual/sXPHbckzoXBokrSLo">tools for debugging</a>, <a href="https://impact.meteor.com/meetings/virtual/9993BajES8RDGwuBn">interesting packages</a> or <a href="https://impact.meteor.com/meetings/virtual/pRnJLcNw34h2RB2b9">tools for debugging and monitoring if you are hosting outside of Galaxy</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*b5SNcVHnJqefWKub.png" /></figure><p>Finally there are meetings where you can virtually hang out with other Meteor developers, talk about Meteor or whatever else comes to your mind, just like you would at a real conference. Some of these are more thematically set than others.</p><p>With the exception of meetings you can already submit questions to any of the talks and few of the talks already have polls for the audience that you can answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*UATqpD4pS0sMohBm.png" /></figure><p>And we are getting just started! Beyond the agenda you can browse <a href="https://impact.meteor.com/exhibitors">exhibitors</a> that show some companies/projects that use Meteor or helped with the conference.</p><p>October is <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a> and <a href="https://github.com/meteor/meteor">Meteor</a> and <a href="https://github.com/Meteor-Community-Packages/">Meteor Community Packages</a> are both setup to be part of it. So your submissions count towards it.</p><p>Till Sunday the conference site will remain open for you to setup <a href="https://impact.meteor.com/meetings/private">private meetings</a> with other attendees and speakers that you meet during the conference.</p><p>And all of that for free! But we would like to encourage you to consider <a href="https://impact.meteor.com/join/sponsor">sponsoring community developers and organizers</a>.</p><p>If you have any question on how to use the platform take a look at the <a href="https://impact.meteor.com/meetings/virtual/3EbRwYbEALSxb7NHm">first meeting</a> which holds many resources to help you get started.</p><p>Please share the news with other Meteor developers and interested friends!</p><p>Thank you and see you at the conference!</p><p><em>Originally published at </em><a href="https://dev.to/storytellercz/meteor-impact-2020-is-this-week-2icj"><em>https://dev.to</em></a><em> on October 19, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db3a1ee1e0cd" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/meteor-impact-2020-is-this-week-db3a1ee1e0cd">Meteor Impact 2020 is this week!</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does the Meteor.js community thinks? —  April 2019]]></title>
            <link>https://medium.com/@storytellercz/what-does-the-meteor-js-community-thinks-april-2019-5915c3a725cd?source=rss-480ffd4d4c95------2</link>
            <guid isPermaLink="false">https://medium.com/p/5915c3a725cd</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Jan Dvorak IV.]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 11:57:44 GMT</pubDate>
            <atom:updated>2019-04-17T00:46:19.568Z</atom:updated>
            <content:encoded><![CDATA[<h3>What does the Meteor.js community thinks? — April 2019</h3><p>What do the results of the survey say and some background.</p><h3>BackgroundThe constant cycle of “Meteor is dead” posts has been haunting the Meteor community for the last few years. Yet here we are, Meteor just released version 1.8.1, 1.9 is already being sketched out and 1.8.2 is under active development.</h3><p>Yet, it is being constantly pointed out that there is a lack of leadership which causes myriad of other problems that the community is facing. Some of that is justified, some of it is not.</p><p>From the MDG side, there has been a transfer of resources to focus more on Apollo, which addresses one of the early complaints on Meteor (that you can’t use other databases) and has found great success in the wider javascript community.</p><p>With the rise of many new libraries that gained a great hype, we saw a lot of top community contributors leaving or as is common in life, moving on to other things or getting busy with AFK life.</p><p>Besides the rumbling on the forums, there has been an activity to address these issues behind the scenes. Although initial talks did not pan out to everyone’s satisfaction, I can tell you that MDG is still committed to Meteor development (they rely on it themselves). Still, we probably won’t see as bigger engagement from MDG as we saw in the growth phase of Meteor.</p><p>Now then this is where the community comes in. Meteor is a mature framework now, but when it comes to community packages, things have been lacking lately. Most of this has to do with attrition on of the big name developers who have developed packages that have become the de facto standards and there are other issues that community can assist with.</p><p>In early March 2019 <a href="http://an open conversation">an open conversation</a> was started between developers on what to do. In summary, first was the creation of a <a href="https://github.com/Meteor-Community-Packages">GitHub organization</a> which will act as an umbrella for important community projects where there are people willing to maintain it. This is especially important if the original author does not have time to do so. We are currently in the process to determine which packages will be added here and figuring out an automated process for publication (suggestions and PRs encouraged).</p><p>There were many other ideas what to do with the community aspect, but eventually, it was decided to conduct a survey to determine primarily what people were looking for. As such a survey was conducted.</p><p>What follows is the summary of the results with my light personal commentary which is a mix of analysis and providing context.</p><h3>Participants</h3><p>First though a note on participants. As of the time of this writing, only 57 people have filled out the survey. Though very limited these people are very likely to be actively engaged with Meteor and want to see it succeed, as the survey was advertised on <a href="https://forums.meteor.com/">Meteor Forums</a> and <a href="https://spectrum.chat/meteor-js?tab=posts">Meteor Spectrum channel</a>.</p><p>Still, a long-running survey will be designed to get as many people’s feedback as possible. Maybe something akin to State of JS survey.</p><h3>Survey results</h3><p>First of all, let’s take a look at the easily measurable results (multiple choice answers).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*V6Nc84WxxwImgIoo9kwELg.png" /></figure><p>For me, this is the main interest, as I have volunteered to do the newsletter. Overall there is an interest in a Meteor newsletter. Possibly since there isn’t a dedicated Meteor newsletter. One of the old ones have either ceased operating or have shifted focus towards general JavaScript.</p><p>Personally, I think the issue is that those newsletters were coming out on a regular basis which leads to burnout from the author and having to work super hard when there is less content. As such the new community newsletter will be occasional mainly centered around important news about packages, discussions and always to inform about Meteor releases. More on that sometime later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*-iarfXLi_7hJ-zsUssHgww.png" /></figure><p><a href="https://medium.com/u/b3c786a4774c">distalx</a> will be very happy that his as this was his idea and he was very excited about it. I think this follows the popularity of the Transmission podcasts that <a href="https://medium.com/u/803918030a60">Sashko Stubailo</a> used to run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*udrQ2UfHhChJL-EI3imtKQ.jpeg" /><figcaption>Transmission podcast thumbnail</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*rjOlr82-gnVmyXBdJ1P7ig.png" /></figure><p>Same numbers as for newsletter. Though this one might be a bit harder to setup. I guess that it is a human need to socialize and make connections, but at the same time as developers, we are more likely to be introverted types.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*0NPKnovgfxyF23WNSr5pVQ.png" /></figure><p>Probably the most contentious question. 💰</p><p>There has been a discussion to speed up development and maintenance and reward developers for doing amazing work for the community. The idea of supporting developers for doing FOSS is more accepted then it was about 5 years ago, but the hesitation is clearly visible and understandable. Hence it will be essential that any effort in this area is open and clear.</p><p>Now we are moving into an area that required a bit of interpretation of the results (especially towards the end of this section), so please check the data for yourself to get the whole picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*yVt8W2s8vTFZodq81O3bBw.png" /></figure><p>Following from the previous there have been many suggestions on which way to support. Open Collective is clearly the winner here and seems to be the way for many FOSS projects. Second is Patreon, a popular support platform in general, though there is <a href="https://www.cnbc.com/2019/01/23/crowd-funding-platform-patreon-announces-it-will-pay-out-half-a-billion-dollars-to-content-creators-in-2019.html">question of sustainability</a> and probably not the best for org as a whole. That said, some individual developers already have Patreon. You can find more info in the related forums thread and would encourage everyone to support the developers and for developers to post where they can be supported into that thread, be it on Patreon, LibrePay, Crypto or <a href="http://ko-fi.com/storyteller">Ko-Fi</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*NRttLG37upnJ8nvuzehe1Q.png" /></figure><p>With a lot of overlap, we can see that Meteor Docs and Guide are the most popular place to go for information about Meteor, closely followed by the forums. This shows how important it is that we put our efforts into improving the docs and guide as much as possible. Later we will see that it has been often identified as lacking. That is also probably why GitHub and Forums are so much visited, besides it is the place to keep a tab on development and community news.</p><p>Finally, written articles are also sought after, but they will often be outdated as the bulk of them was written during the growth years of Meteor in the pre 1.0 or 1.3 eras and will often outrank in search newer articles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3eX4yXUluPUf11sC0wBCPQ.png" /></figure><p>Analyzing the question about Meteor misconceptions required a lot of picking and choosing on my side into which category I should place which comment. Not to mention there have been many answers which weren’t strictly answering the question.</p><p>The most common comment was about the hype train with other technologies and how Meteor is dying. Not much can be said about that what hasn’t been said already. “<a href="https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb">You are not Google</a>” article by <a href="https://medium.com/u/103a223e2d9c">Oz Nova</a> is a great response and summary to most common talking points in this regard. The second most common concern of scalability can also be answered by that. From my point of view through the only problem is just informing people on how to do it (which applies for the point of slowness as well, especially given the few latest releases just focused on that point).</p><p>The last point I would like to highlight is the point about Meteor being outdated. This could be merged with the hype answer as well. Common are the calls about getting everything to npm and Fibers and those are things that have been talked about for a long time and they are (with other points) on the roadmap, but there are other more pressing matters before we start moving onto <a href="https://forums.meteor.com/t/thingking-about-meteor-2-0/46022">Meteor 2.0</a>. There is also an ongoing debate if that is a good direction given <a href="https://blog.meteor.com/know-your-node-js-ff0b3a0f634e">the benefits that tightly coupled framework offers</a>.</p><p>Finally, you will find a long list of Meteor packages that have been highlighted as needing to be updated and that developers have taken onto themselves to update locally.</p><p>Quite a few are around Blaze and this will probably result in the creation of a Blaze centered working group. Beyond that is the legacy of Kadira and alanning:roles. Roles has been something I have been personally interested in as well, so I think that will become our first major project once we figure out the workflow on smaller packages.</p><h3>What is next?</h3><p><strong>Newsletter</strong></p><p>In the coming days, I will be putting up a welcome email to those who have submitted their email in the survey and preparing the first newsletter with other community members (feel free to contact me if you want to help).</p><p><strong>Virtual Meetup</strong></p><p>I think we will investigate some options on how to make this happen, but I wouldn’t expect anything major soon unless someone takes that as their priority.</p><p><strong>Podcast</strong></p><p>Looking forward where <a href="https://medium.com/u/b3c786a4774c">distalx</a> is going to take this now that there has been a clear interest shown. I think we will see a forum thread about this soon.</p><p><strong>Support for developers</strong></p><p>We will have to figure out how to get some finances flowing to developers of popular packages, this will go a long way to ensure their long term prospects. This will take some time as we will have to figure out how to do it properly. Keep a lookout on our organization GitHub for an issue related to it (feedback is always welcomed).</p><p><strong>Crossroad page</strong></p><p>Finally, all of this will require some crossroad page as the overall efforts are not limited to just the forums and GitHub. This will be probably a GitHub hosted a static webpage that we will put up in the near future as a temporary solution until we have a better idea of what to expect from it.</p><p><strong>Survey</strong></p><p>As eluded another survey will likely be constructed to give voice to more developers in the community over a longer time period.</p><p>As you can see we are at the beginning of creating a new chapter for Meteor community. I would like to encourage anyone interested in helping or just sharing an idea to reach out to us, either on our <a href="https://github.com/Meteor-Community-Packages/organization/">GitHub organization repository</a> or by creating a <a href="https://forums.meteor.com/">forum</a> thread with your ideas, suggestions and/or to volunteer to do something. Now is the best time since we are starting from scratch and you can have a great impact.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5915c3a725cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>