We need more maintainers

[drbacke]

We need more maintainers so that the pr can be processed more quickly. Who would be interested?
Many thanks in advance

[fortrieb]

I'm interested on maintaining this project. Are there any requirements needs to be fulfilled before?

[drbacke]

I would say, since we are still a very small group and I wanted to ask you anyway. Don't make it too complicated. I've signed you up as a maintainer.
As soon as we have a good core group here, I would promote the project more and get more people involved. But it's still too early for that

[michaelosthege]

I'm willing to contribute with code review, refactoring and related maintenance work for while.
However, I can't commit to maintaining long-term because I don't have the perspective of using the system myself in the near future (lacking PV, battery, e-car...).

[drbacke]

Thank you very much. You are a maintainer now😊

[sandboxcode]

I am also really interested to join as a maintainer. I lead the IT department of a small pv and charging infrastructure installer in Hamburg. We are also working on other software tools that are in private development right now, but we plan to open source it in the future.
We do also have multiple sites where the owners (clients and or CEO / CTO) allow my team to play around and test around.
Might be really helpful when we want to apply it in the "wild".
Happy to join!

[BerndCzech]

I would be open for maintaining. However to not loose focus I would step back in favor of having a little more focus at the top.

[drbacke]

You are a maintainer now.

[michaelosthege]

@drbacke can you connect all current maintainers? Maybe in a Discord video call or something like that.

It would help tremendously to have a short exchange about priorities, expectations and aligning acceptance criteria for PRs.

[drbacke]

Sorry I don't have time to organize a meeting, also 1 hour of meeting is very difficult for me.
We should do this asynchronous in some kind of chat or in discussions.
Or it will be in some weeks.

[BerndCzech]

@michaelosthege if you could write a strategy proposal we can refer to and discuss, we might do a first step.

[michaelosthege]

Yes, here we go: #187

[Krulle86]

Next supporter for your project.
What tasks are pending? Is there a wish list?

[fortrieb]

Unit tests are priority number one at the moment, to not adding more bugs while merge PR into the project.

[NormannK]

could the maintainers please push some PR? I do understand some might be complicated/controversial but some are super easy and simple bug fixes.

[drbacke]

You are a maintainer now.

[fracbar]

Someone already working on a container release? If not, i can provide a simple workflow script, which will push nightlies (and release) images to the public docker repo. This can make life easier to install/test it out.

[eckelj]

I am also interested in supporting and maintaining the project. are there active transitions that need support? just arrived here on the project, so excuse this maybe naive question.

[SREbuilt]

My recommendation are to
(1) protect the main branch by

• automated integration tests,
• enable check-in policies in the project config,
• (in the future) have automated deployment tests,
  and not only rely on reviewers for their manual review (having tests will free a bit of their capacity).

The goal of this is that the code in the main branch will always be operational.
As of today (2024-11-10) the main branch contains code that is not executable: Several error types are thrown of categories modules are not found (in akkudoktoreos subfolder), and functional errors like exceptions are happening once server starts.

(2) have a branching strategy in a way that all the development (fixing bugs and implement new features and improvements, like refactoring) to only happen in feature branches (of atomic scope/single purpose and short lifetime).
This will help to keep a better overview of what's happening by whom (to avoid duplicate work).

(3) Setup a Project for this repo:
This will have a simple Kanban board that helps to give an overview and to coordinate the contributions amongst themselves.

@drbacke : in case further maintainers/contributors are welcome, let me be one. I've a Site Reliability Engineering background (with focus on solution observability, increase efficiency (reduce toil and increase automation) ...

[NormannK]

how about you setup a Discord as a start

[SREbuilt]

These are very good suggestions, but the biggest problem at the moment is that I'm very busy and therefore can't do the maintaining well. But I'd be happy to add you as a maintainer, that's very important, that's what's currently lacking the most.

@drbacke :many thanks for onboarding me.
Can you please add a Kanban board to the Project tab? Seems only the repo owner can do that.
Thanks,
Bernhard

[SREbuilt]

regarding Discord:
Who ever has experience with that: go for it. Let's try this medium.
For sure we want to get aligned and make a couple of decisions...
I.e. we could

• converge all existing PR and have them merged into main (to not loose any of the valuable contributions)
• not start any new PR
• do the major refactoring (that would break any existing PRs)
• and then start dev in feature and bug-fixing branches only
• have the main branch protected by check-in policies and automated CI-tests + approvals of 1 or 2 reviewers.

[NormannK]

yes I agree. if you would take a look into my PR's it would be great and most open would be gone.
Id rather not merge them myself.
Id love to have the battery Refactoring in #130 also included after that most stuff should be at least english

[SREbuilt]

@drbacke : to add a Kanban board (sorry for nagging):

• click on your Profile picture (top right) >
• Your Projects >
• New Project >
• Choose the Kanban board.
• then follow steps to link the project in the EOS repository, described here: https://docs.github.com/en/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository

sources:

• https://docs.github.com/en/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
• https://docs.github.com/en/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository

Thanks

[Krulle86]

I've started an almost blank discord-server:
https://discord.com/invite/ZpZEmZvm

Feel free to step in and improve the thing.