Project still active?

[darth-veitcher]

Hi there. Is the project still active? Last commit was a year ago and the demo link in the repo is broken.

[yaazkal]

I'll really love to see this project working

[itstmyi]

Me too . Any progress these days ?

[silverf0x0]

Same here, it's still looking very promising. I asked of there Is a way to contribute, but no answer. Il lun 11 ott 2021, 00:00 itstmyi ***@***.***> ha scritto:

…

Me too . Any progress these days ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#130 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5DBXA7BLNTLWFG2F5VLIDUGIEJVANCNFSM47LEVOYQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[silverf0x0]

What if we continue this project ourself? My company is very interested, and we could see if we are able to obtain funds from some opensource foundations. I like the idea of having an ERP totally opensource and robust enough to handle big enterprise real time data. Odoo is shifting a bit from its origin, it's becoming more closed and it's still not mature enough for big companies.

Let me know your honest opinion.

[damendieta]

If Odoo is not mature enough for big companies, I really doubt that a fork will.

I love the idea of Hexya and I think that a lot of us are willing to have this project alive again.

@silverf0x0, I think that the best, for now, will be to fork this project on github, work on the fork and make PR to this project to see if with enough help (PR) the project becomes more active, and the ones willing to contribute can do it in the fork that is getting active development, with the time, if the original project doesn't accepts the PR, the fork will become the main project.

Just my opinion.

Thanks.

[silverf0x0]

Of course a fork is not enough. There's a lot of work to do. But I agree that maybe the best thing to do is to fork and open PR against the main branch. Here maybe we need to share a common vision for the product/framework, and could be useful to share a roadmap about the most important next steps to do. Anyway, thank you again. Il giorno lun 11 ott 2021 alle ore 11:00 Daniel M. ***@***.***> ha scritto:

…

If Odoo is not mature enough for big companies, I really doubt that a fork will. I love the idea of Hexya and I think that a lot of us are willing to have this project alive again. @silverf0x0 <https://github.com/silverf0x0>, I think that the best, for now, will be to fork this project on github, work on the fork and make PR to this project to see if with enough help (PR) the project becomes more active, and the ones willing to contribute can do it in the fork that is getting active development, with the time, if the original project doesn't accepts the PR, the fork will become the main project. Just my opinion. Thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#130 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5DBXAWQ5MG2YVGOY4Y23DUGKRTRANCNFSM47LEVOYQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[yaazkal]

I do agree that doing PRs is not enough.
A clear map should be defined or followed if it exist.

[silverf0x0]

@yaazkal That's the point. Maybe we should make a roadmap based on functional areas: sale, crm, mrp, invoice, inventory, etc.

Having a roadmap could help us to split the workload among the interested people. I will think of something about it

[idc77]

Also consider entgo.io to replace the ORM, if better or not, they look similar and one might get better GraphQL support in the future.

I would love to work on something like this but the rent and food at the very least needs to be paid every month.
I'm sure there are more suitable people than me, people who actually work with ERP systems daily.

[dhinojosac]

Hi all, I see that there are many interested in this project; I was reading it, and I love it! We are thinking that we could create a public repository with the fork's project in which we contribute to launching a stable version at least. Does anybody know how to mount the last version of hexya with the addons in the hexya-addons repo?

[hzmsrv]

Also consider entgo.io to replace the ORM, if better or not, they look similar and one might get better GraphQL support in the future.

I would love to work on something like this but the rent and food at the very least needs to be paid every month. I'm sure there are more suitable people than me, people who actually work with ERP systems daily.

I have an ORM project! would you like to maintain together?

[npiganeau]

Hi all of you,

Thanks for your interest. The project is frozen. I have abandoned it two years ago. It was too much work trying to build up the framework and the business modules at the same time. And with Odoo spinning a new version every year, the very little work I managed to do on business modules became outdated much too quickly.
The framework itself has about 95% of Odoo's framework implemented in Go, making it possible to translate business modules from Odoo to Hexya almost line by line from python to Go. But still this is an enormous job.
If anyone is willing to take the job of writing the business modules (again, much can be done by translating Odoo modules), then I am ready on my side to maintain the framework core (and massive improvements could now be done with generics). But the core framework itself without business modules is useless, and doing both is too much work for me alone !

As for the design choices (ORM, etc.) they all have been made with a single goal in mind : being able to translate line by line Odoo modules to Hexya. There are plenty of very good frameworks out there (certainly even better than Hexya's), but none can achieve this goal. See Design Doc for the rationale.

[alvonwong]

Thanks for your job .

[hzmsrv]

@npiganeau I am trying to write an odoo like ORM, if my prototype is closer to your demand my be we could maintain together。 https://github.com/volts-dev/orm

[silverf0x0]

Hi Nicolas, thank you for your work. The project is super interesting. Can you explain about this conversion method from Odoo/python to Hexya/Go? Maybe I can try to help help. Regarding the project, I wouldn't follow Odoo strategy to go for a New version each year. This is a killing for large projects in case of migration. Thank you again and I wish you a nice day. Best, RD Il Lun 6 Giu 2022, 05:44 Unkonow ***@***.***> ha scritto:

…

@npiganeau <https://github.com/npiganeau> I am trying to write an odoo like ORM, if my prototype is closer to your demand my be we could maintain together — Reply to this email directly, view it on GitHub <#130 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5DBXB3ZYGKUJNZXXHQNFDVNVXZFANCNFSM47LEVOYQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[npiganeau]

Hi @silverf0x0 ,

Have a look at https://github.com/hexya-addons and the base module for example.
Each .go file is equivalent to a .py file of Odoo's base module with roughly the same name (here v12).
But the transcoding is mainly manual.
I have also a tool https://github.com/hexya-erp/OTH (Odoo To Hexya) to scaffold the .go files from the .py files, but it's not user friendly and quite tricky to use.

I agree with you that we should not try to roll out a new version each year. One of the reason each Hexya module is a go module is that they can have their own independent versioning and large Hexya projects can leverage the native go versioning system without having to migrate all at once (if ever needed).
My remark was more about the first Hexya version. It will be more difficult for end users to adopt Hexya if its very first version already lags behind Odoo by a few years.

Have a nice day too.

[silverf0x0]

Hi guys, hope that everyone had a nice summer.
Here many things to do (still) :).

Maybe, what we need here is a bit of PR/Marketing staff: I think that if we let the people know about the projects, and many will join, and if we'll be able to make a small community the project could have some life again.

Odoo OCA members are started to be nervous about Odoo SA policies, and even if all of them are aware that it's not possible to go without Odoo in the short term, having a totally open source ERP, will make them more then happy. Maybe, should we try to get their attention?

Also, what if we recall the project as "OpenSource ERP"? we could get more attention with reach result.

What do you think @npiganeau ?
Best,
RD

[j209]

This may be interesting for you guys:

https://empower.sh/docs/architecture/

[SamyRai]

Hi @npiganeau, I think your project is awesome and it needs further development. Would you be interested in handing it over to someone? If you are open to talk about it, let me know how to contact you.