heed the wisdom of Charlie Martin, but also have at least a gentleman's agreement between the two of you as to responsibilities and commitments for completion and commercialization.
It's one thing to say "yeah i'll help you write the whizbang.com site", but it's quite another to commit to maintaining it, supporting it financially, marketing it, and making it work as a business
I have worked with distributed teams before, The most important thing you need to have is clarity of your goals, milestones and responsibilities. There are many tools on the net to help you with this project:
Google code < You can use this as your code repository.
Checkout the tools at 37signals.com, they have a few good tools for collaboration and the basic versions are free
You can use crossloop to share your screen to fix things and discuss them.
Also, look into Extreme Programming. Not all the details fit this, but there is a technique that will do you great good: organize the project into small "user stories", which describe one little bit of end-to-end functionality, define an "aceptance test" that tells you when a user story is done, and then work on one user story at a time, or one each.
发布评论
评论（4）
留意查理·马丁的智慧，而且你们两人之间还至少达成一份关于完成和商业化的责任和承诺的君子协议。
说“是的，我会帮助您编写whizbang.com 网站”是一回事，但致力于维护它、为其提供经济支持、对其进行营销并使其作为一项业务运作则是另一回事
heed the wisdom of Charlie Martin, but also have at least a gentleman's agreement between the two of you as to responsibilities and commitments for completion and commercialization.
It's one thing to say "yeah i'll help you write the whizbang.com site", but it's quite another to commit to maintaining it, supporting it financially, marketing it, and making it work as a business
我以前曾与分布式团队合作过，最重要的是你需要明确你的目标、里程碑和职责。 网上有很多工具可以帮助您完成这个项目：
I have worked with distributed teams before, The most important thing you need to have is clarity of your goals, milestones and responsibilities. There are many tools on the net to help you with this project:
尝试收听 Stack Overflow 播客 的早期剧集，深入了解 SO 开发流程。
Try listening to the earlier episodes of the Stack Overflow podcast for insight into the SO dev process.
另外，研究一下极限编程。 并非所有细节都符合这一点，但有一种技术可以对您大有裨益：将项目组织成小的“用户故事”，其中描述了一点点端到端功能，定义了一个“验收测试”来说明当一个用户故事完成后，你就可以一次处理一个用户故事，或者每个用户故事一个。
Also, look into Extreme Programming. Not all the details fit this, but there is a technique that will do you great good: organize the project into small "user stories", which describe one little bit of end-to-end functionality, define an "aceptance test" that tells you when a user story is done, and then work on one user story at a time, or one each.