WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Updates from Birgit Olzem 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. :)

  • Birgit Olzem 11:31 am on October 26, 2013 Permalink | Log in to leave a Comment
    CoachBirgit • de.wordpress.org editor
    Tags: ,   

    Hi,

    I miss many names under translator section on credits page. There are only users listed with validator rights, but no user who helped out to translate.

    Can anyone this confirm?

    Best regards,
    Birgit

     
    • dyrer 12:16 pm on October 26, 2013 Permalink | Log in to Reply

      Thats true, validator takes the compliments ;)

    • Naoko Takano 2:31 am on October 27, 2013 Permalink | Log in to Reply

      I noticed the same thing. Non-validators who have translations approved for 3.7 are not showing up on /wp-admin/credits.php as they used to.

    • Nashwan Doaqan 5:26 am on October 27, 2013 Permalink | Log in to Reply

      Thats true, we need a hot-fix!

    • pixolin 8:58 am on November 6, 2013 Permalink | Log in to Reply

      This is somewhat frustrating.

      You attend a WordCamp. You learn, everybody is invited to contribute. You return home and make your contribution by translating all open terms of a new WordPress version. Then … nothing happens. The new version comes out, everybody is happy, the validators get credited for their kind contribution.

      Not being a validator, you feel overlooked. You don’t get mentioned anywhere. You don’t even know, what parts of your translation made it into the new version (and probably even more important, why some where rejected). You don’t know wether anybody cares about your contribution or not.

      You ask a validator, why it is as it is. She cares and writes a blog post here. Some acknowledge that only validators get credited. And that’s about it. A maintenance release comes out. Again, you don’t get credited. Never mind. Just feel free to contribute.

    • Andrew Nacin 1:04 am on November 22, 2013 Permalink | Log in to Reply

      Hi all. I’m sorry, I didn’t see this until now. This was a bug in the credits API. (It was a typo — “wp/wp/dev” instead of “wp/dev”.) It is now fixed. All installs cache credits data for 24 hours, but after that (or if you have not visited credits.php in the last day) this will be fixed everywhere.

      @pixolin I wrote the credits API originally, and pushed really hard to make sure all contributors got included — large or small, translators or validators, developers or designers. I totally understand your frustration and I’m sorry it took until now for you to be properly recognized.

      • pixolin 12:30 pm on December 5, 2013 Permalink | Log in to Reply

        @nacin I just stumbled upon your answer today. Thank you very much for your kind attention!

        In the meantime I tried my best to contribute to WordPress 3.8’s German translation and must say it’s not only fun but also a great way to spot changes in new versions, which alone is already well worth the effort.

  • Birgit Olzem 8:37 am on October 22, 2013 Permalink | Log in to leave a Comment
    CoachBirgit • de.wordpress.org editor
    Tags: , , , ,   

    Hi @Ze and @nacin,

    I can´t create a RC Build in Rosetta for de_DE to test it.

    My workflow:

    1. add all dependent files into svn at /tags/3.7/dist (liesmich.html & wp-config.php)
    2. commit changes to svn
    3. go to rosetta

    Build a new packet:

    • source: translate.wordpress.org
    • Locale branch: /tags/3.7
    • Project: Development trunk
    • Revision: 25851
    • Version: 3.7-RC1-25851
    • push the button

    I get following error message:

    Fehler beim Kopieren von /tmp/rosettaVtIemt/de_DE/dist/liesmich.html zu /tmp/rosetta4vXl9F/wordpress!

    What can I do to fix this problem?

    Best regards,
    Birgit

     
  • Birgit Olzem 1:02 pm on July 30, 2013 Permalink | Log in to leave a Comment
    CoachBirgit • de.wordpress.org editor
    Tags: , ,   

    Hello,

    how can I find out, who was involved in translation for 3.6.x? In the credits.php I´ll find only Users with validator rights.

    We want to list all involved in our blog, to say many thanks for assistance.

    Thanks for answer and best regards,
    Birgit

     
    • Kevin Kyburz (@swissky) 1:07 pm on July 30, 2013 Permalink | Log in to Reply

      You can see this after Update in the about.php Site.

      • Birgit Olzem 1:16 pm on July 30, 2013 Permalink | Log in to Reply

        Hello Kevin,

        that was right in older versions. Actually in 3.5.x are only users with validator rights listed. In 3.6 RC2 too.

        This is strange, because I don´t want to open every string in GlotPress to look, who was the translator ;-)

        Since opening GlotPress for all wp.org Users, it ist possible to have more than 20 Translators or more.

        Perhaps I am blockhead and couldn´t find the solution in easy way ;-)

    • Andrew Nacin 8:29 pm on July 30, 2013 Permalink | Log in to Reply

      This will be fixed come 3.6 final. I’ll try to get to it today.

    • Xavier Borderie 9:04 am on July 31, 2013 Permalink | Log in to Reply

      On the other hand, we are only a couple of translators fro fr_FR in order to keep it tight, and GP users are listed in the About page even though their strings are marked as “Old” — and are often of poor quality (sometimes even gibberish).

      How can I stop them from being listed? Currently I have to filter strings by username, validate their old strings in order to have them under my own name, then re-upload my .po file in order to override their now-validated strings. And there are some usernames that don’t even seem to have strings… Is there an easier way?

      • Remkus de Vries 9:37 am on July 31, 2013 Permalink | Log in to Reply

        Unless I don’t understand you correct, but what I do in such cases is edit the string and hit the add translation button and that registers it as mine. No uploading necessary.

        • Xavier Borderie 9:50 am on July 31, 2013 Permalink | Log in to Reply

          Yep, that’s what I do: click “Add translation” on strings that aren’t mine.
          Uploading my .po file afterwards turns them back to the previous username.

          I uploaded the file in order to overwrite bad strings that I clicked “Add translation” to without correcting the translation, but it seems that’s not enough.

          And there are still username I can’t find strings for.

          GP can be tricky at times :)

        • Xavier Borderie 12:18 pm on July 31, 2013 Permalink | Log in to Reply

          Still, it baffles me a bit that authors of strings marked as Old (and Rejected also?) are present in the translation credits.

          And I can’t just click “add a translation” on a bad string, so I have to edit all these. Erf.

        • Xavier Borderie 12:26 pm on July 31, 2013 Permalink | Log in to Reply

          OK, further testing gave this: clicking “Add translation”, whether I edit the string or not, does not change anything, as when I search for that username again, the same strings (in their unedited state) get listed.

          There is something fishy in there.

      • Marko Heijnen 6:41 pm on August 5, 2013 Permalink | Log in to Reply

        I will see what I can do to fix this.

  • Birgit Olzem 2:03 pm on December 3, 2012 Permalink | Log in to leave a Comment
    CoachBirgit • de.wordpress.org editor
    Tags:   

    What about “Choose a Featured Image” ? In our dev-system we use WordPress 3.5-RC2-22975 to check the translations. Today I got 2 new strings in GlotPress “Reverse order” and “Set featured image”. But I can´t find the string: “Choose a Featured Image”

     
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