Note that the current development for More 1.3 is done in the 1.3wip branch on github. http://github.com/mootools/mootools-more/tree/1.3wip So instead of using the master branch, you should checkout the 1.3wip branch and push your changes to the 1.3wip branch.
If you use git, your workflow might look like this: For mootools more on github. $ git clone https://[email protected]/mootools/mootools-more.git (or the ssh link) $ cd mootools-more $ git checkout 1.3wip Make your changes $ git add ... $ git commit ... $ git push origin 1.3wip Send a pull-request to timwienk, arian or anutron On 1 aug, 13:12, Tim Wienk <[email protected]> wrote: > In an effort to get stuff cleaned up for the 1.3 release of More, I > decided to clean up the Localization stuff, and made a list of things > (based on the English localization files) that still have to be done > to have everything translated for the currently supported languages. > Since I don't speak most of the languages, some help would be > appreciated. So if you feel like contributing, the todo-list will be > attached to this email. (You can submit other improvements as well.) > > For those who don't know: > The best way to contribute would be to fork MooTools More > fromhttp://github.com/mootools/mootools-more/and send a pull-request > after you made your changes. If you don't know how to use git, a patch > or language-file attached to a ticket at lighthouse should work as > well. > > Thanks! > > Tim. > > (PS. This email is posted to both the mootools-users and mootools-lang > Google group.) > > mootools-lang-todo.txt > 1KWeergevenDownloaden
