It's an extremely contentious issue whether "user" is a bad word or not. If you want to maintain any clarity I would strongly advise against calling all people in all situations 'people.' You can't get any less specific and unhelpful than that. As long as there is a distinction between people that user or have access to your service and people in general (there always will be) it makes more sense to use a more descriptive word.
However, I'm not sure /user/
is required in your URL structure, it seems like an unnecessary subdirectory, at least from the ahem user's point of view. Note that Twitter, Google +, Youtube and many other popular profile/user content based sites just use domain.com/bobsmith
or bobsmith.domain.com
, this is most applicable when the user has their own little "page" or section on the site however, and if this is just an account/profile page it wouldn't be as applicable.
If it's more like an account management URL you could consider domain.com/account/bobsmith
but if it's a profile the large majority of sites still use domain.com/user/bobsmith,
including this one. People know what user means and they'll be more familiar with the term in this context than any term you make up to try and be touchy-feely. Unless you have good reason to believe your users feel insulted, uneasy or confused each time they read the word "user" I would stick to semantic convention.