Hello joomleb,

Thank you for your post. I'll try to give a few inputs...

Indeed it is not an easy task for you, neither for us.
As you know, since the beginning of our journey at Octopoos, SEBLOD is our in-house suite of tools that our web agency uses to build high-end websites with Joomla! for our customers. At that time we decided to share SEBLOD core package with the Joomla! community so that you could also benefit from its powerful features and flexibility in order to create websites easily. As of today we have also published more than 100 products (both Free and Paid) for additional capabilities.

We've just released SEBLOD 3.16, and are still releasing new extensions (5 plugins alongside SEBLOD 3.16), and of course the time required to maintain all these extensions (core + more) has increased over the years.

What is complex for us is to find the right balance between community sharing and our enterprise work.

About GitHub, a quick look gives us the following numbers :

• Issues : 119 Open & 196 Closed
• Pull Requests : 28 Open & 179 Closed

As you can see, many are closed, and most of the closed ones have replies and/or have been merged. Which means... YES it helps.
So yes, please keep posting when you find an issue. Also keep trying to test/replicate or confirm others' issues as well.

  Yes, there are more than 100 "issues" opened.
But be careful with the number, those are only "reports". It doesn't mean there are 100 bugs or "real" issues to be fixed.
Sometime it is just about a bad setup or something that is a correct behaviour but could be more obvious...

  And yes, some of the "issues" stay there for years.
But it doesn't mean that it won't be fixed. It just mean that those are not with the highest priority. Maybe it is something important for the person who submit it because of its setup or current need (and that is why we do offer professional support packages for specific and urgent needs), but we try to see the big picture here... based on the report, the number of persons that may be affected by the issue, the time required to fix/implement it (and sometime you may think that it is something small & simple... but it has actually a lot more impact on the code and requires most testing for all dependencies/interactions with other extensions), and of course background compatibility...

  And sometime yes, it just doesn't fit our current timeline, due to internal projects or workload.

We hope that you'll agree that SEBLOD is a unique solution, with a unique design and flexibility, both in and (even) out the Joomla! world.
Our journey has mostly been driven by our projects, and by our team's vision, and I do hope you trust our judgment when we prioritize this or that new feature or implementation.

That being said, nothing is perfect of course, but we do work hard and try to do our best here. We'll try to interact a bit more on GitHub.

About Changelog, we can try to see if we can highlight related Issues/PRs' IDs when it applies.

Regards,
Saba

Hi Saba,

as you know, I'm a Joomler from its fundation and a Sebloder quite from its began. Unfortunately I'm not a "real developer".

So, in first of all, really many thanks for your reply! I understand you.

I'm always very critical, but only and always just constructive and purposeful because I like to collaborate and improve! (I want remember you that I'm been "the first" here to suggest paid subscriptions). This have to be clear. I began this post with:

"I need help to understand how we can help here"

Now, Please,

1 - GitHub: I consider that you have read all the issues / Pull Requests opened there, Am I right ?

2 - Are the issues / Pull Requests up to date ? I mean, if an issue is still open (with or without any comment) we have to consider for sure that is still "unsolved" ?

3 - I'm not a programmer but I'd like to make available my developers to help to solve bugs etc., but without any directions / instructions it is not possible. This is why I'm asking How do I have to do ? More than: discuss here on Forum, open an issue on GitHub, I cannot do noting more. I have to wait your opinions/instructions/confirmations/ before to do anything. Last "Importer issue questions" is a good example...

4 - Changelog suggestions . Please, are a must here to be able to follow and help.

PS I'm sending you an email...

Hi joomleb,

1

Yes.

2

I would say yes (at least for most of them).

3

Let's try to interact a bit more with labels. Now we have 5 "green"  labels with description.
We'll tag "waiting for replication" if we need someone to confirm the issue.
We'll tag "waiting for pull request" if we need someone to work on a fix (i.e when it is not high priority for us).

4

Yes, we'll try.

PS

Thanks, I'll reply next week.

Have a nice weekend

Saba