MooTools Forge Issues

Update: The issues we had been having have been fixed.
Many compliments to the MooTools team, especially to Guiller, the author of the Forge!
The post is maintained for archival purposes.

----

We at Siteroller are in love with Mootools. 
We have been using it since version 1.0, and think, frankly, that the whole thing should be integrated into ECMAscript v2.

About half a year ago they created a public repository wherein anyone can create an upload their own Mootools classes.
A few years late, but better late than never.
If just it work.

It doesn't work.  Getting our MooRTE class in was hours of labor, and updating it has proven impossible.
Since there was a serious bug in our initial commit, this is a major issue.
From our complaint in January:

The forge update button is still not working.
The MooRTE plugin now has nearly 150 downloads.
And every one of them is broken.

Shortly after committing we found a major issue - not sure how it passed through testing - and went to correct it.

Now, nearly a month later, with dozens of attempts to update it ignored, I still have the same buggy commit up there.

Unsurprisingly, this has been a negative experience with our users - I don't know how many we still have.

A bug report was filed on the github branch, the IRC channel was haunted, to no avail.

Please; The forge is supposed to help the community, I beseech, beg, implore, and request if anyone who can look into this issue can please, please look into it.

Sincerely, a poor, desperate, Mootools developer.

The Mootools user group has several threads on this issue, and the uservoice page boasts several high ranking suggestions for this to be fixed.

Mootools has what it takes to dominate their field.  If they would but realize that the community is important.
I understand that Mootools is volunteer work - it includes some of my own commits.
And I understand that the Forge is being handled by just one developer. 
But it is the job of the Mootools team to see that such issues are out of they way if they wish to be taken seriously.

In the Forge plugin page it says:

Never should a plugin rely on a 3rd party link to explain its behavior or functionality. 
We need this to ensure that if a website is removed or becomes inaccessible, people can still enjoy your plugins' functionality.

For now, I strongly recommend that anyone who submits a plugin to add contact links in their README.md, and that you keep as little as possible on the Forge. 
[You] need this to ensure that if ..or [when the Forge] ..becomes inaccessible, people can still enjoy your plugin's functionality.

Loading mentions Retweet

Comments (0)

Leave a comment...

 
Got an account with one of these? Login here, or just enter your comment below.
Posterous-login    twitter


 

About