open+pario [project hosting]

So myself and a buddy put together one of those black background/image panels about "What People Think I Do" but for engineers. Check it out below! And someone made a Russian version!

Hello!

open+pario is going through some substantive changes, and we just wanted to make sure that all current and past users are in the loop regarding new developments.

1. Upgrades and New Servers

We have moved open+pario to a new host (a linode datacenter in NJ, USA) , and have been transitioned from being university affiliated to an independent, not-for-profit organization.

Also, the site will only be available at openpario.net. All old links to openpario.mime.oregonstate.edu will be temporarily broken until OSU approves a year long 301 redirect that should help us avoid confusion!

Michael Koch and Richard Schulte are paying out of pocket for all costs associated with open+pario from here on-out! Donations will be gladly accepted once we add a paypal widget to the site this weekend.

2. Bugfixes and Updates

We have upgraded to the latest version of Redmine - a wonderful Ruby on Rails project management system that makes up most of the tools that open+pario provides.

3. New Features

We will also introduce several new features this weekend. They are designed specifically to make redmine easier to use in an educational and collaborative setting. They will also improve file management. If you chose to remain subscribed to this list, we will send out a message next week that announces these new features, with links to documentation that will explain how to take advantage of them.

Why now? Well, though we thank Oregon State University tremendously for their support since 2009, we are excited to finally have full control over the hosting environment so that we can more flexibly introduce new functionality, fix bugs, and more. This will be quite a game changer for open+pario!

We are also, as I suggested above, going to be opening up a project on open+pario for feature requests, including suggestions of features we have though of ourselves. We will be implementing a voting system so that the community can decide which features will be most useful. Just as a preview:

• WebGL rendering of 3d models from blender
• Assetts tab to access all file attachments for a project
• Thumbnails for image/pdf uploads
• Private Uploads (for providing assignments to instructors securely)
• SSL Encryption
• LaTeK support
• BOM management
• Gitolite Access top repos (upload your pubkeys!)
• R plotting (is that overkill?)

These are just a few ideas, some of which already exist for redmine, others will require custom development. Exciting huh? You can explore what plugins are already out there here: http://openpario.us4.list-manage1.com/track/click?u=92ba5de6d1e8096ece1e7baf2&id=f08e5dd71a&e=54185f52f8 or by searching on github.

We look forward to continuing to engage the needs of the open+pario community and make it a powerful tool for open and collaborative projects.

I had to use an Apple to do the conclusion, so in case the text didn't upload correctly, I have pasted it below:

Final Decision
Sprouting Education decided to use a combination of garden designs. The 1/3-1/3-1/3 Garden offers a variety of growing spaces which allows students to compare different gardening environments while keeping costs low by providing less sheltered, and inexpensive garden space for more resilient plants to grow. The Small Individual Pot Plot Garden offers students a space to call their own, allowing them to have more responsibility and reward in the garden. This design also provides an easy solution to summer maintenance of the garden as students can take their pots home to tend over the summer. Other integrations from designs will also be implemented such as the visual appeal of the Garden Train.

We will all meet Tuesday after our lab to peer review each others lit reviews. After you complete the topic you were assigned to, also sign up for a couple more so that we can make sure we cover all the topics; and note which additional topics you are taking on so that we don't have two people researching the same topic.
*Just a reminder, we all need to use at least one book source.

Finished issues #1736, #1737, #1738, #1739, #1741 and #1742 this week

I'm Working my way down this list: (http://www.cubespawn.com/600Motion.html) Creating the drawings for the components for the motion module this week.

since I am working in a sub-project, I doubt anyone is seeing the activity in the mailing list, but if your interested in the specifics it'll be listed here: http://openpario.mime.oregonstate.edu/projects/sxtfmotion

Here is a Link to the new CAD drawings, More to Follow!!

http://www.cubespawn.com/600mm.html

5 or so months ago - I took a stab at producing the needed drawings for part production.

I wasn't completely satisfied with the results, I made 2 errors on the prints, the shop made 2 additional errors on the parts and there was a brief communications problem.

The part designs have clarified since then, and I have studied a number of on-line tutorials for Solidworks, but best of all I have access to a workstation with a Solidworks install, so I will begin producing drawings and publishing them to the CubeSpawn site this week!!

DAK Esberg set the ball in motion but then left the field ;-) so I have undertaken to structure a part numbering system that'll remove ambiguity.

The short breakdown is thus:

For the cubes there are 4 known T-Slot materials that will be used to construct the frames and motion components:

These 80/20 materials are representative, but not comprehensive of the material types available:
25mm extrusions, (the "Official" international size)
40mm extrusions, (the "Medium Duty" international size)
1 inch extrusions,(the "North American" adaptation of the concept)
and, 1.5 inch extrusions - same as above.

This leads to mention of the sizes, since the system is based on 300mm increments:

300mm - this module will be a pick and place Cube first, one frame has been built from 1 inch material. i.e. a "310" frame

600mm - this is the main platform, due to its reasonable balance between cost and capability.

So the leading numerical group in the part number will denote the machines size and the framing material:
"610" for the 600mm built from 1 inch,
"625" for the Cube built from 25mm
"615" for construction from 1.5 inch, and
"640" for 40mm T-Slot

There will be 9 other digits in the part number to denote things such as "Class" i.e. 0F for a frame component 0M for a motion component
and so on - there will be a part number breakdown sheet posted shortly to clarify the intent and mechanics of the part numbering scheme...

So, a complete part # should look something like this:

06400F052000-01000

"0640" is 600mm built from 40mm T-slot "0F" means its a framing component "0520" denotes its 520mm long - but is arbitrary, meaning its not always going to refer to a part length, just SOME identifying/unique feature,
the last 2 zeros are for a part code, specifics yet to be determined.

The trailing 5 digits are "01" part version, and "000" revision number

I welcome comments if you know something I oughta ;-)

The name of this project was "ArchLinux Development Stack" or archlinux-devstack for short and is now ArchServer ALM Stack (or almstack for short). It can be found under the umbrella of ArchServer. Further additions can be found in my github.com account at Github.

For a short description of the first release of the ALM Stack, take a look on javafreedom.org.