Finding a new official generator-angular

[SBoudrias]

The official generator-angular is not really maintained by anyone anymore. We're lucky that angular have such a strong community relying on Yeoman, so there's a lot of available alternative.

I think what we basically want for generator-angular is to:

1. Be maintained (we need active maintainers)
2. Focused on the frontend (backends should be provided via composability features)
3. Could be used by backend generators (a backend generator could compose generator-angular easily in theirs to provide an angular frontend)
4. Be future ready, so considers moving to angular 2 soon after its official release

So, I'm launching an invitation to a couple popular angular generators out there if one of them feel they'd be a good fit/team to become our official generator-angular. I might've missed some, but a few candidate I can see:

• https://github.com/Swiip/generator-gulp-angular (@Swiip, @zckrs)
• https://github.com/swirlycheetah/generator-angular2 (@swirlycheetah)
• https://github.com/cgross/generator-cg-angular (@cgross)

[roaks3]

This sounds great. FWIW once PRs start rolling through again I'm happy to contribute code for some of the features that have been on the backlog for a while.

[Swiip]

We (@zckrs and I) are sure being interested in such a project. We always worked on our generator to be an open and generic solution. Also, we always had the hidden wish to join in some ways the Yeoman organization.

But the timing is complicated for the Angular community right now. Angular 1 begin to decline, Angular 2 is not totally ready yet and is still changing fast (2 broken beta release last week).

Tools are moving too, if Angular 1 generators mostly use Bower as dependency management and no module management, Angular 2 push to use TypeScript and SystemJS which is drastically different.

I don’t really see how just maintaining generator-angular could be the future, or even stating that generator-gulp-angular is the new official generator (which would be awesome btw).

That’s why we started the FountainJS project which allow us to cross use a Bower configuration generator, a SystemJS configuration and a Webpack configuration with an Angular 1 project and an Angular 2 one (to be honest a React one too).

We really think that’s the future for the Yeoman generators. Somehow, it’s that or binding Angular 1 to Bower and Angular 2 to SystemJS and create two completely different generators.

If you’re interested by our approach, I don’t see exactly how we could merge the FountainJS initiative in the official Yeoman organization but we’re willing to consider any opportunity. Even if it passes by dropping our brand FountainJS or changing some design choices.

[zckrs]

💯 @Swiip

[chrisdwheatley]

Hey, maintainer (albeit a terrible one) of generator-angular2 here.

I'm finding it difficult maintaining the generator currently simply due to the fact I've not been involved with the Angular ecosystem as much for a while now.

I'm passively looking for maintainers and generally I'll give people contributor access to help out as soon as they contribute to the project. That being said things are pretty stale and outdated now and the feature set I planned on developing hasn't been feasible.

It feels like it makes sense to try and combine efforts somehow to ensure people aren't spread too thin but I'm not sure the best way to proceed from here.

I'll link to this from the generator-angular2 repo and see if we can get some eyes on this.

[HaakonH]

plus one for adding typescript as an option to this generator

[zckrs]

https://github.com/FountainJS/generator-fountain-angular2

Or

https://github.com/FountainJS/generator-fountain-angular1