Angular Material2 - Roadmap

[agaurav]

Proposal:

As per milestone & google group threads , it seems this project is currently lagging bit behind. Also https://github.com/angular/material2/issues/11 has been closed but there is still a structured roadmap & devlopment guide missing.

Given that angular2 is close to production release it will be really great if we can have some estimates on when to expect a beta version, the estimate on respective design docs seems to be not updated recently.

Going through google group threads and other forums I think the angular2 community will really appreciate the following:

• Better project organization and pace with explicit roadmap and deadlines (Atleast for when should we expect the apis to be frozen for the essential components)
• If possible then involve others from the community toward contributing (Even a very brief development wiki on the internal working & wiring of the framework will be a real help).

[jelbourn]

alpha.6 is slightly delayed due to some unforeseen work that came up over the last couple of weeks. Situations like this are exactly why we aren't able to commit to a more specific date. We announced at ng-conf that we're aiming at a beta for this year, but promising something more than that will potentially just disappoint everyone if it is delayed. The milestones will be updated next week when we meet again and reschedule the delayed work.

As far as contributing, we're very open to contributions, and there have been quite a few PRs from community members. Check out our contributing guide and dev environment guide.

[aminebizid]

@jelbourn are you planning to upgrade to last angular rc in alpha.6?

[jelbourn]

@zigzag95 Yes, sometime next week

[agaurav]

Delays are part of all projects but having specific dates help others plan accordingly with a slack for them as well as push admin to try hard once they are crossed. As for contributions, a brief guide on usage of the core libs would have been very helpful though now I am going through the source, the code comments are very well written.

A beta by end of the year will fit my migration plans for angular 2 well, thanks.

[DerekTBrown]

Have to agree- this project is not contributor friendly. I would love to contribute to various components within this project, but I am continually told these components have already been assigned to other people, who are not visibly working on the project. Canonical example:

https://github.com/angular/material2/issues/45

[fxck]

+1 !

I'd really appreciate something similar to angular weekly meeting notes, to give us a weekly update on what's actually going on. Even of it was something like "this week: sorry, we didn't have time to work on material2, because of forms and material" or whatever.

It's been over a month since the last release again. I remember Rob telling me couple of months ago "there's a room full of people working on material2 pretty much on full time", and I somehow doubt that seeing how slow the progress is and how many of the team members have to work on other parts of the angular2 as well.

How big of a priority material2 is to angular/google?

tl;dr: I get it, quality takes time and you all are working on bunch of other projects, but at least giving the community weekly updates on what's going on, who's working on what, what problems there are, would be really really appreciated

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}