wiki forum trac otrs blogs mailman bewelcome
Personal tools
164

Unconference conclusion

From BeVolunteer Wiki

Jump to: navigation, search

This page has been moved to the the BeWelcome wiki and locked from further editing.
See BW Wiki: Unconference conclusion

This page is to show an overview of the results of the unconference. It's a list of action items that we can/should address in the coming months.

Contents

Privacy and security

  • Write and perfect a complete and detailed privacy, security and safety policy. What are our procedures? What can be expected? What exactly happens to your data when you are banned/delete your account? Who can see/do what on the site? What are the legal issues involved with hosting?
  • Look at the logging of admin activities so we can monitor (and audit) everything that happens on the site.
  • Write out a proposal for an audit (what would we like to see audited?) and find an outside expert to actually do it. This person will need very detailed information on the inner working of the organization and its members, so we want to make a very good choice here.
  • Work out a schedule for regular, public reporting by the safety team.

Organizational

  • Look at dates for more unconferences.

Development in general

  • Look at the possibility of testing more of our code.
  • Define a standard for a "stable" build. (E.g. no critical bugs, only x major bugs, etc) Work hard to meet this standard.
  • would like to get more clear description what a "stable" build should be used for. e.g. does only a stable build make it to the production website bewelcome.org? philipplangeBW, wikitalk 14:35, 20 January 2008 (UTC)
  • The idea came from the frustration with bugs. In order to have a clear and attainable target, we need to be able to set a "milestone", after which we can reorient on new features. It is a solution to priority issues and not really about our release cycle. --Tgoorden 01:39, 21 January 2008 (UTC)

New features priority list

This is just a first draft and NOT officially decided upon yet.

The clear Number One on the priority list is further bug fixing. Since this is an ongoing process there will only be mentioned the most urging bug fixes here and they wont be repeated in the general priority list.

Urgent bug fixes:

  • Sign up process
  • bug fixing of the geo database, e.g. in search function 'browse by country': Germany --> Cities, instead of the 16 German provinces first and then the respective cities

'Most annoying' problems

These were discusssed in a smaller group, and we did not really finish the discussion.


New Feature Priority list:

We've been intensively brainstorming about the groups within BW and discovered that our vision of a local group actually provides a priority list and road map for many different features.

  1. Reorganizing the groups; more sensible in order to avoid as many groups as in CS (Major categories and subcategories)
  2. Forum improvement; improved navigation and regional forum system
  3. Creation of a travel log (also known as trip planner)
  4. Creation of meeting functionality
  5. Geographical, time and text tagging on profiles, meetings, locations, pictures
  6. Creation of a (local) event calendar
  7. Creation of a regional event display above the respective region
  8. Creation of a local group template page (first draft of page will be added later)
  9. Creation of an administration tool for those local groups to be used by the respective volunteer
back to