Subpage for VemsExecutives
- executive Jason Russell is the ofbiz executive
- vice executive Marcell Gal - will happily hand it over to self-nominees
Tasks
- keep a reasonably tested ofbiz version that suits our needs - work under the hand of other executives (with foresight) in project management infrastructure and CompenSation/Distribution
- instructions for using it
- coordinating backups (CVS-wiki, SVN, Ofbiz)
- test ofbiz
- propose functionality: ofbiz is now used for inventory and there are concrete plans for maintaining shares (CompenSation/Distribution). There are many parts of ofbiz, eg. webshop and project management that we do not currently use. No need to use all, but it must be evaluated what is worth to be used and how.
- support would be needed for micro-tasks, preferrably with capability of fast offline update (that can be synced when connected online, eg. data kept in local XML or even perl files that can be synced via CVS).
- we'll have to organize HQ stuff per department, not by project. Eg. our machining partners will have access to the machinings related to all projects, but not the electronics of any project
- wiki with CVS or SVN backend - tikiwiki.org rocks (maybe even without CVS backend ?) Recommendations and examples for what to store (and how to quickly navigate among:)
- in ofbiz (like prices and manufacturing BOM relations between products)
- CVS-wiki (brainstorming and scratchpad-cache for stuff that finally goes to ofbiz)
- SVN : binary files: eg. CAD, datasheet, images (images also referred from the CVS-wiki via viewCVS that works with SVN too)
- authentication scheme: if possible, shared for CVS, SVN and ofbiz, based on ofbiz role-model
- while many things we deal with is best to represent in ofbiz as product-categories and products (like CAN transceivers, or raw material for frontplates) and associations (like BOM = bill of materials)
- the navigation in ofbiz is often clumsy: [morcego 3D graph visualizer] as used in tikiwiki could help - maybe utopistic
- attaching free-editable content (notes, scratchpad) to products is always necessary during the development phase: though ofbiz has some infrastructure for this, using a wiki link (preferrably to a tiki) seems to be more convenient
Examples for usage:
- matrix of micro-tasks would be to check (current limits, connection sanity) for all signals (megaxx pin1..pin24, mcp3208 pin1..pin16, etc..) of all signals of a few given chips.
- check overflow of a set of variables
- check if documentation of a set of firmware config variables is consistent with the firmware operation
- We should be able to see how many people checked a given item so
- it can be prioritized (generate microtasks) and know when sg. is unverified or absolutely double-checked. Similar could be used for overflow-checking of internal firmware variables, etc..
- any micro-task status must be possible to update in a few sec (local update is recommended vs. website)
- project management (traditional)
The benefit is that tasks, that consist of a large number of micro-tasks can be split up. Eg. noone starts to verify documentation of config variables, but I'm sure many people verifies a few at a time. with a method for administration we would know the status of the process, and it would mean some motivation for people to do it (there is surely a result, maybe just that it's confirmed that it's OK).
Candidates
- Jason Russell
nocandidates
- Marcell Gal