Bike Collectives Wiki - User contributions [en]

Yellow Bike Project

2007-12-04T05:36:25Z

Nwilkes2:

'''Yellow Bike Project''' is a community bike shop in Austin, TX USA.

== Mission Statement ==

The [http://www.austinyellowbike.org/home.htm Yellow Bike Project] (YBP) is a community supported ALL-VOLUNTEER 501(c)(3) non-profit organization dedicated to providing human-powered transportation for the people of Austin, running a community bike shop, and educating kids and adults. People-power is a way to limit the traffic congestion of a rapidly growing city. It also provides a sane, inexpensive, and sustainable alternative to the reliance on motor vehicles. Our project promotes cleaner air, land, and water, while encouraging people to meet their transportation needs through an active lifestyle and community participation.

== Hours ==
[http://www.austinyellowbike.org/schedule.htm Shop Hours] change monthly with volunteer availability

== Locations ==

Main Shop ([http://www.google.com/maps?q=2013+E+51st+St,+Austin,+TX+78723&ie=UTF8&om=1&z=14&ll=30.301241,-97.691561&spn=0.049502,0.127373 map])
Address: 2013 East 51st Austin, TX 78723
Directions: Between Berkman and Manor Rd., in an old airport hangar just off 51st st. Headed east on 51st St, pass through the light at Berkman and look for the 3rd driveway on the right. There will be a yellow bike attached to the sign. Follow the driveway till it ends, we are the last warehouse on the left.

Treasure City Satellite Shop ([http://www.google.com/maps?q=1720+E+12th+St,+Austin,+TX+78702&ie=UTF8&z=15&om=1&iwloc=addr map])
Address: 1720 East 12th Street, 78702
Directions: Located to the left of the Treasure City Thrift Store located at 12th and Leona.

== About ==

[http://www.austinyellowbike.org/about_ybp.htm About]

== Services ==
Yellow Bike Project provides the following services [http://www.austinyellowbike.org/projects.htm View full list on website]:

* Refurbishing donated bicycles for nominal resale and charity purposes
* Community access to bike repair knowledge, tools and shop space
* Earn-A-Bike program for Adults
* Bikes to Schools Program

== Website ==

http://www.austinyellowbike.org

== See Also ==

== See Also ==

* [[Community Bicycle Organizations]]

[[Category:Community Bicycle Organizations]]

Austin Yellow Bike Project

2007-12-04T05:35:56Z

Nwilkes2: Austin Yellow Bike Project moved to Yellow Bike Project: wrong name

#REDIRECT [[Yellow Bike Project]]

Yellow Bike Project

2007-12-04T05:35:55Z

Nwilkes2: Austin Yellow Bike Project moved to Yellow Bike Project: wrong name

'''Austin Yellow Bike Project''' is a community bike shop in Austin, TX USA.

== Mission Statement ==

The [http://www.austinyellowbike.org/home.htm Austin Yellow Bike Project] (YBP) is a community supported ALL-VOLUNTEER 501(c)(3) non-profit organization dedicated to providing human-powered transportation for the people of Austin, running a community bike shop, and educating kids and adults. People-power is a way to limit the traffic congestion of a rapidly growing city. It also provides a sane, inexpensive, and sustainable alternative to the reliance on motor vehicles. Our project promotes cleaner air, land, and water, while encouraging people to meet their transportation needs through an active lifestyle and community participation.

== Hours ==
[http://www.austinyellowbike.org/schedule.htm Shop Hours] change monthly with volunteer availability

== Locations ==

Main Shop ([http://www.google.com/maps?q=2013+E+51st+St,+Austin,+TX+78723&ie=UTF8&om=1&z=14&ll=30.301241,-97.691561&spn=0.049502,0.127373 map])
Address: 2013 East 51st Austin, TX 78723
Directions: Between Berkman and Manor Rd., in an old airport hangar just off 51st st. Headed east on 51st St, pass through the light at Berkman and look for the 3rd driveway on the right. There will be a yellow bike attached to the sign. Follow the driveway till it ends, we are the last warehouse on the left.

Treasure City Satellite Shop ([http://www.google.com/maps?q=1720+E+12th+St,+Austin,+TX+78702&ie=UTF8&z=15&om=1&iwloc=addr map])
Address: 1720 East 12th Street, 78702
Directions: Located to the left of the Treasure City Thrift Store located at 12th and Leona.

== About ==

[http://www.austinyellowbike.org/about_ybp.htm About]

== Services ==
Yellow Bike Project provides the following services [http://www.austinyellowbike.org/projects.htm View full list on website]:

* Refurbishing donated bicycles for nominal resale and charity purposes
* Community access to bike repair knowledge, tools and shop space
* Earn-A-Bike program for Adults
* Bikes to Schools Program

== Website ==

http://www.austinyellowbike.org

== See Also ==

== See Also ==

* [[Community Bicycle Organizations]]

[[Category:Community Bicycle Organizations]]

Bike Collective Software

2007-11-26T03:37:32Z

Nwilkes2: /* Inventory Tracking */

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Interface ===
* Hopefully ajax interface. At Yellow Bike we are having slow load times because entire list of 40 shop users has to be refreshed for each form submit. It makes using the system a bit tedious.
* Have a way to edit and delete any record created. Example: transaction, people tracking.
** Security: To prevent tampering require a password when hours for a person are being changed and do not match current time or location - ip matching.
** Restrict edits for certain events to the ip address that created it. Example: allow users to login to shop only from the shop instead from their living room.
* Database change tracking and deletions.
** Time stamp every change to the database
** Create database so that no data is ever deleted. Instead have a column that designates that the record is deleted and a timestamp for the action.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must have the following capabilities:

* Select user for punch in and out. This should be a autofilter like many sites now use instead of a drop down. (Currently yellow bike has over 1500 people in a drop down and it is difficult to locate a particular user.
* Time Handling
* Allow individuals to punch in and out of a time clock. This should be intuitive.
** Allow for override of current time with password authorization.
** Time selection should be intuitive and quick

*Relationship to events
** Allow individuals to pre-register (volunteer) for events.
** All hours tracking should be assigned to a defined event.

* Optional fields
** Allow individuals to select their role at the event. Example: coordinator, volunteer, court ordered hours
** Allow hours during the event for each person to be assigned to a project. Example: Kid's bike build, Yellow Bikes
** Comments

* Interface
** Allow for a splash screen to welcome new visitors to the event or shop.
** Yellow Bike has multiple shop locations that might be running concurrently. Use IP address to keep shop sign-ins straight otherwise people will be signing into the wrong event.

*Reporting Features
** Allow the organization to report summaries on events and individuals.
** Allow custom queries to database for more complex reporting using external query tool. Example MySQL Query Browser
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

Example
* Yellow Bike uses a transaction log tracking: Date, Sale Type, Amount, Description, Type, sold to, sold by, quantity donated (for yellow bikes and kids bikes to schools). We don't use this for inventory tracking so much as output tracking.

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
** Some properties will affect hours or inventory tracking. example: different events might have a different list of participant roles for the event. At Yellow Bike during a shop event someone can be a coordinator (cook...), volunteer, personal, court ordered hours.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T03:15:21Z

Nwilkes2: /* Hour Tracking */

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Interface ===
* Hopefully ajax interface. At Yellow Bike we are having slow load times because entire list of 40 shop users has to be refreshed for each form submit. It makes using the system a bit tedious.
* Have a way to edit and delete any record created. Example: transaction, people tracking.
** Security: To prevent tampering require a password when hours for a person are being changed and do not match current time or location - ip matching.
** Restrict edits for certain events to the ip address that created it. Example: allow users to login to shop only from the shop instead from their living room.
* Database change tracking and deletions.
** Time stamp every change to the database
** Create database so that no data is ever deleted. Instead have a column that designates that the record is deleted and a timestamp for the action.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must have the following capabilities:

* Select user for punch in and out. This should be a autofilter like many sites now use instead of a drop down. (Currently yellow bike has over 1500 people in a drop down and it is difficult to locate a particular user.
* Time Handling
* Allow individuals to punch in and out of a time clock. This should be intuitive.
** Allow for override of current time with password authorization.
** Time selection should be intuitive and quick

*Relationship to events
** Allow individuals to pre-register (volunteer) for events.
** All hours tracking should be assigned to a defined event.

* Optional fields
** Allow individuals to select their role at the event. Example: coordinator, volunteer, court ordered hours
** Allow hours during the event for each person to be assigned to a project. Example: Kid's bike build, Yellow Bikes
** Comments

* Interface
** Allow for a splash screen to welcome new visitors to the event or shop.
** Yellow Bike has multiple shop locations that might be running concurrently. Use IP address to keep shop sign-ins straight otherwise people will be signing into the wrong event.

*Reporting Features
** Allow the organization to report summaries on events and individuals.
** Allow custom queries to database for more complex reporting using external query tool. Example MySQL Query Browser
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
** Some properties will affect hours or inventory tracking. example: different events might have a different list of participant roles for the event. At Yellow Bike during a shop event someone can be a coordinator (cook...), volunteer, personal, court ordered hours.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T01:47:54Z

Nwilkes2: /* Hour Tracking */

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Interface ===
* Hopefully ajax interface. At Yellow Bike we are having slow load times because entire list of 40 shop users has to be refreshed for each form submit. It makes using the system a bit tedious.
* Have a way to edit and delete any record created. Example: transaction, people tracking.
** Security: To prevent tampering require a password when hours for a person are being changed and do not match current time or location - ip matching.
** Restrict edits for certain events to the ip address that created it. Example: allow users to login to shop only from the shop instead from their living room.
* Database change tracking and deletions.
** Time stamp every change to the database
** Create database so that no data is ever deleted. Instead have a column that designates that the record is deleted and a timestamp for the action.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must have the following capabilities:

* Time Handling
* Allow individuals to punch in and out of a time clock. This should be intuitive.
** Allow for override of current time with password authorization.

*Relationship to events
** Allow individuals to pre-register (volunteer) for events.
** All hours tracking should be assigned to a defined event.

* Optional fields
** Allow individuals to select their role at the event. Example: coordinator, volunteer, court ordered hours
** Allow hours during the event for each person to be assigned to a project. Example: Kid's bike build, Yellow Bikes
** Comments

* Interface
** Allow for a splash screen to welcome new visitors to the event or shop.

*Reporting Features
** Allow the organization to report summaries on events and individuals.
** Allow custom queries to database for more complex reporting using external query tool. Example MySQL Query Browser
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
** Some properties will affect hours or inventory tracking. example: different events might have a different list of participant roles for the event. At Yellow Bike during a shop event someone can be a coordinator (cook...), volunteer, personal, court ordered hours.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T01:37:50Z

Nwilkes2: /* Hour Tracking */

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Interface ===
* Hopefully ajax interface. At Yellow Bike we are having slow load times because entire list of 40 shop users has to be refreshed for each form submit. It makes using the system a bit tedious.
* Have a way to edit and delete any record created. Example: transaction, people tracking.
** Security: To prevent tampering require a password when hours for a person are being changed and do not match current time or location - ip matching.
** Restrict edits for certain events to the ip address that created it. Example: allow users to login to shop only from the shop instead from their living room.
* Database change tracking and deletions.
** Time stamp every change to the database
** Create database so that no data is ever deleted. Instead have a column that designates that the record is deleted and a timestamp for the action.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must:

* Allow individuals to pre-register (volunteer) for events.
* Allow individuals to punch in and out of a time clock.
* Allow hours to be assigned to an event.
* Allow hours during the event for each person to be assigned to a project. Example: Kid's bike build, Yellow Bikes
* Allow individuals to select their role at the event. Example: coordinator, volunteer, court ordered hours
* Allow the organization to report summaries on events and individuals.
* Allow custom queries to database for more complex reporting.
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
** Some properties will affect hours or inventory tracking. example: different events might have a different list of participant roles for the event. At Yellow Bike during a shop event someone can be a coordinator (cook...), volunteer, personal, court ordered hours.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T01:33:09Z

Nwilkes2:

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Interface ===
* Hopefully ajax interface. At Yellow Bike we are having slow load times because entire list of 40 shop users has to be refreshed for each form submit. It makes using the system a bit tedious.
* Have a way to edit and delete any record created. Example: transaction, people tracking.
** Security: To prevent tampering require a password when hours for a person are being changed and do not match current time or location - ip matching.
** Restrict edits for certain events to the ip address that created it. Example: allow users to login to shop only from the shop instead from their living room.
* Database change tracking and deletions.
** Time stamp every change to the database
** Create database so that no data is ever deleted. Instead have a column that designates that the record is deleted and a timestamp for the action.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must:

* Allow individuals to pre-register (volunteer) for events.
* Allow individuals to punch in and out of a time clock.
* Allow the organization to report summaries on events and individuals.
* Allow custom queries to database for more complex reporting.
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
** Some properties will affect hours or inventory tracking. example: different events might have a different list of participant roles for the event. At Yellow Bike during a shop event someone can be a coordinator (cook...), volunteer, personal, court ordered hours.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T01:32:34Z

Nwilkes2:

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

== Interface ==
* Hopefully ajax interface. At Yellow Bike we are having slow load times because entire list of 40 shop users has to be refreshed for each form submit. It makes using the system a bit tedious.
* Have a way to edit and delete any record created. Example: transaction, people tracking.
** Security: To prevent tampering require a password when hours for a person are being changed and do not match current time or location - ip matching.
** Restrict edits for certain events to the ip address that created it. Example: allow users to login to shop only from the shop instead from their living room.
* Database change tracking and deletions.
** Time stamp every change to the database
** Create database so that no data is ever deleted. Instead have a column that designates that the record is deleted and a timestamp for the action.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must:

* Allow individuals to pre-register (volunteer) for events.
* Allow individuals to punch in and out of a time clock.
* Allow the organization to report summaries on events and individuals.
* Allow custom queries to database for more complex reporting.
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
** Some properties will affect hours or inventory tracking. example: different events might have a different list of participant roles for the event. At Yellow Bike during a shop event someone can be a coordinator (cook...), volunteer, personal, court ordered hours.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T01:04:43Z

Nwilkes2: /* Developers */

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must:

* Allow individuals to pre-register (volunteer) for events.
* Allow individuals to punch in and out of a time clock.
* Allow the organization to report summaries on events and individuals.
* Allow custom queries to database for more complex reporting.
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP, MySQL
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T00:59:36Z

Nwilkes2: /* People Tracking */

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must:

* Allow individuals to pre-register (volunteer) for events.
* Allow individuals to punch in and out of a time clock.
* Allow the organization to report summaries on events and individuals.
* Allow custom queries to database for more complex reporting.
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)\
** Several types should be able to be assigned to each person.

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...

Bike Collective Software

2007-11-26T00:51:24Z

Nwilkes2:

This is the collaborative project description for custom '''bike collective software'''.

== Requirements ==

# The software will be an open source component of a CMS system. The choices we already narrowed it down to are Joomla, Drupal, and Wordpress.
# Component features and/or Modules will be built to handle needs of the various shops. These modules can be turned on and off through a GUI interface.
# A very intuitive installer will be crucial to help get all the non-profits started using the software. It should have pre-programmed data-sets for common collective / cooperative types.
# Internationalization via simple language file options.

== CMS Systems ==

Here are some test systems you can experiment on. If you want a login, or even your own test site let [mailto:jonathan@slcbikecollective.org Jonathan Morrison] know.

* [http://drupal.bikecollectives.org/ Drupal]
* [http://joomla.bikecollectives.org/ Joomla]
* [http://wordpress.bikecollectives.org/ Wordpress]

=== Jonathan Morrison's Opinion ===

My background is in software engineering as is my degree. I actually installed [http://wordpress.bikecollectives.org/ Wordpress], [http://joomla.bikecollectives.org/ Joomla], [http://drupal.bikecollectives.org/ Drupal] recently to compare them. Here is my honest opinion of each of them and their user groups. I take into account sustainability factors like, "sure I am a nerd, but if I wasn't here, could someone else cover it?"

Wordpress was by far the easiest to install and get running, however it lacks components and features to _easily_ do anything more than a blog. For example if you want to add a photo gallery, etc.,... One of my main observations is the user group that uses this is more graphic designers, not programmers. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Wordpress. This makes upgrades really easy.

Drupal was by far the most difficult to install, however it is very universal. With flexibility comes complexity, so make sure you have a hard core nerd on staff before you commit to this one. I would for the Salt Lake City Bicycle Collective, but in the event I wasn't around, I can't see it being maintained properly. The user group for this tends to be people like me, geeks. As a result, the graphical templates aren't as impressive as other CMSs. One cool feature that [http://bikegeeks.org/ Bike Geeks] used is they made all the Chicago sites connect. One unique feature of Drupal is that a single installation of Drupal can run several sites. Sadly, Dreamhost does not have a one-click install feature drupal, so installations and upgrades have to be done manually.

Joomla, while I have spent the most time with it is still my personal favorite. It has the largest user base, and more addons and templates than any other CMS out there. To be fair, the big downfall isn't in technical complexity, but what how things are named. There are 1000s of templates, components, modules, mambots out there, but you need to know what they are before you can use them. Another plus is that you, as a nonprofit, can get free hosting using Dreamhost, and they have a simple one-click-install for Joomla. This makes upgrades really easy.

== Existing CMS Plugins with similar functionality ==
* [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,72/Itemid,35/ CiviCRM]

== Features ==

Generically speaking we need to '''keep track of hours, people, and things (sometimes in different stages) as they relate to various events'''. Every community bike organization has a different name for these and uses a different subset of them -- so they will need to be easily re-nameable and be able to turn on and off.

=== Hour Tracking ===

For Volunteers and or Staff as they commit ahead of time to events and then how to keep track of when they do or don't follow through.

The system must:

* Allow individuals to pre-register (volunteer) for events.
* Allow individuals to punch in and out of a time clock.
* Allow the organization to report summaries on events and individuals.
* Allow custom queries to database for more complex reporting.
** Have an alternate export option that dumps raw data to a delimited format for excel editing for less database oriented folk. Filters on data export would be nice.

=== People Tracking ===

The system needs to:

* Allow for individuals to provide their contact information, required and non-required items.
* Allow for individuals to opt into or out of an email list.
* Allow for the organization to more than one contact at once. (ex: Paper signup forms at tabled events.)
* Allow for the organization to designate what contact information is required and what is not.
* Allow for the organization to create a unique set of contact types. (ex: Local Business Contacts, Distributors, Board of Directors, Members, Customers, Earn-A-Bikers, Mechanics, Cooks, Clergy, etc.,...)

=== Inventory Tracking ===

Hopefully we can generalize this as well.

'''Examples:'''
* Fleet/Library/Yellow Bikes
* New Parts
* Used Parts
* Tools
* Rentals

=== Event Listing ===

Events could be meetings, open shop nights, valet bicycle parking, tabling festivals, etc.,...

The system needs to:

* Allow individuals to sign up for events.
* Allow the organization to define different types of events.
* Allow the organization to schedule different events.

=== Event Signups ===

This could be used to sign up for an event or could be used to keep track of people at an event.

=== Repair Tracking ===

This might be a part of Inventory, but a way to easily see what bikes need what work.

=== Accounting ===

=== Fundraising ===

=== Recycling ===

This module will track how many frames, wheels and miscellaneous metal recycling. It will also track items given to artists.

=== Art ===

?

=== Wish List Posting ===

This could be as simple as a classified section. ([http://support.gorsk.net/index.php?option=com_filez&Itemid=40&func=selectfolder&filecatid=3 Joomla Component Example])

== Software Life-cycle ==

Winter is a great time to get this rolling and hopefully have it ready for next spring.

* Create the dev team [http://lists.bikecollectives.org/listinfo.cgi/dev-bikecollectives.org Email List]
* Create a [[Bike Collective Software | project description]]
* Delegate programming / graphic design
* Development Stage
* Internal Testing / External Testing
* Fix Bugs
* Beta Release / External Testing
* Fix Bugs
* Final release
* Maintenance / Feature Requests

== Developers ==

* [mailto:jonathan@slcbikecollective.org Jonathan Morrison] - PHP, etc.,..
* [mailto:rich@richpoints.com Rich Points] - CSS/XHTML
* [mailto:nwilkes2@gmail.com Nathan Wilkes] - PHP
* [mailto:pgarver@gmail.com Peter Garver] - PHP
* [mailto:jayvarner@gmail.com Jay Varner] - Perl, etc.,...