June 2014 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] [GSoC] Snapper Desktop Integration Weekly Report
by Oguz Kayral 15 Jun '14

15 Jun '14

Hi, Last week I worked on adding snapper config management to manta. I've also started working on changing the snapshot list action to show single snapshots as a line and group pre/post snapshots and pretty printing for snapshot userdata. I've also read documents on polkit and internationalisation. This week I'll finish working on manta with all snapper operations and start polishing & start working on desktop integration. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Git-Review Weekly Update
by Xystushi 15 Jun '14

15 Jun '14

Hi, This is a short update on this week’s progress. As I’ve mentioned in the previous update, the minimum variable version of bucketkit was completed last week. This week I started integrating it into the current git-review codebase. I’ve encountered some challenges because git-review was initially designed for github only, and in order to add in other platforms such as BitBucket and GitLab, we need to clearly separate the code that interacts with different platforms and the rest. A few other developers have done quite a lot in this direction, but there are still abstractions to be made. Another thing is the unit tests. Currently we have many tests that cover most of the code, but some of them seem like testing the implementation instead of behavior. The result is that changes to the code almost always means changes to the tests as well. I’m thus also looking at refactoring the tests. Cheers, Xu -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Playlist functionality for Music App of ownCloud - Week 7
by Volkan Gezer 14 Jun '14

14 Jun '14

Hi all, This is the report for week 7 of my GSoC project. Last week, I completed basic playlist operations such as create/edit/delete, but after a discussion with Morris, we thought of doing these actions inline, not in a separate view. For this, I needed to change the methods I use. Calling a template using the same view prevented angularJS to perform ng-click events, so I had to get help from jQuery. Now, jQuery calls our angularJS methods to perform those actions. Here are the images that explains the new inline basic functionalities: Create new playlist: http://i.imgur.com/qTzEysA.png Auto-refresh after list creation: http://i.imgur.com/RcjnVTh.png Edit selected playlist: http://i.imgur.com/nkQY19n.png As you can see, we still type the songs that we would like to add into our playlist, but this is the plan for the following weeks. Follow the updates here: https://github.com/owncloud/music/pull/233 See you next week, Best regards, Volkan GEZER volkangezer(a)gmail.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC2014] Weekly report on TSP application
by karthik senthil 14 Jun '14

14 Jun '14

Hello everyone, Last week, I completed the implementation of the 2 controllers, states_controller and transition_events_controller using gems like inherited resources and ransack. I have also designed their corresponding views to enable CRUD implementation. I added a new user role named 'admin' to have exclusive abilities to manage the State and TransitionEvent model. I have shared the screenshots of the views with my mentor for opinions and suggestions on the design. I am now writing specs to test some scenarios of these 2 controllers. Next week, as instructed by my mentor, I will be working on the interesting part of using the data in the models State and TransitionEvent to implment the state machine in models like request and reimbursement. Thank You Karthik.S 2nd Year,Information Technology NITK,Surathkal -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Re: Weekly Report [OSEM][Week 4] Event Splash Page for Visitors
by Gopesh Tulsyan 14 Jun '14

14 Jun '14

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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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=sha… >>> >>> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] [Cool Live Flash] Weekly report
by zsoltpeterbasak 13 Jun '14

13 Jun '14

Hello everyone! This week i managed to make the environment bootable, to make a rough 'sketch'. (Well, at the moment I start the boot from my current PC, but the rest is on track. Ths will be just a minor task, integrating a boot loader (syslinux) in front of that. Testing was easier like this.) Managed to dig out all the documentation (it was a tougher task than expected) for my final set of tools. So in theory, everything is ready to go for the final round. (Which looks like the longest task so far.) The final step of the drive, which is the automatic discovery of images (simple) + menu system (simple), mount (done), boot (test needed). I have everything written down (like commands, doc, etc), but testing requires some time. I'm working as hard as I can, to make up for make something runnable/testable as soon as possible. Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project][GSOC][MATE]weekly report: ePub support in Atril
by avishkar gupta 13 Jun '14

13 Jun '14

hi, This is my weekly report for week 3 of coding for my project where i add ePub support to Atril, the MATE document viewer.This week i planned on getting a basic ePub up and running, but due to a coding error that got the better of me for two days, i am still working on that, as on where that leaves us, i overhauled the xml parsing functions,and ended up with much better code. I am done with all helper functions, and am now focusing completely on getting the code working inside Atril.Once this is done Mathjax integration should be simple, and although a week over my first project goal still i would be able to get this done in the week. As usual to follow my progess in the project please check out the ePub branch in my repository: https://github.com/rootavish/atril/tree/epub regards, Avishkar Gupta -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 1

[opensuse-project] [gsoc] Weekly status report - MATE gstreamer project
by Michal Ratajsky 13 Jun '14

13 Jun '14

Hi, this is my seventh weekly status report for my GSoc project. This week I continued working on my mixer library. I did a large amount of work on the PulseAudio backend and made several previously unexpected but neccessary changes to the public api. Apart from that the library now also includes early gtk-doc documentation. The library still has some unfinished spots, but I hope to sort them out during the weekend and finally start working on porting the applications on Monday as planned. As always, you can see the code on https://github.com/mratajsky/libmatemixer Thank you, Michal -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [gsoc] week 24 - MATE caja extension project - alexandervdm
by Alexander van der Meij 13 Jun '14

13 Jun '14

Hi, For my GSoC project, I will be working on caja, the file manager for the MATE desktop. My primary goal is to extend its extensions functionality to allow runtime (de-)activation of individual plugins, and to create an extension management system to allow more complex extensions. Last week I started working on the five implementation steps required for the main goal of my project. Unfortunately, I underestimated the amount of work that was required, in particular for the later steps. As such, I did not manage to complete it. Currently, I have almost finished step 3, and I hope to complete it before or on Monday. At that point I will commit my code to github. I should be able to finish all the steps before my last update. 1. Extend the default gsettings schemas to create a subcategory for extensions -modify libcaja-private/org.mate.caja.gschema.xml 2. Make the load_module_dir() procedure keep track of extensions found in CAJA_EXTENSIONDIR. Add new modules to the config (gsettings), and load known modules depending on their enabled/disabled status in said config. -modify libcaja-private/caja-module.c 3. Create new GUI tab in "File Management Preferences" to list available extensions and allow changing of their enabled/disabled status. -modify caja-file-management-properties.[c|ui] 4. Modify load module procedure to allow loading/unloading extensions during runtime. -modify libcaja-private/caja-module.c -modify individual gui elements insertion functions (caja-window-menus.c and such) 5. Allow extensions to expose a proper name, so we don't have to identify them by their module filename ('example.so') in the GUI. With kind regards, Alexander van der Meij alexandervdm @ freenode -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Zorp LBaaS driver for openSUSE
by Péter Vörös 13 Jun '14

13 Jun '14

Hi all, This week I've tested the existing Chainers in Zorp, which are providing the load balancing opportunity in Zorp. I've also implemented the source IP based load balancing strategy, and covered it with unit tests. Next week I continue to implement the other strategies, and I also plan to do some refactoring, and fix some old tests that are failing now. >From now on, you can always check my results at: https://github.com/VPetyaa/zorp/tree/upstream Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 15:00 UTC
by openSUSE Meeting Reminder 10 Jun '14

10 Jun '14

Hello all, The biweekly project meeting will be held tomorrow at 15:00 UTC in #opensuse-project on freenode. Everybody is invited to join and participate! Find out what time the meeting will be in your timezone: http://timeanddate.com/worldclock/fixedtime.html?day=11&month=6&year=2014&h… Agenda of the meeting: http://en.opensuse.org/openSUSE:Project_meeting#Agenda_for_the_next_meeting If you cannot participate and want a specific question to be answered during the meeting, please add your question to: http://en.opensuse.org/openSUSE:Project_meeting#Questions_Section Minutes and logs of previous meetings can be found at: http://community.opensuse.org/meetings/opensuse-project/ Thanks, -- openSUSE Meeting Reminder -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Snapper Desktop Integration Weekly Report
by Oguz Kayral 09 Jun '14

09 Jun '14

Hi, I'm sending a late report this week as I've been busy with some personal troubles for the last few days, which might continue this week :( . I did the ui for snapshot diff and continued working on getting snapper actions available on snapper-gui (which is called manta now). I will be working on features to manage configs (create config, delete config etc.) this week. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Git-Review Weekly Update
by Xystushi 07 Jun '14

07 Jun '14

Hi, This is a short update on this week’s progress. I’ve completed a minimum variable version of bucketkit that has all features needed by git-review. More specifically, Commits: * get a repo’s commits * get single commit * get a commit’s comment(s) * approve a commit Pull requests: * get a repo’s open pull requests * get single pull request * get commits for a pull request * get comments for a pull request * get the diff for a pull request * get the activities for a repo or pull request * send new pull request * approve a pull request * accept and merge a pull request * decline and delete a pull request From now on, I will shift my development focus back to git-review. Next week I’ll start integrating bucketkit into git-review. Cheers, Xu -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] [Cool Live Flash] Weekly report #6
by zsoltpeterbasak 07 Jun '14

07 Jun '14

Hello everyone! I spent this week reading documentation, building a test environment, and of course, building a pre-pre-...-alpha product that can be ran, tried, etc. So far, things are going well. Blog is also updated. I will switch to under promise and over deliver policy. So no promise for next week, but I will try my best to deliver. Good luck for the other GSoC members as well! Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC2014] TSP Application - Weekly Update
by karthik senthil 07 Jun '14

07 Jun '14

Hello everyone, Last week, I worked on both testing the 2 models that I had added, and designing the controllers for the same. In the beginning of the week I wrote some specs to pass the validations in the State and TransitionEvent models.After which, upon the suggestion of my mentor, I wrote a spec(and fixtures) to verify that these 2 models( and their associations) comply with the current request machine's workflow. After these tests, I moved on to designing the controllers StatesController and TransitionEventsController to implement CRUD feature in the 2 models. I referred back to my mentor for suggestions on new gems and methods to be learnt for designing controllers, as a result of which, I learnt the usage of many important gems like inherited_resources,cancancan,simple_form and ransack. These gems have simplified the ideas and thought me the actual principles of Rails developement i.e DRY and RESTful approach. I'm now working on implementing these 2 controllers and accordingly design the views for the same. Thank You Karthik.S 2nd Year,Information Technology NITK,Surathkal -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Re: Weekly Report [OSEM][Week 3] Event Splash Page for Visitors
by Gopesh Tulsyan 07 Jun '14

07 Jun '14

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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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=sha… >> >> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [gsoc] Weekly status report - MATE gstreamer project
by Michal Ratajsky 06 Jun '14

06 Jun '14

Hi, this is my sixth weekly status report for my GSoc project. This week has been rather problematic for me as most of it I was otherwise occupied. I managed to do some PulseAudio backend related work in my library and add some API pieces, but it was much less than I intended to do. However, I now consider the public API pretty much ready to go and for the next week I plan to focus solely on the PulseAudio backend work. I still believe I will have the library ready for a test run at the end of the next week as planned. The latest GitHub commit is very large, but that is mainly because it also contains unfinished work from last week with this week's fixes. Thank you, Michal -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Zorp LBaaS driver for openSUSE
by Vörös Péter 06 Jun '14

06 Jun '14

Hi all, This week as I planned, I finalized the packaging of the newly released Zorp GPL 5.0. Now as you can see, all the Zorp GPL 5.0, and related things are packaged to RPM as well. Also in this week after I finished the packaging stuff, I started to implement the missing load balancing strategies. There is no showable result yet, but at least by the end of the next week I will be able to show you my results. Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] Playlist functionality for Music App of ownCloud - Week 6
by Volkan Gezer 06 Jun '14

06 Jun '14

Hello again, As you might remember, last week I completed Listing hardcoded playlists with hardcoded songs. See the last week's progress here [0]. This week's task was to fetch those lists from the database. For that, I started using Restangular API to sent Rest API Restful Resources easily. - As the first step, I used sqlite3 to add the manual entries to the database (In community bonding period, I have already added the new table to the database) and fetched them to show the same lists that we had in hardcoded way. - The second step was to get the song list written in database and display them on the page. After those steps, I had enough time to implement basic Playlist functionality such as adding, renaming and deleting playlists. I also enabled a simple way to update the songs which you would like to have in the playlist. Here is the new playlist creation page: http://i.imgur.com/xu6bQMb.png And this is the playlist view that lists the songs and allows to do some basic playlist operations (simply click on a listname to open the view): http://i.imgur.com/PNRfY0k.png To delete a list, simply click on x next to the list name. If you would like to try it out, you can go here [1] and use the new-playlist branch in the repository. The newly added playlists will have two songs assigned with 1 and 2 which can be edited as I mentioned. Next week, I will be working on playing the songs one after each other which does not work with the current status. [0] http://volkangezerr.scienceontheweb.net/icerikgoster.php?tur=ownCloud&id=29… [1] https://github.com/owncloud/music/pull/233 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [gsoc] week 23 - MATE caja extension project - alexandervdm
by Alexander van der Meij 06 Jun '14

06 Jun '14

Hi, For my GSoC project, I will be working on caja, the file manager for the MATE desktop. My primary goal is to extend its extensions functionality to allow runtime (de-)activation of individual plugins, and to create an extension management system to allow more complex extensions. Now that my exams are over, I could finally devote myself to my GSoC project. At the beginning of this week, I continued work on my example extensions. I now have a full set of extensions that demonstrate most if not all of the functionality made possible through libcaja-extension. Now that I understand the process better myself, I have also begun writing much-needed documentation on this subject for future extension developers. In the later part of the week, I have begun with the changes required to caja for the main goal of my project. I hope to finish implementing the following five steps in the coming days: 1. Extend the default gsettings schemas to create a subcategory for extensions -modify libcaja-private/org.mate.caja.gschema.xml 2. Make the load_module_dir() procedure keep track of extensions found in CAJA_EXTENSIONDIR. Add new modules to the config (gsettings), and load known modules depending on their enabled/disabled status in said config. -modify libcaja-private/caja-module.c 3. Create new GUI tab in "File Management Preferences" to list available extensions and allow changing of their enabled/disabled status. -modify caja-file-management-properties.[c|ui] 4. Modify load module procedure to allow loading/unloading extensions during runtime. -modify libcaja-private/caja-module.c -modify individual gui elements insertion functions (caja-window-menus.c and such) 5. Allow extensions to expose a proper name, so we don't have to identify them by their module filename ('example.so') in the GUI. With kind regards, Alexander van der Meij alexandervdm @ freenode -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] rsync.opensuse.org not current?
by Jim Henderson 03 Jun '14

03 Jun '14

This question has come up on a couple mailing lists, but I haven't seen any answer yet.... Is rsync.opensuse.org not syncing properly? It seems to not have the obs repos in sync (for example, the Virtualization repo is current through April 14, 2014 or so). I've just noticed, though, that the repo at rsync:// anorien.csc.warwick.ac.uk/opensuse-distribution/repositories/ Virtualization/openSUSE_13.1 is more current (as of a couple days ago at the most). Is this a known issue and being investigated? Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [GSoC] [Cool Live Flash] Weekly report #5
by zsoltpeterbasak 01 Jun '14

01 Jun '14

Hello everyone! Change of plans since last week. No alpha/preview build. We had a voip session with my mentor and we talked over things. So at the moment I'm digging deep in the new software, trying to move forward. The blog will have new entries as soon as I'm done / get anything to blog about. (E.g.: A more complete result.) Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0