We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Everything they didn’t tell you about the Ember Community

00:00

Formal Metadata

Title
Everything they didn’t tell you about the Ember Community
Title of Series
Number of Parts
27
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language
Producer
Production Year2018

Content Metadata

Subject Area
Genre
Abstract
The Ember community describes a worldwide subculture consisting of developers, contributors, bloggers, event organizers, podcasters and many others involved in activities around the framework. But which factors drive this complex community in its efforts? After a retrospective of open-source activity in the ecosystem, we’ll see which core resources and addons are particularly popular and which topics are particularly interesting to the community. Summing up these findings, we’ll finally try to answer how diversity and growth of this community can be furthered even more in the future.
VideoconferencingNichtkommutative Jordan-AlgebraLinker (computing)Multiplication signLocal GroupCommon Language InfrastructureLie groupAnnulus (mathematics)State observerPointer (computer programming)Group actionGradientDifferent (Kate Ryan album)Shared memoryNumberRight angleSimilarity (geometry)Line (geometry)Cartesian coordinate systemMereologyBit rateSystem callMobile appVarianceMultiplication signTwitterProjective planeArithmetic meanVideo gameOptical disc driveGraph (mathematics)Server (computing)Windows RegistryOutlierMusical ensembleStatisticsLatent heatString (computer science)Price indexIdentity managementSuite (music)Software testingPhysical systemCore dumpData conversionQuantumEmailService (economics)Reading (process)Module (mathematics)Text editorCodeLie groupMedical imagingPattern languageVirtual machineSoftware developerWave packetOnline helpState observerWordInformation technology consultingLevel (video gaming)Java appletElectronic visual displaySlide ruleSoftware frameworkAbsolute valueCellular automatonBasis <Mathematik>Sheaf (mathematics)Frame problemSoftware engineeringCommon Language InfrastructureNewsletterProgramming paradigmPerformance appraisalXMLComputer animation
Core dumpDefault (computer science)Common Language InfrastructureInstallation artNumberCodeMobile appSoftware testingAtomic numberNumberArithmetic meanSoftware frameworkDataflow1 (number)Basis <Mathematik>Translation (relic)State of matterDifferent (Kate Ryan album)Projective planeLibrary (computing)Text editorBit rateGroup actionEndliche ModelltheorieWeb pageProcess (computing)Commitment schemeConnectivity (graph theory)Multiplication signCartesian coordinate systemLatent heatRight angleMereologyForm (programming)DatabaseSoftware developerElement (mathematics)Data managementQuicksort2 (number)Point (geometry)Sound effectUnit testingWordElectric generatorMaterialization (paranormal)Internet service providerCore dumpCASE <Informatik>Task (computing)Revision controlBitOutlierMachine visionFigurate numberQuantumSoftware testingDialectFamilySuite (music)Mobile appPower (physics)MultilaterationSoftware maintenanceInheritance (object-oriented programming)Default (computer science)State observerEstimatorElectronic program guideMeeting/Interview
NumberWhiteboardProcess (computing)TelecommunicationStack (abstract data type)State observerTheory of relativityLocal ringGroup actionMobile appProcess (computing)Multiplication signBitPoint (geometry)MathematicsStatisticsDirection (geometry)State observer1 (number)Line (geometry)TwitterCycle (graph theory)Reading (process)NumberInstant MessagingPie chartImplementationMedical imagingMessage passingLie groupSoftware developerState of matterDefault (computer science)Order of magnitudeOnline helpVideo gameObservational studyRight angleSoftware frameworkType theoryFormal languageSlide ruleAreaVideo game consoleLatent heatNegative numberTelecommunicationMereologySheaf (mathematics)Buffer overflowCommutatorComa BerenicesTask (computing)Stack (abstract data type)Cartesian coordinate systemPiWhiteboardHydraulic jumpBit rateScripting languageServer (computing)
Point (geometry)Software developerCone penetration testControl flowType theoryCartesian coordinate systemStability theorySoftware frameworkGodMeeting/Interview
Lemma (mathematics)Core dumpTelecommunicationAverageBit rateGroup actionBasis <Mathematik>BitCore dumpInteractive televisionTelecommunicationNewsletterMultiplication signCountingInformationNumberBit rate2 (number)Archaeological field surveyCategory of beingRight angleAverageBlogGroup actionEvent horizonMedical imagingTraffic reportingBlock (periodic table)Sound effectView (database)WebsiteReading (process)Computer animation
TelecommunicationArithmetic meanPoint (geometry)TelecommunicationStability theoryMereologyProjective planeMultiplication signSoftware developerCellular automatonGroup actionFigurate numberElectronic mailing listSheaf (mathematics)BitComputer animationLecture/Conference
Linker (computing)Daylight saving timeSquare numberAverageComa BerenicesBlock (periodic table)Data typeComputer animationXML
Transcript: English(auto-generated)
Today, I want to share with you everything that they didn't tell you about the Ember
community. And in this talk, I want to show you what the community in Ember is actually about, also what kind of strengths I have found in the community, and also how we can leverage these strengths to actually overcome any challenges that we might still have in actually growing and still further improving our community. And before we get started, just a few words about myself, or maybe in a bit.
I'm a software engineer working at Simplabs. We are a consultancy that is specialized in Ember.js, Ruby on Rails, and also Phoenix on LXC Consulting. And we offer team augmentation, but also reviews and trainings.
Also, I am a member of the Ember core learning team, and also am one of the editors of the Ember.js Times, which is a weekly newsletter that is provided to your inbox to keep you up to date what is happening contribution-wise in Ember. And let's actually get into the topic. When we think about youth culture, and also specifically music culture, we find there are
a lot of like distinct groups that we can identify easily by their style of fashion, and also the way they kind of like present themselves to the outside world. And easily, or at least for me, I can really identify with that, being like a recovering
gothic kid from the naughties. And no offense if you're still into gothic music, it's actually pretty cool. I can say there is a lot of like identity around these specific subcultures that we create for ourselves. And it's more than just like this common interest in a specific musical genre, it's actually something that you build together, like a community that actually creates something
on top of the shared common interest that you have, and that actually brought you together in the first place. And personally, I believe it's not only about music that enables people or that kind of like induces people to create subcultures.
I also believe that actually technology is some place where people frequently actually create subcultures, some subcommunities that have like a common certain core belief to it that brings people together. And let's actually have a look at what the definition of a subculture is to better understand what it is about. A subculture is defined as a cultural group within a larger culture, often having beliefs
or interests at variance with those of the larger culture. So this actually carries two meanings. First of all, the subculture is still a part of the bigger group. It still shares a lot of like similarities with this group and a lot of like core interests. But on the other hand, it also is distinct from it.
It has like some certain beliefs, philosophies, paradigms that actually clearly differentiate itself from the larger group. And being here right now at EmberConf and just like seeing so many people coming from all over the world together to actually share this common interest in a framework and a technology that we all use and love, maybe even on a daily basis, also gives
me a sense of being part of a subculture, some kind of group or community that is a smaller picture of the JavaScript community. And therefore I would, yeah, therefore I would proclaim that what is happening here is actually some display of the Emberista subculture, as I heard about that
people in the Ember community refer themselves to sometimes. And it describes a group that is part of the larger JavaScript community that also has like every now and then different beliefs and different philosophies than the bigger picture. And I wanted to find more out about this very distinct beliefs that we have
in this community. And I set out and actually wanted to learn more about how we interact with the framework and also how we interact with people in the group. And with that said, let's actually have a look at how we develop with Ember, how is it actually used and how has it developed in, yeah, the past year.
When I was thinking about how I could evaluate the usage of Ember and how it's currently kind of like how its popularity might look like in the community so far, I was thinking that probably a good place to start is looking at the MPM registry, just like looking at the absolute
download numbers of Ember or Ember CLI might give me like a kind of like picture of how it's currently going. And I also think what is interesting to note here is that due to the fact that Ember CLI and Ember are highly intertwined, I can also easily assume that if I look at the download numbers of Ember CLI, I also get a picture of how Ember is actually used.
And just like a word of warning beforehand, if I now show numbers for any kind of like download codes for like MPM, we still have to keep in mind that they can never reflect the actual end users installing the modules into the application because we all know that a lot of like CLI tools, test suite and also like mirrors, like other registries that copy
and download packages from the MPM registry will also go into this download numbers. So if you're looking at any statistics, we also have to keep in mind they can only give us like a vague idea of a trend going on, some kind of like maybe development over time, but you can never take these absolute download numbers
as granted for, okay, so and so many users have kind of installed Ember CLI in their app. So just that you know. And looking at the download numbers, the monthly download numbers for Ember CLI, we can see that since the last year, so since the beginning of 2017 until the very now, that yeah, I would say the download numbers
remain quite stable. Between 300,000 to maybe 350,000, 380,000 downloads per month have been registered in the Ember registry for Ember CLI. And this is interesting to note. But I also found interesting to see what is it actually about this Ember CLI that we all cherish so much that it has become this ingrained part of the community.
And I also wanted to have a look at other communities and how they actually deal with scaffolding and building their projects and how they actually use similar command line tools. And just like looking at download data also like in the same time frame from the past year, I can see that there are very
yeah, very significant differences in how CLIs are actually adopted in other communities. As you can see here in this graph, you can also see that Angular CLI, VCLI and also React App, one of the projects that helps you to create React applications, all kind of like don't really hit it off regarding download rates. But on the other hand, Angular CLI,
which originates from a fork of Ember CLI shows that it actually really significantly increases in download rates over time in the last year to almost tenfold of the amount of download rates that it started out with in the beginning of last year. And now you go maybe like, why are you showing off the slide?
What does it now actually mean? I think for me, the takeaway from this is also something very interesting and I think also very important for the understanding for the community. And it's that even though Ember might sometimes adopt any kind of patterns very early on at some stage where
it's maybe not so eminent in the JavaScript community what this pattern is actually about and how it can help to increase developer satisfaction that sometimes when other communities also adapt similar patterns, it actually is a big success for them. And I find it quite striking to see that Ember can also inspire other subcultures in the bigger JavaScript community
to do something that definitely improves developer lives in other scopes. When we further want to evaluate usage of Ember and the Ember ecosystem a very great resource as you might already know but if not, I just want to highlight it all again is Ember Observer.
And Ember quality member Katie Gangland also creator of Ember Observer talks also in a talk about the Ember add-on community and the EmberConf talk from 2016 about all the details. So if you want to learn more about it, check it out. The really great thing about Ember Observer is the scoring system so it gives us an indicator how qualified any kind of add-ons are.
And this is also a great resource to find out what is currently going on in the Ember community and what kind of popular add-ons are currently out there. And I just had a look at the top 10 add-ons scored through Ember Observer and wanted to check what download rates are and also how popular they are indicated through GitHub Starring.
So let's have a look at actually the number of GitHub stars and also how it relates to the number of contributors on GitHub. If you look at the top 10 add-ons scored through Ember Observer they all have a full score of 10 of 10 through Ember Observer. You can find there are a couple of I would say add-ons that kind of like have a similar number of stars sometimes have something about like
200, 500 stars and we can still see there's like one kind of like big outlier Ember data kind of already estimates to over 2000 stars and also has compared to the other add-ons quite a high number of contributors which is kind of like impressive.
And I think we can easily also understand how these numbers can come up. If we also look on Ember Observer we find out that for example Ember data is more with an Ember core add-on something that is maintained by the core team and also is like part of Ember applications right from the start and therefore a lot of developers when they actually try to build their first Ember apps
they will easily stumble upon Ember data as the default data layer and want to find out more about the project and get curious about what it's about. And this can also facilitate contribution of course because here everyone knows like yeah first have to fix the things that are also used on a daily basis and therefore they get like curious and interested in the project.
If you also have a look at the monthly download rates for the top 10 add-ons we find that a lot of them actually have even out a kind of like quite a height number actually of like maybe 200,000 until like 100,000 downloads per month. And one outlier that we can also see here is like Ember CI Battle
with like over three times the amount of downloads per month we can see there's quite a significant number and we might wonder okay where does it actually come from. I can only estimate how this data actually comes about but I would assume that due to the fact that a lot of add-ons also have to rely on actually like transpilation through
Babel they might also come with their own prepackaged version of Ember CI Babel and once they actually create your app with different versions of add-ons they also add up to different versions of Ember CI Babel being installed especially if you handle your package management with for example Yarn. And last but not least let's actually have a look at the ratio
of contributors per download. I was a bit interested with that because I wanted to know okay they're like very popular add-ons and every now and then they're also like quite popular like we can see they are like very very much downloaded but I also wanted to know what the ratio actually is between yeah the kind of popularity and also the kind of commitment the kind of amount of contribution that actually
grows and kind of flows into the add-on. And here we can also see that yeah there is kind of like a contribution going on for many of the add-ons but Ember data also is like a big outlier which can also be explained due to the fact that a lot of like the add-ons that actually come with Ember by default also draw the attention of developers in the first place
because they want to fix what's going on in their application. And yeah this is probably something that we will hear a lot also like today we already heard about it a bit in Melanie's talk just now it's really a thing in Ember
that there's always an add-on for that and if I say that I really mean there's an add-on for any use case and just like looking at the amount of add-ons that provide us with the components some UI element or some form element that we can integrate into our application we find a lot of like curious examples of what is currently out there. There are like all kinds of
things there's like an add-on for example that helps us to create what you see is what you get editor with a very specific library that probably has like a very I don't know maybe not a super high amount of like maintainers around it but still there's an add-on for that because someone had to use it sometime and they go like
okay I can do this myself I can just create an add-on and I can also share with the community so everyone else doesn't have to worry about this problem anymore. There are also like very popular add-ons like Ember PowerSelect or any kind of like other elements out of the power family that you might have already used in the app or are using on a regular basis and also
add-ons like Ember Decorators actually help us to bring future features to Ember that might not be available yet so we can already indulge in all the good things that we love about what is coming up specification wise in our applications today. And I really want to bring this point back home that
there's really an add-on for everything. So when I had to look again at that I also found like this specific add-on that you can Ember install easily via Ember Rickroll and once you actually integrate this component into your application template the user will navigate to this page and what we get is actually like a Rickroll animation.
So this is like it's unbelievable. I also wanted to have a further look at the contribution and how it actually evolves in the Ember community. So let's have a look at some couple of numbers. If you look at the number of contributors for
every kind of like for a couple of like the core projects we can also find there's quite a difference in how many contributors at all time are actually prevalent in those specific projects. Most notably of course one of the oldest core projects in the Ember community, EmberJS itself has a quite high number of contributors
with over 700 of people ever having been contributed to the project. Other projects that are also quite popular are learning materials like for example the guides but also Ember data as you already noticed earlier is very popular as well as Ember CLI being the one go-to that you actually have to use when you want to create Ember applications. Other more
younger projects like GlimmerJS and also GlimmerVM are not so high in contributor numbers but this can also either be explained due to the fact that these projects are actually quite young and also due to the fact that maybe there is also like a very fast pace at which these projects currently evolve and therefore it's also
limited who can actually just like go in and contribute in the first place. But looking at that it's quite first of all astounding that the number of contributors is sometimes pretty high for the specific project itself and it also shows that the community really cares about contributing and helping out with the tools that they use on a daily basis.
It means how the Ember community actually tries to really alleviate contribution and actually tries to further the interest in making contributions to very core aspects of the framework is the RC process with RC standing for
request for comments. And what it does is actually providing a way for first of all the core team to actually communicate to the community what kind of like interesting aspects might be out there in the community. It also facilitates for any kind of person not only like the core team but any one of you sitting here to and also if you're not sitting here like you could also
do an RC it's not like that. To actually create your own vision of what the framework should actually entail and what you really need to actually get things done and make your apps even better. And last but not least it also enables all every one of us to also comment on these things and try to craft
a proposal together in a very collaborative and not so much hierarchical but really group based manner. And there are a lot of examples actually for very successful requests for comments that have been merged in the past years and specifically in the last year. One of these examples is for example the
Ember unit testing API redo. We will also see a couple of talks like later today that will also focus on that. And in this for example the RC opened by Robert Jackson or RWJ Blue as you might know him proposed a new API that should be used in test suites that come with Ember apps.
And it was very well received there were a lot of comments on this specific RC and not shortly after it has been merged at the end of last year Quest issues popped up and what does it actually mean? A Quest issue just like entails yeah kind of like Quest the kind of like story how actually this feature should be implemented and it also tries in a very detailed manner to
actually break down these kind of issues and specific sub tasks that other people in the community can easily pick up because if we want to make contribution even easier in the community I think one of the greatest way to make this possible is actually to enable people to understand what these features are about and also find
ways to easily understand how they can actually help. And Quest issues are a great start to actually achieve that to try to communicate to the community how things could actually be done so everyone feels empowered to actually get together and make it happen. And specifically if you want to learn more about the RC232
you can also listen to the next generation of testing today by Tobias and also the talk by Jamie might say more they will show you a lot about what this is actually about. Just looking at the number of RCs that have been opened and merged recently we can also see here in the red part
that there are actually quite a lot of RCs that are still open and waiting either for your comments as a community or also for further clarification. And this is actually quite a high number if you think about it and also gives us understanding what is still going on. With over 54 open RCs I think we still have a lot of
interesting things coming up into Ember. Also here in the violet like the second biggest part here in this pie chart we can also see that quite a large number of RCs have been merged in the last year. With over 24 RCs
having been merged recently we can also see that there is a certain trend of RCs actually picking up so people understand the RC process better, engage in it more and also RCs actually get merged so they are ready for implementation. And this is actually also quite an interesting thing.
A way for the community to keep up to date how RCs are currently implemented and what the status is of the implementation as the EmberJS status board. You can check it out at emberjs.com status board and what it does is actually give you an overview how the state currently is what kind of people are championing the specific RC if you need
any kind of more details for example for helping with the implementation and also if there are any related quest issues. This I actually found really interesting bringing back home the point that also made earlier about
communities being inspired by other subcultures is that this request for comments process that is already picking up in the Ember community also inspired maybe not many others but at least one other community also to pick it up. And I think it is also worth noting that to see that certain processes that
already work great for our community can also show other communities how they can actually work in a more collaborative manner. And I think it is really cool to see that because it seems to show that it is a successful process that we should further nourish also in the Ember community. Finally, I wanted to have a look how
actually communication works in Ember. And also how the ember with the subculture engages in talking to each other and actually get together. If you have a look at Stack Overflow which is probably for many new JavaScript developers that come into the community and kind of like go to point to find out more about
the framework or maybe like technologies they are losing or kind of like just looking up questions on how they could solve something. We see something a little bit like yeah, a little bit like controversial I would say. So if we have a look at the stats for the EmberJS
tag and how often it is used in Stack Overflow there is a steady decline since the last two years. And then I was a little bit like okay, what is this actually about like but where is everybody? Like they are not in Stack Overflow but I can see every one of you here so what are you doing all day? Why are you not in Stack Overflow? Where are you? Or have you already figured it out how you fix your apps
and this is why this is going down. I actually found that there are a lot of like other communities where people in the Ember world actually engage with each other and I find that probably the Slack community is one of the most notable examples of where actually discourse happens in our community.
And in Slack actually I had a look like at some stats we already have like over 11,500 members which is quite quite a bit. I wasn't aware of that. I only talked to a couple of these 1,500 so maybe I should check it out again. We have over 160 public channels. This is also quite a lot
and this excludes all the private messages and the private channels. And we also send over 2,700,000 messages and this is why you sometimes see this thing like the history is deleted because we have so many messages. It's amazing actually to see that so much is going on. And I want to know what actually people are doing all day on that. And also what kind of channels are there?
Like 160 channels, what do they all do? Of course there are a couple of like defaults that you already opt in when you actually join the Ember community Slack and there are like general or like random and also like the help channel that is very very useful specifically for new people to the Ember community to actually ask quick questions that they will otherwise use or
kind of like carry over to Stack Overflow and maybe like just have them laying there for like 3 days. It's a very straightforward way specifically as people are from all over the world and can easily just like jump in to answer the question. And even if no one is online, at least Lux is online to actually give you an answer. Also we have a lot of like who are on Dev channels like
Dev Ember and Dev Ember CLI. We also have like a couple of local channels so if you're from any other kind of part of the world than the US, you'll probably also find like maybe I don't know, maybe a British channel or maybe like a German channel or some kind of other community that you can engage with either in your kind of like area or maybe like even in your
native language. And also we have a lot of add-on specific channels so if you are using some add-on, you want to interact with maintainers, you can easily do that and last but not least the biggest chunk that we can see in the pie chart is called other fun stuff and I just want to have a look what this actually means. Like what kind of other channels are there?
So as Melanie already mentioned in her talk, there's of course a topic accessibility channel and also many other topic channels that you can find in this kind of area. Also we have the Women in Ember channel that for example helps people to engage in the community if they're like a women developer and want to find out more about Ember. And also
we have like channels like give RBG Blue a beer. Which is also quite useful I guess, right? I mean, that's pretty straight forward. And just looking at the overall stats, we see that regarding the number of weekly users that most of the users, like over three quarters are actually kind of
like just there and just like hanging out and reading what's going on. Maybe hanging out in announcements or in help or in general, just like checking out what's going on. And one quarter is actually messaging and actually sending any kind of like questions or any kind of comments to other people. Also just looking at the most popular channels and how they actually perform regarding messages, we can see the help channel is still the most popular
one. Like most of the messages are still sent there. And actually a lot of this change is happening with a lot of like people that are new in the community. Which is actually a great way to reach new people in the Ember world. And also if you look at the number of users of all time, we see that it actually kind of like evenly distributes over
the default channels that are already set up when you join the Ember community stack. Which also indicates that if you want to drive people in a certain direction, you want to go like, oh, I actually would like that people could see this more. You could just set it up as a default, I was thinking, right? But yeah, this is kind of like an interesting point also to make. Like people just like stay in the channel then and just
go like, yeah, I'm just going to check it out every now and then. And I was curious also who talks the most. So I had a look at like the top five channels that have like the most messages at all time like since the community existed and I could see help is actually quite
actually quite talkative per user, right? I wanted to know like who actually talks the most, like how related to users, how many is it? And help is quite good with it, general also random, Ember data, also quite a bit, but actually most chatty is really team learning, right? And I'm actually not so contributing to that too much so I'm wondering who is that actually?
And also if we look at the last 30 days and who's actually talking a lot in these channels, we find that a couple of like the channels we already mentioned are also there, team learning is also not too bad but then we see that for example in topic type script a lot of activities actually going on. I was a bit curious what
this is about, like I don't know why in the past 30 days did something happen or what is going on? So I had a look at Ember server again to actually find out if there's an add-on or something that is related to the channel and also find Ember CR TypeScript to be there. And interesting with that is also under the top 10 download at Ember add-ons
and also kind of like has quite interesting download rate. If you're looking at the monthly numbers you can also see that specifically in the last month it really skyrocketed a lot and you also found out that it's mostly due to the fact that a lot of people are picking it up more because recent releases actually implemented some major features that were
highly requested in the community and this also shows something very interesting I think about the Ember community especially if you look at the Stack Overflow trend data about the TypeScript tag that a lot of people are actually curious about TypeScript and I think this actually brings back the brings the point back home that it's actually cool to
sometimes be just a JavaScript developer who goes like yeah this is actually really pretty nitty-gritty I really like that I like TypeScript for my application and it's this cool new thing that I want to try out and I actually think like add-ons are a great way to further this excitement without having to lose the stability that we all cherish and value in the Ember framework
also lots of other great ways for communication exists like the blog through the Ember core team and also newsletters like the Ember JS times through the Ember learning team other resources and other newsletters like for example Ember Weekly are also there and actually quite popular with over 6000 subscribers and with the Ember JS times
with 1100 subscribers we can see a lot of people are actually interested in what is going on in the community and subscribe to these newsletters but I also wanted to know if there's more about that like I mean I subscribed also to a lot of newsletters like but what does it actually mean are people actually reading that are they actually doing anything with the newsletter and had a lot of
more insight into the Ember JS times specifically and here for example you can see that first of all subscriber count kind of like elevated over time kind of steadily until the 1100 mark that we are currently at and also if you are looking at engagement rates we actually also find kind of like striking numbers with an average of 30%
engagement rate which is quite a bit I don't know if you ever worked in marketing but this is not too bad and last but not least I also want to have a look what for example the spike that we saw earlier the engagement rate is about and I had a look at this and then I was like oh okay you're right we sent out the survey we were just like asked people can you
answer this one question survey 30 seconds or something and I was a bit like I don't know if people really pick up on that will they really do that right but actually in fact like over 60% of people engage with that and I was like oh this is really cute this is really nice of you you know like I really appreciate this and I think this also really nicely shows that there is actually a lot of ways that you can
communicate with people in the community and people are really appreciative about this information and also try to give a bit back and this is also what I really love about the Ember community it's just like very cozy so with that said I also want to have a quick look on what is actually happening offline and not only online
with over 68 meetup groups worldwide and also a lot of like international conferences like Emberfest also Embercamp London and specifically EmberConf where we are here right now I think there is a great way for us to also engage face to face with the people we already meet online on a daily basis
and I also believe that specifically this personal interactions and these events so we can actually see each other as the very human beings that we are are also a very great way for us to actually broaden the community and I believe this is actually a pretty big point for us as a group
as an Emberista subculture to further the stability and also to improve the community in itself and here I also want to highlight another project that is part of the Ember community the Ember Women Help Women project that for example tries to further leverage the
diversity in the community and tries to support women developers to not only be part of the community but also to support them in speaking gigs and also trying to get the message across and I believe Women Helping Women is probably one of these great means
that also are a reason for me actually currently being here and I would like to see many more of these projects that try to create diversity in our community to merge to actually further grow our community as ourselves and also hopefully to inspire many other JavaScript subcultures to do something very similar to make it a better place
in the technology community and with that said I just want to sum up what my findings were when I set out to actually find more out about the Emberista subculture first of all I found that the Emberista subculture is very inspiring to many other subcultures and this is actually a really great thing and I don't want it to change I actually want it to be distinct from
other subcultures at all times at least a bit to kind of like create something new that can also be leveraged by other people also I want to see more efforts to actually further excitement and I think the add-on culture but also a lot of like cool new features that we saw in the keynote are a great
way to actually achieve that also I think that leveraging communication is a great means to actually make it more efficient to make people understand the community what is going on and I think we are already in a great way to do that and running the community actually approving the overall being of the community is a great aspect to actually make it
more stable but finally it's probably all about kind of like being awesome, staying awesome and I'm very happy that it has been so far so with that said thank you very much and have a great time at EmberConf