tldr; let's aim to make OGV a finished product by iterating on the present work product.
A lot of features in OGV have already been incorporated including authentication (including 3rd party logins), authorization, dashboard features, a variety of views to choose from for the models, and a foundation for sharing and following the models and design owners (which btw includes comments, likes, following etc.). I sincerely oppose the idea of shifting all these functionalities onto a new framework. We have already shifted from PHP to a Javascript framework in the past, and yet the project has not turned up as a complete product. In my view this year's OGV project should focus majorly on integrating all the code written in the past (the one using Meteor framework), with all the functionalities up and running, and finally (and probably more importantly) deployment. It will also include some design and implementation changes to make things more efficient and production ready. Meteor is a javascript based framework, and adding functionalities will be equally (and probably much more) easier in this case. There might be some "bad points" regarding a particular approach or using some framework, but there are always solutions to problems and that's what we all as developers work for :D. Moreover, we are far ahead from the specification phase of OGV as a product. A lot of effort has already been put up, and almost everything is already up there (not yet in the main branch though). I don't say this because I have been a part OGV development or I am really obsessed with the code I have written or anything :P , but just to make things more efficient and productive :D! Cheers! On Sat, Mar 5, 2016 at 1:51 AM, Christopher Sean Morrison <brl...@mac.com> wrote: > > (I will use Existing code as reference, as many of the functions are > deprecated, so I will rewrite it to latest version of PHP. MVC with latest > PHP will enable us to put more features quickly, in future. I think this > will be a good milestone achieved) > > Above ~4 weeks (So by Mid-term, users will see the site online.) > > > How did you arrive at that number? > > 4 weeks in a proposal timetable is generally viewed as very high risk. > Unless it’s basic research, a good proposal has a plan for what will be > worked on and accomplished every week of GSoC. > > https://360.autodesk.com/ is still in Beta phase. So we are not too late > to have these features. > > > We’re not competing with Autodesk. :) > > And some other features like Login through social media and CI Email. will > take ~1.5 week. > > I believe this already exists, but need to confirm. > > Is it okay that I implement Authentication module in CI and demonstrate ? > > Like I said, authentication may already implemented so you’ll have to talk > with some of the other guys about that. Even if it’s not, I don't think > that would make for a very good patch. A good patch / pull request > demonstrates polish and one’s ability to read and modify existing code. > Writing new code is easy. ;) > > Cheers! > Sean > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > BRL-CAD Developer mailing list > brlcad-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/brlcad-devel > > -- Regards Shubham Chauhan
------------------------------------------------------------------------------
_______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
