Calendar?

[Liviu Lalescu]

Yeah, I took it wrong. So your 150 FET days is what basically makes a ~6 months calendar. Your week is a unit composed of 5 or 7 days. I brought up a concept of a week unit composed of 35 days (which is not really a week).  In other words things are repeated every 35 days in my concept. In your concept things are repeated every 5 or 7 days. Nevermind if I still don't put it clear.

As I get it, you generaly propose to approach the problem with a single week rather than with a calendar with varying weeks.

We can modify the FET sources to have as many days as needed in the FET "week". You can even have 366 days per "FET week". And consider for yourself that the FET days 1, 1+7=8, 1+7+7=15, etc., are Monday (Mo1,Mo2,Mo3), 2, 2+7=9, 2+7+7=16, etc. are Tuesday (Tu1,Tu2,Tu3), and so on.

We (me and some users) managed to make this work, as in the custom GEA version (that user, Anthony Siaudeau, only needed 216 days per "FET week", considering that he had 6 real days per real week and 36 real weeks per real year). And the activities will kind of repeat over these real weeks, if they are not missing in a certain week, in which case in that place there can be another activity. But the constraints are problematic. Consider max gaps per week, which in FET is considered per "FET week", but the user wants it for the real week. And other constraints (teachers min days per real week, min hours per day of a specified real week, and maybe other situations). For these constraints, a good implementation is very complicated. I did not make it until now, for GEA we made some hacks.

It is much easier and better for a single real week = a FET week. But if really needed, we can try also the GEA-Anthony-Siaudeau version.

[mimooh]

I have no experience in GitHub. I have no experience in collaborating with a SVN or repository stuff. I prefer to collaborate with Volker by email (we exchange code and use KDiff3 to compare and make sure everything is OK). I also looked at rodolforg's code from https://bitbucket.org/rodolforg/fet/ and took some ideas and also received some code from a few other users. But I do not have the capabilities to take care of a repository in which many users make code changes and read and approve each line of code. I prefer to concentrate on the algorithm, and willing to help other people develop their interface or use the internals of FET.

Give a repository a try. Well, git is an overkill. It is really meant to develop complex projects like linux kernel where it shines, no doubt about it. But for a 2 developers project git may bring more complexity than comfort. So I use subversion to access github. Manual merging of patches, however automated you have it, is still more work than having Volker and you commiting to the common repo. Repo has a history, which sometimes comes useful. And there is really nothing hard in starting the repo and using basically 1 command to get the changes and 1 command to commit the changes. Also people can have an insight to the progress of your work.

On the other hand, I feel very much similar as you to someone commiting to my repo. I trust myself more. I am minimalistic and would be against adding too many ideas/features. I would be afraid someone will break something in the core. And this pressure to inspect someone's code proposals... Perhaps it's better for us all than only 2 of you make FET -- it serves the stability of the code. So maybe a private repo would be a way to go for you.

[mimooh]

We can modify the FET sources to have as many days as needed in the FET "week". You can even have 366 days per "FET week". And consider for yourself that the FET days 1, 1+7=8, 1+7+7=15, etc., are Monday (Mo1,Mo2,Mo3), 2, 2+7=9, 2+7+7=16, etc. are Tuesday (Tu1,Tu2,Tu3), and so on.

It is much easier and better for a single real week = a FET week. But if really needed, we can try also the GEA-Anthony-Siaudeau version.

It's not at all that I need it. Just wanted to get the concepts better to use FET better. I love the 7 days weeks

[Liviu Lalescu]

Give a repository a try. Well, git is an overkill. It is really meant to develop complex projects like linux kernel where it shines, no doubt about it. But for a 2 developers project git may bring more complexity than comfort. So I use subversion to access github. Manual merging of patches, however automated you have it, is still more work than having Volker and you commiting to the common repo. Repo has a history, which sometimes comes useful. And there is really nothing hard in starting the repo and using basically 1 command to get the changes and 1 command to commit the changes. Also people can have an insight to the progress of your work.

On the other hand, I feel very much similar as you to someone commiting to my repo. I trust myself more. I am minimalistic and would be against adding too many ideas/features. I would be afraid someone will break something in the core. And this pressure to inspect someone's code proposals... Perhaps it's better for us all than only 2 of you make FET -- it serves the stability of the code. So maybe a private repo would be a way to go for you.

Thank you for your tips! I'll think of them.

[Liviu Lalescu]

We can modify the FET sources to have as many days as needed in the FET "week". You can even have 366 days per "FET week". And consider for yourself that the FET days 1, 1+7=8, 1+7+7=15, etc., are Monday (Mo1,Mo2,Mo3), 2, 2+7=9, 2+7+7=16, etc. are Tuesday (Tu1,Tu2,Tu3), and so on.

It is much easier and better for a single real week = a FET week. But if really needed, we can try also the GEA-Anthony-Siaudeau version.

It's not at all that I need it. Just wanted to get the concepts better to use FET better. I love the 7 days weeks

Great! Me too