Roadmap for the immediate future
47 views
Skip to first unread message
Ancor Gonzalez Sosa
Sep 29, 2016, 6:50:34 AM9/29/16
to jang...@googlegroups.com
I has been working during the last weeks to fix one of the most annoying bugs we had in Jangouts[1]. Now that it's closed it's time to look into the future.
What should be the next steps in Jangouts development? For me the clear answer is "not letting the GSoC effort to be in vain". So I would like to base the next Jangouts release in the angular-2 branch created by Martin during his Google Summer of Code project[2]. Not only for the shake of using a newer technology, but also because he polished several things and added unit test cases (with the corresponding test infrastructure).That's what I created an specific issue in Github to finish that work and added it to the "0.5.0" milestone. What else would I like to see in that milestone? It's all here:
https://github.com/jangouts/jangouts/milestone/2
https://github.com/jangouts/jangouts/milestone/2
There are all kind of things, from small polishing that should be doable by anybody to more challenging stuff like the above-mentioned polishing of the angular-2 branch.
In parallel with the implementation of all the stuff in that list I would like to see some movement in the UI redesign (not only aesthetic, but specially from usability point of view). And of course, some related "marketing" effort like a landing page. But as I said, that's something I would like to see happening in parallel, not affecting directly the next release.
And also important... any area in which you are willing to contribute?
--
Ancor González Sosa
Imobach González Sosa
Jan 3, 2017, 3:21:51 AM1/3/17
to jangouts
El jueves, 29 de septiembre de 2016, 11:50:34 (UTC+1), Ancor Gonzalez Sosa escribió:
I has been working during the last weeks to fix one of the most annoying bugs we had in Jangouts[1]. Now that it's closed it's time to look into the future.
Thanks! :)
What should be the next steps in Jangouts development? For me the clear answer is "not letting the GSoC effort to be in vain". So I would like to base the next Jangouts release in the angular-2 branch created by Martin during his Google Summer of Code project[2]. Not only for the shake of using a newer technology, but also because he polished several things and added unit test cases (with the corresponding test infrastructure).
I agree.
That's what I created an specific issue in Github to finish that work and added it to the "0.5.0" milestone. What else would I like to see in that milestone? It's all here:
https://github.com/jangouts/jangouts/milestone/2There are all kind of things, from small polishing that should be doable by anybody to more challenging stuff like the above-mentioned polishing of the angular-2 branch.
Yesterday I started to work in this branch. I've updated our dependencies to Angular 2.4.0[1] and now the application starts. I plan to fix the testsuite during this week.
In parallel with the implementation of all the stuff in that list I would like to see some movement in the UI redesign (not only aesthetic, but specially from usability point of view). And of course, some related "marketing" effort like a landing page. But as I said, that's something I would like to see happening in parallel, not affecting directly the next release.
What do you think? Does the 0.5.0 milestone make sense to you? There is something important you miss in the issues list? Would you like to take another approach (like focusing the next release in UI instead)?
0.5.0 milestone makes sense, but I would like to add some UI stuff to this new version. Currently, the Angular 2 branch has some issues regarding the UI:
* The grid does not work. And to be honest, I'm not sure if that's the best approach (I'll open an issue to discuss it).
* Model dialogs are broken.
Some days ago, David Díaz proposed to use Google's Material Design, and I think it's a cool idea. We could give it a try and get rid of components like angular2-modal. The downside is that it will take more time to release a 0.5.0 version.
Meanwhile, we could release a 0.4.x version based in Angular 1 including the latest fixes in master and put that branch into maintenance mode.
And also important... any area in which you are willing to contribute?
I'll help porting the final bits to Angular 2.
Ancor Gonzalez Sosa
Jan 4, 2017, 5:46:25 AM1/4/17
to jangouts
Well, being more ambitious with the 0.5.0 release makes sense to me of we have 2 people (you and David) to work on it. That's 2 more people than we have working in the 0.4 branch (excluding my sprint last week). :-)
Releasing a 0.4.5 version with the latest fixes makes sense to me. The UI is still quite far from perfect, but we also have fixes in master to work better with recent releases of janus and recent browsers, to fix some problems in the chat...
And also important... any area in which you are willing to contribute?
I'll help porting the final bits to Angular 2.
Cheers
--
Ancor González Sosa
Reply all
Reply to author
Forward
0 new messages