Project stutter - guidelines
Project stutter - guidelines
Startup material for a new project stutter is listed below:- Guidelines
- Trawl template
Guidelines
These entries are guidelines only.
They do not, and do not try to, proscribe how to go about doing project stutters.
It is expected that methods will evolve in the future.
Adding ideas for effort
Effort is the application of a person or application to performing an activity.Effort may be manually performing an activity, starting an application / algorithm to work on an activity, or coding up the ability to use an algorithm at a later point. This is not an exhaustive list.
Effort is used rather than task / job because all of the effort entries are optional and suggestions. There is no imposition that the effort needs to be done. Effort is an expression of the evaluation that a piece of work is worthwhile to do.
Where possible flag the effort with some id or use a system from which an id can be extracted. E.g. I use the id sjhunt.
An assessment that effort is worthwhile can be wrong, or changed at a later point. There is (in my opinion) value in expressing efforts that are at the time thought to be of value. I cannot currently see a point in expressing efforts that someone does not find valuable.
Twitter can be used to direct an expression of effort to the appropriate project stutter. E.g. @projectstutter.main will target expressions of effort toward the repository (this blog at main.projectstutter.com). Direction does not need to be exact, every trawl should consider that an effort might be misdirected.
Creating new project stutters
New project stutters should consist of some identifier and some repository.Currently I use the namespace on twitter as the identifier (e.g. @projectstutter.main is used to direct efforts to the project "main")
The dot should be considered a reserved character when performing namespace identification. As such it should not be used within a single level namespace name. There may be some translation required if a system that uses a different separation character is used. E.g. slash (/) is often used.
A blog, such as this one at main.projectstutter.com, or other update-able storage mechanism should be used to retain state. Preferably one with version control such as mercurial.
A reference back to this main blog post can be included in a new project stutter in order to gain access to the common setup elements, such as templates and methods.
Copy certain blog entries to the new project stutter repository may be worthwhile to facilitate independent / disconnected project stutters. Implicit permission is given to do this for any entries that are seen as framework entries / startup entries in this main project stutter. sjhunt.
Notable outstanding efforts
Notable outstanding efforts is a post that contains a list of efforts that have been identified that have not yet been completed.This might mean that there are pieces of the effort that are not done, that the whole of the effort is not done, or that something is blocking the effort.
The post might be ordered according to the last editors sense of priority. Any ordering or priority classification should be considered as a recommendation rather than an insistence. (In line with project stutter principles.)
sjhunt
Comments
Post a Comment