Marketing Committee Meeting 20250516

From iDempiere en

Date: 2025-05-16
Time: 12:00 UTC
Venue: Mattermost - Channel: Marketing
Called by: Marketing Committee


You can find the detailed meeting here:
https://mattermost.idempiere.org/idempiere/pl/meyggxxjpiyembobipwz6e9fah

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

  1. What's new from last week?
    • Development Improvements
      • IDEMPIERE-5150 Support development with IntelliJ
      • IDEMPIERE-6484 Centralized icon css class to org.adempiere.webui.util.Icon Class
      • IDEMPIERE-6521 Create RUN_ImportIdempiereDev.sh
    • Technical Improvements
      • IDEMPIERE-4224 : Decluttering configuration using Attribute on record (#2459)
      • IDEMPIERE-5174 Disable System User
      • IDEMPIERE-6540 Import/Export script doesn't support Oracle running as Docker Container
    • Functional Improvements
      • IDEMPIERE-6028 Override Workflow Responsible at client level
      • IDEMPIERE-6539 [Role Access Update] - Created by / Updated by
    • Bug fixes
      • IDEMPIERE-6543 Error with Post-It on AD_User_Roles (FHCA)
      • IDEMPIERE-6544 Chat window hides thread on Reply
    • Usability Improvements
      • IDEMPIERE-6545 Translation tabs must not allow delete
      • IDEMPIERE-6546 Allow exporting tree definition with 2Pack
      • IDEMPIERE-6549 Add option to Disable "Insufficient Inventory" Popup
    • Community News
      • New Session from Reka Bede: UX/UI Design Principles and AI-Powered Features
      • Final Schedule for the iDempiere conference confrimed: https://conference2025.idempiere.org/schedule
      • New session from Carlos Ruiz: Shaping the Future of iDempiere – Roadmap Review & Community Wishlist
      • New Session from Diego Ruiz: Bringing AI into iDempiere – Faster Development & Conversational Data Access
      • iDempiere Foundation is ready and waiting for documents from the official authorities to start operating
  2. iDempiere results - actions to take
    • Identified problems where the project can take actions
      • Improve Documentation
        • Issue: Many responses cited lack of documentation as the top challenge
        • Actions
          • We are already working on improving that to Chuck
          • One thing we can do, as proposed by Carlos before is to create eginner-friendly, step-by-step onboarding tutorials (written or video).
          • Modernize the User Interface (UI/UX)
        • Issue: Many find the UI non-intuitive or outdated.
        • Actions
          • is constantly working on this topic, we should to keep pushing that
          • Simplify Upgrade & Customization Path
        • Issue: Users and implementers struggle with upgrades due to customizations and plugins.
        • Actions
          • Document better how easy is to update a vanilla iDempiere server
          • Provide clear version migration guides and communicate better plugin and customization guidelines
          • Support Community Contribution
        • Issue: 28% want to contribute but feel blocked by time or lack of clarity.
        • Actions:
          • We can launch initiatives, such as "contribute your first fix" initiative with mentorship by core team members.
          • Recognize contributors with badges for Github or alike.
          • Promote Essential Plugins
        • Observation: Many plugins (REST API, Manufacturing, Validators) are seen as essential. Many people wrote that they should be there when installing
        • Actions:
          • Create a page with a set of "Community Essentials" plugins (?)
          • Include the installattion of those plugins easily in an installer?
          • Create an official plugin maket?
      • We prioritize the list like this:
        • Documentation (we do not take care of this, this is part of the documentation team)
        • Simplify Upgrade & Customization Path -> if we document this better and keep people up to date with good practices, the plugin review process and everything around it will be easier
        • Plugin marketplace
        • Improve UI/UX
        • And as always, "Support Community Contribution" — this is the very reason this committee exists, and we continue to do so consistently.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.