Re: Google Summer of Code 2018 Mentor Registration

[吴晟 Sheng Wu]

Also, I can't find the mail list(ment...@community.apache.org) from 
https://lists.apache.org/


I am using this foxmail address to sub mentors mail list, is this the reason?


--
Sheng Wu
Apache SkyWalking creator and PPMC member


 




-- Original --
From:  "吴晟 Sheng Wu";
Date:  Sun, Feb 25, 2018 08:26 AM
To:  "mentors";"uli";
Cc:  "dev"; 
Subject:  Re: Google Summer of Code 2018 Mentor Registration



Hi, I have tried to subscribe the ment...@community.apache.org , and 
received/confirmed the mail. But nothing more happened.


I also send this mail to the mail list:
--
SkyWalking PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2018 
projects for Apache
SkyWalking.

I would like to receive the mentor invite to wush...@apache.org


And I already start a ticket for GSoC student: 
https://issues.apache.org/jira/browse/COMDEV-247 in that topic.  A student from 
Tongji University, China, has been interested in that topic.

--


But I only received the mail returned from skywalking private mail list: 
priv...@skywalking.apache.org


Can some one help me out? Is there anything wrong?




--
Sheng Wu
Apache SkyWalking creator and PPMC member


 




-- Original --
From:  "Ulrich Stärk";
Date:  Sun, Feb 25, 2018 05:19 AM
To:  "mentors";
Cc:  "dev@community.apache.org"; 
Subject:  Google Summer of Code 2018 Mentor Registration



Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted 
organizations for
Google Summer of Code 2018! [1,2]

It is now time for mentors to sign up, so please pass this email on to your 
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org you 
should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and PMC 
acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor 
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will use 
the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to ensure 
the mentor is in good
standing with the community. When you receive a request for acknowledgement, 
please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my previous 
emails for details).
Students will now begin to explore ideas so if you haven’t already done so, 
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2018 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2018 
projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5718432427802624/
[3] https://summerofcode.withgoogle.com/

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

Re: Google Summer of Code 2018 Mentor Registration

[吴晟 Sheng Wu]

Hi, I have tried to subscribe the ment...@community.apache.org , and 
received/confirmed the mail. But nothing more happened.


I also send this mail to the mail list:
--
SkyWalking PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2018 
projects for Apache
SkyWalking.

I would like to receive the mentor invite to wush...@apache.org


And I already start a ticket for GSoC student: 
https://issues.apache.org/jira/browse/COMDEV-247 in that topic.  A student from 
Tongji University, China, has been interested in that topic.

--


But I only received the mail returned from skywalking private mail list: 
priv...@skywalking.apache.org


Can some one help me out? Is there anything wrong?




--
Sheng Wu
Apache SkyWalking creator and PPMC member


 




-- Original --
From:  "Ulrich Stärk";
Date:  Sun, Feb 25, 2018 05:19 AM
To:  "mentors";
Cc:  "dev@community.apache.org"; 
Subject:  Google Summer of Code 2018 Mentor Registration



Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted 
organizations for
Google Summer of Code 2018! [1,2]

It is now time for mentors to sign up, so please pass this email on to your 
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org you 
should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and PMC 
acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor 
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will use 
the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to ensure 
the mentor is in good
standing with the community. When you receive a request for acknowledgement, 
please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my previous 
emails for details).
Students will now begin to explore ideas so if you haven’t already done so, 
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2018 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2018 
projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5718432427802624/
[3] https://summerofcode.withgoogle.com/

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

Google Summer of Code 2018 Mentor Registration

[Ulrich Stärk]

Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted 
organizations for
Google Summer of Code 2018! [1,2]

It is now time for mentors to sign up, so please pass this email on to your 
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org you 
should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and PMC 
acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor 
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will use 
the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to ensure 
the mentor is in good
standing with the community. When you receive a request for acknowledgement, 
please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my previous 
emails for details).
Students will now begin to explore ideas so if you haven’t already done so, 
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2018 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2018 
projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5718432427802624/
[3] https://summerofcode.withgoogle.com/

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

Fossasia

[Rich Bowen]

We have been offered a booth Presence at the Foss Asia event which is at
the end of this month in Singapore. If you are going to be on site, and you
think you might have a few extra hours to staff a booth, please get in
touch with me as soon as possible. The event is only three weeks away, so
they need an answer pretty quickly. I will be arriving on Saturday and so
cannot do this myself. The days of the expo hall are Thursday and Friday.
Thank you.

Re: Request for Reviewers or Apache EU Roadshow

[Sharan Foga]

Hi All

Thanks very much to everyone who responded to this request . This is an update 
to let you know that I have all the reviewers I need for the Apache Roadshow 
CFP .

All reviewers should have an email from me with the details needed to start the 
review and also the deadline date to get all the reviews completed.

Thanks
Sharan

On 2018/02/21 17:42:56, Sharan Foga  wrote: 
> Hi All
> 
> The CFP for the EU Roadshow will be closing at the weekend so I am looking 
> for some volunteers to help review and rate the submissions. 
> 
> If you are interested in helping out then please follow the submit a talk 
> link to login to the CFP system for the Roadshow, and then click on the link 
> to request to be a reviewer for the event.
> 
> http://apachecon.com/euroadshow18/
> 
> Please note that for the Tomcat and Http tracks, even though you will be 
> reviewing these submissions too, I will be asking the PMCs for both projects 
> to make the final decision regarding the track content.
> 
> Thanks
> Sharan
> 
> -
> 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: Status of the Xalan-C project (is it abandoned?)

[Paul Hammant]

>
> If I fork it, I'll have to change the library name, and that will make me
> incompatible with the rest of the world--all downstream consumers including
> my own.


^ Is an assumption.

You could start with the fork on GitHub 'as is' and make one tiny addition
to the resulting linkable object. Specifically add a "-gh" to the resulting
binary name. Engage the ASF (you kind of are already) as you go.  Keep
going with that until someone has a better idea, which may include
breathing life into Xalan-C at the ASF again (or not) and consuming the
changes back. Maybe get all the contribs to the forked one to be
copyright-granted to you, so that you may later easily copyright grant (and
CLA) them to Apache.  Copyright grant isn't a exclusivity statement, by the
way. There was some kerfuffle on copyrights when *Apache Geronimo *was
created in 2003 and contributors had to rake over the history of certain
source files in order to claim "I authored this originally and later gave a
copyright grant to a legal entity, and now want to do the same to the ASF
for the same source from back then".

Not forks as such necessarily, but *libc* hs plenty of
maintained-divergence alternates - http://www.etalabs.net/compare_libcs.html

Note, I'm not an officer of the ASF it has to be said so I'm only saying
what I'd do if I personally cared enough about a library and couldn't wait
for meetings and decisions to happen.

-ph

Re: Status of the Xalan-C project (is it abandoned?)

[Roger Leigh]

On 24/02/18 13:09, Paul Hammant wrote:

GitHub heralded one fantastic thing that didn't exist before - easy forking
or a repo. That is more likely to force an 'upstream' dev team to be more
benevolent to directions of others. Perhaps because of the possibility of
mind-share shifting to the fork and away from the upstream/origin. That
divergence from the origin happens isn't a problem necessarily. I've been
doing open source for 18 years now, and the only thorny thing that remains
is trademarks (were the forker wanting to release a binary) and a lesser
honor system: "hey stop using the name of my OSS tool/lib because you're
just confusing people". Node.js and Io.js is a notable case

.

If you have your patches, then just apply them to a fork on GitHub. You
don't have to become maintainer - make that clear in the readme
 (oooh maybe
http://makeareadme.com/ applies).  Start something there and see if there
are others that want to help. One of them might become maintainer :)


It's not quite that simple when you're dealing with versioned shared 
libraries, and you yourself are making versioned shared libraries for 
others to use.  We need to be compatible with the wider ecosystem using 
these libraries.


If I fork it, I'll have to change the library name, and that will make 
me incompatible with the rest of the world--all downstream consumers 
including my own.  And the fixes won't propagate through all the various 
OS distributions without a very large effort.  I could fork it, but it's 
an option of last resort since it's easy to do, but a logistical 
nightmare to deal with the fallout.  I don't want to maintain a whole 
forked project, I want to submit a handful of essential bugfixes and 
make a new point release which benefits everyone.


I've already applied a number of these patches to various Linux 
distributions, FreeBSD ports, Mac homebrew formula etc.  We need a new 
upstream release containing these fixes, not a hard fork.



Thanks,
Roger

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

Re: Status of the Xalan-C project (is it abandoned?)

[Paul Hammant]

GitHub heralded one fantastic thing that didn't exist before - easy forking
or a repo. That is more likely to force an 'upstream' dev team to be more
benevolent to directions of others. Perhaps because of the possibility of
mind-share shifting to the fork and away from the upstream/origin. That
divergence from the origin happens isn't a problem necessarily. I've been
doing open source for 18 years now, and the only thorny thing that remains
is trademarks (were the forker wanting to release a binary) and a lesser
honor system: "hey stop using the name of my OSS tool/lib because you're
just confusing people". Node.js and Io.js is a notable case

.

If you have your patches, then just apply them to a fork on GitHub. You
don't have to become maintainer - make that clear in the readme
 (oooh maybe
http://makeareadme.com/ applies).  Start something there and see if there
are others that want to help. One of them might become maintainer :)

Status of the Xalan-C project (is it abandoned?)

[Roger Leigh]

Hi folks,

I'm not sure if this is the most appropriate list, but I'm not sure 
exactly how to proceed, so if it's wrong please redirect me to where I 
should go.


I'm a user of Apache Xerces-C++ and Xalan-C++.  Both of these projects 
haven't seen much maintenance for the last few years, and I was having 
severe problems building them on modern platforms because of the 
outdated and broken build systems these projects used.  It wasn't 
possible to build either on Windows without extensive patching of the 
Visual Studio Project/Solution files, and similar for brokenness in the 
GNU Autoconf/Automake builds, which imposed a significant maintenance 
burden upon myself and other users of these projects.


To fix this, I joined the Apache project and contributed a CMake build 
plus fixes to the Autoconf/Automake build to the Apache Xerces-C++ 
project on behalf of my employer.  There was quite a bit of interest in 
this from other users suffering from the same problems, and the active 
developer on the project was welcoming of the patches.  This was 
eventually released as Xerces-C++ 3.2.0 last year, with a 3.2.1 due 
imminently with some bugfixes for this work.


Unfortunately, I have not have the same success with the Xalan-C 
project.  Over the last two years, I have opened several tickets with 
tested patches, made several posts to the mailing lists regarding the 
same, and received zero responses.


Tickets:
  https://issues.apache.org/jira/browse/XALANC-773
  https://issues.apache.org/jira/browse/XALANC-766
  https://issues.apache.org/jira/browse/XALANC-767
  https://issues.apache.org/jira/browse/XALANC-776

Posts:
  https://marc.info/?l=xalan-dev&m=149748238016328&w=2
  https://marc.info/?l=xalan-dev&m=150228668631916&w=2
  https://marc.info/?l=xalan-dev&m=150618078013560&w=2

It's a bit of a black hole.  Looking at the SVN repository:

  Last release was 1.11: on Oct 31 2012 (5 years, 4 months)
  Last development commit: Sep 25 2013 (4 years, 5 months)

There is zero visible activity there for a long, long time.

There have been a small number of messages from the maintainer to the 
mailing list, but no actual work appears to be taking place, and without 
any replies to my tickets or posts, I'm a bit stuck.  I do need to get 
the longstanding portability bugs fixed so that I can continue to use it 
on contemporary systems without it requiring man weeks of effort 
maintaining out of tree patches which require redoing from scratch for 
every new version of Visual Studio.  Even with hand-patching I'm still 
seeing subtle misbehaviour at link time and runtime on various 
platforms; what's there simply isn't fit for purpose and the current 
situation is not tenable for us as end users.


Is there any process within the Apache project for handling dead 
projects (assuming this is the case).  I don't want to take over the 
project, I just want to submit a bunch of fixes so that we can make a 
new point release which actually works without extensive patching.  I've 
been waiting over two years for a single reply to any of my attempts at 
contact, and my patience has its limits, which is why I'm writing here 
to see if there's any way to make some actionable progress.



Many thanks,
Roger Leigh

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