Decide what to do with this repo

[btford]

We haven't touched this in months, but I think there are valuable things in here.

I vote we move this content into the official angular docs.

Recently, we get a lot of PRs for new features that should be implemented as third-party modules instead. Having a canonical explanation for how to do this would be nice.

[stormpat]

Just found out about this repo, and i think it would be a really good idea to have some kind of conventions on modules. I have been reading other peoples code and trying to figure out a idiomatic way of building modules for angular, but a clear definition would be great in the official documentation.

[0x-r4bbit]

@stormpat talking about module names? Or what conventions? I mean there's not much room left when it comes to modules.

[stormpat]

@PascalPrecht Yeah, i was referring to module naming conventions, ATM community built modules have kind of random naming conventions. I think this is because theres no official guide available.

[0x-r4bbit]

Take a look at @btford 's blog post which is referenced in the spec http://briantford.com/blog/angular-bower there you should find what you're searching for.

[RichardLitt]

+1 to moving content to official docs.