Open Source Ecology - User contributions [en]

Gregoryfoster Log

2017-04-24T16:41:43Z

Gregoryfoster: /* Links */ Adding link to D3D Printer Development Group on OSE Network

=Links=
[[D3D]] - [http://network.opensourceecology.org/groups/profile/676151284687970315/activity D3D Printer Development Group on OSE Network] - [https://hangouts.google.com/hangouts/_/event/cfvdskolaipjgki95aoufjf3l50?hl=en&authuser=0 D3D Meeting Hangout] - [[D3D_Meeting_Log]] - [[Timesheet]]

=Thursday Apr 17, 2017=
* Completed FreeCAD 101 Test ([[File:2017_04_18-freecad101.fcstd]])
* Posted video to [[FreeCAD_101#Self-Verifying_FreeCAD_Exam_Videos]]

[[Category:Logs]]

User:Gregoryfoster

2017-04-24T15:45:39Z

Gregoryfoster: Adding link to Log

humbled by redwoods; Founder @foojutsu; formerly @ConsumersUnion @EFFAustin

One Two Three Four Five Six Seven Eight Nine Ten
Ten-One Ten-Two Ten-Three Ten-Four Ten-Five Ten-Six Ten-Seven Ten-Eight Ten-Nine Ten-Ten
Twenty-One Twenty-Two Twenty-Three Twenty-Four Twenty-Five Twenty-Six Twenty-Seven Twenty-Eight Twenty-Nine Twenty-Ten
Thirty-One Thirty-Two Thirty-Three Thirty-Four Thirty-Five Thirty-Six Thirty-Seven Thirty-Eight Thirty-Nine Thirty-Ten
Forty-One Forty-Two Forty-Three Forty-Four Forty-Five Forty-Six Forty-Seven Forty-Eight Forty-Nine Forty-Ten
Words Minimum.

http://https://keybase.io/gregoryfoster

==Open Source Ecology==
* [[Gregoryfoster_Log]]

Gregoryfoster Log

2017-04-19T15:07:58Z

Gregoryfoster: Adding links to top of log

=Links=
[[D3D]] - [https://hangouts.google.com/hangouts/_/event/cfvdskolaipjgki95aoufjf3l50?hl=en&authuser=0 D3D Meeting Hangout] - [[D3D_Meeting_Log]] - [[Timesheet]]

=Thursday Apr 17, 2017=
* Completed FreeCAD 101 Test ([[File:2017_04_18-freecad101.fcstd]])
* Posted video to [[FreeCAD_101#Self-Verifying_FreeCAD_Exam_Videos]]

[[Category:Logs]]

Gregoryfoster Log

2017-04-19T01:30:36Z

Gregoryfoster: /* Thursday Apr 17, 2017 */ Using bullets

=Thursday Apr 17, 2017=
* Completed FreeCAD 101 Test ([[File:2017_04_18-freecad101.fcstd]])
* Posted video to [[FreeCAD_101#Self-Verifying_FreeCAD_Exam_Videos]]

[[Category:Logs]]

Gregoryfoster Log

2017-04-19T01:29:08Z

Gregoryfoster: Adding "Logs" Category to page

=Thursday Apr 17, 2017=
Completed FreeCAD 101 Test ([[File:2017_04_18-freecad101.fcstd]]). Added [[FreeCAD_101#Self-Verifying_FreeCAD_Exam_Videos]] video.

[[Category:Logs]]

Daily Log of Tasks

2017-04-19T01:22:42Z

Gregoryfoster: /* Guidelines */ typo

<span style="color:red">Last updated Dec 10, 2016 </span>

=Instructional Video on How to Write a Work Log=

<html><iframe src="http://popcorn.webmadecontent.org/12ii_" width="640" height="403" frameborder="0" mozallowfullscreen webkitallowfullscreen allowfullscreen></iframe></html>

=Introduction=
OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for planning, review, and coordination. It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration over the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

=Instructions Summary=
To start a work log, set up an account and log in to the Wiki - see [[Instructions]]. Then create a page titled Your_Name_Log - such as [[Marcin Log]]. Keep daily entries for every day Monday-Friday, and record entries with a date. The format for the dates should be placing the date in between = signs (this is a heading in Wiki language). The proper heading format is, for example, "Tue Apr 8, 2014". Then, record newer entries on top, so that one does not have to scroll down a page to see your latest work. When recording entries, you should have a link or picture embed to all that you have done.

=List of Logs=
*See [[Logs]] for project-based and person-based logs.

=Work Log Checklist=

'''Log your work for learning purposes - so you can learn to do it better the next time.''' This is a list of best practices for logging work for OSE:

#Did you link to your work product?
#When listing items that you have done, did you write down a complete list to avoid potential redundancy with other collaborators working in parallel?
#Is the entry specific, so others could help?
#Is the entry '''self-verifiable'''? That is, is there a link to work product or other evidence that the work has actually been done, or that you and not someone else did it?
#Are you keeping weekly planning goals on your log?
#Are you formatting your log with the latest entry on top, and date formatted as in [[Marcin Log]] as an example?
#Is continuity/progress visible in your log?
#Are you using the versioning capacity of the wiki to upload new files?

=Key Points=
*Update log daily or as relevant work is done. Presumption of non-logging in a given time period is that no work has been done.
*Add most recent update on top of page
*Link directly to new results every day so that result can be viewed in one click from your log
*Log items that have been logged previously, if updates have been made to those links
*If you are linking to an update on a page and only a small item has changed on that page, link to that specific item that has been changed - if possible.
*Keep log tight and short. Put all results on other pages, and link to those pages - so that a comprehensive picture of one's work is seen immediately. See [[Marcin Log]] as an example.
*At best, the Work Log should consist mostly of hyperlinks, with short description of what the hyperlink is.

==Design Rationale==
Log of progress should include who was contacted, resources found, links to work product generated, comments on what is working and not working, and any insights on the organizational process. See [[Marcin Log]] for an example. Tasks shall be logged as soon as they are completed. This is intended for:
*'''Organizational learning''' - to assess and review the duration of tasks, scope of tasks performed, what worked and what didn’t. Future team members can look at the log, learn from the tasks done, and assess the time that it takes to do certain tasks.
*'''Team coordination and project status'''- Work logs are universally identified within the team as a location for logging activity, and have a unique URL that any other team member can access, as in opensourceecology.org/wiki/Name_Log - with the name corresponding to the team member’s name. Any team member can view another person’s log. Since the log is done on a continuous basis as soon as tasks are comppleted, anyone can find out what has been done as soon as it has been done.
*'''Transparency'''. This allows other team members to see what is happening for purposes of transparency. Credit can thus be given properly to those who log tasks. If a task is not logged, others can not learn more about that task. Such trasnparency promotes autonomous operation within OSE.
*'''Self-Verifiability'''. Self-verifiability is an aspect of Transparency. Self-verifiability of the work log can be achieved by linking directly to work product - so that credit can be given for work done.
*'''Management scalability''' - Work logs provide universal indexing of a person’s work. Once there is a large number of people working on a project, an easy way to access a person’s work product is through the person’s log. The log is intended to be accessible with zero access barriers, an essential part of an open, collaborative organization. A log allows indexing of large amounts of disperse content from an unlimited number of people.
*'''Open culture''' - Work Logs are visible to the world, and thus promote working openly and collaboratively.

==Effective Communication==
To facilitate effective communication via the Daily Log, keep the following points in mind in order to help others learn rapidly from and assess your work.
*'''First and foremost - log your work in a concise paragraph instead of spreading it over a number of pages, and link to work product on other pages instead of embedding work product on the Work Log.''' This allows one to see daily work and weekly work product readily.
*Critical insights should be captured in the log. If a link is simply posted, one cannot tell what to expect from the link.
*The power of the wiki lies in using wikiwords - ie, a word or phrase in double brackets in edit mode allows you to link directly to any other page or subheading on the wiki. This way, you can build on former work without having to explain each time. Any wikiword becomes its own page on the wiki.
*Communicate as much as possible like you are commuinicating to the first-time reader in order to provide perspective. This means for concepts or formerly entered concepts or pages - link to those pages in your explanations as wiki words.
*Feel free to create pages that are simply definitions of words or phrases that you are using - so you can refer to that page any time in the future by putting the link in double brackets.
*Do not overwrite wikiwords that are already used if you are documenting a different usage of that wikiword, just start a page with a different wikiword. This is because any other pages that link to that page would then be pointing to the wrong definition.
*To inform the reader more fully, try to provide context as relevant. For example - if a link is a new entry in the wiki, write 'Started page so and so'.
*Always try to inform the reader about the context and perspective of your work. Useful work could be finding, sourcing prices, finding an online design calculator, reading, reviewing, starting wiki pages, editing a wiki page, continuing on work from another day, making video, taking pictures, writing an instructional, conference calling, getting something reviewed, picking up where someone else left off, etc... Please make a note of such activity and include a link to anything online, and for something that you generated (picture, document, video), upload it and link to it.
*If you want to upload an unsupported file format to the wiki which the wiki does not allow you to upload - compress it to a zip or other format and upload it then. The wiki supports uploads of compressed files such as .zip.
*If you are adding to an existing page, think of creating a subsection so that you can link to it directly as a wiki link. Otherwise, the only way for the reader to see what you have contributed is to look at the page history, which takes more time.
*If you are reporting a physical result, you should include a picture or video.
*If you are reporting a concept design, link to a google doc drawing or other diagram .
*If you are doing conceptual design - use google docs - so others can view and download the source. Set up sharing accordingly.
*If you are embedding google docs, paste a link to the actual document so others can access it directly to view, comment, or edit. This allows global collaboration to happen.
*When posting pictures or files - do not just put them on your log - but also on the related wiki page for that particular project.
*If you are uploading pictures as a zipped file - embed at least some of the pictures or thumbs themselves for viewing - for easy access - especially if the file is large and it takes a long time to download just to view the pictures.

==Guidelines==
To make the most use of the log as a cloud platform:
*Keep track of and coordinate with other core developers. Take any name - and you should be able to find their log: ex: [[Marcin Log]], [[Gabi Log]], [[Yoonseo Log]], [[Lenny Wayne Log]].
*There are also project based logs - [[Guatemala Log]], [[Power Cube Log]] - in addition to personal logs - for tracking projects which have multiple participants.
*Any documentation relevant to GVCS technical deployment - video, pictures, diagrams, reviews, etc - should be copied to or linked to the wiki. For example, a picture of a build should be embedded in a wiki procedure, and if there is a relevant album of images, that link should be placed on the wiki.
*Google Docs should be embedded and an Edit link should be added for easy access.
*Iframes and other embeds should be taken advantage of - to make the Wiki a central repository of all project-related material.

==Standards==
*Document any work relevant to critical path as on the [[Critical Path]] for deploying the GVCS and building the world's first, post-scarcity, open source, global village.
*Weekly project meetings are logged at the [[D3D Log]] for the 3D printer.
*'''Use hyperlinks for work product.''' Do this by putting hyperwords in double brackets. See [[Wiki Instructions]].
*Make every day indexable by entering it as a heading, such as =Thu Oct 11, 2012=, such that any day can be accessed from an automatically-generated index on top of wiki page.
*Use Weekday, Month, Day, Year as standard headings, such as =Thu Oct 11, 2012=
*Roll up entries into a single link on a monthly basis, see bottom of [[Marcin Log]] for example.

=How To=

For a log to be effective it should provide on a daily basis:

#Tasks done
#Comments on important learnings
#Links to all work product that took more than 15 minutes to complete. All work should be documented on wiki
##This is easy for organizational work: start a wiki page with what you did with links
##For physical work, take pictures and vlogs, link to them as your work product
#Do this on a running basis to allow the log to serve as a monitor of progress that other team members can use to facilitate coordination on a sub-hour timescale

On a weekly basis - the Log should provide a Weekly Assessment- including Planning and Review:
#At the beginning of the week, list your goals for the week
#At the end of the week, assess:
##Did you meet your milestones?
##If not, why not, and how you can do better?

==Execution==

Make it really simple. Start a wiki page named Name_Log, such as [[Marcin Log]]. Add new posts on top of page. Every two weeks, roll up the entries into a 2 week history - so the Index doesn't get too lengthy. Repeat for every month, quarter, and year.

#Log tasks in an ongoing fashion.
#Week plan due Monday: what do you intend to do this week (in your own words)
#What did you in fact do this past week? What unplanned items?
#What is your own assessment of that / your progress?

#Share it with each other - over Monday dinner?
#Sharing it means, if you didn't do it, you at least have to think about it while being shared.
#You want to write things down, because then it'll be hard to think of things you did, and it'll look to the group like you didn't do anything.

=Explanation of Daily Log=

The purpose of the Daily Log is to facilitate organizational learning and performance management by promoting feedback, assessment, and transparency. The Daily Log is required for people at Factor e Farm.

A Log allows others to access quick links to review work - which is highly relevant when working on a distributed team where many people provide feedback. This assumes that links must be explicit - we do not assume that someone knows how to find a link online.

When people log their work - this work can be evaluated and assessed for efficiency, direction, and prioritization. Without a task log, it is not possible to evaluate and learn about what a person is doing.

Further, OSE is an organization that incubates other [[OSE Incubators]]. For organizational learning across these Incubators and other OSE Chapters, it is important to document what people are doing to clarify expectations/process/etc.

Further, the weekly Log serves as the basis for [[Monthly Planning and Review]]:
#What were the major milestones reached?
#What were the major milestones missed?
#What did you learn this month?
#What could you have done better?
#What are your milestones for next month?

See sample Daily Log - [[Marcin Blog]]

=Comments=
From [[Colby]]:
Have a process where people set their own goals and timeline and present them to the group and file them on a wiki.
Then meet weekly and have them add a status update with what they accomplished over the week (or even daily).

Each month, have them present to the group the summary of their accomplishments each week, lessons learned, how they are on schedule, what "unplanned items" came up that delayed the schedule.

Keep track over time, the number of weeks in which they hit their own goals and didn't. Offer each time they don't hit their goals that they can come for you for advice.

The same thing applies to under and over budget, etc.

Once a month or week, take part of a day and sit down with each person for 10-15 minutes to discuss what is going well and isn't... and look at their progress reports and schedule.

=Links=
*See list of logs - [[Logs]]

[[Category:Structuring]]
[[Category:Logs]]

Daily Log of Tasks

2017-04-19T01:21:42Z

Gregoryfoster: /* Effective Communication */ typo

<span style="color:red">Last updated Dec 10, 2016 </span>

=Instructional Video on How to Write a Work Log=

<html><iframe src="http://popcorn.webmadecontent.org/12ii_" width="640" height="403" frameborder="0" mozallowfullscreen webkitallowfullscreen allowfullscreen></iframe></html>

=Introduction=
OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for planning, review, and coordination. It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration over the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

=Instructions Summary=
To start a work log, set up an account and log in to the Wiki - see [[Instructions]]. Then create a page titled Your_Name_Log - such as [[Marcin Log]]. Keep daily entries for every day Monday-Friday, and record entries with a date. The format for the dates should be placing the date in between = signs (this is a heading in Wiki language). The proper heading format is, for example, "Tue Apr 8, 2014". Then, record newer entries on top, so that one does not have to scroll down a page to see your latest work. When recording entries, you should have a link or picture embed to all that you have done.

=List of Logs=
*See [[Logs]] for project-based and person-based logs.

=Work Log Checklist=

'''Log your work for learning purposes - so you can learn to do it better the next time.''' This is a list of best practices for logging work for OSE:

#Did you link to your work product?
#When listing items that you have done, did you write down a complete list to avoid potential redundancy with other collaborators working in parallel?
#Is the entry specific, so others could help?
#Is the entry '''self-verifiable'''? That is, is there a link to work product or other evidence that the work has actually been done, or that you and not someone else did it?
#Are you keeping weekly planning goals on your log?
#Are you formatting your log with the latest entry on top, and date formatted as in [[Marcin Log]] as an example?
#Is continuity/progress visible in your log?
#Are you using the versioning capacity of the wiki to upload new files?

=Key Points=
*Update log daily or as relevant work is done. Presumption of non-logging in a given time period is that no work has been done.
*Add most recent update on top of page
*Link directly to new results every day so that result can be viewed in one click from your log
*Log items that have been logged previously, if updates have been made to those links
*If you are linking to an update on a page and only a small item has changed on that page, link to that specific item that has been changed - if possible.
*Keep log tight and short. Put all results on other pages, and link to those pages - so that a comprehensive picture of one's work is seen immediately. See [[Marcin Log]] as an example.
*At best, the Work Log should consist mostly of hyperlinks, with short description of what the hyperlink is.

==Design Rationale==
Log of progress should include who was contacted, resources found, links to work product generated, comments on what is working and not working, and any insights on the organizational process. See [[Marcin Log]] for an example. Tasks shall be logged as soon as they are completed. This is intended for:
*'''Organizational learning''' - to assess and review the duration of tasks, scope of tasks performed, what worked and what didn’t. Future team members can look at the log, learn from the tasks done, and assess the time that it takes to do certain tasks.
*'''Team coordination and project status'''- Work logs are universally identified within the team as a location for logging activity, and have a unique URL that any other team member can access, as in opensourceecology.org/wiki/Name_Log - with the name corresponding to the team member’s name. Any team member can view another person’s log. Since the log is done on a continuous basis as soon as tasks are comppleted, anyone can find out what has been done as soon as it has been done.
*'''Transparency'''. This allows other team members to see what is happening for purposes of transparency. Credit can thus be given properly to those who log tasks. If a task is not logged, others can not learn more about that task. Such trasnparency promotes autonomous operation within OSE.
*'''Self-Verifiability'''. Self-verifiability is an aspect of Transparency. Self-verifiability of the work log can be achieved by linking directly to work product - so that credit can be given for work done.
*'''Management scalability''' - Work logs provide universal indexing of a person’s work. Once there is a large number of people working on a project, an easy way to access a person’s work product is through the person’s log. The log is intended to be accessible with zero access barriers, an essential part of an open, collaborative organization. A log allows indexing of large amounts of disperse content from an unlimited number of people.
*'''Open culture''' - Work Logs are visible to the world, and thus promote working openly and collaboratively.

==Effective Communication==
To facilitate effective communication via the Daily Log, keep the following points in mind in order to help others learn rapidly from and assess your work.
*'''First and foremost - log your work in a concise paragraph instead of spreading it over a number of pages, and link to work product on other pages instead of embedding work product on the Work Log.''' This allows one to see daily work and weekly work product readily.
*Critical insights should be captured in the log. If a link is simply posted, one cannot tell what to expect from the link.
*The power of the wiki lies in using wikiwords - ie, a word or phrase in double brackets in edit mode allows you to link directly to any other page or subheading on the wiki. This way, you can build on former work without having to explain each time. Any wikiword becomes its own page on the wiki.
*Communicate as much as possible like you are commuinicating to the first-time reader in order to provide perspective. This means for concepts or formerly entered concepts or pages - link to those pages in your explanations as wiki words.
*Feel free to create pages that are simply definitions of words or phrases that you are using - so you can refer to that page any time in the future by putting the link in double brackets.
*Do not overwrite wikiwords that are already used if you are documenting a different usage of that wikiword, just start a page with a different wikiword. This is because any other pages that link to that page would then be pointing to the wrong definition.
*To inform the reader more fully, try to provide context as relevant. For example - if a link is a new entry in the wiki, write 'Started page so and so'.
*Always try to inform the reader about the context and perspective of your work. Useful work could be finding, sourcing prices, finding an online design calculator, reading, reviewing, starting wiki pages, editing a wiki page, continuing on work from another day, making video, taking pictures, writing an instructional, conference calling, getting something reviewed, picking up where someone else left off, etc... Please make a note of such activity and include a link to anything online, and for something that you generated (picture, document, video), upload it and link to it.
*If you want to upload an unsupported file format to the wiki which the wiki does not allow you to upload - compress it to a zip or other format and upload it then. The wiki supports uploads of compressed files such as .zip.
*If you are adding to an existing page, think of creating a subsection so that you can link to it directly as a wiki link. Otherwise, the only way for the reader to see what you have contributed is to look at the page history, which takes more time.
*If you are reporting a physical result, you should include a picture or video.
*If you are reporting a concept design, link to a google doc drawing or other diagram .
*If you are doing conceptual design - use google docs - so others can view and download the source. Set up sharing accordingly.
*If you are embedding google docs, paste a link to the actual document so others can access it directly to view, comment, or edit. This allows global collaboration to happen.
*When posting pictures or files - do not just put them on your log - but also on the related wiki page for that particular project.
*If you are uploading pictures as a zipped file - embed at least some of the pictures or thumbs themselves for viewing - for easy access - especially if the file is large and it takes a long time to download just to view the pictures.

==Guidelines==
To make the most use of the log as a cloud platform:
*Keep track of and coordinate with other core developers. Take any name - and you should be able to find their log: ex: [[Marcin Log]], [[Gabi Log]], [[Yoonseo Log]], [[Lenny Wayne Log]].
*There are also project based logs - [[Guatemala Log]], [[Power Cube Log]] - in addition to personal logs - for tracking projects which have multiple participants.
*Any documentation relevant to GVCS technical deployment - video, pictures, diagrams, reeviews, etc - should be copied to or linked to the wiki. For example, a picture of a build should be embedded in a wiki procedure, and if there is a relevant album of images, that link should be placed on the wiki.
*Google Docs should be embedded and an Edit link should be added for easy access.
*Iframes and other embeds should be taken advantage of - to make the Wiki a central repository of all project-related material.

==Standards==
*Document any work relevant to critical path as on the [[Critical Path]] for deploying the GVCS and building the world's first, post-scarcity, open source, global village.
*Weekly project meetings are logged at the [[D3D Log]] for the 3D printer.
*'''Use hyperlinks for work product.''' Do this by putting hyperwords in double brackets. See [[Wiki Instructions]].
*Make every day indexable by entering it as a heading, such as =Thu Oct 11, 2012=, such that any day can be accessed from an automatically-generated index on top of wiki page.
*Use Weekday, Month, Day, Year as standard headings, such as =Thu Oct 11, 2012=
*Roll up entries into a single link on a monthly basis, see bottom of [[Marcin Log]] for example.

=How To=

For a log to be effective it should provide on a daily basis:

#Tasks done
#Comments on important learnings
#Links to all work product that took more than 15 minutes to complete. All work should be documented on wiki
##This is easy for organizational work: start a wiki page with what you did with links
##For physical work, take pictures and vlogs, link to them as your work product
#Do this on a running basis to allow the log to serve as a monitor of progress that other team members can use to facilitate coordination on a sub-hour timescale

On a weekly basis - the Log should provide a Weekly Assessment- including Planning and Review:
#At the beginning of the week, list your goals for the week
#At the end of the week, assess:
##Did you meet your milestones?
##If not, why not, and how you can do better?

==Execution==

Make it really simple. Start a wiki page named Name_Log, such as [[Marcin Log]]. Add new posts on top of page. Every two weeks, roll up the entries into a 2 week history - so the Index doesn't get too lengthy. Repeat for every month, quarter, and year.

#Log tasks in an ongoing fashion.
#Week plan due Monday: what do you intend to do this week (in your own words)
#What did you in fact do this past week? What unplanned items?
#What is your own assessment of that / your progress?

#Share it with each other - over Monday dinner?
#Sharing it means, if you didn't do it, you at least have to think about it while being shared.
#You want to write things down, because then it'll be hard to think of things you did, and it'll look to the group like you didn't do anything.

=Explanation of Daily Log=

The purpose of the Daily Log is to facilitate organizational learning and performance management by promoting feedback, assessment, and transparency. The Daily Log is required for people at Factor e Farm.

A Log allows others to access quick links to review work - which is highly relevant when working on a distributed team where many people provide feedback. This assumes that links must be explicit - we do not assume that someone knows how to find a link online.

When people log their work - this work can be evaluated and assessed for efficiency, direction, and prioritization. Without a task log, it is not possible to evaluate and learn about what a person is doing.

Further, OSE is an organization that incubates other [[OSE Incubators]]. For organizational learning across these Incubators and other OSE Chapters, it is important to document what people are doing to clarify expectations/process/etc.

Further, the weekly Log serves as the basis for [[Monthly Planning and Review]]:
#What were the major milestones reached?
#What were the major milestones missed?
#What did you learn this month?
#What could you have done better?
#What are your milestones for next month?

See sample Daily Log - [[Marcin Blog]]

=Comments=
From [[Colby]]:
Have a process where people set their own goals and timeline and present them to the group and file them on a wiki.
Then meet weekly and have them add a status update with what they accomplished over the week (or even daily).

Each month, have them present to the group the summary of their accomplishments each week, lessons learned, how they are on schedule, what "unplanned items" came up that delayed the schedule.

Keep track over time, the number of weeks in which they hit their own goals and didn't. Offer each time they don't hit their goals that they can come for you for advice.

The same thing applies to under and over budget, etc.

Once a month or week, take part of a day and sit down with each person for 10-15 minutes to discuss what is going well and isn't... and look at their progress reports and schedule.

=Links=
*See list of logs - [[Logs]]

[[Category:Structuring]]
[[Category:Logs]]

Gregoryfoster Log

2017-04-19T00:04:11Z

Gregoryfoster: /* Thursday Apr 17, 2017 */ Adding FreeCAD work file.

=Thursday Apr 17, 2017=
Completed FreeCAD 101 Test ([[File:2017_04_18-freecad101.fcstd]]). Added [[FreeCAD_101#Self-Verifying_FreeCAD_Exam_Videos]] video.

File:2017 04 18-freecad101.fcstd

2017-04-19T00:01:31Z

Gregoryfoster: OSE FreeCad 101 test for Gregoryfoster

OSE FreeCad 101 test for Gregoryfoster

Logs

2017-04-18T23:58:43Z

Gregoryfoster: /* Work Logs */ Adding Gregoryfoster

'''See explainer video from 2013 on how to start a [[Work Log]]'''

=Project Logs=
==Organizational Development Logs==
*[[Development Process Log]]
:*[[Development Template Log]]
*[[Enterprise Log]]
*[[Team Building Log]]
*[[Organizational Log]]
*[[Admin Log]]
*[[Graphics Team Log]]
*[[Collaborative Literacy Log]]
*[[Publicity Log]]
*[[Viral Replicability Criteria Log]]
*[[HR Strategy Log]]
*[[Status Log]]
*[[Design Sprint Log]]

==Project Development Logs==
*[[D3D Log]]
*[[Biodigester Log]]
*[[Water Filter Log]]
*[[Greenlab Log]]
*[[Ultrasonic Sensor Log]]
*[[Nut Breeding Log]]
*[[3D Printer Log]]
*[[CEB Press Log]]
*[[Universal Rotor Log]]
*[[Polylactic acid log]]
*[[FreeCAD Log]]
*[[Agriculture Log]]
*[[Dogs Log]]
*[[Rabbitry Log]]
*[[Aquaponic Greenhouse Log]]
*[[Mushroom Log]]
*[[Pelletizer Log]]
==IT Logs==
*[[Wiki Log]]
*[[WordPress Log]]
*[[MediaWiki Log]]
*[[Wiki Templates Log]]
*[[Server Log]]

=Subproject Logs=
*[[Tobbens_Adding_Inductive_Proximity_Sensor_Log]]

=Work Logs=
*[[Jose Log]]
*[[Brian Log]]
*[[Hart Log]]
*[[Richard Log]]
*[[Cedric Log]]
*[[Polemidis Log]]
*[[Martijn log]]
*[[William Log]]
*[[Kyle Log]]
*[[Aaron Yarbrough Log]]
*[[Mark Log]]
*[[Lukas Log]] - NMR
*[[Lucas Log]] - tractor 2013
*[[Andrea Log]]
*[[AbeAnd Log]]
*[[Donney Log]]
*[[Michel Log]]
*[[Monica Log]]
*[[Cody Log]]
*[[2ben log]]
*[[Joshua Log]]
*[[Jonathan Log]]
*[[Alec Log]]
*[[Tobben Log]]
*[[Marcin Log]]
*[[Aidan Log]]
*[[Ellena log]]
*[[Edo Log]]
*[[Curtis Log]]
*[[Eric Log]]
*[[Jim Log]]
*[[Michael Hess Log]]
*[[Victor Log]]
*[[Arif Log]]
*[[Moriah Log]]
*[[Greg Log]]
*[[Gabriel Kind log‎]]
*[[Cris Log]]
*[[Graham Coffman's log]]
*[[Stephen_Log]]
*[[Emily Log]]
*[[Molly log]]
*[[Danny K Log]]
*[[Anthony_douglas_log]]
*[[Chrisc log]]
*[[Sam Kiyomi Log]]
*[[Juan log]]
*[[Jasonshah_log]]
*[[Jeff Log]]
*[[Brenna log]]
*[[Clair Rose log]]
*[[Catarina Log]]
*[[Michael Pendergast Log]]
*[[Guillaume Log]]
*[[Charlie log]]
*[[Will Log]]
*[[Jose Antonio log]]
*[[Max Log]]
*[[Yann Log]]
*[[Tom Log]]
*[[Rob Beddingfield Log]]
*[[Jean-Baptiste Log]]
*[[Andrea Log]]
*[[Jacob Log]]
*[[Colin_Log]]
*[[Lukas Log]]
*[[Aaron Log]]
*[[Roberto Log]]
*[[Gregoryfoster Log]]

=Spring breakers 2014=
*[[Chrisc log]]
*[[Colten Jackson Log]]
*[[Anthony douglas log]]
*[[Eric Potash Log]]
*[[Wes Log]]
*[[Laurynn log]]
*[[Catwilmes log]]
*[[Ben Lloyd Pearson Log]]
*[[Michael Seffren Log]]
*[[Andrew Graham Log]]
*[[Kyle log]]

=2013 Logs=
*[[Samthetechie Log]]
*[[Jordan Log]]
*[[Scott Log]]
*[[Lucas Log]]
*[[Leandra Log]]
*[[Cory Log]]
*[[Justin Burnett Log]]
*[[Chris Reinhart Log]]
*[[Gary Log]]
*[[Audrey Log]]
*[[Lisa Log]]
*[[Husam Log]]

==Other Logs==
*[[Rob_Beddingfield_Log]]
*[[Inverter Log]]
*[[Universal Rotor Log]]
*[[Accounting System Log]]

==Links==
*[[Old Logs]]
*[http://opensourceecology.org/wiki/Category:Logs Category:Logs]

[[Category:Logs]]

Gregoryfoster Log

2017-04-18T23:56:12Z

Gregoryfoster: Log (04.17.2017)

=Thursday Apr 17, 2017=
Added [[FreeCAD_101#Self-Verifying_FreeCAD_Exam_Videos]] video.

Daily Log of Tasks

2017-04-18T23:46:13Z

Gregoryfoster: /* Introduction */ typos

<span style="color:red">Last updated Dec 10, 2016 </span>

=Instructional Video on How to Write a Work Log=

<html><iframe src="http://popcorn.webmadecontent.org/12ii_" width="640" height="403" frameborder="0" mozallowfullscreen webkitallowfullscreen allowfullscreen></iframe></html>

=Introduction=
OSE promotes the use of a Log by all individuals and projects because the key to effective global collaboration is transparency and awareness of what any other individual or team is doing. A Log is a concise summary of tasks done with numerous hyperlinks to work product. It is intended to be used primarily for planning, review, and coordination. It is different than a regular Blog in that it focuses on access to work product as opposed to a narrative. Logs are intended to be quick notes, which take a few seconds of time and are therefore not a chore. They should not be as refined as Blog or some other piece of formal writing - the goal is to simply keep a record of ongoing activity with intent of maximizing collaboration. The simple theory behind a Log, and behind documentation in general - is that if it is not documented, it effectively does not exist - from the standpoint of potential collaboration over the internet. One should keep in mind that a log is a permanent record, and as such, if nobody reads it today or tomorrow, it does not mean that someone won't see it next year - if the content is relevant from a long-term perspective.

=Instructions Summary=
To start a work log, set up an account and log in to the Wiki - see [[Instructions]]. Then create a page titled Your_Name_Log - such as [[Marcin Log]]. Keep daily entries for every day Monday-Friday, and record entries with a date. The format for the dates should be placing the date in between = signs (this is a heading in Wiki language). The proper heading format is, for example, "Tue Apr 8, 2014". Then, record newer entries on top, so that one does not have to scroll down a page to see your latest work. When recording entries, you should have a link or picture embed to all that you have done.

=List of Logs=
*See [[Logs]] for project-based and person-based logs.

=Work Log Checklist=

'''Log your work for learning purposes - so you can learn to do it better the next time.''' This is a list of best practices for logging work for OSE:

#Did you link to your work product?
#When listing items that you have done, did you write down a complete list to avoid potential redundancy with other collaborators working in parallel?
#Is the entry specific, so others could help?
#Is the entry '''self-verifiable'''? That is, is there a link to work product or other evidence that the work has actually been done, or that you and not someone else did it?
#Are you keeping weekly planning goals on your log?
#Are you formatting your log with the latest entry on top, and date formatted as in [[Marcin Log]] as an example?
#Is continuity/progress visible in your log?
#Are you using the versioning capacity of the wiki to upload new files?

=Key Points=
*Update log daily or as relevant work is done. Presumption of non-logging in a given time period is that no work has been done.
*Add most recent update on top of page
*Link directly to new results every day so that result can be viewed in one click from your log
*Log items that have been logged previously, if updates have been made to those links
*If you are linking to an update on a page and only a small item has changed on that page, link to that specific item that has been changed - if possible.
*Keep log tight and short. Put all results on other pages, and link to those pages - so that a comprehensive picture of one's work is seen immediately. See [[Marcin Log]] as an example.
*At best, the Work Log should consist mostly of hyperlinks, with short description of what the hyperlink is.

==Design Rationale==
Log of progress should include who was contacted, resources found, links to work product generated, comments on what is working and not working, and any insights on the organizational process. See [[Marcin Log]] for an example. Tasks shall be logged as soon as they are completed. This is intended for:
*'''Organizational learning''' - to assess and review the duration of tasks, scope of tasks performed, what worked and what didn’t. Future team members can look at the log, learn from the tasks done, and assess the time that it takes to do certain tasks.
*'''Team coordination and project status'''- Work logs are universally identified within the team as a location for logging activity, and have a unique URL that any other team member can access, as in opensourceecology.org/wiki/Name_Log - with the name corresponding to the team member’s name. Any team member can view another person’s log. Since the log is done on a continuous basis as soon as tasks are comppleted, anyone can find out what has been done as soon as it has been done.
*'''Transparency'''. This allows other team members to see what is happening for purposes of transparency. Credit can thus be given properly to those who log tasks. If a task is not logged, others can not learn more about that task. Such trasnparency promotes autonomous operation within OSE.
*'''Self-Verifiability'''. Self-verifiability is an aspect of Transparency. Self-verifiability of the work log can be achieved by linking directly to work product - so that credit can be given for work done.
*'''Management scalability''' - Work logs provide universal indexing of a person’s work. Once there is a large number of people working on a project, an easy way to access a person’s work product is through the person’s log. The log is intended to be accessible with zero access barriers, an essential part of an open, collaborative organization. A log allows indexing of large amounts of disperse content from an unlimited number of people.
*'''Open culture''' - Work Logs are visible to the world, and thus promote working openly and collaboratively.

==Effective Communication==
To facilitate effective communication via the Daily Log, keep the following points in mind in order to help others learn rapidly from and assess your work.
*'''First and foremost - log your work in a concise paragraph instead of spreading it over a number of pages, and link to work product on other pages instead of embedding work product on the Work Log.''' This allows one to see daily work and weekly work product readily.
*Critical insights should be captured in the log. If a link is simply posted, one cannot tell what to expect from the link.
*The power of the wiki lies in using wikiwords - ie, a word or phrase in double brackets in edit mode allows you to link directly to any other page or subheading on the wiki. This way, you can build on former work without having to explain each time. Any wikiword becomes its own page on the wiki.
*Communicate as much as possible like you are commuinicating to the first-time reader in order to provide perspective. This means for concepts or formerly entered concepts or pages - link to those pages in your explanations as wiki words.
*Feel free to create pages that are simply definitions of words or phrases that you are using - so you can refer to that page any time in the future by putting the link in double brackets.
*Do not overwrite wikiwords that are already used if you are documenting a different usage of that wikiword, just start a page with a different wikiword. This is because any other pages that link to that page would then be pointing to the wrong definition.
*To inform the reader more fully, try to provide context as relevant. For example - if a link is a new entry in the wiki, write 'Started page so and so'.
*Always try to inform the reader about the context and perspective of your work. Useful work could be finding, sourcing prices, finding an online design calculator, reading, reviewing, starting wiki pages, editing a wiki page, continuing on work from another day, making video, taking pictures, writing an instructional, conference calling, getting something reviewed, picking up where someone else left off, etc... Please make a note of such activity and include a link to anything online, and for something that you generated (picture, document, video), upload it and link to it.
*If you want to upload an unsupported file format to the wiki which the wiki does not allow you to upload - compress it to a zip or other format and upload it then. The wiki supports uploads of compressed files such as .zip.
*If you are adding to an existing page, think of creating a subsection so that you can link to it directly as a wiki link. Otherwise, the only way for the reader to see what you have contributed is to look at the page history, which takes more time.
*If you are reporting a physical result, you should include a picture or video.
*If you are reporting a concept design, link to a google doc drawing or other diagram .
*If you are doing conceptual design - use google docs - so others can view and download the source. Set up sharind accordingly.
*If you are embedding google docs, paste a link to the actual document so others can access it directly to view, comment, or edit. This allows global collaboration to happen.
*When posting pictures or files - do not just put them on your log - but also on the related wiki page for that particular project.
*If you are uploading pictures as a zipped file - embed at least some of the pictures or thumbs themselves for viewing - for easy access - especially if the file is large and it takes a long time to download just to view the pictures.

==Guidelines==
To make the most use of the log as a cloud platform:
*Keep track of and coordinate with other core developers. Take any name - and you should be able to find their log: ex: [[Marcin Log]], [[Gabi Log]], [[Yoonseo Log]], [[Lenny Wayne Log]].
*There are also project based logs - [[Guatemala Log]], [[Power Cube Log]] - in addition to personal logs - for tracking projects which have multiple participants.
*Any documentation relevant to GVCS technical deployment - video, pictures, diagrams, reeviews, etc - should be copied to or linked to the wiki. For example, a picture of a build should be embedded in a wiki procedure, and if there is a relevant album of images, that link should be placed on the wiki.
*Google Docs should be embedded and an Edit link should be added for easy access.
*Iframes and other embeds should be taken advantage of - to make the Wiki a central repository of all project-related material.

==Standards==
*Document any work relevant to critical path as on the [[Critical Path]] for deploying the GVCS and building the world's first, post-scarcity, open source, global village.
*Weekly project meetings are logged at the [[D3D Log]] for the 3D printer.
*'''Use hyperlinks for work product.''' Do this by putting hyperwords in double brackets. See [[Wiki Instructions]].
*Make every day indexable by entering it as a heading, such as =Thu Oct 11, 2012=, such that any day can be accessed from an automatically-generated index on top of wiki page.
*Use Weekday, Month, Day, Year as standard headings, such as =Thu Oct 11, 2012=
*Roll up entries into a single link on a monthly basis, see bottom of [[Marcin Log]] for example.

=How To=

For a log to be effective it should provide on a daily basis:

#Tasks done
#Comments on important learnings
#Links to all work product that took more than 15 minutes to complete. All work should be documented on wiki
##This is easy for organizational work: start a wiki page with what you did with links
##For physical work, take pictures and vlogs, link to them as your work product
#Do this on a running basis to allow the log to serve as a monitor of progress that other team members can use to facilitate coordination on a sub-hour timescale

On a weekly basis - the Log should provide a Weekly Assessment- including Planning and Review:
#At the beginning of the week, list your goals for the week
#At the end of the week, assess:
##Did you meet your milestones?
##If not, why not, and how you can do better?

==Execution==

Make it really simple. Start a wiki page named Name_Log, such as [[Marcin Log]]. Add new posts on top of page. Every two weeks, roll up the entries into a 2 week history - so the Index doesn't get too lengthy. Repeat for every month, quarter, and year.

#Log tasks in an ongoing fashion.
#Week plan due Monday: what do you intend to do this week (in your own words)
#What did you in fact do this past week? What unplanned items?
#What is your own assessment of that / your progress?

#Share it with each other - over Monday dinner?
#Sharing it means, if you didn't do it, you at least have to think about it while being shared.
#You want to write things down, because then it'll be hard to think of things you did, and it'll look to the group like you didn't do anything.

=Explanation of Daily Log=

The purpose of the Daily Log is to facilitate organizational learning and performance management by promoting feedback, assessment, and transparency. The Daily Log is required for people at Factor e Farm.

A Log allows others to access quick links to review work - which is highly relevant when working on a distributed team where many people provide feedback. This assumes that links must be explicit - we do not assume that someone knows how to find a link online.

When people log their work - this work can be evaluated and assessed for efficiency, direction, and prioritization. Without a task log, it is not possible to evaluate and learn about what a person is doing.

Further, OSE is an organization that incubates other [[OSE Incubators]]. For organizational learning across these Incubators and other OSE Chapters, it is important to document what people are doing to clarify expectations/process/etc.

Further, the weekly Log serves as the basis for [[Monthly Planning and Review]]:
#What were the major milestones reached?
#What were the major milestones missed?
#What did you learn this month?
#What could you have done better?
#What are your milestones for next month?

See sample Daily Log - [[Marcin Blog]]

=Comments=
From [[Colby]]:
Have a process where people set their own goals and timeline and present them to the group and file them on a wiki.
Then meet weekly and have them add a status update with what they accomplished over the week (or even daily).

Each month, have them present to the group the summary of their accomplishments each week, lessons learned, how they are on schedule, what "unplanned items" came up that delayed the schedule.

Keep track over time, the number of weeks in which they hit their own goals and didn't. Offer each time they don't hit their goals that they can come for you for advice.

The same thing applies to under and over budget, etc.

Once a month or week, take part of a day and sit down with each person for 10-15 minutes to discuss what is going well and isn't... and look at their progress reports and schedule.

=Links=
*See list of logs - [[Logs]]

[[Category:Structuring]]
[[Category:Logs]]

FreeCAD 101

2017-04-18T23:41:46Z

Gregoryfoster: /* Self-Verifying FreeCAD Exam Videos */

=Meta=
Take-home points and learning outcomes of the 2 tutorials below:
*by learning to sketch in FreeCAD, you can then create any 3D objects imaginable
*Importing part libraries and working with them is a powerful way to do design work using Part Libraries. This can get the casual user to powerful design capacity using real geometries.

=Introduction=
After these 2 tutorials, you are ready to work on [[User Contributed Designs]]. Please pause the videos as needed in order to practice the demonstrated lesson, as these tutorials are dense.

=A FreeCAD Manual=
[https://www.gitbook.com/book/yorikvanhavre/a-freecad-manual/details The FreeCAD Manual] has a different learning approach than the [http://www.freecadweb.org/wiki official FreeCAD documentation wiki] that makes it more suitable for a first contact with FreeCAD.

=Tutorial 1=

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/RwcFg-anVHE" frameborder="0" allowfullscreen></iframe></html>

=Tutorial 2=

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/RLRppdFAtzY" frameborder="0" allowfullscreen></iframe></html>

=FreeCAD Test=
==Purpose==
This exercise tests your ability to:
*Install OSE Linux
*Download and use library parts in FreeCAD
*rotate, move, and align objects in 3D
*Use the Sketcher in FreeCAD to make features on faces
*Use circular assembly constraints in FreeCAD
*Use Vokoscreen to record instructional screen-casts
*Use KdenLive to edit a basic video, adding images and sound
*Upload videos to YouTube
*Upload FreeCAD source files to the wiki
*Embed videos in the wiki
*Using Disqus and upvoting comments

==Test==
#Download and install the [[OSE Linux]] with FreeCAD, Kdenlive, and Vokoscreen.
#Download 8-hole square tubing (without rounded corners) from the [[OSE Part Library]].
#Use the tubing to create an x-y-z bolted corner cube.
#Record a video of you building the cube, from the beginning, using [[Vokoscreen]].
#When you are done building the cube, create a 1" bolt and nut using the [[Bolt Library in FreeCAD]].
#Insert one bolt through any of the corners, as if you were actually building the cube - using the [[Assembly Workbench]] in FreeCAD.
#Tighten the bolt with the nut (just insert the nut onto the bolt).
#Now take any face on the tubing of the resulting cube - and using Sketcher on that particular face - write your initials on that face. Pocket those initials so that they are cut into the face.
#Speed up the file to turn it into a 30 second video using [[Kdenlive]].
#Add Pling by Jaspertine from the [[Open Source Soundtracks]]
#Upload the video to YouTube and embed in the section below - above the Disqus section.
#Upload the FreeCAD file to your [[Work Log]].
#Use Disqus below to tell us how long it took you to learn the FreeCAD tutorials and Kdenlive. Please include any suggestions on the videos. Also, please score yourself 0-100 based on the percentage of the Test points that you have completed successfully - and include that score in your Disqus comment.

At that point - Welcome to the Team, Ms/r. Opensourcer. You now have the basic skills to manipulate objects in 3D and to begin composing useful parts - including your ability to document your work with videos.

==Self-Verifying FreeCAD Exam Videos==
[https://youtu.be/1KNs4gqO1-c Polemidis] <br/>
Having completed this exercise, you will enable any reviewer to verify your skill set in 30 seconds by viewing a video with your signature (initials on the cube). Here are the results:

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/1KNs4gqO1-c" frameborder="0" allowfullscreen></iframe>

<br> Michael Beyer Jr : 3/29/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/RWXTXvui4aw" frameborder="0" allowfullscreen></iframe>

<br> Roberto Jaramillo : 3/30/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/vSZk13lWUVE" frameborder="0" allowfullscreen></iframe>

<br> Chas Murillo : 4/7/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/Cno--47Mufk" frameborder="0" allowfullscreen></iframe>

<br> Abe Anderson : 4/7/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/I6IQUbtD7Ac" frameborder="0" allowfullscreen></iframe>

<br> Frank McCormick : 4/11/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/VMBiWsABotM" frameborder="0" allowfullscreen></iframe>

<br/>
Gregory Foster (04.18.2017)<br/>
<iframe width="560" height="315" src="https://www.youtube.com/embed/KVqbdWqx5Yc" frameborder="0" allowfullscreen></iframe>
</html>

=Please Comment on Your FreeCAD 101 Test Experience=

How long did it take you? Were you able to do it? What could have helped you to learn the skills more effectively? Please upvote most useful responses here.

<hr><hr><br>Brian Hull completed OSE FreeCAD test 2/16/2017

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/nAZBConV2AY" frameborder="0" allowfullscreen></iframe></html>

Test took me 30 minutes to complete. A lot of that time was spent clicking around and learning how the software worked. Overall, FreeCAD worked fine and only had a few glitches for me. I would say pretty good for a free software. This was my first time working with the assembly workbench. There was a few places where I thought the software could be improved but I'll wait until I use it more before I complain too much. I would rate myself a 75 out 100.

<hr><hr><br>Jonathan Kocurek - Completed OSE FreeCAD Test 02/28/17

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/5XDIK7Nc5ak" frameborder="0" allowfullscreen></iframe></html>

The FreeCAD took me awhile due to software and also a new interface, features, and multiple unknowns. It took me about 6+hrs figuring out certain issues with sketching my initials on to the metal. Definitely will have to study up on all of the different components of the software.

<hr><hr><br>Jean-Baptiste Vervaeck - Completed OSE FreeCAD Test 06/03/2017

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/YUpx8uizeUk" frameborder="0" allowfullscreen></iframe></html>

After 12+ hours of practicing in FreeCAD, downloads & installations, watching tutorials and reading through freeCAD documentation, I was able to work through steps 3 through 8 in 37 minutes. I was running FreeCAD in ubuntu 16.04 running inside VirtualBox 5.1.14 on a Win7 PC which slowed down the process considerably. It took me quite a while just to find the "just right" configuration in order for kdenlive to properly render the edited video (it was only when my CPU usage maxed out that there were interruptions in the quality of the rendered video). 80/100 -- 10 point deduction for not tightening the nut/washer on the bolt and another 10 point deduction for not adding in the inner parts on the letter "B" in my initials pocket. Also, I started out working with the wrong parts file, not having been able to find the 8 hole tube with square corner file on the wiki till it was pointed out to me.

<hr><hr><br>Michael Beyer Jr : 2017-03-29 : 15 hours

probably more like a total of 45 hours as i am still actively learning linux after making it my main operating system a few months ago, so time spent learning freecad was interspersed through also learning linux at the same time. i believe i completed all tasks in a satisfactory manner. i can't grade myself exactly but i know i would like to just generally keep improving learning all functions of creating and manipulating 3d objects as well as improving creating objects with the most efficient constraint set as possible, and to become quicker at all these processes.

ways to improve my learning will be continued practice, continued vigilant documentation.. having better documentation would have made it easier for me to learn more quickly and effectively, so i seek to add to the documentation. this way, others will have an easier time getting up to speed with the current developments, as the ultimate goal is to decrease barriers to entry and increase motivation to contribute to the project.

<hr><hr><br>Chas Murillo : 08 April 2017 : 15+ hours

I had some trouble with FreeCAD 0.15 freezing while doing part design so I upgraded to 0.16 on my own ubuntu 16.04 OS. I struggled with manipulating the objects and what sides to click on when moving or revolving an object but eventually figured it out after watching some of the tutorials. I also struggled with writing my initials on the edge of the xyzCube. I figured out that by clicking the face part in sketcher view then clicking "create new sketch" the reference sketch would align with the part. My order of operations for creating the pocket was off and I just had to play around with it for a while and watch some tutorials.

With Vokoscreen I had trouble with it not saving my recordings after I stopped or paused the recording multiple times while taking breaks. All in all I give myself a 90/100 cuz I think I could've done a nicer job and I didn't follow directions by upgrading to the newer FreeCAD to finish my part.

<hr><hr><br>[[User:LaszloLG]] 09 April 2017
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/DXQJBtO69II" frameborder="0" allowfullscreen></iframe></html>
<hr><hr><br>
<html>
<p>Frank McCormick: April 10 2017: 4 hours</p>
<p> I would say for me i spent a couple of hours just messing around in freecad to get a feel for it. Once I spent a couple of hours in the program I was able to get the hang of it and was able to complete the build fairly quickly(20minutes or so). The longer portion was learning Vdenlive and getting the video rendered. I also had a couple of issues with my files saving. So there was a little rework for me when I lost some files. Overall I would give myself an 85/100. I struggled at first with the bolt and getting it placed and also had a little trouble with Kdenlive at first. I think my initial use of Kdenlive was sloppy and poorly edited. I definitely think I could improve my use there.</p>

<html><div id="disqus_thread"></div>
<script>
/**
* RECOMMENDED CONFIGURATION VARIABLES: EDIT AND UNCOMMENT THE SECTION BELOW TO INSERT DYNAMIC VALUES FROM YOUR PLATFORM OR CMS.
* LEARN WHY DEFINING THESE VARIABLES IS IMPORTANT: https://disqus.com/admin/universalcode/#configuration-variables
*/
/*
var disqus_config = function () {
this.page.url = PAGE_URL; // Replace PAGE_URL with your page's canonical URL variable
this.page.identifier = PAGE_IDENTIFIER; // Replace PAGE_IDENTIFIER with your page's unique identifier variable
};
*/
(function() { // DON'T EDIT BELOW THIS LINE
var d = document, s = d.createElement('script');

s.src = '//osefreecadinstructionals.disqus.com/embed.js';

s.setAttribute('data-timestamp', +new Date());
(d.head || d.body).appendChild(s);
})();
</script>-
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript" rel="nofollow">comments powered by Disqus.</a></noscript></html>

=Links=
*[[FreeCAD Architecture Tutorial]]

[[Category:FreeCAD]]
[[Category:101 101s]]

FreeCAD 101

2017-04-18T23:35:40Z

Gregoryfoster: /* Self-Verifying FreeCAD Exam Videos */ Adding video for Gregory Foster

=Meta=
Take-home points and learning outcomes of the 2 tutorials below:
*by learning to sketch in FreeCAD, you can then create any 3D objects imaginable
*Importing part libraries and working with them is a powerful way to do design work using Part Libraries. This can get the casual user to powerful design capacity using real geometries.

=Introduction=
After these 2 tutorials, you are ready to work on [[User Contributed Designs]]. Please pause the videos as needed in order to practice the demonstrated lesson, as these tutorials are dense.

=A FreeCAD Manual=
[https://www.gitbook.com/book/yorikvanhavre/a-freecad-manual/details The FreeCAD Manual] has a different learning approach than the [http://www.freecadweb.org/wiki official FreeCAD documentation wiki] that makes it more suitable for a first contact with FreeCAD.

=Tutorial 1=

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/RwcFg-anVHE" frameborder="0" allowfullscreen></iframe></html>

=Tutorial 2=

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/RLRppdFAtzY" frameborder="0" allowfullscreen></iframe></html>

=FreeCAD Test=
==Purpose==
This exercise tests your ability to:
*Install OSE Linux
*Download and use library parts in FreeCAD
*rotate, move, and align objects in 3D
*Use the Sketcher in FreeCAD to make features on faces
*Use circular assembly constraints in FreeCAD
*Use Vokoscreen to record instructional screen-casts
*Use KdenLive to edit a basic video, adding images and sound
*Upload videos to YouTube
*Upload FreeCAD source files to the wiki
*Embed videos in the wiki
*Using Disqus and upvoting comments

==Test==
#Download and install the [[OSE Linux]] with FreeCAD, Kdenlive, and Vokoscreen.
#Download 8-hole square tubing (without rounded corners) from the [[OSE Part Library]].
#Use the tubing to create an x-y-z bolted corner cube.
#Record a video of you building the cube, from the beginning, using [[Vokoscreen]].
#When you are done building the cube, create a 1" bolt and nut using the [[Bolt Library in FreeCAD]].
#Insert one bolt through any of the corners, as if you were actually building the cube - using the [[Assembly Workbench]] in FreeCAD.
#Tighten the bolt with the nut (just insert the nut onto the bolt).
#Now take any face on the tubing of the resulting cube - and using Sketcher on that particular face - write your initials on that face. Pocket those initials so that they are cut into the face.
#Speed up the file to turn it into a 30 second video using [[Kdenlive]].
#Add Pling by Jaspertine from the [[Open Source Soundtracks]]
#Upload the video to YouTube and embed in the section below - above the Disqus section.
#Upload the FreeCAD file to your [[Work Log]].
#Use Disqus below to tell us how long it took you to learn the FreeCAD tutorials and Kdenlive. Please include any suggestions on the videos. Also, please score yourself 0-100 based on the percentage of the Test points that you have completed successfully - and include that score in your Disqus comment.

At that point - Welcome to the Team, Ms/r. Opensourcer. You now have the basic skills to manipulate objects in 3D and to begin composing useful parts - including your ability to document your work with videos.

==Self-Verifying FreeCAD Exam Videos==
[https://youtu.be/1KNs4gqO1-c Polemidis] <br/>
Having completed this exercise, you will enable any reviewer to verify your skill set in 30 seconds by viewing a video with your signature (initials on the cube). Here are the results:

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/1KNs4gqO1-c" frameborder="0" allowfullscreen></iframe>

<br> Michael Beyer Jr : 3/29/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/RWXTXvui4aw" frameborder="0" allowfullscreen></iframe>

<br> Roberto Jaramillo : 3/30/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/vSZk13lWUVE" frameborder="0" allowfullscreen></iframe>

<br> Chas Murillo : 4/7/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/Cno--47Mufk" frameborder="0" allowfullscreen></iframe>

<br> Abe Anderson : 4/7/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/I6IQUbtD7Ac" frameborder="0" allowfullscreen></iframe>

<br> Frank McCormick : 4/11/2017 <br>

<iframe width="560" height="315" src="https://www.youtube.com/embed/VMBiWsABotM" frameborder="0" allowfullscreen></iframe>

<br/>
[[User:Gregoryfoster|Gregory Foster]] (04.18.2017)
<iframe width="560" height="315" src="https://www.youtube.com/embed/KVqbdWqx5Yc" frameborder="0" allowfullscreen></iframe>
</html>

=Please Comment on Your FreeCAD 101 Test Experience=

How long did it take you? Were you able to do it? What could have helped you to learn the skills more effectively? Please upvote most useful responses here.

<hr><hr><br>Brian Hull completed OSE FreeCAD test 2/16/2017

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/nAZBConV2AY" frameborder="0" allowfullscreen></iframe></html>

Test took me 30 minutes to complete. A lot of that time was spent clicking around and learning how the software worked. Overall, FreeCAD worked fine and only had a few glitches for me. I would say pretty good for a free software. This was my first time working with the assembly workbench. There was a few places where I thought the software could be improved but I'll wait until I use it more before I complain too much. I would rate myself a 75 out 100.

<hr><hr><br>Jonathan Kocurek - Completed OSE FreeCAD Test 02/28/17

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/5XDIK7Nc5ak" frameborder="0" allowfullscreen></iframe></html>

The FreeCAD took me awhile due to software and also a new interface, features, and multiple unknowns. It took me about 6+hrs figuring out certain issues with sketching my initials on to the metal. Definitely will have to study up on all of the different components of the software.

<hr><hr><br>Jean-Baptiste Vervaeck - Completed OSE FreeCAD Test 06/03/2017

<html><iframe width="560" height="315" src="https://www.youtube.com/embed/YUpx8uizeUk" frameborder="0" allowfullscreen></iframe></html>

After 12+ hours of practicing in FreeCAD, downloads & installations, watching tutorials and reading through freeCAD documentation, I was able to work through steps 3 through 8 in 37 minutes. I was running FreeCAD in ubuntu 16.04 running inside VirtualBox 5.1.14 on a Win7 PC which slowed down the process considerably. It took me quite a while just to find the "just right" configuration in order for kdenlive to properly render the edited video (it was only when my CPU usage maxed out that there were interruptions in the quality of the rendered video). 80/100 -- 10 point deduction for not tightening the nut/washer on the bolt and another 10 point deduction for not adding in the inner parts on the letter "B" in my initials pocket. Also, I started out working with the wrong parts file, not having been able to find the 8 hole tube with square corner file on the wiki till it was pointed out to me.

<hr><hr><br>Michael Beyer Jr : 2017-03-29 : 15 hours

probably more like a total of 45 hours as i am still actively learning linux after making it my main operating system a few months ago, so time spent learning freecad was interspersed through also learning linux at the same time. i believe i completed all tasks in a satisfactory manner. i can't grade myself exactly but i know i would like to just generally keep improving learning all functions of creating and manipulating 3d objects as well as improving creating objects with the most efficient constraint set as possible, and to become quicker at all these processes.

ways to improve my learning will be continued practice, continued vigilant documentation.. having better documentation would have made it easier for me to learn more quickly and effectively, so i seek to add to the documentation. this way, others will have an easier time getting up to speed with the current developments, as the ultimate goal is to decrease barriers to entry and increase motivation to contribute to the project.

<hr><hr><br>Chas Murillo : 08 April 2017 : 15+ hours

I had some trouble with FreeCAD 0.15 freezing while doing part design so I upgraded to 0.16 on my own ubuntu 16.04 OS. I struggled with manipulating the objects and what sides to click on when moving or revolving an object but eventually figured it out after watching some of the tutorials. I also struggled with writing my initials on the edge of the xyzCube. I figured out that by clicking the face part in sketcher view then clicking "create new sketch" the reference sketch would align with the part. My order of operations for creating the pocket was off and I just had to play around with it for a while and watch some tutorials.

With Vokoscreen I had trouble with it not saving my recordings after I stopped or paused the recording multiple times while taking breaks. All in all I give myself a 90/100 cuz I think I could've done a nicer job and I didn't follow directions by upgrading to the newer FreeCAD to finish my part.

<hr><hr><br>[[User:LaszloLG]] 09 April 2017
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/DXQJBtO69II" frameborder="0" allowfullscreen></iframe></html>
<hr><hr><br>
<html>
<p>Frank McCormick: April 10 2017: 4 hours</p>
<p> I would say for me i spent a couple of hours just messing around in freecad to get a feel for it. Once I spent a couple of hours in the program I was able to get the hang of it and was able to complete the build fairly quickly(20minutes or so). The longer portion was learning Vdenlive and getting the video rendered. I also had a couple of issues with my files saving. So there was a little rework for me when I lost some files. Overall I would give myself an 85/100. I struggled at first with the bolt and getting it placed and also had a little trouble with Kdenlive at first. I think my initial use of Kdenlive was sloppy and poorly edited. I definitely think I could improve my use there.</p>

<html><div id="disqus_thread"></div>
<script>
/**
* RECOMMENDED CONFIGURATION VARIABLES: EDIT AND UNCOMMENT THE SECTION BELOW TO INSERT DYNAMIC VALUES FROM YOUR PLATFORM OR CMS.
* LEARN WHY DEFINING THESE VARIABLES IS IMPORTANT: https://disqus.com/admin/universalcode/#configuration-variables
*/
/*
var disqus_config = function () {
this.page.url = PAGE_URL; // Replace PAGE_URL with your page's canonical URL variable
this.page.identifier = PAGE_IDENTIFIER; // Replace PAGE_IDENTIFIER with your page's unique identifier variable
};
*/
(function() { // DON'T EDIT BELOW THIS LINE
var d = document, s = d.createElement('script');

s.src = '//osefreecadinstructionals.disqus.com/embed.js';

s.setAttribute('data-timestamp', +new Date());
(d.head || d.body).appendChild(s);
})();
</script>-
<noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript" rel="nofollow">comments powered by Disqus.</a></noscript></html>

=Links=
*[[FreeCAD Architecture Tutorial]]

[[Category:FreeCAD]]
[[Category:101 101s]]