How do I contribute to the Toolkit?
We have been brainstorming ideas to get community contributions in the Toolkit for almost a year now. After long deliberation we now have a plan and would like to try it out.
If these are some questions on your mind?
- How do I fix a bug in the Toolkit?
- How do I add a new feature to a Toolkit control?
- How do I get my control to be included in the Toolkit?
Then this document should answer them.
The Patch Utility has been very effective in getting small fixes and feature requests be included in the Toolkit. New controls, however, need more design and code review iterations before they can be released. Hence we are suggesting that they be staged as Codeplex projects. Based on the project's activity using metrics like number of downloads, feature requests, actual fixes and frequency of releases we will decide if the control should be included in the Toolkit. This will allow multiple users to submit the same control but let the users decide which one works best for them and should be a part of the Toolkit.
Hope that helps and we look forward to your contributions!
Comments
Anonymous
October 15, 2007
We have been brainstorming ideas to get community contributions in the Toolkit for almost a year nowAnonymous
October 18, 2007
I'm hoping someone will implement a rich text editor...Anonymous
October 18, 2007
We have a community member who plans to have one soon. We will link it from here: http://www.codeplex.com/AtlasControlToolkit/Wiki/View.aspx?title=CandidateControls&version=1 when it is ready.Anonymous
November 27, 2007
Maybe you can have an official incubator project on codeplex? That way, it has the benefits of the testing framework, and more people working on one single project instead of some nice controls below the radar. Ajax Control Toolkit has something 'official' about it that makes people trust it/use it more than other projects (I know I do). So share the wealth and start up an official ACT Lab. First project in the list: RTE! Thanks for considering!