Skip to content

Credit where credit is due #4

Open
@joshgoebel

Description

@joshgoebel

It seems easiest to start by copying many of the great Javascript exercises and then porting them to Wren. In many cases the instructions may even work as-is (though perhaps this will change as the exercises get harder). Hopefully many of the test suits will work (after reworking syntax/porting slightly, etc). The Wren solutions I'm writing from scratch.

Obviously in some cases the exercises will need to change or be rethought because the language is different, but I think I can get a long ways for many exercises by taking advantage of the hard work already put in on the JS side.

So... if I'm starting with the foundation of using JS exercises... what information should go in the author and contributor blocks for config.js for each exercise? Should I be the new author? Should the contributors from JS be left in place? Should it all reset to zero because it's now Wren?

I don't want to borrow without giving credit where it's due so I want to do the right thing here whatever that is.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions