Automatic checking of all MagicMirror² modules

BKeyport

@sdetweil It don’t matter how it’s done, honestly. JS, JSON - Same diff in my book… I’d just love to see it get simpler, and wrap up some of these projects into one.

sdetweil

@BKeyport what we really need is an AI page layout/designer tool. mushing all these disparate css together w the base design is getting beyond most people’s capabilities. I know it’s way beyond mine.

KristjanESPERANTO

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 …

Jalibu

@KristjanESPERANTO are there plans to make this the official linked modules store on the project‘s page?
In my opinion it is already by far better than the existing one. I‘d also vote for making this the source of truth without dependency to the old page as a datasource

KristjanESPERANTO

@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:

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

karsten13

@KristjanESPERANTO said in Automatic checking of all MagicMirror² modules:

@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 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:

moving the repository to MagicMirrorOrg.

finding a better way to maintain the source of truth (currently the wiki page).

replacing/redirect references to the old module list.

automating the creation of the module list website.

I’m fine with this. The Wiki stuff should not stay the source of truth, this construction is horrible. Maybe we have to wait until we have full control over MagicMirrorOrg …

sdetweil

@KristjanESPERANTO @karsten13

I’m also ok with this style list becoming the current. but I think the order of task needs to change

show how to resolve the integrity problem, without constant intervention
show the automation
then move to org
then redirect links, and seo
and
show how we migrate the list as new requirements come along. is it you that becomes the maintainer?

mumblebaj

@KristjanESPERANTO My 20pence/cents worth, I vote to make this the official page. We need to move with the times and the old page is outdated.

KristjanESPERANTO

@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.

sdetweil

@KristjanESPERANTO integrity.

you said user error or vandal mess up the data

currently we don’t have different roles.

but that wasn’t my point.

I have enough on my plate and wouldn’t be able to maintain this