Marketing Committee Meeting 20210903

From iDempiere en

Date: 2021-09-03
Time: 12:00 UTC
Venue: Mattermost - Channel: Marketing
Called by: Marketing Committee

You can find the detailed meeting here:

Summary of the day
Meeting led by: Diego
Meeting notes and follow-up actions: Diego
Attendance list: Diego, Carlos, Eugene, Chuck, Heng Sin

  1. What's new from this week?
    • Bug fixes
      • IDEMPIERE-4911 Silent fail when translated column is shorter than original column (FHCA-2888) / fix issue with 2Pack
    • Usability Improvements
      • IDEMPIERE-4927 Header mobile not showing menu and searchbox when username is too long
    • Technical Improvements
      • IDEMPIERE-1575 Increase some columns length AD_ImpFormat_Row.Callout
      • IDEMPIERE-3101 implement OAuth2 for mail (gmail, outlook and other mail system) / add context discovery to AD_AuthorizationCredential.AuthorizationRedirectURL
      • IDEMPIERE-4917 Inject Context Variables from Menu to Info Window
      • IDEMPIERE-4936 Add IsDisplayedGrid on UserDefWindow
      • IDEMPIERE-4939 Implement ability to discover operating system environment variables when parsing context (FHCA-3026)
    • Development Improvements
      • IDEMPIERE-2853 Support for IADTabPanel as factory to add custom Tab …
      • IDEMPIERE-4250 Implement optimistic locking support
      • IDEMPIERE-4940 Allow to set title and defaultvalue for FDialog.askForInputiDempiere name usage petition with @adam-flamingologic
    • -> On other news, since last week we have a new hero chosen by the community: Fernando Saavedra
    • We have a new committer: @dram is taking charge of maintaining the swing client
    • And within the last days I've seen new names in the pull requests, so new code contributors. Which is amazing!
  2. Plugin Test Day - Organization
    • 1 - We ask the community to review each plug-in based on these guidelines:
    • 2 - We set up test servers for that day. @chuckboecking can donate them
    • 3 - We announce publicly the plug-in test day a month before the official date we choose, making a call to plug-in developers to test their plug-ins before that day, so they don't get removed from the list unfairly
    • 4 - On the selected date, we communicate with the participants via Mattermost as done before in the JIRA purging days
    • We set the date after the release candidate freeze to test the plug-ins with the upcoming stable version. In that way we can announce a new version and ideally, the new plug-in page with the supported plug-ins at the same time
    • We work on improving the plug-in page simultanously to be able to announce the release and the plug-in marketplace at the same time.
  3. Donation initiative - follow up
    • So, the text suggested by @chuckboecking together with the image contributed by Vanessa is the way we want to go. We can proceed to develop the ticket with the right permissions.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.