Read the statement by Michael Teeuw here.
Automatic checking of all MagicMirror² modules
-
@karsten13 mmpm doesn’t do config editing
and to do config editing in a reliable way, we need programming standards too. -
@sdetweil We already have some standards in place (node_helper.js, naming conventions, package.json, etc) - what’s one more (config-schema.json) for the programmer? Think along the lines of the schema.json file used in MMM-Config.
Programmer creates the GUI settings page, using API into a specific file. It’s up to the core to insert result into the main config file. if GUI file isn’t there, then resort to a web based editor.
https://github.com/homebridge/homebridge/wiki/Verified-Plugins describes the process in homebridge’s case. Provide a reward, and bam - We’ve got easier access to the project, making it more widespread, and it completely eclipses the automatic checking process here.
Reward for the programmer is rather simple. A badge set thusly - everywhere - in the built in plugin manager’s search, on websites, etc.
Example - No GUI settings page file (the dead module):
Example - GUI settings page file (my reworked module with more functionality):
and the resulting config (I believe they use JSON rather than JS):
-
@BKeyport I believe we use js because you can have comments, json does not support comments
-
@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.
-
@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.
-
S sdetweil referenced this topic on
-
S sdetweil pinned this topic on
-
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 …
-
@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 -
@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.
-
@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 …
-
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?
-
