Thread: Commitfest manager 2020-11
Hi all, Admittedly quite ahead of time, I would like to volunteer as Commitfest manager for 2020-11. If the role is not filled and there are no objections, I can reach out again in October for confirmation. //Georgios
On 24.08.2020 16:08, gkokolatos@pm.me wrote: > Hi all, > > Admittedly quite ahead of time, I would like to volunteer as Commitfest manager for 2020-11. > > If the role is not filled and there are no objections, I can reach out again in October for confirmation. > > //Georgios Wow, that was well in advance) I am willing to assist if you need any help. I was looking for this message, to find out who is the current CFM. Apparently, the November commitfest is not in progress yet. Still, I have a question. Should we also maintain statuses of the patches in the "Open" commitfest? 21 patches were already committed during this CF, which shows that even "open" CF is quite active. I've updated a few patches, that were sent by my colleagues. If there are no objections, I can do that for other entries too. On the other hand, I noticed a lot of stall threads, that weren't updated in months. Some of them seem to pass several CFs without any activity at all. I believe that it is wrong for many reasons, the major of which IMHO is a frustration of the authors. Can we come up with something to impove this situation? P.S. I have a few more ideas about the CF management. I suppose, that they are usually being discussed at pgcon meetings, but those won't happen anytime soon. Is there a special place for such discussions, or I may continue this thread? -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Anastasia Lubennikova <a.lubennikova@postgrespro.ru> writes:
> I was looking for this message, to find out who is the current CFM.
> Apparently, the November commitfest is not in progress yet.
Nope, nor have we officially appointed a CFM for it yet. We're seldom
organized enough to do that much in advance of the CF's start.
> Still, I have a question. Should we also maintain statuses of the
> patches in the "Open" commitfest?
Yes, absolutely, if you notice something out-of-date there, go ahead
and fix it. If nothing else, you'll save the eventual CFM some time.
> On the other hand, I noticed a lot of stall threads, that weren't
> updated in months. Some of them seem to pass several CFs without any
> activity at all. I believe that it is wrong for many reasons, the major
> of which IMHO is a frustration of the authors. Can we come up with
> something to impove this situation?
Yeah, that's a perennial problem. Part of the issue is just a shortage
of people --- there are always more patches than we can review and
commit in one month. IMO, another cause is that we have a hard time
saying "no". If a particular patch isn't too well liked, we tend to
just let it slide to the next CF rather than making the uncomfortable
decision to reject it. If you've got thoughts about that, or any other
ways to improve the process, for sure speak up.
> P.S. I have a few more ideas about the CF management. I suppose, that
> they are usually being discussed at pgcon meetings, but those won't
> happen anytime soon. Is there a special place for such discussions, or I
> may continue this thread?
This thread seems like an OK place for the discussion. As you say,
there are not likely to be any in-person meetings for awhile :-(
regards, tom lane
On 16.10.2020 21:57, Tom Lane wrote: > Anastasia Lubennikova <a.lubennikova@postgrespro.ru> writes: >> On the other hand, I noticed a lot of stall threads, that weren't >> updated in months. Some of them seem to pass several CFs without any >> activity at all. I believe that it is wrong for many reasons, the major >> of which IMHO is a frustration of the authors. Can we come up with >> something to impove this situation? > Yeah, that's a perennial problem. Part of the issue is just a shortage > of people --- there are always more patches than we can review and > commit in one month. IMO, another cause is that we have a hard time > saying "no". If a particular patch isn't too well liked, we tend to > just let it slide to the next CF rather than making the uncomfortable > decision to reject it. If you've got thoughts about that, or any other > ways to improve the process, for sure speak up. > From a CFM perspective, we can try the following things: - Write recaps for long-running threads, listing open questions and TODOs. This one is my personal pain. Some threads do look scary and it is less likely that someone will even start a review if they have to catch up with a year-long discussion of 10 people. - Mark patches from first-time contributors with some tag. Probably, these entries are simple/dummy enough to handle them faster. And also it will be a good reminder to be a bit less demanding with beginners. See Dmitry's statistic about how many people have sent patch only once [1]. - Proactively ask committers, if they are going to work on the upcoming CF and will they need any specific help. Maybe we can also ask about their preferred code areas and check what is left uncovered. It's really bad if there is no one, who is working with let's say WAL internals during the CF. TBH, I have no idea, what are we going to do with this knowledge, but I think it's better to know. - From time to time call a council of several committers and make tough decisions about patches that are in discussion for too long (let's say 4 commitfests). Hopefully, it will be easier to reach a consensus in a "real-time" discussion, or we can toss a coin. This problem was raised in previous discussions too [2]. [1] https://www.postgresql.org/message-id/CA+q6zcXtg7cFwX-c+BoOwk65+jtR-sQGZ=1mqG-VGMVZuH86sQ@mail.gmail.com [2] https://www.postgresql.org/message-id/flat/CAA8%3DA7-owFLugBVZ0JjehTZJue7brEs2qTjVyZFRDq-B%3D%2BNwNg%40mail.gmail.com -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > [snip] > > Wow, that was well in advance) I am willing to assist if you need any help. > Indeed it was a bit early. I left for vacation after that. For the record, I am newly active to the community. In our PUG,in Stockholm, we held a meetup during which a contributor presented ways to contribute to the community, one of whichis becoming CFM. So, I thought of picking up the recommendation. I have taken little part in CFs as reviewer/author and I have no idea how a CF is actually run. A contributor from Stockholmhas been willing to mentor me to the part. Since you have both the knowledge and specific ideas on improving the CF, how about me assisting you? I could shadow youand you can groom me to the part, so that I can take the lead to a future CF more effectively. This is just a suggestion of course. I am happy with anything that can help the community as a whole.
On 20.10.2020 10:30, gkokolatos@pm.me wrote: > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> [snip] >> >> Wow, that was well in advance) I am willing to assist if you need any help. >> > Indeed it was a bit early. I left for vacation after that. For the record, I am newly active to the community. In our PUG,in Stockholm, we held a meetup during which a contributor presented ways to contribute to the community, one of whichis becoming CFM. So, I thought of picking up the recommendation. > > I have taken little part in CFs as reviewer/author and I have no idea how a CF is actually run. A contributor from Stockholmhas been willing to mentor me to the part. > > Since you have both the knowledge and specific ideas on improving the CF, how about me assisting you? I could shadow youand you can groom me to the part, so that I can take the lead to a future CF more effectively. > > This is just a suggestion of course. I am happy with anything that can help the community as a whole. > Even though, I've worked a lot with community, I have never been CFM before as well. So, I think we can just follow these articles: https://www.2ndquadrant.com/en/blog/managing-a-postgresql-commitfest/ https://wiki.postgresql.org/wiki/CommitFest_Checklist Some parts are a bit outdated, but in general the checklist is clear. I've already requested CFM privileges in pgsql-www and I'm going to spend next week sending pings and updates to the patches at commitfest. There are already 219 patches, so I will appreciate if you join me in this task. -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, October 25, 2020 8:01 PM, Anastasia Lubennikova <a.lubennikova@postgrespro.ru> wrote: > On 20.10.2020 10:30, gkokolatos@pm.me wrote: > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > > > [snip] > > > Wow, that was well in advance) I am willing to assist if you need any help. > > > > Indeed it was a bit early. I left for vacation after that. For the record, I am newly active to the community. In ourPUG, in Stockholm, we held a meetup during which a contributor presented ways to contribute to the community, one of whichis becoming CFM. So, I thought of picking up the recommendation. > > I have taken little part in CFs as reviewer/author and I have no idea how a CF is actually run. A contributor from Stockholmhas been willing to mentor me to the part. > > Since you have both the knowledge and specific ideas on improving the CF, how about me assisting you? I could shadowyou and you can groom me to the part, so that I can take the lead to a future CF more effectively. > > This is just a suggestion of course. I am happy with anything that can help the community as a whole. > > Even though, I've worked a lot with community, I have never been CFM > before as well. So, I think we can just follow these articles: > > https://www.2ndquadrant.com/en/blog/managing-a-postgresql-commitfest/ > https://wiki.postgresql.org/wiki/CommitFest_Checklist > > Some parts are a bit outdated, but in general the checklist is clear. > I've already requested CFM privileges in pgsql-www and I'm going to > spend next week sending pings and updates to the patches at commitfest. Awesome. I will start with requesting the privileges then. > > There are already 219 patches, so I will appreciate if you join me in > this task. Count me in. > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Anastasia Lubennikova > Postgres Professional: http://www.postgrespro.com > The Russian Postgres Company