Guild Wars 2 Wiki talk:ArenaNet employee formatting
From Guild Wars 2 Wiki
Jump to navigationJump to search
Feedback 2022/08/24[edit]
- → moved from Talk:Stéphane Lo Presti
According to LinkedIn, his position has changed. --Inculpatus cedo (talk) 06:06, 25 August 2022 (UTC)
- I'm a bit concerned about this trend to look people up on LinkedIn and update their wiki articles with every latest detail (especially for past employees, which I recognize is not the case for Stéphane).
- In my own job I would not enjoy people looking me up and doing this, though I'm sure this varies for other people, especially in more community-facing roles.
- As far as I know User:Stephane Lo Presti is directly active in the wiki, so I figure let's ask: is there an ArenaNet policy about crew pages on the wiki?
- For example, I've seen this comment on User talk:Kvothe/Game credits: "keep red links to incentivise dev page creation? I'd rather not. Rationale: it makes this page look better, and does not invite editors to start looking for information about all employees for safety and privacy reasons.", which I think implies a preference towards not looking so deeply at crew's details and status. Heillos (talk) 07:09, 25 August 2022 (UTC)
- We have the Anet employee article guideline that deals with this issue, and there was a discussion and right after that an overhaul of it, too, few years ago. Cannot link atm tho since on phone. Tl:dr keep the dev pages GW2 (Anet) related only, no unnecessary personal info. ~Sime 09:22, 25 August 2022 (UTC)
- Ahh true, I guess there is Guild Wars 2 Wiki:ArenaNet employee formatting. I get a somewhat mixed message from that. On one hand it states "please do not link to an employee's LinkedIn account.", but on the other hand the copy/paste template implies that information could be sourced from LinkedIn: "<!--Include a comment here on the last day the history was checked. Useful for when employees leave. Example:Last checked August 29, 2017. Source: LinkedIn-->".
- Personally I'd like a bit stronger stance against looking up LinkedIn info etc. The current implication that you can't link it, but an interested editor should go and find it, seems inconsistent.
- Perhaps something along the lines of "only material from official ArenaNet comms" is more appropriate? That is, if a crew member appears in a blog post, interview, or official tweet, that information is relevant and applicable, but not information looked up outside of some certain scope like that. This would lead to more out-of-date crew articles, but imo the gain in privacy is preferred. My reasoning is that, every time a crew member appears in official comms, that has been appropriately vetted and they consented - whereas they may not necessarily consent to people scraping their LinkedIn, even if it's public. Heillos (talk) 21:07, 25 August 2022 (UTC)
- I'm going to add my vote to this idea. Employee articles have always been an edge case for the wiki since they're not about the game. You can easily get down a rabbit hole that's not healthy for you, the wiki, and the employee. --Stephane Lo Presti talk 15:31, 26 August 2022 (UTC)
- I believe that LinkedIn can be a source of relevant information for us regarding roles within ArenaNet. For example, when a person moves from QA to a design role, especially if this person has been public-facing in both roles. What I find most valuable in an employee article is what specific content a developer worked on. Da-Hee Im shared several stories about this in Guild Chat episodes, but we don't have any of that in her article. I feel that what is relevant from LinkedIn usually does not extend to what happened at other companies. For example, we do not need to know where they interned or if they worked at a video rental store in 1998. Currently, I don't feel that we're adhering to the format guide on that. -- Dashface
15:02, 29 August 2022 (UTC)
- I believe that LinkedIn can be a source of relevant information for us regarding roles within ArenaNet. For example, when a person moves from QA to a design role, especially if this person has been public-facing in both roles. What I find most valuable in an employee article is what specific content a developer worked on. Da-Hee Im shared several stories about this in Guild Chat episodes, but we don't have any of that in her article. I feel that what is relevant from LinkedIn usually does not extend to what happened at other companies. For example, we do not need to know where they interned or if they worked at a video rental store in 1998. Currently, I don't feel that we're adhering to the format guide on that. -- Dashface
- I'm going to add my vote to this idea. Employee articles have always been an edge case for the wiki since they're not about the game. You can easily get down a rabbit hole that's not healthy for you, the wiki, and the employee. --Stephane Lo Presti talk 15:31, 26 August 2022 (UTC)
- We have the Anet employee article guideline that deals with this issue, and there was a discussion and right after that an overhaul of it, too, few years ago. Cannot link atm tho since on phone. Tl:dr keep the dev pages GW2 (Anet) related only, no unnecessary personal info. ~Sime 09:22, 25 August 2022 (UTC)
- Technically this is a title change, not a role/position change. Although technically I haven't spent the majority of my time on Guild Wars 2 for quite a few years, but I still work on it from time to time. I don't know what these details bring to this article, but it's of course entirely up to the community to decide. --Stephane Lo Presti talk 15:30, 25 August 2022 (UTC)
