[opensuse-project] Re: Weekly Report [OSEM][Final Week] [GSoC]Event Splash Page for Visitors

Hello Community, This week I completed the deleted user feature and added some docs for delated jobs and wrote a scripts to start and stop delayed jobs worker on deployments. Well this is the final weekly report for the GSoC work that I have done so far. For the first part I implemented the splash page as proposed in my project for OSEM application.And I am happy to see that is already being used by ownCloud for their conference and soon it will be used by openSUSE Asia Summit. For the second part I implemented email notifications and markdown for all description fields, took up GitHub issues solved bugs, changed design of the splash as said by other community members. Well I guess still the work is not over, I don't want it to get over and take up new things.I want to keep contributing as I am already a part of this awesome community.The work will go on, and we as team will make this application even popular so that it is used by more number of people for their conferences. Of all thanks to my mentor James Mason and Cornelius Schumacher for their constant support and help.I would also like to thank Henne , Artem, Christian, Stella for correcting me whenever I was wrong. Thank you it has been a great experience so far, I want to keep up this spirit and continue coding for this application. Happy Hacking!! :) Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur On Mon, Aug 11, 2014 at 1:04 AM, Gopesh Tulsyan wrote:

Hello Community, This week I fixed some issues that were pending with the splash like the splash layout bug for consistency with the OSEM app, the fix for the routing to the home page if the conference is not made public when the splash url is explicitly accessed instead of giving 404 error.Well the email settings merge is still pending as James wanted me to optimize a rails ORM query.On a different note I started user deletion afresh in here https://github.com/gopesht/osem/compare/user_deletion .

Well I am planning to add some documentation about my work for splash additions to OSEM next week. Also make some progress with user deletion and implement the keynote speakers feature.

Happy Hacking !!! Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur

On Sun, Aug 3, 2014 at 10:40 AM, Gopesh Tulsyan wrote:

...

Hello Community, This week as I completed the email notifications, only the last one is left that is, send emails on price of ticket change to all participants.The github issue where the registration date update mail should only go to people who are subscribed and not registered is closed now.I did some refactoring with the routes to subscribe/unsubscribe for email notifications as suggested by James, still in pipeline.I completed github issues for splash layout (https://github.com/openSUSE/osem/pull/412) and fixed the template error which was throwing on creating a new user from the admin interface, https://github.com/openSUSE/osem/issues/380 .

Next Week, I plan to implement delete user feature as decided by Henne, as discussed in https://github.com/openSUSE/osem/issues/383 . I plan to implement the keynote speakers, preview feature of the splash for admins after filling up components, fix https://github.com/openSUSE/osem/issues/309 .Also redesign the splash settings if possible in the admin interface to make it look like a APP rather than a CMS as suggested by Henne. Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur

On Sat, Jul 26, 2014 at 8:26 PM, Gopesh Tulsyan wrote:

...

Hello Community, This week I finished Email Notifications with all refactoring and suggestions by Henne and other members and by mentor James.I finished the first four notifications with delayed_jobs integration.I also added a subscribe button in the button list for conference partial in the home page for logged in users.The users now can subscribe/unsubscribe from notifications even if they register or submit a proposal.I thoroughly tested the subscribe feature in combination with registration.

I also did some code clean-up to DRY things in email_settings.rb model.One thing that is left is to add markdown to the email templates, that I will do and complete the notifications with the last one that is still remaining.

The commit are still in review https://github.com/openSUSE/osem/pulls/gopesht .Most probably, they will be pushed by start of next week, then I will take up Github issues that are referenced for Splash Page and other parts of OSEM.

Well this bit for this week. Happy Hacking :)

Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur

On Sat, Jul 19, 2014 at 8:19 PM, Gopesh Tulsyan wrote:

...

Hello Community, Well, this week was really busy for me, I had to go college twice for my registration purposes and room allotment and it consumed 2 working days of the week.Still James co-operated with me and I have pushed the remaining notifications, they are currently in review.I am just left with one more notification from the list that I mentioned last weekend.Delayed job integration is still pending.

On a different note, I have some github issues pending for the splash and work that I have done which was found as bugs.So I wish to spent the next week completing the github issues, integrate delayed jobs or any background queuing gem for sending emails and complete the notifications.

As per my proposal, I discussed with James, we are not using redis in the production and so we will not intrgrate any in-house notification system for OSEM. Rather, I will have to discuss other feature that I can implement in time and would also write some documentation of using the splash.

That's all this week!! Happy Hacking :) Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur

On Sun, Jul 13, 2014 at 8:56 AM, Gopesh Tulsyan wrote:

...

Hello Community, This week I started with email notifications. James said the listed 5 notifications * Notify all participants when Conference dates/Registration dates are updated.Highlight dates. * Notify all participants when venue is changed.Highlight address and Venue name. * Notify all participants when a supporter level added.Also to notify, when the price of the supporter level in changed. * Notify all participants when Call for papers dates are added/updated. * Notify all participants when the schedule is made public.

are good to go.So I completed the first and the second, both are in pipeline and is not merged yet.The other thing I thought while implementing is that it takes lot of time to send email to participants in the middle of updating the conference for the first (say).So sending emails while updating data is a really bad idea, so I thought of putting these in the background jobs, well in layman terms Queue them to get processed later so that the UX is not hampered.

I thought of using https://github.com/collectiveidea/delayed_job . But using this didn't seem to worked well.The emails are getting delivered without using the gem and on using it is throwing errors. So major time went on fixing this and still I am not been to fix this issue.I worked with James and it figured out that for new emails I should first write tests and then reproduce the error that I got with delated_jobs on specs.

So probably, I try to finish email notifications with the gem.Well, that's all this week.

Happy Hacking!!! :) Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur

On Sat, Jul 5, 2014 at 11:56 PM, Gopesh Tulsyan wrote:

...

Hello Community, This week I finished the remaining components: Gallery and Footer and added Markdown for description fields that are rendered in the splash.The gallery is designed such that the splash page load is not affected.When the user clicks the "Gallery" button for the first time, the photos are loaded in a modal with the carousel via AJAX.After that for preceding clicks only the modal is invoked, until the page is refreshed. I did this by keeping a countdown variable in Javascript.

For the footer I just made a up-arrow button which is displayed when the user scrolls down length of 100px.On clicking the button the user is taken to the topmost component, i,e the banner via smoothscroll.So the navigation and UX is built properly by using animation, tabs on the header and a button at the footer.

I implemented markdown for only description fields that are rendered directly on to the splash.I did this using redcarpet gem and also added bootstrap-markdown(toopay) editor for description fields so that easily markdown tags are added by click without any hassle.

Next week, I will start with email notifications.I have listed some notifications on my Trello board as suggested by James, to keep track of things.I still has to discuss what notifications are relevant to be sent.

Well thats it!! for this week. Happy Hacking!! Gopesh Tulsyan ROR Enthusiast, Final Year Information Technology, National Institute of Technology, Durgapur

On Sat, Jun 28, 2014 at 11:12 PM, Gopesh Tulsyan wrote: > Hello Community, > I happy to say that I passed my mid-term evaluations, thank you for > the support and guidance so far. > > This week I integrated a theme inspired by onassis of > http://www.blacktie.co(license http://www.blacktie.co/about-themes/). > I also integrated FontAwesome(license > http://fortawesome.github.io/Font-Awesome/license/) and smoothscroll > for better effects and animation for the splash.Although I am open any > kind of addition to view level be it animations, assets, layouts.My > mentor said that theme would be generally changed by the admins using > OSEM, so I wrote only one css file for the time being, if time is left > I can write one more theme for the splash. > > So I am left with three components(Press, Footer and Gallery) which I > will finish and push next week and as per my proposal I would be > working on Email Notifications. The email notifications needs > attention because whenever a conference is updated there is no check > which part is updated and the participants are not informed about the > update which is very essential. > > This is the link to the folder Week 6, which contains some snaps with > theme implemented. > > https://drive.google.com/folderview?id=0B8TQsfyoffN5cWNPaUU1OE1UWms&usp=sharing > > Happy Hacking :) > > Gopesh Tulsyan > ROR Enthusiast, > Final Year Information Technology, > National Institute of Technology, Durgapur > > > On Sat, Jun 21, 2014 at 4:41 PM, Gopesh Tulsyan wrote: >> >> Hello Community, >> This week I completed the Location component with lodgings and added a >> banner component to the splash.This banner component is in place of >> carousel, it contains a background image, conference title, start-end >> dates and description. >> >> I also added the checkboxes for each component in admin dashboard as >> decided previous week, so that admins/organizer now can enable the >> component on the splash when they think it's completed.On a different >> note, we locked down on the carousel to be implemented as gallery in a >> lightbox.This enabled me to use the carousel code that I have written >> for taking photos for carousel. Only thing I have to do for gallery is >> to make the frontend the backend code for taking photos form the admin >> dashboard is merged. >> >> Next week is mid-term evaluation.Next, I will implement some styling >> onto the splash as decided by James.This won't take much time as I >> have to implement styling by looking at the themes.However, James and >> I decided that I will next improvise the email notifications as >> mentioned in my proposal.The email notifications have to implemented >> in a way so that the Users attending the Conference are aware about >> each and every update that the admins make to the conference and these >> mails will be fired by the admins explicitly. >> >> Some snaps of the splash page with test data are attatched. >> >> Google Drive link to the folder ----> Splash till Mid-Term(folder name)Week 5 >> https://drive.google.com/folderview?id=0B8TQsfyoffN5UF8yMno4S3ZvTTg&usp=sharing >> >> Happy Hacking!! >> >> Gopesh Tulsyan >> ROR Enthusiast, >> 3rd Year Information Technology, >> National Institute of Technology, Durgapur >> >> >> On Sat, Jun 14, 2014 at 9:34 AM, Gopesh Tulsyan wrote: >> > Hello Community, >> > This week was less work and more review.My mentor was not well so I >> > got my components reviewed later this week.However, the Sponsor and >> > Social Media components are merged now.I need to little refactoring >> > with with Location component and that will be merged too. >> > >> > Well I did the carousel component but Henne said that carousel are >> > useless so indeed we decided to have fold as in >> > https://conference.opensuse.org/index.html#home. >> > and we discussed here >> > https://github.com/openSUSE/osem/pull/222. >> > >> > So on discussing with James I have to redo this component again. >> > >> > Next Week Plans: >> > Right now there is no admin check on the components like whenever the >> > data for components are entered in the admin dashboard for the >> > conference they are rendered.So I will go ahead and create checkboxes >> > for each and every component so that the components are only visible >> > in the splash when the admin/organizers wants them to be displayed. >> > >> > Happy Hacking!! >> > Gopesh Tulsyan >> > ROR Enthusiast, >> > 3rd Year Information Technology, >> > National Institute of Technology, Durgapur >> > >> > >> > On Sat, Jun 7, 2014 at 9:54 AM, Gopesh Tulsyan wrote: >> >> Hello Community, >> >> >> >> This week I completed the remaining components namely Sponsors, Social >> >> Media, Location with Lodging.The sponsor component involved in >> >> building a dashboard which was is currently absent in OSEM. Similarly, >> >> lodging component involves building a lodging dashboard under Venue >> >> section.The social media involved addition of fields in conference >> >> section to take urls for the conference in different social media like >> >> Google+, Twitter and Facebook. >> >> I built these components in pieces so that my commits are atomic, >> >> following the coding style suggested by James. >> >> >> >> These components are currently in review, once reviewed and merged I >> >> will focus on the style and theme integration. >> >> >> >> That's all this week. Happy Hacking! >> >> >> >> Gopesh Tulsyan >> >> ROR Enthusiast, >> >> 3rd Year Information Technology, >> >> National Institute of Technology, Durgapur >> >> >> >> >> >> On Sat, Jun 7, 2014 at 9:46 AM, Gopesh Tulsyan wrote: >> >>> >> >>> Hello Community, >> >>> >> >>> This week I completed the remaining components namely Sponsors, Social Media, Location with Lodging.The sponsor component involved in building a dashboard which was is currently absent in OSEM. Similarly, lodging component involves building a lodging dashboard under Venue section.The social media involved addition of fields in conference section to take urls for the conference in different social media like Google+, Twitter and Facebook. >> >>> I built these components in pieces so that my commits are atomic, following the coding style suggested by James. >> >>> >> >>> These components are currently in review, once reviewed and merged I will focus on the style and theme integration. >> >>> >> >>> That's all this week. Happy Hacking! >> >>> >> >>> Gopesh Tulsyan >> >>> ROR Enthusiast, >> >>> 3rd Year Information Technology, >> >>> National Institute of Technology, Durgapur >> >>> >> >>> >> >>> On Sat, May 31, 2014 at 2:09 PM, Gopesh Tulsyan wrote: >> >>>> >> >>>> Hello Community, >> >>>> This week my previously built components were reviewed by the OSEM >> >>>> maintainer Henne and my mentors James & Cornelius. James pointed out >> >>>> my mistakes I had done while coding those components.I had built these >> >>>> segments in a way that was hard to review, as well as my code was >> >>>> redundant as I was doing lot of compound work. So James thought me to >> >>>> do cherry-pick commits(for those pieces which I require in multiple >> >>>> components and which is not yet merged), so that my commits are more >> >>>> granular and atomic.Out of the five components Sponsors is still >> >>>> pending to reviewed, but the rest four(Header, Program, Registration, >> >>>> Cfp) are merged now. I did the components again in small patches which >> >>>> was easily reviewed and was merged. >> >>>> >> >>>> >> >>>> So I faced problems this week in understanding the procedure to code >> >>>> in a way that is accepted.My logic was clear, but I was not following >> >>>> the norms due to which I had to redo my work. I am still working on >> >>>> the coding style suggested by James. >> >>>> >> >>>> Since the larger chunks are over I plan to complete the remaining five >> >>>> segments the upcoming week, so the structure of the splash page with >> >>>> all the data is in place.And to test the splash page with test data so >> >>>> that it doesn't break in any possible case. >> >>>> >> >>>> That's all this week, my progress on OSEM can be found in >> >>>> https://github.com/gopesht/osem .Here's the link to drive folder >> >>>> >> >>>> OSEM Event Splash Page for Visitors Week 2 updates snaps -> >> >>>> https://drive.google.com/folderview?id=0B8TQsfyoffN5emVsNzAzV1VVZFE&usp=sharing >> >>>> >> >>>> Happy Hacking!! >> >>>> >> >>>> Gopesh Tulsyan >> >>>> ROR Enthusiast, >> >>>> 3rd Year Information Technology, >> >>>> National Institute of Technology, Durgapur >> >>>> >> >>>> >> >>>> On Sat, May 24, 2014 at 12:52 PM, Gopesh Tulsyan wrote: >> >>>> > >> >>>> > Hello Community, >> >>>> > This week I had built three components namely Program component, Call >> >>>> > for Papers component and Registration component for the splash page. I >> >>>> > had built these components as a whole, both the frontend and >> >>>> > backend.Migrations for the missing attributes are done for the proper >> >>>> > display of these components.These components are designed with >> >>>> > conditional rendering of attributes so that the splash doesn't break >> >>>> > if one or more attributes are blank. >> >>>> > >> >>>> > What I intentded to do this week according to my proposal -> >> >>>> > Create models and associations, and decide what all can be given to >> >>>> > the admin to customize the splash page apart from the things discussed >> >>>> > above.Test with one sample conference how things are working. >> >>>> > >> >>>> > So the initial base is setup, the features(components are already >> >>>> > decided and it in the trello board as told by my mentor james).The >> >>>> > backend modeling are being done simultaneously as I will build these >> >>>> > components. >> >>>> > >> >>>> > Though I had this components, but they are still in review. I will >> >>>> > make suggested changes as will be told by my mentors James & >> >>>> > Cornelius. >> >>>> > Also as James suggested to built the structure of the components with >> >>>> > plain and simple layout, rather than focussing on styling and looks. >> >>>> > As when the data will be in place with the desired components, then I >> >>>> > will intregrate some themes to beautify the splash page. >> >>>> > >> >>>> > What I intent to do next week-> >> >>>> > Currently, the sponsor dashboard is missing, and we require the >> >>>> > sponsor component for the splash.So I will first built the sponsor >> >>>> > dashboard with the modeling suggested by James.After that I will go >> >>>> > ahead and build the remaining components in the trello board. >> >>>> > >> >>>> > Happy Hacking! >> >>>> > >> >>>> > Gopesh Tulsyan >> >>>> > ROR Enthusiast, >> >>>> > 3rd Year Information Technology, >> >>>> > National Institute of Technology, Durgapur >> >>>> > >> >>>> > >> >>>> > On Sat, May 17, 2014 at 8:28 AM, Gopesh Tulsyan wrote: >> >>>> > > Hello, >> >>>> > > This week I learnt testing, some basics and written controller test >> >>>> > > for admin/users, feature test for users, volunteers.I will be writing >> >>>> > > more tests for views as suggested my mentor James Mason.He tells >> >>>> > > writing view specs will make me implement my features better.I had >> >>>> > > also fixed bugs while testing like modal view in admin/users page, >> >>>> > > display users in admin/users page, fix attachment for proposals. >> >>>> > > I also reviewed and and added navigation for event splash page(initial kick-off) >> >>>> > > Tasks for the next week -> >> >>>> > > Write view specs, and start building components as mentioned in trello >> >>>> > > board for my GSoC project. >> >>>> > > >> >>>> > > Happy Hacking! >> >>>> > > Gopesh Tulsyan >> >>>> > > ROR Enthusiast, >> >>>> > > 3rd Year Information Technology, >> >>>> > > National Institute of Technology, Durgapur >> >>>> > > >> >>>> > > >> >>>> > > On Fri, May 9, 2014 at 9:04 PM, Gopesh Tulsyan wrote: >> >>>> > >> I recently pushed a commit to kick start my GSoC project.The commit >> >>>> > >> consisted of a view displaying just the title of the conference.This >> >>>> > >> is the result of clicking the event on the home page. >> >>>> > >> >> >>>> > >> I had also setup the trello board where James assigned tasks to me such as >> >>>> > >> 1) Read the Ruby on Rails Guidelines for selected topics. >> >>>> > >> 2) Asked me to see 20 splash pages and figure out the components to >> >>>> > >> create a list for the OSEM splash page. >> >>>> > >> >> >>>> > >> Currently, I am done with the listing of the components and waiting >> >>>> > >> for the review.I am continuing with the guides. >> >>>> > >> >> >>>> > >> Looking forward to a great summers ahead. >> >>>> > >> >> >>>> > >> Happy Hacking! >> >>>> > >> Gopesh Tulsyan >> >>>> > >> ROR Enthusiast, >> >>>> > >> 3rd Year Information Technology, >> >>>> > >> National Institute of Technology, Durgapur >> >>> >> >>> -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org