zlacker

Features, yes. Are those features directly connected to those clients' work, or is it a more general feature that has to do with the execution of the service?

I will agree that it's dubious that that nuance is reflected in the rulings on the Masterpiece case. I'm trying to follow the same lines set there, though, in my argumentation.

>>Fellsh+(OP)
> Are those features directly connected to those clients' work

How can they not be?

>>joshua+e1
Let me rephrase to see if it answers your question:

Would the added features be useful in another context? Would they be useful regardless of the type of work being done? Are they merely enhancements of the platform, or are they specifically tailored to the client's domain?

>>Fellsh+j7
FWIW, in my work I've seen both. But I'm sort of asking things at a higher level. If a client is asking you to prioritize a generic enhancement over others, they are presumably doing so because they believe that generic enhancement will have the greatest value to their work.

So if ICE asks github to prioritize better native CI support for Windows, or something, they're doing it because it is of maximum benefit to ICE.

>>joshua+ok
It is still debatable how much this has to do with the matter at hand. It is completely possible that github only utility is to process applications faster so that people will stay detained for shorter times. Or that it serves a completely unrelated purpose that has no influence on the issue.