New Event Site Project - Which Version to Use

Good day everyone! I am new to this forum, although have been using EL and JEM for some time. My question is for the good people who maintains JEM core code: @jojo12, @ernst67, @Bluefox (JKoelman), @egnarts, @diesl, @hoffi1, @mckillo and others...

I am about to start a new implementation that will require adding several additional features to JEM: multiple user registration on single form, ability to register others with ability to see who registered who and when, extended registration to allow selection of specific start time, staggered starting times for the same event, custom exports, custom mailer, etc..
Some of it may be useful to other JEM users and/or core JEM.

Which version of JEM should I fork? - jemproject/JEM-Project or Egnarts94/JEM-Project or just start with www.joomlaeventmanager.net/forum/jem-2-2-x-for-joomla-2-5-joomla-3-community-support/10484-the-responsive-jem-included-to-jem

I am planning to keep modified JEM on github and to document the added functions as I go along, so you can check and decide if any are useful for core JEM.

Thank you for your good work!

Welcome depebo,
nice that you want to help us developing JEM and bring it forward.

My overrides (Egnarts94/Jem-Project) and both JEM-Responsive-Topics here in the forum are just feature-forks to be included into the original JEM repository.

Hoffi, our main developer is currently working in this branch: github.com/jemproject/JEM-Project/tree/dev23 and as far as I understood he is currently working on integrating my override into JEM (via a much better solution).

Before we add new features to JEM, I think the first task that we should do is to make JEM Joomla 4.x compatible. But you are welcome to take part in the development. Hopefully hoffi responds to your pull-requests in future...

@Egnarts - Thanks for prompt reply.
Happy to offer my help with version 4 migration / redesign / coding, but have no idea even where to begin, to be honest. I have little experience in building J! components from scratch, let alone on version 4. Is the process going to be managed centrally by Hoffi? What about architecture / feature implementation decisions? We are all volunteers with full time jobs, so realistically speaking, are we looking at 6-9 months to get version 4 production ready?
A lot of question, I know. Let me know what do you think.

depebo wrote: @Egnarts - Thanks for prompt reply.
Happy to offer my help with version 4 migration / redesign / coding, but have no idea even where to begin, to be honest. I have little experience in building J! components from scratch, let alone on version 4.

Somewhere on the internet (I did not found anymore) there was a guide about "What hast to be changed between J3 and J4". As far as I know the main problem was the usage of JError, that does not exist anymore in J4. Eventually searching yourself for that developer guide helps where to begin.

depebo wrote: Is the process going to be managed centrally by Hoffi? What about architecture / feature implementation decisions?

Nearly all development is checked and approved by hoffi.

depebo wrote: We are all volunteers with full time jobs, so realistically speaking, are we looking at 6-9 months to get version 4 production ready?

Some years before whe had two releases per year (February/October), but I think we are now at one release per year. So... I don't know.

Although it all sounds pessimistic, I still invite you to develop JEM with us.

Have found this video by Allon Moritz covering fundamental steps in converting from 3 to 4. But it is from JWC17 (over 1 year old). Not much else on version 4. Might be best to look at one of core components (Contacts?) in the latest alpha release to understand the architecture.

As far as I know the main problem was the usage of JError

You are correct: JError, JGrid, JTree, JNode all gone. Here is a link I found on version 4 compatibility, covers deprecated classes/interfaces as well changes in CMS libraries docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_4
If anyone has any more information for version 4 please post here.

Nearly all development is checked and approved by hoffi.

Checking and approving is OK, but someone (collective vote?) needs to decide/manage:

• which version to convert
• namespacing: to use or not?
• what JEM features to take forward
• what functions need to be re-written or re-implemented
• order of development
• resources available
• task assignment

Might give everyone a better idea what we trying to achieve, as well as an indication of the effort and time required. Might also encourage others to contribute once they know what they will be getting in to.