Marketing Committee Meeting 20230303

Date: 2023-03-03
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/8y8ws1c6xtfdiqj4fp97ew3e7h

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

What's new from last two weeks?
- Bug fixes
  - IDEMPIERE-5093 Scheduler cron pattern scheduling is always using server time zone - fix Oracle scripts
  - IDEMPIERE-5494 [WLocationEditor] - Enable Zoom - fix NPE
  - IDEMPIERE-5589 Drill Assistant throws Mandatory Exception when the Key Parameter is Mandatory
  - IDEMPIERE-5596 Advance Find: List of Tab is wrong for Product > Price
  - IDEMPIERE-5597 2pack updating root level menu items failling.
- Usability Improvements
  - IDEMPIERE-5470 Date Range Fieldtype (Reference List)
  - IDEMPIERE-5563 Font Icons not implemented on HTML Report column menu
  - IDEMPIERE-5574 Drop Ship BPartner must have opposite IsSOTrx logic on Info Window
  - IDEMPIERE-5585 Drill Assistant image not shown using theme with images
  - IDEMPIERE-5593 Drill Rule: Do not render Drill Rules for the same Report
- Development Improvements
  - IDEMPIERE-5570 Zk: Improve readability of code
  - IDEMPIERE-5581 Dialog.askForInput : allow Integer
- Technical Improvements
  - IDEMPIERE-5586 Implement ID independent migration script
- Functional Improvements
  - IDEMPIERE-5592 Add C_Calendar_ID to Period Control Management
Documenting how to host a conference
- We will create a wiki with the identifying steps to ease the task of hosting a conference in the future.
Conference 2023 - Review, results and what's next
- From the Plugin vs Core discussion (What should go in Core and what should be a plugin):
  - Improve the communication process -> People don't know where to ask and how to have these discussions
  - Define and communicate a clear process to propose things for the core -> The leaders might have an idea of how it works. They mentioned @nmicoud as an example of what to do. But the community seem to have no idea about it.
  - Have functional leaders to review proposed solutions. -> Many requests get lost or rejected because the burden of reviewing them on the core committers is too big. If we had functional leaders for each area, f.i Steven for accounting, Norbert for UX. They could review the proposed solutions and smooth the path to land in the core.
  - Give more visibility to plug-ins -> Many people ask for a better "Marketplace", many didn't even know where they could find the existing plug-ins
- From the security Discussion:
  - Create a security hall of fame for white hackers who report vulnerability issues -> This will make them contribute more their findings because they get recognized
- From the documentation discussion:
  - @ralexsander proposed to use ReadTheDocs for developers documentation to motivate developers to contribute -> This is already being discussed in the docuentation channel
  - A documentation team was formed with the following volunteers: @pedrorozo, @frankwol, @chuckboecking, @henrym, @gauravsontakkke, @dpansheriya
  - We agreed that the marketing team will collaborate and support the documentation team, whenever they need it
- Various from different moments:
  - Steven proposed to contribute an implementers documentation (minimal steps to implement iDempiere, best practices, what to have in mind, common mistakes, etc) -> He wants our help to make it better and usable for a wider audience.
  - We need to define image trademark guidelines (how to use official images taken during conference and so on)
  - Chuck communicated the message of people who live from iDempiere donating an equivalent of 100 USD per month -> We need to communicate this more
  - People ask for case studies and showcases but somehow do not provide them to the project -> We need to better communicate this as well
  - So, the idea is to have this list as a base for the upcoming meetings. My proposal is to focus on the points mentioned here, improving and addressing them this year