Contribution tips. about haxe.org HOT 12 CLOSED

My personal feeling is that anyone who is willing to/capable of contributing is going to figure out how to do that without any overview like that. Having said that, it could still be nice to have this information.

The one thing I would like to have is a short introduction on how to hack the compiler, but that's quite technical and requires some thought.

from haxe.org.

There is a couple of pages on the old wiki regarding that: http://old.haxe.org/doc/advanced/code_generators

from haxe.org.

I think the page is a good idea.

Especially having a heading "Filing issue reports" that we can link to when
useless issue reports arrive on Github could help explain to people why we
need a minimal example ;)

On Wed, May 28, 2014 at 6:19 AM, Dan Korostelev [email protected]:

There are a couple of pages on the old wiki regarding that:
http://old.haxe.org/doc/advanced/code_generators

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-44342963
.

from haxe.org.

@jasononeil +1 :)

from haxe.org.

Some good ideas in there : https://github.com/pengwynn/flint

from haxe.org.

I've written a short filing-issues overview here: https://github.com/HaxeFoundation/haxe/wiki/Filing-Issues-checklist

from haxe.org.

@Simn. Wouldnt it be an idea to put that wiki content (also) into a CONTIBUTING.md file? This is picked up by github like this (see tooltip message)

from haxe.org.

Oh nice, I wasn't aware of that.

from haxe.org.

How nice! Good idea!

from haxe.org.

It's in HaxeFoundation/haxe#3918 and works 😄

from haxe.org.

Is this sorted now or are we still in progress?

from haxe.org.

It's good enough. Not like anyone reads these things but at least we tried.

from haxe.org.