Create a wiki page for our codeplex feature requests.

Sep 20, 2010 at 4:33 AM

I think we should create a wiki page that lists the codeplex feature requests that would enable the project to have more collaboration/efficentci and link to it from the Get Involved section of the project homepage.  We could ask for support by asking users to vote up our requests.. 

 

just a thought.

Coordinator
Sep 20, 2010 at 4:35 AM

You mean the feature requests for improvements to CodePlex.com that we’ve made or need? If that’s what you meant, I think that’s a great idea. Can you take the lead on that?

Sep 20, 2010 at 4:37 AM

that is what I meant and I will take lead on that.. since I cannot commit code :(

Coordinator
Sep 20, 2010 at 4:42 AM

Thanks!

BTW, just because you can't commit code directly to the main repository doesn't mean you can't contribute coding help in the form of bug fixes. The primary development model we've been working with is to do all development in private forks and send pull requests. I've been doing that, even though technically I could commit directly to the main repository (and risk getting gobsmacked by my co-workers).

Your only limitation is that without a CLA on file, you can't commit new features. You can only commit bug fixes and small code tweaks. I'll have to check, but I imagine Infrastructure work should actually be fine. But better to double check.

Sep 20, 2010 at 4:43 AM
Just as a question for pull requests - when completing a feature, should I be submitting a pull request at that point or waiting for the code to be verified?
____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

Sep 20, 2010 at 4:45 AM
i totally will commit some bug fixes.. its just a PIA while the project is in private mode. I will fork it up, on tuesday.
 
Coordinator
Sep 20, 2010 at 4:46 AM

Submit the pull request. I think we should only spend our time verifying features that are in the main fork. Drew, do you agree?

When you issue the pull request, the integration master (I just made that name up. What should we call that role?) will review the code before pulling it in.

Phil

Sep 20, 2010 at 4:51 AM
So basically you put on a different hat and review the changes? ;p

Pull request out.
Coordinator
Sep 20, 2010 at 4:53 AM

No, I leave that job to someone who knows what they’re doing. ;)

Q: What do you call the person that integrates pull requests?

A: I call him “David”

Phil

Sep 20, 2010 at 4:57 AM
FAQ it up! :D
Sep 20, 2010 at 5:45 AM

> Submit the pull request. I think we should only spend our time verifying features that are in the main fork. Drew, do you agree?

Yes, I agree. The flow I expect is: 1) dev'r reviews the pull request, 2) if accepted, integrates changes into the project's repo', and 3) assigns an associated work item as Fixed to me.

Coordinator
Sep 20, 2010 at 3:53 PM

Ack! I can't embed a YouTube video when using HTML markup. It only works for wiki markup. Fail!

Please add this to the list of issues we need voted up: http://codeplex.codeplex.com/workitem/25585

Meanwhile, I'll change the home page back to wiki markup. :(

Coordinator
Oct 3, 2010 at 8:49 PM

Hey all, I updated the Wiki Page where we're tracking the essential changes we want to see happen at CodePlex.com for it to be a viable project host for NuPack. 

http://nupack.codeplex.com/wikipage?title=Support%20the%20Project

Please take a minute to vote these items up. Also, let me know if there's anything we need to add there. Once we go public, we should try to push people to this page and ask them to vote these issues up. A little Hanseltweet ough to give these items a lot of exposure.