Wiki confilict in April's Incubator report

[Huxing Zhang]

Hi,

It looks like there is some conflict in April's incubator report[1].

I have reverted it.

It looks like the only affected podling is Annotator.

Thinking about how can avoid it again, shall we have a preview of the
diff before saving the changes?

[1] https://wiki.apache.org/incubator/April2018

-- 
Best Regards！
Huxing

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

Re: [ANNOUNCE] Release Apache SkyWalking (incubating) version 5.0.0-alpha

[Wang Xin]

Congratulations!

Xin Wang
lovep...@hotmail.com



在 2018年4月4日，上午9:32，吴晟 Sheng Wu 
> 写道：

Hi all,


Apache SkyWalking (incubating) Team is glad to announce the first release of 
Apache SkyWalking Incubating 5.0.0-alpha


SkyWalking: APM (application performance monitor) tool for distributed systems,
especially designed for microservices, cloud native and container-based 
(Docker, Kubernetes, Mesos) architectures.
Underlying technology is a distributed tracing system.


Download Links : 
http://www.apache.org/dyn/closer.cgi/incubator/skywalking/5.0.0-alpha/


Release Notes : 
https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/CHANGES.md


SkyWalking Resources:
- Issue: https://github.com/apache/incubator-skywalking/issues
- Mailing list: 
d...@skywalkiing.incubator.apache.org
- Documents: 
https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/docs/README.md




- Apache SkyWalking (incubating) Team


=
*Disclaimer*


Apache SkyWalking (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the name of Apache
Incubator PMC. Incubation is required of all newly accepted
projects until a further review indicates that the
infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate
that the project has yet to be fully endorsed by the ASF.





--
Sheng Wu
Apache SkyWalking original creator and PPMC member

[ANNOUNCE] Release Apache SkyWalking (incubating) version 5.0.0-alpha

[???? Sheng Wu]

Hi all,


Apache SkyWalking (incubating) Team is glad to announce the first release of 
Apache SkyWalking Incubating 5.0.0-alpha


SkyWalking: APM (application performance monitor) tool for distributed systems, 
especially designed for microservices, cloud native and container-based 
(Docker, Kubernetes, Mesos) architectures. 
Underlying technology is a distributed tracing system.


Download Links : 
http://www.apache.org/dyn/closer.cgi/incubator/skywalking/5.0.0-alpha/


Release Notes : 
https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/CHANGES.md


SkyWalking Resources:
- Issue: https://github.com/apache/incubator-skywalking/issues
- Mailing list: d...@skywalkiing.incubator.apache.org
- Documents: 
https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/docs/README.md




- Apache SkyWalking (incubating) Team


=
*Disclaimer*


Apache SkyWalking (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the name of Apache
Incubator PMC. Incubation is required of all newly accepted
projects until a further review indicates that the
infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate
that the project has yet to be fully endorsed by the ASF.





--
Sheng Wu
Apache SkyWalking original creator and PPMC member

Re: [DISCUSS] Absent mentors

[Dave Fisher]

Hi -
> On Apr 2, 2018, at 11:23 AM, Mark Thomas  wrote:
> 
> On 01/04/18 21:26, Dave Fisher wrote:
>> 
>>> On Apr 1, 2018, at 1:15 PM, Shane Curcuru >> > wrote:
>>> 
>>> Jim Jagielski wrote on 4/1/18 10:19 AM:
 Would it be possible to generate a short list of all current
 mentors for all current podlings to see how many podlings
 each mentor is signed up for? That would be a good metric
 to know.
>>> 
>>> Presuming podlings.xml is kept updated:
>>> 
>>> 
>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
>>> 
>>> That now sorts by @status first, so current podlings are on top.  That's
>>> separate from whimsy cross-checks of what's listed in board reports and
>>> actual signoffs.
>> 
>> The clutch runs periodically and
>> generates 
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/clutch/clutchm.ent
>> 
>> This file has each mentor listed. There are duplicates lines when people
>> have variations on their names in the date in podlings.xml. Probably
>> there needs to be a fix to use username attribute and not the mentor
>> value in the clutch.py program.
>> 
>> I can see people in the list who probably don’t even think they are a
>> mentor to a podling.
>> 
>> Should we send a note to all mentors recorded asking if they are still
>> engaged?
> 
> That seems like a sensible first step to me. I suggest asking for
> explicit confirmation that they wish to continue as a mentor. That
> should hopefully give us a better picture of how things currently stand.

I have extracted a list of mentors, emails, and podlings as an ODS file. 
Attached:


mentor-contacts.ods
Description: application/vnd.oasis.opendocument.spreadsheet


There are 101 mentors currently on the roster.
52 have 1 podling
24 have 2 podlings
17 have 3 podlings
3 have 4 podlings
2 have 5 podlings
2 have 7 podlings
1 has 8 podlings

The next step would be to discuss the email to send.

Regards,
Dave


signature.asc
Description: Message signed with OpenPGP

Re: The role of a mentor

[Kevin A. McGrail]

Adding to the responses:

- One of the duties I try and fill as a champion / mentor is to liaison
concerns and introduce them to the way the project should self-service
their own requests.

- I also try and quell the "this stinks" because there can be push back to
the way we do things.  I have said it takes about 2-3 years for people to
really appreciate the Apache Way and making sure they don't get too
frustrated in the meantime.

Regards,
KAM

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Tue, Apr 3, 2018 at 5:42 AM, Mark Struberg 
wrote:

> +1
>
> I'd also add to the list: explaining the reasons behind some of the things
> how projects at ASF works.
> Often people new to the ASF complain about the release checks and
> procedure. When you explain them the legal impact and our quality goals and
> the community aspects then they quickly understand and even actively
> support the way we run projects.
>
> People should not do it 'the Apache way' because it is some ceremony, but
> because it actually makes a lot of sense!
>
>
> Some the interpretation of the mentor role also depends on whether oneself
> is using the project as well.
> There are projects (like NetBeans, ISIS) where I mainly help with/focus on
> legal and infra stuff.
> And there are other projects where I'm also an active committer.
> Both cases are fine. But of course as committing mentor one has a way
> deeper insight into the projects health!
>
> LieGrue,
> strub
>
>
> > Am 03.04.2018 um 08:05 schrieb Romain Manni-Bucau  >:
> >
> > Hi John,
> >
> > for me it is close to what JB described:
> >
> > 1. be there when needed (how do I create a git repo? how do I ask a
> > JIRA?Why do I need X?). Even documented, having somebody you can ask
> > more directly is often valuable.
> > 2. ensure the releases are legal (+ respect mandatory ASF rules + point
> out
> > not mandatory but recommanded rules)
> > 3. be there to remind community is important and not only code to
> prepare a
> > good graduation
> >
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github  rmannibucau> |
> > LinkedIn  | Book
> >  ee-8-high-performance>
> >
> > 2018-04-03 7:31 GMT+02:00 Jean-Baptiste Onofré :
> >
> >> Hi John,
> >>
> >> IMHO, a mentor is not necessary involved in the project
> technics/codebase
> >> (it's
> >> actually a bonus).
> >>
> >> As a mentor, I'm focusing:
> >> 1. Insure of the legal aspect of the project (ICLA/CCLA, SGA, ...)
> >> 2. Help around infra and release preparation according to Apache rules
> >> 3. Help to promote the project and build communities around
> >> 4. See if there's potential interaction with other podlings and existing
> >> TLPs
> >> 5. Help to go to graduation (following the graduation checklist)
> >> 6. (optional) Help on the contribution (codebase, website, ...)
> >>
> >> My $0.01
> >>
> >> Regards
> >> JB
> >>
> >> On 04/03/2018 12:54 AM, John D. Ament wrote:
> >>> I've been following along the absent mentors discussion.  But I'm
> >> curious,
> >>> from both an IPMC member's perspective as well as a member of a
> podling,
> >>> what roles do you see for a mentor?  What are their responsibilities to
> >> the
> >>> podling?
> >>>
> >>> We have a few things written down, and I'm not too interested in
> >> rehashing
> >>> the written version.  But what do podlings need from their mentors?
> >> Point
> >>> you in a direction to run with?  Do the apache work for the podling?
> Do
> >> we
> >>> (the ASF) need mentors to ensure that podlings are operating within
> >> certain
> >>> bounds?  Do we rely on mentors to be a read of the pulse of a podling?
> >>>
> >>> John
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: The role of a mentor

[Mark Struberg]

+1

I'd also add to the list: explaining the reasons behind some of the things how 
projects at ASF works.
Often people new to the ASF complain about the release checks and procedure. 
When you explain them the legal impact and our quality goals and the community 
aspects then they quickly understand and even actively support the way we run 
projects.

People should not do it 'the Apache way' because it is some ceremony, but 
because it actually makes a lot of sense!


Some the interpretation of the mentor role also depends on whether oneself is 
using the project as well.
There are projects (like NetBeans, ISIS) where I mainly help with/focus on 
legal and infra stuff.
And there are other projects where I'm also an active committer. 
Both cases are fine. But of course as committing mentor one has a way deeper 
insight into the projects health!

LieGrue,
strub


> Am 03.04.2018 um 08:05 schrieb Romain Manni-Bucau :
> 
> Hi John,
> 
> for me it is close to what JB described:
> 
> 1. be there when needed (how do I create a git repo? how do I ask a
> JIRA?Why do I need X?). Even documented, having somebody you can ask
> more directly is often valuable.
> 2. ensure the releases are legal (+ respect mandatory ASF rules + point out
> not mandatory but recommanded rules)
> 3. be there to remind community is important and not only code to prepare a
> good graduation
> 
> 
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
> 
> 2018-04-03 7:31 GMT+02:00 Jean-Baptiste Onofré :
> 
>> Hi John,
>> 
>> IMHO, a mentor is not necessary involved in the project technics/codebase
>> (it's
>> actually a bonus).
>> 
>> As a mentor, I'm focusing:
>> 1. Insure of the legal aspect of the project (ICLA/CCLA, SGA, ...)
>> 2. Help around infra and release preparation according to Apache rules
>> 3. Help to promote the project and build communities around
>> 4. See if there's potential interaction with other podlings and existing
>> TLPs
>> 5. Help to go to graduation (following the graduation checklist)
>> 6. (optional) Help on the contribution (codebase, website, ...)
>> 
>> My $0.01
>> 
>> Regards
>> JB
>> 
>> On 04/03/2018 12:54 AM, John D. Ament wrote:
>>> I've been following along the absent mentors discussion.  But I'm
>> curious,
>>> from both an IPMC member's perspective as well as a member of a podling,
>>> what roles do you see for a mentor?  What are their responsibilities to
>> the
>>> podling?
>>> 
>>> We have a few things written down, and I'm not too interested in
>> rehashing
>>> the written version.  But what do podlings need from their mentors?
>> Point
>>> you in a direction to run with?  Do the apache work for the podling?  Do
>> we
>>> (the ASF) need mentors to ensure that podlings are operating within
>> certain
>>> bounds?  Do we rely on mentors to be a read of the pulse of a podling?
>>> 
>>> John
>>> 
>> 
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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

Re: The role of a mentor

[Romain Manni-Bucau]

Hi John,

for me it is close to what JB described:

1. be there when needed (how do I create a git repo? how do I ask a
JIRA?Why do I need X?). Even documented, having somebody you can ask
more directly is often valuable.
2. ensure the releases are legal (+ respect mandatory ASF rules + point out
not mandatory but recommanded rules)
3. be there to remind community is important and not only code to prepare a
good graduation



Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book


2018-04-03 7:31 GMT+02:00 Jean-Baptiste Onofré :

> Hi John,
>
> IMHO, a mentor is not necessary involved in the project technics/codebase
> (it's
> actually a bonus).
>
> As a mentor, I'm focusing:
> 1. Insure of the legal aspect of the project (ICLA/CCLA, SGA, ...)
> 2. Help around infra and release preparation according to Apache rules
> 3. Help to promote the project and build communities around
> 4. See if there's potential interaction with other podlings and existing
> TLPs
> 5. Help to go to graduation (following the graduation checklist)
> 6. (optional) Help on the contribution (codebase, website, ...)
>
> My $0.01
>
> Regards
> JB
>
> On 04/03/2018 12:54 AM, John D. Ament wrote:
> > I've been following along the absent mentors discussion.  But I'm
> curious,
> > from both an IPMC member's perspective as well as a member of a podling,
> > what roles do you see for a mentor?  What are their responsibilities to
> the
> > podling?
> >
> > We have a few things written down, and I'm not too interested in
> rehashing
> > the written version.  But what do podlings need from their mentors?
> Point
> > you in a direction to run with?  Do the apache work for the podling?  Do
> we
> > (the ASF) need mentors to ensure that podlings are operating within
> certain
> > bounds?  Do we rely on mentors to be a read of the pulse of a podling?
> >
> > John
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>