Re: Back to basics: What we do @comdev
rbo...@rcbowen.com wrote on 3/17/23 6:11 AM: On Fri, 2023-03-17 at 12:56 +, Drew Foulks wrote: Additionally, some sort of volunteer mentoring program would also be a huge boon to keeping newcomers involved in the larger community. While I strenuously agree, I also know how much work it is to run an actual effective mentoring program. I would *LOVE* to see someone step up to manage this, even as an informal spreadsheet, mailing list, or whatever. We had a "mentoring programme" with all sorts of structure until Rich nuked it... 8-) because no-one really used it (except perhaps the couple of people who checked in the webpages for it years ago). We also have a separate (non-public) mentoring program, with simple data-driven "who am I" forms, that got a handful of people to sign up... but no-one seems to remember it's there. The root issue is finding a group of people passionate about the idea to actively maintain the program over a longer time than just a few months. Questions that come to mind immediately are: * Who would we be willing to "endorse" as mentors? Is there some kind of vetting process so that we don't have random folks posing as representatives of the Foundation? Oh, yeah, the other key issue is finding volunteers for mentors who are active enough that they will help more than just a few emails. And, I agree with Rich: we need some vetting process along with training. * What advice would we give those folks? In particular, I don't want to throw people into the fire with no guardrails, and end up with people feeling obliged to be a "do my homework" service. In the past, a HUGE percentage of the people that come asking for mentoring are trying to do an assignment for class with vague instructions like "Contribute to an open source project". Yup, and especially key guidelines for both sides of time commitment expected. It needs to be very clear up front what the minimum amount of effort a mentor is willing to give, and also a target of how long a mentoring match is expected to last (at minimum). We'd also need the program volunteers to do check-ins with mentors/mentees occasionally to make sure something's happening. * What kind of disclaimers would we need to put on such a program to protect folks from people who don't get the results they're looking for? I'd want to look at some of the other projects/foundations who have done this successfully, and see what landmines there are that we can avoid stepping on. Getting a wiki page with a rough outline of what ComDev might realistically put together, plus a listing of other mentoring programs in FOSS would be a great start; at least then we could constructively think about this. We do have more focused energy showing up here these days! -- - Shane ComDev PMC The Apache Software Foundation - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
Hi Rich, thank you so much for raising this. 100% agree with you. On Thu, Mar 16, 2023 at 9:11 PM wrote: > > Hi, folks, > > I have tried to write this email several times, and keep getting > overwhelmed. Trying again. > > Comdev has no focus. Our website is a mess. We have no clear idea of > what we do. I would like to get back to basics, and figure out what it > actually is that we do here, and get rid of the stuff that we don't. > > For example: Looking at the website, we claim we have a mentoring > program. This is not true, and I'd like to cull that entire part of the > site. But I don't want to step on people who might actually want to do > that work. > > And that's just one example. > > A while back (2017) I rather over-optimistically wrote > https://community.apache.org/about/ which was a list of things that I > hoped that we might do some day. That was a mistake, because it makes > promises that nobody is following up on. > > I want to get back to our mandate: > > Provide a wide array of information, FAQs, and help to newcomers and > existing committers, and maintains a number of helpful tools. > > We should be a repository for useful information and best practice for > people at all levels of our community: newcomers; contributors; > committers; pmcs. > > The tools that we presumably maintain include: > projects.a.o > reporter.a.o > helpwanted (I think this is EOL, realistically) > > We facilitate Apache Local Communities (which does not appear to be > references on the website?) We have a section about ALC at the bottom right section of our site https://community.apache.org/ But agree, if it is not visible properly, we can think about updating its location or content. > > And we also facilitate GSoC > > I would like to refocus our website, and our efforts, around those > things, and drop everything else from our website, until and unless > someone actually steps up to do them. > > And, yes, I'm volunteering to do this work, but want to be sure I'm not > taking too much authority in doing so. Will be happy to collaborate with you on this effort. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On Fri, 2023-03-17 at 08:45 -0400, Jim Jagielski wrote: > Maybe part of ComDev could be in the matchmaker aspect of connecting > external people to internal groups. For example, Petri is a sort of > mentoring program... I must admit I had not looked at Petri in that light. Does Petri want us to send individuals to them for one-on-one mentoring? Or is it more, as I had understood, for a *project* that is looking for advice? Yeah, we should absolutely link to https://petri.apache.org/ from ... somewhere. Unsure what that link text should look like, though. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On Fri, 2023-03-17 at 12:56 +, Drew Foulks wrote: > Additionally, some sort of volunteer mentoring program would also be > a huge boon to keeping newcomers involved in the larger community. While I strenuously agree, I also know how much work it is to run an actual effective mentoring program. I would *LOVE* to see someone step up to manage this, even as an informal spreadsheet, mailing list, or whatever. Questions that come to mind immediately are: * Who would we be willing to "endorse" as mentors? Is there some kind of vetting process so that we don't have random folks posing as representatives of the Foundation? * What advice would we give those folks? In particular, I don't want to throw people into the fire with no guardrails, and end up with people feeling obliged to be a "do my homework" service. In the past, a HUGE percentage of the people that come asking for mentoring are trying to do an assignment for class with vague instructions like "Contribute to an open source project". * What kind of disclaimers would we need to put on such a program to protect folks from people who don't get the results they're looking for? I'd want to look at some of the other projects/foundations who have done this successfully, and see what landmines there are that we can avoid stepping on. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On 2023/03/17 12:45:22 Jim Jagielski wrote: > Maybe part of ComDev could be in the matchmaker aspect of connecting > external people to internal groups. For example, Petri is a sort of > mentoring program... Matching external people to internal groups would be a huge step forward in increasing the accessibility to the foundation! What kinds of groups should we be trying to grow this way? Additionally, some sort of volunteer mentoring program would also be a huge boon to keeping newcomers involved in the larger community. > > Just 2c from a peanut > > > On Mar 16, 2023, at 11:40 AM, rbo...@rcbowen.com wrote: > > > > Hi, folks, > > > > I have tried to write this email several times, and keep getting > > overwhelmed. Trying again. > > > > Comdev has no focus. Our website is a mess. We have no clear idea of > > what we do. I would like to get back to basics, and figure out what it > > actually is that we do here, and get rid of the stuff that we don't. > > > > For example: Looking at the website, we claim we have a mentoring > > program. This is not true, and I'd like to cull that entire part of the > > site. But I don't want to step on people who might actually want to do > > that work. > > > > And that's just one example. > > > > A while back (2017) I rather over-optimistically wrote > > https://community.apache.org/about/ which was a list of things that I > > hoped that we might do some day. That was a mistake, because it makes > > promises that nobody is following up on. > > > > I want to get back to our mandate: > > > > Provide a wide array of information, FAQs, and help to newcomers and > > existing committers, and maintains a number of helpful tools. > > > > We should be a repository for useful information and best practice for > > people at all levels of our community: newcomers; contributors; > > committers; pmcs. > > > > The tools that we presumably maintain include: > > projects.a.o > > reporter.a.o > > helpwanted (I think this is EOL, realistically) > > > > We facilitate Apache Local Communities (which does not appear to be > > references on the website?) > > > > And we also facilitate GSoC > > > > I would like to refocus our website, and our efforts, around those > > things, and drop everything else from our website, until and unless > > someone actually steps up to do them. > > > > And, yes, I'm volunteering to do this work, but want to be sure I'm not > > taking too much authority in doing so. > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
Maybe part of ComDev could be in the matchmaker aspect of connecting external people to internal groups. For example, Petri is a sort of mentoring program... Just 2c from a peanut > On Mar 16, 2023, at 11:40 AM, rbo...@rcbowen.com wrote: > > Hi, folks, > > I have tried to write this email several times, and keep getting > overwhelmed. Trying again. > > Comdev has no focus. Our website is a mess. We have no clear idea of > what we do. I would like to get back to basics, and figure out what it > actually is that we do here, and get rid of the stuff that we don't. > > For example: Looking at the website, we claim we have a mentoring > program. This is not true, and I'd like to cull that entire part of the > site. But I don't want to step on people who might actually want to do > that work. > > And that's just one example. > > A while back (2017) I rather over-optimistically wrote > https://community.apache.org/about/ which was a list of things that I > hoped that we might do some day. That was a mistake, because it makes > promises that nobody is following up on. > > I want to get back to our mandate: > > Provide a wide array of information, FAQs, and help to newcomers and > existing committers, and maintains a number of helpful tools. > > We should be a repository for useful information and best practice for > people at all levels of our community: newcomers; contributors; > committers; pmcs. > > The tools that we presumably maintain include: > projects.a.o > reporter.a.o > helpwanted (I think this is EOL, realistically) > > We facilitate Apache Local Communities (which does not appear to be > references on the website?) > > And we also facilitate GSoC > > I would like to refocus our website, and our efforts, around those > things, and drop everything else from our website, until and unless > someone actually steps up to do them. > > And, yes, I'm volunteering to do this work, but want to be sure I'm not > taking too much authority in doing so. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On Fri, 2023-03-17 at 08:48 +, sebb wrote: > Created GSOC Jira project; hope that's OK > > Note: self-serve hung, but the project appears to have been created > OK. > > If agreed, the next stage would be to update the documentation to > point to the new project, and transfer existing issues. Yes please, if Max is on board with this. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
Created GSOC Jira project; hope that's OK Note: self-serve hung, but the project appears to have been created OK. If agreed, the next stage would be to update the documentation to point to the new project, and transfer existing issues. On Fri, 17 Mar 2023 at 03:02, Craig Russell wrote: > > > > > On Mar 16, 2023, at 10:07, sebb wrote: > > > > I think there need to be 3 mailing lists instead of just dev@ > > > > general community help > > GSOC > > tool development > > > > I agree having a separate JIRA for GSOC would be a good idea. > > That would leave COMDEV for the website and various tools. > > This is an excellent idea. GSOC is a great sub-project and has lots of > interest and deserves its own space. > > Craig > > > > Sebb > > > > On Thu, 16 Mar 2023 at 16:31, Maxim Solodovnik wrote: > >> > >> On Thu, 16 Mar 2023 at 23:29, Daniel Gruno wrote: > >>> > >>> On 3/16/23 11:26, Maxim Solodovnik wrote: > > almost all communications are already at mentors@community :) > > >>> > >>> And yet we have 185 messages on this list in just the past month. I do > >>> believe splitting GSOC out from the COMDEV Jira space will make most of > >>> that go away. > >> > >> Separate GSoC project in JIRA is a great idea! > >> Thanks for it :))) > >> > >>> > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >>> For additional commands, e-mail: dev-h...@community.apache.org > >>> > >> > >> > >> -- > >> Best regards, > >> Maxim > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > Craig L Russell > c...@apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
> On Mar 16, 2023, at 10:07, sebb wrote: > > I think there need to be 3 mailing lists instead of just dev@ > > general community help > GSOC > tool development > > I agree having a separate JIRA for GSOC would be a good idea. > That would leave COMDEV for the website and various tools. This is an excellent idea. GSOC is a great sub-project and has lots of interest and deserves its own space. Craig > > Sebb > > On Thu, 16 Mar 2023 at 16:31, Maxim Solodovnik wrote: >> >> On Thu, 16 Mar 2023 at 23:29, Daniel Gruno wrote: >>> >>> On 3/16/23 11:26, Maxim Solodovnik wrote: almost all communications are already at mentors@community :) >>> >>> And yet we have 185 messages on this list in just the past month. I do >>> believe splitting GSOC out from the COMDEV Jira space will make most of >>> that go away. >> >> Separate GSoC project in JIRA is a great idea! >> Thanks for it :))) >> >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> >> >> >> -- >> Best regards, >> Maxim >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > Craig L Russell c...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
I think there need to be 3 mailing lists instead of just dev@ general community help GSOC tool development I agree having a separate JIRA for GSOC would be a good idea. That would leave COMDEV for the website and various tools. Sebb On Thu, 16 Mar 2023 at 16:31, Maxim Solodovnik wrote: > > On Thu, 16 Mar 2023 at 23:29, Daniel Gruno wrote: > > > > On 3/16/23 11:26, Maxim Solodovnik wrote: > > > > > > almost all communications are already at mentors@community :) > > > > > > > And yet we have 185 messages on this list in just the past month. I do > > believe splitting GSOC out from the COMDEV Jira space will make most of > > that go away. > > Separate GSoC project in JIRA is a great idea! > Thanks for it :))) > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > -- > Best regards, > Maxim > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On Thu, 16 Mar 2023 at 23:29, Daniel Gruno wrote: > > On 3/16/23 11:26, Maxim Solodovnik wrote: > > > > almost all communications are already at mentors@community :) > > > > And yet we have 185 messages on this list in just the past month. I do > believe splitting GSOC out from the COMDEV Jira space will make most of > that go away. Separate GSoC project in JIRA is a great idea! Thanks for it :))) > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > -- Best regards, Maxim - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
> > > projects.a.o > > reporter.a.o > > helpwanted (I think this is EOL, realistically) > I am interested in helping with reporter.a.o and possibly more. On Thu, Mar 16, 2023 at 9:29 AM Daniel Gruno wrote: > On 3/16/23 11:26, Maxim Solodovnik wrote: > > > > almost all communications are already at mentors@community :) > > > > And yet we have 185 messages on this list in just the past month. I do > believe splitting GSOC out from the COMDEV Jira space will make most of > that go away. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Back to basics: What we do @comdev
On 3/16/23 11:26, Maxim Solodovnik wrote: almost all communications are already at mentors@community :) And yet we have 185 messages on this list in just the past month. I do believe splitting GSOC out from the COMDEV Jira space will make most of that go away. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On Thu, 16 Mar 2023 at 22:50, Daniel Gruno wrote: > > On 3/16/23 10:40, rbo...@rcbowen.com wrote: > > Hi, folks, > > > > I have tried to write this email several times, and keep getting > > overwhelmed. Trying again. > > > > Comdev has no focus. Our website is a mess. We have no clear idea of > > what we do. I would like to get back to basics, and figure out what it > > actually is that we do here, and get rid of the stuff that we don't. > > I completely agree here, this is a perennial request. Comdev is woefully > oversubscribed to unmaintained projects and initiatives and needs to be > reigned in to a manageable size. > > I would (again, I've mentioned it over the years) really love for us to > establish some sort of BoM here: Which projects do we currently have, > which do we have people actively or willing to actively maintain, and > which projects should we scrap. I believe getting this clarified would > be a great help. > > As a sort of aside, I'd also like for GSOC to be moved to a separate > list from dev@community (gsoc@community? maybe some generic term for > these events?) almost all communications are already at mentors@community :) > as well as moved out of the COMDEV Jira space. It is > quite frankly littering the mailing list with messages that do not > pertain to 90% of the subscribers. > > As with Rich, I am also very much willing to help with this. > > > > > For example: Looking at the website, we claim we have a mentoring > > program. This is not true, and I'd like to cull that entire part of the > > site. But I don't want to step on people who might actually want to do > > that work. > > > > And that's just one example. > > > > A while back (2017) I rather over-optimistically wrote > > https://community.apache.org/about/ which was a list of things that I > > hoped that we might do some day. That was a mistake, because it makes > > promises that nobody is following up on. > > > > I want to get back to our mandate: > > > > Provide a wide array of information, FAQs, and help to newcomers and > > existing committers, and maintains a number of helpful tools. > > > > We should be a repository for useful information and best practice for > > people at all levels of our community: newcomers; contributors; > > committers; pmcs. > > > > The tools that we presumably maintain include: > > projects.a.o > > reporter.a.o > > helpwanted (I think this is EOL, realistically) > > > > We facilitate Apache Local Communities (which does not appear to be > > references on the website?) > > > > And we also facilitate GSoC > > > > I would like to refocus our website, and our efforts, around those > > things, and drop everything else from our website, until and unless > > someone actually steps up to do them. > > > > And, yes, I'm volunteering to do this work, but want to be sure I'm not > > taking too much authority in doing so. > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > -- Best regards, Maxim - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On 2023/03/16 15:40:12 rbo...@rcbowen.com wrote: > Hi, folks, > > I have tried to write this email several times, and keep getting > overwhelmed. Trying again. > > Comdev has no focus. Our website is a mess. We have no clear idea of > what we do. I would like to get back to basics, and figure out what it > actually is that we do here, and get rid of the stuff that we don't. > > For example: Looking at the website, we claim we have a mentoring > program. This is not true, and I'd like to cull that entire part of the > site. But I don't want to step on people who might actually want to do > that work. > > And that's just one example. > > A while back (2017) I rather over-optimistically wrote > https://community.apache.org/about/ which was a list of things that I > hoped that we might do some day. That was a mistake, because it makes > promises that nobody is following up on. > > I want to get back to our mandate: > > Provide a wide array of information, FAQs, and help to newcomers and > existing committers, and maintains a number of helpful tools. I absolutely agree, paring back, simplifying, and re-organizing the overwhelming amount of information available, would make it much easier to get started, and stay involved. > > We should be a repository for useful information and best practice for > people at all levels of our community: newcomers; contributors; > committers; pmcs. > > The tools that we presumably maintain include: > projects.a.o > reporter.a.o > helpwanted (I think this is EOL, realistically) > > We facilitate Apache Local Communities (which does not appear to be > references on the website?) > > And we also facilitate GSoC > > I would like to refocus our website, and our efforts, around those > things, and drop everything else from our website, until and unless > someone actually steps up to do them. > > And, yes, I'm volunteering to do this work, but want to be sure I'm not > taking too much authority in doing so. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > I'd be happy to help with this also. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Back to basics: What we do @comdev
On 3/16/23 10:40, rbo...@rcbowen.com wrote: Hi, folks, I have tried to write this email several times, and keep getting overwhelmed. Trying again. Comdev has no focus. Our website is a mess. We have no clear idea of what we do. I would like to get back to basics, and figure out what it actually is that we do here, and get rid of the stuff that we don't. I completely agree here, this is a perennial request. Comdev is woefully oversubscribed to unmaintained projects and initiatives and needs to be reigned in to a manageable size. I would (again, I've mentioned it over the years) really love for us to establish some sort of BoM here: Which projects do we currently have, which do we have people actively or willing to actively maintain, and which projects should we scrap. I believe getting this clarified would be a great help. As a sort of aside, I'd also like for GSOC to be moved to a separate list from dev@community (gsoc@community? maybe some generic term for these events?) as well as moved out of the COMDEV Jira space. It is quite frankly littering the mailing list with messages that do not pertain to 90% of the subscribers. As with Rich, I am also very much willing to help with this. For example: Looking at the website, we claim we have a mentoring program. This is not true, and I'd like to cull that entire part of the site. But I don't want to step on people who might actually want to do that work. And that's just one example. A while back (2017) I rather over-optimistically wrote https://community.apache.org/about/ which was a list of things that I hoped that we might do some day. That was a mistake, because it makes promises that nobody is following up on. I want to get back to our mandate: Provide a wide array of information, FAQs, and help to newcomers and existing committers, and maintains a number of helpful tools. We should be a repository for useful information and best practice for people at all levels of our community: newcomers; contributors; committers; pmcs. The tools that we presumably maintain include: projects.a.o reporter.a.o helpwanted (I think this is EOL, realistically) We facilitate Apache Local Communities (which does not appear to be references on the website?) And we also facilitate GSoC I would like to refocus our website, and our efforts, around those things, and drop everything else from our website, until and unless someone actually steps up to do them. And, yes, I'm volunteering to do this work, but want to be sure I'm not taking too much authority in doing so. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Back to basics: What we do @comdev
Hi, folks, I have tried to write this email several times, and keep getting overwhelmed. Trying again. Comdev has no focus. Our website is a mess. We have no clear idea of what we do. I would like to get back to basics, and figure out what it actually is that we do here, and get rid of the stuff that we don't. For example: Looking at the website, we claim we have a mentoring program. This is not true, and I'd like to cull that entire part of the site. But I don't want to step on people who might actually want to do that work. And that's just one example. A while back (2017) I rather over-optimistically wrote https://community.apache.org/about/ which was a list of things that I hoped that we might do some day. That was a mistake, because it makes promises that nobody is following up on. I want to get back to our mandate: Provide a wide array of information, FAQs, and help to newcomers and existing committers, and maintains a number of helpful tools. We should be a repository for useful information and best practice for people at all levels of our community: newcomers; contributors; committers; pmcs. The tools that we presumably maintain include: projects.a.o reporter.a.o helpwanted (I think this is EOL, realistically) We facilitate Apache Local Communities (which does not appear to be references on the website?) And we also facilitate GSoC I would like to refocus our website, and our efforts, around those things, and drop everything else from our website, until and unless someone actually steps up to do them. And, yes, I'm volunteering to do this work, but want to be sure I'm not taking too much authority in doing so. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
