> We can't claim that we support Elixir while we don't have somebody who > maintains Elixir in the TG2 template, somebody who makes sure it works in TG2 > itself, somebody who makes sure it's supported in the packages used in TG2 > apps by default (namely, repoze.who.plugins.sa and repoze.what.plugins.sql) > and somebody who is willing to answer questions related to Elixir in TG2 > applications. > > If we're not certain that it works and will continue working, we can't claim > Elixir support and thus we can't have a switch to generate Elixir projects > from the quickstart command.
Exactly, and not claiming support is not equal to it not working as jonathan says, he's using it extensively. But he's not using the default auth mechanisms, and he's not able to provide that level of support to turbogears users. If someone is, we can easily add the elixir command back to quickstart. But we were shipping it, and it was broken, and nobody offered to help fix it. And while we could have done a one time fix, we would still be in this situation on every future release where we'd have to do that work without help from anybody in the elixir community. And SA declarative is honestly pretty good these days, so I think it's an good compromise. At least until somebody steps up ad agrees to help support elixir. --Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
