Igor Dejanović

@goto40 Thanks for the thorough analysis of the problem. I agree with you. I vote for moving the logic of `importURI` model loading out of scope providers. It makes sense...

Those are the tools developed by @danixeee, @danielkupco and @starcev as a part of their master thesis. The tools are hosted at [textx-tools](https://github.com/textx-tools) organization but the plan is to move...

@Aluriak, @simkimsia I fully agree, and I think it is the right time to set up the policy for asking question as the project [will move under textX organization](https://github.com/igordejanovic/textX/issues/122). At...

@simkimsia self-dsl should definitely be linked from textX docs. I just did that. Thanks for bringing this up. :) So, we will go with SO as the place to ask...

@goto40 Regarding how-to/FAQ, correct me if I'm wrong but I think their purpose is different. While FAQ should be some questions one could ask while learning the tool that could...

I've put instruction on SO usage in README and docs. We can start with the migration. From now on, questions should be asked on SO. We can start gradually moving...

> how do we organize the code? A validation module? Yes, I vote for `validation` module with all generic/reusable semantic checks. > do we need more expressiveness (e.g., for an...

> I wanted to ask about it in another thread, but since it came up here: from what I understand all errors are non-recoverable because once an error is detected...

> I would leave this PR open, or reopen it for 2.0.0. I agree to leave this open for now.

@goto40 Exactly. It's better to wait some time until we gather more experience with multiple languages used inside textX-LS. We'll be able to make a better decision then.