Hmm.
Maybe you could do a copy-on-write approach to the site's data. When you forked the source,
your copy of the source would also get a "virtual fork" of the site's data that would just use
the site's original data until you changed something, then the change would stay local to the
version that was visible to your fork of the software.
I agree with smurf that the idea of letting people fork the software but use it to modify the
site's data directly is unmanageably permissive. Linus doesn't let you directly modify his
tree...
Posted Nov 29, 2007 19:56 UTC (Thu) by smurf (subscriber, #17840)
[Link]
Copy-on-write sounds like a good idea, except that (a) you'd need database support for it, (b)
you still have the "anybody could read everybody's personal data and crack their passwords"
problem.
Freeing web services with Forkolator
Posted Nov 30, 2007 1:33 UTC (Fri) by sepreece (subscriber, #19270)
[Link]
Sure - I was assuming access controls would still be in place for private data and only
talking about an approach to allowing software forks to work on communal sites.