Re: "Maintainer" as an alias of PMC Member?
Hi tison, Could you do this thread belongs apache Tomcat Regards Koti On Sat, 23 Mar 2024, 14:18 tison, wrote: > Hi, > > Random thought. > > You may find people not a native English speaker keep calling a PMC Member > of Apache Foo "Foo PMC". > > We correct it so many times and spread the knowledge on list. But the trend > I observed doesn't change and IMO it's hopeless to change. > > Since people tend to use a short ref and "committer" gives a one-word > identifier first image, I'm trying to propose officially alias "PMC Member" > as "Maintainer" so that our wording is aligned. > > What do you think? > > Best, > tison. >
Re: [DISCUSSION] Community over Code Europe 2025
I am interested to join the Community over Code Europe 2025 On Mon, 18 Mar 2024, 14:26 Claude Warren, wrote: > Is anyone interested in starting work on Community over Code Europe 2025? > This is the premier ASF conference in Europe. > > The 2024 conference is in Bratislava in June [1], and it is probably time > to start thinking about 2025. I would be nice to have a leadership team in > place before CoC EU 2024 so that we can share info and lessons learned > directly. > > Claude Warren > Chair, > CoC EU 2024 Organizing Committee. > > > > > [1] http://eu.communityovercode.org >
Re: [WG: Badging] Proposed working group
Dynamic work should be able to figured out from the like minded process Establish the like minded process by having the everyone having the chance to be a committer Regards Koti On Wed, 28 Feb 2024, 22:59 Paulo Motta, wrote: > I'd be interested in collaborating on this WG. I'd probably not be able to > drive this, but would like to participate in discussions and maybe help > with one of the items. > > On Wed, Feb 28, 2024 at 8:54 AM Rich Bowen wrote: > > > TL;DR: https://github.com/apache/comdev-working-groups/pull/26 > > > > Over the years, we’ve discussed a badging/achievement system, but have > > never actually figured out the details around doing it. This is a > proposal > > for a working group to figure out what’s necessary, and determine whether > > we want to set up such a system. > > > > I’m interested in being part of the discussion, but don’t want to be the > > only one driving it, since I’m already taking on too much. But I didn’t > > want to drop a conversation that comes up several times a year, as far > back > > as I can remember. > > > > — > > Rich Bowen > > rbo...@rcbowen.com > > > > > > > > > > >
Re: [PR] working group content [comdev-working-groups]
Hi I have applied to commit as a committer from a contributor through icla Please consider Regards Koti On Tue, 27 Feb 2024, 19:05 rbowen (via GitHub), wrote: > > rbowen opened a new pull request, #24: > URL: https://github.com/apache/comdev-working-groups/pull/24 > >(no comment) > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For queries about this service, please contact Infrastructure at: > us...@infra.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: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
I agree the core idea behind the Asf is contribute in a committ mode Others should be added for different areas Who are redflagged should be re grouped Regards Koti On Tue, 27 Feb 2024, 20:04 koteswara Rao Gundapaneni, < koti.gundapan...@gmail.com> wrote: > > I totally agree the knowledge base is essential > > Regards > Koti > > > On Tue, 27 Feb 2024, 19:28 potiuk (via GitHub), wrote: > >> >> potiuk commented on PR #16: >> URL: >> https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1966599011 >> >>If there are no more comments. I'd love to get this one merged and >> then maybe others (I can do as well) add a bit more why`s for different >> areas. I think also - when we have a few whys we might actually regroup the >> "red-flags" and have them groupped according to the `why` they are >> referring to - rather than link them individually - but taht migh be a >> refactor of the docs when we add 2nd or 3rd why as well. >> >> >> -- >> This is an automated message from the Apache Git Service. >> To respond to the message, please log on to GitHub and use the >> URL above to go to the specific comment. >> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> >> For queries about this service, please contact Infrastructure at: >> us...@infra.apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
Re: [PR] Propose "why" folder that we will keep as "advisors" knowledge base [comdev-working-groups]
I totally agree the knowledge base is essential Regards Koti On Tue, 27 Feb 2024, 19:28 potiuk (via GitHub), wrote: > > potiuk commented on PR #16: > URL: > https://github.com/apache/comdev-working-groups/pull/16#issuecomment-1966599011 > >If there are no more comments. I'd love to get this one merged and then > maybe others (I can do as well) add a bit more why`s for different areas. I > think also - when we have a few whys we might actually regroup the > "red-flags" and have them groupped according to the `why` they are > referring to - rather than link them individually - but taht migh be a > refactor of the docs when we add 2nd or 3rd why as well. > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For queries about this service, please contact Infrastructure at: > us...@infra.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
