WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • Birgit Olzem 6:57 pm on June 18, 2014 Permalink | Log in to leave a Comment
    CoachBirgit • de.wordpress.org editor
    Tags: international sites, o2, , team blog   

    At our first Contributor Day, at WordCamp Hamburg last monday, we have build a team to improve our germanophon community. In this procedere we´ve discussed how we can organize our team.

    One idea is to having an own P2 / O2 Make (public reading), where we can talk in german without flooding the existing make blogs here at w.org. Temporary we try to organize with a trello board. For small tasks it is a fine solution, but for general discussions to confusing.

    Here are some scenarios, that we had extracted:

    • XX.wordpress.org/make
    • make.wordpress.org/XX
    • make.wordpress.org/polyglots/XX
    • make.wordpress.org/community/XX

    What do you think? Is this an idea, you can deal with and use for your community?

    How is your workflow in your community?

    Thanks for your opinion and engagement to make the world a little better ;-)

     
    • daveshine (David Decker) 7:13 pm on June 18, 2014 Permalink | Log in to Reply

      For “speaking URLs” I like “make.wordpress.org/XX” the best, otherwise also “XX.wordpress.org/make” makes sense. The other 2 are already too long in my opinion.

    • Ze Fontainhas 9:20 pm on June 18, 2014 Permalink | Log in to Reply

      xx.wordpress.org/something is what makes sense to me, in which “something” could be either “team”, “discuss” or any variation of that. “make” already has a specific connotation I guess

    • Andrew Nacin 11:19 pm on June 18, 2014 Permalink | Log in to Reply

      I definitely think we can do something on xx.wordpress.org (something I remember discussing previously).

      Alternatively: Let’s say your forums were bbPress 2.0 and everyone had them — would a single “meta” forum area be appropriate and sufficient?

      • Birgit Olzem 10:41 am on June 19, 2014 Permalink | Log in to Reply

        Yes, we´ve talked about this topic at Contributor Day in London last year.

        I think forums are not the best solution. For beeing consistently in organisation and communication for teams, I think we must use the infrastructure P2 / O2 Make-Blogs. New members could better get envolved with this scheme / model. They could orient oneself and easily find the way to communicate and contribute to.

        My thought goes a little bit forward: The user management for access the teams can driven by rosetta sites admins / editor resp. the locale reps. Every user with a .org profile could sign up over contact form.

        The main argument, why I think P2 / O2 is the best way: Notifications. It is much easier to get notified over a make blog, instead a topic in forums. And we can inform better about getting envolved with notes in sidebar and so on.

        All the arguments, why we use – for example – here for polyglots the same way to communicate with each other.

      • Ze Fontainhas 12:07 pm on June 19, 2014 Permalink | Log in to Reply

        Agree with P2/O2 being better than forums, for all the reasons listed by Birgit and David. That said, let’s keep in mind that make/polyglots is the home of translators and not necessarily a country/locale community. Granted, they often overlap, but not always. Speaking exclusively for pt_PT, we’d have no problem moving all discussions about translations to a .org hosted P2/O2, but would have a serious one moving the community debate there; community management requires a lot more than just slapping a P2/O2 on it, and neither does that discussion necessarily belong exclusively on make/polyglots, nor is it mature enough (yet) to implement. Baby steps.

        • Remkus de Vries 12:30 pm on June 19, 2014 Permalink | Log in to Reply

          Agreed 100%.

        • daveshine (David Decker) 1:24 pm on June 19, 2014 Permalink | Log in to Reply

          As of my understanding it’s not about touching the Polyglots base here, it’s just offering the P2/O2 functionality to locale/country communities to power their blogs. Example: de.wordpress.org/blog/ would open as a P2/O2 — that would be awesome!

          This P2 here has to stay, absolutely!

          • Birgit Olzem 1:39 pm on June 19, 2014 Permalink | Log in to Reply

            Sorry for objection @daveshine, don´t replace the standard blog for P2/O2!

            The blog is reserved for announcements and public articles. Not for discussion about organisation and improvements for locale communities.

            I prefer de.wordpress.org/make

            It´s a better consistence and namespacing

            „make“ in context doing great stuff for / with / in the locale community

            Organising contribution to other w.org projects für beginners in native language and so on.

          • Ze Fontainhas 1:43 pm on June 19, 2014 Permalink | Log in to Reply

            That was my point: community-operation-under-org is not defined or discussed, at this point (and keep in mind that “locale” isn’t necessarily “community”, see Belgium, Switzerland (1 community, n languages), or French (1 language, n communities). I am all for discussing it, but just not in this specific context, which has a clear, feasible and objective scope.

        • Torsten Landsiedel 7:44 am on June 20, 2014 Permalink | Log in to Reply

          This is not about having central place to discuss all things community, it is about adopting the idea of the make-blogs to locales. (At least for me.)

          Examples:
          de.wordpress.org/translation -> discussions about German translations
          de.wordpress.org/supporting -> discussions about supporting in the German forums
          de.wordpress.org/core -> discussions about German/translation related core patches
          etc. etc.

          This could be a place to prepare contributions in German and to discuss things which don’t have to flood international P2s.

          We don’t want to use the name “make” or make the make-blogs obsolete. It is just a step between, like we do now (with a wp.com blog) with translation here: http://teamwpde.wordpress.com/

          Or would this be an act of isolation again?

          • Ze Fontainhas 9:35 am on June 20, 2014 Permalink | Log in to Reply

            That looks like a lot of buckets :) It seems to me that discussing things like support and core patches, even if specific to a locale, could benefit all locales by being at the same place and in English, no? This may require some @samuelsidler input, so ping.

            • samuelsidler 4:21 am on July 9, 2014 Permalink

              Yeah, too many buckets. In general those things belong back on the English-speaking sites. Only locale-specific things should be on the locale sites.

          • Birgit Olzem 11:11 am on June 20, 2014 Permalink | Log in to Reply

            @zodiac1978: I think, it don´t need more than one P2. The locale specific topics – in native language for german speaking – could separated with categories and colour tags.

            The big picture, why I want to discuss it here, is to make this native speaking P2s available for all people, who has a w.org login.

            I´ve talked with @samuelsidler some days ago and he meant, that we could use our community site wpde.org for this case.

            But I think, that option is likely an isolated application. We´re endeavored to desestablish this gap.

            @vanillalounge you´ve criticized this same gap in your keynote at #wchh14

            Please correct me, if my thoughts going into a wrong direction.

            I seem to remember, that at #wceu last year it was a topic, to bring the communities together. So I think, using the w.org infrastructure is the best way – because we all use the same CI / CD for the project.

            For us in Germany it is one mouseclick away to setup an own P2, but is this the best way for working together as a big worldwide community?

            The second argument. If we set up an own P2, so who is the Gatekeeper? If we use w.org infrastructure, so there can the respective user for the international sites step into this role, too. It is easier to maintain and respects the trademark policies.

            My 2cts and reflects my personal opinion. ;-)

    • obstschale 10:31 am on June 19, 2014 Permalink | Log in to Reply

      I like xx.wordpress.org/sth. Ze’s arguments are good.

    • daveshine (David Decker) 11:07 am on June 19, 2014 Permalink | Log in to Reply

      I vote for a P2/O2 solution! It’s more native and dynamic and most “insiders” are already used to it because of the Make network on .org.

      Especially easy live comments, feeds and subscriptions make it more easy, and if there’s something more “long form” content to tell about, than the blog functionaly is also an advantage.

      Thanks, Dave :)

    • Caspar 2:41 pm on June 20, 2014 Permalink | Log in to Reply

      @nacin Only because our Trello boards are flooded and we *really* need to create a solution within a matter of days rather than weeks:

      Would xx.wordpress.org/sth be available very soon? Or would it need to be discussed in general?

      We generally wouldn’t have a problem to use a self-hosted P2 for now if it wasn’t for the idea being so overwhelmingly intriguing that people logging into their w.org profiles could just post away in a xx.wordpress.org/sth solution.

      So, is it something we could help making available real soon? Or should we go with a self-hosted for now?

    • Caspar 2:42 pm on June 20, 2014 Permalink | Log in to Reply

      community management requires a lot more than just slapping a P2/O2 on it

      Got that. :)

  • Rasheed Bydousi 3:35 pm on June 18, 2014 Permalink | Log in to leave a Comment
    rasheed • ar.wordpress.org editor
    Tags:   

    I’m trying to rebuild 3.9.1 but it isn’t pulling the right files.
    Here is my settings: http://i.imgur.com/ePrBnIY.png

     
    • Naoko Takano 3:07 am on June 23, 2014 Permalink | Log in to Reply

      For ja package, we used the same settings except for the third one (WordPress Branch) – try tags/3.9.1 there too?

  • booboooz 10:18 pm on June 15, 2014 Permalink | Log in to leave a Comment
    booboooz
    Tags:   

    HI Guys, I am new to wordpress and keen to get involved. Is there anyone working on translating the documentation to Irish?

     
  • Wacław Jacek 4:18 pm on June 15, 2014 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor
    Tags:   

    There’s a massive spike in spam sent to pl.wordpress.org today.

     
  • Aaron Douglas 5:03 pm on June 12, 2014 Permalink | Log in to leave a Comment
    astralbodies
    Tags:   

    WordPress for iOS 4.1.2 was approved and am just waiting for a couple translations on the release notes. If anyone has a bit of time to handle the translations, please update it in GlotPress. I finally got the strings imported properly this time. :)

    https://translate.wordpress.org/projects/ios/dev/release-notes

     
  • mrfroasty 10:54 pm on June 5, 2014 Permalink | Log in to leave a Comment
    mrfroasty • sw.wordpress.org editor  

    Hello,

    Please help me get on the right track, I have translated wordpress some couple years ago and now I want to continue.

    I have lost access to svn.automattic.com/wordpress-i18n/sw/.

    P:S
    **Anything i should be awared of, its been a while since I have done anything related to translation.

    Many thanks

     
    • Remkus de Vries 12:22 pm on June 19, 2014 Permalink | Log in to Reply

      Welcome back :) All translations are now handled via GlotPress and releases are built from the Rosetta sites. Do you know who is in charge of the releases in your language currently?

    • Ze Fontainhas 10:34 am on June 20, 2014 Permalink | Log in to Reply

      You’re still the editor for http://sw.wordpress.org, but the i18n repos have changed url, it’s now i18n.svn.wordpress.org/sw (and you have permissions there already)

    • mrfroasty 9:38 pm on June 20, 2014 Permalink | Log in to Reply

      @Remkus de Vries,

      Thanks I think I am still in charge of the releases.

      @Ze Fontainhas,
      Not so sure but I still can not commit anything in those repos.

      svn info
      Path: .
      Working Copy Root Path: /home/muhsin/public_html/mzalendo.net/wp-content/languages/wpsvn-repo
      URL: http://i18n.svn.wordpress.org/sw
      Repository Root: http://i18n.svn.wordpress.org
      Repository UUID: 2066f16a-a1ef-0310-b9f2-d44eba5528fd
      Revision: 23336
      Node Kind: directory
      Schedule: normal
      Last Changed Author: nacin
      Last Changed Rev: 19149
      Last Changed Date: 2012-02-02 23:33:36 +0100 (Thu, 02 Feb 2012)

      LOGIN:
      Authentication realm: Use your WordPress.org login
      Username: mrfroasty
      Password for ‘mrfroasty':
      svn: E170001: Commit failed (details follow):
      svn: E170001: POST of ‘/!svn/me': authorization failed: Could not authenticate to server: rejected Basic challenge (http://i18n.svn.wordpress.org)

      Many thanks for the support so far and quick responses…..

  • Aaron Douglas 6:27 pm on June 5, 2014 Permalink | Log in to leave a Comment
    astralbodies
    Tags:   

    WordPress for iOS 4.1.1 includes a few new translations and a critical bug fix for a crash happening. If you could reply to this post with your translation I’ll make sure it gets included – thanks!!

    • Fixed a bug causing a crash upon startup in certain scenarios – thanks to everyone who took the time to report it on our forums!
    • Updated translations for Thai, Korean, Japanese, Russian, and Indonesian languages.
    • 4.1.2 will be out soon with a fix for a bug that doesn’t allow sites to connect via Jetpack.

     
  • Daisuke Takahashi 9:03 am on June 5, 2014 Permalink | Log in to leave a Comment
    extendwings
    Tags: , , gsw   

    I found that wrong “Untranslated” count is displayed for “Swiss German (Formal)” in GlotPress.

    https://i.cloudup.com/r-u3d8jIZo.png

    Anyone can recount this (like forum)?

     
  • abuzarsajjad 1:46 pm on June 4, 2014 Permalink | Log in to leave a Comment
    abuzarsajjad
    Tags:   

    Administrator: abuzarsajjad
    Language code: ur
    Language name: Urdu, اردو
    Country code: pk
    Country name: Pakistan, پاکستان

     
  • Wacław Jacek 8:31 pm on June 2, 2014 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor
    Tags:   

    First of all, if I visit the page of a forums thread that has a URL starting with http:// and then click “Admin”, I get redirected to the forums homepage. If I visit the same URL using https instead of http, I get a certificate error. If I tell Chrome to ignore that and then click “Admin”, it works.

    Secondly, we’re experiencing trouble with an user account. A user whom I’ve been in touch with on several occasions during the years keeps getting his account marked as BOZO for some reason (maybe it’s Akismet? I don’t have sufficient access permissions to check.) Could you please investigate into that? I think it’s about the fifth time in, say, two years that I’m cancelling the bozo flag on his account and marking his posts as “not spam”. It’s pretty annoying. By the way, this time I also checked the “Akismet Always Trust” flag on his account page. Maybe this will help?

    Thanks. :)

     
    • samuelsidler 7:21 am on June 3, 2014 Permalink | Log in to Reply

      On the first one, we’re still working through SSL issues. If there are specific ones you have, feel free to file a ticket on meta trac with full steps to reproduce.

  • Maxime 3:23 am on June 2, 2014 Permalink | Log in to leave a Comment
    mbiais
    Tags: , ,   

    Hey Polyglots,

    We’re going to release WordPress Android 2.9 and we need you to translate the release notes here:

    https://translate.wordpress.org/projects/android/dev/release-notes

    and a few new strings, here:

    https://translate.wordpress.org/projects/android/dev

     
  • Naoko Takano 2:25 am on June 2, 2014 Permalink | Log in to leave a Comment
    Nao • ja.wordpress.org editor
    Tags: ,   

    Our forum volunteers noticed that the “hot topic” section of the Japanese forum top page is now filled with spammy tags.

    From bb-admin, I can see a bunch of posts from bozo users with such tags. The posts themselves are no longer appearing, but looks like the hot topic section is ignoring the bozo status.

    The same issue with other local forums, e.g. http://de.forums.wordpress.org and http://nl.forums.wordpress.org

     
  • Cybr 1:21 pm on May 31, 2014 Permalink | Log in to leave a Comment
    Cybr
    Tags: dutch translation comment request je jouw   

    Hi there!

    I’ve been noticing a lot of “basic” Dutch translations over a lot of plugins, which aren’t all that bad. However, when it comes to WordPress, bbPress and BuddyPress itself, I think there’s two things we should change.

    The word I’m talking about is “comment” and “your”.

    Let’s start off with “comment”:
    Almost all translations in Dutch regarding that word are like these:
    commentaar – Comment (noun)
    Reageer – Comment (verb)
    Laat commentaar achter – Leave a comment
    Voeg commentaar toe – Add a comment
    Commentaren – Comments
    Uw commentaar – Your comment

    Now what “commentaar” actually means, is: Critic.
    Which is a negative word in itself. Although, a lot of people perceive it negatively, as do I.

    I would like to change this word to “Reageren”, which is a much kinder word. And it means litteraly “React”.

    The list would go like this:
    Reactie – Comment (noun)
    Reageer – Comment (verb)
    Laat een reactie achter – Leave a comment
    Voeg een reactie toe – Add a comment
    Reacties – Comments
    Uw reactie – Your comment

    I’ve changed it already using a localization plugin on my own website, I’m not sure it gets uploaded to wordpress.org, but I would like this to catch on :).


    The second word, “Your”.
    I see that the Dutch translations for this on bbPress, BuddyPress and WordPress itself is “Je”.
    This actually means: “You” (nonformal) or “U” (formal)

    The correct term for “Your” should be:
    “Jouw” (nonformal) or “Uw” (formal)

    Because it’s possessive :) – Just a note here, the formal form doesn’t have to be a capital letter, that’s only in German.

    Thanks for reading.

     
    • Remkus de Vries 12:19 pm on June 19, 2014 Permalink | Log in to Reply

      Hi there :)

      Thanks for taking the time to bring this up. We’ve decided to not use the formal version a long time ago and we’re not switching back anytime soon. The better place to discuss this however is over here. See you there?

    • Cybr 1:20 pm on June 19, 2014 Permalink | Log in to Reply

      Hi there Remkus,

      It doesn’t really matter if it’s formal or not.
      What I really want to bring up is that it says “Je” instead of “Jouw”.

      Which is comparable with this:
      “You comments”
      “Je reacties”

      As you can see, it’s grammatically incorrect, it should be in the possessive forms:
      “Your comments”
      “Jouw reacties”

      Have a good one :).

    • Remkus de Vries 1:22 pm on June 19, 2014 Permalink | Log in to Reply

      Agreed, but this here is still not the place to discuss this :) Can we please move it over to the aforementioned location?

  • Brad Angelcyk 12:56 am on May 29, 2014 Permalink | Log in to leave a Comment
    irbrad
    Tags: ,   

    I’m not sure if I have access to the release notes page but we are submitted WordPress for iOS 4.1 to the App Store and would like some translation help with the “What’s New” text.

    Improved Reader and Stats performance.
    Backend updates for future features.
    Miscellaneous stability fixes.

    Thanks!

     
    • Naoko Takano 6:17 am on May 29, 2014 Permalink | Log in to Reply

      ja:

      Reader および統計情報画面のパフォーマンスを向上。
      将来の機能向けのバックエンド更新。
      安定性を高めるためのさまざまなバグ修正。

    • Sergey Biryukov 10:55 am on May 29, 2014 Permalink | Log in to Reply

      ru_RU:

      Улучшено быстродействие при просмотре новостей и статистики.
      Обновления в панели управления для будущих функций.
      Различные исправления для улучшения стабильности.

    • Emre Erkan 5:08 pm on May 29, 2014 Permalink | Log in to Reply

      tr_TR

      Okuma ve istatistik performansında gelişmeler.
      Gelecek sürümler için arka planda güncelleme.
      Bir çok ufak düzeltme.

    • Kazama 9:55 am on May 30, 2014 Permalink | Log in to Reply

      th:

      ปรับปรุงการอ่านและประสิทธิภาพสถิติ
      การอัปเดตระบบจัดการสำหรับคุณสมบัติในอนาคต
      แก้ไขความเสถียรของระบบต่าง ๆ

    • Eka Y Saputra 3:10 pm on May 30, 2014 Permalink | Log in to Reply

      id:

      Peningkatan performa Pembaca dan Statistik.
      Pemutakhiran backend untuk fitur-fitur mendatang.
      Berbagai perbaikan untuk stabilitas.

    • drssay 12:50 pm on June 1, 2014 Permalink | Log in to Reply

      ko-KR:
      리더와 통계 화면의 성능을 향상.
      미래의 기능을위한 백엔드 갱신.
      안정성을 높이기위한 다양한 버그 수정.

      • drssay 12:52 pm on June 1, 2014 Permalink | Log in to Reply

        ko-KR: (Updated)

        Reader 및 통계 화면 성능을 향상.
        미래의 기능을위한 백엔드 갱신.
        안정성을 높이기위한 다양한 버그 수정.

        • webix 11:47 am on June 2, 2014 Permalink | Log in to Reply

          리더 및 통계 성능 향상
          앞으로 추가되는 기능들에 대한 백엔드 업데이트(미래에 대하여는 좀 길어지지만, 의역이 좋을 것 같습니다)
          다양한 형태의 안정성 수정 ( 이부분은 직역이 좋을 것 같습니다)

    • Team Vivacity 7:32 am on June 9, 2014 Permalink | Log in to Reply

      hi-HI

      Improved रीडर और आँकड़े प्रदर्शन.
      भविष्य सुविधाओं के लिए बैकएंड अद्यतन.
      विविध स्थिरता को हल करता है.

    • Lorna Timbah 12:34 am on June 11, 2014 Permalink | Log in to Reply

      ms:

      Penambahbaikan prestasi Pembaca (Reader) dan Statistik (Stats).
      Pengemaskinian bahagian belakang bagi ciri-ciri masa depan.
      Lain-lain pembaikan terhadap kestabilan.

  • Samuel Sidler 12:15 pm on May 25, 2014 Permalink | Log in to leave a Comment
    samuelsidler  

    There’s been a lot of things happening recently. Here’s a quick recap:

    Your feedback on all of these posts is incredibly important. If you have thoughts on any of these topics, leave it on the respective post. Thanks for reading!

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel