Yesterday was crazy....between losing power and a freak hail/thunderstorm which turned my car seats into sponges, getting things done was difficult.
Yesterday was crazy....between losing power and a freak hail/thunderstorm which turned my car seats into sponges, getting things done was difficult.
This concludes our third week working with FOSS@RIT for our summer Co-op. It was a week of mostly planning and course laying for the rest of our summer. We exploited Github and it's wonderful ticket feature to add milestones and tickets for our goals. Since we now have our goals clearly outlined on Github, we can finally get to work on the purpose of our summer Co-op. These tickets are an open feature and I thoroughly encourage you all to create some of your own when to start working on a project because it really streamlines the workflow.
Last Friday was our first real "Work From Home Friday". I woke up that morning with confidence in finding the way the OLPC journal talks to each activity and vice versa. Unfortunately, it wasn't meant to be. I spent the greater part of the day unsuccessfully pinging Google and the interwebz for some information on this ticket of mine. Having another day where I felt like I made no progress whatsoever isn't very encouraging....As a last ditch effort, I pinged #sugar in IRC hoping that they would be able to point me in the right direction, but to no avail.
This week I have been working on Gourciferous, which will become the our GUI of the combination of RIT FOSS Multi-Gource and, of course, Gource itself. Gourciferous will be written entirely in Python and the GUI will be built using Glade. The goal will be to create the most simple way to run Gource and combine GIT logs.
WOOOO!!!! This was our first full week at FOSSbox, exciting stuff!! Here's a recap of what I've done:
-> Days got mixed up, monday's entry was added into last week's week in review post
Marking Milestones
-> Issues on GitHub
-->> I transferred over our list of "Core Requirements" and"Would be Nice-ties"
As I mentioned on day 12, we planned out when our issues would have to be dealt with by, as well as who has to solve which issue.
All this can be seen here: HERE!!!!
Click on any issue to see a more detailed explanation of what it entails, or filter by milestone to see when things are due.
I had a relaxing weekend and most of today was the same. I did do a little hacking on Tahrir, though. I made some design updates in preparation for adding all sorts of cool metrics and functionality this week. Tomorrow I'll be tackling some database connection rewiring between Tahrir and Tahrir-API. After that, I'll be able to make all sorts of awesome updates.
Please, send your questions and comments in a plain text email to oddshocks at riseup dot net. I may respond publicly, so please tell me if you would not like the email content and/or your name published.
I am happy to report that this summer has been excellent. We are making real progress on the Fedora Badges infrastructure and I'm very satisfied with our pace. There is going to be some awesome hackery ahead.
Fedora cloud node is still live with current develop branch, though not much in the way of end-user functionality. That will be this coming week.
Notable improvements to the interface.
Did away with is_admin and implemented proper Pyramid __acl__ machinery. See issue #33.
As per issue #61, took variables base_url and title out of views' return dicts and added them as Pyramid events with super-fancy Pyramid magic:
# This is Tahrir's events.py file.
from pyramid.events import (
subscriber,
BeforeRender,
)
from pyramid.security import (
authenticated_userid,
)
@subscriber(BeforeRender)
def inject_globals(event):
"""Injects global variables into every template after the view
is processed but before the template is rendered."""
# request is available in every template, and we can just pull it
# in like so...
request = event['request']
# ... and then set a couple global variables that will be available
# in every template, so we don't have to pass them through the
# dict returned by the view every time!
event['title'] = request.registry.settings['tahrir.title']
event['base_url'] = request.registry.settings['tahrir.base_url']
Began rewiring database structure. Tahrir will now soon have a database connection through tahrir_api.dbapi to tahrir_api.model, rather than being directly connected to tahrir_api.model. I will be implementing the currently-unused TahrirDatabase class provided by Tahrir-API's dbapi.py file.
Other changes required by changes to database model in Tahrir-API, detailed below.
Please, send your questions and comments in a plain text email to oddshocks at riseup dot net. I may respond publicly, so please tell me if you would not like the email content and/or your name published.
Please, send your questions and comments in a plain text email to oddshocks at riseup dot net. I may respond publicly, so please tell me if you would not like the email content and/or your name published.
Today we wrapped up assigning issues for phase one to one another, as well as decide our team roles. For the first trimester, I got assigned the issue about connecting to school servers and looking into creating an Mozilla Open Badge allotment system.
Near the end of the day, I got to playtest the Ouya Android Gaming System.
Today I cracked down on our project, and marked out all our milestones on Github
Today had a bunch of unexpected happenings. We began the day working on our own this time because our mentor was busy with meetings and the such, so we set up our own EtherPad, which is essentially what we do every morning with various different online text editors. This gives the teams a place to jot down their roles for the day and allow us that amazing feeling of literally crossing a task off of your list of todo's. We then took a specific ticket that needed a little more definition in it's description and ironed it out for about two hours.
I saw Dave Jones on the Fedora Planet doing "daily log" posts in the form of overview-style lists detailing his thoughts and discoveries from his day's work. I thought it'd be cool to do them myself, at least for days when a more specific, detailed post isn't appropriate. It's not every day you're neck-deep.
What is up with the results of pkgwat search fortune?
Grateful Dead show of the day: 1979-12-05.
One of the recent changes to my .zshrc pipes the results of fortune -a via fortune-mod through cowsay. Results have been entertaining, as expected. One from tonight:
_______________________
< Too ripped. Gotta go. >
-----------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
I should really be keeping a better list of my thoughts and discoveries during my work day. Perhaps these logs will become a daily thing. If they do, they will definitely go along with more topical posts.
Please, send your questions and comments in a plain text email to oddshocks at riseup dot net. I may respond publicly, so please tell me if you would not like the email content and/or your name published.
Today we had a lot of busy work in Lemonade world. We finished creating our github tickets, and just need to assign these tickets to our team members. With this done, I turned my focus to researching Mozilla Open Badges.