Jozef Log

Status - Done: ...(see below) To Do: Meet re: Wiki 101, upload all badges to roster, edit HR & make weekly to-do list in interim, edit video for invitation Blocks: Meeting with Marcin & Dixon, waiting on marcin footage

D3D. D3D Log. Development Team Log. Dixon Log. Marcin Log. Roberto Log. Wiki Instructions. Wiki Formatting Help. OSE Hangout Jitsi Meetup. OSE Network. Time Sheet. Jozef's User Page

Saturday, July 29, 2017

Made simplified CAD place holder for limit switch File:Limit switch place holder.fcstd Made Screw 4 @ 1/2" File:Screw 4 at 1:2in.fcstd

Friday, July 28, 2017

1. Cross checked the CEB press assembly page to see who contributed for the design sprint and then check logs to see who had made dxf's. Those who add, I added the files the the CNC Cut list. Those who hadn't, I emailed. Added the [CNC cut files] section
2. I exported my rib as DXF and added it.

[2 hrs]

Wednesday, July 26, 2017

Watched Development Meeting, July 25, 2017 Watched 1st MicroHouse build Misc communications.

[2 hrs]

Monday, July 24, 2017

1. Reading: (Economies of...) Scope, Not Scale, 8 Forms of Capital so I could understand what 9 Forms of Capital are. Regenerative Enterprise
2. Reviewing instructions for D3D Workshop and installing programs
3. I think I found a print of demand option for OSE stickers at Rebubble which takes user generated designs and lets them set the markup...so I think we can use for both in house purchases and for merch (with no overheard).
4. Got sidetracked on really good opensource motorcycle build.

[5 hrs]

Saturday, July 22, 2017

1. For the CEB Design Sprint removed soil block (flat bar) File:CEB Rib 2.FCStd.zip and merged with the main assembly.
2. Reviewing OSE's long term educational plans: OSE Campus OSE Fellows, Dunbar's Number, What is the Monkeysphere?, Dedicated Project Visits, Extreme Manufacturing, Extreme Manufacturing Workshop, Factor e Farm Guidelines, Factor e Farm Community Standards, Contract-First Manufacturing, Integrated Human, From Henry Ford to Joe Justice: Wikispeed, Manufacturing in the Age of Open Collaboration, Poka-yoke (design for "mistake proofing"), Entrepreneur in Residence, Roadmap, EIR Review Process, Distributive Enterprise, D3D Business Plan
3. Made an OSE business card for myself: source file here. Since it may serve as a template for others, I'm going to submit it informally to team for review--seeking feedback on the following:
   1. Content: How is text? Additional links or information? Add Open Hardware logo?
   2. Form: Layout? People ok with vertical?
   3. Medium: Thought it would be cool to cut & etch them in house with the CNC Circuit mill and save a bunch of money on cards.

[4 hrs]

Monday, July 17, 2017

Replying to emails. Updating spreadsheet. [1 hr]

Sunday, July 16, 2017

1. Outlined a proposal for the criteria for advancing through the karate belts toward an OSE Black Belt Dev Ninja
2. Made badges for Antonio, Alejandro, and Sarah and emailed welcome email to Alejandro.
3. Nudged people to add/edit their bios (Dixon, Christian, Will) and format logs. Reminded Christian and Will to do time sheets this round.
4. Checked in with current devs whose weekly numbers are down (Dixon, Kassie, Chas) to see if they're ok / need help or new tasks.
5. Emailed old AWOL developers in good standing (Laszlo, Jean-Baptiste, Emmanouil, & Jonathan) to investigate whether/when/how they might like to be involved.
6. Made a Developer Roster to integrate the following in a consolidated list (as I previously went on a scavenger hunt for it):
   1. developers past and present (in chronological order of joining)
   2. their Dev number (on the badge), which I think was previously only documented in the HR email
   3. their badge files
   4. status: active, former, adjunct (proposing adjunct as a category for a former developer in good standing who now takes occasional projects)
   5. karate rank
7. Proposed a sort of growth template / badge reward for all our 101 pages in general, and Wiki 101 page in particular and a meeting agenda I'd like to have with Dixon and Marcin about it. (Is anybody else interested in documentation and education?)
8. Added Dev graphs (of progress toward 120 hours & two week avg as snapshot of engagement) to working document for hangout.
9. Started new edit of Human Resources Operations Manual organizing the existing content into four main headings of the basic job description (General Promotion, Recruiting, Onboarding, Support) in the chronological / practical sequence in which those tasks naturally happen.
10. Met with farmer about interest in marijuana application of OSE aquaponic greenhouse. Planning follow up.
11. Searched for companies that sell custom stickers with no minimum / print on demand option for developer swag (at completion of 1st dev cycle). Some options I want to explore Makestickers, Stickeryou Printaholic Vistaprint most are approx $10 though I think, excepting vistaprint.
12. Made OSE instagram and added login info & pw on second sheet of spreadsheet sharing in-house contact info--so hypothetically any Dev can upload a picture or edit.

[9hrs]

Saturday, July 15, 2017

Reviewed last meeting (2hrs) Communicating with Antonio in really bad Portuguese. [3 hrs]

Thursday, July 13, 2017

1. Finished spreadsheet
2. Wrote Marcin about results, engagement, incentives, etc.
3. Edited the Welcome Email page to update the new welcome email.
4. Learned how to edit badges on Inkscape from the HR Operations Manual.

[5 hrs]

Wednesday, July 12, 2017

1. Began making the spreadsheet for tallying total developer hours and bi-weekly engagement.
2. Grass roots sharing about OSE in Grass Valley, CA

[1 hr]

Monday, July 10, 2017

Review the Human Resources Operations Manual. [1hr]

Sunday, July 9, 2017

1. Finished the script.
2. Worked on business card template
3. Misc. communications

[3 hrs]

Saturday, July 8, 2017

1. Catching up on communications
2. Started New Invitation to Developers Video Script

[5 hrs]

Monday, June 26, 2017

Completed draft one of the video for the New Developer Orientation but I need to make sure ppl are ok with it bc it snaps by the developer contact info. I want to make sure it's ok with developers first if I just keep the youtube video unlisted since I don't want to compromise their contact info. [4 hrs]

Sunday, June 25, 2017

Working on New Developer Orientation video. Approx 80% shots complete. [3 hrs]

Saturday, June 24, 2017

• Just finished re-editing the Developer Test and New Developer Orientation which clarifies the script for the video, which I'm back on after a little backtracking.
• Misc communications with developers about posting on the Developer Test page, getting bios up on the OSE Developers Page, and supporting engagement.

[3 hrs]

Wednesday, June 21, 2017

Trying to figure out how to migrate the old Disqus thread on FreeCAD 101 to the Developer Test. It seems to copy a new blank discussion thread but not bring any of the old discussion over. >=1

[1.5 hrs]

Tuesday, June 20, 2017

Developer Test almost complete. I'm stuck @ the Disqus comments though. Need help migrating the Disqus comments over from FreeCAD 101. I tried copying the code but it came out wonky and I'm not sure why.
FreeCAD 101 restructured as a tutorial-in-construction for each of our tasks. Headings greatly simplified.
All prior items sorted out so I began final edit of New Developer Orientation.

[3 hrs]

Sunday, June 17, 2017

Made contact information sheet and emailed everyone individually.

Started following up with people about posting bios.

Completed Developer Test.

Restructured FreeCAD 101 as follows:

• Overview
• General FreeCAD resources (manuals, forums, youtube series)
• Task 1: Build a Corner Cube
• Task 2: Convert STL's for Smaller File Sizes
• Task 3: Create Final Assemblies
• Task4: Extract Isometric views...
• etc.

This makes it a sort of repository of 1) General Resources and 2) OSE Tasks (as we develop them). I need the OK to complete the edit as it would remove much content, and relocate the test.

[5 hrs]

Thursday, June 15, 2017

Spoke with Dixon about an onboarding flow that resolves gaps, redundancies, and backtracking in the new applicant / new developer user experience. [1.5 hr] I copied the test items from FreeCAD 101 over to a new page Developer Test. (I won't change the FreeCAD 101 page until the new flow is fully operational.) [1.5 hrs]

Tuesday, June 13, 2017

This week's goals: a) Complete Welcome Vid for New Developer Orientation; b) determine a good messaging app; c) collect and share Dev Team's contact info in-house (since survey reveals majority prefers text for quick com); d) settle on template with Dixon for 101 pages e) start on simplifying an stl file with Kassie.

Capturing more screen shots for new orientation video and digging up a couple of props. [1.5 hrs]

Sunday, June 11, 2017

First, I was 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 (though I do). 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 like (FreeCAD 101, Wiki 101, KdenLive 101, etc.
   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. Because 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.
   2. However, as the tutorials cover the material they could conveniently cover exactly the material required first by the applicant and second by the developer.

Second, Regarding the Technical Community Development role, I want to gather some information from everybody and am comparing free survey websites: Survey Nuts and Survey Monkey which has a free version. Draft of questionnaire items here. Third, worked on some screen captures for the New Developer Orientation vid.

[7 hrs]

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.