Agile frameworks like Scrum generally refer to developers as "team members." The specific nomenclature can vary from framework to framework, though, and is not prescriptive.
Project Management is About Resource Constraints
Project management is a field built around managing constraints. Those constraints may be time, money, skill, or available labor, but all of those things can be defined as "resources." Almost by definition, employees and contractors provide skill and labor resources, but the use of the word to describe the people themselves is an unfortunate by-product of modern business culture.
It could be worse; in some companies, you may not even rise to the level of a "human resource." You could be labeled a "report" or an "asset," both of which are still better than being a "cost center." Count your blessings and move onto something more productive.
Build Alternative Terminology into Organizational Change
So, from a project perspective, you are a resource. However, the shift to agile practices tries to instill a sense of value for people beyond treating them as fungible assets. The Agile Manifesto explicitly values individuals and interactions over processes and tools.
On projects that I manage, I try to differentiate between the resources that people provide and the people themselves. Treating people as people—and as integral members of a team—is certainly important. However, while words sometimes convey ideas about how a company views the people who comprise its workforce, organizational culture is much more than just a bit of neuro-linguistic programming. Improving organizational culture may include changes in nomenclature, but it shouldn't become an end unto itself. That's just tilting at windmills.