Difference between revisions of "Projects:Projects"
Scott Keeler (talk | contribs) |
(→Discussion) |
||
| Line 59: | Line 59: | ||
==== Discussion ==== | ==== Discussion ==== | ||
| − | + | I love the description of a project above, where new people can come to a place and get involved. '''And''', I think our use of ''Meetings'' pages hinders that goal, currently. Here's a point of view: | |
| − | + | * Meetings are a means to an end, the advancement of a project. | |
| + | * Face to face meetings are only one way we communicate. We also use ad hoc IRC, ad hoc skype, scheduled skype, phone calls, etc. | ||
| + | * If a meeting is about organizing a project, the outcome of that meeting is an enchanced project page, with more clear goals, more clear upcoming tasks, more clear "completed" tasks, more clear roles to be filled or that are filled, etc. | ||
| + | * If the meeting is actually doing some work (parallel pairing, or some such), then work is actually getting done and the results of that work getting done can also appear on the project page. | ||
| + | * If a meeting goes of into "Thoughts On" territory, that can be documented on a linked "Thoughts On ..." page, without cluttering up the project page. | ||
| + | * There is not need for a specific "meeting" page for a particular meeting, unless there's a reason, for some reason. We don't need a page for every IRC interaction or skype phone call. It's just communication. The work is the work, and that's on the project pages. | ||
| + | Just thoughts. What are yours? [[User:TedErnst|TedErnst]] | ||
Revision as of 20:54, 9 July 2007
PROJECTS: Community / Content / Design / Development / Admin
Why we're doing this
- To know how we're deploying our resources
- To enable growth
- New people can join us and know how
- To advance ideas into action leading to completion of valuable activities
- Moving our planning and work into a shareable space
- To encourage self directed effort
We know we are done when
- We all know and trust the process
- When a community and a staff member (Portland and non-Portland) can come to the page and effortlessly join a project
Project Tasks
- When this is finished, we'll move it to an OngoingProject.
- Create Projects Tour
People
- Ward and Scott are organizing this
- Scott is transferring the cards into project pages
- Tanwir will coordinate this effort with the Lahore office
Meetings
- Portland content & community plans on every wednesday
- Portland development group plans every other friday
Useful Links
Community
Content
Design
Development
Admin
Discussion
I love the description of a project above, where new people can come to a place and get involved. And, I think our use of Meetings pages hinders that goal, currently. Here's a point of view:
- Meetings are a means to an end, the advancement of a project.
- Face to face meetings are only one way we communicate. We also use ad hoc IRC, ad hoc skype, scheduled skype, phone calls, etc.
- If a meeting is about organizing a project, the outcome of that meeting is an enchanced project page, with more clear goals, more clear upcoming tasks, more clear "completed" tasks, more clear roles to be filled or that are filled, etc.
- If the meeting is actually doing some work (parallel pairing, or some such), then work is actually getting done and the results of that work getting done can also appear on the project page.
- If a meeting goes of into "Thoughts On" territory, that can be documented on a linked "Thoughts On ..." page, without cluttering up the project page.
- There is not need for a specific "meeting" page for a particular meeting, unless there's a reason, for some reason. We don't need a page for every IRC interaction or skype phone call. It's just communication. The work is the work, and that's on the project pages.
Just thoughts. What are yours? TedErnst
