Sorry it's taken me so long to reply. It's been a busy week.
Your release cycle would work fine for me. Generally, the way I contribute is by throwing in tidbits of my everyday work into the project. A more predictable release cycle does seem to be the way to go. I may be able to sprinkle in a few
topical extensions here and there that you can use for your article.
The only problem we might have in making this happen is where we merge to. Here are my concerns:
1) You have established links into your project from other places, as do I. MSDN magazine will also be crediting my project in an upcoming issue on extension methods. You have several references to your project out there, as well.
2) Regarding the namespace, I'm not sure how I feel about it being based upon a commercial entity (I'm not sure how I feel with it being attached to any commercial ventures). How attached are you to PGK as a root namespace?
3) There are also a few other contributors to my project, and I haven't had a chance to find out how they feel about merging into another project.
Would you require that we merged into yours? Should we create a new project, perhaps, and create a namespace that is more generic; and both link our current project homepages to it? We could link to your articles, as you do now, from the homepage.
Coordinator bios/pictures/links, perhaps? Also, I wouldn't mind contacting a few other (less active) extension project coordinators and asking them if they'd like to merge into whatever we create.
What are your thoughts on these concerns? I apologize that I have them, but I have them nonetheless.
I do have one other thing to contribute - I created a documentation app that creates the CodePlex homepage code from xml comments (which I could spice up to make it look more like yours). It also documents code usage examples (you can see these in
other discussions on my project page).