Copy Trans will no longer run by default
I look forward to seeing your infra ticket as you drive this to completion. 3
What kind of update cadence should be expected? How much notice? Who is coordinating this relative to the rest of the project’s schedule?
Who is coordinating this relative to the rest of the project’s schedule
--On Wed, May 23, 2018 at 2:28 AM Alex Eng <aeng@redhat.com> wrote:Can you provide details on the changes translators should see in this version?As this is a huge upgrade since 3.9.6, it would be better to refer to our release notes on all the Jira from 3.9.6 onwards.This is a massive list. That speaks to both the productivity of the team and the length of time without updates.Can you summarize this so that we get a clear easy to follow guide for what changed for each role? (Translator, coordinator, consumers, etc.)I feel like asking everyone to read this and digest it will mean that a lot of people miss things as they skim to get through it. Also, because the list is so large, they’ll miss things because the Jira descriptions don’t initially lead them to believe the change is applicable to them.I’m concerned, as a content provider who pushes and pulls to Zanata that there are more changes like “Copy Trans will no longer run by default.“ that I’ve missed. This is where an update targeting me would be helpful.I wouldn’t make this request with every release, but right now you and the team are in the best position to know what you did.Can you provide updates on new features and options that are available? Is fedmsg integration working now?The main missing feature requested from the community was the webhook integration and it is now is available and ready to integrate with fedmsg.We will need to configure the projects to start feeding the message. Happy to get in contact with the infra team to get this rolling.I look forward to seeing your infra ticket as you drive this to completion.Another feature worth mentioning is the new and improved editor which is almost out of the alpha version.This is a great place where having you and the team go into detail will encourage he kind of real-world testing you need to get this feature released.As mentioned, with the new setup, we can now release in more frequent as any new feature is being implemented.What kind of update cadence should be expected? How much notice? Who is coordinating this relative to the rest of the project’s schedule?Regards,bexWe need to take advantage of this and future updates or else this work was just maintenance :)Agreed.On Tue, May 22, 2018 at 4:39 PM, Brian (bex) Exelbierd <bexelbie@redhat.com> wrote:On Tue, May 22, 2018 at 12:26 AM, Alex Eng <aeng@redhat.com> wrote:Hi,After a long process and battling with infrastructure for hosting Zanata, I'm glad to announce that fedora.zanata.org is now running on version 4.4.5. I understand this has been a long delay and would like to apologize for any inconvenience caused as a result it.With this new setup, we are now able to provide the latest fixes and release of Zanata more frequently to Fedora community. We are looking forward to more collaboration to improve toward localization effort.This is great news. I know how much of a struggle this has been.Can you provide details on the changes translators should see in this version? Can you provide updates on new features and options that are available? Is fedmsg integration working now?We need to take advantage of this and future updates or else this work was just maintenance :)regards,bexPlease let me know if you have any questions.Regards,Alex EngZanata Platform
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/trans@lists. fedoraproject.org/message/ 2IXMJMNWPTZTS62RNQRMVJLGWRNB2R FA/
--Brian (bex) Exelbierd | bexelbie@redhat.com | bex@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines ______________________________List Archives: https://lists.fedoraproject.org/archives/list/trans@lists. fedoraproject.org/message/ UVI5TYOJMUDR2TMZBCHULJYB3S6GPY FP/
--ALEX ENG
ASSOCIATE MANAGER
globalization TOOLING, CUSTOMER PLATFORM
193 North Quay, Brisbane City QLD 4000
alex.eng@redhat.com M: 0423353457 IM: aeng
_________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/trans@lists. fedoraproject.org/message/ W4EXVRADW3JGDJ6RZQZI25GRNNPKIW M5/
Brian (bex) Exelbierd | bexelbie@redhat.com | bex@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/trans@lists. fedoraproject.org/message/ RFTSRCV2RMWFKQSGV23UT45VY7WZVE WR/
ALEX ENG
ASSOCIATE MANAGER
globalization TOOLING, CUSTOMER PLATFORM
193 North Quay, Brisbane City QLD 4000
alex.eng@redhat.com M: 0423353457 IM: aeng