Jozef Log

D3D. D3D Log. Development Team Log. Abe Log. Dixon Log. Kassie Log. Marcin Log. Polemidis Log.

Wiki Instructions. Wiki Formatting Help. OSE Jitsi Meetup. OSE Network. Time Sheet.

Sunday, June 11, 2017

Discussing the architecture of OSE onboarding and educational materials for applicants and developers with Dixon. This was my initial proposal. Or see the picture here:

1. Propose making a dedicated Developer Test page by extracting the test items from FreeCAD 101 page and relocating them there with a) test prompts, and b) linked help resources (our 101 series). My thoughts are as follows:
   1. Consolidating test prompts on a dedicated page makes them easier to find under a more appropriate and logical heading. This also tidies up FreeCAD 101 to be a dedicated tutorial space instead of muddling it with applicant admin.
   2. By separating help resources from the test and making them optional, it allows people to cherry-pick their help resources during the application process. Those applicants who do not need help with the wiki, linux, etc., they're saved from being universally funneled through a bunch of slow motion classes that they do not need. I think this is a more "modular" design serving different end-users (from newbie-to-pro), who may use none, some, or all of the supplemental 101's. This gives them the option to skip, refresh, or learn from scratch.
2. Propose making dedicated 101 Tutorial pages on our toolchains.
   1. Organizing help resources by higher order tasks vs. "elemental" program skills. If we build pages around tasks (like "documentation") instead of programs (wiki101, google docs 101, etc.) then I'd worry about a ton of overlap (duplication and ambiguity) between them. Bc a lot of tasks potentially include the same multiple programs in combination (sharing google docs on google hangouts, sharing google docs on the wiki. etc.) You potentially end up with more pages and less certainty about where to find what you need. I think the stricter logic of labels serves more intuitive navigation.

Thursday, June 8, 2017

Got the Welcome Email reviewed by Marcin, and paired it down. Migrated the rest of the email content to the New Developer Orientation page, and there I separated the content out in terms of (1) General Practices and (2) New Developer's To-Do List.

[3hrs]

Sunday, June 4, 2017

Completed the overview of the Onboarding Flow here. In line with that, here's:

1. Proposed Welcome Email edit.
2. The New Developer Orientation page to help new developers get set up their first week. It consolidates their action items and provides help resources for each of the tools we use.
3. The New Developer Orientation page links to the following tutorials which need to be developed. (For the meantime I just added some helpful links as placeholders until we make our own. There isn't any text or intro at present. We should probably have a simple template for each 101 page.)
   1. Wiki 101 Seems to me some/much of the content from Wiki Instructions could be migrated here.
   2. Google Drive 101
   3. Google Docs 101
   4. OSE Network 101
   5. etc.
4. The Video Script for the orientation page.

[3 hrs]

Wednesday, May 31, 2017

I'm working on streamlining an onboarding content overview which I'm breaking down into three categories:

1. Welcome and orientation email. (This says hi and lays out ground rules and leads new developers to step #2.)
2. New Developer To-do list wiki page with embedded video walkthrough. (This takes the newbie through all the basic tasks and links them to #3.)
3. OSE Dev Tool Instructionals. I'm envisioning each dev tool as having it's own wiki page with a short series of condensed videos--not exhaustive but with sufficient material to get people up to speed for our most common tasks....
   1. OSE Wiki 101
   2. VokoScreen 101
   3. KdenLive 101
   4. FreeCAD 101
   5. etc.

Now I'm moving on to the video walkthrough script for the new developer to do list (#2).

[2.5 hrs]

Tuesday, May 30, 2017

I'm working on the on-boarding content & arrangement here. It's my understanding that you're on your own for the FreeCAD test, but that once you're on the team you're on the team; and that OSE switches to a support role and does not treat any question as stupid in principle. Everybody needs to get up to speed on the development tools (the wiki, FreeCAD, jitsi/hangouts, google drive, docs, etc.) if they are not already, so I started hunting down short vids as instructional references.

[2 hrs]

Monday, May 29, 2017

Marcin and I discussed temporarily shifting me from the D3D project to a community development role, so I worked on the following:

1. I reviewed the Onboarding Flowchart which seems to suggest that familiarity with workflow and culture occur prior to joining a team (unless I'm mistaken). I want to redefine 'on-boarding' in terms of getting everyone (and me!) aboard a project by:
   1. Getting familiar with the communication platforms (jitsi, google hangouts, OSE network), protocol, and team members. (I'm clumsy and I've only said hi to one team member!)
   2. Attending meet-ups regularly, and contributing ideas (I missed today's meeting which I thought was tomorrow. I lucked out and it got postponed.)
   3. Producing good logs in terms of content/files, arrangement, and style. (One litmus test is that several of us have been 'on-boarded' at the same time and none of our logs look the same.)
   4. Getting everyone engaged and communicating with their team members. (Do any of us have each other's emails or phone numbers handy?)
   5. Competently using the universal bundle of OSE dev tools: the wiki, google docs, etc... (Actually, what else?)
   6. Submitting time-sheets consistently.
   7. [...]
2. I pulled the "Welcome Email" content and am editing it here. From my POV the issue is not content but arrangement and medium. My thought was to rearrange it into:
   1. The Welcome and General Orientation
   2. New Developer To-Do list with embedded help video. By the way, the video would depend on the to-do list so I want to get that nailed down before working on that.

[4 hrs]

Thursday, May 25, 2017

To familiarize myself with the D3D project overview I reviewed:

1. The Construction Manual for Lyman's Filament Extruder V6 pdf.
2. The video of Lymen's Extruder V6 with Spool Winder .
3. The Filament Maker Team Meeting 5/22/2017.
4. The Spooler files for the Lyman Filament Extruder.
5. In the The May 22-23 Development Team Meeting Marcin said I'd trace the winder files and Kassie would take the spooler files, but on review they're somewhat mixed with miscellaneous files. I tried getting in contact with Kassie via the OSE Network to say, to say "Hey all the mixed files are numbered 1-15. Let's just split them roughly down the middle, and I'll take 1-8, and you take 9-15 (or whatever)," but reached the character limit prematurely.
6. I was trying to figure out why I'm tracing the stl. files in the first place. I think I'm tracing solids in sketcher to create equivalent meshes to keep file size down?

Wednesday, May 24, 2017

Took care of new developer housekeeping:

1. Replied to the HR email to supply info for the team bios.
2. Read the Daily Log of Tasks to review Best Practices for logging work.
3. Started to set up this log with the appropriate links, etc. I've never contributed on a wiki so I skimmed over Wiki Formatting Help to help me with formatting (I added the link up top for quick reference), and spent a little time looking at other developer logs and flipping back and forth between their Read & Edit pages to see how they got different formatting effects.
4. Signed up at OSE Network
5. Shot an email to a local guy who runs Linux on a Mac to try and get help with the dual boot. I'm currently running Ubuntu 16.04 on Parallels as a short term fix, but I need a game plan and don't have one yet.
6. Learned how to add images on the Wiki Instructions page so I could add my badge, and referred to Image Help to learn how to scale it down.

Saturday, May 20, 2017

File:Jozef Mikler's FreeCad Test cube.fcstd and YouTube video.