// ravi wrote at 12:24 (EST) on Sunday: > rather than speak in the abstract, why not consider the actual > proposals made that I was referring to
Part of my point in this thread has been that Node.js community need not narrow its options for an organizational home down to just one or two choices immediately. > I differ, perhaps, in my inability to see a problem in the > arrangement, as it exists today As I also pointed out in my original post, how the question came up is not necessarily relevant to considering the question of where Node.js wants its organizational home. I also pointed out that status quo has a strong power in situations like this. Both the upsides and the downsides of having an Open Source and Free Software project housed in a single for-profit entity are pretty apparent. If the upsides outweigh the downsides for this community, then you should stick with it. -- -- bkuhn -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
