WordPress.org

Making WordPress.org

Opened 13 months ago

Closed 11 months ago

Last modified 6 months ago

#3512 closed defect (maybelater)

Localization support for jobs.wordpress.net

Reported by: claudiosanches Owned by:
Milestone: Priority: normal
Component: Jobs (jobs.wordpress.net) Keywords: close
Cc:

Description (last modified by Otto42)

Currently it's not possible to use jobs.wordpress.net if you do not speak English, this impends companies, developers and users from various places in the world to use the tool.

Jobs.wordpress.net is a wonderful tool that could be better used if it is possible to translate and maybe use sub-domains for each country, as it's are done with the Rosetta sites.

Change History (15)

#1 @Otto42
13 months ago

  • Description modified (diff)
  • Summary changed from Localization support for jobs.wordpress.org to Localization support for jobs.wordpress.net

#2 @anyssa
13 months ago

+1 In many countries there's lack of a easy way to find and advertise WordPress jobs. Being able to translate jobs.wordpress.net would be great!

#3 @AllysonSouza
13 months ago

+1. This is really important for some countries like Brasil, where the language still a barrier to the usage of platforms like WordPress Jobs. Would be great to have it localized and in a way local jobs can be announced in their local language, sub-domains would be perfect for it.

#4 @rafaelfunchal
13 months ago

Good point, Claudio!

It would be great if we could translate that website.

#5 @Rahmohn
13 months ago

Good catch, totally agree.

#6 @marioernestoms
13 months ago

That's an awesome point, Claudio.
In my opinion, this is a strong barrier for who don't have contact with English language.
If we could translate this site to others languages, It'll open a strong channel to centralize job opportunities for other countries and cultures.

For me, that has a Company in Brazil and provide job opportunities in WordPress for designers and front-end Developers freelancers that's a perfect way to announce these opportunities.

Totally agree with this idea.

Last edited 13 months ago by marioernestoms (previous) (diff)

#7 @deblynprado
13 months ago

Certainly would be amazing get jobs.wordpress translated to Portuguese and enable this to all other languages around the world.

As @marioernestoms told, it'll open a really strong channel to publish and discover new opportunities using WordPress.

Great ticket @claudiosanches hopefully we'll be able to translate this soon :D

#8 @locodiego
13 months ago

Great ticket!
+1 Spanish is a very huge market and this could be a great idea to Keep growing in many spanish-speaking countries.

#9 follow-up: @coffee2code
13 months ago

  • Keywords close added

This main issue with this is not having the site actually available in non-English languages, it's that there are not enough people capable of reviewing job submissions in non-English languages. It is for this reason that it is an explicit requirement that all jobs that are submitted must be in English.

All submitted jobs must be reviewed by a moderator prior to appearing on the site. This necessarily entails that a moderator must be able to read the job posting (and any site potentially being referenced). Anyone doing this would have to be inducted onto the jobs team and capable of reviewing job submissions for the criteria set forth by the site. Also, contact form submissions would have to be regularly reviewed for language-specific submissions. This commitment requires reviewing such jobs postings and emails at least every day or two forever going forward.

Basically a jobs team would have to be more formally organized and managed. That and the above would all need to be hashed out before considering the implementation decisions and development changes necessary to get it all going.

To be honest, the Jobs site hasn't been a site with such high aspirations. Bear in mind the site does not run on the wordpress.org infrastructure and does not share user tables or anything else; it is a standalone site.

#10 @SergeyBiryukov
13 months ago

Another thing to consider is that commercial assistance is prohibited on WordPress.org support forums.

While the main support forums can just direct people to jobs.wordpress.net, localized forums don't have a centralized resource the moderators would feel comfortable recommending, but that does not mean there's no demand.

The only workaround for them is to create a special subforum for commercial assistance so that such topics could at least be contained in that section rather than scattered across all other forums, but that's also discouraged. See an example in #WP25679, where the Romanian forums were forced to remove such a section with no alternative.

This situation always seemed unfair to me, but I understand the Jobs team would need to be expanded for being able to handle international submissions before any changes could happen here.

#11 in reply to: ↑ 9 @claudiosanches
13 months ago

Replying to coffee2code:

I understand that there is no enough people, and not being part of wordpress.org... But as @SergeyBiryukov pointed out, we can't provide commercial assistance, we can just recommend some site, like jobs.wordpress.net.
If it's possible to share the same database from wordpress.org we could use the locale managers or create local teams for each country, like we already have with Rosetta sites.

#12 in reply to: ↑ description @djio
13 months ago

+1 High priority! :-)
Thanks @claudiosanches awesome idea!

Replying to claudiosanches:

Jobs.wordpress.net is a wonderful tool that could be better used if it is possible to translate and maybe use sub-domains for each country, as it's are done with the Rosetta sites.

#13 in reply to: ↑ description @djio
13 months ago

(please ignore this)
My browser resent the message twice, I've edited the duplicate messagem

Last edited 13 months ago by djio (previous) (diff)

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


11 months ago

#15 @tellyworth
11 months ago

  • Resolution set to maybelater
  • Status changed from new to closed

It'd be great to find a solution for this, but we just don't have the resources right now. Closing as maybelater pending a solid proposal and resources.

Note: See TracTickets for help on using tickets.