i'm not familiair with forking, but i think the most important thing is: Significant change.
It is stating: significant code improvement, either in features or security and structure.
This is the problem if the forked is in the JED, but what if it disappears (in case JED decides to remove old extensions) what then?. But i did take a look and it seems that the v1.0.1 for Joomla 1.5 is there.
Besides the obvious things like posting an events and listing it, i guess something like this:
- improvement of recurrence
- trashcan option
- RSS and Ical output
- PDF maker
- Content triggering
- Delete confirmation (say that you get a confirm message before you delete something
- image uploader
- gmap integrating
ernst67 wrote: It might sound a bit soon to already start a discussion about a project we don't yet know the name of, but it will take some time to get things lined up.
A discussion is very useful, apart from the name.
I don't want to get annoying, but after surfing through joomla's extension documents, I found one
piece of information
that makes a name like "Joomla Event Manager" very unlikely:
Are there any restrictions how I can name an extension?
Yes, we won't accept any extension names that starts with â€œJoomlaâ€ like â€œJoomlashopâ€ or any names that can create confusion with already existing names.
A solution would be to name it "JEM" (like JCE). "Event Manager" is already in use in the JED. What do you think?
What will the version number be?
With an extension name other than Eventlist, I would either start with a version number 1.0, or a version number that is oriented at the latest currently supported Joomla version, like 2.5.
ernst67 wrote: What is the minimum functionality we will put in the new version? What will the version number be?
My opinion is to concentrate on removing as much bugs as possible to get a good basis for further development. Another requirement in my eyes lies in fulfilling the requirements and standards/conventions of Joomla 2.5. Examples that come to my mind: Supporting the integrated update checker. Or later, using the Bootstrap framework for the future J3.0+ versions.
I think after these steps we can talk about adding (bigger) features. But I don't think adding many features at the start while tidying up the code helps us.