ActivitiesAtom Feed

Displaying activities 1 - 25 of 1984 in total

August 24, 2016

  • Day 37

    Team RubyCats (Rails Girls Summer of Code — The Teams App) — at August 24, 2016 07:26 UTC

    • testing - learning, reading (about things like controller, request and feature tests
    • managed to put together a working controller test for preview
    • going through rails basics - routing ans some helpers
    • fighting the overwhelming feeling of coding despair.

  • Day 48

    Team B'More Stunners (Bundler) — at August 24, 2016 02:11 UTC

    Today's Updates:

    • Met as a team at our local Rails Meetup
    • Worked on client request as practice (Ash)
    • Reviewed unclear code in Bundler repo with coach Jamie (Ash)

  • Day 36: Making a web browser is hard, said Malisa

    Team JaM (Servo) — at August 24, 2016 00:00 UTC

    Things we did:

    • Headers

      • Submitted a PR about implementing iterable for headers.
      • Submitted a PR for updating DOM Headers. Making more tests pass is fun!!!
    • Response

      • Finished up implementing dom::Response. Now dealing with wpt test errors.

    Things we learned:

    • Fetch requests originate in the script thread via a JavaScript function. The request gets sent to the dom objects (e.g. dom::Request) and are sent to the resource thread using net_traits::CoreResourceMsg. The resource thread calls the actual HttpRequest. The response is sent back to the script thread and the original Promise is resolved. Yay! This is just a broad overview...


    • Fetch Method (Jeena)

      • Read about fetch. Decided to start working on fetch (one of jdm's suggestions). He wrote: "Start working on the actual fetch() API, focusing on the code that deals with the arguments and initiating the request and ignoring the return value for now." At this moment, I won't have to worry about Promise because "there's enough work that goes into dealing with the arguments to the function and initiating the request that the promise-related bits can be done separately and subsequently."
    • Response

      • Submit the PR once tests pass.

August 23, 2016

  • August 23rd: Experimental Travis CI Alpha tools and

    Team Hackbrighters (Lektor CMS) — at August 23, 2016 23:33 UTC

    This morning we returned to Exercism katas; Team Hackbrighters was excited to jump back into the world of katas, since we had somewhat paused our kata-learning these past few weeks due to deeply exploring Travis and the challenges it posed. For our daily kata, we went over an intriguing pangram challenge. We learned about Ruby's .gsub regex method, the .uniq method (which is similar to Python's set method), in addition to Ruby's .scan regex method. We found out that if you'd like to scan a string for alphabetic characters (including alphabetic characters with accents and special punctuation), you can use .scan(/[[:alpha:]]/) and it will be inclusive of those 'weird' characters. We also learned about how you can quickly call ("a".."z").to_a if you need an alphabet in a jiffy in Ruby! Lastly, we explored how .freeze makes something immutable. This is particularly useful for constants that you want to make sure is not changed.

    Furthermore, we learned more git commands. We learned how to branch off of a branch. You do this by git checkout -b myNewFeatureBranch originalBranch. As time goes on, our team keeps being reminded how complicated git truly can be.

    Today we are exploring and poking at Travis CI's Alpha debugging tools so as to attempt to better configure Lektor's .travis.yml file. We emailed Travis CI support this morning, and received instructions both for triggering than sshing into debug build for a open source project. Currently we're exploring their instructions.

  • Aug 22nd: First code review, yay!

    Team Hackbrighters (Lektor CMS) — at August 23, 2016 23:04 UTC

    We got our first code review from one of the Lektor maintainers regarding our PR from last week. We did manage to pass Travis CI's tools last week, with the caveat that there was a python 3.5 problem. Python 3.5 wasn't importing one of the critical modules we needed to run a test server. We filed the issue with the maintainer of the pytest-plugins, whose library we're using and pinged the Lektor community about the issue. David Baumgold (aka @singingwolfboy ) got back to us today with recommendations on how to refactor our file. With the help of (Doc Rietzel)[] we had hacked together a test server by cherry picking modules from the pytest library. David pointed us to the pytest-mock library which has a mocker method that we could use. We tried replacing our current server methods with the mocker one by one and running our tests each time. We tried to do some of the wholesale changes that David recommended, but some of his recommendations failed. We made adaptive compromises with his recommendations and our working code, and eventually got the whole thing working. All our tests, after the refactor, pass locally! This shows us that collaborative coding in Open Source is always a little give and take so the whole things works.

    We also heard back from Travis CI support, and they have a debugging tool that we'll try out so we can test our code against a Travis CI environment before making pull requests. We're excited for the opportunity to play with this tool which is still in alpha mode.

  • Day 37

    Team perifericas (Speakerinnen) — at August 23, 2016 22:52 UTC

    We're still working on the issues #469 and #408.
    Sometimes we think "oh, that'll be ok. we can deal it in just one day" than you realize it's so simple.

    We are doing some mind maps to help us figure out and get the whole cenario. It's helping a lot. :)

    Others things we did:
    * Answering a Q&A for Speakerinnen;
    * Discuss with Coach Brena about CI (Continuous Integration) and CD (Continuous Delivery) tools (when to use on a project, how to choose)

  • Day 37 : Perseverance

    Team Ruby's secret (Exception Notification) — at August 23, 2016 20:30 UTC

    today , we again focused more on learning , trying to deeply understand the thing we're dealing with , we re-watched some videos of a course talking about how to build a gem , we had abandoned this course a long time ago because back then we found it quite hard to understand but now after getting our hands somewhat dirty with exception notification gem , the course seems more clear and actually emphasizing the huge amount of information that we got to know since the beginning of the work . We also read more and more about Post Request and functional testing . At the end of the day , we tried to do some changes to the code after we had finally discovered how to run the dummy app .We feel that we're so close to the solution .
    We also had our weekly call with our supervisor .

  • Day 37: Playing Battleship

    Team kindr3d (Discourse – Visual Forum Analytics) — at August 23, 2016 18:51 UTC

    We are finally branching and committing to our project! Feels nice to finally start contributing and do some programming out in the wild.


    • branched discourse & installed d3
    • had a git lesson with Vincent
    • understood why semantic versioning exists
    • almost done building the d3 bubble chart

    To Do

    • work on visits controller
    • write an account of our progress for blog

  • Day 37 - Coaching and gardening

    Team XYZ (Keystone) — at August 23, 2016 18:32 UTC

    Today we woke up to an email notification from github which said that our password max character option pull request #3302 was finally merged! Now that this task is done and out of the picture, we can focus fully on the Twitter field.

    We had an intense coaching session where we focused mainly on the validateInput function and discussed all the ways we can check whether the value provided by user is valid. We had started working on this function in the previous days, so we showed to Josef what we had and he suggested some very insightful ideas about how to do the same thing in a more elegant way.

    We also spent some time studying - today we decided to deep dive into http requests and how they are handled in express.js, we tried it out using a mock application that we whipped up with the express generator and we learned a lot of new cool stuff.

    Tomorrow we will keep working on the validateInput function for the Twitter field. Another thing that we would like to start working on in the next days is the guide for creating a blog using keystone.

  • Day 38: Closing in on issue#1516

    Team Echo (qutebrowser) — at August 23, 2016 17:09 UTC

    What we did today

    ******* Did a great work analyzing the yank command. First of all the puzzle was on how it works as in what it actually achieves in qutebrowser. Then did a lot of digging in the code to understand how it was implemented so that we are able to edit it to solve the issue. We also explored the qt 5 documentation to understand the QUrl and QurlQuery classes with a bias on how to use the removeQueryItem and setQuery methods. And did some reading on UTM parameters and their use.We hope you find a solution soonest :)

    What we will do tomorrow

    ****Make a PR for issue#1516.

  • 23.08.2016 Day 38

    Team joda (SoundDrop) — at August 23, 2016 15:48 UTC

    -We met with Team LoadToCode to exchange experiences and strategies✅
    -We had our all-team call ✅
    -We began organizing an all-team meetup ✅
    -Gathered JS questions for session with Markus✅

  • A little too late

    Team LoadToCode (LEAP Encryption Access Project — Webapp) — at August 23, 2016 13:10 UTC

    Once again the monday caught me by surprise and I will sum up what we did yesterday.
    - after having last week a very successfull projectplaning session we started the monday with walking the board and doing some time estimation on our tasks this week
    - we had a very successfull design planing session where we decided on one design and made a sample
    - in our coaching session we talked about bootstrap and figured out where to put our css from the sample into leap to have it actually read and implemented
    - we worked on our own little koans to keep up with the ruby/rails learning

  • Day 35: Back to Work

    Team JaM (Servo) — at August 23, 2016 00:00 UTC

    We both enjoyed our long weekends. It featured swimming, the Seattle Opera, a movie triathlon, air conditioning, and Thai food. We feel energized for the second half of RGSoC!

    Things we did:

    • Headers (Jeena)
      • After addressing a couple comments, the PR for including "content-type" was approved.
      • It turns out headers list should be sorted before iterating over. Currently figuring out how to sort a hash map. Probably make a vector of the hash map elements and sort the vector.
    • Response (Malisa)
      • Implemented more dom::Response methods: Type, Url, Redirected, Status, Ok, and StatusText.

    Things we learned:

    • Was able to use destructuring with ref and & in a match statement, which helped me understand those concepts a little more. (Malisa)
    • BTreeMap is a hash map in which the elements can be sorted! (Jeena)


    • Headers (Jeena)
      • Figure out how to sort a hash map/iterate through a hash map and create a sorted vector.
    • Response (Malisa)
      • Finish up dom::Response functions
      • Read up on the function of the GlobalRef
      • figure out what I should do next

August 22, 2016

  • Day 36 : Testing ..again and again

    Team Ruby's secret (Exception Notification) — at August 22, 2016 22:27 UTC

    today we decided that we should read more and more about testing , so we didn't work on the code , instead we watched tutorials on functional testing and read some blogs about Post Request .Actually we have learned that we still have a lot to learn .Whenever we feel that we had finally reached the shore we discover that we are still in the middle of the ocean and that there are still more and more adventures that we shouldn't miss.
    We also have got some documents that are required for our trip to the conference .

  • Day 36 and about #rgsocdayoff

    Team perifericas (Speakerinnen) — at August 22, 2016 22:10 UTC

    So RGSoC Day Off recharged our batteries!
    It was difficult to not check Github, Slack and even read something about Ruby or programming, but we did it!

    It was a great refresh for all of us, we think.

    What we did:

    • Geisa updated her readings for Clean Code book;
    • We talked with Coach Brena about issue #408 and clear up some questions to solve it;
    • Emma worked on issue #469
    • We talked about releases from Rails and Jekyll;

  • Day 36 - Back to work.

    Team XYZ (Keystone) — at August 22, 2016 19:12 UTC

    After the day off, we were refreshed and full of energy to dive into coding again. We finally came up with the validation method for twitter field, as well as format method. Format method is supposed to strip out everything but the twitter username, and the validation method checks the result against regex containing twitter username rules (max 15 chars, alphanumeric chars + underscores). Resulting username can then be used for building up twitter urls as well as formatted output in Admin UI, and that's where we are going to next.