openSUSE Project June 2014

project@lists.opensuse.org

26 participants
46 discussions

[opensuse-project] opensuse-user not on gmane any more?

by Jim Henderson

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

6 years, 3 months

[opensuse-project] Re: [GSOC] OSEM Refactor user management model

by differentreality

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

6 years, 6 months

[opensuse-project] [GSoC 2014] OSEM Organizer Dashboard weekly update

by Christian Bruckmayer

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

6 years, 6 months

[opensuse-project] [GSoC] [Cool Live Flash] Weekly report

by zsoltpeterbasak

Hello everyone! This week I spent my time with crafting my scripts and making the boot pretty. Pretty as in, work normally. Because so far I used a trick (rd.break, anyone?) to get things up. Taming Dracut is not the easiest thing, if you have no former experience doing so. But I managed to dig through all the modules scripts now (literally, all of them), and now I'm working on the correct way of injecting our system into it. A bulleted list with a somewhat accurate timeline: - Made a quick blog, so my mentor can follow my progress much easier. It's also good for me to backtrack my process a lot easier. - Fixed up the CLF system script, so it mounts up 'modules'. Basically squashfs files, which can contain software, or modules, for example. Currently it's used to update the image's modules. - Fixed up the scripts so they would chainload perfectly. The system gets mounted flawless after the user selects his image of choice. - Learned a ton about Dracut again. One such thing was it's conf and switches. How they behave. - Spent a ton of time with pivot_root, switch_root and the like (manual mount). Because pivot_root and switch_root would fail miserably at boot. Michal (my mentor) had a great idea. The default mount point and a clean exit booted up the new system. This took me to the right track. - 'exec' fooled me great at debugging. ;_; - Learned how to use expect, where to execute it. Not sure if we will need it in the final version without breaks... But expect is so powerful, it may come in handy later on. - Debugging, debugging, debugging. So CLF is at the stage where automagic is being worked on. Mount is done = booting, working system. I need to add syslinux to the equation and it's a thing people could already install on a pendrive. (Of course, we are far from the final goals, as there are so many things I could improve, and so many things I could implement, even if the basics are done. Which is not the case at the moment, so yeah.) Thanks to the quickblog, expect lenghtier reports from now on. (I did work a lot before as well, but I just summed things up real fast each week.) Regards, Peter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 years, 7 months

[opensuse-project] upgrade oS 13.1

by Axel Braun

Good morning, not sure if this is the right group to ask, but is there a plan to upgrade the current openSUSE 13.1 to KDE 4.13.3 (or later)? I'm asking for the Official openSUSE build, not the respective KDE Project in Buildservice. Thanks Axel

6 years, 8 months

[opensuse-project] [GSoC] Git-Review Progress Update

by Xystushi

Hi All, Midterm evaluation is over. Thank you for the support. I continued adding bitbucket support into git-review. Currently, git-review is able to do the following operations on bitbucket repositories: 1. List all open pull requests 2. Show details (diff, comments, etc.) of single pull request 3. Open pull request in a browser window 4. Checkout a pull request’s changes to local repo The next step is to enable git-review to create, approve/decline, and merge pull requests. These will be the tasks for the following few weeks. Cheers, Xu -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 years, 8 months

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

by Gopesh Tulsyan

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

6 years, 8 months

[opensuse-project] [GSoC2014]TSP Application Weekly Update

by karthik senthil

Hello everyone, This week, my work so far was completely reviewed and merged to a separate branch in the main repository on GitHub. Further, more state machines have been added to the app(Shipments). I have designed the implementation method to automate the state machines and discussed about the same with my mentor.During this discussion some shortcomings of the current design were spotted and fixes for them were considered. Upon my mentor's suggestions, I will start implementing this method and also test it at the same time with the current existing state machines in the app. My progress can be tracked here :https://github.com/karthiksenthil/travel-support-program/tree/gsoc2014 Thank You Karthik.S 2nd Year,Information Technology NITK,Surathkal -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 years, 8 months

[opensuse-project][MATE][GSoC 2014]weekly report: ePub support in Atril

by avishkar gupta

hi all, This is my report for the week of May,26 to May,31 2014.I'm working on adding ePub support in Atril,the MATE document-viewer. This week i wrote the code that would be used to extract and parse the ePub archive. I am almost done with the helper functions, and now i am trying to get everything to build as a part of Atril compilation, which requires linking the Atril document and view librarieswith my backend. I am currently on top of that and hope to get a successful build by Tuesday. Here is the commit history for the week: 415b008....06 7f33c34....5d 070a26e....77 If you'd like to see these please see the tree. Here is the tree,if you would like to monitor my dev brach(which i hope you do, it's always nice to have random followers!): https://github.com/rootAvish/atril/tree/epub -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 years, 8 months

[opensuse-project] [gsoc] Weekly status report - MATE gstreamer project

by Michal Ratajsky

Hi, this is my ninth weekly status report for my GSoc project. I don't have a lot of exciting news this week. As planned I have started working on porting the MATE volume control application to my new mixer library and just as expected it's still too early to have a working version. I believe I'll have a working version by the end of the next week. Along with that I have commited a couple of fixes to my library. Next week I'm going to continue working on porting the app and there will also be some updates to the library which will be required for the app to work. Thank you, Michal -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

6 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project June 2014