Hey,
just wanted to let the avid reader of this mailing list know, that I
applied to become the maintainer of aerc. If Drew agrees to it, I intend
to keep everything as transparent and open as it is right now, and I
intend to reduce the number of open issues, in order to give aerc a new
release after more than 9 months in the hope to make this great mail
client even better. (Especially when it comes to PGP and Docs.)
> On Aug 25, 2021, at 12:28 PM, Moritz Poldrack <ich@moritz-poldrack.de> wrote:> > Hey,> just wanted to let the avid reader of this mailing list know, that I> applied to become the maintainer of aerc. If Drew agrees to it, I intend> to keep everything as transparent and open as it is right now, and I> intend to reduce the number of open issues, in order to give aerc a new> release after more than 9 months in the hope to make this great mail> client even better. (Especially when it comes to PGP and Docs.)
Awesome! Thanks, Moritz!
Connor
>just wanted to let the avid reader of this mailing list know, that I>applied to become the maintainer of aerc. If Drew agrees to it, I intend>to keep everything as transparent and open as it is right now, and I>intend to reduce the number of open issues, in order to give aerc a new>release after more than 9 months in the hope to make this great mail>client even better. (Especially when it comes to PGP and Docs.)
Nice! Hope Drew agrees!
Cheers and thanks for stepping up!
On Wed Aug 25, 2021 at 10:28 AM PDT, Moritz Poldrack wrote:
> Hey,> just wanted to let the avid reader of this mailing list know, that I> applied to become the maintainer of aerc. If Drew agrees to it, I intend> to keep everything as transparent and open as it is right now, and I> intend to reduce the number of open issues, in order to give aerc a new> release after more than 9 months in the hope to make this great mail> client even better. (Especially when it comes to PGP and Docs.)
---
Seán C McCord
ulexus@gmail.com
PGP/GPG: https://keys.openpgp.org/vks/v1/by-fingerprint/D9C871CCDEBD2C7A23D83041798DDA5251824DEA
Great news!
On Wed Aug 25, 2021 at 7:28 PM CEST, Moritz Poldrack wrote:
> Hey,> just wanted to let the avid reader of this mailing list know, that I> applied to become the maintainer of aerc. If Drew agrees to it, I intend> to keep everything as transparent and open as it is right now, and I> intend to reduce the number of open issues, in order to give aerc a new> release after more than 9 months in the hope to make this great mail> client even better. (Especially when it comes to PGP and Docs.)
It'd be great for this project to have a maintainer,
though I guess I don't really know what to expect from you.
Would you consider pushing something to your fork (maybe in a branch)
(https://git.sr.ht/~poldi1405/aerc)
so we'll have a better idea of what current patches you like
or would accept?
In this decentralized development model,
all we really need is for people to say
"I like Moritz' fork best",
and start basing their patches off of that.
First off, thanks to everyone for their support. I hope Drew will share
this sentiment.
> Would you consider pushing something to your fork (maybe in a branch)> (https://git.sr.ht/~poldi1405/aerc)> so we'll have a better idea of what current patches you like> or would accept?
I am currently[¹] working through the patches and comment on
them/forward them to Drew if I think they should be added.
I'll provide feedback right here on this mailing-list, just where the
patches already are. I feel like that is more useful than
cross-referencing my copy of the repo.
> In this decentralized development model, all we really need is for> people to say "I like Moritz' fork best", and start basing their> patches off of that.
To be honest, it was never my intention to make an aerc-Fork, as I
really do not see the need. Forking is – to my knowledge – intended as a
last-resort solution if there are severe disagreements. See: the drama
around Audacity.
[¹]: "currently" means: I started with things like the most recent
libera.chat patch and am working my way backwards. However, due to time
constraints, this will take a while. I think the weekend will see a
sharp increase of activity in that regard.
On Fri Aug 27, 2021 at 8:50 AM CEST, Moritz Poldrack wrote:
> First off, thanks to everyone for their support. I hope Drew will share> this sentiment.
First of all, thanks for stepping up!
I have been very conflicted about making that move myself. As on one
hand, I really want this project to continue and think my go skills
could be sufficient, but on the other hand I totally lack any experience
in maintaining an open source project and I am afraid I don't have the
time right now to learn it on the job. So I am glad you did.
> I'll provide feedback right here on this mailing-list, just where the> patches already are. I feel like that is more useful than> cross-referencing my copy of the repo.
I agree with you. For now at least. And in the light of the above: if I
can be of any help with your work, don't hesitate to ask me directly.
Erik
> I have been very conflicted about making that move myself. As on one> hand, I really want this project to continue and think my go skills> could be sufficient, but on the other hand I totally lack any experience> in maintaining an open source project and I am afraid I don't have the> time right now to learn it on the job. So I am glad you did.
I felt quite similar, but thought you have to start somewhere and it's
better for aerc to have an inexperienced, but willing maintainer, than
none at all.
> I agree with you. For now at least. And in the light of the above: if I> can be of any help with your work, don't hesitate to ask me directly.
Thanks for the offer, and I will do. :)
>> I have been very conflicted about making that move myself. As on one>> hand, I really want this project to continue and think my go skills>> could be sufficient, but on the other hand I totally lack any experience>> in maintaining an open source project and I am afraid I don't have the>> time right now to learn it on the job. So I am glad you did.>>I felt quite similar, but thought you have to start somewhere and it's>better for aerc to have an inexperienced, but willing maintainer, than>none at all.
I think, if you're willing to put the effort and the time to an open
source project being the maintainer (an inexperienced one), some of the
veterans would help if you need it. You just have to ask!
Anyway, this is a bit offtopic. I'm glad someone is stepping up to this,
I will try and help testing things if possible.
Cheers!