Summary of ERPNext Foundation Meeting on 21st September, 2017


Here is the summary on the ERPNext foundation meeting.

ERPNext Community Meetups

In September, two community meetups were conducted. The first meetup was organized by the ERPNext Bangalore Chapter. Rushabh flew to Bangalore to conduct a developer workshop and guided community on how to make most of the eco-system and build a revenue model out of it. The domain on Restaurant/Hospitatily was an instance fruit of this meetup.

The second meetup was organized by Thomas Lie @tlie in Jakarta, Indonesia. It was another successful meetup where members shared their ERPNext implementation experience. To check pictures and videos of Jakarta meetup, please check the following link.

Python 3 Compitability

At Frappe, migrating from Python 2 to Python 3 is in full swing. We expect to completely migrate to Python 3 in the near future (2 months?).


In yesterday’s meetup, we heard from @max_morais_dmm, one of the active and earliest community members. He raised an interesting question.

If you are customizing ERPNext, how to design it to ensure it gets merged into the core ERPNext repository?

First step in this direction would be to create a Github Issue for the feature. With the community’s suggestion, you can design feature in a generic way, so that larger user base can benefit from it.

Secondly, sending a pull request is also another medium to getting technical consultation, and to make a robust feature contribution. For an example, check discussion on the pull request made by @revant_one which is about contributing new feature.

Missing Translation

While using ERPNext, if you find any term which is not properly translated in your native language, please create a Github Issue for it. Also tag it as a Bug and Locatization, so that we (the community :)) can filter and address all the translation issues at once.

Thanks and regards,


@umair We have made some small customizations which could be contributed back so could you please standardize a process like so

  1. Create GitHub issue with use case
  2. Mockups


This would be very helpful.



@jai_kejriwal Awesome! Best to start with a pull request