[openspending-dev] Development process

[Tryggvi Björgvinsson]

Þann þri 12.mar 2013 21:29, skrifaði Adam Stiles:
> Where is the todo list for code dev? Would that go under #1? (I'm a novice
> developer but I work with real ones and will try to recruit.)

Thanks Adam!

I totally forgot about this (how could I, this is so important). That
was a really good catch (especially so early in the discussions). Thanks
a bunch!

Yes, this would go under #1 (but also under #2).

So we now have:

1. What do I do if I want to contribute code?

* Where do I find stuff to work on?
* From what branch do I base my development?
* How's the git workflow (merge vs. rebase)?
* How to I submit my patch?
* What do I do if the dev team does nothing with my patch?

2. What does the dev team do with contributions?

* How do we manage our todo list (our issue tracker)?
* How's the patch reviewed?
* How's the patch tested?
* How's the patch merged?
* How's the patch deployed?

3. How can everybody be updated on the focus of OpenSpending?

* What tools do we use for communications?
* How do we decide on our roadmap?
* Should we have regular dev meetings?
* Should we try to do regular dev blog posts (e.g. based on the dev
meetings)?

/Tryggvi