August 2014 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] How we will use the GSoC money
by Vincent Untz 18 Jul '24

18 Jul '24

Hi, (let's see how a public discussion about money goes :-)) The Google Summer of Code brings us great students, but also means that the openSUSE project will get $8000 (if I'm not mistaken) at the end of the summer. That's $500 per student. A while ago, I requested comments on my blog about what to do with the money, but didn't get any feedback. So I take this as "do what you feel is best", and this mail is about the plan. As a reminder, the main issue is that we will likely not have the openSUSE Foundation created in time for this. For instance, Google would like us to get some form filled before the end of June; this is not a mandatory timeline, but I think it shows that we won't be ready with the Foundation for that. The current plan is to give that money to another organization we feel close to, and I have two candidates in mind: - the Software Freedom Conservancy (http://sfconservancy.org/) it's a really nice org that provides a home for various cool projects (see http://sfconservancy.org/members/current/) and those projects help make openSUSE a great project. - the Desktop Summit (https://www.desktopsummit.org/) it's one of the biggest event this year, and this would help us have some more visibility (since we'd be sponsors, I guess). I'm sure they would welcome this to secure their budget. Note that an alternative solution would be to leave the money to Google for a future GSoC or similar program, but I feel it's better to use the money where it can make a difference today. Now, it's not too late to change the plan. If you have a better suggestion, please tell us. There's no need to argue forever about it, just explain why you think it's good. Keep in mind that if we cannot receive the money ourselves, this also means that we cannot use it to buy stuff for openSUSE. Pavol and I will take the final decision since we are the GSoC admins for openSUSE. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

22 38

[opensuse-project] opensuse-user not on gmane any more?
by Jim Henderson 19 Nov '14

19 Nov '14

I just noticed today that the gmane.linux.suse.opensuse.user group is missing from gmane.org - did the project request the list be removed from gmane? Just wondering if it was intentional or if something went wrong somewhere. Thanks, 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

10 24

[opensuse-project] Login to news.o.o not working properly
by Jim Henderson 26 Aug '14

26 Aug '14

It seems that this site does the normal/expected redirect to Attachmate's authentication system, but then it redirects after success to a Wordpress login. Can someone look into what's going on there? 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

3 15

[opensuse-project] GSoC: MATE gstreamer project
by Michal Ratajsky 21 Aug '14

21 Aug '14

Hello everyone, I had the opportunity to work on the 2014 MATE GSoC project aimed on providing a replacement for deprecated GstMixer functionality, used by the mate-media and mate-settings-daemon packages. *** The state before my project: The mate-media package used to provide two distinct volume control applications. A more modern PulseAudio-based one called MATE Volume Control and a legacy GstMixer-based one. The reason for supporting two separate volume control applications was portability. The newer PulseAudio-based application relies on having functional PulseAudio support in the operating system and many (especially BSD) systems choose not to use PulseAudio by default and prefer the legacy GstMixer-based application instead. The main problem with GstMixer is that it used to be a part of the gstreamer package, which was removed from gstreamer in version 1.0 and the application relies on the now unsupported version 0.10. This creates maintenance overhead as it requires operating systems and distributions to keep providing packages of an unsupported library. My project was based on the idea of removing the legacy GstMixer-based application from MATE and improving the newer PulseAudio-based one to support other sound systems as well. The newer application contained a somehow separable PulseAudio support code, which was also duplicated in mate-settings-daemon to provide support for multimedia key actions (changing volume and muting). I decided the best approach would be to develop a new library, providing an abstraction layer for PulseAudio and other sound systems and allow both the volume control application and the settings daemon to use this library instead of duplicating the existing PulseAudio support code. I also decided to write the library from scratch, using ideas from both the PulseAudio support code in the applications and also from GstMixer. *** How my work progressed: At the start of my project I created a library called libmatemixer. Designing a reasonable API for the library turned out to be very challenging as there are big design differences between PulseAudio and other sound systems. The volume control application also uses many PulseAudio features, which are not available in other sound systems. The approach I took was to make the API initially resemble the existing PulseAudio support code, but in a more robust way to make room to later support at least ALSA and OSS sound systems without requiring larger design changes of the API. Even so, I couldn't avoid changing and rethinking the API design several times during the project as there were always cases where some parts just didn't fit. I'd say this was one of the major struggles I had with the project. Each time you see a well designed API, it may make you think that it must be so easy to design such thing yourself, but I learned the hard way that it is not :) During the first half of the coding period I made the library fully functional with most PulseAudio features working and I did some initial work done on porting the applications. I managed to follow my project schedule almost exactly as I planned it. The second half turned out to be much more challenging. I spent much more time on the project (some days 12-16 hours a day including most weekends), but as the code became more complex, the progress was much slower than I anticipated. At first I continued porting the applications until I got them into a reasonable shape. I took more time with the volume control program, cleaning it up, rewriting some parts to better match libmatemixer design, removing dead code and improving GTK3 support (which wasn't really a part of the project, but the idea of making user-visible changes was very tempting :) Then I moved back to libmatemixer and started working on supporting the ALSA and OSS sound systems. I added initial support for both of them fairly quickly, in less than 2 weeks, but making them fully functional took me pretty much another month of time (mainly due to making API changes in libmatemixer, incomplete documentation of both sound systems and OSS differences on Linux/FreeBSD/other BSDs). I also spent about a week looking into OSS version 4, but after seeing how difficult it is to map OSS4 mixer elements to libmatemixer, I decided to postpone it and later abandoned it completely. About 2-3 weeks before the end of the coding period, I finally started cleaning things up and adapting the PulseAudio code and the applications to the API changes I made while working on ALSA and OSS. This was the most difficult time for me, I still kept finding API inconsistencies, thinking, rethinking, and my progress was very slow. As I had to spend most of the polishing time fixing problems, the code didn't receive as much testing and polishing as I wanted to, but I managed to complete it and with several late fixes, I can say that the code works very well. *** So what is libmatemixer like? The libmatemixer library makes heavy use of GLib and GObject libraries and is written in the C programming language. I have taken care to provide an easy to use API, which will be familiar to programmers experienced with PulseAudio or GstMixer. My intention was to make the library dynamic, flexible, robust, extensible, make good use of GObject features (properties and signals) and follow the OOP principles. Support for each sound system is provided as a dynamically loaded module (a plugin) and allows for individual modules to be packaged separately. While the supported sound systems differ greatly in functionality, they share a single abstract API and their capabilities can be queried dynamically by applications. They also don't need to worry about which sound system they are running on (though the library tells them if they ask). The library provides one main entry point to communicate with a sound system, called a Context. Context can be associated with some particular sound system or it can select a working sound system automatically. When done so, the Context can be used to query the system for a list of sound cards and streams (described in the next paragraph). Most sound cards are capable of providing sound input (recording) and output (playback), in libmatemixer, these input/output "channels" are called streams. Streams may not only be found on sound cards, but a stream may for example exist to output sound over a network (this is possible on PulseAudio and supported by libmatemixer). Each stream can contain an arbitrary number of volume controls and switches. Volume control is simply a volume slider with any number of channels. Depending on the sound system, controls can have readable/writable volume, a mute toggle and may even support peak level monitoring. Per-application volume controls, per-channel volume, decibel values, balancing, fading and volume limits are all supported. Switches can be used for example to change the active recording source of a sound card or the sound card profile on PulseAudio. All the elements in libmatemixer are dynamic, they can appear and disappear at any time (for example when user unplugs a USB sound card or starts her music player) and the library provides asynchronous notifications for all events and on all the sound systems using the GObject facilities. This was only a brief intro and a fraction of supported features. I have taken care to provide support to all features which may be useful to applications and to allow writing both PulseAudio-style mixers (such as the MATE Volume Control with a single input/output volume slider) as well as applications wanting to provide many controls at once, such as the legacy GstMixer application, XFCE mixer or KMix. As you can see, my goal was to provide a flexible library, not just to match the needs of a single application. *** Final word I must say that working on the project was challenging, but I enjoyed it a lot and it was a valuable learning experience. I hope libmatemixer will get a chance and that we can provide it as a production quality code for the next MATE release. I'd like to thank my mentors Stefano and Martin and the openSUSE program admins Manu and Saurabh for giving me this opportunity (you've all been great!) and of course everyone who followed my project (I'm sure there was at least one person hiding in the shadows). If you are interested in seeing or playing with the code, see my GitHub: https://github.com/mratajsky I keep providing fixes for the packages and they reside in a separate branch called after-gsoc, this branch contains some important fixes and will probably give you a better testing experience ;) *** But wait, we want screenshots! Cielos! Seriously? Alright, I somehow expected you'd ask, so let me show you MATE Volume Control running on libmatemixer using Pulse, ALSA and OSS (notice the differently named devices, but they are made on the same hardware and OS). https://dl.dropboxusercontent.com/u/28460082/MATE/alsa-1.png https://dl.dropboxusercontent.com/u/28460082/MATE/alsa-2.png https://dl.dropboxusercontent.com/u/28460082/MATE/oss-1.png https://dl.dropboxusercontent.com/u/28460082/MATE/oss-2.png https://dl.dropboxusercontent.com/u/28460082/MATE/oss-3.png https://dl.dropboxusercontent.com/u/28460082/MATE/pulse-1.png https://dl.dropboxusercontent.com/u/28460082/MATE/pulse-2.png https://dl.dropboxusercontent.com/u/28460082/MATE/pulse-3.png https://dl.dropboxusercontent.com/u/28460082/MATE/pulse-4.png Thank you and see you next year, 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] Today's project meeting minutes
by Robert Schweikert 20 Aug '14

20 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Meeting ended Wed Aug 20 15:19:12 2014 UTC. The log and minutes are available from: (v 0.1.4) (11:19:12 AM) bugbot: Minutes: http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… (11:19:12 AM) bugbot: Minutes (text): http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… (11:19:12 AM) bugbot: Log: http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… - -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJT9LyRAAoJEE4FgL32d2UkLSEH/1pDM0sv3z/H5P2V142WFLQA yNvOJd/LiQVP6FI1kseIOaESSSEafnK8TE5LpZA9XLjujrPcz3MdJmFs8GB8/boZ 84fTIJH5uTepOGtA/jnXCs8Q8Bc4WQXdhFLlp1KYmVpQW8zWFwBZTwyTBVRvYkRc lC1TpVdeiHwnY9XaaJI4pVKKA5v+f9Qg2zHcva36WeGXNsW4dohh+DBCicQV4JdA muybANIliwTEBzZQ2iEE2tV+4/b13/T4ia9FmJVaXXLpgM6XpPjVBGeEXUpILWOr CIWnrQAR71TCygnA8APXwC5/Sqy5VWDb3hezfa1/pshM0dMitbG7u36kwFjEnRY= =r9n/ -----END PGP SIGNATURE----- -- 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 19 Aug '14

19 Aug '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=20&month=8&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] RE: EARN $300 WEEKLY VIA AUTO VEHICLE WRAP ADVERTISEMENT PROGRAM .
by HYDRAULICS INTERNATIONAL,INC. 19 Aug '14

19 Aug '14

Ladies and Gentlemen, We are currently seeking to employ individual's world wide. How would you like to make money by simply driving your vehicle or bike advertising for HYDRAULICS INTERNATIONAL,INC. How it works ?: Here is the basic premise of the "paid to drive" concept: HYDRAULICS INTERNATIONAL,INC.seeks individual- regular citizens,professional drivers to go about their normal routine as they usually do,only with a big advert for "HYDRAULICS INTERNATIONAL,INC." plastered on your vehicle or bike.The adverts are typically vinyl decals,also known as "Auto Wraps,"that is almost seem to be painted on the vehicle or bike, and which will cover any portion of your the exterior surface. What does the company get out of this type of advertising strategy ?.Lots of exposure and awareness. The auto wraps tend to be colorful,eye-catching and attract lots of attention. Plus, it's a form of advertising with a captive audience,meaning people who are stuck in traffic can't avoid seeing the wrapped vehicle or bike alongside them. This program will last for 3 months and the minimum you can participate is 1 month.You will be compensated with $300 per week which is essentially a "rental"payment for letting our company use the space on your vehicle,boat or bike and no fee is required from you,HYDRAULICS INTERNATIONAL,INC. shall provide experts that would handle the advert placing on your mobiles. You will receive an up front payment of $300 inform of a check via courier service for accepting to carry this advert on your vehicle or bike. It is very easy and simple,no application fees required.Please do contact get back to me with the requested info below if you are interested in this offer. Full Name: Physical Address: City: State: Zip Code: Age: Make Of Car/Year: Exterior Color Of Car: Telephone Numbers: We will contact you immediately we receive this information. Kind Regards. (R) HYDRAULICS INTERNATIONAL,INC. All rights reserved (TM). -- 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][Final Week] [GSoC]Event Splash Page for Visitors
by Gopesh Tulsyan 18 Aug '14

18 Aug '14

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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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=sha… >>>>>>> >>>>>>> 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 <gopesh.7500(a)gmail.com> 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=sha… >>>>>>>> >>>>>>>> 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 <gopesh.7500(a)gmail.com> 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 <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 2014][MATE]Final Weekly Report : Epub support in Atril
by avishkar-gupta 18 Aug '14

18 Aug '14

Hi community, So today is that day when the official GSoC coding period comes to a close. Here is the final status of the project. You can read epubs with Atril. Search through epubs. Thumbnails. Dual library support at buildtime(both GTK2 and GTK3) A night reading mode(inverted colors) Conforms to both epub2 and epub3 standards (to an extent) and the usual. I am happy with the way the project turned out. Some bugs such as memory leaks at some places etc. remain, but those can be taken care of easily in the upcoming days, once the packaging problems of Gentoo are taken care of, the patch will most likely be upstreamed, and Epub support available with MATE-1.10 . For the last few days, I was working on Adding Mathjax support, but the terrible(sorry) tool that is GNU automake, I don't think that would be ready before 13:00 PST today (the 18th), so that would be a post-GSoC addition. Thanks for the opportunity to work as a GSoC student for MATE and openSUSE, and kickstarting my open source journey. If anybody's interested, I'll be writing a blog post, sort of a full lookback of the project, available at my blog rootavish(dot)github(dot)io. As usual the code is available at https://github.com/rootavish/atril.git And you can follow this discussion to see when the commits are merged with the repo: https://github.com/mate-desktop/atril/pull/84 Regards and thanks, 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] Snapper Desktop Integration
by Oguz Kayral 18 Aug '14

18 Aug '14

Hi all! I spent this week fixing some bugs, adding a few small features and making sure everything works as intended. Today we had a meeting with me mentor about the current status and the future of snapper desktop integrations. I made an image album showing how different snapper actions work with the gui client and dolphin integration https://imgur.com/a/ocPiN The code needs some refactoring, the UI needs a bit of polishing (especially the changes dialog, but I'm already working on a better design for it) but snapper actions can now be performed directly from the desktop. - Oguz -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] Re: [GSOC] OSEM Refactor user management model
by differentreality 18 Aug '14

18 Aug '14

On Sun, Jun 22, 2014 at 9:46 PM, differentreality <differentreality(a)gmail.com> wrote: > > > On Jun 16, 2014 11:00 AM, "differentreality" <differentreality(a)gmail.com> wrote: > > > > On Sun, Jun 8, 2014 at 5:41 PM, differentreality > > <differentreality(a)gmail.com> wrote: > > > On Sat, May 31, 2014 at 10:47 PM, differentreality > > > <differentreality(a)gmail.com> wrote: > > >> On Sat, May 24, 2014 at 10:30 AM, differentreality > > >> <differentreality(a)gmail.com> wrote: > > >>> On Sat, May 3, 2014 at 9:27 PM, differentreality > > >>> <differentreality(a)gmail.com> wrote: > > >>>> Hey all, > > >>>> > > >>>> I will be working (too) on OSEM for this GSOC. > > >>>> > > >>>> My project is about refactoring the user/person model and implementing roles. > > >>>> My mentors are Ancor and Artem, and we are already in touch. > > >>>> If everything goes smoothly with these changes, there might be some > > >>>> time left for me to work on more stuff too. But let's see... > > >>>> > > >>>> As Christian mentioned, recently there were several changes implemented. > > >>>> Most related bugs are fixed, and we are still working on what's left. > > >>>> In addition, we are starting to write tests, and that hopefully will > > >>>> attract more contributors too. > > >>>> > > >>>> For the user/person model part of my project, I will be changing stuff > > >>>> that could affect the other two projects too, so I hope that all 3 > > >>>> students we can be in touch and coordinate efforts on that. > > >>>> > > >>>> I will be soon making public details about the implementation of my > > >>>> gsoc project. > > >>>> As a conference organizer I do have some concrete ideas regarding how > > >>>> we should change the user/person models and what kind of roles we > > >>>> would need, but I have had some very interesting ideas coming from > > >>>> other organizers, based on their needs for their conferences. > > >>>> > > >>>> OSEM is for everyone to use, not just for openSUSE Conference, but any > > >>>> other conference or other event (smaller or bigger). As such, we want > > >>>> to try and make OSEM a suitable tool for more people. > > >>>> So any valuable input is more than welcome! > > >>>> > > >>>> Feel free to contact me directly via email or ping me on IRC, create a > > >>>> new issue or comment on github, reply to this thread... Anything works > > >>>> really :) > > >>>> > > >>>> And stay tuned for more news! > > >>>> > > >>>> Stella > > >>> > > >>> Hey all, > > >>> > > >>> a lot of changes happening to OSEM these days :) > > >>> > > >>> A feature for translation of OSEM was requested during oSC14 and > > >>> that's what I was working on before GSOC coding period officially > > >>> started as well as the first couple of days of this week. > > >>> Translation files will be uploaded at https://www.transifex.com/projects/p/osem/ > > >>> Transifex project automatically accepts anyone to join the team in > > >>> order to start translating. > > >>> There is, however, an issue with devise routing when using locales > > >>> which I still haven't figured out, as well as implementing the > > >>> translation to the models, for which I have already automatically > > >>> produced a translation file. > > >>> > > >>> In the meantime I am working on the first part of my GSOC project, > > >>> which is the user/person model refactoring. My approach is to make the > > >>> person model per conference and keep the user model just for signing > > >>> in to the application. > > >>> > > >>> That way, we can maintain the integrity of conference data as time > > >>> goes by (considering that a person does not always have the same > > >>> biography, not even the same name!) > > >>> > > >>> I am almost through making the necessary changes to the code and the database. > > >>> > > >>> What is left to do? > > >>> I still need to adjust the information shown for each user and person > > >>> so that it better depicts the new structure. Moreover I want to add > > >>> the functionality of either importing latest profile to person model > > >>> or create a new person only if something has changed. I assume people > > >>> do not want to re-enter their personal details for every single > > >>> conference (and the profile information, which is held in the person > > >>> model, is mandatory for registering to a conference or submitting a > > >>> proposal). And that's what I will be working on next week! > > >>> > > >>> Stella > > >> > > >> Hi! > > >> > > >> It has been a tricky week, half of which was occupied by an unresolved > > >> debate [1] on the need of conference-specific user data, and the other > > >> half by studying about openID implementation in rails. > > >> > > >> I seem to be on the right track of openID with the gem > > >> open_id_authenticate and the development keeps going. > > >> > > >> Stella > > >> > > >> [1] https://github.com/openSUSE/osem/issues/22 > > > > > > Hey :) > > > > > > I am finalizing openID feature, omni_auth gem turned out to be easy to > > > use, it does require, though, that you sign up as developer with each > > > provider you want to use. > > > > > > Waiting to hear back from my mentor, Ancor, for next week. > > > > Hi, > > > > I have worked on the User/Person models merge. There are a couple of > > things to finalize along with any additional comments that might come > > up from my mentors. > > > > In addition, I made some final touches to the openid feature too, > > which is progressing. > > > > They shall both be finalized this coming week, hopefully. > > > > Stella > > Hi all, > > OpenID is implemented in OSEM and some final checks and documentation are on their way. > > The user/person merge is ready, pending review for its implementation. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 3

[opensuse-project] Reminder - Last day for openSUSE.Asia Summit 2014 Travel support application and Call for Paper
by Max 18 Aug '14

18 Aug '14

openSUSE.Asia Summit Call for Paper deadline today!! Deadline 18th, Aug 2014. Submit your paper now!! * Detail: please see http://summit.opensuse.org/#cfp * conference submission tool https://events.opensuse.org/conference/summitasia14/proposal/new -------------------------------------------------------------------------------------------------------------- Travel Support Program apply deadline is 18th, Aug 2014. Today ------------------------------------------------------------------ APPLY FOR TRAVEL SUPPORT First the applicant needs to read: http://en.opensuse.org/openSUSE:Travel_Support_Program Then please send the request through: https://connect.opensuse.org/travel-support You are required to send application during Aug 1st to Aug 18th. We will review and confirm from Sep 1st to 15th. If you have any questions, please contact opensuse-summit(a)opensuse.org. openSUSE.Asia Summit team -- 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 18 Aug '14

18 Aug '14

Hello everyone, This is a brief summary of my work last week. I worked completely on running a clean build with respect to the tests and also added documentation for all the code added by me to the current repo. The app now passes all the tests and the HTML documentation(created by yardoc) is also complete. Thus the TSP application is in a stable state with the additional feature of creating/designing the state machines and then create objects of the same( like requests,reimbursements and shipments). The feature includes a seperate UI for a special user role called Admin and the generic code to dynamically create the state_machine object is available at the concern HasState. The complete code can be viewed at : https://github.com/karthiksenthil/travel-support-program/tree/gsoc2014 Thank You Karthik.S 3rd 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] Research paper: Preliminary empirical identification of barriers faced by newcomers to Open Source Software projects
by Per Jessen 17 Aug '14

17 Aug '14

Pavel Kačer posted this on yast-development: https://www.academia.edu/7628876/Preliminary_empirical_identification_of_ba… Perhaps a bit long and theoretical, but an interesting read nonetheless. -- Per Jessen, Zürich (18.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] [GSoC]Project "Add snapshot support to libvirt xenlight driver"
by David Kiarie 17 Aug '14

17 Aug '14

Hi there, Its been a *very* busy two weeks merging what I have been to libvirt master(turns out Jim is *very* strict on any piece of code getting into libvirt master. Some of the work is not yet merged though but we are working to get it merged Cheers, David. -- 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] Status on Git-Review
by Xystushi 17 Aug '14

17 Aug '14

Hi All, As it’s about the end of this year’s GSoC, I would like to give you an update on what has been done for git-review (many thanks to the creator and my mentor Dominik Bamberger) over the summer. In the first half of the summer, I created a ruby gem called bucketkit[1], which is a client for Bitbucket’s API. It is very similar to Octokit (for github), for those of you who are familiar with it. However, due to the lack of time and sufficient documentation from Bitbucket, I decided to only implement the features needed by git-review first. Hopefully this project will continue, and one day becomes a full-fledged Bitbucket API client. I welcome anyone who is interested to checkout the code and hack and improve this library together. For the second half of the summer, my main task was to integrate bucketkit into git-review by introducing the bitbucket module. Git-review was originally designed specifically for Github’s pull request workflow. Hence the biggest challenge was to identify the components in git-review that are actually provider independent and extract them into separate modules. Dominik and I worked together to refactor the code (and tests) and eventually conquered the challenge. So currently git-review not only supports two major git-hosting platforms, i.e. Github and Bitbucket, but also provides a framework such that adding support for new platforms is easy - just like writing a plugin - without the need to modify the entire codebase. Cheers, Xu — [1] https://github.com/xystushi/bucketkit -- 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 Report - Zorp LBaaS driver for OpenStack
by Péter Vörös 16 Aug '14

16 Aug '14

Hi everyone! This week passed with a lot of testing, fixing, and refactoring, finally I was able to correct all the problems I've faced with OpenStack. Finally the instances can be started in the different stack namespaces, and traffic is going through Zorp smooth. So, now the status is, that Zorp driver is fully integrated into OpenStack, it can also be selected from the dashboard. The whole load balancing works, with all of the load balancing algorithms, after the pools, members and vips are set up. So almost everything is done, I'm doing the job what is remaining. I'm writing the documentation and how-to. I'm creating a VirtualBox image, which with trying out Zorp as a LBaaS will be much easier, and faster. 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] YAPC::EU attendance and openQA lightning talk
by Alex-P. Natsios 16 Aug '14

16 Aug '14

Hello lizards, Next week i will be attending YAPC::EU[0] which this year will be held at sofia.bg If any geeko is around at the time, feel free to drop a notice. I have also submitted a lightning talk about openQA[1] and the cool usages of Perl around it. (status: pending as of this writing) [0] http://act.yapc.eu [1] http://en.opensuse.org/openSUSE:OpenQA PS. if i forgot any relevant party in the CC feel free to forward/cross-post there. -- Regards, Alex-P. Natsios (a.k.a Drakevr) -- 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 project] (totally not a flash player) Weekly report
by zsoltpeterbasak 15 Aug '14

15 Aug '14

Hey everyone! - This week I started writing rules, for the detection part. This is needed for the squashfs part. The system works (currently), like the tool "file" does. It goes through a set of rules. Confident rules, like openSUSE and SUSE studio images are on top. More generic ones have lower priority. A heuristic, generic approach is the latest rule. New rules can be added all the time of course. (They will be placed in a folder. Think of systemd modules, grub config files and such.) - Made a Github repo for the project: Started ticket tracking there. Will start committing the code ASAP. - This week I also made a live test, where everything went fine. Pendrive was done fast. Installed Syslinux, the mbr on the pendrive. Then I copied up the Dracut archive, and the kernel which Dracut used. (they must match) And I booted it up. And it worked. - Went back to simple "oneshot" type of script, since the 'systemd-notify' tool requires systemd libs to be included. While it definitely looks more robust that way... adding more bloat Well, everything looks fine so far. I want to write an install script today. Then write some extra rules, add more images. Overall, a good week, the project is in a good shape (IMO). 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] Proposal: first bootup tips
by G G 15 Aug '14

15 Aug '14

Hi All, at the first boot of a newly installed openSUSE some users could feel a little bit confused. That because they are going to use a new operating system (different from Windows or Mac OS), so they have to do stuff like network setup, graphics driver installation, audio/video codecs installation and so on. We could improve the openSUSE Greeter with first boot tips to help new users with the initial configuration of the system. Following there are some ideas from other projects that i (as user) find interesting: -> Classical way, like the PC-BSD guys have done [0] (screenshot 2, 3 and 4); -> Something more stylish like Mozilla did to present the new UI of Firefox [1]; -> Rework the current Greeter to contain less text (that is very scary to the user) to obtain something like Manjaro Linux [2] (screenshots 3, and 4). What do you think about? Best Regards hawake [0] http://www.linuxscreenshots.org/?release=PC-BSD%2020130806&l= [1] https://www.mozilla.org/it/firefox/31.0/tour/ [2] http://www.linuxscreenshots.org/?release=Manjaro%200.8.10%20Xfce -- Linux user number 433087 Linux registered machine number 351448 http://linuxcounter.net/ -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 2

Re: Re: [opensuse-project] Re: Where to Find ocaml-pcre Package
by Sam M 14 Aug '14

14 Aug '14

Thanks, but I am searching for OCaml Magic, and cannot find a package for SUSE: http://sourceforge.net/projects/ocaml-magic/ On Thu, Aug 14, 2014 at 3:53 AM, Axel Braun <Axel.Braun(a)gmx.de> wrote: > > >> Gesendet: Donnerstag, 14. August 2014 um 12:23 Uhr >> Von: "Sam M" <backgroundprocess(a)gmail.com> >> An: opensuse-project(a)opensuse.org >> Betreff: Re: [opensuse-project] Re: Where to Find ocaml-pcre Package >> >> I cann't find the OCaml magic package using the above link or using >> zypper, and it's needed to build the source I'm attempting to pile. Is >> there something I'm missing or can somebody check if OCaml magic >> exists for openSUSE? >> > > https://build.opensuse.org/search?utf8=%E2%9C%93&search_text=ocaml-pcre&com… > > HTH > Axel -- 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] Where to Find ocaml-pcre Package
by Sam M 14 Aug '14

14 Aug '14

Hi, I'm trying to compile a program written in OCaml, and it's asking for this: checking for ocaml pcre module... configure: error: Not found. However, I've searched the repos and have not been able to find it. Is anybody familiar here about OCaml and does it exist anywhere in the repos? Thanks -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 4

[opensuse-project] Announcing Peter Linnell joining the openSUSE Board
by Richard Brown 13 Aug '14

13 Aug '14

Hi All, I'm happy to be able to announce that the openSUSE Board has appointed Peter Linnell to join the Board until the elections at the end of this year, taking the seat which was vacated by my recent appointment as Chairman. For many of you Peter requires no introduction. A long term contributor to the Project, Peter is also member of the Review Team and maintainer of several packages, including Scribus (which he founded). He previously served in the openSUSE Board in 2011. Thanks Peter for stepping up and helping out, Regards Richard Brown openSUSE Chairman -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

7 6

[opensuse-project] [GSoC2014] Weekly update on TSP application
by karthik senthil 11 Aug '14

11 Aug '14

Hello everyone, Sorry for being late in reporting my weekly update for the TSP application. Last week, there were many small changes and modifications done in the app. The process of moving the dynamic machine generation code to the HasState concern is now complete and tested. Also, I have added the code to add ability for a role on a transition_event(like in the inheritance branch) through the interface. For every transition the admin can also define a set of roles who can perform the same which will be accordingly populated in the ability.rb through queries on the db. This week I will be working on running all the specs cleanly and adding documentation to my work. This recent progress can be followed on : https://github.com/karthiksenthil/travel-support-program/tree/temp_gsoc Thank You Karthik.S 3rd 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] [GSoC] Snapper Desktop Integration
by Oguz Kayral 10 Aug '14

10 Aug '14

Hi all. In the last weeks I continued working on snapper-gui and snapper KDE integration. The GUI now offers all the functionality of snapper without the hassle of using the command line client. And all snapper operations (except creating and deleting configs) are available to use from Dolphin. For the last week I will do some refactoring, write the help sections for each snapper-gui action and some documentation. Many people don't use btrfs yet (and the ones that do might not want to jeopardize their snapshots by using a tool in such an early release) so it's hard to test snapper-gui. In the last report, I will include a lot of screenshots so people can have an idea for when they start using btrfs and snapper. After GSoC, I want to continue developing and release a more polished version before openSUSE 13.2 is released (which will come with btrfs as default) Oguz -- 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 2014] OSEM Organizer Dashboard weekly update
by Christian Bruckmayer 10 Aug '14

10 Aug '14

Hello Community, my name is Chris and I am one of the Google Summer of Code Students involved in the Open Source Event Manager (OSEM). I am a student currently in the 3 year of the Bachelor of Science course with information systems and management major at the university of applied science in Nuremberg, Germany. I would like to take the opportunity to give you a short update of my work during the last week: A few days ago Henne migrated OSEM from Rails 3.2 to Rails 4.1. Because of that this week I have tried to fix bugs caused by this migration! In Rails 4, now PATCH replaces PUT for partial updates. Hence it was necessary to rewrite some url routes and update most of the html forms. Artem Chernikov gave me some advices and supported me during this task (thanks again!). Another task was to replace the deprecated Active Record methods. Regards Chris -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 15

[opensuse-project] re:AUTO WRAP ADVERT ON YOUR VEHICLE,BOAT AND BIKE- $300 / WEEK.
by HYDRAULICS INTERNATIONAL,INC. 10 Aug '14

10 Aug '14

Ladies and Gentlemen, We are currently seeking to employ individual's world wide. How would you like to make money by simply driving your vehicle or bike advertising for HYDRAULICS INTERNATIONAL,INC. How it works ?: Here is the basic premise of the "paid to drive" concept: HYDRAULICS INTERNATIONAL,INC.seeks individual- regular citizens,professional drivers to go about their normal routine as they usually do,only with a big advert for "HYDRAULICS INTERNATIONAL,INC." plastered on your vehicle or bike.The adverts are typically vinyl decals,also known as "Auto Wraps,"that is almost seem to be painted on the vehicle or bike, and which will cover any portion of your the exterior surface. What does the company get out of this type of advertising strategy ?.Lots of exposure and awareness. The auto wraps tend to be colorful,eye-catching and attract lots of attention. Plus, it's a form of advertising with a captive audience,meaning people who are stuck in traffic can't avoid seeing the wrapped vehicle or bike alongside them. This program will last for 3 months and the minimum you can participate is 1 month.You will be compensated with $300 per week which is essentially a "rental"payment for letting our company use the space on your vehicle,boat or bike and no fee is required from you,HYDRAULICS INTERNATIONAL,INC. shall provide experts that would handle the advert placing on your mobiles. You will receive an up front payment of $300 inform of a check via courier service for accepting to carry this advert on your vehicle or bike. It is very easy and simple,no application fees required.Please do contact get back to me with the requested info below if you are interested in this offer. Full Name: Physical Address: City: State: Zip Code: Age: Make Of Car/Year: Exterior Color Of Car: Telephone Numbers: We will contact you immediately we receive this information. Kind Regards. (R) HYDRAULICS INTERNATIONAL,INC. All rights reserved (TM). -- 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 12] [GSoC]Event Splash Page for Visitors
by Gopesh Tulsyan 10 Aug '14

10 Aug '14

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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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=sha… >>>>>> >>>>>> 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 <gopesh.7500(a)gmail.com> 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=sha… >>>>>>> >>>>>>> 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 <gopesh.7500(a)gmail.com> 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 <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 project] (totally not a flash player)
by zsoltpeterbasak 09 Aug '14

09 Aug '14

Hey everyone! This week I added preliminary support for SUSE studio images, Fedora images. Preliminary, as in, have to test things out (like persistent storage). Now I want to install things on my pendrive, and prepare the bootloader. If that's done, and things work from my pendrive, I want to make the menu-system a bit more advanced. (So you can select for each ISO that you want to boot the ISO; you want to use existing persistent storage; boot with storage.) But, the core works. The menu works. Everything going smooth. (Which is a great thing, considering the deadline coming closer.) When everything is done, I will start implementing the other ideas we have. After GSOC, I will upload the code to Github, and make a site for the project. So others can contribute/fork/use the product. Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 2

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

09 Aug '14

Hi, this is my fifteenth weekly status report for my GSoc project. My plan for this week was work on OSS4 support for libmatemixer, improving code and fixing problems in other backends and cleaning up the code. The OSS4 work has turned out to be a nightmare. The biggest problem I've been facing is the enforced layout of mixer controls, implemented directly in sound drivers and largely incompatible with the libmatemixer way (and even among the drivers). I haven't made a lot of progress on it and mainly focused on getting the other code right. At this moment I'm undecided whether I'm going to include OSS4 support or not, it's not a part of the project plan and solely my initiative, so I have some freedom in the decision. So to point out a few things that I did was revamping ALSA polling to do the right thing and run in a custom thread, generalizing support for mixer switches and toggles, I have also decided to provide translatable string for some common elements in ALSA and implemented some little things that were missing previously, such as balance, fade and decibel support. I've made a good progress cleaning up the code too. My current plan for the next days is to provide some sort of release candidate before the soft deadline on Monday. Then I'd like to make sure the code works on other hardware I have access to and on older platforms and complete the documentation. As far as OSS4 is concerned, if I end up being done and just twisting my fingers several days before the hard deadline, I intend to get back to it and hopefully provide the support for it in the initial code. Otherwise I'll probably wait for after the GSoC and discuss with the other devs if it's worth the trouble or not, but I'm certainly not giving up on it now that I have spent a lot of time studying it and the initial code exists. So now this is my last progress report of this kind, thanks all of you who have been reading them, wish me luck finishing things up and at the hard deadline time, I'm going to provide you with a lengthy summary of what I have done, how cool it is and how it helps save little animals and improve the lives of all of us (and all free of charge). 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] composition of OpenSUSE
by Kevin Buchs 08 Aug '14

08 Aug '14

For recent releases (not historical past), is OpenSUSE derived from other distributions (I have a coworker who thought all distributions trace back to Red Hat/Fedora and whom I am trying to disavow of this misunderstanding) or is it taking the inputs of the Linux kernel, GNU rest of OS plus building other packages from source distributions from the package maintainers (like LibreOffice). I know that Yum is included, but are there other parts from RedHat? Kevin Buchs -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

8 9

[opensuse-project] Reminder - openSUSE.Asia Summit Travel Support Program apply deadline 18th, Aug
by Max 07 Aug '14

07 Aug '14

Dear ALL: Just reminder Travel Support Program apply deadline is 18th, Aug 2014. ------------------------------------------------------------------ APPLY FOR TRAVEL SUPPORT First the applicant needs to read: http://en.opensuse.org/openSUSE:Travel_Support_Program Then please send the request through: https://connect.opensuse.org/travel-support You are required to send application during Aug 1st to Aug 18th. We will review and confirm from Sep 1st to 15th. If you have any questions, please contact opensuse-summit(a)opensuse.org. openSUSE.Asia Summit team -- 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.Asia Summit Call for Paper deadline 18th, Aug
by Max 07 Aug '14

07 Aug '14

openSUSE.Asia Summit Call for Paper deadline count down. Deadline 18th, Aug 2014. Submit your paper now!! * Detail: please see http://summit.opensuse.org/#cfp * conference submission tool https://events.opensuse.org/conference/summitasia14/proposal/new --------------------------------------------------- CALL FOR PAPER The first openSUSE Asia Summit Program Committee is ready to accept your proposals for sessions! We're also ready to register visitors interested in joining us. Your talk and workshop submissions should be fit for one of the four main tracks: End Users, Business, Community and Project, Technology and Development. You can submit your abstracts in our conference submission tool. The submission period begins today, and closes Aug 18. Note that the first bunch of accepted proposal acceptance emails will be sent on Sep 1, allowing you to start planning your trip already. And of course, first come, first served! So, be in time! The Four Tracks This is the first openSUSE Asia Summit. The theme is: openSUSE - Bring you to the free world! End User Track The end user track provides the opportunity for the power users of any application to share their knowledge and share tricks they apply to get the most out of the applications they use. Know of a non-obvious but very useful feature, present it's usage to fellow Geekos and users in this track. Topics include, but not limited to, applications, desktop environments, multimedia solutions and games. Business Track The business track provides the opportunity for those that use openSUSE and/or FOSS in their business to describe the unique challenges they face. This includes, but not limited to, issues and solutions of interfacing with regulatory institutions, other business, staff training, and changing technology course. Community & Project Track Sessions in this area should focus on project and community activities, including, but not limited to, project governance, marketing, artwork and advocate reports. In many cases, this sessions bring a strong sense of unity to the project as a whole as we discuss some of the unique challenges that an Open Source Community confronts. If you have ideas that can help a community be stronger, join this track. Technology & Development Track Sessions in this area should focus on system technology and distribution development. Including, but not limited to, software packaging, development/testing/debugging tools/practices/methods. Infrastructure software, deployment strategies and monitoring. These sessions will help a few of our members gain understanding of the many tools they can use when working in development for the distribution and other exciting projects. The Events We will have four types of events: Lightning Talk (10 mins) Short Talk (30 mins) Long Talk (60 mins) Workshop (2 hours) If it is possible that your audience can practise what you share in a meeting room, you would better do a workshop. You can send in proposals until Aug 18, but the sooner the better. We will start accepting submissions on Sep 1. -- 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] Minutes of Todays Project Meeting
by Richard Brown 06 Aug '14

06 Aug '14

Hi all, Below is the minutes from todays Project Meeting The full logs are available at http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… Meeting summary --------------- * Action Item Review * saurabhsood91 has posted announcements to the openSUSE india google group to encorage more involvement in openSUSE Few responses so far, more reminders on the way, hoping for more going forward. Get in touch with saurabhsood91 if you think you can help * GSoC * No major news for GSoC this fortnight - the program ends on August 18 this year * openSUSE Asia Summit * the Asia summit team still need help with artwork - especially a logo for the event and posters * Planning for Summit is progressing well. More proposed sessions would be nice - http://summit.opensuse.org/#cfp * Deadline for Call for Paper and Artwork is August 18th - Please help spread the word! * TSP Applications for openSUSE Asia summit are *open* until August 18th - Let openSUSE reimburse your travel to the summit - Please apply on https://connect.opensuse.org/travel-support * Next Meeting Date * The next openSUSE Project Meeting will be on Wed 20th August at 15:00 UTC - See you then! -- 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 05 Aug '14

05 Aug '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=6&month=8&year=2014&ho… 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] Re: [opensuse-announce] Factory moves to Rolling Release Development Model
by Gerald Pfeifer 04 Aug '14

04 Aug '14

On Tue, 29 Jul 2014, Henne Vogelsang wrote: > We are proud to announce that we have just switched our beloved > development distribution, openSUSE Factory, to be an independent > distribution using the “rolling release” development model. openSUSE > Factory is now a tested, reliable and bleeding edge Linux distribution! This is awesome news. On the technical front this may be the biggest step forward for openSUSE since the opening of Factory, Bugzilla, et al. I still recall the days when I was sitting in a hotel room in Bangkok preparing for an important presentation the following morning while my notebook was updating to latest Factory. Since then I've become a bit more cautious (and time constrained). After this news, I may start picking up old habits again. ;-) Kudos! Gerald -- Dr. Gerald Pfeifer <gp(a)suse.com> Sr. Director Product Management and Operations, SUSE

7 7

[opensuse-project] [MATE][GSoC]Weekly report : ePub support in Atril
by avishkar-gupta 03 Aug '14

03 Aug '14

Hi community, I got the Table of contents up and running for the epub plugin . Now that we have find, TOC and thumbnails as the available options, next week my primary focus would be to stabilise the program, and other than that add webkit-2 compliant code for Atril with GTK3, as the plan for the next release of MATE (1.10) would probably be based off GTK3. Support for webkitgtk-3.0 will be ending with the next release of webkit2, so the part which doesn't work with webkit2 will need to be tweaked. Other than that I'll work on adding the all important print feature and then maybe Mathjax. Now that the coding period is ending, and there is no limit on how many features one can add, I'll instead focus on providing a smooth experience with the existing features, both with GTK-2 and 3. This one is a short report, because I plan on giving a full one next week, once I am on par with what has/hasn't been done, as post next week there wouldn't be time for adding more than a feature or two. Annotations, which I fully intended to provide initially, would have to wait for a future time. repository - https://github.com/rootavish/atril.git 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 0

[opensuse-project] [GSoC] Weekly Report - Zorp LBaaS driver for OpenStack
by Péter Vörös 03 Aug '14

03 Aug '14

Hi all, This week passed with the implementation of the generator. It seems to be done, but I had some troubles while testing it. It showed up, that the virtual interfaces and routes are not created as they had to. I misunderstood a little bit how OpenStack works around the load balancers. So I had to do a lot of fixes, and it's still not yet done, but I feel I'm in the finish line. :) This week I plan to finalize it, talk through everything with my mentors to make it sure I didn't miss a thing. I also start to pay more attention to the documentation. 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] Re: Weekly Report [OSEM][Week 11] [GSoC]Event Splash Page for Visitors
by Gopesh Tulsyan 03 Aug '14

03 Aug '14

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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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 <gopesh.7500(a)gmail.com> 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=sha… >>>>> >>>>> 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 <gopesh.7500(a)gmail.com> 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=sha… >>>>>> >>>>>> 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 <gopesh.7500(a)gmail.com> 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 <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] [GSoC2014] Weekly update for TSP app
by karthik senthil 02 Aug '14

02 Aug '14

Hello everyone, This is a brief summary of my work last week. I discussed the various issues with the dynamic implementation of state_machine with my mentor, and solved each of them accordingly to make them pass the existing tests. After this I moved this dynamic code to a more generic place i.e HasState concern so that each machine has the dynamic implemenation procedures to create the state_machine. Along with this I added some specs to verify that a change in the states/transitions_events of a machine is subsequently reflected in the machine objects and that these changes are unique to a machine. This recent progress can be followed on : https://github.com/karthiksenthil/travel-support-program/tree/temp_gsoc This branch will be merged to the main gsoc2014 branch after a few more specs and on completely passing the build. Next week I will be working on permissions with respect to models and a workspace for the admin in concern with the workflow management. Thank You Karthik.S 3rd 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] [GSoC] [Cool Live Flash project] (totally not a flash player) Weekly report
by zsoltpeterbasak 02 Aug '14

02 Aug '14

Hey everyone! Last week's problem: Turns out, Virtualbox cannot mount the second drive. Nor the primary one. I tried adding the drives to the IDE controller, and to the SATA one (in Virtualbox), but nothing. I switched _back_ to Vmware. And voila, it works! Okay, mounting. I still had to fix a lot more issues before it could boot. But. It boots, works now. https://www.dropbox.com/s/zqyaf90c7puawa3/GSOC_ALPHA.mp4 Rest assured, there is plenty of work left. So what works: - Auto detect - Auto mount - Persistent changes - Cool dialog interface Current issues/TODO: - Dialog may misbehave on random boots - Various VM issues ( I want to fix Virtualbox behaviour) - Have to test system on a real pendrive, on a real machine (I did work with a real machine, so it will work, but have to confirm). - Implement NFS and the other "let's do this" things Let me know if I missed anything. Good luck for everyone! Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 2

[opensuse-project] [GSoC] Project "Add snapshot support to libvirt xenlight driver"
by David Kiarie 02 Aug '14

02 Aug '14

Hi there, THis week I wrote the xen-xl parser with support for spice graphics and the disk format!Am integrating it into the build system May be I will add support for the network config and vTPM. I will send out for review next week. Cheers, David. -- 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] 岁序更新
by suchufhbt＠sohu.com 02 Aug '14

02 Aug '14

sheffu 代电开话发 l 票 8 验 8 证 9 后 8 付 5 款 6 保 5 真 8 刘 6 经 7 理 fih N��r��y隊Z)z{.��k�7��맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��k�7��0��Ǩ�

1 0

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

02 Aug '14

Hi, this is my fourteenth weekly status report for my GSoc project. This week I have been working on adding ALSA and OSS4 support to libmatemixer. ALSA turned out to be quite simple, even though the documentation is pretty sparse, there is a lot of example code and the API is intuitive. OSS4 is a bit of a different story and for the whole time I haven't been sure if I wanted to do it at all, but I'm brave and adventurous and I'm going to struggle with it till the end. So for the weekend and the next week the plans are big. I have incomplete OSS4, some known problems in the other backends and I must adapt the previous library code and application code to API changes I have made recently. So once again, wish me luck, I'm almost done :) 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 31 - MATE caja extension project - alexandervdm
by Alexander van der Meij 01 Aug '14

01 Aug '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. In the last few weeks, I've worked on the main step for my project; allowing extensions to be toggled on/off during runtime. This step took a lot longer than I anticipated, but my implementation now works. I think I will require most of the upcoming week to make the code production-ready. It still needs a lot of polish, and I also struggle with a strange crash bug for which gdb is unexpectedly unhelpful. As soon as this issue is resolved, I will commit my 'at-runtime' code to github and invite people to test it. I also hope to start writing the documentation for the extension system, and start on step (5) below, but finishing the code is my first priority at this point. 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