Open Source Ecology - User contributions [en]

Pivotal Task Tracker

2011-06-21T22:56:04Z

Vann:

* User story - a request; who is requesting something and why
* story - a deliverable; specific request
* Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.

== Abstract ==

Right now with GVCS Development we have the wonderful pickle of having many assistance offers, but many of them are not aligned with our core mission. This ends up wasting organizational time on part of the core GVCS development team. To address this, we are pursuing a task tracking system which by design - or automatically - puts people on the right track.

Properties of Tracker:

* Low entry barrier to participation
* Infinite spawnability of new projects
* By invite only

== Metalevel Description of Pivotal Functionality ==

* Someone creates a project
* 5-10 people per project - or too many people trying to work together; at best, small team, collocated, with high level of trust
* Task list is created (Icebox). These are the user stories or requests as defined above.
* Someone takes on task, rates its difficulty on a relative scale, and then it can be started.
* Reasons for using a Tracker:
** Provides transparency:
*** Tasks to be done
*** If anyone is doing a task
*** What the status is (not taken, in development, delivered, or complete
** Prioritizing all tasks (in backlog and initial task list)
** Estimation of time to completion (probably not so useful due to a large number of unknown, critical parameters)
** Allows stakeholder to make requests and rank them in importance, and allows team members to offer a deliverable on their own schedule; allows team team members' difficulty ratings to influence prioritization by stakeholder

To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.

== Populating the Tracker with Tasks ==

* Start with 32 steps of [[GVCS Development Template]]
* Break down the 32 steps into substeps. This is the master index.
* Import into pivotal tracker
* Generate [[Systems Engineering Breakdown Map]]
* Use google map or cMap tools as a breakdown tool and indexical environment for each project.

== Useful Tips ==

'''Use Labels'''

Create labels that represent sub-tasks. Say for example that your machine has three parts: base, box, and button. Naturally, each of these will need engineering drawings. Create the story with the name of the drawing and give it a label of "drawing". The titles of the stories will then appear as:

* ''drawing'' base
* ''drawing'' box
* ''drawing'' button

== Motivation ==

Pivotal is a hosted, agile, free for public use, project management tool that just "gets out of your way." Unlike some heavier weight tools (say, BaseCamp) that include chat rooms, forums, and so forth, we decided to adopt a modular approach, one that both encourages an agile work flow, and who modularity mirrors OSE's hardware development efforts.

Pivotal is based around the concept of tracking "user stories." User stories are high level requests by a stakeholder, written in plain English, that state who needs what, and why. A user story might be "OSE needs a way for team leaders to sort through all these people offering to help us so we can get the GVCS built ASAP! "

After stakeholders create some user stories, team members can take ownership of the stories, and rate their difficulty on a relative scale. Stakeholders can prioritize user stories accordingly based on their difficulties. Pivotal takes care of estimating a team's capacity by observing how many tasks (of what difficulty) are performed per week, and automatically breaks the tasks into iterations and creates burn down charts, thereby giving project leaders an easy way to estimate how long a given project will take.

Members can optionally break down user stories into finer grained user stories, or they can attach actionable tasks to it. There's also provisions to comment on them, attach files, and move user stories through a cycle of "Not Yet Scheduled, Started, Finished, Delivered, Accepted or Rejected, and Finished." Pivotal takes care of putting the user stories in the right place, and notifying the invested parties: the task requester (often the stakeholder), or the task owner (usually a team member), or everyone on the team (if the team member likes). It's simple, but great at what it does.

[[Category: Organization]]
[[Category: IT Infrastructure]]

Vann Miller

2011-06-09T20:06:57Z

Vann:

=Team Culturing Information=

last updated: 24. May, 2011

==='''WHO''' are you?===
*''Name'' - Vann Miller

*''Location (city, country)'' - New Orleans, LA & San Francisco, CA

*''Contact Information (email, phone, Skype)'' -
vann (dot) miller (at) gmail (dot) com<br/>
vannmiller (skype)

*''Introductory Video'' -

*''Resume/CV'' - http://www.linkedin.com/in/vannm

==='''WHY''' are you motivated to support/develop this work?===
*''Do you endorse open source culture?''
Yes

*''Why are you interested in collaborating with us?''
transportation costs are rising, economies are crashing, and our ecosystems are collapsing: all reasons to produce locally.

*''How do you think that the GVCS can address pressing world issues?''
by empowering people to produce the tools they need to use local natural resources to maintain a modern and sustainable standard of living

*''What should happen so that you become more involved with the project?''
i'm already on the factorefarm; it's happened!

*''What are you missing in the project?''
not sure i understand this question. i have a lot to learn about the various GCVS tools.

*''What are your suggestions for improvement of the project?''
i'm working with marcin on researching appropriate project and contact mgmt web tools for helping to manage development of the GCVS.

==='''WHAT'''===
*''List all of your skills in these areas: Communications - Organizational - Computer Support - Finances - Design - Natural Building - Electronics - Automation - Metallurgy - Engineering - Fabrication - Agriculture - Energy - Architecture - Video/Graphics/Art - PR/Marketing - Education - Construction - Industry - CNC - Chemistry - Product Design - Other''
graduated berkeley in applied math/comp sci, 20+ years in software development, some experience building circuits, robots, and metal shop eperience.

*''How have you already contributed to the project?''
been helping build tractors in the factorefarm workshop the last few days. been a true fan since july 2010.

==='''HOW''' can you help?''===
*''How are you interested in contributing to the work of GVCS development?''
more of the same; web development and shop work.

*''Can you volunteer to work with us, and if so, how many hours per week?''
doing it full time now. part time once offsite. say 10-15 hours.

*''Are you interested in working with us for pay? If so, what services can you offer, and what is your hourly or per-project rate?''
i could do software development for pay. let's see how this goes.

*''Are you interested in [http://openfarmtech.org/wiki/Dedicated_Project_Visit Dedicated Project Visit]?''
i'm on one.

*''Are you interested in purchasing equipment from us to help bootstrap development?''
perhaps!

*''Are you interested in bidding for consulting/design/prototyping work?''
perhaps!

*''Are you a [http://openfarmtech.org/wiki/True_Fans True Fan]? If not, why not?''
yes!

*''Would you like to see yourself working with us on a full-time basis?''
i am right now.

*''Are you interested in using the technologies that we are developing directly?''
yes.

*''Are you interested in being part of the world's first, open source, resilient community? The GVCS is the preparatory step for the OSE Village Experiment - a 2 year, immersion experiment (2013-2014) for testing whether a real, thriving, modern-day prototype community of 200 people can be built on 200 acres using local resources and open access to information? We are looking for approximately 200 people to fill a diverse array of roles, according to the Social Contract that is being developed. This may be the boldest social experiment on earth - a pioneering community whose goal is to extend the index of possibilities regarding harmonious existence of humans, ecology, and technology - as a beacon of light to benefit of all people on Earth.
i may well be. i'm getting a taste of the community at population 3 right now.

[[Category:Team Culturing]] [[Category: IT team]]

Forum Policy

2011-06-06T19:10:13Z

Vann: /* Proposed Category Structure */

=Introduction=

The forum is a platform where both general discussion and technical development can occur. The general discussion is moderated, and includes both Introductions and General Discussion on all topics - questions about the projects.

To increase the quality of discussion - we recommend that participants:

*Read the [[Crash Course]] and [[FAQs]]
*Technical contributors (both organizational and technological) read [[OSE Specifications]]
*Technical discussion is the next level of forum discussion. For Technical Discussion, people are required to fill in the [[Team Culturing]] prior to starting their contributions.
*Read the Forum Discussion Standards below.

=Moving Forward=

Issues to address:
*Who is general moderator team?
**Elifarley - admin, permissions, logins
*Clarity on zero spam tolerance in technical development, no personal attacks, adhering to absolute creative approach
** Create roles limiting access:
*** General - General forum only.
*** Contributor - Technical and Organizational Forums
*** Staff - Access to staff forums
*** Moderators - Special permissions forums moderated
*** Admin - God like powers.

=Content=

Desirable Forums list (before continuing, let's get consensus on this):

*'''General Discussion'''. Includes General Discussion, Introductions, [[Open Source Fab Lab]] (Industry 2.0 concept of global design and local production, with technical development below under CAD, CNC & Robotics, Flexible Fabrication), and [[Open Source Agroecology]]. Product sales, fabrication, and many other discussions could be handled here. This should be a place that we could direct many new people. All discussion should be covered in these topics. People can graduate/filter from these discussions into Technical Discussion. All other discussions beyond General Discussion require [[Team Culturing]] to be filled out as a prerequisite, and are by invitation or request only.
**Moderator?
*'''Web Development and Support''' - all discussion on internet infrastructure, including strategy, process, policy, and structure. Wiki, cms, CiviCRM, blog, opensourceecology.org, forums, repository, fundraising tools, development needs, secuirty, backup, mirrors, traffic.
**Who will moderate?
**'''Wiki Policy''' subsection
**'''Forum Policy''' - discussion of how this policy should be maintained and upgraded
**'''Linux Support''' - support on OSE infrastructure in Linux - from installations, compatibility, software choices (such as what is the best Video editing software), Linux connection to iPhone, etc.
*'''Organizational Development'''- all organizational topics for bringing about an infrastructure to support [[50/2/2]], but mainly, the organizational form, legal, financial infrastructure. Includes strategy, structure, and process development.
*'''Communications/Translations/Media Development/PR
*'''Production and Marketing'''-Topics surrounding product sales, production facilities, and marketing.
*'''Resource Development''' - includes crowd funding, crowd microfunding, nonprofit sector (grants, donor relations), and awards/distinction applications. Ties in to Media Development.
*'''Project Management'''-developing the process and infrastructure for parallel, open source product development
*'''Team Development'''- advisory team development, developer recruiting, viral marketing development, collaboration incubation. ''Collaboration Incubation'' - one distinguishing feature of this work is its identity as an open source project - capable of open collaboration and absorption of new participants into the project. This discussion centers around incubating relationships with allies and supporters on all levels, from technical to organizational. We want to position OSE as a growth organization - one that is capable of absorbing unlimited growth in its collaborator pool, while remaining manageable and flat in its organizational structure.
*'''True Fans'''- We should have a dedicated Forum for True Fans, where collaboration and further recruitment of True Fans can be discussed.
*'''Education'''- Topics related to OSE 2 Year Immersion Training, Whole Village education, Gaia University collaboration, and K-PhD Renaissance Education towards Freedom, as well as Augmented Reality training for fabricators.
*'''CEB Press'''- particular discussion, focused on completing the 31 steps of the [[GVCS Development Template]]
*'''Construction''' - includes tractor, CEB press, pulverizer, Sawmill, Cement Mixer, Trencher, Backhoe, Bulldozer, and eventually, rebar (Rod and Wire Mill), sheet metal and structural metal (Metal Rolling). May discuss [[Modular CEB Construction]], [[Mobile Microhouse]]s, [[Superinsulated CEB Construction]] (thick cavity walls with hammermilled biomass), closed loop wastewater systems including biofilters and [[Living Machines]], etc.
**Who will moderate?
*'''Open Source Tractor/Microtractor/Bulldozer''' - discussion on LifeTrac, MicroTrac, bulldozer, and all implements
**Who will moderate?
*'''Open Source Car''' - microcar and truck included
**Who will moderate?
[[appropedia: Category: Transport]])
*'''FLexible Fabrication''' - Ironworker machine, Mill/Drill/Lathe, Surface Grinder, Cold Cut Saw, Oxyhydrogen Torch, Welder, Plasma Cutter, Metal Bandsaw, Abrasive Saw
*'''CNC and Robotics'''- Industrial Robot, RepRap, CNC Mill/Drill/Lathe, Circuit Mill, Torch Table/Router Table, Laser Cutter
*'''CAD, CAM, and Prototyping''' - If we have all the designs in CAD, then we can produce fabrication drawings, CAM files, and engage in parallel prototyping.
*'''Social Contract and Land Stewardship'''- how property is owned and maintained, and how productivity is assured for prosperity and resilience, while regenerating the environment and contributing to the welfare of surrounding communities
*'''Field Agriculture'''- including Seeder, Haying, Baling, Microcombine
*'''Hot Metal Processing''' - includes Induction Furnace, Metal Rolling, Wire and Rod Mill, Casting, Press Forge, and alloying
*'''Solar Concentrator Electric System''' - this is a solar thermal system for producing electricity. This is a step beyond heating applications, and is the most difficult project within the [[GVCS]]. The goal is a home-scale (5 kW) solar electric system at approximately $1/watt cost, and at least 20 year lifetime. It requires addressing of hail, wind, and mirror-cleaning issues.
**Who will moderate?
*'''Modern Steam Engine'''- includes Pelletizer, Gasifier Burner, Steam Generator, Steam Engine, and Electric Generator with charge control. Also includes fuel crops, appication of Haying/forestry equipment, combined heat and power systems, greenhouse drying systems.
*'''50 kW Wind Turbine'''
**Who will moderate?
*'''Water''' - Well Drilling Rig, closed-loop water systems, Living Machines, biofilters, redworms, closed-loop flush toilets, rain catchment, berming, ponds, irrigation, condensation
**Who will moderate?
*'''Agriculture - Open Source Agroecology''' - includes agriculture discussions and the creation of comprehensive gene banks (http://openfarmtech.org/wiki/Community_Gene_Bank). The goal of our agriculture discussion is focused on open source agroecology - combination of best organic practices, with access to mechanical and processing tools, with access to gene banks for replicating perennial-based food systems. We want to cultivate cutting-edge discussion on replicable, complete, year-round, local food systems. Our point of differentiation is that we are interested in creating the world's first complete and replicable farm - a farm that produces the entire diet for a community. There is no precedent for this in the developed world, but we want to show an example that it is possible to do a complete operation in one place. There is a number of people engaged in organic, local food systems - all of which are doing great work - but to date, i have not seen an example of a replicable, single farm that produces a complete, year-round diet. The second point of differentiation is that we want to make such an operation affordable to the common man, not just to eco-elites, as is common for most of the organic farming movement.
**Who will moderate?
*'''Power Electronics''' - includes all power electronics devices from the GVCS, plus nickel-iron batteries (for welders, tractors, off-grid power). Inverters, power supplies for welder, laser, plasma cutter, battery charger, charge controller (wind turbine)
**Who will moderate?
*'''Bioplastics'''-bioplastic extruder and synthesis of greenhouse plastic from plants
*'''Extraction of Aluminum from Clay''' - this is the most exotic one showing the possibility of advanced civilization creation on the scale of a 6000 square foot facility.

==Proposed Category Structure==

The following category structure is proposed to simplify organization and define access:

* General
** A single, general category with no sub-categories; one forum each for English, Spanish, French, Russian, and Portuguese. (writable by all)
** Announcements (read only, press releases, etc.)
* Technical (writable by contributors, readable by all)
** GVCS Projects (50, top 20 for now)
** Component Projects (5 or so now, much more later)
** Community Projects (villages, communities, local OSE chapters, etc)
** Agriculture Projects (farming, permaculture, etc.)
** Other Projects
* Organization (writable by contributors, readable by all)
** Resource Development
** Web Infrastructure
** Project Management
** Standards (Docs, CAD, CAM, etc.)
** Fundraising
* Staff (private to OSE staff)
** Grant Management
** Press
** Marketing
** Personnel

=Forum Moderator Duties=

Forum moderators should have subject-matter expertise, practical experience, and at the very least, serious interest in, their respective topic of moderation. Moderators are to serve indefinitely, unless otherwise agreed upon, but other moderators may be added to a particular forum in case of increased traffic or other circumstances. Moderators should have sufficient time to read through postings, to make sure that they adhere to [[OSE Specifications]] and general goals of OSE as specified in the [[Crash Course]]. Moderators should seek assistance if the volume of communication exceeds their ability to handle the discussion. Moderators should contact [[Elifarley Cruz]] with any issues.

Moderators should become with the roles of [[Project Managers]] and other members of the [[Development Team]] - both in technical and organizational development, to make sure that any discussion leading to substantial development on the project is handled accordingly or forwarded to responsible parties for further action. Moderators should be familiar with the membership of the [[Development Team]], so that moderators can take initiative in linking contributors to further resources and team members.

Moderators should also start, contribute to, or maintain, an FAQ on their Forum, to help inform and orient contributors.

Moderators should also provide a digest of their forum activity, after, say, 100 messages transpire. A digest would serve the purpose of regrouping and reorganizing discussion to facilitate progress, to point out worthwhile highlights, and to propose new initiatives. This digest can be a post on the forum, and it may be worthwhile to start a wiki page. If substantial activity warrants it, Moderators are invited to blog on the Factor e Farm blog to share their highlights.

Moderators are expected to facilitate keeping discussion on track, and making sure that spam, [[wikipedia:Wikipedia:No_personal_attacks|personal attacks]], and any non-constructive behavior does not take over discussions. There may be a fine line in certain cases, so the Moderator should become keen in focusing discussion towards practical results, rather than philosophical discussion or armchair critique.

What else should moderators do?

=Forum Use=
* Notifications per Email
** If you want to receive notifications per email go to your [http://openfarmtech.org/forum/profile/notifications Profile Notifications] and on the right side there are two options: "My Preferences" and "E-mail Subscriptions". Check them out.

=Forum Discussion Standards=
==Intention==
The purpose of the OSE Forums is to promote the [[Current Scope]] of the project. The general culture of the forums is:

*Adherence to [[Core Values of OSE]]
*An 'absolute creative approach' with respect to finding creative solutions as opposed to dwelling on negatives. Read this [[Essay on Creative Problem-Solving]] for an in-depth discussion on this important topic.
*We have a zero tolerance policy for spam, [[wikipedia:Wikipedia:No_personal_attacks|personal attacks]], trolling, or other disrespectful behavior. Therefore, we will moderate such behavior actively, and eggregious behavior will result in immediate ban from the forum. Violators will have an option to make amends.

[[Category:Standards]]

Vann Miller

2011-06-04T01:28:08Z

Vann: /* WHO are you? */