GSOC Sugar Labs - Week 11

1 minute read

This is the eleventh post in the series of my weekly GSOC Sugar Labs, where I summarize my week of working with Sugar Labs under GSOC.

Weekly Journal

This week Samuel and I refined the image management module, added a communication bot and frontend.

First major thing that was on the list was bot communication, add first we were thinking to use Github Statuses but they are not that effective while communicating status back to developer. One big advantage of using comments is that developer will receive both email and notification, so it helps us make sure that news get delivered. To comment and for other future purposes we made a special bot named aslo-v3-bot and we uses it’s Oauth token to comment on the release tag. When a release is made github sends the tag number used but not the commit :sad:, so to find the commit (so we can comment on that) we retrieve a list of tags and then find the target commit.

def find_tag_commit(repo_name, tag_name):
    g = auth()
    tags = g.get_repo(repo_name).get_tags()
    for tag in tags:
        if == tag_name:
            return tag.commit

    return None

Once we have the commit we can comment on the commit. We do it two times once build starts and once when build finishes along with the status (success or failure), along with the details.

def release_process(self, gh_json):
    except (ReleaseError, BuildProcessError) as error:
        logger.exception("Error in activity release process!")
        tag_commit = find_tag_commit(
            gh_json['repository']['full_name'], gh_json['release']['tag_name'])
            tag_commit, "Build Failed :x: Details:  {}".format(error))
    else:'Activity release process has finished successfully!')
        tag_commit = find_tag_commit(
            gh_json['repository']['full_name'], gh_json['release']['tag_name'])
        comment_on_commit(tag_commit, "Build Passed :white_check_mark:")

Here are two such examples, one for successful Build

Success Build

and other for a failed build

Failed Build

Samuel pulled an all nighter :night: to fix the screenshots and implement the Model Service architecture, here are [some][] useful links on the methodology.

Frontend is finally taking up shape. I am using bootstrap-material-design. A demo can be viewed here . Each version of a activity gets an unique url which is following format bundle_id/activity_version In case demo was inaccessible here are the screenshots

Index Page

Detail Page

Goals for Next Week

My plans for next week is to focus on Frontend and make a beautiful and minimal UI. Focus on testing and accessibility.