Re: [C/C Europe 25] [DISCUSS] Where to hold the conference

> On May 17, 2024, at 3:49 AM, Claude Warren wrote: > > Who will be at CoC Bratislava? Do we want to hold a BoF for CoC > organizers? Yes, but, I will caution you, these meetings are seldom productive. Having 20 people sit around and say the names of their favorite city is not actually a

[WG-Website] Calling attention to projects that Do Stuff Right

projects to write up something similar for their sites. These could perhaps go somewhere in https://community.apache.org/pmc/ — Rich Bowen rbo...@rcbowen.com

Re: Apache Phoenix Community health metrics are not getting displayed

> On May 7, 2024, at 4:42 PM, rajeshb...@apache.org > wrote: > > Hi > > I am Apache Phoenix Chair and need to prepare a board report and for that > requires the community health metrics which are not getting displayed at > board report wizard statistics. > > Only thing I could see is the dev

Re: https://projects.apache.org/statistics.html

> On May 13, 2024, at 9:08 AM, Pierre Smits wrote: > > That is indeed a pity. > > IMO, regular and consistent provision of statistical insights (BI, comes to > mind) supporting the statements in the quarterly project report would help > would help the reader of a o assess a project's health

[WG-Advisors] Short instructional videos

. — Rich Bowen rbo...@rcbowen.com

Re: [C/C Europe 25] [DISCUSS] Where to hold the conference

> On May 6, 2024, at 5:12 AM, Bertrand Delacretaz > wrote: > > On Fri, May 3, 2024 at 7:37 AM Claude Warren wrote: >> ...if you have opinions and/or ideas please speak up... > > I've been to several small/medium conferences in Berlin [1] in the > last few years and it was always a great

Re: [C/C Europe 25] [DISCUSS] Where to hold the conference

London can be a hassle for non citizen EU residents to travel to, since Brexit. Meanwhile many of us are at least familiar with Brussels having gone there for fosdem for a decade or more. Rich On Fri, May 3, 2024, 05:54 Claude Warren wrote: > Francois, > > Do you know of anyone on the ground

Re: Events calendar: help wanted

> On Apr 19, 2024, at 12:36 PM, sebb wrote: > > Before diving into any changes to how the calendar is defined and > maintained, I think it is vital to establish what is wanted from the > calendar, both from the maintenance point of view and the user PoV. > > The existing calendar allows views

Re: Events calendar: help wanted

> On Apr 19, 2024, at 7:08 AM, Raphael Bircher wrote: > > The JavaScript Calendar will only need a .ics files I would *really* like to not have to edit ics files directly. That way lies madness.

[jira] [Commented] (COMDEV-544) Improve comdev website navigation to GSoC mentor resources

[ https://issues.apache.org/jira/browse/COMDEV-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838680#comment-17838680 ] Rich Bowen commented on COMDEV-544: --- FYI, that page is at [https://github.com/apache/comdev-site/blob

Re: Events calendar: help wanted

> On Apr 18, 2024, at 10:25 AM, Raphael Bircher > wrote: > > Hi all > > Just a notice: before we install an other tool only to have a Ical > function... confluence already has a calendar. Can you possibly say more about this, or perhaps provide a link?

Re: I am interested in contributing to the

Thank you for your interest in the Apache Software Foundation projects. The ASF is home to more than 200 projects that span many topics, programming languages, project sizes, code complexity, and other ways of measuring. So where you get involved is going to vary based on your interests. *

Re: Events calendar: help wanted

On Apr 17, 2024, at 12:33 PM, Raphael Bircher wrote: > > Hi Rich > > The ICal from Google seems to work, so we could use a JavaScript wrapper to > display it on the page. And if we want, we could replace the iCal Feed from > Google to our own Doc food ;-) To be clear, are you volunteering to

Re: Events calendar: help wanted

> On Apr 17, 2024, at 11:46 AM, sebb wrote: > > An obvious work-round is to provide a link to the calendar, rather > than embedding it. > > A link requires action by the user, so presumably counts as giving > consent, (as long as the destination of the link is clear). Sure. This also feels

Events calendar: help wanted

roach, to me, since it seems that we’d just be kicking the can down the road a while longer until yet another privacy policy bites us. The events site is in Git here: https://github.com/apache/comdev-events-site Is anyone available/willing to help with this work? — Rich Bowen rbo...@rcbowen.com

Re: [wg-socialmedia] Creating a BlueSky account?

Fwiw I'm in favor of being in every non-trivial social network if we have people who will step up to * Work with M to understand messaging * Amplify official messages * Engage with people on these platforms Unfortunately the tools that allowed you to post to multiple platforms at the same time

Re: possible booth at the DevBcnf 2024 June , 13-14.

> On Apr 4, 2024, at 7:28 PM, jean-frederic clere wrote: > > Hi, > > We can get a table and 2 chairs for our booth at the DevBcn in Barcelona, > June 13-14. > > Any interest? > > I will be in Barcelona at that time, the agreement is the same as last year > and I can do the 50% presence

Re: New Joiner Msc Industrial Psychology

On Apr 2, 2024, at 1:30 PM, Ibrahim Mukherjee wrote: > > From: Ibrahim Mukherjee >> Date: 2 April 2024 at 18:23:45 BST >> To: mailto:dev@community.apache.org >> Subject: WG: New Joiner >> >> Hi, >> >> I am currently a PhD student interested in contributing to this group and >> Apache

Re: Conflicting information about event promotion

I’ve fixed the doc on www-site with https://github.com/apache/www-site/pull/358 But ... > On Apr 1, 2024, at 8:10 AM, Rich Bowen wrote: > > https://events.apache.org/README is almost completely wrong. > > https://github.com/apache/comdev-events-site contains old informatio

Re: [PR] New Design for events.apache.org [comdev-events-site]

> On Apr 1, 2024, at 8:16 AM, RedYetiDev (via GitHub) wrote: > > > RedYetiDev commented on PR #12: > URL: > https://github.com/apache/comdev-events-site/pull/12#issuecomment-2029669946 > > Okay! Do you want me to split up this PR, or keep that in note for the > future? > > Thank you!

Conflicting information about event promotion

n I do, and so I don’t forget. — Rich Bowen rbo...@rcbowen.com

Re: [PR] New Design for events.apache.org [comdev-events-site]

On Sat, Mar 30, 2024, 17:08 RedYetiDev (via GitHub) wrote: > > RedYetiDev opened a new pull request, #12: > URL: https://github.com/apache/comdev-events-site/pull/12 > >In , the > following item was listed: 'Keep this events.apache.org

Re: Board report wizard is not collecting statistics

On Sat, Mar 30, 2024, 21:06 Sheng Wu wrote: > Hi ComDev team > > I was working on writing SkyWalking board report, and wanted to check > the community activity statistics, but I notice the board report > wizard is not collecting statistics about GitHub relative things. > > -

Re: [WG] Workgroups update

On Fri, Mar 29, 2024, 21:14 Jarek Potiuk wrote: > > * signing up to become an advisor: > > https://github.com/apache/comdev-working-groups/blob/main/wg-advisors/advisors.md > I know I'm not usually the one to raise this objection, but... It occurs to me that some projects, and some individuals

Re: [WG] Workgroups update

> On Mar 29, 2024, at 1:17 PM, Jean-Baptiste Onofré wrote: > > Hi Rich, > > That's great, thanks ! > > Quick question about wg-advisors: does this WG include "strong" advice > to the PMC, like legal/trademark/brand advices to avoid issue ? > Yes, we should definitely be giving this advice

Re: Getting a project back on track

Thanks, folks. I’ve opened a PR with the feedback from this thread - https://github.com/apache/comdev-site/pull/174 - and would appreciate a review, and if you think it passes muster, a merge. Thanks. > On Mar 29, 2024, at 9:35 AM, Rich Bowen wrote: > > This week, I’ve been a

Re: [WG] Workgroups update

se things and run with them. I think they all desperately need to be done, but I only have time for one or two of them, myself. —Rich > On Fri, Mar 29, 2024, 10:06 AM Rich Bowen wrote: > >> A month or so ago I started pitching workgroups as a way to organize and >> make pro

Re: Getting a project back on track

am, and end up being one or two people trying to keep the lights on, with no time to go out and find helpers. > On Fri, Mar 29, 2024 at 9:36 AM Rich Bowen wrote: >> >> This week, I’ve been approached by someone concerned about one of our >> projects, and look

[WG] Workgroups update

as an Advisor on a couple of projects, and am working on the website as I have time. But this is going to take all of us. — Rich Bowen rbo...@rcbowen.com

Getting a project back on track

for getting committer. Consider lowering your wall a little * What else? Another question that I have is where to put this doc. I’m thinking it goes in https://github.com/apache/comdev-site/tree/main/source/pmc somewhere, but I’m not sure that to name it. — Rich Bowen rbo...@rcbowen.com

Re: "Maintainer" as an alias of PMC Member?

As much as folks love to debate names ... this isn't a real problem. Some l People call PMC members simply "PMC" and while this might grate on some people, it's not a real problem. It does not actually cause any bad outcomes other than the annoyance of a few people. There is nothing to solve

Re: [WG: Badging] Tooling, reclaiming thread

> On Mar 20, 2024, at 11:59 AM, Paulo Motta wrote: > > Rich: > > I need some time to better elaborate this. I will prepare sometime in the > next week or so a short doc explaining what am I proposing, what problem it > solves and how it intersects with the badging tool object of this working >

Re: [WG: Badging] Tooling, reclaiming thread

On Tue, Mar 19, 2024, 16:55 Paulo Motta wrote: > > it looks like there’s no way to run this on the hosted service and have > it integrated with ASF LDAP, as each individual badge recipient would have > to create an account through their tooling. > > Backing off a bit, do we really need logins

Re: Community Over Code NA community track, CFP closing soon

> On Mar 19, 2024, at 10:43 AM, Rich Bowen wrote: > > Hey, folks, > The CFP - Call for Presentations - for Community Over Code North America is > closing very soon - at 23:59 UTC on April 1, 2024 > > https://communityovercode.org/call-for-presentations/ >

Community Over Code NA community track, CFP closing soon

, onboarding, community growth, and so on. We almost always have twice as many submissions as we can reasonably run, so please do write your abstracts carefully with that in mind, and wow us with your presentation ideas. We hope to see many of you in Denver! — Rich Bowen rbo...@rcbowen.com

Re: Reporter tool for board reports needs some love

> On Mar 18, 2024, at 5:18 PM, Craig Russell wrote: > > Hi, > > Is there anyone who can take a look at the Reporter tool that many projects > rely on to help create board reports? > > A number of projects have commented that the statistics seem to be in > conflict with reality. Every

[WG-website] Front page is a mess

be stuck with this forever. So … if you would like to be involved with that, please do let me know, either here or on Slack. Otherwise I’m going to just dive in and start breaking things. Thanks. — Rich Bowen rbo...@rcbowen.com

[WG: Badging] Tooling, reclaiming thread

e might do that, or another badging tool that may make this easier? — Rich Bowen rbo...@rcbowen.com

Re: [WG: Badging] Tooling

> On Mar 8, 2024, at 12:09 PM, Gary D. Gregory wrote: > > Sure, badging can be fun and it sure seems popular on GitHub: I do like my > Mars 2020 Helicopter Mission badge (https://github.com/garydgregory/) ! > > I wonder if there are there any privacy issue we should be able to foresee? > > I

Re: [WG: Badging] Tooling

On Mar 8, 2024, at 9:19 AM, Rich Bowen wrote: > > I attended a talk last week at FOSS Backstage by Spot Callaway, who started > the Fedora badges program. He said that the guiding principles are: > > * It should be fun, not legalistic. > * It should celebrate non-code accomp

Re: [WG: Badging] Tooling

Let me state this more clearly: > > If someone never logged in, they would never see their badges. That is common > to all of the badge platforms that I have looked at. For every badge system I’ve looked at, nobody receives any badges until they log into the system, creating their account.

Re: [WG: Badging] Tooling

> On Mar 8, 2024, at 10:24 AM, sebb wrote: > > Some people may not want badges; they should not be forced to have > them if they happen to meet the criteria. > I agree that opt-in is necessary. > If someone never logged in, they would never see their badges. That is common to all of the badge

Re: [WG: Badging] Tooling

> On Mar 3, 2024, at 11:47 AM, Paulo Motta wrote: > > I've thought a bit more and rather than starting with multiple badges, it > probably makes more sense to start with a single badge to validate the > idea. More can be proposed later if the first one is shown to be effective. > > I'd propose

Re: Query about the GitHub statistics for Lucene

Looks like the .invalid in your email address caused my response to go astray. The second half of your question: https://reporter.apache.org/about.html Unfortunately the tool is not actively maintained at the moment. We could certainly use some more eyes and fingers on it. Rich On Tue, Mar 5,

Re: [WG: Badging] Tooling

> On Feb 29, 2024, at 9:44 AM, Paulo Motta wrote: > >> The most promising of these was Badgr (https://badgr.com/) which seems to > have become a paid service, and not open any more. > > An active fork of badgr is available on > https://github.com/edubadges/edubadges-server. I note that it’s

[WG: Badging] Tooling

? — Rich Bowen rbo...@rcbowen.com

[WG: Badging] Proposed working group

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: Web site checker needs help

> On Feb 28, 2024, at 3:01 AM, Bertrand Delacretaz > wrote: > > On Wed, Feb 28, 2024 at 1:28 AM Craig Russell wrote: >> ...Is it worth creating a new community-working-group-site-check to document >> the issues with the tool?... > > Whimsy is created and managed by the

Re: [WG: Welcome] Proposal, a Welcome Working Group - onboarding too?

> On Feb 25, 2024, at 5:10 PM, Shane Curcuru wrote: > > Rich Bowen wrote on 2/7/24 11:53 AM: >> Proposed: A formal working group around how we welcome new folks in a >> consistent and helpful manner. >> We get people on this list (and on every dev@ and user@ list at

Re: Query about the GitHub statistics for Lucene

The second half of your question: https://reporter.apache.org/about.html Unfortunately the tool is not actively maintained at the moment. We could certainly use some more eyes and fingers on it. Rich On Fri, Feb 23, 2024, 03:20 Chris Hegarty wrote: > Hi, > > I have a query about the GitHub

Re: [PR] Prototype "volunteers" page (comdev-site)

I've not had a chance to review carefully because I'm traveling but I love the idea and am +1 to the patch in concept. Since it is replacing something that doesn't work, I see no risk in moving forward with this. Thanks! Rich On Fri, Feb 23, 2024, 03:44 bdelacretaz (via GitHub) wrote: > >

Re: [DISCUSS] Create a new repo for website template

On Wed, Feb 21, 2024, 12:40 Christian Grobmeier wrote: > > On Wed, Feb 21, 2024, at 10:43, tison wrote: > > Hi Chris, > > > > Thanks you. Now we found a volunteer to improve the jekyll template and > > it's good :D > > Haha ok great, I will send a patch as suggested. I can also commit > directly

Re: [PR] Change Sharpeners to Advisors advisors [comdev-working-groups]

Thanks. Merged. — Rich Bowen rbo...@rcbowen.com > On Feb 19, 2024, at 2:26 PM, dave2wave (via GitHub) wrote: > > > dave2wave opened a new pull request, #10: > URL: https://github.com/apache/comdev-working-groups/pull/10 > > (no comment) > > > -- >

Re: [WG: Sharpeners] Propose: milder name

me. >>> >>> All of this sounds to me like an advisory role where advisory is >>> "having or consisting in the power to make recommendations but not to >>> take action enforcing them."[1] >>> So I'd go with "PMC Advisor". It's not cute or clev

Re: [WG: Sharpeners] Propose: milder name

> On Feb 18, 2024, at 10:02 AM, Gary Gregory wrote: > > I've never heard of someone being called a "sharpener"; I've used a > knife sharpener and a pencil sharpener ;-) ... it feels like a stretch > here. > > In general, I prefer names that simply describe intent instead of >

Re: [WG: Sharpeners] Propose: milder name

I'm not tied to either the name or the alliteration. I thought it was cute. I honestly don't see the antagonistic overtones, but I'll take your word for it. I also don't relish the naming debate. I suppose every name has implications for someone. I'll defer to whatever folks want to call it.

Re: [WG: Sharpeners] Proposed: Escalation advice

Sorry, I managed to miss the second half of your email. > On Feb 16, 2024, at 1:12 PM, Dave Fisher wrote: > >> https://github.com/rbowen/comdev-working-groups/blob/main/wg-sharpeners/escallation.md > > It’s spelled “escalation”. In addition you use the term mentors here where > there are

Re: [WG: Sharpeners] Proposed: Escalation advice

> On Feb 16, 2024, at 1:12 PM, Dave Fisher wrote: > > I have a couple of overarching comments. > > A. Why “Sharpener”? I don’t really want to bike shed the name, but here are > definitions: > > 1. a device or tool for making something sharper, esp. pencils or knives: > 2. (Slang) An

[WG: Sharpeners] Proposed: Escalation advice

the perception which I’m seeing from more than one place that this is just a way for people to be policemen in our projects. Let me know what y’all think. — Rich Bowen rbo...@rcbowen.com

Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases

Bit of a long message here, but that’s because I’m trying to address your many disparate points. Jarek, I am sensing TWO things in your message. 1) You are concerned that we are instituting a police state 2) You have a subtly different understanding of what it is that I’m trying to do here

Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases

> I just have strong feelings about > community self-governance and understanding and I will be honest about the > fact that I am worried about creeping legalism at the ASF. Instead of > looking for symptoms, I think Sharpeners should be looking for, and aiming > to help with, basic challenges.

Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases

> >> "However, having an idea of what red flags we're looking for >> in a project can be a helpful way to start looking for places to mentor, >> and sharpen, our projects." >> >> That is absolutely the wrong message to give. Who is "we"? This kind of >> thing sets the tone of the working

Re: [jira] [Commented] (COMDEV-543) Sharpeners use cases

On Feb 14, 2024, at 2:46 PM, Phil Steitz wrote: > > I guess I am too late here, but fwiw, I agree strongly with Rich's > comment. I would much rather see the checklisty stuff incorporated into > either the use cases or the main doc somewhere and not presented as "things > 'we' are looking for".

[jira] [Commented] (COMDEV-543) Sharpeners use cases

[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817400#comment-17817400 ] Rich Bowen commented on COMDEV-543: --- Added to doc in https://github.com/apache/comdev-working-groups

[jira] [Commented] (COMDEV-543) Sharpeners use cases

[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817371#comment-17817371 ] Rich Bowen commented on COMDEV-543: --- These are all good, but I am *very* concerned that we would

[WG] Workgroups repo moved to git

The workgroups repo has now moved to https://github.com/apache/comdev-working-groups Please adjust accordingly Zili, can you close the ticket you opened? I appear to not have permission to do so. — Rich Bowen rbo...@rcbowen.com

Re: [WG: Sharpeners] Proposed - Sharpeners

Thanks, Phil. Patches applied. This is all good stuff. — Rich Bowen rbo...@rcbowen.com > On Feb 12, 2024, at 5:21 PM, Phil Steitz wrote: > > Sorry, last message got away from me. The point of the use cases is to get > a rough consensus of the kinds of things that a Sharpen

[jira] [Closed] (COMDEV-543) Sharpeners use cases

[ https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Bowen closed COMDEV-543. - Resolution: Fixed Thanks. Added in r1915770. > Sharpeners use ca

[jira] [Commented] (COMDEV-542) More public tone for sharpeners

[ https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816993#comment-17816993 ] Rich Bowen commented on COMDEV-542: --- Thanks. Applied in r1915769. > More public tone for sharpen

[jira] [Closed] (COMDEV-542) More public tone for sharpeners

[ https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Bowen closed COMDEV-542. - > More public tone for sharpeners > --- > > Key

[jira] [Resolved] (COMDEV-542) More public tone for sharpeners

[ https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Bowen resolved COMDEV-542. --- Resolution: Fixed Patch applied > More public tone for sharpen

Re: [WG: Social Media] Proposed - Social Media working group

> On Feb 11, 2024, at 6:24 AM, Slawomir Jaranowski > wrote: > > Hi, > > Thanks for the idea ... > > Some time ago we discuss on Maven slack channel who can publish message > behalf of ASF like announcements about new releases > > Clear rules for ASF wide and for project accounts will be

Re: [REQUEST] Create apache/community GitHub Repo (WAS: Working groups working group)

> On Feb 12, 2024, at 10:24 AM, sebb wrote: > > Why not migrate the SVN repo to Git? > Is there any need to keep the info in SVN? FWIW, I have no opinion on this, beyond my fiery and abiding antipathy for Git. If that’s what people want, go ahead, and I’ll adjust. This is a discussion. I’m

Re: [WG: Sharpeners] Proposed - Sharpeners

> On Feb 12, 2024, at 10:57 AM, tison wrote: > > Thank you for starting this discussion, Rich. > > I'm trying to get the points of this WG: > > 1. This WG is NOT a new office to "shepherd" TLPs, but to write down > how any community member can help in sharpening an ASF project. > 2. For

Re: [REQUEST] Create apache/community GitHub Repo (WAS: Working groups working group)

> On Feb 12, 2024, at 10:46 AM, tison wrote: > >> Why not migrate the SVN repo to Git? >> Is there any need to keep the info in SVN? > > I'm +1 in this direction. But it doesn't bother me if we keep a gate > to allow commiting via SVN and sync to GitHub. If Rich likes this way > and now he is

Re: [REQUEST] Create apache/community GitHub Repo (WAS: Working groups working group)

On Feb 12, 2024, at 10:13 AM, tison wrote: > > According to the INFRA ticket [1], we'd better create the > apache/community GitHub repo first. > > I'm glad to execute the self-serve command but I'm yet to be a COMDEV > PMC member. I remember that in another thread, it's said that an > Apache

Re: [WG: Sharpeners] Proposed - Sharpeners

— Rich Bowen rbo...@rcbowen.com > On Feb 11, 2024, at 6:04 PM, Phil Steitz wrote: > > I am working on a PR to take a stab at tweaking the wording. I am also > playing with some ideas around use cases - kinds of things sharpeners will > work on. I think it's really a good i

Re: New Project Proposal

is a good home for your project. It’s kind of a long document, but entering the Incubator is a long-term commitment, so it’s worth going in informed. — Rich Bowen rbo...@rcbowen.com > On Feb 10, 2024, at 6:13 AM, Ayaan Khan wrote: > > Hi everyone, > > Few months back I started

Re: [WG: Sharpeners] Proposed - Sharpeners

some historical examples and tease out a > little more what exactly "sharpening" is going to be. If it is primarily > (re-)education or community transformation, that really does need to be > public and community-based. If its more admin / legal / policy compliance, > that fits with the private

Re: [WG: Sharpeners] Proposed - Sharpeners

> On Feb 9, 2024, at 11:33 AM, Christofer Dutz > wrote: > > Hi Rich, > > I love every line of it … the only thing I would possibly “fine tune” in the > text, would be to be a bit more explicit: > “You must not already be a member of the PMC.” -> “You must not already be a > member of the

Re: [WG: Sharpeners] Proposed - Sharpeners

> On Feb 9, 2024, at 10:18 AM, Daniel Gruno wrote: > > I like this proposal a lot, and would be happy to sharpen some pencil > mahogany cases, if allowed (unless this pun was so bad you have to decline my > offer). > > I do have one question, which is where this ... report bit > would go,

[WG: Sharpeners] Proposed - Sharpeners

n ASF member has already earned trust in the context of the ASF. Trust is transitive - that is, you may not know all members personally, but each member was nominated and elected by people that you, in turn, nominated and elected. — Rich Bowen rbo...@rcbowen.com

[WG: Social Media] Proposed - Social Media working group

nsibly, consistently, positively and coherently be spokespeople for the ASF. Possibly work with MarkPub to establish some kind of guidelines or certification? — Rich Bowen rbo...@rcbowen.com

[WG: Social] Proposed - Social working group

with trademarks@ to ensure that you're not stepping on toes here. * This is an unfunded, volunteer effort. You don't have access to ComDev budget for this, except with regard to foundation swag (stickers, for example) that ComDev chooses to provide. — Rich Bowen rbo...@rcbowen.com

Re: charges from Apache Maven

://lists.apache.org/list.html?d...@maven.apache.org I think) might know? — Rich Bowen rbo...@rcbowen.com > On Feb 8, 2024, at 9:44 AM, Daniela Botterbusch Cole wrote: > > hi- > > Since mid-2023 I've been receiving monthly charges to my Amex card for $13. > Those charges are linked to Apa

Re: [WG: Website] Proposal - Website working group

done. — Rich Bowen rbo...@rcbowen.com > On Feb 7, 2024, at 11:11 AM, Rich Bowen wrote: > > Proposed: Form a formal Website working group. > > (I am aware that I haven’t defined “working group” yet, and I do, in fact, > intend to propose a Working Groups Working Group wh

Re: [WG: WG] Proposal: Working groups working group

> On Feb 7, 2024, at 11:22 AM, Rich Bowen wrote: > > * Where to we want to track WG status? I would propose that we create > GitHub.com/apache/community <http://github.com/apache/community> for stuff > like this, to mirror GitHub.com/kubernetes/community > <h

[WG: Welcome] Proposal, a Welcome Working Group

would love to talk much more about, but are beyond the scope of this proposal. What do y’all think? — Rich Bowen rbo...@rcbowen.com

[WG: WG] Proposal: Working groups working group

that they fit into it. What do y’all think? — Rich Bowen rbo...@rcbowen.com

[WG: Website] Proposal - Website working group

d hope that a WG would have regular checkins (could be email, Slack, Google Meet, I really don’t care, as long as everyone is engaging with the conversation.) If you are interested in helping form this group, please speak up in this thread, and help us help one another. — Rich Bowen rbo...@rcbowen.com

Working groups

this week, as soon as soon as I can write it up, and asking for folks to participate. More, and more rambling, thoughts on this topic, here: https://drbacchus.com/the-many-hats-of-a-maintainer/ - if you’re interested. — Rich Bowen rbo...@rcbowen.com

VP Conferences changes

Fyi, effective yesterday, I have stepped down as VP conferences. The responsibility for that role has passed to VP marketing, but communication around conferences will still happen on the planners mailing list, as it has for many years. It's my hope to get a little more engaged on the side of the

(NuttX) Re: Missing DOAP file

On Tue, 2023-09-05 at 14:29 -0300, Alan C. Assis wrote: > Hi Rich, > > Thank you very much for let us to know about it. > > Before you create the DOAP, could you please include the Category: > RTOS or IoT ? > > NuttX doesn't fit in any of existing categories: Big Data, Build > Management,

Requests for comdev membership

It seems to me that the recent requests for comdev membership are symptoms of broken process. I understand that this is necessary to get things done, but the fact that someone has to be a comdev member in order to edit the website is broken. I am not sure what the way forward is here, but if

Re: [DRAFT] Email to all PMCs or Committers

As discussed offline, I feel like the tone of this messaging is wrong. Give me a bit to get to my desk and I will propose an alternate draft. Shosholoza, Rich On Fri, Aug 4, 2023, 04:43 Christofer Dutz wrote: > Hi, > > Here comes a draft for an email I would like to send out. > > Not quite

[jira] [Commented] (COMDEV-423) svn pubsub fallen over on apachecon.com

[ https://issues.apache.org/jira/browse/COMDEV-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17742431#comment-17742431 ] Rich Bowen commented on COMDEV-423: ---  and, as I recall, was addressed almost immediately. Thank you

Final Reminder: Community Over Code call for presentations closing soon

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] This is your final reminder that the Call for Presentations for Community Over Code (formerly known as ApacheCon) is closing soon - on Thursday, 13 July 2023

Re: Intent to recreate reporter.apache.org as a pipservice

+1 do it! Rich On Wed, Jun 28, 2023, 09:45 Daniel Gruno wrote: > Looks like there is a comdev-reporter.git which is an obsolete svn > mirror. Any objections to removing that repository? History will still > be present in subversion for the current reporter service. > > On 2023-06-28 13:27,

Re: [PR] What makes a good report? (comdev-site)

Sat, 24 Jun 2023 at 00:28, Rich Bowen wrote: > > > > On Fri, Jun 23, 2023, 06:10 rlenferink (via GitHub) > wrote: > > > > > > > > rlenferink commented on code in PR #125: > > > URL: > https://github.com/apache/comdev-site/pull/125#discuss

Re: [PR] What makes a good report? (comdev-site)

On Fri, Jun 23, 2023, 06:10 rlenferink (via GitHub) wrote: > > rlenferink commented on code in PR #125: > URL: https://github.com/apache/comdev-site/pull/125#discussion_r1239637617 > > > > Review Comment: >Great addition! Should we maybe link to > https://whimsy.apache.org/board/minutes/ if

  1   2   3   4   5   6   7   8   9   10   >