Hi Keith,
There is a built-in wiki, issues, etc.... in github. I agree that a format needs to be setup starting of with the structure of the solution, etc...
I am not too worried about the commands names slapped together in the samples because I can not see any reason for it to contain any commands.
A consistent naming convention for parameters, methods, etc... is important and hopefully if it starts to gain more traction then the more input and ideas to toss around.
Right now I was thinking of people just slapping together ideas and what the best plan of attack would be.
Should we wrap certain objects or use extension methods, the GroupDictionary in PrintGroups will fall flat on its face if IncludingErased property is called. It can be fixed.
What I posted was one of fifty different ways I thought about doing it.
It would be much easier verbally and visually to express ideas I know it is for me.
There so many things could do and so many different ways of doing them.
We could start off with a coming up with small set of decisions and actions that need to be made to get project started.
I had same thought if it gained a little steam to ask gile if he wanted to incorporate his geometry extensions.