Foundation Resources: What are they working on?

Hi Rushabh,

Would you please update us about the Foundation Resources. We have 4 developers.

What are they working on?

What have they done so far?

How do we prioritize and allocate projects to the Foundation Resources?

Next time around, can we please include the cost of travel for the Foundation Resources to travel to the Main Conference into the Conference Budget?

I think it is important for them to feel like they are part of an organization, so it would have been great to see Tunde at the conference and I am sure that it would have been great for Tunde to interact with everybody at the conference.




@JayRam thanks for asking!


  1. Non-profit domain (
  2. (bug fixing)
  3. Logistics domain (discussion with @tara_antonius)


  1. General bugfixing (


  1. Bug fixing
  2. Construction domain (with @salman_dawood) Converting Task into Tree Converting Task to a Tree structure by Zlash65 · Pull Request #11117 · frappe/erpnext · GitHub
  3. He has been given a complex construction project data and he is trying to map it to the ERPNext Project module


  1. Working on MWS Connector

Devs please add to your updates.


Please suggest this. Need your help on this one. Right now its pretty random based on what immediate opportunity is available

1 Like

Hi, sorry to jump in,

Some of the Idea:
As for core development: 1st priority
Should concentrate on documentation, bug-fixes, stability and code review.

As for feature development: 2nd priority
As we were discussing about building development road map for ERPNext module ahead, I think we can compile a development wish-list from user in discuss for every module (CRM, Manufacturing, Selling, Purchase, Project, Etc) and start from there…

Best Regards,



Hi, Is there any definition/plan about this construction domain?
I work in a Construction Company and I think I could help with something.
It could be interesting to see if what you are planning to do is what other construction company needs.

  1. Accounts Module

My Priority is general bug fixing. I also work on the Accounts module as I’m actually from an accounting background and I’ve worked on a few new features like Payment Terms (unreleased) and others.

Presently, apart from bug fixing, I have taken up the responsibility to test upgrades from v7 and fix the ever present, annoying issues that make everybody afraid to run bench update. Frappe is done, ERPNext is WIP with ETC tomorrow.


I have proposed a number of accounting module enhancements that I think would make the platform a lot better. I am really glad @tundebabzy is putting some concentration on this core module. I am concerned that focus is being placed on new fun features like construction, logistics, etc “domains” that the core product is losing needed attention. There are a number of features in ERP Accounting and HR that still need a good deal of work to make it easier for these departments to do their work.


Has anyone looked over this thread to see how v9 stacks up with the discussion points?

and also

Just don’t want the new shiny thing to cause the team to lose focus on things we discussed in the past that have not been completed yet.


@rmehta I shared a possible mechanism to sort and address feature requests -

Agree with @James_Robertson about prioritizing Accounting and HR (Hourly Attendances!)

1 Like

It’d be really helpful if you can tel more about whats the kind of data you use revolving around construction. How does the data flow from one task to another…

@Zlash65 @almeidapaulopt I am glad to help in development of construction project management model.

@Zlash65 @salman_dawood : you may like to incorporate ‘Batch Billing’ functionality, which is the critical challange of road construction and residential construction players.

@akurungadam from earthians, I believe is working on it - Collaboration could help making construction domain more comprehensive.


Awesome we have more than one projects going on in Construction, lets nail this one too!

Specially for new (entry-level) devs its better to get them started on something new rather than build on existing functionality. This is because fixing existing functionality is mostly pretty hard which needs at least 6-8 months of development experience.

@almeidapaulopt @dufani1 Good to hear from you guys. I think we should start a dedicated thread for construction management and discuss over there. Construction Management

1 Like

I read the post from Rushabh on the fact that a new functionality is easier for a new resource to develop than enhancing an existing functionality.

That maybe the case, but I think we are all better off if the Foundation Resources struggle with enhancing existing functionality, rather than build new ones.

So, I would like to propose the following:

We only focus on ERPNext, Schools and Healthcare Module. The community can pick up the Not for Profit Module, the Construction Module and the AgriTech Module and develop that further using their own resources, or if they want the Foundation Resource to continue working on those functionalities, they pay for the resource for the duration that it will take the resource to develop these modules. Rushabh can indicate how much that will entail per month.

If the community is not willing to fund it, we park these development at the logical point and redeploy these resources.

I hear @LifeP’s approach and it is a great approach, but I think that for the next 6 months we are better off focusing on the following four areas:

  1. Bug fixing
  2. Better Deliver existing functionality
  3. Enhancements to deliver normal expectations of existing functionality
  4. Localize existing functionality to countries we (Foundation) chooses to invest in (US, Canada, South Africa, UK, Ireland, Australia, New Zealand, Singapore, Hong Kong, UAE, Saudi Arabia, Oman - not that I have anything against other countries, but I’m choosing countries where the business language is English and has huge potential. If I’ve missed out any country, please let me know and I will add on those countries too).

I suggest that we have one resource dedicated to bug fixing. But because bug fixing is a drag and developers would much rather work on sexy enhancements, I suggest that each Foundation Resource focus on Bug Fixing and Bug Fixing only for 1 out of every 4 weeks. I understand that Tunde is the king of bug fixing, but he can help bring the other resources up to speed on bug fixing.

Each of the four Foundation Resources are allocated projects that they work on 3 out of every 4 weeks. The other one week, they are working on bug fixing.

Here are the projects that I think we need to get going on ASAP:

Manufacturing Module
Subcontracting Process
HR Module
Accounting Module
CRM Module
Fee Module and Integration with Accounting for ERPNext Schools
Please add your passion

We assign one Foundation Resource for each activity and two Foundation Members to drive the development on that module.

Tunde is an obvious choice for the Accounting related development.

If there are other important development of existing functionality that we need to address, please add to this list.

Once we come up with the final list of initiatives, we assign developers and Foundation Members and we get going.

After getting inputs on this thread, I suggest we post this as a separate thread, get the inputs of the Foundation Members and then the Community and we execute.

Your inputs please!




What we really need is a person to define work for the devs and help them with specs and feedback. Hence my earlier post for a full time analyst for the foundation.


I agree that improving existing features and bugfix should be the major point for foundation developers. That said, @rmehta is right : you need more experience to work on complex existing features and on bugfixes than when you create new ones.

So one question is : who can supervise new foundation developers ? Only Frappé ? Maybe foundation members employees ?

It could also be an idea to ask current foundations developers to systematically take time to document things they learn (docstrings, maybe doctests, developer documentation…) to help at the same time new community developers and new foundations developers.

Bugfixing, testing and documenting from the foundation can help Frappé team to have more time to made R&D.


My view:
Let them work what they like to do.
I am sure lots of more developer willing to contribute more features in ERPNext and Frappe. They just need some guidance and documentation.

After developer training video the contributions are increased. Foundation need some working plan for increasing community involvement.

I think we are concentring more on ERPNext Product rather than community. We need to build ecosystem which mentioned in following blogpost.


As a developer we also face same issue when we make new feature OR making any generic design from customer specific requirement.
Developer might be good in Coding, but thats not mean every good developer understand business logic and able to design system.


I disagree with this. It’s good to work within your comfort zone. but, foundation as an organization needs to make their resource work on things they like and related areas based on ERPNext-community priorities.

I also feel this is a challenge. Many want to contribute, but the process of pull request & related docs is too much for someone to motivate - Maybe the solution could be 2-3 contributors collaborate and work on one aspect/feature than everyone building their own ship.

Why do you say so? I thought ERPNext itself is the central part of ERPNext community eco-system. Please elaborate on what I might be missing while reading your comments.