Maintainership

[vivien]

This is a simple ticket to track i3blocks-contrib maintainers. It is subject to change.

Actual maintainers (who owns write access):

• @jpleau contributor and Debian package maintainer
• @Nycroth active contributor (code and documentation)
• @kb100 active contributor and reviewer

[vivien]

@kb100 you are quite active, in terms of code and review. Would you like to have merge access to give you more flexibility?

[kb100]

Yes please.

[vivien]

Done and welcome @kb100, thanks ;-)
Remember guys not to merge your own PR and merge (without hurry) clean commits!

[ghost]

Hey @vivien, I haven't really been active lately. Probably best to revoke my commit access. Best of luck with the project everyone! 😄

[vivien]

@kb100, @jpleau, you are the two current maintainers of i3blocks-contrib. Thanks a lot for your good work (I'm looking at @Nycroth too)!

How are things doing so far for you two? Do other active contributors deserve to be granted collaborator? Any specific request I could take care of?

[kb100]

@vivien Thanks for checking in. In the past 6 months or so I have been the only active maintainer. I'm not sure if @jpleau has moved on to bigger and better things. We have had some good contributions and bugfixes from contributors but most contributors just contribute once. If I see someone who is taking a more active role in development, contributing multiple times, writing new blocklets, etc., I will let you know.

[kb100]

The repo does seem to be getting a fair number of views and clones each week, so I wonder if we just need to make it clear that we are still looking for new contributors and blocklets. Perhaps add a "blocklet wanted" list or get that debian i3blocks-contrib package into the official repository.

[vivien]

Having forks of i3blocks-contrib is not a bad idea per-se. People knows that this is the official one if they care about. Since @jpleau maintains the Debian package for i3blocks, I'd like to hear from him about an eventual i3blocks-contrib package. I don't have strong opinion on this, maybe this can simplify people's life. In the meantime, let me know if you have any concern about maintainership! Thank you.

[jpleau]

Hi @vivien @kb100

I'm still watching what goes on here from time to time, but I do not have the time anymore to actively review PRs and merge. (Besides, a lot of the blocklets I see coming in are ones I actually cannot use, ie: openvpn, battery status, wifi, etc. It's hard to test if they work correctly when I don't have the hardware to test them hehe.).

I still want to package i3blocks-contrib for Debian, but we'd need a release for that (or I can use a git commit, but that's not preferable). Reason being I need to have a dependency list (some scripts are written in bash, perl, C, python). I know it was said at one point to have a release of -contrib matching a release of i3blocks, that would be great to have.

Sorry for not being active lately @kb100, you've done a great job here :)

[kb100]

@jpleau Good to see you are still around. You may want to coordinate with @roobre and I in #78. I think he wants to package for arch, and honestly I don't know how to best resolve the issues he mentions (blocks with duplicate names and where should package manager place contrib blocklets).

[nadiamoe]

Hello,

Yes, I plan to create a PKGBUILD for my own convenience, and I plan uploading it to the AUR.

As I've mentioned on #78, there is an issue which conflicting names that should be addressed. @kb100 also proposed some kind of pre-processing and symlinking, but I think renaming the conflicting blockets it's just easier for everyone.

About the release tags, I also think it would be nice to have some kind of release system (weeklies maybe?). However, in arch packages is fairly common to package the last commit directly, so it's not a big problem for me.

[hashworks]

Yes, I plan to create a PKGBUILD for my own convenience, and I plan uploading it to the AUR.

Please note that there is now an AUR package which places the script-dirs in /usr/lib/i3blocks and can be used with:
command=/usr/lib/i3blocks/$BLOCK_NAME/$BLOCK_NAME