ABC
1
What makes a maker?
One or several of the next
NOTE: I'm mentioning points below because maybe we could track the top monthly of each category, have a committee to assign points and based on that we define the hero of the month.
2
ContributionCommentjun/2024
3
* Core maintainerThis is the people that maintains the core - at this moment just Heng Sin and Carlos can do peer review and push to the repository. One of the main goals is to review contributions and integrate to core.
This is traceable easily by number of commits, but is not easy to determine the work based on size. One line commit can require exhaustive tests, while some big commits (many lines) are isolated enough to require not many tests and code review.
Could be tracked to assign points.
Carlos Ruiz
+IDEMPIERE-2826 Pull the promotions out of the trunk. Leave it as a plugin (#2395)
+IDEMPIERE-2981 Implement JSON Field type - generate model for Test (#2402)
+IDEMPIERE-6176 UUID indexes without constraint (#2397)
+IDEMPIERE-2981 Implement JSON Field type - integrate to release-11 (#2396)
+IDEMPIERE-6169 Performance on AD_ChangeLog with Record_UU (#2393)
+IDEMPIERE-6165 + IDEMPIERE-6168 More problems with jasper setting filename (#2392)
+IDEMPIERE-6168 Found problems with jasper setting filename (#2390)
+IDEMPIERE-6166 PostgreSQL DUAL table with more than one record (#2387)
+IDEMPIERE-6167 BOM Price List must search just for Verified BOMs (#2388)
Heng Sin
+IDEMPIERE-6180 Account Element (Chart of Accounts) tree is shown without icons on the branches (#2404)
+IDEMPIERE-6179 Upgrade to zk10 (#2403)
+IDEMPIERE-5570 Zk: Improve readability of code (#2389)
+IDEMPIERE-6178 Level 3 tab is invisible after collapse and expand of bottom pane (#2401)
+IDEMPIERE-6172 Open from a highlighted window, DateRangePicker popup will auto close when selecting an item in dropdown list (#2400)
+IDEMPIERE-6170 MUser.isEMailValid not implemented correctly (#2391)
+IDEMPIERE-6117 POI: WorkbookFactory.create cannot be used to open XLSX files (#2357)
Hiep LeQuy
+IDEMPIERE-6161:JasperReports encounters issues using encrypted functions due to incompatible dependencies (#2381)
4
* Core contribution (patches, new features)* Core contribution (patches, new features)Diego Ruiz
+IDEMPIERE-6165 - Custom name is not taken when running a core report … (#2386)
Nicolas Micoud
+IDEMPIERE-6164: InitialClientSetup : use static variables for transaction (#2384)
Peter Takacs
+IDEMPIERE-6174 - Create Production from Order process doesn't set BOM Formula (#2399)
5
* Money donorThis is easily traceable.
The easier to track and assign points.
Eugene Barg++
Hideaki Hagiwara++
Chuck Boecking+
Brent Boecking - Pro-Care Medical Center+
Gaurav Sontakke - S-Pieretech+
Olivier LAURENCE - tgi.fr+
Geoffroy Perdu - capbarthodia+
Murilo H Torquato - devcoffee.com.br+
Marco Longo - iDempiere Consulting srl+
Bret Stern - Machine management+
Adam Sawtell - Flamingo logic+
Carlo Morizio - ERP Open Source Italia+
Fernando Saavedra - www.comus.com.ec+
6
* Forum supportThis can be tracked also - a basic metric is the number of answers in forums, but is harder to determine the complexity of the answer, and the accuracy (giving useful answers).
Maybe we could encourage people to go to forums and mark the best answer.
Could be tracked to assign points per good answer (somebody must qualify points based on complexity, communication, etc)
Jesús Castillo+
Carlos Ruiz+
Heng Sin+
Alejandro Jesus Guerra+
Anozi Mada+
Norbert Bede+
Ricardo Santana+
Michal Zilincar+
Luis Amesty+
Saulo Gil+
Vincent Paruh+
Murilo+
Andres Lopez+
7
* Spanish Forum support
8
* Mattermost support
9
* Social media / Project awarenessCreating project awareness - at this moment I'm tracking the official channels (facebook, twitter, youtube). But maybe this could be extended to track for example tags or mentions in social channels. Types of contributions here include:
* Social media content management
* Marketing committee participation
* Content contribution (case studies, testimonials, blog posts etc...)
Official accounts and tags could be tracked to assign points (based on relevance, reachness, communication, etc)

Diego Ruiz
10
* Content contributorPeople contributing content to our website or the wiki - It would be easy to track (somebody must qualify points).Carlos Ruiz
Chuck Boecking
Diego Ruiz
Eugene Barg
11
* Web site maintainerMaintaining the actual home page in WordPress.
Could be tracked by number of content integrated.
Diego Ruiz
12
* Useful and open plugins contributionContributing useful, easy to install plugins. This could be tracked and points assigned based on complexity, usability, etc. Some body needs to qualify.
13
* Sponsoring developers for core or public pluginsCompanies that hire developers to contribute to core or plugins.
This could be tracked, at some point it intersect with the rest of contributions, but maybe for these specific points we sum all the points of developers and give some percentage to the company sponsoring.
Norbert Bede - Cloudempiere
Thomas Bayen - BX Service
14
* Pull request peer reviewPull requests peer review. You can follow this guide ->
https://wiki.idempiere.org/en/Pull_Request_Review
17
* Stackoverflow support
18
* Infrastructure sponsorThis is really easy to track based on the size of the server, if it is maintained, or just donated for us to maintain, etc.
There are some big companies here that we use, they're not specifically sponsoring the project, but open source in general, so I just mention the little companies that specifically sponsor our project.
Dirk Niemeyer - Action 42+
Orlando Curieles - INGEINT+
Murilo Habermann - DevCoffee+
Marco Longo - iDempiere consulting srl+
19
* DocumentationThis can be easy to track in wiki, or some official tool we choose. Some body must assign points based on accuracy, usefulness, etc.
Here we will have also problem with contributions in other languages, we would need to delegate in a local to make us aware if some contributions are worthy.
Carlos Ruiz+
Chuck Boecking+
Frank Wolff+
Heng Sin+
20
* Translations and LocalizationsSome body needs to monitor accuracy, freshness.
Accuracy in different languages can just be done by peer reviewers in the same language.
We can assign points too, but probably requires delegation on a local.
21
* DevOpPeople that maintain the servers and the tools to keep the project running
This can be tracked and points assigned.
22
* Event organizerPeople that organize events, such as conferences meetups, etc.
This can be tracked and points assigned.
23
* Suggesting new featuresPeople that suggest new features that can benefit the majority of the community, those features can be functional, technical, security improvements, UI/UX, etc...
This can be tracked in forums and JIRA
Carlos Ruiz (x1)
Deepak Pansheriya (x1)
Heng Sin Low(x3)
Nicolas Micoud (x2)
Norbert Bede (x1)
24
* Testing and reporting issuesThis is not easy to track, maybe we would need to establish a way for people to report testings and results in JIRA.
Some body needs to qualify quality of tests, accuracy, etc.
Carlos Ruiz (x3)
Diego Ruiz (x2)
DustZeck (x1)
Heng Sin Low(x4)
Nicolas Micoud (x2)
Norbert Bede (x1)
25
* Triage ticketsHelping triaging JIRA tickets