Source Tree

From RCC 2007

Jump to: navigation, search

Source Tree Strategic Roadmap

Collaborative space for software development. For geeks, but also hopefully for users, testers, etc as a community. See SourceTree for more of a context.

If we were to look right now from what we know about open source software, what would be build to support collaboration, project management, bug tracking, feature request feedback to be the way we want? This isn't about centralizing control, but about increasing collaboration. Right now, because sourceforge doesn't give you what you need, you've got token info on source forge, but they do their real work somewhere else. Being able to have distributed architecture where people can manage their own trees. People can sponsor their own "families" that are complying with particular protocol, API, etc...possibly supporting object registries; visualization tools, etc.

What's the plan? We need to create a plan.

We do have some tools that would be helpful in building this infrastructure.

(note: look into http://communitywiki.org/ProjectSpace )

What are the priorities? What things are within reach that we can implement? What are the biggest needs?

We need:

We have to pick what works best to start with and an API so that if someone wants to use something else, they can but still have it be connectible to the system as a whole.

Here are pieces needed and possible OOB solutions:

First Tier

  • Source Control: svn
  • Project Management: needs to be built incrementally {need to identify components and prioritize development: specification}
  • Web presence: (wiki, RSS, News) - pick a default CMS

These things can be implemented within a matter of weeks

Other features

  • Issue Tracking:
  • Release System:
  • Calendaring:
  • Bug reporting:
  • Feature Requests:
  • Related Projects: (social network map - see people who are connected to projects)
  • Build testing:
  • Communication Tool: mailman (build out congo to allow mulitple methods of viewing / pulling data)
  • Decision Making Process: mydecision, beyond yes,
  • Reputation / contribution tracking: congo

Resources available:

  • Mike B available for programming
  • Kevin knows some geeks who are so annoyed with track that they want build something else

How we intend on communicating and continuing to collaborate mailing list, newsletters, oguild.org (primary method of communicating)

[edit]

Comments

Are there links available that describe mydecision and congo-db? I can't figure out what mydecision refers to, and I found the company that makes congo-db but i couldn't find a detailed description of it. Thanks Bayle Shanks 23:35, 4 February 2007 (UTC)

Retrieved from "http://2007.recentchangescamp.org/Source_Tree"
Personal tools