hi,
This is my weekly report for week 3 of coding for my project where i add
ePub support to Atril, the MATE document viewer.This week i planned on
getting a basic ePub up and running, but due to a coding error that got
the better of me for two days, i am still working on that, as on where
that leaves us, i overhauled the xml parsing functions,and ended up with
much better code.
I am done with all helper functions, and am now focusing completely on
getting the code working inside Atril.Once this is done Mathjax
integration should be simple, and although a week over my first project
goal still i would be able to get this done in the week.
As usual to follow my progess in the project please check out the ePub
branch in my repository:
https://github.com/rootavish/atril/tree/epub
regards,
Avishkar Gupta
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
this is my seventh weekly status report for my GSoc project.
This week I continued working on my mixer library. I did a large amount
of work on the PulseAudio backend and made several previously unexpected
but neccessary changes to the public api. Apart from that the library
now also includes early gtk-doc documentation. The library still has
some unfinished spots, but I hope to sort them out during the weekend
and finally start working on porting the applications on Monday as planned.
As always, you can see the code on https://github.com/mratajsky/libmatemixer
Thank you,
Michal
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
For my GSoC project, I will be working on caja, the file manager for the
MATE desktop. My primary goal is to extend its extensions functionality
to allow runtime (de-)activation of individual plugins, and to create an
extension management system to allow more complex extensions.
Last week I started working on the five implementation steps required
for the main goal of my project. Unfortunately, I underestimated the
amount of work that was required, in particular for the later steps. As
such, I did not manage to complete it. Currently, I have almost finished
step 3, and I hope to complete it before or on Monday. At that point I
will commit my code to github. I should be able to finish all the steps
before my last update.
1. Extend the default gsettings schemas to create a subcategory for
extensions
-modify libcaja-private/org.mate.caja.gschema.xml
2. Make the load_module_dir() procedure keep track of extensions found
in CAJA_EXTENSIONDIR.
Add new modules to the config (gsettings), and load known modules
depending on their
enabled/disabled status in said config.
-modify libcaja-private/caja-module.c
3. Create new GUI tab in "File Management Preferences" to list available
extensions and allow changing of their enabled/disabled status.
-modify caja-file-management-properties.[c|ui]
4. Modify load module procedure to allow loading/unloading extensions
during runtime.
-modify libcaja-private/caja-module.c
-modify individual gui elements insertion functions (caja-window-menus.c
and such)
5. Allow extensions to expose a proper name, so we don't have to
identify them by their module filename ('example.so') in the GUI.
With kind regards,
Alexander van der Meij
alexandervdm @ freenode
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi all,
This week I've tested the existing Chainers in Zorp, which are
providing the load balancing opportunity in Zorp. I've also
implemented the source IP based load balancing strategy, and covered
it with unit tests.
Next week I continue to implement the other strategies, and I also
plan to do some refactoring, and fix some old tests that are failing
now.
>From now on, you can always check my results at:
https://github.com/VPetyaa/zorp/tree/upstream
Regards,
Peter
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
I'm sending a late report this week as I've been busy with some
personal troubles for the last few days, which might continue this
week :( .
I did the ui for snapshot diff and continued working on getting
snapper actions available on snapper-gui (which is called manta now).
I will be working on features to manage configs (create config, delete
config etc.) this week.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
This is a short update on this week’s progress.
I’ve completed a minimum variable version of bucketkit that has all features needed by git-review. More specifically,
Commits:
* get a repo’s commits
* get single commit
* get a commit’s comment(s)
* approve a commit
Pull requests:
* get a repo’s open pull requests
* get single pull request
* get commits for a pull request
* get comments for a pull request
* get the diff for a pull request
* get the activities for a repo or pull request
* send new pull request
* approve a pull request
* accept and merge a pull request
* decline and delete a pull request
From now on, I will shift my development focus back to git-review. Next week I’ll start integrating bucketkit into git-review.
Cheers,
Xu
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello everyone!
I spent this week reading documentation, building a test environment,
and of course, building a pre-pre-...-alpha product that can be ran,
tried, etc.
So far, things are going well. Blog is also updated.
I will switch to under promise and over deliver policy. So no promise
for next week, but I will try my best to deliver.
Good luck for the other GSoC members as well!
Regards,
Peter
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello everyone,
Last week, I worked on both testing the 2 models that I had added, and
designing the controllers for the same.
In the beginning of the week I wrote some specs to pass the
validations in the State and TransitionEvent models.After which, upon
the suggestion of my mentor, I wrote a spec(and fixtures) to verify
that these 2 models( and their associations) comply with the current
request machine's workflow.
After these tests, I moved on to designing the controllers
StatesController and TransitionEventsController to implement CRUD
feature in the 2 models. I referred back to my mentor for suggestions
on new gems and methods to be learnt for designing controllers, as a
result of which, I learnt the usage of many important gems like
inherited_resources,cancancan,simple_form and ransack.
These gems have simplified the ideas and thought me the actual
principles of Rails developement i.e DRY and RESTful approach.
I'm now working on implementing these 2 controllers and accordingly
design the views for the same.
Thank You
Karthik.S
2nd Year,Information Technology
NITK,Surathkal
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
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