https://github.com/blog/2256-a-whole-new-github-universe-ann...
* GH Projects exist within a repo, so you can only have Issues from a single repo on a Project.
* A Project contains a subset of issues within a repo - they need to be added manually to the project. This would make it tough to manage a whole project with a Project because you'd have to manually add any issue you created to it.
* You can't filter issues in a Project. Fundamentally a Project is not driven by a query, it's driven by manually adding issues to a Project. So slicing and dicing issues on a Project isn't possible.
I think GH Projects could be used to manage the release of an Epic (e.g. a subset of issues grouped together within a repo). But I think it'd be challenging to manage an entire project with one.
1 - http://blog.codetree.com/articles/the-important-differences-...
I'd want to feel good about the reasons the creator wanted to sell and keep working on it. I think it would be hard to take the product where we wanted without the creator getting frustrated - if s/he had the vision and ability to execute, why did they need to be hired?
That said, I'd be open to it.
> how would you estimate the valuation in that case? would you offer him/her the price to purchase the side project in addition to a salary? or offer a unique compensation package that takes into account of the valuation of the side project?
Hard to say because I think it depends on the situation.
If you're interested in buying a business the people who know how all this stuff works are the private equity people (PE). These guys do this stuff all day long (obviously at much larger scales. If you search you can find a fair amount of info on PE. On a smaller scale there is good info from people researching search funds. Search funds are basically small scale PE. Here's a good starting point: http://www.gsb.stanford.edu/faculty-research/centers-initiat....
Otherwise, it depends what you want to learn. I'm sure a quick search on Amazon would be fruitful.