Office Hour - Code Contributions - October 24, 2020

Thank you contributors :tada: :rocket::exclamation:

:tada: We are hosting another Office Hour :tada: Saturday, October 24, 2020 2:00 PM β†’ Saturday, October 24, 2020 2:45 PM.

If you signed up for the mailing list mentioned here, you should have gotten an invite. You should RSVP to that, to get a notification.

Note: A meeting link will be available in the invite.

Here is what you need:

  1. A working headset :headphones: (with a mic :studio_microphone:).

  2. Camera :video_camera:. Optional - We would love to see you though!

  3. Something to stay hydrated :tea::tropical_drink: :coffee: :beers:
    Sorry, you will have to bring your own because of the nature of meeting. :frowning:

Here is the agenda for the meeting:

  1. Quick 10 second intros of everyone :stopwatch: Share what you’ve been working on :elephant:

  2. Discuss outstanding issues on main repo and assign them to interested contributors.

  3. Discuss reviewing and merging of curriculum PR’s in wake of new MDX parser
    (Create single source of instructions and notes for back-end Node challenges Β· Issue #39720 Β· freeCodeCamp/freeCodeCamp Β· GitHub).
    (Create single source of user stories and notes for back-end Node certification projects Β· Issue #39721 Β· freeCodeCamp/freeCodeCamp Β· GitHub).

  4. Create new testable projects interface: designers wanted :pencil2:

  5. Hang out for a bit :smile_cat:

Note: We will add/update items before the meeting if need arises. If you have something specific that you would like to add please let us know in the comments.


P.S: Here is a list of all the office-hour meetings we have had.

I haven’t seen that email yet - did it just go out? Or did I miss it?

After doing a round of introduction and welcoming a couple of new (to the meeting, not fCC) contributors we discussed the following:

  • How Crowdin works. @ilenia demoed it to us, highlighting some of the cool features and how the UI is a little confusing. We discussed adding a guide.
  • The new chat client, how we might move over to it and the degree to which the bots might be migrated. @nhcarrigan pointed out that the api is different and that quite a lot of rewriting may be needed.
  • The mdx parser, what it’s for and why it’s needed before we can go ahead with translating the curriculum.
  • Contributing to open source in general and fCC in particular, including how to find something to work on. It’s clear we need to do better at making things available to new contributors.

Apologies if I missed anyone/anything.