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
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
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
Hi there,
This week I worked on helper functions which are needed by the major
functions(API) which I am supposed to implement.This included
1)libxlsnapshotMetadataWrite
This function should be called each time a snapshot is taken to update
libvirt xml metadata to track the snapshot.
2)libxlSnapshotMetadataUpdate
This function should be called on various occasions e.g to update the
current domain xml config after taking or deleting a snapshot.
3)libxlSnapshotForEachQdisk
This function is a wrapper function around xen libxl's disk_snapshot
function.I takes care of all the disks on a domain.This is what should
be called when taking the internal snapshot of an inactive domain.
4)libxlSnapshotObjFromSnapshot
This function takes a snapshot and returns a snapshot obj
representation.The difference between the two being that the "snapshot
obj" structure has more information.
Also because I am following the libvirt qemu driver(which I this has a
lot of boiler plate code anyway) I was thinking about having functions
to prepare the disks for snapshots.Here I am taking of checking the
user commands for errors and maybe some operations which are not
supported.
All in all, I will continue working on this and should be done next week.
*Ahem*,..sorry for writing sooo much detail.I just don't know how else
to explain this.
Regards,
David.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
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
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
Last week I finished config & snapshot list operations. I also did the
rest of the ui work except snapshot diff.
I started working on snapshot create & modify actions, I will continue
working on them next week and also do the ui for snapshot diff action.
Last week I said I was having some questions regarding the build
system (mostly about code generation from qt designer files also
dependency management), we resolved these problems in a meeting with
my mentor.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello everyone,
This is a brief summary of last week's progress.
I added the 2 models State and TransitionEvent as planned in the DB
design. I discussed with my mentor on the points like validations, and
ActiveRelations between these 2 models and other existing models.
After considering all points, I implemented the 2 models.I have tested
them for the sample workflow of the existing request and reimbursement
machines.I am now testing the models using RSpec and will be adding
the required specs to the branch.
My progress can be viewed here :
https://github.com/karthiksenthil/travel-support-program/tree/gsoc2014
Next week I plan on designing the controllers for these 2 models.
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
Hi,
This is the summary of this week’s progress.
I continued working on Bucketkit gem. The features needed for Git-Review (primarily getting/sending pull requests, comments, etc.) are near completion. During this week there was some school stuff so I didn’t spend too much time on the project. I will make it up over the weekend.
I’m planning to focus on the development of Git-Review as soon as the necessary features are done, instead of completing Bucketkit as a full-fledged BitBucket API client. This is because Git-Review is the main project for the summer, and currently it only needs a small subset of the APIs offered by BitBucket. Nevertheless, if in the future more people find Bucketkit useful, we can go on adding new API supports for it.
Cheers,
Xystushi
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
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
Hi,
this is my fifth weekly status report for my GSoc project.
This week I've been hard at work at improving my library, adding
features and fixing problems. I have spent most of the time working on
PulseAudio backend code. However, I have a large portion of code still
waiting to be commited on Github as there are several issues that I have
to resolve first and I try to avoid commiting broken code. I expect my
code updates to be available sometime during the weekend.
For the next 2 weeks I plan to keep working on the library just as I
have been so far. In 2 weeks I hope to have the library in a fully
functional state and start working on porting the applications.
Thank you,
Michal
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org