ActivitiesAtom Feed

Displaying activities 76 - 100 of 2742 in total

July 18, 2017

  • Day #14 -

    Team 276linesofCode (Tessel) — at July 18, 2017 18:28 UTC


    So we had a call with our mentor Kelsey today. We discussed the plans for this week which includes making tests for crash reporter ( This one's written in Python, so we would have a little less trouble in going through the code base.

    Later on, we read further resources on One Wire protocol. Hardware integration is very difficult and we'll try our best to implement it. Our solutions as of now include making a UART to 1-Wire communication bus so that we can implement a few modules that work in 1-wire. We shared a few resources on it with our coach, Diksha, who would be helping us with that.

    Another great thing happened today! Our blog update for Tessel (PR #58) got merged! We would share the links soon ☺️

    Till then, adios.

  • #Day12:Mystery solved: Culprit found

    Team Bundledore (AFDC League Management System) — at July 18, 2017 18:20 UTC

    So, our last update was on how we couldn't get Gibbon gem running so we shifted to Mail Chimp ? We figured out exactly who the culprit was. The good old Docker :P We understood a very fundamental concept about Docker(that installing gems on the system does not install it in the container). After that there were still a few problems in getting everything running, but finally it did just a few minutes back. Next step is of course, continuing with the issue and I donot expect a smooth ride. Our mentor, Pete has been great in helping us out such a lot whenever we were stuck :)

    PS: Mukesh is a bit ill so we were one coach down but alfie is equally awesome !

  • Day 12!

    Team prodyoGEEKY (OpenLMIS: vaccine and medicine logistics for low- and middle-income countries) — at July 18, 2017 18:15 UTC

    Met with Mary Jo over call today who walked us through OpenLMIS version 3 series where we discussed things like the background, features and product roadmap to name a few. Thanks Mary! :)
    Our major takeaways from the meeting -
    Why OpenLMIS?
    Stock management is done on paper which gets approved by a hierarchy of people before order is dispatched and delivered. OpenLMIS is trying to make that process automated for easy use.
    Shared Investment, Shared Benefit
    Shared investment: If someone pays to build a software for some purpose, we want to build that feature in a generic way so that it can be used in different countries.
    Shared Benefit: So when we build a software as a developer, make sure that we should build it in a generic way so that it can be used as a shared benefit for a larger community
    At the moment, we do not have a shared benefit as different countries have software with different features and versions.

  • Day 12

    Team Victorious Secret (The Processing Foundation) — at July 18, 2017 17:12 UTC

    What we did today

    • Filed our first PR! We filed our first PR for Issue 385.
    • Met with our mentor Cassie who guided us on how to proceed with Issue 383 and 385.
    • Worked on Issue 383 by editing the scss file to add a dialog box in React.

    Agenda for the week

    • Meet our coaches.
    • Send in final PR's for all issues we have been working on
    • Start working on other Issues.

    Team Victorious Secret signs off for today!
    Stay tuned for further updates.

  • Day 13

    Team NK42 (Foodsaving and Foodsharing) — at July 18, 2017 16:44 UTC

    Django, Django and a little bit of Django – together with our coach Ana we started from the scratch again to get a better understanding of the Python framework Django: How to construct urls and views; how to write a model and how to connect all these code snippets. For orientation we used the first three chapters of the 'getting started' section in the Django documentation. ( We plan to do the rest of the tutorial tomorrow.

    Ines installed DB Browser for SQL and gets a more concrete idea of the database. Marie practised to work with the Django shell. In the last half hour at SoundCloud we are writing a short text about the hackathon for the yunity community and afterwards we plan to visit a meetup. About what? Django of course!

  • Day 13 - PRs and Mistakes!!

    Team Fusion (OpenDF) — at July 18, 2017 16:31 UTC

    Now the picture is getting bigger. Workload is increasing but we are enjoying it. πŸŽ‰πŸŽˆ πŸ’ƒ Our coach Udanie informed that she's unable to come since she' having some urgent work. But no problem, we can have it on friday. πŸ™‚ So we took our whole working time for learning, implementation of searchable field panel and finalizing our first blog post.

    Things we did today:

    • Since our supervisor checked and commented, we were able to finalize our first blog post. Relieved πŸ˜… βœ…
    • Had to resize and compress some of the images of our blog post. βœ…
    • We mistakenly sent a pull request, adding only images without the our blog post, as we thought we are supposed to get the images merged first. Funny :D, But "Each mistake teaches us something" 😊 βœ…
    • Sent the requested documents to our Scrum master Dr.Gamindu. βœ…
    • Started the implementation of the search panel by writing a component for the search field list. βœ…
    • Also took some time to discuss about our CVs, modules we learnt in universities as we are from different universities, different carrier paths relevant to our degrees and etc. Learnt a lot :D βœ…
    • Continued learning React and React Boilerplate while working. βœ…

    Things to do tomorrow:

    • Send pull request of our blog post.
    • Continue the Development of Searchable Field Panel and Query Bar

  • Day Twelve!

    Team Code_Hoppers (OpenFarm) — at July 18, 2017 16:10 UTC

    What we had planned to do today:
    1) Finalize on the icons on
    2) Push the blog post to github for publishing
    3) Work on resolving homepage UI redesign - #903 issue
    4) Look at more angular javascript exercises

    What we managed to do:
    -Worked to resolve pending issue on #903
    -Pushed progress update to new branch for #874 - we realized that there was code that was missing beforehand on the branch we were working on.(Debugging)
    -Corrected spacing on input tabs and created css mockups for 874

    What we will look at tommorow:
    -Look more into angular1.x services and how they work
    -Finish on UI for the sidebar navigation for the search bar

    It was a great day, looking forward to tommorow!

  • Day #12

    Team Codeaholics (Nextcloud) — at July 18, 2017 15:33 UTC

    What we have done:

    • Started working at 9am
    • Reviewed the Contacts Documentation PR
    • Still working on working on issue #253 and we realized that when adding the 3 props tel email and adr to the template after they are created in the controller they do not have a $$hashKey. We tried multiple things, such as adding track by value option to the foreach loop but it didn't worked because it says that contains dupes. Therefore, we are currently stuck and we asked our coaches and other contributors to have a look at the code.
    • watered the flowers at Open Labs Hackerspace and cleaned the place

    To Do:

    • Have a call with our supervisor (Benedikt)

  • Day 12

    Team Code Bears (diaspora*) — at July 18, 2017 15:21 UTC

    First thing we did this morning was to look at the comments our pull request got. Even though it was exciting to already have some comments, we realized we need a small break from handling this issue. Therefor we decided to give it another day, maybe get even more comments and fix things tomorrow.
    at this point we started to work on our second issue . It involves a list of issues regarding poll features in diaspora. We read the issue and the entire discussion alongside testing polls creation on our own diaspora profiles, and came up with a list of 9(!) improvements. In our coaching session we divided the list to two categories:
    1. Visual issues (like radio buttons alignment or delete icons alignment and so on).
    2. Missing behaviors (like enable to shut down poll/time limit voting, mark the option the user voted for, enable re-sharing poll ans so on).
    We don't know if we actually will tackle all those issues, we still need to choose some and prioritize.
    In any case, after a quick look at the code we have realized we need to learn about Active Records and ORM, so we are looking at some videos and tutorials.

  • Day 12 of RGSoC

    Team Alexa (JoopeA Club) — at July 18, 2017 15:00 UTC


    Today we've been working all day on adding language model to pages. We've managed to finish the task, and we're happy to see how working on the project gets easier each day, our tasks become clearer to us as we understand more and more about Django and our project.

    Tomorrow we'll add different languages to communities and hopefully we'll close this big issue we've been working on for a week now.

  • Week 3 - Day 12

    Team berlin diamonds (Discourse) — at July 18, 2017 14:29 UTC

    We have ready the first version of our Discourse backups to Google Drive plugin, yay! The instructions for its usage are in the readme of the repository:
    Discourse googledrive backups plugin

    Today we've:

    • Learnt how to use opendiff to solve conflicts in github (git mergetool)
    • We discovered that the 'google_drive gem' was reading the full json hash with the credentials as if it was a (veeeery long) path. It raised the error "Errno::ENAMETOOLONG".

    We didn't want to include a path to a file (this would mean forcing the user to put the json file into the Plugin structure manually). The idea was to let the user copy&paste its json-formatted credentials provided by google into the UI of the plugin settings and connect like that to Drive.

    Luckily, this gem also gives the option to pass an IO object to create a session. We converted the json-alike string into one and connected to Drive successfully: session = GoogleDrive::Session.fromserviceaccountkey(

  • Creating a Plugin for Discourse

    Team berlin diamonds (Discourse) — at July 18, 2017 14:17 UTC

    Discourse MetaIf you want to contribute to Discourse there is the awesome Discourse Meta Community to help you. So in order to avoid starting without any tipps and hints, just create a new post on Discourse Meta and describe your project and ask for hints.Example PluginThere are already plugins … Read more.

  • Week 3 (Jul 17 - Jul 21) Status Update #2

    Team 200 OK (coala) — at July 18, 2017 03:41 UTC

    Yesterday, we tried to resolve some of the issues that we were facing with our existing PRs including code coverage, the working of pytest and other minor things. We had been feeling quite frustrated because our PRs were not going anywhere for the past few days, so we also had a video call with our coaches who suggested that we take up some other issues similar to the ones we have done before and then return to these once we had our confidence back.

    Also, we looked up the dates of Pycon Delhi and might send a proposal for a talk if we can draft it in time. Fingers crossed
    That's all for now!

  • Day 11

    Team BansheeBandits ( — at July 18, 2017 00:24 UTC

    What we did today:

    -Conference Call with Jeff. We discussed the possibility of aiding in the development of bots that can potentially interact across multiple platforms
    -Discussed PublicLab logo design
    -Conference Call with Nada, our supervisor. We discussed some of the challenges we faced, and potential ways to counter those challenges.

    On Deck:

    -Meet with Katie to go over typeahead.js solution & dropdown menu solution
    -Pick apart the WeChat bot write-up on github
    -make a list of Lynda classes to participate in with a timeline

July 17, 2017

  • Day 11 - third week already :O

    Team RailsGyn (RGSoC: The Teams App) — at July 17, 2017 23:35 UTC

    We cannot believe that it is already the third week!

    We are in the middle of a really huge PR correction, but today we finally finished it.
    Now we have to wait for more reviews and suggestions.
    It is awesome when someone spends his time to look into your job and help you to get better...
    While people review our code, we have started to do some minor issues.
    That is it. We are having fun in the teams' app, it is amazing to make part of this.
    Tomorrow, we will start new issues.

  • Day 11 - New Week with React!

    Team ImpactDevs (WorldBrain - Verifying the Internet with Science) — at July 17, 2017 21:25 UTC

    After a call with our supervisor and several meetings with coaches over the weekend, we've focused our efforts on learning fundamentals of React in order to properly build our admin and client-side interfaces. Today Jessica went through exercises to render an object in react with createClass and props. Vanessa learned to create components and map arrays of objects. We also met with a node & react developer who works at Info (our host office company), and he will be able to give us guidance from time to time in the office.

  • Day 10 & Day 11

    Team Serv0101 (Servo) — at July 17, 2017 20:58 UTC

    Last weekend we had the meetup with the local rust community members.
    In the meetup, we learned about references and borrowing. We will cover these topic breifly in coming blogs.
    It was the great time spending with Rust community people and we also met one of our coach who introduced us to this community.

    Things we learned:
    * Iterator and Enumerator:
    fn main () {
    Let foo = vec![1, 3, 7, 9, 12, 25, 27];
    for (i, item) in foo.iter().enumerate() {
    println!("the { }th item is { }", i+1, item);
    the 1th item is 1
    the 2th item is 3
    the 3th item is 7
    so on...

    Iterator: It gives us a sequence of things.
    Enumerator: Creates an iterator which gives iteration count as well as the next value.

    Generic Data Type : It is more flexible, provide more functionality and remove code duplication.

    Generic function -->
    fn foo(list:&[T]) ->T

    Here T : Type parameter
    The function foo is generic over some type T. It has one parameter named list and type of list is a slice of values of type T
    The foo function will return a value of the same type T.

  • Day #11

    Team Codeaholics (Nextcloud) — at July 17, 2017 19:09 UTC

    What we have done:

    • We started the week with a coffee and we set some goals
    • We continued working on issue #256, but we haven't fixed it yet
    • We read AngularJS documentation where one of the things we learned was that $q is a service that helps you run functions asynchronously

  • Day 11, Loads of React!

    Team Victorious Secret (The Processing Foundation) — at July 17, 2017 18:29 UTC

    We had a great weekend, working on issues together on Saturday. On Sunday, we attended a meet-up organized by Facebook Developers' Circle. Eric Nakagawa, who has been working in the React, React Native team at Facebook gave a talk and we were on cloud nine. To hear about the future of React, from someone who's actually working on it, was the best experience possible. We also networked with a lot of developers and went back, content with spending our Sunday fruitfully.

    What we did today

    • Almost completed issue 385, but for one minor problem. We sent out the details of our problem to one of our coaches and our mentor.
    • Met with a coach today to discuss the complexities of issue 383.

    Agenda for the week

    • Meet out mentor and set goals for the next week.
    • Send in final PR's for all issues we have been working on

    Team Victorious Secret signs off for today!
    Stay tuned for further updates.

  • day 11

    Team Clojurians (re-frame) — at July 17, 2017 17:55 UTC

    • Saskia pair programmed with Dave
    • Chris looked at boot with Martin. Well it appears dirac works with boot (':
    • installed and played around with re-frisk and re-frame-trace