My role is currently very simple, I just have an idea and I think someone else may find it useful. I have no experience managing open source projects, so if someone has experience (or wants to take it on), please step forward :)
Conditions for participating? None really. If you want to help write code, write tests, find bugs, etc. do it :) I could do this all on my own, but the client may end up being only useful to me. For architecture I haven't given it too much thought yet. PSR-0 and Composer package are as far as I've gone. Some things that bothered me when working with the official client are: - lack namespaces - multiple class definitions for the same class in various files - lots of relative require_once statements - arguably many superfluous classes (e.g. Paging) So these are the things I would like to solve, but others may have other opinions, so please let me know. Project planning is difficult, when you don't know what you're building, so that surely depends heavily on the design decisions. Thankfully the official client does work well (in it's own way), so it's not like this is a blocker. Anyways, please let me know what you think :) -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
