[ALC] Request to establish an ALC in Bangalore, India

[Navendu Pottekkat]

Hi,

We would like to start an ALC chapter in Bangalore, India.

This idea started when a couple of ASF Members, PMCs, and Committers 
came together and met at Open Source India Summit in September 2022, 
where the ASF had a booth.


Since Bangalore is a developer hub in India and a lot of people involved 
in ASF projects are active here, an ALC chapter would help provide a 
platform for these contributors to build and foster a community.


We have the following initial members:

 * Atri Sharma (atri, ASF Member, Lucene, Solr, HAWQ, MADLib, and
   Incubator PMC, Pinot Committer)
 * Mohammad Asif Siddiqui (asifdxtreme, ASF Member, ServiceComb and
   Incubator PMC, Nuttx Mentor)
 * Sumit Maheshwari (msumit, Airflow PMC)
 * Navendu Pottekkat (navendu, APISIX Committer)
 * Joshua Poddoku (Apache DevLake Contributor)

We look forward to a favorable reply.

- Navendu Pottekkat

Re: [ALC] Request to establish ALC in Xi'an

[peacewong]

+1, Good Luck!

Eason Chen  于2023年3月17日周五 14:34写道：

> My big +1, Good Luck!
>
> On Fri, Mar 17, 2023 at 10:14 AM wudi <676366...@qq.com.invalid> wrote:
> >
> > Thanks! CalvinKirs.
> >
> > I am very happy with the establishment of ALC in Xi’an!
> >
> > > 2023年3月17日 上午9:47，Jiafeng.Zhang  写道：
> > >
> > > This is very good news
> > > As a member of Apache Doris PMC, if ALC Xi'an can be established, we
> will be able to promote local open source development in the name of ALC
> > >
> > >
> > >
> > > -
> > > Best wishes！
> > > Jiafeng.Zhang / 张家锋
> > >
> > > Yikun Jiang mailto:yi...@apache.org>>
> 于2023年3月16日周四 22:57写道：
> > > Thanks! CalvinKirs.
> > >
> > > +1 from me.
> > >
> > > I am also exciting about ALC Xi'an setup.
> > >
> > > On Thursday, March 16, 2023, Willem Jiang  > wrote:
> > > my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
> > > Please check out this link[1] for more information.
> > > [1]
> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
> <
> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
> >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs  k...@apache.org>> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm an ASF member and I know many Apache project developers from
> > > > Xi'an. If ALC Xi'an can be established, then I think we can gather
> > > > everyone together in the name of ALC to promote the local development
> > > > of ASF.
> > > >
> > > > --
> > > > Best wishes！
> > > > CalvinKirs
> > > >
> > > > -
> > > > 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: [Discussion] ASF Booth at FOSSASIA 2023

[Navendu Pottekkat]

Hi Willem and Rich,

I will also be at FOSSASIA to give a talk about Apache APISIX. Will see 
you there!


- Navendu

On 15/03/23 6:21 pm, Priya Sharma wrote:

Ah, Rich, I think I didn't make it clear, but sadly I am not going to the event.
And so I was asking other volunteers to do it.

I would have loved to staff the booth (full-time) if I could go.

Williem and Rich, have a good time!

On Wed, 15 Mar 2023 at 18:08,  wrote:

On Wed, 2023-03-15 at 15:58 +0530, Priya Sharma wrote:

Thanks for your reply Rich!
But, unfortunately, we won't be having our booth there due to a lack
of volunteers.

I hope you have a fantastic time at the event!

Ok. Well, perhaps I'll see you there anyway.


On Tue, 28 Feb 2023 at 19:36,  wrote:

On Tue, 2023-02-28 at 18:27 +0530, Priya Sharma wrote:

Hello All,

I recently came to know about FOSSASIA. It develops Open Source
software and hardware solutions with a global developer community
from
its base in Asia and organizes Open Technology events around the
year.

FOSSASIA's annual Summit in Singapore is the premier Open
Technology
event in Asia for developers, tech companies, and contributors.
[1]

FOSSASIA Summit 2023 will be an in-person and online event,
taking
place from Thursday 13th April to Saturday 15th April at Lifelong
Learning Institute Singapore.
I believe it would be a good event to have Apache Software
Foundation's presence.

I reached out to the organizers and they are happy to offer us a
free
booth along with three complimentary event tickets.

Is someone planning to be at the event and would like to
volunteer
for
the booth (maybe those residing in or near Singapore)?


I will be speaking at the event, and can volunteer *some* time for
a
booth, but am not able to run it, manage it, or staff it full-time,
as
I have other obligations that week.

--Rich

---
--
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: [ALC] Request to establish ALC in Xi'an

[Xin Wang]

+1

peacewong  于2023年3月17日周五 15:38写道：

> +1, Good Luck!
>
> Eason Chen  于2023年3月17日周五 14:34写道：
>
> > My big +1, Good Luck!
> >
> > On Fri, Mar 17, 2023 at 10:14 AM wudi <676366...@qq.com.invalid> wrote:
> > >
> > > Thanks! CalvinKirs.
> > >
> > > I am very happy with the establishment of ALC in Xi’an!
> > >
> > > > 2023年3月17日 上午9:47，Jiafeng.Zhang  写道：
> > > >
> > > > This is very good news
> > > > As a member of Apache Doris PMC, if ALC Xi'an can be established, we
> > will be able to promote local open source development in the name of ALC
> > > >
> > > >
> > > >
> > > > -
> > > > Best wishes！
> > > > Jiafeng.Zhang / 张家锋
> > > >
> > > > Yikun Jiang mailto:yi...@apache.org>>
> > 于2023年3月16日周四 22:57写道：
> > > > Thanks! CalvinKirs.
> > > >
> > > > +1 from me.
> > > >
> > > > I am also exciting about ALC Xi'an setup.
> > > >
> > > > On Thursday, March 16, 2023, Willem Jiang  > > wrote:
> > > > my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
> > > > Please check out this link[1] for more information.
> > > > [1]
> >
> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
> > <
> >
> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
> > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs   > k...@apache.org>> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm an ASF member and I know many Apache project developers from
> > > > > Xi'an. If ALC Xi'an can be established, then I think we can gather
> > > > > everyone together in the name of ALC to promote the local
> development
> > > > > of ASF.
> > > > >
> > > > > --
> > > > > Best wishes！
> > > > > CalvinKirs
> > > > >
> > > > >
> -
> > > > > 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
> >
> >
>


-- 
Thanks,
Xin

Re: Back to basics: What we do @comdev

[sebb]

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

[GitHub] [comdev-site] rbowen commented on pull request #87: Remove references to helpwanted

[via GitHub]

rbowen commented on PR #87:
URL: https://github.com/apache/comdev-site/pull/87#issuecomment-1473750609

   @navendu-pottekkat the helpwanted code is at 
https://svn.apache.org/repos/asf/comdev/helpwanted.apache.org and you're 
absolutely welcome to work on it. If and when it becomes useful again, we could 
link to it again.
   


-- 
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: Back to basics: What we do @comdev

[rbowen]

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

[GitHub] [comdev-site] rbowen merged pull request #87: Remove references to helpwanted

[via GitHub]

rbowen merged PR #87:
URL: https://github.com/apache/comdev-site/pull/87


-- 
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: Back to basics: What we do @comdev

[Jim Jagielski]

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

[Drew Foulks]

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

[jira] [Resolved] (COMDEV-384) Tasks in the help page seems to have not been updated for a long time

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved COMDEV-384.
-
Resolution: Fixed

There are no longer any outdated tasks -- there are now no tasks at all

> Tasks in the help page seems to have not been updated for a long time
> -
>
> Key: COMDEV-384
> URL: https://issues.apache.org/jira/browse/COMDEV-384
> Project: Community Development
>  Issue Type: Improvement
>  Components: Help Wanted
>Reporter: ningtao
>Priority: Major
>
> https://helpwanted.apache.org/
> First, chose “Programming and Development”,  pick  “Java language”, then 
> “Found 26 items you might be interested in”,  but these tasks looks too old,  
> 25 task is created at 2017, one task created at 2019. And some of these tasks 
> are already in “closed” status. 
> I guess there are a lots of Java project need help in Apache, just not 
> include by Help Wanted.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[GitHub] [comdev-site] rbowen opened a new pull request, #88: Remove some things we don't actually do

[via GitHub]

rbowen opened a new pull request, #88:
URL: https://github.com/apache/comdev-site/pull/88

   Remove some items from the "what we do" page that we don't actually do. See 
https://cwiki.apache.org/confluence/display/COMDEV/Website for further 
discussion.


-- 
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

[GitHub] [comdev-site] rbowen merged pull request #88: Remove some things we don't actually do

[via GitHub]

rbowen merged PR #88:
URL: https://github.com/apache/comdev-site/pull/88


-- 
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: Back to basics: What we do @comdev

[rbowen]

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

[rbowen]

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

[GitHub] [comdev-site] rbowen opened a new pull request, #89: The speakers tool, at community.zones.apache.org, has been abandoned for

[via GitHub]

rbowen opened a new pull request, #89:
URL: https://github.com/apache/comdev-site/pull/89

   The speakers tool, at community.zones.apache.org, has been abandoned for a 
very long time, and we really shouldn't be promoting it.
   
   This removes links, but leaves the speakers/ directory, which has some 
(possibly?) useful links in it. I'll come back and clean that up some more when 
I have some time.
   


-- 
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

tika-offheap-leak

[朱桂锋]

Firstly,  thank you for tika project, she is great project!

Recently, i run the tika project and extract text from document， i find
java offheap is increasing until all the memory to the 100%, and then
killed by oom-killer.

then i use pmap and dump data from memory(exclude the java heap), i find
they are like this:

[ Content

Types] . xM1PK

rels/.relsPK word/ rels/document.xm1.relsPK word /document.xm1PK
word/footer4.xmIPK word/header4. xm1PK word/footer2.xmIPK word/header2.
xm1PK word /header3.xmIPK word/footer3.xmlPK word /header1.xm1PK

word/ footer1 . xm1PK

word / footnotes.xmlPK word/endnotes .xm1PK word/header5. xm1PK word/media/
image3.pngPK word/media/imagel. jpegPK word/media/image2. jpegPK word /
theme/ theme 1. xm1PK word/settings. xm1PK

customxml/ itemProps2 .xm1PK

customXml /item2 . xm1PK docProps /custom. xm1 PK t?92
customXml/rels/item1.xm1.relsPK customXml/ rels/item2.xm1.relsPK customXm1
/itemProps1.xm1PK



they are office document text，why they are in offheap?  so i doubt when
parse some special  office  document  it will cause memory leak.

And sorry  i don't know what the special office document and i  can't
afford the sample.


another infomation:  when i debug code on my own mac computer, using xlsx
sample ,
when it calling tika.detect, it called ZipArchiveInputStream constructor
twice, and the same times calling java.util.zip.Inflater#end();
but when it calling tika.parseToString,  it called ZipArchiveInputStream
constructor once, but no times calling java.util.zip.Inflater#end();

Is that caused the offheap memory leak because of the Inflater use native
code?

Look forward for your reply!  thank you very much!

Re: tika-offheap-leak

[rbowen]

Hi.

Unfortunately, you've reached the wrong list. This is a general
community list for the Apache Software Foundation as a whole. Tika has
its own lists, which you can find at
https://tika.apache.org/mail-lists.html and that's where the people
that can help with this hang out.

--Rich

On Fri, 2023-03-17 at 22:02 +0800, 朱桂锋 wrote:
> Firstly,  thank you for tika project, she is great project!
> 
> Recently, i run the tika project and extract text from document， i
> find
> java offheap is increasing until all the memory to the 100%, and then
> killed by oom-killer.
> 
> then i use pmap and dump data from memory(exclude the java heap), i
> find
> they are like this:
> 
> [ Content
> 
> Types] . xM1PK
> 
> rels/.relsPK word/ rels/document.xm1.relsPK word /document.xm1PK
> word/footer4.xmIPK word/header4. xm1PK word/footer2.xmIPK
> word/header2.
> xm1PK word /header3.xmIPK word/footer3.xmlPK word /header1.xm1PK
> 
> word/ footer1 . xm1PK
> 
> word / footnotes.xmlPK word/endnotes .xm1PK word/header5. xm1PK
> word/media/
> image3.pngPK word/media/imagel. jpegPK word/media/image2. jpegPK word
> /
> theme/ theme 1. xm1PK word/settings. xm1PK
> 
> customxml/ itemProps2 .xm1PK
> 
> customXml /item2 . xm1PK docProps /custom. xm1 PK t?92
> customXml/rels/item1.xm1.relsPK customXml/ rels/item2.xm1.relsPK
> customXm1
> /itemProps1.xm1PK
> 
> 
> 
> they are office document text，why they are in offheap?  so i doubt
> when
> parse some special  office  document  it will cause memory leak.
> 
> And sorry  i don't know what the special office document and i  can't
> afford the sample.
> 
> 
> another infomation:  when i debug code on my own mac computer, using
> xlsx
> sample ,
> when it calling tika.detect, it called ZipArchiveInputStream
> constructor
> twice, and the same times calling java.util.zip.Inflater#end();
> but when it calling tika.parseToString,  it called
> ZipArchiveInputStream
> constructor once, but no times calling java.util.zip.Inflater#end();
> 
> Is that caused the offheap memory leak because of the Inflater use
> native
> code?
> 
> Look forward for your reply!  thank you very much!


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove release page

[Robert Munteanu (Jira)]

[ 
https://issues.apache.org/jira/browse/COMDEV-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701831#comment-17701831
 ] 

Robert Munteanu commented on COMDEV-227:


[~akm] - fair enough. I probably won't have the time to look into this either, 
but for the record - the source code lives at 
https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/ .

> Only list last X releases and the add/remove release page
> -
>
> Key: COMDEV-227
> URL: https://issues.apache.org/jira/browse/COMDEV-227
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Robert Munteanu
>Priority: Major
> Attachments: COMDEV-227.patch.txt
>
>
> In the Apache Sling project we have a large number of releases as we have 
> many independent modules. When loading the 
> https://reporter.apache.org/addrelease.html?sling page, it takes upwards of 
> 10 seconds to load. It would be great if only the last X (50?) releases were 
> shown, and then a "load all" link would be available at the bottom.
> This would greatly speed up our usage of this tool.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: tika-offheap-leak

[朱桂锋]

Thank you for the clarification.

 于2023年3月17日周五 22:45写道：

> Hi.
>
> Unfortunately, you've reached the wrong list. This is a general
> community list for the Apache Software Foundation as a whole. Tika has
> its own lists, which you can find at
> https://tika.apache.org/mail-lists.html and that's where the people
> that can help with this hang out.
>
> --Rich
>
> On Fri, 2023-03-17 at 22:02 +0800, 朱桂锋 wrote:
> > Firstly,  thank you for tika project, she is great project!
> >
> > Recently, i run the tika project and extract text from document， i
> > find
> > java offheap is increasing until all the memory to the 100%, and then
> > killed by oom-killer.
> >
> > then i use pmap and dump data from memory(exclude the java heap), i
> > find
> > they are like this:
> >
> > [ Content
> >
> > Types] . xM1PK
> >
> > rels/.relsPK word/ rels/document.xm1.relsPK word /document.xm1PK
> > word/footer4.xmIPK word/header4. xm1PK word/footer2.xmIPK
> > word/header2.
> > xm1PK word /header3.xmIPK word/footer3.xmlPK word /header1.xm1PK
> >
> > word/ footer1 . xm1PK
> >
> > word / footnotes.xmlPK word/endnotes .xm1PK word/header5. xm1PK
> > word/media/
> > image3.pngPK word/media/imagel. jpegPK word/media/image2. jpegPK word
> > /
> > theme/ theme 1. xm1PK word/settings. xm1PK
> >
> > customxml/ itemProps2 .xm1PK
> >
> > customXml /item2 . xm1PK docProps /custom. xm1 PK t?92
> > customXml/rels/item1.xm1.relsPK customXml/ rels/item2.xm1.relsPK
> > customXm1
> > /itemProps1.xm1PK
> >
> >
> >
> > they are office document text，why they are in offheap?  so i doubt
> > when
> > parse some special  office  document  it will cause memory leak.
> >
> > And sorry  i don't know what the special office document and i  can't
> > afford the sample.
> >
> >
> > another infomation:  when i debug code on my own mac computer, using
> > xlsx
> > sample ,
> > when it calling tika.detect, it called ZipArchiveInputStream
> > constructor
> > twice, and the same times calling java.util.zip.Inflater#end();
> > but when it calling tika.parseToString,  it called
> > ZipArchiveInputStream
> > constructor once, but no times calling java.util.zip.Inflater#end();
> >
> > Is that caused the offheap memory leak because of the Inflater use
> > native
> > code?
> >
> > Look forward for your reply!  thank you very much!
>
>

Re: [ALC] Request to establish ALC in Xi'an

[Yuanhao Ji]

+1 from me. Looking forward to communicating with all friends!

Xin Wang  于2023年3月17日周五 16:33写道：

> +1
>
> peacewong  于2023年3月17日周五 15:38写道：
>
>> +1, Good Luck!
>>
>> Eason Chen  于2023年3月17日周五 14:34写道：
>>
>> > My big +1, Good Luck!
>> >
>> > On Fri, Mar 17, 2023 at 10:14 AM wudi <676366...@qq.com.invalid> wrote:
>> > >
>> > > Thanks! CalvinKirs.
>> > >
>> > > I am very happy with the establishment of ALC in Xi’an!
>> > >
>> > > > 2023年3月17日 上午9:47，Jiafeng.Zhang  写道：
>> > > >
>> > > > This is very good news
>> > > > As a member of Apache Doris PMC, if ALC Xi'an can be established, we
>> > will be able to promote local open source development in the name of ALC
>> > > >
>> > > >
>> > > >
>> > > > -
>> > > > Best wishes！
>> > > > Jiafeng.Zhang / 张家锋
>> > > >
>> > > > Yikun Jiang mailto:yi...@apache.org>>
>> > 于2023年3月16日周四 22:57写道：
>> > > > Thanks! CalvinKirs.
>> > > >
>> > > > +1 from me.
>> > > >
>> > > > I am also exciting about ALC Xi'an setup.
>> > > >
>> > > > On Thursday, March 16, 2023, Willem Jiang > > > wrote:
>> > > > my big +1，I'd be happy to be a mentor to help setup ALC Xi'an.
>> > > > Please check out this link[1] for more information.
>> > > > [1]
>> >
>> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
>> > <
>> >
>> https://cwiki.apache.org/confluence/display/COMDEV/Apache+Local+Community+-+ALC#ApacheLocalCommunityALC-HowtoapplytosetupALCChapter
>> > >
>> > > >
>> > > > Willem Jiang
>> > > >
>> > > > Twitter: willemjiang
>> > > > Weibo: 姜宁willem
>> > > >
>> > > > On Thu, Mar 16, 2023 at 10:26 PM Calvin Kirs > > > k...@apache.org>> wrote:
>> > > > >
>> > > > > Hi,
>> > > > >
>> > > > > I'm an ASF member and I know many Apache project developers from
>> > > > > Xi'an. If ALC Xi'an can be established, then I think we can gather
>> > > > > everyone together in the name of ALC to promote the local
>> development
>> > > > > of ASF.
>> > > > >
>> > > > > --
>> > > > > Best wishes！
>> > > > > CalvinKirs
>> > > > >
>> > > > >
>> -
>> > > > > 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
>> >
>> >
>>
>
>
> --
> Thanks,
> Xin
>

[GitHub] [comdev-site] rbowen opened a new pull request, #90: Advice for becoming a committer.

[via GitHub]

rbowen opened a new pull request, #90:
URL: https://github.com/apache/comdev-site/pull/90

   Proposed new document, offering practical advice for how to become a 
committer on an ASF project.


-- 
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

[GitHub] [comdev-site] mjfoulks opened a new pull request, #91: Update etiquette.md

[via GitHub]

mjfoulks opened a new pull request, #91:
URL: https://github.com/apache/comdev-site/pull/91

   Fixed typos; removed redundancies.


-- 
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

[GitHub] [comdev-site] rbowen merged pull request #91: Update etiquette.md

[via GitHub]

rbowen merged PR #91:
URL: https://github.com/apache/comdev-site/pull/91


-- 
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

[GitHub] [comdev-site] rbowen commented on pull request #91: Update etiquette.md

[via GitHub]

rbowen commented on PR #91:
URL: https://github.com/apache/comdev-site/pull/91#issuecomment-1474038390

   Thank you!


-- 
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

[GitHub] [comdev-site] mjfoulks opened a new pull request, #92: Update _index.md

[via GitHub]

mjfoulks opened a new pull request, #92:
URL: https://github.com/apache/comdev-site/pull/92

   minor changes for better readability


-- 
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

[GitHub] [comdev-site] rbowen opened a new pull request, #93: Remove mentoring section

[via GitHub]

rbowen opened a new pull request, #93:
URL: https://github.com/apache/comdev-site/pull/93

   We do not have a mentoring program(me) and I would like to stop pretending 
that we do.


-- 
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

[GitHub] [comdev-site] rbowen merged pull request #92: Update _index.md

[via GitHub]

rbowen merged PR #92:
URL: https://github.com/apache/comdev-site/pull/92


-- 
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

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #89: The speakers tool, at community.zones.apache.org, has been abandoned for

[via GitHub]

ShaneCurcuru commented on PR #89:
URL: https://github.com/apache/comdev-site/pull/89#issuecomment-1474100490

   I think eventually it will be useful to have a general speaker's resource 
page, so glad to leave it.


-- 
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

[GitHub] [comdev-site] ShaneCurcuru merged pull request #89: The speakers tool, at community.zones.apache.org, has been abandoned for

[via GitHub]

ShaneCurcuru merged PR #89:
URL: https://github.com/apache/comdev-site/pull/89


-- 
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

[GitHub] [comdev-site] mjfoulks opened a new pull request, #94: Update etiquette.md

[via GitHub]

mjfoulks opened a new pull request, #94:
URL: https://github.com/apache/comdev-site/pull/94

   removed link


-- 
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

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #94: Update etiquette.md

[via GitHub]

ShaneCurcuru commented on PR #94:
URL: https://github.com/apache/comdev-site/pull/94#issuecomment-1474178948

   Good catch, we have our own more polite versions of email etiquette 
guidelines.


-- 
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

[GitHub] [comdev-site] ShaneCurcuru merged pull request #94: Update etiquette.md

[via GitHub]

ShaneCurcuru merged PR #94:
URL: https://github.com/apache/comdev-site/pull/94


-- 
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

[GitHub] [comdev-site] clr-apache commented on a diff in pull request #90: Advice for becoming a committer.

[via GitHub]

clr-apache commented on code in PR #90:
URL: https://github.com/apache/comdev-site/pull/90#discussion_r1140531846


##
source/contributors/becomingacommitter.md:
##
@@ -0,0 +1,93 @@
+---
+title: Becoming a committer
+slug: becomingacommitter
+--
+
+# Disclaimer
+Nothing in this post should be construed as a guarantee. You can do everything 
listed here, for years, and still not become a committer. This is because the 
decision is made by individuals on the project PMC, who do things for their own 
reasons.
+
+On the contrary, this document discusses how things should work, and sometimes 
do work, in some Apache Software Foundation (ASF) projects, but might not on 
the one you’re interested in.
+
+Beneath each of these recommendations is the assumption that you are acting in 
good faith, for the benefit of the project. Simply attempting to check these 
boxes to game the system will reflect badly on you, and probably on your 
employer, too.
+
+# Becoming a Committer
+It’s important to remember that becoming a committer is not a reward, or a 
recognition, so much as that it is the project expressing self-interest. That 
is, people are added as a committer to a project because it benefits the 
project, not because it’s some kind of pat on the back for the individual in 
question. As such, every behavior suggested here is about advancing the 
interests of the project. It is critical that you think, first and foremost, 
about being a project owner, and working towards the benefit of the project and 
its users.
+
+These, therefore, are the behaviors that you should exhibit if you want to 
become a committer, and then a PMC member, on an ASF project. (These are not 
unique to ASF projects, of course, but process will differ greatly from one 
project to another, and are largely similar among ASF projects.)
+
+# Read the mailing list
+ASF projects communicate on the mailing list. If you want to be involved in 
the community, you must set aside time every week (preferably every day) to 
keep current on the community discussion.
+
+When first participating in an ASF project, you can (and should) look back 
several months (or as far as you have time for) to see what has been discussed 
recently. You can do this at [lists.apache.org](http://lists.apache.org/).
+
+A growing number of projects also have a presence on Slack, Discord, or 
somewhere else. Find where that is, and become a regular. A shrinking number of 
projects have a presence on Libera IRC – mostly the much older projects. This 
is where you’ll connect with the older members of the projects and learn more 
of the ancient project lore.
+
+# Contribute code (and other things)
+If you want to become a committer, you should make significant contributions 
to the project. The most obvious thing to contribute to a software project is 
code. Code contributions should be diverse in terms of size and significance. 
That is, you should work on small issues and large. You should collaborate with 
others on features and fixes, and you should propose significant changes 
yourself. You should dig up old tickets, and work towards resolving them.
+
+In particular, you should work on code that is of benefit to all users, rather 
than focusing solely on features that benefit only yourself, or your employer. 
As a project owner, you should care about the entire health and sustainability 
of the project.
+
+Code contributions are not the only type of contribution that counts towards 
becoming a committer, it’s just the most common. Design, documentation, 
marketing, event management, and many other ways of contributing to the success 
of a project are also often considered in making someone a committer. While the 
term “committer” implies committing code, it can also be interpreted as someone 
who is committed to the project.
+
+# End user support
+Answering end user questions has many benefits. It’s the best way to establish 
expertise in aspects of the software that effect actual users, and, thus, the 
best way to stay in touch with user concerns. It’s also the way to establish 
and maintain visibility in the project community, because your name is always 
visible on the mailing list.
+
+Caution: Do not just jump in and answer every question with visibility as a 
primary goal. Ensure that your answers are actually useful, and contribute 
something to the conversation. Simply posting to every conversation, 
particularly when someone else has already offered a good answer, can be 
perceived as attempting to game the metrics.
+
+# Documentation
+Improving the documentation is one of the most effective things that one can 
do to improve the user experience. If you notice many people asking similar 
questions, this is usually an indication that the documentation is weak on that 
point. Fix it. When the question is asked again, point to the improved 
documentation, and ask for feedback as to how it could be further improved.
+
+Take criticism of the documentation

Re: dev Digest 17 Mar 2023 17:32:48 -0000 Issue 2294

[Donavon Gamblin]

o unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org

i need unsubscribed asap

From: dev-digest-h...@community.apache.org 

Sent: Friday, March 17, 2023 11:32 AM
To: dev@community.apache.org 
Subject: dev Digest 17 Mar 2023 17:32:48 - Issue 2294


dev Digest 17 Mar 2023 17:32:48 - Issue 2294

Topics (messages 17647 through 17676)

Re: [Discussion] ASF Booth at FOSSASIA 2023
17647 by: Navendu Pottekkat

Re: [ALC] Request to establish ALC in Xi'an
17648 by: Xin Wang
17665 by: Yuanhao Ji

Re: Back to basics: What we do @comdev
17649 by: sebb
17651 by: rbowen.rcbowen.com
17653 by: Jim Jagielski
17655 by: Drew Foulks
17658 by: rbowen.rcbowen.com
17659 by: rbowen.rcbowen.com

[GitHub] [comdev-site] rbowen commented on pull request #87: Remove references 
to helpwanted
17650 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen merged pull request #87: Remove references to 
helpwanted
17652 by: rbowen (via GitHub)

[jira] [Resolved] (COMDEV-384) Tasks in the help page seems to have not been 
updated for a long time
17654 by: Sebb (Jira)

[GitHub] [comdev-site] rbowen opened a new pull request, #88: Remove some 
things we don't actually do
17656 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen merged pull request #88: Remove some things we 
don't actually do
17657 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen opened a new pull request, #89: The speakers 
tool, at community.zones.apache.org, has been abandoned for
17660 by: rbowen (via GitHub)

tika-offheap-leak
17661 by: 朱桂锋
17662 by: rbowen.rcbowen.com
17664 by: 朱桂锋

[jira] [Commented] (COMDEV-227) Only list last X releases and the add/remove 
release page
17663 by: Sebb (Jira)

[GitHub] [comdev-site] rbowen opened a new pull request, #90: Advice for 
becoming a committer.
17666 by: rbowen (via GitHub)

[GitHub] [comdev-site] mjfoulks opened a new pull request, #91: Update 
etiquette.md
17667 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen commented on pull request #91: Update etiquette.md
17668 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen merged pull request #91: Update etiquette.md
17669 by: rbowen (via GitHub)

[GitHub] [comdev-site] mjfoulks opened a new pull request, #92: Update _index.md
17670 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen opened a new pull request, #93: Remove mentoring 
section
17671 by: rbowen (via GitHub)

[GitHub] [comdev-site] rbowen merged pull request #92: Update _index.md
17672 by: rbowen (via GitHub)

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #89: The speakers 
tool, at community.zones.apache.org, has been abandoned for
17673 by: rbowen (via GitHub)

[GitHub] [comdev-site] ShaneCurcuru merged pull request #89: The speakers tool, 
at community.zones.apache.org, has been abandoned for
17674 by: rbowen (via GitHub)

[GitHub] [comdev-site] mjfoulks opened a new pull request, #94: Update 
etiquette.md
17675 by: rbowen (via GitHub)

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #94: Update 
etiquette.md
17676 by: rbowen (via GitHub)

Administrivia:

-
To post to the list, e-mail: dev@community.apache.org
To unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org
For additional commands, e-mail: dev-digest-h...@community.apache.org

--

Re: dev Digest 17 Mar 2023 17:32:48 -0000 Issue 2294

[rbowen]

On Fri, 2023-03-17 at 19:14 +, Donavon Gamblin wrote:
> 
> o unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org
> 
> i need unsubscribed asap

The instructions are in the email that you sent:

> To unsubscribe, e-mail: dev-digest-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-digest-h...@community.apache.org

--Rich

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[GitHub] [comdev-site] ShaneCurcuru merged pull request #93: Remove mentoring section

[via GitHub]

ShaneCurcuru merged PR #93:
URL: https://github.com/apache/comdev-site/pull/93


-- 
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

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #64: Send GitBox notifications to separate list

[via GitHub]

ShaneCurcuru commented on PR #64:
URL: https://github.com/apache/comdev-site/pull/64#issuecomment-1474512788

   Given the new energy around updating the ComDev website, this should be 
revisited, along with the work to move GSOC issues to a separate JIRA/separate 
mailing list.  I.e. what overall mailing lists with these automated 
notifications do we want?  Just notifications@ for both GSOC and COMDEV jiras 
and GitBox emails?  Or is GSOC separate and deserves it's own gsoc-something@ 
lists?


-- 
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

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #42: Update mentoringprogramme.md

[via GitHub]

ShaneCurcuru commented on PR #42:
URL: https://github.com/apache/comdev-site/pull/42#issuecomment-1474513382

   The mentoring programme is effectively defunct, so changes here are 
pointless.  If we get sufficient energy to revive it, we can create it again.


-- 
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

[GitHub] [comdev-site] ShaneCurcuru closed pull request #42: Update mentoringprogramme.md

[via GitHub]

ShaneCurcuru closed pull request #42: Update mentoringprogramme.md
URL: https://github.com/apache/comdev-site/pull/42


-- 
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

[GitHub] [comdev-site] ShaneCurcuru commented on pull request #31: Update funding-disclaimer.md

[via GitHub]

ShaneCurcuru commented on PR #31:
URL: https://github.com/apache/comdev-site/pull/31#issuecomment-1474514196

   Thanks for the tweaks, sorry for the delay.


-- 
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

[GitHub] [comdev-site] ShaneCurcuru merged pull request #31: Update funding-disclaimer.md

[via GitHub]

ShaneCurcuru merged PR #31:
URL: https://github.com/apache/comdev-site/pull/31


-- 
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

[GitHub] [comdev-site] ShaneCurcuru merged pull request #53: Update decisionMaking.md

[via GitHub]

ShaneCurcuru merged PR #53:
URL: https://github.com/apache/comdev-site/pull/53


-- 
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

[GitHub] [comdev-site] sebbASF commented on pull request #64: Send GitBox notifications to separate list

[via GitHub]

sebbASF commented on PR #64:
URL: https://github.com/apache/comdev-site/pull/64#issuecomment-1474519180

   I think GSOC should have its own list. I suggest:
   
   general@ for community discussion
   tools@ for projects/reporter etc
   gsoc@ for all things GSOC
   issues@ for COMDEV Jiras
   
   I think it would be best to drop dev@ in the long term.


-- 
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