Roadmap

I'll discuss with Bluefox and PM you the details...

hi there,.

We will use Projectfork (we can add tasks, messages in there) but we can also open a topic in the forum, accessible to members of the development etc..

I'm planning to set-up an Github account tonight and post a folder with original files and the conversion project. I don't think will people will mind if we offer the original files for download at the website.

About the versions, for the installer there needs a version number but it can be whatever we decide. But that for later.

My idea is to:
- put Eventlist v1.1 in github (conversion folder)
- put original files also there (seperated by Joomla version)
- In Eventlist v1.02 there were some alterations made in the settings and stripping out functionality. So we can't just copy/past everything but a lot can be used.
- I do like to start with v1.1 and then convert everything to J2.5 format without any hacks.
- when needed use code of the v1.02 package
- that means: translating languagefiles, change JText code to the new format, etc..

When all that is done we do have a v1.1 version very compatible with J1.6+. We then do have a very good base to make adjustments and alterations in the code.

Some alterations that should be integrated:
- changed view of settings (backend)
- new imagepack backend
- category image upload, just like the way it was done with venue & events.
- gmap code

At the moment i do have a converted v1.1 version with:
- a working installer
- it creates the database tables
- frontend works partially
- did translate the language file ( maybe better to just copy/past ah well)
- backend shows up (settings view is different)
- finally know why the calendar was having problems in changing to SEF/common mode
--> these alterations will be posted
--> i did ran into a lot of common error notices and will also post them, in a topic or in PF.
--> there were also some issues that can be resolved (aid), Jfilter clean, etc..

Well, i guess the messages should be posted in ProjectFork next time. So will try that. And about Github: i'm not sure how everythings works but w'll find out . hmm, this project seems to be getting big .

So to be short: tonight the account will be there and then we can start and see how things will develop.


//
Unfortunately my time these 2 weeks will be limited (due to school tests), but am willing to contribute what i can.

I don't know Projectfork, but everything is better than a forum
Does PF offer the same things like Github? E.g. wiki or issue tracker?


@Bluefox: Why the Conversion folder? I think the folder should be removed (I compared the structure with Kunena which is also at github)


I think we should add all the comments/feature requests to PF when it is set up.

@Diesl,.

PF is projectfork and it is about project management.. It seems you can add tasks etc to it. But it does not have the issue-tracker + wiki function.

The conversion folder was there cause i did not know how to name it, but it is now called JEM-DV. It can easily be renamed.

I agree that all the others features have to be there, but did say a few because i did already make the adjustements and it can be easily integrated. But before that we probably should have the converted version as basic.

As said a Repo at github is created and did put the files in there.
it's located at github.com/jemproject folder JEM-DV2.
--> not sure if should have been posted but well..

there are 2 folders at the moment but will remove JEM-DV. It was the v1.1 version that had been altered for a bit. Instead JEM-DV2 will be renamed to that. Sorry for the confusion but it seems github was in maintenance at the moment.

In that folder is the version i've been working on and in the backend the multi-cat is working. I've decided to start with v1.02 and to change it, hmm time to flip a coin . Will save a lot of time, but it possible a few things have been overlooked. I mean that some things can be missing by integrating the v1.1 version.

So we need to check the code and alterations, things have to be cleaned up but it is a start. The clean version of v1.02 was installed and then i uploaded the thing.

- The install & uninstall script has to be altered (v1.1 was better)
- Uninstall should not remove the tables (just to make sure information will not be gone)
- Frontend has to be changed due the cats_relations table
The frontend does not use the multi-cat at this moment, has to be fixed.
- there can be a lot of meshy or leftovers in the script (i was messy :blush: )
- The filter:clean has to be integrated in the models
Did remove it but do know how to fix it
- my view has to be looked at
- mail plugin has to be altered, perhaps we can use the v1.1 and rename it
- recurrence plugin is not needed any more
-[strike] calender view in router .php has to be added.[/strike] (done)
- etc....



//
It's probably better to have a topic or section where we can discuss such things.

Bluefox wrote: it's located at github.com/jemproject folder JEM-DV2.

What does DV mean?

In that folder is the version i've been working on and in the backend the multi-cat is working. I've decided to start with v1.02 and to change it, hmm time to flip a coin .

So I understand you right that you use v1.02 as basis for further work? :blink: Just asking because I thought Ernst and you were favoring v1.1:

In my conversations with Edmond we spoke about which version to use as a starting point to work from.
He was also in favour of using 1.1 as a starting point, implementing the code changes of 1.0.2 to make it Joomla 2.5-installable.

- there can be a lot of meshy or leftovers in the script (i was messy :blush: )

I would strongly suggest that no messy code and hacks is uploaded into the repo. :ohmy:
Better take some time to do it right. Messy code leads to more messy code until nobody understands what some code does without tidying up things which just costs nerves and time.

So, enough negative vibrations Apart from that: Good work