Hi everybody, I've got an Hamletic doubt: to trash or not to trash (my code)?
I'm about to give up ModX on a complex website.
I have done some nice sites with MODx, but in this one (it's a big project) I got tired of patching a CMP I wrote (a Catalog management Custom Manager Page).
Besides, another famous CMS allows doing the same things and more without writing a single line of code...
As things go on, the CMP code I wrote across two years, porting it from Evolution to Revo 2.0 and -not complete- to 2.2, will be trashed.
I must admint that at this moment I'm not so proud of the code, lots of improvements need to be done, but on the other hand it runs without problems in many scenarios.
I won't have time to take care of debugging it, adding features, and even less patching it to follow the API changes again (for all MODx developers out there: it's been a real pain to jump from 0.9.6 to 2.0 API...I know that all APIs change across versions, but I just cannot spend my time reinventing the wheel every time a minor release is released).
I'm asking the opinion of all the people who read this post: what do you suggest to do?
Trash the whole project?
Publish it to a code sharing portal, e.g. GitHub?
Other?
I'm not very keen on publishing as a MODx package, for it's still a beta code which I'll never release.
-
☆ A M B ☆
- 571 Posts
Hi stefanp_safilo,
In my opinion, publishing the source on Github would be the best option :
- it could make some resource to learn from
- someone might even fork, optimize & maintain it
Sad to see you giving you by the way :/
-
☆ A M B ☆
- 894 Posts
Putting it on github would allow the project to live on and evolve with the help of other community members if there's interest for it.
It really depends on what you want to do with the project.
Good luck.
