Matt Maier Log

From Open Source Ecology
Jump to: navigation, search

What I've been up to. User:Matt_Maier

Documents & Programs

  • Modular GVCS car concept and the CabCube concept



  • Worked on how to incorporate the Connexions website into OSE's development/publication process. It is a well established site already, and open source is at the core of its value, so despite not being absolutely perfect it is at least a great start.


  • Converted and posted all the current CAD describing Wikispeed's SGT01 vehicle Wikispeed_SGT01#CAD


  • Posted images of concepts related to GVCS modular vehicles in general and the open source car in particular.


  • Transferred more Wikispeed STG01 documentation to the OSE wiki.




  • Published the final(ish) draft of the LifeTrac fabrication report. Sent it out for comments and/or approval.
  • Updated the Distributed_Collaboration page with lessons learned and examples from the LifeTrac documentation.


  • Sent Aaron_Makaruk a draft of my distributed collaboration process proposal.
  • Created Distributed_Collaboration to document the method I'm working on for getting from machine prototypes to published reports.


  • Incorporated some of Marcin's notes into the tractor report. Also built and added clarifying illustrations.
  • Encouraged Expressman to create a "spec sheet" for the tractor that would answer the sort of questions people who are used to dealing with tractors would want answered. LifeTrac IV/User's Manual/Spec Sheet


  • Contacted James Slade of Creation Flame since he's field-testing the LifeTrac.
  • Added a lot more to version 2 of the LifeTrac Fab Instructions.
    • It seems to be working out that the blueprints should be organized by part/assembly but the instructions should be organized by material/activity. For example, if someone is going to build the thing, particularly if they're going to build it with one or more other people, they'll break up the work by stock material since different stock requires different tools (for the most part). Actually, it would make more sense to organize the build according to tools; have one person at the chop saw, another at the torch/welder, etc...but there's no way to know what kind of tools someone will have or how many. The next closest thing is the "action" like "cut something" and "weld something."
  • Exported a draft of version 2 of the instructions so people can see where it's going.


  • Uploaded examples of building blocks for the modular vehicle kit. Rotors for low rpm, high weight (unsuspended) and high rpm, low weight (suspended).
  • Contacted a custom metal fabricator in Houston.
  • Contacted D&H Tractors about opening communication. They're high school seniors who are building a LifeTrac for South Central Farmers.


  • Joined Team Wikispeed and exchanged ideas with team lead Joe Justice on a possible OSE/Wikispeed collaboration.


  • Called in to scrum with Lex (Daily SCRUM). Trying to convince other active developers to invest in some kind of centralized update/discussion process to maximize creativity and generate a team atmosphere.
  • Discussed CEBs on the forum.


  • Coordinated with Lex about his Collaborative Engineering project. He is going to upgrade FreeCAD with project management features.
  • Added information and Lessons Learned about Team Wikispeed. They demonstrated how a nominally open source and distributed collaborative engineering project can do seriously impressive things. They produced a street-legal car that gets 100 mpg and a 5-star equivalent safety rating.
  • Working on a concept for better machine fabrication documentation. After getting a bit stuck on the LifeTrac fabrication document, and having some time to step back and think, I realized that a dead, isolated document wasn't accomplishing enough goals simultaneously. I am experimenting with the open source and free OpenProj (basically a weak version of Microsoft Project) to see if documenting the machine fabrication as a project will better capture diverse pieces of information like time, ergonomics, and resources. Basically, replicating a machine IS a project, so it might as well be documented that way first. I predict that building the fabrication procedure in a project management program will automate the tracking of things like, say, how many bolts the tractor needs. Instead of tediously counting and double-checking, just enter the number of bolts at each step and the program will tally them all up in a report. Changes will be tracked automatically. Additionally, when it's finished people can download the free program, download the free project file, and input their own numbers (like how long it actually took them to do something). It will help them organize their project and it will help the FeF gather important feedback.


  • I've been posting on the forum and adding information to the wiki
  • Communicating with individuals about the the ironworker and program management/CAD program



  • Added FPGA rationale and resources
  • compiled a list of people to contact re: FPGA-centered universal axis controller
  • Added some specific info on construction vehicle modularity