new 2.0 release

Hi,

Valentine's day is coming around the corner, and although I don't see myself as a flying cupid that shoots arrows everywhere, it is a special day to perhaps latch onto for the 2.0 release.

When I look in Github for the new 2.0 milestone, there are still some things to be verified, next to the discussion about the csstidy ticket. I estimate we might be ready to release a quick RC on monday, just to get the scope finalised and do some more non-regression tests. And after that release on tuesday, just in time for Valentine's Day - Because we love our users so much

Would that be a reasonable (if short) timeline?

Topic | Forum


Re: Updates and upgrades for 2.0

I hadn't considered all those points when going for the news module. At the time, Madfish was still actively developing his modules, and his modules were based on the last version of IPF, so it seemed like a given to integrate modules that were built on the most recent best practices.

Topic | Forum


Re: A new milestone has been reached!

That is a momentous occasion! Thank you for putting this into the spotlight.

With the new 2.0 coming around the corner and also some movement in our newly-minted ImpressTNG branch, that number of PRs is certainly going to rise even more!



A new milestone has been reached!

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!


Attach file:



png  impresscms-1000-github-prs-merged.png (27.52 KB)
54__1014063e7daba541ec.png 640X198 px


Re: New designation for our old 2.0 branch

I like it! Maybe we should all take on a character from the series and make that our avatar.



Re: Updates and upgrades for 2.0

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.



New designation for our old 2.0 branch

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



Curious about Github Codespaces

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.



Re: Updates and upgrades for 2.0

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.



Re: Updates and upgrades for 2.0

I think right now is not a good time to merge these two modules. They are written in different code styles - one is IPF another not. Right now these modules are needed just for testing. Faster icms release is better.



Re: Updates and upgrades for 2.0

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.





Re: Improving search efficiency and speed

@skenow did you create a ticket for this search optimisation on github?



Re: Updates and upgrades for 2.0

I think imBlogging and news more or less have the same use case? Perhaps we should prioritise one of the two. We use news on the impresscms site for example, but it should be possible to do a conversion from one to the other.



Re: Updates and upgrades for 2.0

I also know which modules I will prioritize -

  • SimplyWiki
  • imBlogging
  • imTagging
  • Billboard
  • xcGallery

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.



Re: Updates and upgrades for 2.0

Loosely based on what I use normally on my sites:

  • News
  • Menu
  • Sitemap
  • Tools
  • Content
  • Contact Center



Re: Updates and upgrades for 2.0

Just choice 10 modules for now.

All these stats are cool but not possible right now.



Re: Updates and upgrades for 2.0

To be honest, the feature was a bit wonky, so it would need a bit more work to bring back 😁

Might be a good subject for a newsletter.



Re: Updates and upgrades for 2.0

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.



Re: Updates and upgrades for 2.0

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.




 Top