Over the years, we have used different version control repositories, our current one being GitHub. A recent merge of a pull request has pushed us to 1,000 pull requests that have been merged into our core - https://github.com/ImpressCMS/impresscms/pulls
Thanks for all the efforts that have gone into bringing us this far!
I think it's OK that we have more than one option for a type of module, that's been part of our heritage and what fuels the OSS community. There have always been multiple options for various types of content - news, blogs, galleries, downloads, links, calendars. The same is true in other environments, too - WordPress, Drupal, XOOPS.
The choices are also available in other markets - Microsoft Office (Word, Excel, PowerPoint), or Google Apps (Docs, Sheets, Slides)? Or, LibreOffice? Zoom, Teams, or Google Meet?
For me, it is the least amount of resistance to move forward. News from InstantZero is much more mature, robust, and feature rich than any other news module available. It does things - and I use them - that no other similar module does. The news module we use here is based on IPF and needs another module to create and manage categories (a good thing, actually, from a site management perspective). So does imBlogging - but it uses a different category/tag module. SmartSection had even more features - allowing a preview of an article, but viewing the entire article required another level of authentication, if you chose to do that. I'm not going to wait until one module can do it all. I don't think one module should do it all.
We can't create and support all the variations webmasters will demand, nor should we have to. That is why the marketplace exists.
The key at this point - what do we do with the core, and how does that affect the marketplace? Once I know what to aim for in module compatibility, I know what to do with my sites and the modules they use.
Hi, we arrived at the situation that our new branch number (2.0) was being overtaken by the needs of the legacy version. That is a common pitfall with long-winding releases, quite common actually.
The solution is to not give your next version a number, simple as that That way, your version number cannot be taken by the legacy codebase.
I'm a sci-fi aficionado (sometimes described as 'geek') so I would propose "ImpressTNG" as designation for our next major version. ImpressCMS - The Next Generation (cue Star Trek The Next Generation theme song). What do you think? Other proposals certainly welcome. Let's see what we can come up with
Hi, I'm curious if some of you have experience with Github Codespaces. I tried some similar services some years ago but they were very clunky, more or less a remote desktop via your browser to a virtualised pc.
The user experience wasn't great, and the features were severely limited. I don't know if all this has improved enough for me to look into using Github Codespaces as an alternative to a local IDE.
For some codebases, my laptop (a nice but slightly out-of-date Surface Book 2 with only 8GB of RAM) is starting to get limited by it's RAM, but adding RAM is no option, I'd have to replace the entire laptop. For the price of a new laptop, I could work many hours on Github Codespaces
Curious if you have experience with this.
Totally agree. I've been going through some problematic libraries for PHP 8.0 and I'm updating them one by one. But I don't know if @skenow wants to wait for all those upgrades before launching the new 2.0 release into the wild.
I still need to clean up PR #1397 before it can be merged. That's going to be done right after.
I have sites where I use both, and could probably merge them into a single module with some thought to the navigation changes. One for reporting events and activities, the other more for conversation, ideas, and opinions.
The news module I've been using is the one from InstantZero and it has the ability to manage submit, approve, and viewing based on groups and topic (category). It also has the ability to expire articles and move them to the 'archive', which I like. That's a lot to try and build into another module, along with bringing it up to the latest ImpressCMS, PHP, and MySQL versions. I'm open to it, though.
Yes, I did - https://github.com/ImpressCMS/impresscms/issues/1368
I also know which modules I will prioritize -
I do need to figure out what to do with forms (Formulize), and decide on which news module. A downloads module, a links module, and iForum are also on my list.
It would have been nice if that feature stayed active. I know we used a different server instance for gathering the data.
We could put up a survey and capture information via Google Forms. Download information is always another option to get a sense of what people are trying.
How can we capture our top must have modules?
We had something in that direction several years back, with the heartbeat functionality each time impresscms was installed. Short term, we could look into a similar system that sends the modules and the versions once every month with a autotask. Setting up the receiving end will be the hardest (Google Docs perhaps?)
On the longer term, we can look at the installation statistics from packagist when our modules are installed using composer.
I agree - progress in the core cannot and should not be held back by the lack of module development. And the core should not get so far ahead that no one can follow.
What we do not have is a good sense of what modules are being used, other than what we are using ourselves. Some have alternatives that could be used in place of the module selected. In those situations, when the alternative is compliant with the core and the underlying architecture, we proceed. In cases where there are limited options and the module is highly used, we need to work together to improve the core and the module.
What I see as the outcome of this next release is a way to gauge what modules are active and will be updated. We will be better off as a community when we all have a path forward together.
How can we capture our top must have modules?
You're correct there @Mekdrop. And that is the difficulty : we have no idea what situation most of our users are in. I think Skenow is one of the user with most active sites a the moment, and I know of a few users in Germany that are awaiting newer PHP support because of the shutdown of PHP 7.4 by hosting companies there (they try to be up-to-date).
But other than that, it's a big unknown.
I'm trying to get htmlpurifier 4.15.0 standalone updated but Git is giving me some dificulties with unchanged files that it keeps marking as changed. And I'm still waiting for the PRs for 1.5.x to be approved in order to be able to continue.