ActivitiesAtom Feed

Displaying activities 101 - 125 of 2434 in total

September 23, 2016

  • Sept 22nd: Up, Up, and away!

    Team Hackbrighters (Lektor CMS) [2016] — at September 23, 2016 05:51 UTC

    Today we tried to make clean pull requests. We had started implementing a refactor of error handling in our git commit feature, and we wanted to make these two super clean commits. We telegraphed what we were doing in the issues log. So we had to pull out the new error handling code from the code where we started the new command line feature, and then we pushed a cleaner version of the commit to Github and then reopened the pull request. And then we filed the issue that coach Gavin had found earlier. He found that a malformed url in the project file threw up traceback error instead of "failing gracefully", as he put it. He had found this error earlier and offered an opinion on how to fix it. We had to table filing the bug and fixing it until we finished the git commit feature. However, there had been new code added that addressed a similar in an unusual place--the command line option file. He helped us re-think the fix so that raising a malformed url error would be generalizable enough so that we wouldn't have to do a url validation check in all the different types of Lektor deployment, as well as the command line. We found a way to do the error check in the publish function in the file. All the publishing / deployment targets touch that function, so that seemed the best place to raise the error instead of copying and pasting an raise PublishError function in multiple places. The easiest implementation of the error handling would've been to copy and paste, but to really thinking through the most efficient and most DRY (don't repeat yourself) approach was harder. And we're very lucky to have Gavin help us think through the problem like a computer scientist! A nice result of all this banging-of-head-against-wall was that we made two clean PRs that we're really proud of.

    We also worked on doing the blog post for the Rails Girls main blog. The pictures we took exceeded the recommended size, and we needed to get the size down to 600x600 or less. Instead of resizing them with a dedicated image editor or viewer, we used an atom editor package called image-resize where you can resize the pictures within the editor! Sublime will read images as binary files, but because atom is basically a chromium browser window with super powers, Atom can preview and manipulate images and animations. If you handle front-end web development, Atom editor seems to be text editor to beat.

    It also took a little while to work with Jekyll again. It's been a little while, so while we're much better with the Markdown language than the first time we posted a blog, building and previewing the pages took a little while. Jekyll was locking up while we were previewing changes, and we had to shut it down and restart preview a few times. It was hard to tell whether if Jekyll was crashing or the laptop we were running it off of. We'll happy to share our experiences at Github universe once we get this launched!

  • Day 57: First Day of Fall! :(

    Team JaM (Servo) [2016] — at September 23, 2016 00:13 UTC

    Things we did:

    • Body
      • Started refactoring consumebody based on feedback and yesterday's planning. Created and pulled out `consumebodyandrunpackagedata_algorithminto it, and created aBodyTrait`. The project was oddly compiling without complaints for most of the day. I mentioned this to Jeena, who reminded me that I have to list new dom files it in dom/ :) I did, and then all my bugs were then revealed upon the next compile. :P
    • Promise in Fetch
      • net_traits had changed! So I had to modify the process_response() method to accomodate the changes. It is more secure now as it allows the fetched data to be filtered. Filter exists to protect sites from having their data stolen by other sites.
    • Package Data Algorithm
      • I implemented(though no guarantee it works :wink:) Json(), Blob(), and part of FormData().

    Things we learned:

    It's a little long today, so check it out at our blog.


    • Body
      • debug and finish refactoring. Push to github and then merge with Jeena's implementation of Blob() and FormData(). Then work on Body for Request.
    • Test Curation
      • Go through the new tests, and categorize them.
    • Package Data Algorithm
      • Figure out how to write FormData() when MIMEType is "multipart/form-data".

September 22, 2016

  • Day 56: planning

    Team Ruby's secret (Exception Notification) [2016] — at September 22, 2016 22:32 UTC

    Today , we had a call with team Loadtocode regarding our conference talk and after the call we did some planning to the talk and brainstorming some ideas on the script , we also contacted our coaches to have a call regarding our project to see what's going wrong

  • Day 58

    Team XYZ (Keystone) [2016] — at September 22, 2016 19:55 UTC

    Design, design, design - we were still not completely happy with our ideas for the layout of the visualization page, so we brainstormed some more ideas and played around with them. This is not an easy part of the task for us, because none of us is really a design person. But it is definitely good experience for us. We are happy that the color theme and basic styles are already in place in Keystone, so we can just use them and we don't have to come up with all the styles from scratch. But the layout is still largely up to us. We alternated work on the design with study breaks, as we continued going through the React tutorials we had started before, and we also did some research on Redux, since we were not exactly sure that we understood its use completely.

    In the end of the day, we think we have a nicely working layout that is quite easy on the eye. We will now leave it overnight, to be able to look at it again tomorrow with fresh eyes, and then we decide whether it is ready to go, or whether it needs some more work.

    During the process of building it, we have also come up with some ideas about how to improve the visualization and enrich it with more features. We will revisit them and possibly implement some of these ideas.

    Here is an example of our work in progress from somewhere in the middle of our creative process:
    visualization layout on paper

  • Day 60: Commits to the PR and held RGK

    Team Echo (qutebrowser) [2016] — at September 22, 2016 19:42 UTC

    What we did Today

    ******* Made significant commits to PR for issue 1758. We got alot of feedabak/review of the code. We started working on the reviews today shall do more tomorrow and make more commits to the PR
    ******* We conducted conducted a thirds session for RGK. We didadvanced Ruby today. It was totally awesome :)
    ******* We also continued working on issue 1768.

    What we will do tomorrow

    ******* We shall continue working on the reviews for PR of issue1758. And we shall make more significant commits
    ******* Continue working on issue 1768.

  • Linux package and Bootstrap

    Team Reactives (Poetic Computation) [2016] — at September 22, 2016 15:10 UTC

    Bootstrapping our new UI (Revamp UI II) is complete, we can repackage our project after testing out the various methods to do so for different operating systems. Attempted to package the app with the old UI for Linux today but after testing with our coach, it seems that it failed due to an error regarding lib

  • Day 60

    Team KaUlah (GitLab Community Edition) [2016] — at September 22, 2016 14:02 UTC

    Summary of the day:

    • opened two MRs !6478 and !6474
    • solved Issue about disabling @all for non members of project
    • learning how to update gem sprockets version 3.7.0
    • Issue about adding merge_request_id to Commit API and handle with merge_request_id with null

  • Wednesday, September 21st: Coach Gavin explains Inception Lektor and Our Brains Exploded

    Team Hackbrighters (Lektor CMS) [2016] — at September 22, 2016 11:32 UTC

    Before Coach Gavin paid Team Hackbrighters a visit at Github, our Team began printing a bust of the Greek statue Herkeles, on Github's 3D printer. The torso of Herkeles should be done sometime tomorrow.

    When Coach Gavin joined our team, we were struggling to re-create the scenario we had accomplished with Coach Ramil. We began diving deep into our development version of Lektor's virtualvenv, where we then believed to have found another on earth was this even possible?! This accidental discovery was so horrendously disturbing to us -- because we know it's not really possible to have a virtual environment within another virtual environment.

    We believe what had happened is that we had accidentally pip install lektor inside of an instance of pip install --editable .. We believe this happened because pip install lektor seems to be much more natural and intuitive of a command than pip install --editable . It's also interesting to note that there are no safeguards from this happening to other developers. Because of this interesting Lektor inception, we had to do a deep-search-dive into a venv in Lektor, and then hand compile with Coach Ramil on Monday, September 19th. This is what we did not entirely realize with Coach Ramil.

    After figuring out the mind-blowing Lektor inception, we attempted to create a beautiful pull request to finally implement the git commit --message CLI flag. We realized we had made a small syntax error, so we quickly utilized a git commit --amend to change the small error. Then, another error. We quickly realized we had accidentally added code we meant to be in another entirely separate commit that addresses another Lektor issue. We had made yet another mistake after we had just amended the pull request. At this point in time, it had grown to be very late, and Team Hackbrigthers was tired. We decided to just close our pull request and try again tomorrow, when we're more fresh and bright-eyed. We didn't want to risk making more mistakes due to being physically and mentally -exhausted.
    Stay tuned...!

  • Day 57: Riding the wave

    Team kindr3d (Discourse – Visual Forum Analytics) [2016] — at September 22, 2016 10:38 UTC

    We skipped the last day and took our time, because conference week hit us pretty hard. However after resting we managed to get on with it and were very productive.


    • render horizontal bar chart
    • refactored and commented the code to add readability, tho there is more work to be done


    • create last query calls for topics and posts components
    • start rendering donut/pie chart for topics

  • Day 57: First Day of Fall! :(

    Team JaM (Servo) [2016] — at September 22, 2016 07:00 UTC

    Things we did: Body Started refactoring consume_body based on feedback and yesterday’s planning. Created and pulled out consume_body and run_package_data_algorithm into it, and created a BodyTrait. The project was oddly compiling without complaints for most of the day. I … Read more.

  • Day 59

    RGAU2016 - TEAM VEGEMITE ( [2016] — at September 22, 2016 05:17 UTC

    1. We had a last retrospective with our Mentor Katrina, coaches and supervisor Vi- We talked about things that I have learnt and shared my experience with all. '
    2. Talked about challenges and the difficulties that I have faced. How could have been avoided at the first place or improved.
    3. Worked on the issue
    4. Made changes to filter deprecated problems -Wrote tests to test the functionality.
    5. Submitted the PR.
    6. Also learnt about how to write descriptions for PRs. And learnt about the templates they follow at the coaching company for bugs and improvements.

  • Tuesday, September 20th - Open Source Panel at Hackbright Academy with Katrina Owen and Carol Smith

    Team Hackbrighters (Lektor CMS) [2016] — at September 22, 2016 00:09 UTC

    Team Hackbrighters was invited to speak at an Open Source panel hosted at Hackbright Academy, a software engineering school that trains women in software development and computer science. The panel included our team, in addition to GitHubbers Katrina Owen and Carol Smith.

    Katrina Owen, Developer Advocate at Github, is co-author of 99 Bottles of OOP with Sandy Metz, author of, and Project Maintainer for Sinatra. Carol Smith is currently the Education Partnership Manager at Github, and previously was the Google Summer of Code Program Manager, an online, international, philanthropic university outreach program that has served thousands of students. As Education Partnership Manager at Github, Carol oversees Github Classroom. GitHub Classroom automates repository creation and access control, making it easy for teachers to distribute starter code and collect assignments. Both Melissa and Patricia are alumna of Hackbright Academy, so our team feels a strong camaraderie with the current Hackbright students.

    The entire panel supports more women in tech, and agreed to giving our expertise and unique viewpoints on Open Source in order to create opportunities for fellow women early in their software engineering careers. We spoke to current students about the opportunities Team Hackbrighters have taken advantage of at Github as Rails Girls Summer of Code fellows. We gave the Hackbright students advice on how to break into tech via Open Source, by citing fellowships such as Google Summer of Code, Outreachy, and Rails Girls Summer of Code.

    Moreover, Melissa dived deep into her personal narrative of how she first began her coding journey and became interested in Open Source. She attended an Open Source Meetup, where Carol Smith was presenting a session on how to get-into the Google Summer of Code fellowship. Carol Smith highlighted that one does not have to be a traditional student enrolled at a four-year institution with a full-time course-load. All one has to do to fulfill the student requirement is to enroll in a swimming class at their local community college, and then drop said swimming class after one has proven they are a student.

    Also, the panel spoke about strategies on how to contribute to Open Source as a beginner. Our team gave advice on how to go about finding mentorship in the world of Open Source. Katrina Owen spoke about how to 'sneakily' find mentorship on Open Source projects. To explain, Katrina suggested that students help out overwhelmed and stressed Project Maintainers via closing out finished issues. By doing this, a student's Github handle reappears and is made familiar to Project Maintainers -- a student can create a rapport with Project Maintainers and the project's community, which then (hopefully) increases the likelihood of a student to successfully receive mentorship. Katrina advises this indirect strategy of asking for mentorship, rather than directly asking for someone to be a mentor. Rather than directly asking a senior developer for mentorship on a particular Open Source project, and risk overwhelming and overloading the senior developer with more responsibility.

    Furthermore, Carol Smith spoke about how problematic it is for supposedly begginer-friendly programming books are entrenched with math jargon. She strongly expressed how the fact that theoretical math is so deeply intertwined within programming education at the university-level is problematic, and is a large reason why women are pushed out of learning to code.

    Afterwards, Melissa taught part-time Hackbright Academy students, while Patricia mentored current full-time Hackbright students about Model-View-Controller.

  • Day 56: Next Steps

    Team JaM (Servo) [2016] — at September 22, 2016 00:03 UTC

    Things we did:

    • Body
      • Submitted PR last night for dom::Response's Body::text function. Got back some feedback. Spent some of this afternoon planning the next steps.
    • Blog
      • I (Malisa) spent some time writing my Strange Loop blog....will try to do some more coding tonight.
    • Promise in Fetch
      • Addressed review comments from the PR.
    • OpenEndedDictionary in Headers
      • Opened a PR and addressed review comments.


    • Body (Malisa)
      • Fix code based on jdm's feedback and refactor.
    • Test Curation
      • Go through the new tests, and categorize them.
    • Package Data Algorithm (Jeena)
      • We decided that I should work on implementing the rest of the package data algorithm. This decides what to do given a Body, depending on its type (a text, json, and etc). Malisa already implemented text, so that's great! Malisa will focus on going through review comments from her recent PR, and refactoring consume_body and making it into a public function. That way, it can be called by both Request and Response. At this moment, consume_body is customized for Response specifically, and it will be redundant to do the write the same function for Request.

September 21, 2016

  • Monday, September 19th - CLI Git Commit Message Breakthrough!

    Team Hackbrighters (Lektor CMS) [2016] — at September 21, 2016 23:33 UTC

    Team Hackbrighters had a very fruitful day! Albeit we had a very long, mentally-exhausting day, our Coach Ramil from LinkedIn helped unblock us on how to implement the Command-line Git Commit message on Lektor. Our team had been pouring over our Project Maintainer's library, Click. Click is a library that facilitates creating command-line interfaces in a succinct, easy-to-understand way. Specifically, our team focused on the Options API section of Click. After familiarizing ourselves with Click's interface, we implemented a --commit flag in in Lektor. We believed we had correctly constructed the necessary code, but we quickly realized couldn't even get our code to run. We inserted print statements in and we weren't even able to get the print statements to output to the terminal. We even inserted nonsense code in but we were unsuccessful in getting our code to fail where we expected it to fail. We realized that we weren't even running the code we were editing. How could this be possible? We showed this to Ramil, and he was also perplexed. He also agreed with our hypothesis that we weren't even running the correct code. With this at hand, Ramil gave us debugging tips. After examining the codebase, Ramil showed us that we had to actually had to go deep into Lektor development's virtualenv. We then had to hand compile the file. In order to accomplish this, Ramil showed us the command python py_compile! Ramil had showed us the Python Compile docs in order to accomplish this. After this magical incantation, we were finally able to get the Lektor development code we were editing to update and run! Hooray! Ramil advised us to ask the Lektor community about their development workflow; how do they develop on Lektor proper? The fact that it's so difficult and non-obvious how to run Lektor development code is an issue that should be better documented and explicated. There must be a better way to develop on Lektor's development codebase, rather than diving deep into Lektor's venv and hand-compiling single files to see its changes.
    Along the way, Ramil showed us useful bash commands, such as top. top shows you sorted information about processes on your computer. Ramil also showed uspushd and popd, which are Unix commands that allow us to manipulate the directory stack. These are handy commands for developers to efficiently jump around directories.

  • Sept 16th -Friday: In the after-glow of Github Universe.

    Team Hackbrighters (Lektor CMS) [2016] — at September 21, 2016 22:20 UTC

    Team Hackbrighters went back to the coding grindstone after the basking in glow of Github Universe. We picked up working on the git commit message feature upon deployment of a lecture build. We studied the documentation for the python click library that our project mentor wrote. It uses a lot of decorator patterns which we're generally unfamiliar with. We practiced using some of the code snippets from click's documentation to see how it worked. We still don't quite understand how decorators are used. And with click's library you can apparently stack many decorators on top of a single function for a single command because one command may have many options for it. We think we know how to use the click library and it's api, but we'll need someone to help us understand decorators patterns in general. They're supposed to be cool and amazing?

    We wrote a draft of the feature that should take in a command line flag --message and it should collect the string after the flag and then pass the string into the function. We implemented the road map that coach Gavin gave us and we think it should work. We talked through the code and tested simpler versions of the patter, but we can't seem to get the option to become activated from the command line. we've saved the file, and we've added print statements. However, when we try to deploy the test site from the command line, a lektor build and deploy actually occurs, but we can't see any of our test print statements. We'll keep working on this mysterious black hole of where are our git message going next week.

  • Day 57 - Can't wait for RubyConfBR

    Team perifericas (Speakerinnen) [2016] — at September 21, 2016 21:50 UTC

    Hi, everyone!

    This is Geisa :)
    I woke up so early to get in time to the flight. I prefer to come two days before the conference to meet other groups of dev girls.
    I'm so excited! Sunday, after the conference, i will participe of a workshop to learn about development games with Unity3D at MariaLab, a feminist hackerspace (the only one in Brazil).

    Today we

    • Get some informations about the translation;
    • Some RGSoC tasks;
    • Schedule some meetings with locals groups at Sao Paulo (Geisa);
    • Try to to talk with other dev friends for guidance about social plugins;

  • Day 57

    Team XYZ (Keystone) [2016] — at September 21, 2016 21:47 UTC

    As the Summer of Code program is nearing to its end, we are realizing how much we have learned over the summer, and also how much there is still to learn for us. As we are progressing our work on the list visualization task and discovering yet new problems, we are noticing it even more. Sometimes it can get slightly frustrating, but overcoming the challenges is so satisfying! We will persevere and we will get there. Our coaches are providing us with immense support, both technical and moral, and we are really so happy to have them. Today our coach Josef brought us some surprise gifts he had got for us from GitHub (thank you, GitHub!) - stickers, cheat sheets and some more swag, including really cool Rails Girls branded stickers. So sweet! Josef and Jano, you are the best, thank you for all you do for us!

  • Day 55 : Stuck

    Team Ruby's secret (Exception Notification) [2016] — at September 21, 2016 21:10 UTC

    Now we are stuck . There is something which we can't figure out regarding the dashboard .We now can catch exceptions and store them , the problem is that the gem supports Sintara and Rails, and the method we used supports Rails only . We are trying to ask on the helpdesk , trying to prepare calls with our coaches and our mentor . Hope we can figure that out soon :D .
    During the past days we've been working on Nada's laptop only because the terminal on mine was giving errors for almost every command I type , it was driving me crazy but today , thanks God , I managed to fix it .