Hi guys,

it's time to RedRacer now that both benschi and erisco have offered to work on it. My role in this project will mostly be a managerial one, although I will look over the code regularly to make sure it meets our best practices.

I'd like all dev related discussions to happen here on this list.

Trac and SVN are set up at http://www.redracer.org/

I have added two milestones, and will add the major feature tickets once we have discussed them.

Right now, the focus is *not* on multitenancy, that'll be reserved for 2.0. Version 1.0 should only have basic features.

Benjamin and I have discussed those already, but I'll put them up for discussion here again:

- Users (registration, simple profile)
- Projects
  - Downloads/Releases
  - Comments
- Ratings, although we might consider using a "stack" like Ohloh's exclusively, and no ratings at all (I've read a blog post about that somewhere recently, but can't remember where or how) - "Tip of the hat" and "Wag of the finger" (where Agavi core devs can say "this is awesome, we recommend it" or "this is not good because it breaks x or is insecure or defeats purpose bleh") - separate from ratings

For future releases, there'd be stuff like:
- Tags
- Dependencies
- Remote package installs (that mostly requires an infrastructure in Agavi, not in the forge, and is specific to forge.agavi.org) - Multitenancy support (so that RedRacer is a real software, with a bunch of user-editable config files to control templates, settings etc)
- Magic

Two non-technical questions:
- I think we should have Contributor License Agreements; anyone has objections? It would be the standard Apache CLA.
- What license do we use?

Cheers,

- David

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev

Reply via email to