I don't know how much of the following of the following should be included
in the proposal, but its probably worth starting discussions
on separate threads:
*Branding/Marketing,*
*Documentation, *
*.Net API*
*Backwards Compatibility Support *
*Linq/WCF/Annotations*
*
*
On Thu, Dec 30,
*PR/Marketing/Branding:*
Even open source need this. Its never something totally the forefront on the
developers mind, but its going to be key in order to build a community.
The main part of marketing to strategically build connections between people
and a product/service so that they associate a
*Net Idiomatic Api Version*
*We should probably be looking for with this criteria is readability
getting people familiar with any new code base faster within their own
Idiom. *
*
*
Starting with a proposal that we use the internal Ms coding
*Last one for the year, See ya next year Happy New Year to all.*
*
*
*Documentation.*
*
*
Who should be responsible for this? Where should it live? Wiki or should
we have a separate site that aggregates. blogs, twitter feeds, facebook,
tutorials, wiki, documentation, etc?
I propose that we
I agree with the suggestion to follow the MS Coding standard. It's a
good general guideline. Specifically, I'd like to follow all
guidelines put forth in the book:
Framework Design Guidelines: Conventions, Idioms, and Patterns for
Reusable .NET Libraries by Krzysztof Cwalina and Brad Abrams
There are a number of out of the box projects that I think should be developed
as we have time that will help facilitate new people getting started, be used
as examples and templates, and give us some good stuff to blog about :). This
all goes to the marketing/PR/Community stuff that was sent
