Agile project development

One of the new release life-cycles we want to introduce to Transifex is the scrum product/project management.

In Scrum, the product backlog is the single most important list. Backlog is a comprehensive to-do list, with each piece of work that the feature requires.

Despite the naming conventions scrum approach uses (uhm :( ) we really want to build a backlog of features that the community needs/wants and think that would be a valuable addition to Transifex. In order to do this we request from each one of you that has some comment/proposal/idea on how to do things better to present and or introduce it onĀ our user knowledgebase & feedback system.

Hope to hear from you soon :)

5 Responses to “Agile project development”

  1. Dimitris Glezos says:

    Niko, I want a pony.

  2. Martin Geisler says:

    My biggest wish is that you keep Transifex simple: make it a frontend for editing .po files and keep it at that. I always dislike it when a site feel that they must add a messaging system (I use my email for that) or a discussion board (I use mailinglists) or a diary/blog (I use my own blog).

    There are lots of ground to be covered by “only” being a .po editor front-end: in Mercurial, some of our strings are in ReST format. Transifex runs all the text together and destroys the markup. It also shows newlines as “\n” when I would have expected them to be, well, newlines. The same with double-quotes, which are shown as ‘\”‘ instead of just ‘”‘ — as a translator, I shouldn’t have to worry about how Gettext wants the quote to be escaped.

    I mention those things to say that though Transifex is already a very nice system, there are still some core parts that could be improved before you run off and add what I consider to be secondary features.

  3. Steffen Hoffmann says:

    Yeah, like M. Geisler, I feel that not having support for formatting like found in the SVN/Mercurial/Git repos for i.e. some multi-line messages in python scripts is a big drawback. You/we miss the chance for contributions, that could be instantly/easy applied by program maintainers just by feeding it to their repos AS it IS.

    So please (some quick thoughts) * preserve coding language-specific formatting, * provide some basic plausibility checks (highlighting for missing braches, % etc., * assist with per project dictionary to lookup common word already translated somewhere for consistency throughout the whole translation

    Make Transifex the best only translator and just that. Thanks in advance for taking the challenge. Keep it going.

  4. Steffen Hoffmann says:

    BTW, did you recognize, that tool-tips “watch it” and “stop watching it” are applied the wroung way, making it quite irritating, what to do i.e. on the project PO-file lists. Same for icons. I felt like I’d watch all files by default and had to unsubscribe.

  5. Alfred Meyer says:

    There are lots of ground to be covered by “only” being a .po editor front-end: in Mercurial, some of our strings are in ReST format. Transifex runs all the text together and destroys the markup. It also shows newlines as “\n” when I would have expected them to be, well, newlines. The same with double-quotes, which are shown as ‘\”‘ instead of just ‘”‘ — as a translator, I shouldn’t have to worry about how Gettext wants the quote to be escaped. +1