When I searched for a clean and simple CMS for a few, relatively simple, sites I stumbled upon Pluck. Version 4.6.3 impressed me with it's simplicity, especially way I could make my own theme and the backend. Version 4.7 seems to have a few nice new features like the SEO files and submenu so I decided to check the development branch and contribute back where I can. Yesterday I filed some bugs, issues and fixes to launchpad. But there are still some questions about working on Pluck so here we go. 
One thing that bothers me is the workflow. How does it work for you... Right now I make a clean checkout, try to install a site and find some issues. Attempt to fix them locally and report the bug/fix on launchpad. When I see they are also fixed in the development branch I try to merge the local repo. I get a message from bazaar which tells me to commit but I don't feel like sharing my local version with the world. It contains no real value and contains mostly test code and ipsum lorem pages. So I throw away (or backup) the folder, checkout a clean version and start over. This is of course far from an ideal workflow so please enlighten me 
Another point is there some information available on the internal changes for 4.7? On launchpad I read that 4.6.3 modules won't work with 4.7 but what is the difference. And what can we expect to break in the (near) future and how is this communicated among developers? Is there for instance a mailinglist?
If I want to make some changes to the gallery, like include an option to add only the selected album(s) instead of the whole gallery on a page, will these changes be accepted to the main branch? In other words what is the big picture? Or does the features grow where the devs need them most (fine by me but good to know).
Will pluck for version 4.7 have some way of dealing with multiple versions of the same site but in different languages. For instance build a site in my native language (Dutch) and translate the pages to English for a broader audience. This requires some serious code design and forces all modules must support this as well.
Well that's all for now. I'll be around both here and on launchpad.
Cheers,
Sander but to avoid confusion just call me San 