[jira] [Closed] (COMDEV-269) GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations

[Shi Jinghai (Jira)]

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

Shi Jinghai closed COMDEV-269.
--
Resolution: Invalid

Close now.

> GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations
> 
>
> Key: COMDEV-269
> URL: https://issues.apache.org/jira/browse/COMDEV-269
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Major
>  Labels: Java, OFBiz, gsoc2018
>
> We can imagine business as a network, every company is a node.
> In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
> outgoing from the node to other one is AP.
> In China accounting regulations, every company has suppliers and customers. A 
> payment flow between suppliers and the company is AP, no matter it's an 
> incoming or outgoing payment. A payment flow between the company and 
> customers is AR, no matter it's an incoming or outgoing payment. The pros of 
> China accounting regulations is it's easy to understand a company's financial 
> problems, purchase too much, sales too little. The cons is it's not popular 
> and natural.
> No surprise, the balance numbers are same as the results of AR - AP are equal.
> Here are the task requirements:
> 1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
> company to use general and/or China AR/AP.
> 2. The implement should be a patch against OFBiz trunk.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Closed] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Shi Jinghai (Jira)]

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

Shi Jinghai closed COMDEV-270.
--
Resolution: Invalid

I agree with Jacques. This issue is no longer valid as it's for gsoc 2018. 
Close now.

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Jacques Le Roux (Jira)]

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

Jacques Le Roux commented on COMDEV-270:


I see no reasons to not close this issue now. BTW the last contribution to 
https://github.com/jwarby/jquery-pagewalkthrough was 5 years ago...

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Rajkumar Raiyan (Jira)]

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

Rajkumar Raiyan commented on COMDEV-270:


Thanks for your help

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Rajkumar Raiyan (Jira)]

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

Rajkumar Raiyan commented on COMDEV-270:


Thanks for your help

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Issue Comment Deleted] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Gavin (JIRA)]

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

Gavin updated COMDEV-270:
-
Comment: was deleted

(was: Hi guys. Can i get all applycation form by outomatic.)

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Vuthysean (JIRA)]

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

Vuthysean commented on COMDEV-270:
--

Hi guys. Can i get all applycation form by outomatic.

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[James johnson (JIRA)]

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

James johnson commented on COMDEV-270:
--

Yes

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-269) GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on COMDEV-269:


Hi JInghai,

Should we keep this open reading 
https://wiki.openmrs.org/display/RES/Summer+Of+Code+2018#SummerOfCode2018-ProgramTimeline
 ?

> GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations
> 
>
> Key: COMDEV-269
> URL: https://issues.apache.org/jira/browse/COMDEV-269
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Major
>  Labels: Java, OFBiz, gsoc2018
>
> We can imagine business as a network, every company is a node.
> In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
> outgoing from the node to other one is AP.
> In China accounting regulations, every company has suppliers and customers. A 
> payment flow between suppliers and the company is AP, no matter it's an 
> incoming or outgoing payment. A payment flow between the company and 
> customers is AR, no matter it's an incoming or outgoing payment. The pros of 
> China accounting regulations is it's easy to understand a company's financial 
> problems, purchase too much, sales too little. The cons is it's not popular 
> and natural.
> No surprise, the balance numbers are same as the results of AR - AP are equal.
> Here are the task requirements:
> 1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
> company to use general and/or China AR/AP.
> 2. The implement should be a patch against OFBiz trunk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on COMDEV-270:


Hi JInghai, 

Should we keep this open reading 
https://wiki.openmrs.org/display/RES/Summer+Of+Code+2018#SummerOfCode2018-ProgramTimeline
 ?

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>  Labels: gsoc2018
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-275) Apache DRAT - GSOC 2018 issues

[Sebb (JIRA)]

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

Sebb updated COMDEV-275:

Component/s: GSoC/Mentoring ideas

> Apache DRAT - GSOC 2018 issues
> --
>
> Key: COMDEV-275
> URL: https://issues.apache.org/jira/browse/COMDEV-275
> Project: Community Development
>  Issue Type: Brainstorming
>  Components: GSoC/Mentoring ideas
>Reporter: Chris A. Mattmann
>Priority: Major
>  Labels: GSoC2018, gsoc, gsoc2018
>
> The Apache DRAT project solicits new projects for GSOC 2018. You can find our 
> project list here:
>  
> [https://s.apache.org/BnDF]
>  
> Thanks,
> Chris Mattmann



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-271) GSOC 2018: AJP client library and CLI tooling

[Mark Thomas (JIRA)]

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

Mark Thomas commented on COMDEV-271:


See comment above for how to get started

> GSOC 2018: AJP client library and CLI tooling
> -
>
> Key: COMDEV-271
> URL: https://issues.apache.org/jira/browse/COMDEV-271
> Project: Community Development
>  Issue Type: Bug
>  Components: GSoC/Mentoring ideas
>Reporter: Mark Thomas
>Priority: Major
>  Labels: gsoc2018
>
> Develop an AJP client library that can be used by:
> a) Tomcat to provide a simple AJP command line tool similar to wget
> b) JMeter
> See https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 for further pointers.
> The expectation is that this would be mentored by the Apache Tomcat project 
> but would involve working with both Tomcat and JMeter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-268) GSOC 2018 SpamAssassin Statistical Classifier Plugin

[Saahil Sirowa (JIRA)]

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

Saahil Sirowa commented on COMDEV-268:
--

Hi Kevin, the bug description page mentioned in the description is not opening. 
Can you please post some alternate links to help me get information about it. I 
would like to know what sort of functionality you will be expecting at the end 
of the project.

> GSOC 2018 SpamAssassin Statistical Classifier Plugin
> 
>
> Key: COMDEV-268
> URL: https://issues.apache.org/jira/browse/COMDEV-268
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>  Labels: gsoc2018
>
> As discussed in 2015 at 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7287,] this idea was 
> ideal for GSOC but there was a problem with a deadline missed. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-268) GSOC 2018 SpamAssassin Statistical Classifier Plugin

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail commented on COMDEV-268:
-

Hi Saahil, nice to meet you.  Working on the Apache SpamAssassin project 
especially on a statistical classifier is an excellent choice for a student 
GSOC student.

For this and the ticket 267 that you also expressed interest in, you'll want to 
email with me on the 
[d...@spamassassin.apache.org|mailto:d...@spamassassin.apache.org] mailing 
list.  That way you can engage the entire community.  
https://wiki.apache.org/spamassassin/MailingLists

 

After that:

1st step is to go to [https://community.apache.org/gsoc.html] and make sure you 
read the "Students Read this Section"

2nd step is discussion and to start drafting your proposal. 

 

Regards,

KAM

> GSOC 2018 SpamAssassin Statistical Classifier Plugin
> 
>
> Key: COMDEV-268
> URL: https://issues.apache.org/jira/browse/COMDEV-268
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>  Labels: gsoc2018
>
> As discussed in 2015 at 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7287,] this idea was 
> ideal for GSOC but there was a problem with a deadline missed. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Re: registering as a mentor for GSoC 2018

[Maxim Solodovnik]

Hello,

1) it's neve too late (c) :)))
2) please subscribe to mentors@community.a.o
3) send request to mentors@, private@yourproject.a.o
4) get ACK

we will send you invitation

This process is described in original email from Uli
http://mail-archives.apache.org/mod_mbox/avro-dev/201803.mbox/%3ccafk5+rlcdoxp4ch6kztoq7a3hgoxopstygkh4a+zshr1ghu...@mail.gmail.com%3E


On Mon, Mar 12, 2018 at 4:26 PM, Radu Cotescu  wrote:

> Hello,
>
> I've followed the steps from [1] and [2] to register as a mentor, however I
> have a few questions:
>
> 1. is it too late to register as a mentor for this year's GSoC?
> 2. how does a mentor register with the GSoC webapp?
>
> Thanks,
> Radu
>
> P.S. I know I still have to email the PMC of the project for which I intend
> to become a mentor.
>
> [1] - http://community.apache.org/gsoc.html
> [2] - http://community.apache.org/guide-to-being-a-mentor.html
>



-- 
WBR
Maxim aka solomax

registering as a mentor for GSoC 2018

[Radu Cotescu]

Hello,

I've followed the steps from [1] and [2] to register as a mentor, however I
have a few questions:

1. is it too late to register as a mentor for this year's GSoC?
2. how does a mentor register with the GSoC webapp?

Thanks,
Radu

P.S. I know I still have to email the PMC of the project for which I intend
to become a mentor.

[1] - http://community.apache.org/gsoc.html
[2] - http://community.apache.org/guide-to-being-a-mentor.html

[jira] [Comment Edited] (COMDEV-267) GSOC 2018 SpamAssassin Improve Headers for RBL research

[Saahil Sirowa (JIRA)]

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

Saahil Sirowa edited comment on COMDEV-267 at 3/11/18 11:33 PM:


Hello, I m Computer Science and Engineering student at IITH. I would like to 
work on this project for GSoC. Can you help me get started?


was (Author: ssirowa):
Hello, I would like to work on this project for GSoC. Can you help me get 
started?

> GSOC 2018 SpamAssassin Improve Headers for RBL research
> ---
>
> Key: COMDEV-267
> URL: https://issues.apache.org/jira/browse/COMDEV-267
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>  Labels: gsoc2018
>
> add subtests to headers for SA for logging / research purposes
> parse out URIs from $report _URIDOMAINS(,)_ list
> add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ 
> subtests=_SUBTESTS_ autolearn=_AUTOLEARN_ version=_VERSION_
> logic such as a tflag describe an RBL and then have rbls=_RBLS_.  So every 
> rbl test for PCCC will have a tflag that gives it a name like PCCC even if I 
> have 20 tests.  Same for URIBL or SURBL or SpamHause.  So the 
> rbls=PCCC,SURBL,URIBL as an overarching hit about which RBL hit.
> With this we can better identify overlap of RBLs.
> Also, it appears that URIDOMAINS(,)_ is not being interpolated in report 
> body. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Comment Edited] (COMDEV-268) GSOC 2018 SpamAssassin Statistical Classifier Plugin

[Saahil Sirowa (JIRA)]

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

Saahil Sirowa edited comment on COMDEV-268 at 3/11/18 11:32 PM:


Hello, I m Computer Science and Engineering student at IITH. I would like to 
work on this project for GSoC. Can you help me get started?


was (Author: ssirowa):
Hello, I would like to work on this project for GSoC. Can you help me get 
started?

> GSOC 2018 SpamAssassin Statistical Classifier Plugin
> 
>
> Key: COMDEV-268
> URL: https://issues.apache.org/jira/browse/COMDEV-268
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>  Labels: gsoc2018
>
> As discussed in 2015 at 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7287,] this idea was 
> ideal for GSOC but there was a problem with a deadline missed. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-267) GSOC 2018 SpamAssassin Improve Headers for RBL research

[Saahil Sirowa (JIRA)]

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

Saahil Sirowa commented on COMDEV-267:
--

Hello, I would like to work on this project for GSoC. Can you help me get 
started?

> GSOC 2018 SpamAssassin Improve Headers for RBL research
> ---
>
> Key: COMDEV-267
> URL: https://issues.apache.org/jira/browse/COMDEV-267
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>  Labels: gsoc2018
>
> add subtests to headers for SA for logging / research purposes
> parse out URIs from $report _URIDOMAINS(,)_ list
> add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ 
> subtests=_SUBTESTS_ autolearn=_AUTOLEARN_ version=_VERSION_
> logic such as a tflag describe an RBL and then have rbls=_RBLS_.  So every 
> rbl test for PCCC will have a tflag that gives it a name like PCCC even if I 
> have 20 tests.  Same for URIBL or SURBL or SpamHause.  So the 
> rbls=PCCC,SURBL,URIBL as an overarching hit about which RBL hit.
> With this we can better identify overlap of RBLs.
> Also, it appears that URIDOMAINS(,)_ is not being interpolated in report 
> body. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-268) GSOC 2018 SpamAssassin Statistical Classifier Plugin

[Saahil Sirowa (JIRA)]

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

Saahil Sirowa commented on COMDEV-268:
--

Hello, I would like to work on this project for GSoC. Can you help me get 
started?

> GSOC 2018 SpamAssassin Statistical Classifier Plugin
> 
>
> Key: COMDEV-268
> URL: https://issues.apache.org/jira/browse/COMDEV-268
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>  Labels: gsoc2018
>
> As discussed in 2015 at 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7287,] this idea was 
> ideal for GSOC but there was a problem with a deadline missed. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-271) GSOC 2018: AJP client library and CLI tooling

[Milan Karunarathne (JIRA)]

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

Milan Karunarathne commented on COMDEV-271:
---

I'm Milan Karunarathne and a student at Information Technology, University of 
Moratuwa, Sri Lanka. I participated in GSoC 2015 and completed my project on 
OpenMRS successfully. I'm interesting in contributing to "AJP client library 
and CLI tooling" during GSoC 2018 program and like to implement that idea.

Thanks

> GSOC 2018: AJP client library and CLI tooling
> -
>
> Key: COMDEV-271
> URL: https://issues.apache.org/jira/browse/COMDEV-271
> Project: Community Development
>  Issue Type: Bug
>  Components: GSoC/Mentoring ideas
>Reporter: Mark Thomas
>Priority: Major
>  Labels: gsoc2018
>
> Develop an AJP client library that can be used by:
> a) Tomcat to provide a simple AJP command line tool similar to wget
> b) JMeter
> See https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 for further pointers.
> The expectation is that this would be mentored by the Apache Tomcat project 
> but would involve working with both Tomcat and JMeter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-271) GSOC 2018: AJP client library and CLI tooling

[Mark Thomas (JIRA)]

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

Mark Thomas commented on COMDEV-271:


Hi.

For more details and some background, take a look at the Bugzilla issue in the 
description.

To start contributing you should:
- subscribe to d...@tomcat.apache.org (http://tomcat.apache.org/lists)
- subscribe to d...@jmeter.apache.org (http://jmeter.apache.org/mail.html)
- sign up for a ASF Bugzilla account

Step one is introduce yourself to the mailing lists.

The step 2 will be to draft an API. For that, you'll probably want to use the 
Tomcat wiki so sign up for an account there (cwiki.apache.org) and ask on the 
Tomcat dev list for edit privs for the wiki. Look at the code linked from the 
BZ issue for ideas. Keep in mind that we need to be able to send invalid as 
well as valid data via this API. Put some ideas together and ask for feedback.

I'm sure you'll have lots of questions as you go. Just ask on the 
dev@tomcat.a.o list.

> GSOC 2018: AJP client library and CLI tooling
> -
>
> Key: COMDEV-271
> URL: https://issues.apache.org/jira/browse/COMDEV-271
> Project: Community Development
>  Issue Type: Bug
>  Components: GSoC/Mentoring ideas
>Reporter: Mark Thomas
>Priority: Major
>  Labels: gsoc2018
>
> Develop an AJP client library that can be used by:
> a) Tomcat to provide a simple AJP command line tool similar to wget
> b) JMeter
> See https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 for further pointers.
> The expectation is that this would be mentored by the Apache Tomcat project 
> but would involve working with both Tomcat and JMeter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (COMDEV-271) GSOC 2018: AJP client library and CLI tooling

[Hishan Indrajith (JIRA)]

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

Hishan Indrajith commented on COMDEV-271:
-

Hello, I am Hishan Indrajith Adikari from Sri Lanka. I am currently a third 
year Computer Engineering undergraduate at faculty of Engineering, University 
of Peradeniya. I want to work on this project ("AJP client library and CLI 
tooling") for GSoC 2018. I have worked with java and tomcat. 

I would like to know more details about the project and how should I start 
contributing.

> GSOC 2018: AJP client library and CLI tooling
> -
>
> Key: COMDEV-271
> URL: https://issues.apache.org/jira/browse/COMDEV-271
> Project: Community Development
>  Issue Type: Bug
>  Components: GSoC/Mentoring ideas
>Reporter: Mark Thomas
>Priority: Major
>  Labels: gsoc2018
>
> Develop an AJP client library that can be used by:
> a) Tomcat to provide a simple AJP command line tool similar to wget
> b) JMeter
> See https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 for further pointers.
> The expectation is that this would be mentored by the Apache Tomcat project 
> but would involve working with both Tomcat and JMeter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Resolved] (COMDEV-271) GSOC 2018: AJP client library and CLI tooling

[Mark Thomas (JIRA)]

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

Mark Thomas resolved COMDEV-271.

Resolution: Duplicate

> GSOC 2018: AJP client library and CLI tooling
> -
>
> Key: COMDEV-271
> URL: https://issues.apache.org/jira/browse/COMDEV-271
> Project: Community Development
>  Issue Type: Bug
>  Components: GSoC/Mentoring ideas
>Reporter: Mark Thomas
>Priority: Major
>  Labels: gsoc2018
>
> Develop an AJP client library that can be used by:
> a) Tomcat to provide a simple AJP command line tool similar to wget
> b) JMeter
> See https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 for further pointers.
> The expectation is that this would be mentored by the Apache Tomcat project 
> but would involve working with both Tomcat and JMeter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-271) GSOC 2018: AJP client library and CLI tooling

[Mark Thomas (JIRA)]

Mark Thomas created COMDEV-271:
--

 Summary: GSOC 2018: AJP client library and CLI tooling
 Key: COMDEV-271
 URL: https://issues.apache.org/jira/browse/COMDEV-271
 Project: Community Development
  Issue Type: Bug
  Components: GSoC/Mentoring ideas
Reporter: Mark Thomas


Develop an AJP client library that can be used by:
a) Tomcat to provide a simple AJP command line tool similar to wget
b) JMeter

See https://bz.apache.org/bugzilla/show_bug.cgi?id=47242 for further pointers.

The expectation is that this would be mentored by the Apache Tomcat project but 
would involve working with both Tomcat and JMeter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-260) GSOC 2018 SpamAssassin Bayes Token ID

[Mark Thomas (JIRA)]

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

Mark Thomas updated COMDEV-260:
---
Component/s: GSoC/Mentoring ideas

> GSOC 2018 SpamAssassin Bayes Token ID
> -
>
> Key: COMDEV-260
> URL: https://issues.apache.org/jira/browse/COMDEV-260
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> From Diane F Skoll idea (used with permission):
> We tokenize inbound messages and store the tokens on the server. In each 
> message, we add links for doing training. When you click on a training link, 
> the system trains the message based on the tokens stored on the server. In 
> that way, you are training using exactly the tokens that the Bayes code saw.
> For SA, the key point is a framework to store the Bayesian tokens from the 
> email before delivery of the email so later, a "this is spam" "this is ham" 
> mechanism can take advantage of that information without having the entire 
> email.
> Adding a header with the message id for the storage of the headers allows a 
> framework to be built for train as spam, train as ham to be more readily 
> built.
> The issues you are pointing to have to deal more with the implementation of 
> the this is spam/this is ham mechanism.
> By storing just the tokens, there is less space and privacy & legal concerns 
> are mitigated.
> sa-learn would then be extended to use the message id and learn as spam/ham 
> instead of feeding it the entire message.
>  
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Mark Thomas (JIRA)]

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

Mark Thomas updated COMDEV-270:
---
Component/s: GSoC/Mentoring ideas

> GSOC 2018 OFBiz Onpage help tool
> 
>
> Key: COMDEV-270
> URL: https://issues.apache.org/jira/browse/COMDEV-270
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Critical
>
> Sometimes we want to tell OFBiz user that we add a new important function on 
> a page he/she is viewing, or help user understand the steps on a page without 
> leaving that page.
> Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
> onpage helps, and developers can create/edit the multi-language content of 
> helps in OFBiz content component.
> The target of this task is to implement this Onpage help tool and several 
> example pages for OFBiz trunk.
>  
> 1. [https://github.com/jwarby/jquery-pagewalkthrough]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool

[Shi Jinghai (JIRA)]

Shi Jinghai created COMDEV-270:
--

 Summary: GSOC 2018 OFBiz Onpage help tool
 Key: COMDEV-270
 URL: https://issues.apache.org/jira/browse/COMDEV-270
 Project: Community Development
  Issue Type: New Feature
Reporter: Shi Jinghai


Sometimes we want to tell OFBiz user that we add a new important function on a 
page he/she is viewing, or help user understand the steps on a page without 
leaving that page.

Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of 
onpage helps, and developers can create/edit the multi-language content of 
helps in OFBiz content component.

The target of this task is to implement this Onpage help tool and several 
example pages for OFBiz trunk.

 

1. [https://github.com/jwarby/jquery-pagewalkthrough]

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-269) GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations

[Shi Jinghai (JIRA)]

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

Shi Jinghai updated COMDEV-269:
---
Description: 
We can imagine business as a network, every company is a node.

In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
outgoing from the node to other one is AP.

In China accounting regulations, every company has suppliers and customers. A 
payment flow between suppliers and the company is AP, no matter it's an 
incoming or outgoing payment. A payment flow between the company and customers 
is AR, no matter it's an incoming or outgoing payment. The pros of China 
accounting regulations is it's easy to understand a company's financial 
problems, purchase too much, sales too little. The cons is it's not popular and 
natural.

No surprise, the balance numbers are same as the results of AR - AP are equal.

Here are the task requirements:

1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
company to use general and/or China AR/AP.

2. The implement should be a patch against OFBiz trunk.

  was:
We can imagine business as a network, every company is a node.

In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
outgoing from the node to other one is AP.

In China accounting regulations, every company has suppliers and customers. A 
payment flow between suppliers and the company is AP, no matter it's an 
incoming or outgoing payment. A payment flow between the company and customers 
is AR, no matter it's an incoming or outgoing payment. The pros are that 
purchase and sales have different staff to deal with, different business rules 
to run such as contracts, payment terms and etc. The cons is it's not popular 
and natural.

No surprise, the balance numbers are same as the results of AR - AP are equal.

Here are the task requirements:

1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
company to use general and/or China AR/AP.

2. The implement should be a patch against OFBiz trunk.


> GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations
> 
>
> Key: COMDEV-269
> URL: https://issues.apache.org/jira/browse/COMDEV-269
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Major
>  Labels: Java, OFBiz, gsoc2018
>
> We can imagine business as a network, every company is a node.
> In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
> outgoing from the node to other one is AP.
> In China accounting regulations, every company has suppliers and customers. A 
> payment flow between suppliers and the company is AP, no matter it's an 
> incoming or outgoing payment. A payment flow between the company and 
> customers is AR, no matter it's an incoming or outgoing payment. The pros of 
> China accounting regulations is it's easy to understand a company's financial 
> problems, purchase too much, sales too little. The cons is it's not popular 
> and natural.
> No surprise, the balance numbers are same as the results of AR - AP are equal.
> Here are the task requirements:
> 1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
> company to use general and/or China AR/AP.
> 2. The implement should be a patch against OFBiz trunk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-269) GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations

[Shi Jinghai (JIRA)]

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

Shi Jinghai updated COMDEV-269:
---
Labels: Java OFBiz gsoc2018  (was: )

> GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations
> 
>
> Key: COMDEV-269
> URL: https://issues.apache.org/jira/browse/COMDEV-269
> Project: Community Development
>  Issue Type: New Feature
>  Components: GSoC/Mentoring ideas
>Reporter: Shi Jinghai
>Priority: Major
>  Labels: Java, OFBiz, gsoc2018
>
> We can imagine business as a network, every company is a node.
> In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
> outgoing from the node to other one is AP.
> In China accounting regulations, every company has suppliers and customers. A 
> payment flow between suppliers and the company is AP, no matter it's an 
> incoming or outgoing payment. A payment flow between the company and 
> customers is AR, no matter it's an incoming or outgoing payment. The pros are 
> that purchase and sales have different staff to deal with, different business 
> rules to run such as contracts, payment terms and etc. The cons is it's not 
> popular and natural.
> No surprise, the balance numbers are same as the results of AR - AP are equal.
> Here are the task requirements:
> 1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
> company to use general and/or China AR/AP.
> 2. The implement should be a patch against OFBiz trunk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (COMDEV-269) GSOC 2018 OFBiz Extend AR/AP to support China accounting regulations

[Shi Jinghai (JIRA)]

Shi Jinghai created COMDEV-269:
--

 Summary: GSOC 2018 OFBiz Extend AR/AP to support China accounting 
regulations
 Key: COMDEV-269
 URL: https://issues.apache.org/jira/browse/COMDEV-269
 Project: Community Development
  Issue Type: New Feature
  Components: GSoC/Mentoring ideas
Reporter: Shi Jinghai


We can imagine business as a network, every company is a node.

In current OFBiz AR/AP model, a payment incoming to the node is AR, a payment 
outgoing from the node to other one is AP.

In China accounting regulations, every company has suppliers and customers. A 
payment flow between suppliers and the company is AP, no matter it's an 
incoming or outgoing payment. A payment flow between the company and customers 
is AR, no matter it's an incoming or outgoing payment. The pros are that 
purchase and sales have different staff to deal with, different business rules 
to run such as contracts, payment terms and etc. The cons is it's not popular 
and natural.

No surprise, the balance numbers are same as the results of AR - AP are equal.

Here are the task requirements:

1. Extend OFBiz to support China accounting regulations, OFBiz user can set a 
company to use general and/or China AR/AP.

2. The implement should be a patch against OFBiz trunk.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-266) GSOC 2018 SpamAssassin Rule Publishing Speed

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-266:

Description: 
The SpamAssassin rules are published after a lengthy process of distributed 
checks that takes too long.  Identify ways to speed this up so rules can be 
published in 12 hours and 2x per day.

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:The SpamAssassin rules are published after a lengthy process of 
distributed checks that takes too long.  Identify ways to speed this up so 
rules can be published in 12 hours and 2x per day.


> GSOC 2018 SpamAssassin Rule Publishing Speed
> 
>
> Key: COMDEV-266
> URL: https://issues.apache.org/jira/browse/COMDEV-266
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> The SpamAssassin rules are published after a lengthy process of distributed 
> checks that takes too long.  Identify ways to speed this up so rules can be 
> published in 12 hours and 2x per day.
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-258) GSOC 2018 SpamAssassin DMARC Support

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-258:

Summary: GSOC 2018 SpamAssassin DMARC Support  (was: SpamAssassin DMARC 
Support)

> GSOC 2018 SpamAssassin DMARC Support
> 
>
> Key: COMDEV-258
> URL: https://issues.apache.org/jira/browse/COMDEV-258
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> As described in SA Bugzilla 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7189,] DMARC is an 
> important standard for email security [https://en.wikipedia.org/wiki/DMARC]
> Implementing a plugin for testing and reporting of DMARC.
> Because a plugin is not enabled by default, it is a less risky way to get 
> involved and learn the guts of email and email security.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-258) GSOC 2018 SpamAssassin DMARC Support

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-258:

Description: 
As described in SA Bugzilla 
[https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7189,] DMARC is an 
important standard for email security [https://en.wikipedia.org/wiki/DMARC]

Implementing a plugin for testing and reporting of DMARC.

Because a plugin is not enabled by default, it is a less risky way to get 
involved and learn the guts of email and email security.

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:
As described in SA Bugzilla 
[https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7189,] DMARC is an 
important standard for email security [https://en.wikipedia.org/wiki/DMARC]

Implementing a plugin for testing and reporting of DMARC.

Because a plugin is not enabled by default, it is a less risky way to get 
involved and learn the guts of email and email security.


> GSOC 2018 SpamAssassin DMARC Support
> 
>
> Key: COMDEV-258
> URL: https://issues.apache.org/jira/browse/COMDEV-258
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> As described in SA Bugzilla 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7189,] DMARC is an 
> important standard for email security [https://en.wikipedia.org/wiki/DMARC]
> Implementing a plugin for testing and reporting of DMARC.
> Because a plugin is not enabled by default, it is a less risky way to get 
> involved and learn the guts of email and email security.
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-259) GSOC 2018 SpamAssassin Size Check Improvements

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-259:

Description: 
SpamAssassin is a computationally expensive process to run.  It is more costly 
as emails get larger.

So SA has safety valves to prevent excessive usage and DoS by limiting the 
maximum size of emails processed.

Spammers sometimes try and get around this with short messages and large 
attachments to bypass scanning.

There are techniques that exist to truncate emails that are sometimes less 
effective so this task would be to identify better techniques in order such as:

For example:
 * remove attachments for scanning
 * Check size and scan if small enough
 * Truncate the message after closing any open tags
 * scan

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:
SpamAssassin is a computationally expensive process to run.  It is more costly 
as emails get larger.

So SA has safety valves to prevent excessive usage and DoS by limiting the 
maximum size of emails processed.

Spammers sometimes try and get around this with short messages and large 
attachments to bypass scanning.

There are techniques that exist to truncate emails that are sometimes less 
effective so this task would be to identify better techniques in order such as:

For example:
 * remove attachments for scanning
 * Check size and scan if small enough
 * Truncate the message after closing any open tags
 * scan


> GSOC 2018 SpamAssassin Size Check Improvements
> --
>
> Key: COMDEV-259
> URL: https://issues.apache.org/jira/browse/COMDEV-259
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> SpamAssassin is a computationally expensive process to run.  It is more 
> costly as emails get larger.
> So SA has safety valves to prevent excessive usage and DoS by limiting the 
> maximum size of emails processed.
> Spammers sometimes try and get around this with short messages and large 
> attachments to bypass scanning.
> There are techniques that exist to truncate emails that are sometimes less 
> effective so this task would be to identify better techniques in order such 
> as:
> For example:
>  * remove attachments for scanning
>  * Check size and scan if small enough
>  * Truncate the message after closing any open tags
>  * scan
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to g

[jira] [Updated] (COMDEV-267) GSOC 2018 SpamAssassin Improve Headers for RBL research

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-267:

Summary: GSOC 2018 SpamAssassin Improve Headers for RBL research  (was: 
SpamAssassin Improve Headers for RBL research)

> GSOC 2018 SpamAssassin Improve Headers for RBL research
> ---
>
> Key: COMDEV-267
> URL: https://issues.apache.org/jira/browse/COMDEV-267
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> add subtests to headers for SA for logging / research purposes
> parse out URIs from $report _URIDOMAINS(,)_ list
> add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ 
> subtests=_SUBTESTS_ autolearn=_AUTOLEARN_ version=_VERSION_
> logic such as a tflag describe an RBL and then have rbls=_RBLS_.  So every 
> rbl test for PCCC will have a tflag that gives it a name like PCCC even if I 
> have 20 tests.  Same for URIBL or SURBL or SpamHause.  So the 
> rbls=PCCC,SURBL,URIBL as an overarching hit about which RBL hit.
> With this we can better identify overlap of RBLs.
> Also, it appears that URIDOMAINS(,)_ is not being interpolated in report 
> body. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-267) GSOC 2018 SpamAssassin Improve Headers for RBL research

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-267:

Description: 
add subtests to headers for SA for logging / research purposes

parse out URIs from $report _URIDOMAINS(,)_ list

add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ 
subtests=_SUBTESTS_ autolearn=_AUTOLEARN_ version=_VERSION_

logic such as a tflag describe an RBL and then have rbls=_RBLS_.  So every rbl 
test for PCCC will have a tflag that gives it a name like PCCC even if I have 
20 tests.  Same for URIBL or SURBL or SpamHause.  So the rbls=PCCC,SURBL,URIBL 
as an overarching hit about which RBL hit.

With this we can better identify overlap of RBLs.

Also, it appears that URIDOMAINS(,)_ is not being interpolated in report body. 

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:
add subtests to headers for SA for logging / research purposes

parse out URIs from $report _URIDOMAINS(,)_ list

add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ 
subtests=_SUBTESTS_ autolearn=_AUTOLEARN_ version=_VERSION_

logic such as a tflag describe an RBL and then have rbls=_RBLS_.  So every rbl 
test for PCCC will have a tflag that gives it a name like PCCC even if I have 
20 tests.  Same for URIBL or SURBL or SpamHause.  So the rbls=PCCC,SURBL,URIBL 
as an overarching hit about which RBL hit.

With this we can better identify overlap of RBLs.

Also, it appears that URIDOMAINS(,)_ is not being interpolated in report body. 


> GSOC 2018 SpamAssassin Improve Headers for RBL research
> ---
>
> Key: COMDEV-267
> URL: https://issues.apache.org/jira/browse/COMDEV-267
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> add subtests to headers for SA for logging / research purposes
> parse out URIs from $report _URIDOMAINS(,)_ list
> add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ 
> subtests=_SUBTESTS_ autolearn=_AUTOLEARN_ version=_VERSION_
> logic such as a tflag describe an RBL and then have rbls=_RBLS_.  So every 
> rbl test for PCCC will have a tflag that gives it a name like PCCC even if I 
> have 20 tests.  Same for URIBL or SURBL or SpamHause.  So the 
> rbls=PCCC,SURBL,URIBL as an overarching hit about which RBL hit.
> With this we can better identify overlap of RBLs.
> Also, it appears that URIDOMAINS(,)_ is not being interpolated in report 
> body. 
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distr

[jira] [Updated] (COMDEV-268) GSOC 2018 SpamAssassin Statistical Classifier Plugin

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-268:

Summary: GSOC 2018 SpamAssassin Statistical Classifier Plugin  (was: 
SpamAssassin Statistical Classifier Plugin)

> GSOC 2018 SpamAssassin Statistical Classifier Plugin
> 
>
> Key: COMDEV-268
> URL: https://issues.apache.org/jira/browse/COMDEV-268
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> As discussed in 2015 at 
> [https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7287,] this idea was 
> ideal for GSOC but there was a problem with a deadline missed. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-262) GSOC 2018 SpamAssassin tflag to bypass Body + Subject being prepended

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-262:

Description: 
tflags or test flags are a way of changing the behavior of tests in 
SpamAssassin.

In spamassassin, one test type is body but body actually prepends the subject 
to the body as well.  This behavior works very well for 99.9% of the time but 
occasionally it surprises people.

Extended the framework for a body test to have a tflag to bypass the prepending 
of the subject to the body for tests.

Alternately, change the default behavior not to add the subject with a tflag to 
add the subject with appropriate efficacy testing.

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:
tflags or test flags are a way of changing the behavior of tests in 
SpamAssassin.

In spamassassin, one test type is body but body actually prepends the subject 
to the body as well.  This behavior works very well for 99.9% of the time but 
occasionally it surprises people.

Extended the framework for a body test to have a tflag to bypass the prepending 
of the subject to the body for tests.

Alternately, change the default behavior not to add the subject with a tflag to 
add the subject with appropriate efficacy testing.


> GSOC 2018 SpamAssassin tflag to bypass Body + Subject being prepended
> -
>
> Key: COMDEV-262
> URL: https://issues.apache.org/jira/browse/COMDEV-262
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> tflags or test flags are a way of changing the behavior of tests in 
> SpamAssassin.
> In spamassassin, one test type is body but body actually prepends the subject 
> to the body as well.  This behavior works very well for 99.9% of the time but 
> occasionally it surprises people.
> Extended the framework for a body test to have a tflag to bypass the 
> prepending of the subject to the body for tests.
> Alternately, change the default behavior not to add the subject with a tflag 
> to add the subject with appropriate efficacy testing.
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that 

[jira] [Updated] (COMDEV-259) GSOC 2018 SpamAssassin Size Check Improvements

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-259:

Summary: GSOC 2018 SpamAssassin Size Check Improvements  (was: SpamAssassin 
Size Check Improvements)

> GSOC 2018 SpamAssassin Size Check Improvements
> --
>
> Key: COMDEV-259
> URL: https://issues.apache.org/jira/browse/COMDEV-259
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> SpamAssassin is a computationally expensive process to run.  It is more 
> costly as emails get larger.
> So SA has safety valves to prevent excessive usage and DoS by limiting the 
> maximum size of emails processed.
> Spammers sometimes try and get around this with short messages and large 
> attachments to bypass scanning.
> There are techniques that exist to truncate emails that are sometimes less 
> effective so this task would be to identify better techniques in order such 
> as:
> For example:
>  * remove attachments for scanning
>  * Check size and scan if small enough
>  * Truncate the message after closing any open tags
>  * scan



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-260) GSOC 2018 SpamAssassin Bayes Token ID

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-260:

Description: 
>From Diane F Skoll idea (used with permission):

We tokenize inbound messages and store the tokens on the server. In each 
message, we add links for doing training. When you click on a training link, 
the system trains the message based on the tokens stored on the server. In that 
way, you are training using exactly the tokens that the Bayes code saw.

For SA, the key point is a framework to store the Bayesian tokens from the 
email before delivery of the email so later, a "this is spam" "this is ham" 
mechanism can take advantage of that information without having the entire 
email.

Adding a header with the message id for the storage of the headers allows a 
framework to be built for train as spam, train as ham to be more readily built.

The issues you are pointing to have to deal more with the implementation of the 
this is spam/this is ham mechanism.

By storing just the tokens, there is less space and privacy & legal concerns 
are mitigated.

sa-learn would then be extended to use the message id and learn as spam/ham 
instead of feeding it the entire message.

 

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:
>From DFS idea used with permission:

We tokenize inbound messages and store the tokens on the server. In each 
message, we add links for doing training. When you click on a training link, 
the system trains the message based on the tokens stored on the server. In that 
way, you are training using exactly the tokens that the Bayes code saw. 

For SA, the key point is a framework to store the Bayesian tokens from the 
email before delivery of the email so later, a "this is spam" "this is ham" 
mechanism can take advantage of that information without having the entire 
email.

Adding a header with the message id for the storage of the headers allows a 
framework to be built for train as spam, train as ham to be more readily built.

The issues you are pointing to have to deal more with the implementation of the 
this is spam/this is ham mechanism.

By storing just the tokens, there is less space and privacy & legal concerns 
are mitigated.

sa-learn would then be extended to use the message id and learn as spam/ham 
instead of feeding it the entire message.


> GSOC 2018 SpamAssassin Bayes Token ID
> -
>
> Key: COMDEV-260
> URL: https://issues.apache.org/jira/browse/COMDEV-260
> Project: Community Development
>  Issue Type: Project
>Reporter: Kevin A. McGrail
>Priority: Major
>
> From Diane F Skoll idea (used with permission):
> We tokenize inbound messages and store the tokens on the server. In each 
> message, we add links for doing training. When you click on a training link, 
> the system trains the message based on the tokens stored on the server. In 
> that way, you are training using exactly the tokens that the Bayes code saw.
> For SA, the key point is a framework to store the Bayesian tokens from the 
> email before delivery of the email so later, a "this is spam" "this is ham" 
> mechanism can take advantage of that information without having the entire 
> email.
> Adding a header with the message id for the storage of the headers allows a 
> framework to be built for train as spam, train as ham to be more readily 
> built.
> The issues you are pointing to have to deal m

[jira] [Updated] (COMDEV-261) GSOC 2018 SpamAssassin MIMEHash RBL support for Images & Attachments

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-261:

Description: 
Continue the work on MIMEHash plugin for Image and Attachment RBL support for 
SpamAssassin.

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:Continue the work on MIMEHash plugin for Image and Attachment RBL support 
for SpamAssassin.


> GSOC 2018 SpamAssassin MIMEHash RBL support for Images & Attachments
> 
>
> Key: COMDEV-261
> URL: https://issues.apache.org/jira/browse/COMDEV-261
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> Continue the work on MIMEHash plugin for Image and Attachment RBL support for 
> SpamAssassin.
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-262) GSOC 2018 SpamAssassin tflag to bypass Body + Subject being prepended

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-262:

Summary: GSOC 2018 SpamAssassin tflag to bypass Body + Subject being 
prepended  (was: SpamAssassin tflag to bypass Body + Subject being prepended)

> GSOC 2018 SpamAssassin tflag to bypass Body + Subject being prepended
> -
>
> Key: COMDEV-262
> URL: https://issues.apache.org/jira/browse/COMDEV-262
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> tflags or test flags are a way of changing the behavior of tests in 
> SpamAssassin.
> In spamassassin, one test type is body but body actually prepends the subject 
> to the body as well.  This behavior works very well for 99.9% of the time but 
> occasionally it surprises people.
> Extended the framework for a body test to have a tflag to bypass the 
> prepending of the subject to the body for tests.
> Alternately, change the default behavior not to add the subject with a tflag 
> to add the subject with appropriate efficacy testing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-260) GSOC 2018 SpamAssassin Bayes Token ID

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-260:

Summary: GSOC 2018 SpamAssassin Bayes Token ID  (was: SpamAssassin Bayes 
Token ID)

> GSOC 2018 SpamAssassin Bayes Token ID
> -
>
> Key: COMDEV-260
> URL: https://issues.apache.org/jira/browse/COMDEV-260
> Project: Community Development
>  Issue Type: Project
>Reporter: Kevin A. McGrail
>Priority: Major
>
> From DFS idea used with permission:
> We tokenize inbound messages and store the tokens on the server. In each 
> message, we add links for doing training. When you click on a training link, 
> the system trains the message based on the tokens stored on the server. In 
> that way, you are training using exactly the tokens that the Bayes code saw. 
> For SA, the key point is a framework to store the Bayesian tokens from the 
> email before delivery of the email so later, a "this is spam" "this is ham" 
> mechanism can take advantage of that information without having the entire 
> email.
> Adding a header with the message id for the storage of the headers allows a 
> framework to be built for train as spam, train as ham to be more readily 
> built.
> The issues you are pointing to have to deal more with the implementation of 
> the this is spam/this is ham mechanism.
> By storing just the tokens, there is less space and privacy & legal concerns 
> are mitigated.
> sa-learn would then be extended to use the message id and learn as spam/ham 
> instead of feeding it the entire message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-261) GSOC 2018 SpamAssassin MIMEHash RBL support for Images & Attachments

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-261:

Summary: GSOC 2018 SpamAssassin MIMEHash RBL support for Images & 
Attachments  (was: SpamAssassin MIMEHash RBL support for Images & Attachments)

> GSOC 2018 SpamAssassin MIMEHash RBL support for Images & Attachments
> 
>
> Key: COMDEV-261
> URL: https://issues.apache.org/jira/browse/COMDEV-261
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> Continue the work on MIMEHash plugin for Image and Attachment RBL support for 
> SpamAssassin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-264) GSOC 2018 - SpamAssassin Improve TxRep

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-264:

Description: 
TxRep is a transmission tracking database to identify emails from people you 
correspond with regularly.

It needs bug fixes and performance improvements perhaps using Redis to improve 
the feature.

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:
TxRep is a transmission tracking database to identify emails from people you 
correspond with regularly.

It needs bug fixes and performance improvements perhaps using Redis to improve 
the feature.


> GSOC 2018 - SpamAssassin Improve TxRep
> --
>
> Key: COMDEV-264
> URL: https://issues.apache.org/jira/browse/COMDEV-264
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> TxRep is a transmission tracking database to identify emails from people you 
> correspond with regularly.
> It needs bug fixes and performance improvements perhaps using Redis to 
> improve the feature.
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-263) GSOC 2018 SpamAssassin reply-to and additional header framework for RBLs

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-263:

Summary: GSOC 2018 SpamAssassin reply-to and additional header framework 
for RBLs  (was: SpamAssassin reply-to and additional header framework for RBLs)

> GSOC 2018 SpamAssassin reply-to and additional header framework for RBLs
> 
>
> Key: COMDEV-263
> URL: https://issues.apache.org/jira/browse/COMDEV-263
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> Extend the RBL tests to include checks for headers such as Reply-To and to 
> include a flexible design for headers that do not exist yet.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-263) GSOC 2018 SpamAssassin reply-to and additional header framework for RBLs

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-263:

Description: 
Extend the RBL tests to include checks for headers such as Reply-To and to 
include a flexible design for headers that do not exist yet.

 

Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
email filter which uses a diverse range of tests to identify unsolicited bulk 
email, more commonly known as Spam. These tests are applied to email headers 
and content to classify email using advanced statistical methods. 

In addition, SpamAssassin has a modular architecture that allows other 
technologies to be quickly wielded against spam and is designed for easy 
integration into virtually any email system. 

It is primarily written in Perl with a few bits in C and shell scripts for 
system integration.

The compendium at 
https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
to understand some of the concepts with SpamAssassin

It will be helpful for a student in this project to understand SMTP but a 
willingness to learn and setup your own mail server on a Linux Distribution 
with SpamAssassin for a personal test domain will be very desired with 
assistance provided to get the basic framework for a sandbox for learning.

As email becomes more commodotized by major providers, knowledge of email 
systems and their security is dwindling.  This opportunity can provide 
real-world experience with an email security product that is employed by 
countless commercial systems in the world.

  was:Extend the RBL tests to include checks for headers such as Reply-To and 
to include a flexible design for headers that do not exist yet.


> GSOC 2018 SpamAssassin reply-to and additional header framework for RBLs
> 
>
> Key: COMDEV-263
> URL: https://issues.apache.org/jira/browse/COMDEV-263
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> Extend the RBL tests to include checks for headers such as Reply-To and to 
> include a flexible design for headers that do not exist yet.
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-264) GSOC 2018 - SpamAssassin Improve TxRep

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-264:

Summary: GSOC 2018 - SpamAssassin Improve TxRep  (was: SpamAssassin Improve 
TxRep)

> GSOC 2018 - SpamAssassin Improve TxRep
> --
>
> Key: COMDEV-264
> URL: https://issues.apache.org/jira/browse/COMDEV-264
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> TxRep is a transmission tracking database to identify emails from people you 
> correspond with regularly.
> It needs bug fixes and performance improvements perhaps using Redis to 
> improve the feature.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Updated] (COMDEV-265) GSOC 2018 - SpamAssassin RBL for DNS Servers

[Kevin A. McGrail (JIRA)]

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

Kevin A. McGrail updated COMDEV-265:

Summary: GSOC 2018 - SpamAssassin RBL for DNS Servers  (was: SpamAssassin 
RBL for DNS Servers)

> GSOC 2018 - SpamAssassin RBL for DNS Servers
> 
>
> Key: COMDEV-265
> URL: https://issues.apache.org/jira/browse/COMDEV-265
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Kevin A. McGrail
>Priority: Major
>
> Add RBL support for looking up DNS servers that are shared among bad actors
>  
> Apache SpamAssassin is a mail filter to identify spam. It is an intelligent 
> email filter which uses a diverse range of tests to identify unsolicited bulk 
> email, more commonly known as Spam. These tests are applied to email headers 
> and content to classify email using advanced statistical methods. 
> In addition, SpamAssassin has a modular architecture that allows other 
> technologies to be quickly wielded against spam and is designed for easy 
> integration into virtually any email system. 
> It is primarily written in Perl with a few bits in C and shell scripts for 
> system integration.
> The compendium at 
> https://raptor.pccc.com/raptor.cgim?template=email_spam_compendium is helpful 
> to understand some of the concepts with SpamAssassin
> It will be helpful for a student in this project to understand SMTP but a 
> willingness to learn and setup your own mail server on a Linux Distribution 
> with SpamAssassin for a personal test domain will be very desired with 
> assistance provided to get the basic framework for a sandbox for learning.
> As email becomes more commodotized by major providers, knowledge of email 
> systems and their security is dwindling.  This opportunity can provide 
> real-world experience with an email security product that is employed by 
> countless commercial systems in the world.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Maxim Solodovnik]

Will also try to update this https://community.apache.org/gsoc.html page
later tonight 

On Mon, Jan 22, 2018 at 9:56 AM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Sure :)
> I'm on my way :))
>
> On Mon, Jan 22, 2018 at 3:38 AM, Ulrich Stärk <u...@apache.org> wrote:
>
>> Still lots of time :). I am finalizing the application, could you help
>> with the org profile Maxim?
>>
>> Cheers,
>>
>> Uli
>>
>> On 21.01.18 15:18, Maxim Solodovnik wrote:
>> > It seems we running out of time .
>> > @Uli have you applied for ASF? Shall I apply?
>> >
>> > On Thu, Jan 18, 2018 at 9:55 PM, Maxim Solodovnik <solomax...@gmail.com
>> > <mailto:solomax...@gmail.com>> wrote:
>> >
>> > Hello Uli,
>> >
>> > have you created Apache profile?
>> > Or I can do it :)
>> >
>> > On Sun, Jan 14, 2018 at 3:18 AM, Ulrich Stärk <u...@apache.org
>> <mailto:u...@apache.org>> wrote:
>> > > I happily do it again this year but as always would be happy for
>> any help I can get especially
>> > with chasing mentors ;)
>> > >
>> > > Cheers,
>> > >
>> > > Uli
>> > >
>> > >> On 13. Jan 2018, at 18:17, Maxim Solodovnik <
>> solomax...@gmail.com
>> > <mailto:solomax...@gmail.com>> wrote:
>> > >>
>> > >> Usually Uli was the main org admin.
>> > >> I can register ASF application 
>> > >>
>> > >> @Uli can you please confirm it is OK?
>> > >>
>> > >> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
>> > >> <piergior...@apache.org <mailto:piergior...@apache.org>> wrote:
>> > >>> Hi,
>> > >>>
>> > >>> I received this invitation as a mentor for renewing our
>> participation in
>> > >>> the Google Summer of Code program.
>> > >>>
>> > >>> I think that we are interested as usual, is it right?
>> > >>> Who is in charge for giving the official confirmation by our
>> side?
>> > >>>
>> > >>> Please let me know.
>> > >>> Thank you.
>> > >>>
>> > >>> Cheers,
>> > >>> PJ
>> > >>>
>> > >>> -- Forwarded message --
>> > >>> From: 'Stephanie Taylor' via Google Summer of Code Mentors
>> Announce List <
>> > >>> gsoc-mentors-annou...@googlegroups.com > gsoc-mentors-annou...@googlegroups.com>>
>> > >>> Date: 2018-01-13 0:01 GMT+01:00
>> > >>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization
>> Applications due by
>> > >>> Jan 23rd!
>> > >>> To: Google Summer of Code Mentors Announce List <
>> > >>> gsoc-mentors-annou...@googlegroups.com > gsoc-mentors-annou...@googlegroups.com>>
>> > >>>
>> > >>>
>> > >>> Hi all,
>> > >>>
>> > >>> If your open source organization is interested in being a
>> mentoring
>> > >>> organization for Google Summer of Code 2018 please be sure to
>> submit your
>> > >>> organization's application via g.co/gsoc <http://g.co/gsoc>
>> before January 23rd at 16:00 UTC.
>> > >>>
>> > >>> Organizations chosen for GSoC 2018 will be announced on
>> February 12th.
>> > >>>
>> > >>> Best,
>> > >>> Google Open Source Programs Office
>> > >>>
>> > >>> --
>> > >>> You received this message because you are subscribed to the
>> Google Groups
>> > >>> "Google Summer of Code Mentors Announce List" group.
>> > >>> To unsubscribe from this group and stop receiving emails from
>> it, send an
>> > >>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com
>> > <mailto:gsoc-mentors-announce%2bunsubscr...@googlegroups.com>.
>> > >>> Visit this group at https://groups.google.com/grou
>> p/gsoc-mentors-announce
>> > <https://groups.google.c

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Maxim Solodovnik]

Sure :)
I'm on my way :))

On Mon, Jan 22, 2018 at 3:38 AM, Ulrich Stärk <u...@apache.org> wrote:

> Still lots of time :). I am finalizing the application, could you help
> with the org profile Maxim?
>
> Cheers,
>
> Uli
>
> On 21.01.18 15:18, Maxim Solodovnik wrote:
> > It seems we running out of time .
> > @Uli have you applied for ASF? Shall I apply?
> >
> > On Thu, Jan 18, 2018 at 9:55 PM, Maxim Solodovnik <solomax...@gmail.com
> > <mailto:solomax...@gmail.com>> wrote:
> >
> > Hello Uli,
> >
> > have you created Apache profile?
> > Or I can do it :)
> >
> > On Sun, Jan 14, 2018 at 3:18 AM, Ulrich Stärk <u...@apache.org
> <mailto:u...@apache.org>> wrote:
> > > I happily do it again this year but as always would be happy for
> any help I can get especially
> > with chasing mentors ;)
> > >
> > > Cheers,
> > >
> > > Uli
> > >
> > >> On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com
> > <mailto:solomax...@gmail.com>> wrote:
> > >>
> > >> Usually Uli was the main org admin.
> > >> I can register ASF application 
> > >>
> > >> @Uli can you please confirm it is OK?
> > >>
> > >> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> > >> <piergior...@apache.org <mailto:piergior...@apache.org>> wrote:
> > >>> Hi,
> > >>>
> > >>> I received this invitation as a mentor for renewing our
> participation in
> > >>> the Google Summer of Code program.
> > >>>
> > >>> I think that we are interested as usual, is it right?
> > >>> Who is in charge for giving the official confirmation by our
> side?
> >     >>>
> > >>> Please let me know.
> > >>> Thank you.
> > >>>
> > >>> Cheers,
> > >>> PJ
> > >>>
> > >>> -- Forwarded message --
> > >>> From: 'Stephanie Taylor' via Google Summer of Code Mentors
> Announce List <
> > >>> gsoc-mentors-annou...@googlegroups.com  gsoc-mentors-annou...@googlegroups.com>>
> > >>> Date: 2018-01-13 0:01 GMT+01:00
> > >>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization
> Applications due by
> > >>> Jan 23rd!
> > >>> To: Google Summer of Code Mentors Announce List <
> > >>> gsoc-mentors-annou...@googlegroups.com  gsoc-mentors-annou...@googlegroups.com>>
> > >>>
> > >>>
> > >>> Hi all,
> > >>>
> > >>> If your open source organization is interested in being a
> mentoring
> > >>> organization for Google Summer of Code 2018 please be sure to
> submit your
> > >>> organization's application via g.co/gsoc <http://g.co/gsoc>
> before January 23rd at 16:00 UTC.
> > >>>
> > >>> Organizations chosen for GSoC 2018 will be announced on February
> 12th.
> > >>>
> > >>> Best,
> > >>> Google Open Source Programs Office
> > >>>
> > >>> --
> > >>> You received this message because you are subscribed to the
> Google Groups
> > >>> "Google Summer of Code Mentors Announce List" group.
> > >>> To unsubscribe from this group and stop receiving emails from
> it, send an
> > >>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com
> > <mailto:gsoc-mentors-announce%2bunsubscr...@googlegroups.com>.
> > >>> Visit this group at https://groups.google.com/
> group/gsoc-mentors-announce
> > <https://groups.google.com/group/gsoc-mentors-announce>.
> > >>> For more options, visit https://groups.google.com/d/optout <
> https://groups.google.com/d/optout>.
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Piergiorgio Lucidi
> > >>> Open Source Evangelist and Enterprise Information Management
> Specialist
> > >>> Mentor / PMC Member / Committer @ Apache Software Foundation
> > >>> Community Star / Wiki Gardener / Global Forum Mode

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Maxim Solodovnik]

It seems we running out of time .
@Uli have you applied for ASF? Shall I apply?

On Thu, Jan 18, 2018 at 9:55 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Hello Uli,
>
> have you created Apache profile?
> Or I can do it :)
>
> On Sun, Jan 14, 2018 at 3:18 AM, Ulrich Stärk <u...@apache.org> wrote:
> > I happily do it again this year but as always would be happy for any
> help I can get especially with chasing mentors ;)
> >
> > Cheers,
> >
> > Uli
> >
> >> On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com>
> wrote:
> >>
> >> Usually Uli was the main org admin.
> >> I can register ASF application 
> >>
> >> @Uli can you please confirm it is OK?
> >>
> >> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> >> <piergior...@apache.org> wrote:
> >>> Hi,
> >>>
> >>> I received this invitation as a mentor for renewing our participation
> in
> >>> the Google Summer of Code program.
> >>>
> >>> I think that we are interested as usual, is it right?
> >>> Who is in charge for giving the official confirmation by our side?
> >>>
> >>> Please let me know.
> >>> Thank you.
> >>>
> >>> Cheers,
> >>> PJ
> >>>
> >>> -- Forwarded message --
> >>> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce
> List <
> >>> gsoc-mentors-annou...@googlegroups.com>
> >>> Date: 2018-01-13 0:01 GMT+01:00
> >>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications
> due by
> >>> Jan 23rd!
> >>> To: Google Summer of Code Mentors Announce List <
> >>> gsoc-mentors-annou...@googlegroups.com>
> >>>
> >>>
> >>> Hi all,
> >>>
> >>> If your open source organization is interested in being a mentoring
> >>> organization for Google Summer of Code 2018 please be sure to submit
> your
> >>> organization's application via g.co/gsoc before January 23rd at 16:00
> UTC.
> >>>
> >>> Organizations chosen for GSoC 2018 will be announced on February 12th.
> >>>
> >>> Best,
> >>> Google Open Source Programs Office
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "Google Summer of Code Mentors Announce List" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an
> >>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
> >>> Visit this group at https://groups.google.com/
> group/gsoc-mentors-announce.
> >>> For more options, visit https://groups.google.com/d/optout.
> >>>
> >>>
> >>>
> >>> --
> >>> Piergiorgio Lucidi
> >>> Open Source Evangelist and Enterprise Information Management Specialist
> >>> Mentor / PMC Member / Committer @ Apache Software Foundation
> >>> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> >>> Author and Technical Reviewer @ Packt Publishing
> >>> Technical Advisory Group Member @ Microsoft
> >>> Top Community Contributor @ Crafter
> >>> Project Leader / Committer @ JBoss
> >>> https://www.open4dev.com
> >>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >> -
> >> 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
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Ulrich Stärk]

Still lots of time :). I am finalizing the application, could you help with the 
org profile Maxim?

Cheers,

Uli

On 21.01.18 15:18, Maxim Solodovnik wrote:
> It seems we running out of time .
> @Uli have you applied for ASF? Shall I apply?
> 
> On Thu, Jan 18, 2018 at 9:55 PM, Maxim Solodovnik <solomax...@gmail.com
> <mailto:solomax...@gmail.com>> wrote:
> 
> Hello Uli,
> 
> have you created Apache profile?
> Or I can do it :)
> 
> On Sun, Jan 14, 2018 at 3:18 AM, Ulrich Stärk <u...@apache.org 
> <mailto:u...@apache.org>> wrote:
> > I happily do it again this year but as always would be happy for any 
> help I can get especially
> with chasing mentors ;)
> >
> > Cheers,
> >
> > Uli
> >
> >> On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com
> <mailto:solomax...@gmail.com>> wrote:
> >>
> >> Usually Uli was the main org admin.
> >> I can register ASF application 
> >>
> >> @Uli can you please confirm it is OK?
> >>
> >> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> >> <piergior...@apache.org <mailto:piergior...@apache.org>> wrote:
> >>> Hi,
> >>>
> >>> I received this invitation as a mentor for renewing our participation 
> in
> >>> the Google Summer of Code program.
> >>>
> >>> I think that we are interested as usual, is it right?
> >>> Who is in charge for giving the official confirmation by our side?
> >>>
> >>> Please let me know.
> >>> Thank you.
> >>>
> >>> Cheers,
> >>> PJ
> >>>
> >>> -- Forwarded message --
> >>> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce 
> List <
> >>> gsoc-mentors-annou...@googlegroups.com 
> <mailto:gsoc-mentors-annou...@googlegroups.com>>
> >>> Date: 2018-01-13 0:01 GMT+01:00
> >>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications 
> due by
> >>> Jan 23rd!
> >>> To: Google Summer of Code Mentors Announce List <
> >>> gsoc-mentors-annou...@googlegroups.com 
> <mailto:gsoc-mentors-annou...@googlegroups.com>>
> >>>
> >>>
> >>> Hi all,
> >>>
> >>> If your open source organization is interested in being a mentoring
> >>> organization for Google Summer of Code 2018 please be sure to submit 
> your
> >>> organization's application via g.co/gsoc <http://g.co/gsoc> before 
> January 23rd at 16:00 UTC.
> >>>
> >>> Organizations chosen for GSoC 2018 will be announced on February 12th.
> >>>
> >>> Best,
> >>> Google Open Source Programs Office
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google 
> Groups
> >>> "Google Summer of Code Mentors Announce List" group.
> >>> To unsubscribe from this group and stop receiving emails from it, 
> send an
> >>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com
> <mailto:gsoc-mentors-announce%2bunsubscr...@googlegroups.com>.
> >>> Visit this group at 
> https://groups.google.com/group/gsoc-mentors-announce
> <https://groups.google.com/group/gsoc-mentors-announce>.
> >>> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> >>>
> >>>
> >>>
> >>> --
> >>> Piergiorgio Lucidi
> >>> Open Source Evangelist and Enterprise Information Management 
> Specialist
> >>> Mentor / PMC Member / Committer @ Apache Software Foundation
> >>> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> >>> Author and Technical Reviewer @ Packt Publishing
> >>> Technical Advisory Group Member @ Microsoft
> >>> Top Community Contributor @ Crafter
> >>> Project Leader / Committer @ JBoss
> >>> https://www.open4dev.com
> >>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> <mailto:dev-unsubscr...@community.apache.org>
> >> For additional commands, e-mail: dev-h...@community.apache.org
> <mailto:dev-h...@community.apache.org>
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> <mailto:dev-unsubscr...@community.apache.org>
> > For additional commands, e-mail: dev-h...@community.apache.org
> <mailto:dev-h...@community.apache.org>
> >
> 
> 
> 
> --
> WBR
> Maxim aka solomax
> 
> 
> 
> 
> -- 
> WBR
> Maxim aka solomax

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

Re: GSoC 2018?

[sebb]

On 19 January 2018 at 16:32, Shane Curcuru  wrote:
> sebb wrote on 1/19/18 11:01 AM:
>> On 19 January 2018 at 12:49, Daan Hoogland  wrote:
>>> Hello there,
>>>
>>> I tried to subscribe but wasn't allowed to.
>>
>> Note that it is the community@a.o mailing list that has been closed.
>> Where did you get the details from?
>
> Double-check the below: this may be a simple user typo and/or weird
> ezmlm error.
>
> How to subscribe to Apache Mailing Lists:
>
>   http://www.apache.org/foundation/mailinglists.html

Looks OK to me.

SO the question remains - where did the address come from?
There does not seem to be a reference to it anywhere on the ASF site.

>>
>>> I plan to add a few student
>>> projects to the cloudstack project board. Can I be added to any 2018 GSoC
>>> announce or discuss lists if applicable?
>>>
>>> error message:
>>> "
>>> Hi. This is the qmail-send program at apache.org.
>>> I'm afraid I wasn't able to deliver your message to the following addresses.
>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>>
>>> :
>
> Normally, you'd use dev-subscr...@community.apache.org  But it's odd if
> ezmlm assumed that meant the closed commun...@apache.org list.

Agreed

However it appears there is an ambiguity here w.r.t. the catchall addresses.
The intention was presumably to detect mails sent to community-xyz@a.o.
The bounce message was set up accordingly.

However it looks like the same file also handles mails sent to xyz@community.a.o
The bounce message is not so appropriate.

I'll raise an INFRA JIRA when that returns.

>>> This list is closed. Please see dev@community.apache.org or
>>> http://community.apache.org
>>> "
>>>
>>> --
>>> Daan
>
> --
>
> - Shane
>   https://www.apache.org/foundation/marks/resources
>
> -
> 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: GSoC 2018?

[Shane Curcuru]

sebb wrote on 1/19/18 11:01 AM:
> On 19 January 2018 at 12:49, Daan Hoogland  wrote:
>> Hello there,
>>
>> I tried to subscribe but wasn't allowed to.
> 
> Note that it is the community@a.o mailing list that has been closed.
> Where did you get the details from?

Double-check the below: this may be a simple user typo and/or weird
ezmlm error.

How to subscribe to Apache Mailing Lists:

  http://www.apache.org/foundation/mailinglists.html

> 
>> I plan to add a few student
>> projects to the cloudstack project board. Can I be added to any 2018 GSoC
>> announce or discuss lists if applicable?
>>
>> error message:
>> "
>> Hi. This is the qmail-send program at apache.org.
>> I'm afraid I wasn't able to deliver your message to the following addresses.
>> This is a permanent error; I've given up. Sorry it didn't work out.
>>
>> :

Normally, you'd use dev-subscr...@community.apache.org  But it's odd if
ezmlm assumed that meant the closed commun...@apache.org list.

>> This list is closed. Please see dev@community.apache.org or
>> http://community.apache.org
>> "
>>
>> --
>> Daan

-- 

- Shane
  https://www.apache.org/foundation/marks/resources

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

Re: GSoC 2018?

[sebb]

On 19 January 2018 at 12:49, Daan Hoogland  wrote:
> Hello there,
>
> I tried to subscribe but wasn't allowed to.

Note that it is the community@a.o mailing list that has been closed.
Where did you get the details from?

> I plan to add a few student
> projects to the cloudstack project board. Can I be added to any 2018 GSoC
> announce or discuss lists if applicable?
>
> error message:
> "
> Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> :
> This list is closed. Please see dev@community.apache.org or
> http://community.apache.org
> "
>
> --
> Daan

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

GSoC 2018?

[Daan Hoogland]

Hello there,

I tried to subscribe but wasn't allowed to. I plan to add a few student
projects to the cloudstack project board. Can I be added to any 2018 GSoC
announce or discuss lists if applicable?

​error message:
"
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
This list is closed. Please see dev@community.apache.org or
http://community.apache.org
"​

-- 
Daan

Re: Request to mentor GSoC 2018 for SkyWalking project

[Maxim Solodovnik]

AFAIK there are no rules to avoid students to contact Apache projects,
submit patches, participate in discussions etc. 

On Thu, Jan 18, 2018 at 11:06 PM, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
> Org certify first, then students submit proposal, then choose mentors, right?
>
>
>
> ---Original---
> From: "Maxim Solodovnik"<solomax...@gmail.com>
> Date: 2018/1/19 00:02:46
> To: "dev"<dev@community.apache.org>;
> Cc: "Claude Edney"<claude.ed...@yahoo.com>;
> Subject: Re: Request to mentor GSoC 2018 for SkyWalking project
>
>
> I believe this is the time to collect GSOC project ideas :))
>
> On Wed, Jan 17, 2018 at 8:18 AM, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
>> The @community.a.o is good, already subscribed. We just need to take part 
>> after students submit their proposals? right?
>>
>>
>> --
>> Sheng Wu
>> Apache SkyWalking creator and PPMC member
>>
>>
>>
>>
>>
>>
>>
>> -- Original --
>> From:  "Mark Thomas";<ma...@apache.org>;
>> Date:  Tue, Jan 16, 2018 10:23 PM
>> To:  "dev"<dev@community.apache.org>;"Maxim 
>> Solodovnik"<solomax...@gmail.com>;
>> Cc:  "吴晟 Sheng Wu"<wu.sh...@foxmail.com>; "Claude 
>> Edney"<claude.ed...@yahoo.com>;
>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>
>>
>>
>> On 16/01/18 14:21, Maxim Solodovnik wrote:
>>> My bad,
>>> I do remember the email was started with mentors@ .
>>> I perform search and sent link :(
>>
>> No problem. I've fixed that page.
>>
>> Mark
>>
>>
>>>
>>> On Tue, Jan 16, 2018 at 9:19 PM, Mark Thomas <ma...@apache.org> wrote:
>>>> On 16/01/18 13:21, 吴晟 Sheng Wu wrote:
>>>>> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. 
>>>>> Both of them reply fail
>>>>
>>>> You have been given some incorrect information (and the website needs to
>>>> be updated to). The correct list is ment...@community.apache.org and the
>>>> subscription address is:
>>>>
>>>> mentors-subscr...@community.apache.org
>>>>
>>>> Mark
>>>>
>>>>
>>>>> to me, like this:
>>>>>
>>>>>
>>>>> 
>>>>>> Hi. This is the qmail-send program at apache.org.
>>>>> I'm afraid I wasn't able to deliver your message to the following 
>>>>> addresses.
>>>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>>>>
>>>>> <ment...@apache.org>:
>>>>> Sorry, no mailbox here by that name. (#5.1.1)
>>>>>
>>>>>
>>>>> Where am I wrong?
>>>>>
>>>>>
>>>>> --
>>>>> Sheng Wu
>>>>> Apache SkyWalking creator and PPMC member
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- Original ------
>>>>> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
>>>>> Date:  Tue, Jan 16, 2018 08:59 PM
>>>>> To:  "dev"<dev@community.apache.org>;"Claude 
>>>>> Edney"<claude.ed...@yahoo.com>;
>>>>>
>>>>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>>>>
>>>>>
>>>>>
>>>>> I would subscribe and write to mentors@a.o
>>>>> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
>>>>>
>>>>> According to slots: As soon as Apache as organisation will register for 
>>>>> GSOC
>>>>> We will collect all GSOC ideas and will request slots from google.
>>>>> Please ensure you have enough mentors :)
>>>>>
>>>>> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
>>>>> <claude.ed...@yahoo.com.invalid> wrote:
>>>>>> Sheng Wu I am interested please include me Claude Edney 
>>>>>> claude.ed...@yahoo.com
>>>>>> ---

Re: Request to mentor GSoC 2018 for SkyWalking project

[???? Sheng Wu]

Org certify first, then students submit proposal, then choose mentors, right?


 
---Original---
From: "Maxim Solodovnik"<solomax...@gmail.com>
Date: 2018/1/19 00:02:46
To: "dev"<dev@community.apache.org>;
Cc: "Claude Edney"<claude.ed...@yahoo.com>;
Subject: Re: Request to mentor GSoC 2018 for SkyWalking project


I believe this is the time to collect GSOC project ideas :))

On Wed, Jan 17, 2018 at 8:18 AM,  Sheng Wu <wu.sh...@foxmail.com> wrote:
> The @community.a.o is good, already subscribed. We just need to take part 
> after students submit their proposals? right?
>
>
> --
> Sheng Wu
> Apache SkyWalking creator and PPMC member
>
>
>
>
>
>
>
> -- Original --
> From:  "Mark Thomas";<ma...@apache.org>;
> Date:  Tue, Jan 16, 2018 10:23 PM
> To:  "dev"<dev@community.apache.org>;"Maxim Solodovnik"<solomax...@gmail.com>;
> Cc:  " Sheng Wu"<wu.sh...@foxmail.com>; "Claude 
> Edney"<claude.ed...@yahoo.com>;
> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>
>
>
> On 16/01/18 14:21, Maxim Solodovnik wrote:
>> My bad,
>> I do remember the email was started with mentors@ .
>> I perform search and sent link :(
>
> No problem. I've fixed that page.
>
> Mark
>
>
>>
>> On Tue, Jan 16, 2018 at 9:19 PM, Mark Thomas <ma...@apache.org> wrote:
>>> On 16/01/18 13:21,  Sheng Wu wrote:
>>>> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. 
>>>> Both of them reply fail
>>>
>>> You have been given some incorrect information (and the website needs to
>>> be updated to). The correct list is ment...@community.apache.org and the
>>> subscription address is:
>>>
>>> mentors-subscr...@community.apache.org
>>>
>>> Mark
>>>
>>>
>>>> to me, like this:
>>>>
>>>>
>>>> 
>>>>> Hi. This is the qmail-send program at apache.org.
>>>> I'm afraid I wasn't able to deliver your message to the following 
>>>> addresses.
>>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>>>
>>>> <ment...@apache.org>:
>>>> Sorry, no mailbox here by that name. (#5.1.1)
>>>>
>>>>
>>>> Where am I wrong?
>>>>
>>>>
>>>> --
>>>> Sheng Wu
>>>> Apache SkyWalking creator and PPMC member
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -- Original --
>>>> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
>>>> Date:  Tue, Jan 16, 2018 08:59 PM
>>>> To:  "dev"<dev@community.apache.org>;"Claude 
>>>> Edney"<claude.ed...@yahoo.com>;
>>>>
>>>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>>>
>>>>
>>>>
>>>> I would subscribe and write to mentors@a.o
>>>> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
>>>>
>>>> According to slots: As soon as Apache as organisation will register for 
>>>> GSOC
>>>> We will collect all GSOC ideas and will request slots from google.
>>>> Please ensure you have enough mentors :)
>>>>
>>>> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
>>>> <claude.ed...@yahoo.com.invalid> wrote:
>>>>> Sheng Wu I am interested please include me Claude Edney 
>>>>> claude.ed...@yahoo.com
>>>>> 
>>>>> On Tue, 1/16/18,  Sheng Wu <wu.sh...@foxmail.com> wrote:
>>>>>
>>>>>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>>>>>  To: "dev" <dev@community.apache.org>
>>>>>  Date: Tuesday, January 16, 2018, 7:45 AM
>>>>>
>>>>>  Hi Apache community.
>>>>>
>>>>>
>>>>>  I am a PPMC member of Apache Incubator
>>>>>  SkyWalking project. Some students ask me to mentor them in
>>>>>  GSoC 2018, because I used to mentor for CNCF foundation last
>>>>>  year. And I think this is a great idea, SkyWalking as an
>>>&g

Re: Request to mentor GSoC 2018 for SkyWalking project

[Maxim Solodovnik]

I believe this is the time to collect GSOC project ideas :))

On Wed, Jan 17, 2018 at 8:18 AM, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
> The @community.a.o is good, already subscribed. We just need to take part 
> after students submit their proposals? right?
>
>
> --
> Sheng Wu
> Apache SkyWalking creator and PPMC member
>
>
>
>
>
>
>
> -- Original --
> From:  "Mark Thomas";<ma...@apache.org>;
> Date:  Tue, Jan 16, 2018 10:23 PM
> To:  "dev"<dev@community.apache.org>;"Maxim Solodovnik"<solomax...@gmail.com>;
> Cc:  "吴晟 Sheng Wu"<wu.sh...@foxmail.com>; "Claude 
> Edney"<claude.ed...@yahoo.com>;
> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>
>
>
> On 16/01/18 14:21, Maxim Solodovnik wrote:
>> My bad,
>> I do remember the email was started with mentors@ .
>> I perform search and sent link :(
>
> No problem. I've fixed that page.
>
> Mark
>
>
>>
>> On Tue, Jan 16, 2018 at 9:19 PM, Mark Thomas <ma...@apache.org> wrote:
>>> On 16/01/18 13:21, 吴晟 Sheng Wu wrote:
>>>> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. 
>>>> Both of them reply fail
>>>
>>> You have been given some incorrect information (and the website needs to
>>> be updated to). The correct list is ment...@community.apache.org and the
>>> subscription address is:
>>>
>>> mentors-subscr...@community.apache.org
>>>
>>> Mark
>>>
>>>
>>>> to me, like this:
>>>>
>>>>
>>>> 
>>>>> Hi. This is the qmail-send program at apache.org.
>>>> I'm afraid I wasn't able to deliver your message to the following 
>>>> addresses.
>>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>>>
>>>> <ment...@apache.org>:
>>>> Sorry, no mailbox here by that name. (#5.1.1)
>>>>
>>>>
>>>> Where am I wrong?
>>>>
>>>>
>>>> --
>>>> Sheng Wu
>>>> Apache SkyWalking creator and PPMC member
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -- Original --
>>>> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
>>>> Date:  Tue, Jan 16, 2018 08:59 PM
>>>> To:  "dev"<dev@community.apache.org>;"Claude 
>>>> Edney"<claude.ed...@yahoo.com>;
>>>>
>>>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>>>
>>>>
>>>>
>>>> I would subscribe and write to mentors@a.o
>>>> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
>>>>
>>>> According to slots: As soon as Apache as organisation will register for 
>>>> GSOC
>>>> We will collect all GSOC ideas and will request slots from google.
>>>> Please ensure you have enough mentors :)
>>>>
>>>> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
>>>> <claude.ed...@yahoo.com.invalid> wrote:
>>>>> Sheng Wu I am interested please include me Claude Edney 
>>>>> claude.ed...@yahoo.com
>>>>> 
>>>>> On Tue, 1/16/18, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
>>>>>
>>>>>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>>>>>  To: "dev" <dev@community.apache.org>
>>>>>  Date: Tuesday, January 16, 2018, 7:45 AM
>>>>>
>>>>>  Hi Apache community.
>>>>>
>>>>>
>>>>>  I am a PPMC member of Apache Incubator
>>>>>  SkyWalking project. Some students ask me to mentor them in
>>>>>  GSoC 2018, because I used to mentor for CNCF foundation last
>>>>>  year. And I think this is a great idea, SkyWalking as an
>>>>>  incubator project, need and welcome new people to join us.
>>>>>  At the same time, SkyWalking plugin mechanism is stable and
>>>>>  not too hard for student. After all, they have total 3
>>>>>  months for a simple plugin.
>>>>>
>>>>>
>>>>>  So, I want to ask the community, how
>>>>>  should SkyWalking project volunteer mentors? And how many
>>>>>  slots could we ask? Right now, there are 3 students asked
>>>>>  me. And I post a jira ticket here: 
>>>>> https://issues.apache.org/jira/browse/COMDEV-247
>>>>>
>>>>>
>>>>>  --
>>>>>  Sheng Wu
>>>>>  Apache SkyWalking creator and PPMC
>>>>>  member
>>>>>
>>>>> -
>>>>> 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
>>>
>>
>>
>>



-- 
WBR
Maxim aka solomax

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

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Maxim Solodovnik]

Hello Uli,

have you created Apache profile?
Or I can do it :)

On Sun, Jan 14, 2018 at 3:18 AM, Ulrich Stärk <u...@apache.org> wrote:
> I happily do it again this year but as always would be happy for any help I 
> can get especially with chasing mentors ;)
>
> Cheers,
>
> Uli
>
>> On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com> wrote:
>>
>> Usually Uli was the main org admin.
>> I can register ASF application 
>>
>> @Uli can you please confirm it is OK?
>>
>> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
>> <piergior...@apache.org> wrote:
>>> Hi,
>>>
>>> I received this invitation as a mentor for renewing our participation in
>>> the Google Summer of Code program.
>>>
>>> I think that we are interested as usual, is it right?
>>> Who is in charge for giving the official confirmation by our side?
>>>
>>> Please let me know.
>>> Thank you.
>>>
>>> Cheers,
>>> PJ
>>>
>>> -- Forwarded message --
>>> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce List <
>>> gsoc-mentors-annou...@googlegroups.com>
>>> Date: 2018-01-13 0:01 GMT+01:00
>>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by
>>> Jan 23rd!
>>> To: Google Summer of Code Mentors Announce List <
>>> gsoc-mentors-annou...@googlegroups.com>
>>>
>>>
>>> Hi all,
>>>
>>> If your open source organization is interested in being a mentoring
>>> organization for Google Summer of Code 2018 please be sure to submit your
>>> organization's application via g.co/gsoc before January 23rd at 16:00 UTC.
>>>
>>> Organizations chosen for GSoC 2018 will be announced on February 12th.
>>>
>>> Best,
>>> Google Open Source Programs Office
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Google Summer of Code Mentors Announce List" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/gsoc-mentors-announce.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> Piergiorgio Lucidi
>>> Open Source Evangelist and Enterprise Information Management Specialist
>>> Mentor / PMC Member / Committer @ Apache Software Foundation
>>> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
>>> Author and Technical Reviewer @ Packt Publishing
>>> Technical Advisory Group Member @ Microsoft
>>> Top Community Contributor @ Crafter
>>> Project Leader / Committer @ JBoss
>>> https://www.open4dev.com
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>> -
>> 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
>



-- 
WBR
Maxim aka solomax

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

Re: Request to mentor GSoC 2018 for SkyWalking project

[???? Sheng Wu]

The @community.a.o is good, already subscribed. We just need to take part after 
students submit their proposals? right?


--
Sheng Wu
Apache SkyWalking creator and PPMC member


 




-- Original --
From:  "Mark Thomas";<ma...@apache.org>;
Date:  Tue, Jan 16, 2018 10:23 PM
To:  "dev"<dev@community.apache.org>;"Maxim Solodovnik"<solomax...@gmail.com>;
Cc:  " Sheng Wu"<wu.sh...@foxmail.com>; "Claude 
Edney"<claude.ed...@yahoo.com>; 
Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project



On 16/01/18 14:21, Maxim Solodovnik wrote:
> My bad,
> I do remember the email was started with mentors@ .
> I perform search and sent link :(

No problem. I've fixed that page.

Mark


> 
> On Tue, Jan 16, 2018 at 9:19 PM, Mark Thomas <ma...@apache.org> wrote:
>> On 16/01/18 13:21,  Sheng Wu wrote:
>>> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. Both 
>>> of them reply fail
>>
>> You have been given some incorrect information (and the website needs to
>> be updated to). The correct list is ment...@community.apache.org and the
>> subscription address is:
>>
>> mentors-subscr...@community.apache.org
>>
>> Mark
>>
>>
>>> to me, like this:
>>>
>>>
>>> 
>>>> Hi. This is the qmail-send program at apache.org.
>>> I'm afraid I wasn't able to deliver your message to the following addresses.
>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>>
>>> <ment...@apache.org>:
>>> Sorry, no mailbox here by that name. (#5.1.1)
>>>
>>>
>>> Where am I wrong?
>>>
>>>
>>> --
>>> Sheng Wu
>>> Apache SkyWalking creator and PPMC member
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- Original --
>>> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
>>> Date:  Tue, Jan 16, 2018 08:59 PM
>>> To:  "dev"<dev@community.apache.org>;"Claude Edney"<claude.ed...@yahoo.com>;
>>>
>>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>>
>>>
>>>
>>> I would subscribe and write to mentors@a.o
>>> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
>>>
>>> According to slots: As soon as Apache as organisation will register for GSOC
>>> We will collect all GSOC ideas and will request slots from google.
>>> Please ensure you have enough mentors :)
>>>
>>> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
>>> <claude.ed...@yahoo.com.invalid> wrote:
>>>> Sheng Wu I am interested please include me Claude Edney 
>>>> claude.ed...@yahoo.com
>>>> 
>>>> On Tue, 1/16/18,  Sheng Wu <wu.sh...@foxmail.com> wrote:
>>>>
>>>>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>>>>  To: "dev" <dev@community.apache.org>
>>>>  Date: Tuesday, January 16, 2018, 7:45 AM
>>>>
>>>>  Hi Apache community.
>>>>
>>>>
>>>>  I am a PPMC member of Apache Incubator
>>>>  SkyWalking project. Some students ask me to mentor them in
>>>>  GSoC 2018, because I used to mentor for CNCF foundation last
>>>>  year. And I think this is a great idea, SkyWalking as an
>>>>  incubator project, need and welcome new people to join us.
>>>>  At the same time, SkyWalking plugin mechanism is stable and
>>>>  not too hard for student. After all, they have total 3
>>>>  months for a simple plugin.
>>>>
>>>>
>>>>  So, I want to ask the community, how
>>>>  should SkyWalking project volunteer mentors? And how many
>>>>  slots could we ask? Right now, there are 3 students asked
>>>>  me. And I post a jira ticket here: 
>>>> https://issues.apache.org/jira/browse/COMDEV-247
>>>>
>>>>
>>>>  --
>>>>  Sheng Wu
>>>>  Apache SkyWalking creator and PPMC
>>>>  member
>>>>
>>>> -
>>>> 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: Request to mentor GSoC 2018 for SkyWalking project

[Mark Thomas]

On 16/01/18 14:21, Maxim Solodovnik wrote:
> My bad,
> I do remember the email was started with mentors@ .
> I perform search and sent link :(

No problem. I've fixed that page.

Mark


> 
> On Tue, Jan 16, 2018 at 9:19 PM, Mark Thomas <ma...@apache.org> wrote:
>> On 16/01/18 13:21, 吴晟 Sheng Wu wrote:
>>> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. Both 
>>> of them reply fail
>>
>> You have been given some incorrect information (and the website needs to
>> be updated to). The correct list is ment...@community.apache.org and the
>> subscription address is:
>>
>> mentors-subscr...@community.apache.org
>>
>> Mark
>>
>>
>>> to me, like this:
>>>
>>>
>>> 
>>>> Hi. This is the qmail-send program at apache.org.
>>> I'm afraid I wasn't able to deliver your message to the following addresses.
>>> This is a permanent error; I've given up. Sorry it didn't work out.
>>>
>>> <ment...@apache.org>:
>>> Sorry, no mailbox here by that name. (#5.1.1)
>>>
>>>
>>> Where am I wrong?
>>>
>>>
>>> --
>>> Sheng Wu
>>> Apache SkyWalking creator and PPMC member
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -- Original --
>>> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
>>> Date:  Tue, Jan 16, 2018 08:59 PM
>>> To:  "dev"<dev@community.apache.org>;"Claude Edney"<claude.ed...@yahoo.com>;
>>>
>>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>>
>>>
>>>
>>> I would subscribe and write to mentors@a.o
>>> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
>>>
>>> According to slots: As soon as Apache as organisation will register for GSOC
>>> We will collect all GSOC ideas and will request slots from google.
>>> Please ensure you have enough mentors :)
>>>
>>> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
>>> <claude.ed...@yahoo.com.invalid> wrote:
>>>> Sheng Wu I am interested please include me Claude Edney 
>>>> claude.ed...@yahoo.com
>>>> 
>>>> On Tue, 1/16/18, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
>>>>
>>>>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>>>>  To: "dev" <dev@community.apache.org>
>>>>  Date: Tuesday, January 16, 2018, 7:45 AM
>>>>
>>>>  Hi Apache community.
>>>>
>>>>
>>>>  I am a PPMC member of Apache Incubator
>>>>  SkyWalking project. Some students ask me to mentor them in
>>>>  GSoC 2018, because I used to mentor for CNCF foundation last
>>>>  year. And I think this is a great idea, SkyWalking as an
>>>>  incubator project, need and welcome new people to join us.
>>>>  At the same time, SkyWalking plugin mechanism is stable and
>>>>  not too hard for student. After all, they have total 3
>>>>  months for a simple plugin.
>>>>
>>>>
>>>>  So, I want to ask the community, how
>>>>  should SkyWalking project volunteer mentors? And how many
>>>>  slots could we ask? Right now, there are 3 students asked
>>>>  me. And I post a jira ticket here: 
>>>> https://issues.apache.org/jira/browse/COMDEV-247
>>>>
>>>>
>>>>  --
>>>>  Sheng Wu
>>>>  Apache SkyWalking creator and PPMC
>>>>  member
>>>>
>>>> -
>>>> 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: Request to mentor GSoC 2018 for SkyWalking project

[Maxim Solodovnik]

My bad,
I do remember the email was started with mentors@ .
I perform search and sent link :(

On Tue, Jan 16, 2018 at 9:19 PM, Mark Thomas <ma...@apache.org> wrote:
> On 16/01/18 13:21, 吴晟 Sheng Wu wrote:
>> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. Both 
>> of them reply fail
>
> You have been given some incorrect information (and the website needs to
> be updated to). The correct list is ment...@community.apache.org and the
> subscription address is:
>
> mentors-subscr...@community.apache.org
>
> Mark
>
>
>> to me, like this:
>>
>>
>> 
>>> Hi. This is the qmail-send program at apache.org.
>> I'm afraid I wasn't able to deliver your message to the following addresses.
>> This is a permanent error; I've given up. Sorry it didn't work out.
>>
>> <ment...@apache.org>:
>> Sorry, no mailbox here by that name. (#5.1.1)
>>
>>
>> Where am I wrong?
>>
>>
>> --
>> Sheng Wu
>> Apache SkyWalking creator and PPMC member
>>
>>
>>
>>
>>
>>
>>
>> -- Original ------
>> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
>> Date:  Tue, Jan 16, 2018 08:59 PM
>> To:  "dev"<dev@community.apache.org>;"Claude Edney"<claude.ed...@yahoo.com>;
>>
>> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
>>
>>
>>
>> I would subscribe and write to mentors@a.o
>> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
>>
>> According to slots: As soon as Apache as organisation will register for GSOC
>> We will collect all GSOC ideas and will request slots from google.
>> Please ensure you have enough mentors :)
>>
>> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
>> <claude.ed...@yahoo.com.invalid> wrote:
>>> Sheng Wu I am interested please include me Claude Edney 
>>> claude.ed...@yahoo.com
>>> ----
>>> On Tue, 1/16/18, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
>>>
>>>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>>>  To: "dev" <dev@community.apache.org>
>>>  Date: Tuesday, January 16, 2018, 7:45 AM
>>>
>>>  Hi Apache community.
>>>
>>>
>>>  I am a PPMC member of Apache Incubator
>>>  SkyWalking project. Some students ask me to mentor them in
>>>  GSoC 2018, because I used to mentor for CNCF foundation last
>>>  year. And I think this is a great idea, SkyWalking as an
>>>  incubator project, need and welcome new people to join us.
>>>  At the same time, SkyWalking plugin mechanism is stable and
>>>  not too hard for student. After all, they have total 3
>>>  months for a simple plugin.
>>>
>>>
>>>  So, I want to ask the community, how
>>>  should SkyWalking project volunteer mentors? And how many
>>>  slots could we ask? Right now, there are 3 students asked
>>>  me. And I post a jira ticket here: 
>>> https://issues.apache.org/jira/browse/COMDEV-247
>>>
>>>
>>>  --
>>>  Sheng Wu
>>>  Apache SkyWalking creator and PPMC
>>>  member
>>>
>>> -
>>> 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
>



-- 
WBR
Maxim aka solomax

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

Re: Request to mentor GSoC 2018 for SkyWalking project

[Mark Thomas]

On 16/01/18 13:21,  Sheng Wu wrote:
> I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. Both 
> of them reply fail

You have been given some incorrect information (and the website needs to
be updated to). The correct list is ment...@community.apache.org and the
subscription address is:

mentors-subscr...@community.apache.org

Mark


> to me, like this:
> 
> 
> 
>> Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> 
> <ment...@apache.org>:
> Sorry, no mailbox here by that name. (#5.1.1)
> 
> 
> Where am I wrong?
> 
> 
> --
> Sheng Wu
> Apache SkyWalking creator and PPMC member
> 
> 
>  
> 
> 
> 
> 
> -- Original --
> From:  "Maxim Solodovnik";<solomax...@gmail.com>;
> Date:  Tue, Jan 16, 2018 08:59 PM
> To:  "dev"<dev@community.apache.org>;"Claude Edney"<claude.ed...@yahoo.com>;
> 
> Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project
> 
> 
> 
> I would subscribe and write to mentors@a.o
> (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
> 
> According to slots: As soon as Apache as organisation will register for GSOC
> We will collect all GSOC ideas and will request slots from google.
> Please ensure you have enough mentors :)
> 
> On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
> <claude.ed...@yahoo.com.invalid> wrote:
>> Sheng Wu I am interested please include me Claude Edney 
>> claude.ed...@yahoo.com
>> 
>> On Tue, 1/16/18,  Sheng Wu <wu.sh...@foxmail.com> wrote:
>>
>>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>>  To: "dev" <dev@community.apache.org>
>>  Date: Tuesday, January 16, 2018, 7:45 AM
>>
>>  Hi Apache community.
>>
>>
>>  I am a PPMC member of Apache Incubator
>>  SkyWalking project. Some students ask me to mentor them in
>>  GSoC 2018, because I used to mentor for CNCF foundation last
>>  year. And I think this is a great idea, SkyWalking as an
>>  incubator project, need and welcome new people to join us.
>>  At the same time, SkyWalking plugin mechanism is stable and
>>  not too hard for student. After all, they have total 3
>>  months for a simple plugin.
>>
>>
>>  So, I want to ask the community, how
>>  should SkyWalking project volunteer mentors? And how many
>>  slots could we ask? Right now, there are 3 students asked
>>  me. And I post a jira ticket here: 
>> https://issues.apache.org/jira/browse/COMDEV-247
>>
>>
>>  --
>>  Sheng Wu
>>  Apache SkyWalking creator and PPMC
>>  member
>>
>> -
>> 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: Request to mentor GSoC 2018 for SkyWalking project

[Claude Edney]

It's probably a generic mail address that you're sending the emails to see if 
you can go on the apache.org website and maybe you can find contact emails that 
can get you in touch with the correct administrators to get this up and running 
just food for thought that's all

On Tue, 1/16/18, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:

 Subject: Re:  Request to mentor GSoC 2018 for SkyWalking project
 To: "dev" <dev@community.apache.org>, "Claude Edney" <claude.ed...@yahoo.com>
 Date: Tuesday, January 16, 2018, 8:21 AM
 
 I have tried to mail ment...@apache.org,
 mentors-subscr...@apache.org.
 Both of them reply fail to me, like this:
 
 
 
 >Hi. This is the qmail-send program
 at apache.org.
 I'm afraid I wasn't able to deliver
 your message to the following addresses.
 This is a permanent error; I've given
 up. Sorry it didn't work out.
 
 <ment...@apache.org>:
 Sorry, no mailbox here by that name.
 (#5.1.1)
 
 
 Where am I wrong?
 
 
 --
 Sheng Wu
 Apache SkyWalking creator and PPMC
 member
 
 
  
 
 
 
 
 -- Original
 --
 From:  "Maxim Solodovnik";<solomax...@gmail.com>;
 Date:  Tue, Jan 16, 2018 08:59 PM
 To:  "dev"<dev@community.apache.org>;"Claude
 Edney"<claude.ed...@yahoo.com>;
 
 Subject:  Re: Request to mentor
 GSoC 2018 for SkyWalking project
 
 
 
 I would subscribe and write to mentors@a.o
 (https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)
 
 According to slots: As soon as Apache
 as organisation will register for GSOC
 We will collect all GSOC ideas and will
 request slots from google.
 Please ensure you have enough mentors
 :)
 
 On Tue, Jan 16, 2018 at 7:47 PM, Claude
 Edney
 <claude.ed...@yahoo.com.invalid>
 wrote:
 > Sheng Wu I am interested please
 include me Claude Edney claude.ed...@yahoo.com
 >
 ----
 > On Tue, 1/16/18, 吴晟 Sheng Wu
 <wu.sh...@foxmail.com>
 wrote:
 >
 >  Subject: Request to mentor
 GSoC 2018 for SkyWalking project
 >  To: "dev" <dev@community.apache.org>
 >  Date: Tuesday, January 16,
 2018, 7:45 AM
 >
 >  Hi Apache community.
 >
 >
 >  I am a PPMC member of Apache
 Incubator
 >  SkyWalking project. Some
 students ask me to mentor them in
 >  GSoC 2018, because I used to
 mentor for CNCF foundation last
 >  year. And I think this is a
 great idea, SkyWalking as an
 >  incubator project, need and
 welcome new people to join us.
 >  At the same time, SkyWalking
 plugin mechanism is stable and
 >  not too hard for student.
 After all, they have total 3
 >  months for a simple plugin.
 >
 >
 >  So, I want to ask the
 community, how
 >  should SkyWalking project
 volunteer mentors? And how many
 >  slots could we ask? Right
 now, there are 3 students asked
 >  me. And I post a jira ticket
 here: https://issues.apache.org/jira/browse/COMDEV-247
 >
 >
 >  --
 >  Sheng Wu
 >  Apache SkyWalking creator
 and PPMC
 >  member
 >
 >
 -
 > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
 > For additional commands, e-mail:
 dev-h...@community.apache.org
 >
 
 
 
 -- 
 WBR
 Maxim aka solomax
 
 -
 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: Request to mentor GSoC 2018 for SkyWalking project

[???? Sheng Wu]

I have tried to mail ment...@apache.org, mentors-subscr...@apache.org. Both of 
them reply fail to me, like this:



>Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<ment...@apache.org>:
Sorry, no mailbox here by that name. (#5.1.1)


Where am I wrong?


--
Sheng Wu
Apache SkyWalking creator and PPMC member


 




-- Original --
From:  "Maxim Solodovnik";<solomax...@gmail.com>;
Date:  Tue, Jan 16, 2018 08:59 PM
To:  "dev"<dev@community.apache.org>;"Claude Edney"<claude.ed...@yahoo.com>;

Subject:  Re: Request to mentor GSoC 2018 for SkyWalking project



I would subscribe and write to mentors@a.o
(https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)

According to slots: As soon as Apache as organisation will register for GSOC
We will collect all GSOC ideas and will request slots from google.
Please ensure you have enough mentors :)

On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
<claude.ed...@yahoo.com.invalid> wrote:
> Sheng Wu I am interested please include me Claude Edney claude.ed...@yahoo.com
> 
> On Tue, 1/16/18,  Sheng Wu <wu.sh...@foxmail.com> wrote:
>
>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>  To: "dev" <dev@community.apache.org>
>  Date: Tuesday, January 16, 2018, 7:45 AM
>
>  Hi Apache community.
>
>
>  I am a PPMC member of Apache Incubator
>  SkyWalking project. Some students ask me to mentor them in
>  GSoC 2018, because I used to mentor for CNCF foundation last
>  year. And I think this is a great idea, SkyWalking as an
>  incubator project, need and welcome new people to join us.
>  At the same time, SkyWalking plugin mechanism is stable and
>  not too hard for student. After all, they have total 3
>  months for a simple plugin.
>
>
>  So, I want to ask the community, how
>  should SkyWalking project volunteer mentors? And how many
>  slots could we ask? Right now, there are 3 students asked
>  me. And I post a jira ticket here: 
> https://issues.apache.org/jira/browse/COMDEV-247
>
>
>  --
>  Sheng Wu
>  Apache SkyWalking creator and PPMC
>  member
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>



-- 
WBR
Maxim aka solomax

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

Re: Request to mentor GSoC 2018 for SkyWalking project

[Maxim Solodovnik]

I would subscribe and write to mentors@a.o
(https://community.apache.org/guide-to-being-a-mentor.html#staying-in-touch)

According to slots: As soon as Apache as organisation will register for GSOC
We will collect all GSOC ideas and will request slots from google.
Please ensure you have enough mentors :)

On Tue, Jan 16, 2018 at 7:47 PM, Claude Edney
<claude.ed...@yahoo.com.invalid> wrote:
> Sheng Wu I am interested please include me Claude Edney claude.ed...@yahoo.com
> 
> On Tue, 1/16/18, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:
>
>  Subject: Request to mentor GSoC 2018 for SkyWalking project
>  To: "dev" <dev@community.apache.org>
>  Date: Tuesday, January 16, 2018, 7:45 AM
>
>  Hi Apache community.
>
>
>  I am a PPMC member of Apache Incubator
>  SkyWalking project. Some students ask me to mentor them in
>  GSoC 2018, because I used to mentor for CNCF foundation last
>  year. And I think this is a great idea, SkyWalking as an
>  incubator project, need and welcome new people to join us.
>  At the same time, SkyWalking plugin mechanism is stable and
>  not too hard for student. After all, they have total 3
>  months for a simple plugin.
>
>
>  So, I want to ask the community, how
>  should SkyWalking project volunteer mentors? And how many
>  slots could we ask? Right now, there are 3 students asked
>  me. And I post a jira ticket here: 
> https://issues.apache.org/jira/browse/COMDEV-247
>
>
>  --
>  Sheng Wu
>  Apache SkyWalking creator and PPMC
>  member
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>



-- 
WBR
Maxim aka solomax

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

Re: Request to mentor GSoC 2018 for SkyWalking project

[Claude Edney]

Sheng Wu I am interested please include me Claude Edney claude.ed...@yahoo.com

On Tue, 1/16/18, 吴晟 Sheng Wu <wu.sh...@foxmail.com> wrote:

 Subject: Request to mentor GSoC 2018 for SkyWalking project
 To: "dev" <dev@community.apache.org>
 Date: Tuesday, January 16, 2018, 7:45 AM
 
 Hi Apache community.
 
 
 I am a PPMC member of Apache Incubator
 SkyWalking project. Some students ask me to mentor them in
 GSoC 2018, because I used to mentor for CNCF foundation last
 year. And I think this is a great idea, SkyWalking as an
 incubator project, need and welcome new people to join us.
 At the same time, SkyWalking plugin mechanism is stable and
 not too hard for student. After all, they have total 3
 months for a simple plugin.
 
 
 So, I want to ask the community, how
 should SkyWalking project volunteer mentors? And how many
 slots could we ask? Right now, there are 3 students asked
 me. And I post a jira ticket here: 
https://issues.apache.org/jira/browse/COMDEV-247
 
 
 --
 Sheng Wu
 Apache SkyWalking creator and PPMC
 member

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

Request to mentor GSoC 2018 for SkyWalking project

[???? Sheng Wu]

Hi Apache community.


I am a PPMC member of Apache Incubator SkyWalking project. Some students ask me 
to mentor them in GSoC 2018, because I used to mentor for CNCF foundation last 
year. And I think this is a great idea, SkyWalking as an incubator project, 
need and welcome new people to join us. At the same time, SkyWalking plugin 
mechanism is stable and not too hard for student. After all, they have total 3 
months for a simple plugin.


So, I want to ask the community, how should SkyWalking project volunteer 
mentors? And how many slots could we ask? Right now, there are 3 students asked 
me. And I post a jira ticket here: 
https://issues.apache.org/jira/browse/COMDEV-247


--
Sheng Wu
Apache SkyWalking creator and PPMC member

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Piergiorgio Lucidi]

Feel free to involve me.
Happy to join again as a mentor here :)

Cheers,
PJ

2018-01-15 8:15 GMT+01:00 Kanchana Welagedara <kanch...@opensource.lk>:

> Hi there,
> I will help as well
>
> Cheers
> Kanchana
>
> On Sun, Jan 14, 2018 at 8:22 AM, Xavier Sumba <xavier.sumb...@ucuenca.ec>
> wrote:
>
> > Hi,
> >
> > I participated last year as a mentor, and I can help this year with
> > administrative issues.
> >
> > Cheers,
> > Xavier.
> >
> > On Jan 14, 2018 6:04 AM, "Sharan Foga" <sha...@apache.org> wrote:
> >
> > That's great and thanks Uli!
> >
> > And it's a good idea to get more people involved with helping out with
> any
> > admin as it shares the knowledge and workload :-)
> >
> > Thanks
> > Sharan
> >
> >
> > On 2018-01-13 21:18, Ulrich Stärk <u...@apache.org> wrote:
> > > I happily do it again this year but as always would be happy for any
> help
> > I can get especially with chasing mentors ;)
> > >
> > > Cheers,
> > >
> > > Uli
> > >
> > > > On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com>
> > wrote:
> > > >
> > > > Usually Uli was the main org admin.
> > > > I can register ASF application 
> > > >
> > > > @Uli can you please confirm it is OK?
> > > >
> > > > On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> > > > <piergior...@apache.org> wrote:
> > > >> Hi,
> > > >>
> > > >> I received this invitation as a mentor for renewing our
> participation
> > in
> > > >> the Google Summer of Code program.
> > > >>
> > > >> I think that we are interested as usual, is it right?
> > > >> Who is in charge for giving the official confirmation by our side?
> > > >>
> > > >> Please let me know.
> > > >> Thank you.
> > > >>
> > > >> Cheers,
> > > >> PJ
> > > >>
> > > >> -- Forwarded message --
> > > >> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce
> > List <
> > > >> gsoc-mentors-annou...@googlegroups.com>
> > > >> Date: 2018-01-13 0:01 GMT+01:00
> > > >> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications
> > due by
> > > >> Jan 23rd!
> > > >> To: Google Summer of Code Mentors Announce List <
> > > >> gsoc-mentors-annou...@googlegroups.com>
> > > >>
> > > >>
> > > >> Hi all,
> > > >>
> > > >> If your open source organization is interested in being a mentoring
> > > >> organization for Google Summer of Code 2018 please be sure to submit
> > your
> > > >> organization's application via g.co/gsoc before January 23rd at
> 16:00
> > UTC.
> > > >>
> > > >> Organizations chosen for GSoC 2018 will be announced on February
> 12th.
> > > >>
> > > >> Best,
> > > >> Google Open Source Programs Office
> > > >>
> > > >> --
> > > >> You received this message because you are subscribed to the Google
> > Groups
> > > >> "Google Summer of Code Mentors Announce List" group.
> > > >> To unsubscribe from this group and stop receiving emails from it,
> send
> > an
> > > >> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
> > > >> Visit this group at https://groups.google.com/
> > group/gsoc-mentors-announce.
> > > >> For more options, visit https://groups.google.com/d/optout.
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Piergiorgio Lucidi
> > > >> Open Source Evangelist and Enterprise Information Management
> > Specialist
> > > >> Mentor / PMC Member / Committer @ Apache Software Foundation
> > > >> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> > > >> Author and Technical Reviewer @ Packt Publishing
> > > >> Technical Advisory Group Member @ Microsoft
> > > >> Top Community Contributor @ Crafter
> > > >> Project Leader / Committer @ JBoss
> > > >> https://www.open4dev.com
> > > >
> > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > > >
> > > > 
> -
> > > > 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
> >
>



-- 
Piergiorgio Lucidi
Open Source Evangelist and Enterprise Information Management Specialist
Mentor / PMC Member / Committer @ Apache Software Foundation
Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
Author and Technical Reviewer @ Packt Publishing
Technical Advisory Group Member @ Microsoft
Top Community Contributor @ Crafter
Project Leader / Committer @ JBoss
https://www.open4dev.com

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Xavier Sumba]

Hi,

I participated last year as a mentor, and I can help this year with
administrative issues.

Cheers,
Xavier.

On Jan 14, 2018 6:04 AM, "Sharan Foga" <sha...@apache.org> wrote:

That's great and thanks Uli!

And it's a good idea to get more people involved with helping out with any
admin as it shares the knowledge and workload :-)

Thanks
Sharan


On 2018-01-13 21:18, Ulrich Stärk <u...@apache.org> wrote:
> I happily do it again this year but as always would be happy for any help
I can get especially with chasing mentors ;)
>
> Cheers,
>
> Uli
>
> > On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com>
wrote:
> >
> > Usually Uli was the main org admin.
> > I can register ASF application 
> >
> > @Uli can you please confirm it is OK?
> >
> > On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> > <piergior...@apache.org> wrote:
> >> Hi,
> >>
> >> I received this invitation as a mentor for renewing our participation
in
> >> the Google Summer of Code program.
> >>
> >> I think that we are interested as usual, is it right?
> >> Who is in charge for giving the official confirmation by our side?
> >>
> >> Please let me know.
> >> Thank you.
> >>
> >> Cheers,
> >> PJ
> >>
> >> ------ Forwarded message --
> >> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce
List <
> >> gsoc-mentors-annou...@googlegroups.com>
> >> Date: 2018-01-13 0:01 GMT+01:00
> >> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications
due by
> >> Jan 23rd!
> >> To: Google Summer of Code Mentors Announce List <
> >> gsoc-mentors-annou...@googlegroups.com>
> >>
> >>
> >> Hi all,
> >>
> >> If your open source organization is interested in being a mentoring
> >> organization for Google Summer of Code 2018 please be sure to submit
your
> >> organization's application via g.co/gsoc before January 23rd at 16:00
UTC.
> >>
> >> Organizations chosen for GSoC 2018 will be announced on February 12th.
> >>
> >> Best,
> >> Google Open Source Programs Office
> >>
> >> --
> >> You received this message because you are subscribed to the Google
Groups
> >> "Google Summer of Code Mentors Announce List" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
an
> >> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
> >> Visit this group at https://groups.google.com/
group/gsoc-mentors-announce.
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >>
> >>
> >> --
> >> Piergiorgio Lucidi
> >> Open Source Evangelist and Enterprise Information Management Specialist
> >> Mentor / PMC Member / Committer @ Apache Software Foundation
> >> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> >> Author and Technical Reviewer @ Packt Publishing
> >> Technical Advisory Group Member @ Microsoft
> >> Top Community Contributor @ Crafter
> >> Project Leader / Committer @ JBoss
> >> https://www.open4dev.com
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
> > -
> > 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: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Sharan Foga]

That's great and thanks Uli!

And it's a good idea to get more people involved with helping out with any 
admin as it shares the knowledge and workload :-)

Thanks
Sharan


On 2018-01-13 21:18, Ulrich Stärk <u...@apache.org> wrote: 
> I happily do it again this year but as always would be happy for any help I 
> can get especially with chasing mentors ;)
> 
> Cheers,
> 
> Uli
> 
> > On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com> wrote:
> > 
> > Usually Uli was the main org admin.
> > I can register ASF application 
> > 
> > @Uli can you please confirm it is OK?
> > 
> > On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> > <piergior...@apache.org> wrote:
> >> Hi,
> >> 
> >> I received this invitation as a mentor for renewing our participation in
> >> the Google Summer of Code program.
> >> 
> >> I think that we are interested as usual, is it right?
> >> Who is in charge for giving the official confirmation by our side?
> >> 
> >> Please let me know.
> >> Thank you.
> >> 
> >> Cheers,
> >> PJ
> >> 
> >> -- Forwarded message --
> >> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce List <
> >> gsoc-mentors-annou...@googlegroups.com>
> >> Date: 2018-01-13 0:01 GMT+01:00
> >> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by
> >> Jan 23rd!
> >> To: Google Summer of Code Mentors Announce List <
> >> gsoc-mentors-annou...@googlegroups.com>
> >> 
> >> 
> >> Hi all,
> >> 
> >> If your open source organization is interested in being a mentoring
> >> organization for Google Summer of Code 2018 please be sure to submit your
> >> organization's application via g.co/gsoc before January 23rd at 16:00 UTC.
> >> 
> >> Organizations chosen for GSoC 2018 will be announced on February 12th.
> >> 
> >> Best,
> >> Google Open Source Programs Office
> >> 
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Google Summer of Code Mentors Announce List" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/gsoc-mentors-announce.
> >> For more options, visit https://groups.google.com/d/optout.
> >> 
> >> 
> >> 
> >> --
> >> Piergiorgio Lucidi
> >> Open Source Evangelist and Enterprise Information Management Specialist
> >> Mentor / PMC Member / Committer @ Apache Software Foundation
> >> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> >> Author and Technical Reviewer @ Packt Publishing
> >> Technical Advisory Group Member @ Microsoft
> >> Top Community Contributor @ Crafter
> >> Project Leader / Committer @ JBoss
> >> https://www.open4dev.com
> > 
> > 
> > 
> > -- 
> > WBR
> > Maxim aka solomax
> > 
> > -
> > 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: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Maxim Solodovnik]

Count on me, I'll help :)

On Sun, Jan 14, 2018 at 3:18 AM, Ulrich Stärk <u...@apache.org> wrote:
> I happily do it again this year but as always would be happy for any help I 
> can get especially with chasing mentors ;)
>
> Cheers,
>
> Uli
>
>> On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com> wrote:
>>
>> Usually Uli was the main org admin.
>> I can register ASF application 
>>
>> @Uli can you please confirm it is OK?
>>
>> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
>> <piergior...@apache.org> wrote:
>>> Hi,
>>>
>>> I received this invitation as a mentor for renewing our participation in
>>> the Google Summer of Code program.
>>>
>>> I think that we are interested as usual, is it right?
>>> Who is in charge for giving the official confirmation by our side?
>>>
>>> Please let me know.
>>> Thank you.
>>>
>>> Cheers,
>>> PJ
>>>
>>> -- Forwarded message --
>>> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce List <
>>> gsoc-mentors-annou...@googlegroups.com>
>>> Date: 2018-01-13 0:01 GMT+01:00
>>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by
>>> Jan 23rd!
>>> To: Google Summer of Code Mentors Announce List <
>>> gsoc-mentors-annou...@googlegroups.com>
>>>
>>>
>>> Hi all,
>>>
>>> If your open source organization is interested in being a mentoring
>>> organization for Google Summer of Code 2018 please be sure to submit your
>>> organization's application via g.co/gsoc before January 23rd at 16:00 UTC.
>>>
>>> Organizations chosen for GSoC 2018 will be announced on February 12th.
>>>
>>> Best,
>>> Google Open Source Programs Office
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Google Summer of Code Mentors Announce List" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/gsoc-mentors-announce.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> Piergiorgio Lucidi
>>> Open Source Evangelist and Enterprise Information Management Specialist
>>> Mentor / PMC Member / Committer @ Apache Software Foundation
>>> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
>>> Author and Technical Reviewer @ Packt Publishing
>>> Technical Advisory Group Member @ Microsoft
>>> Top Community Contributor @ Crafter
>>> Project Leader / Committer @ JBoss
>>> https://www.open4dev.com
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>> -
>> 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
>



-- 
WBR
Maxim aka solomax

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

Re: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Ulrich Stärk]

I happily do it again this year but as always would be happy for any help I can 
get especially with chasing mentors ;)

Cheers,

Uli

> On 13. Jan 2018, at 18:17, Maxim Solodovnik <solomax...@gmail.com> wrote:
> 
> Usually Uli was the main org admin.
> I can register ASF application 
> 
> @Uli can you please confirm it is OK?
> 
> On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
> <piergior...@apache.org> wrote:
>> Hi,
>> 
>> I received this invitation as a mentor for renewing our participation in
>> the Google Summer of Code program.
>> 
>> I think that we are interested as usual, is it right?
>> Who is in charge for giving the official confirmation by our side?
>> 
>> Please let me know.
>> Thank you.
>> 
>> Cheers,
>> PJ
>> 
>> -- Forwarded message --
>> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce List <
>> gsoc-mentors-annou...@googlegroups.com>
>> Date: 2018-01-13 0:01 GMT+01:00
>> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by
>> Jan 23rd!
>> To: Google Summer of Code Mentors Announce List <
>> gsoc-mentors-annou...@googlegroups.com>
>> 
>> 
>> Hi all,
>> 
>> If your open source organization is interested in being a mentoring
>> organization for Google Summer of Code 2018 please be sure to submit your
>> organization's application via g.co/gsoc before January 23rd at 16:00 UTC.
>> 
>> Organizations chosen for GSoC 2018 will be announced on February 12th.
>> 
>> Best,
>> Google Open Source Programs Office
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google Summer of Code Mentors Announce List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/gsoc-mentors-announce.
>> For more options, visit https://groups.google.com/d/optout.
>> 
>> 
>> 
>> --
>> Piergiorgio Lucidi
>> Open Source Evangelist and Enterprise Information Management Specialist
>> Mentor / PMC Member / Committer @ Apache Software Foundation
>> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
>> Author and Technical Reviewer @ Packt Publishing
>> Technical Advisory Group Member @ Microsoft
>> Top Community Contributor @ Crafter
>> Project Leader / Committer @ JBoss
>> https://www.open4dev.com
> 
> 
> 
> -- 
> WBR
> Maxim aka solomax
> 
> -
> 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: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Maxim Solodovnik]

Usually Uli was the main org admin.
I can register ASF application 

@Uli can you please confirm it is OK?

On Sun, Jan 14, 2018 at 12:09 AM, Piergiorgio Lucidi
<piergior...@apache.org> wrote:
> Hi,
>
> I received this invitation as a mentor for renewing our participation in
> the Google Summer of Code program.
>
> I think that we are interested as usual, is it right?
> Who is in charge for giving the official confirmation by our side?
>
> Please let me know.
> Thank you.
>
> Cheers,
> PJ
>
> -- Forwarded message --
> From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce List <
> gsoc-mentors-annou...@googlegroups.com>
> Date: 2018-01-13 0:01 GMT+01:00
> Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by
> Jan 23rd!
> To: Google Summer of Code Mentors Announce List <
> gsoc-mentors-annou...@googlegroups.com>
>
>
> Hi all,
>
> If your open source organization is interested in being a mentoring
> organization for Google Summer of Code 2018 please be sure to submit your
> organization's application via g.co/gsoc before January 23rd at 16:00 UTC.
>
> Organizations chosen for GSoC 2018 will be announced on February 12th.
>
> Best,
> Google Open Source Programs Office
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Summer of Code Mentors Announce List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/gsoc-mentors-announce.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Piergiorgio Lucidi
> Open Source Evangelist and Enterprise Information Management Specialist
> Mentor / PMC Member / Committer @ Apache Software Foundation
> Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
> Author and Technical Reviewer @ Packt Publishing
> Technical Advisory Group Member @ Microsoft
> Top Community Contributor @ Crafter
> Project Leader / Committer @ JBoss
> https://www.open4dev.com



-- 
WBR
Maxim aka solomax

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

Fwd: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by Jan 23rd!

[Piergiorgio Lucidi]

Hi,

I received this invitation as a mentor for renewing our participation in
the Google Summer of Code program.

I think that we are interested as usual, is it right?
Who is in charge for giving the official confirmation by our side?

Please let me know.
Thank you.

Cheers,
PJ

-- Forwarded message --
From: 'Stephanie Taylor' via Google Summer of Code Mentors Announce List <
gsoc-mentors-annou...@googlegroups.com>
Date: 2018-01-13 0:01 GMT+01:00
Subject: [GSoC Mentors Announce] GSoC 2018 Organization Applications due by
Jan 23rd!
To: Google Summer of Code Mentors Announce List <
gsoc-mentors-annou...@googlegroups.com>


Hi all,

If your open source organization is interested in being a mentoring
organization for Google Summer of Code 2018 please be sure to submit your
organization's application via g.co/gsoc before January 23rd at 16:00 UTC.

Organizations chosen for GSoC 2018 will be announced on February 12th.

Best,
Google Open Source Programs Office

-- 
You received this message because you are subscribed to the Google Groups
"Google Summer of Code Mentors Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to gsoc-mentors-announce+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/d/optout.



-- 
Piergiorgio Lucidi
Open Source Evangelist and Enterprise Information Management Specialist
Mentor / PMC Member / Committer @ Apache Software Foundation
Community Star / Wiki Gardener / Global Forum Moderator @ Alfresco
Author and Technical Reviewer @ Packt Publishing
Technical Advisory Group Member @ Microsoft
Top Community Contributor @ Crafter
Project Leader / Committer @ JBoss
https://www.open4dev.com

gsoc 2018

[clash of clans hack]

sir/mam
I am student presently studying in netaji shubhash institute of technology
and is interested in google summer of code program.
I wanted to work with you on your project mirage.
I have knowledge of c++ .
please notify me if their is any vacancy and how can I participate

waiting for your reply
jatin garg
1 year
netaji subhash institute of technology