> Prescript: Quit CC'ing me. I am on the list.
Sure, no problem. It's just that the practice I've observed on this list seems to be to reply to the person directly, and CC the list.
I think you're stretching a bit here. Preventing code forks for the sake of maintenance is plainly naieve. It implies that the source code is or can be available to those that ask. Only those people that are interested are even going to look at it anyway. The majority of end-users wouldn't know the difference, so obfuscating code for their sake is a null op.
No, I don't think I'm stretching here. I'm actually facing this situation. I have an app that the user has full access to because I don't intend to, and cannot restrict access to the box--it's their box. Some of the code is OK for them to touch, but some isn't.
Basically, there are parts of the code base that are specific to them, and parts that are shared across all users. The problem then, is how to allow them to feel free to fiddle with their customized bits, but also stop a fork of the common code.
I could tell them to not touch it, but if they do, it's going to be hard to put Humpty Dumpty back together again.
So it isn't a case of locking away the entire application from them, but stopping them from inadvertently forking critical parts of the code.
...Edmund.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
