@bugsounet Sure :-D It’s already in the stats.json.

1. mykle1: 42
2. bugsounet: 35
3. MMRIZE: 19
4. fewieden: 15
5. Tom-Hirschberger: 13

Hello everyone!

Have you ever wondered what the most popular MagicMirror² modules are? Until now it wasn’t easy to find out. Recently, I added a new sorting feature to the new module list I am working on. It allows you to sort by GitHub stars! So now it’s easier than ever to find out which modules are the community’s favorites 😀

At the moment the top ten modules are:

1. MMM-Remote-Control (476 stars)
2. mmpm (168 stars)
3. MMM-Screencast (160 stars)
4. MMM-GooglePhotos (154 stars)
5. MMM-Todoist (147 stars)
6. MMM-Traffic (139 stars)
7. MMM-BackgroundSlideshow (130 stars)
8. MMM-pages (102 stars)
9. MMM-ModuleScheduler (96 stars)
10. WallberryTheme (94 stars)

Why is it important to star modules? Starring modules on GitHub is a great way to show your appreciation for the developers’ hard work. It also helps other users find popular modules.

How can I star a module? To star a module, simply go to the module’s GitHub page and click the “Star” button.

I encourage you to star all the modules you use and appreciate ⭐ And don’t forget to give the MagicMirror project itself a star! 🙃

I hope this new sorting option helps you find the perfect modules for your MagicMirror² setup!

Your feedback is welcome: Would you have expected these modules to be in the top 10? Which modules are not in the top 10 and should get more stars in your opinion?

@sdetweil With git reset ... everything is reset hard, this fixes the problem, but does not help to explain it. I haven’t fully understood myself why git pull didn’t worked after git stash.

@1a2a3a If you want to reset the module without saving your local changes, you can do this in the module’s directory:

git fetch origin master
git reset --hard origin/master
git pull

@Manu85 said in Hello everyone, do you know if there is an MM module for rugby:

@mumblebaj Hi I saw that @KristjanESPERANTO had made a football module like your Rugby module with the selection of different leagues, do you think that the module is adaptable with yours? it’s just a question
https://github.com/0m4r/MMM-SoccerLiveScore

MMM-SoccerLiveScore is maintained by @0m4r. I don’t really deal with sports modules :-)

@Dankodan I don’t use Alexa, but MMM-AlexaControl still gets updates. So it seems to me that it still might work.

MMM-PIR didn’t get an update since 2020. Are you talking about MMM-Pir from @bugsounet?

@fischi87 said in module.js mismatch error and good by os:

do u mean the whole errors come from the MMM-MyCommute module?

I don’t know. Deactivate all modules except this one and then see if the errors still occur.

@fischi87 That project hasn’t been updated since 7 years. On the official module list is a newer fork which got updated 2 years ago. So I recommend try this newer fork: https://github.com/qistoph/MMM-MyCommute.

Which fork of MMM-MyCommute are you using? Go to the module’s directory and run git remote -v.

@BerkSmash1984 I just fixed it. It was a mistake on my part and should not happen again :-)

The only game on MM I know is snake: https://github.com/superuserx/MMM-Snake :-)

Nice! :smiley: Don’t forget to add it to the module list.

You are using a very old fork from RaymondMolenaar. I recommend that you switch to the original (and active maintained) module from CFenner: https://github.com/CFenner/MMM-Netatmo

Awesome! Thanks!

@sdetweil said:

show how to resolve the integrity problem, without constant intervention

With “integrity problem” you are talking about how to add new modules to the list?

I’m also fine with your order of tasks :slightly_smiling_face:

is it you that becomes the maintainer?

A maintainer of this project, yes. But as I understand it, we can assign different teams with different roles for each project. So I don’t automatically have to become a maintainer of the core.

@Jalibu wrote:

are there plans to make this the official linked modules store on the project‘s page?

I’m definitely open to the idea of turning it into an official part of the project and moving it to MagicMirrorOrg, for example.

However, I have not yet sought dialogue with the core developers in this regard. It would be very interesting to hear if the core developers are open to that idea. @karsten13 , @rejas and @sdetweil, what do you think?

I‘d also vote for making this the source of truth without dependency to the old page as a datasource

The current solution (the list in the wiki) works and does not cause any additional work for the core developers.

However, as soon as we automate the process of creating the new module webpage, a vandal could provoke ugly effects. That’s why a different approach to maintaining the list, one that provides more protection against (intentional and unintentional) vandalism and includes a simple quality check, would make sense.

My concrete suggestion would be to create a pull request template for this purpose.

---

If we decide that “my” list should become an official part of the MM project, I would spontaneously suggest these rough milestones in the following order:

1. moving the repository to MagicMirrorOrg.
2. finding a better way to maintain the source of truth (currently the wiki page).
3. replacing/redirect references to the old module list.
4. automating the creation of the module list website.

Meanwhile, there have been some changes to the module list. E.g.

• If you click on a maintainer’s name, you will get a list of all modules by that maintainer :smiley:
• Dark mode switch
• Style changes
• Many module maintainers added screenshots and keywords and fixed listed issues
• GitHub stars are displayed
• New sort option: number of stars
• Module tags are now clickable
• Screenshots are now clickable
• Optimized mobile view

And some more …

well we use it to control the test platforms.

Can you show me where?

That’s the point of npm ci it takes the package-lock.json to install and it don’t change it.