I decided to become a SoapBox Core contributor because I think the project is great and I thought I could help make it better while learning a lot. Now though, I don’t know what to do because I don’t know what needs to be done. I am not a sheep that needs to be told exactly what to do and how to do it I just want to work on contributions that will most benefit the project and help move it along in an organized fashion.

I know why SoapBox Core was started, but the project is almost 1 year old now (congratulations !) so I guess my question is where is it headed? Is the overall vision for the future of SoapBox Core explained anywhere?

Of course, I have some ideas of my own for directions SoapBox Core could take but how do I know if people are interested in my ideas becoming part of the core or how/if these ideas – once implemented – would become part of the main project? I am not looking for anything super formal , I’m just looking for some guidelines.



asked 19 Oct '10, 11:42

KarlB's gravatar image

accept rate: 0%

edited 31 Oct '10, 20:15

Mark%20Phipps's gravatar image

Mark Phipps ♦♦

What are some of your ideas for SoapBox Core?

(19 Oct '10, 18:50) Mark Phipps ♦♦

If you're seriously interested in writing unit tests, currently I only have unit tests for the bulk of SoapBox.Core.Contracts. All other assemblies in Soapbox.Core, plus SoapBox.Utilities, could use unit tests. If you are thinking of doing that, email me so I can give you more details. For now, you should be aware I'm using NUnit and Rhino Mocks. (I started SoapBox.* before I became a TDD convert, so I apologize for the lack of 100% test coverage.)

(19 Oct '10, 20:17) Scott Whitlock ♦♦

Mark:I am going to take Scott's advice from the answer he gave and submit a series of questions to this site right now... please be sure to give your input. I look forward to the discussion.

(19 Oct '10, 22:11) KarlB

Scott: I would be interested in helping to increase the code coverage, so long as I can get a little help

(19 Oct '10, 22:27) KarlB

I've been following this process:

  1. Users submit requests for features by asking a question on this site.
  2. I've been tagging that with the feature-request tag
  3. If it seems like it's a good idea, I also tag it with status-planned
  4. When I roll out a new version, I change the tags on rolled-out features to status-complete and with the version number, something in the form of: v20yy-mm-dd

Therefore, all active feature requests are available if you filter by the status-planned tag, like this.

Use the regular answer/comment mechanisms to discuss the feature itself, and talk about how it's going to be implemented. You can always erase irrelevant conversation later when the feature rolls out.

Now one of the things we really need in SoapBox Core is a way to specify a default startup location for a Pad (docked right, left, top, bottom, floating, etc.). So, I'll go add a feature request for it...


answered 19 Oct '10, 19:21

Scott%20Whitlock's gravatar image

Scott Whitlock ♦♦
accept rate: 50%

edited 19 Oct '10, 19:21

Scott: I just added a batch of questions and feature-requests to the questions page that summarize most of the ideas I had for the things I was thinking of contributing to SoapBox Core. I welcome everyone's comments on each of the questions I ask and answers I gave. I would also be interested in getting an overall commentary of the priorities of the features that end up becoming wanted by the community.

(19 Oct '10, 22:54) KarlB
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 19 Oct '10, 11:42

Seen: 2,008 times

Last updated: 31 Oct '10, 20:15

Related questions

powered by OSQA