Project name clash (jSPF project already exists since 2006)

[GoogleCodeExporter]

I just want to point you to james.apache.org/jspf, a java implementation of the 
SPF protocol.

jSPF exists since 2006, and I am one of the authors.

As they are both java open source projects I don't think it is good to have 
this name clash for the community.

WDYT?

Original issue reported on code.google.com by stefano....@gmail.com on 28 Nov 2011 at 11:20

[GoogleCodeExporter]

Dear Stefano,

thank you for your report. When I started and named the plugin framework a few 
years ago I was not really aware of your sender policy framework (and, 
anecdotally, also not of the "Japan Society of Plasma Science and Nuclear 
Fusion Research", which is the third big hit for JSPF).

While I do agree that when searching with a single keyword the results are 
often arbitrary, I feel that adding a second keyword (like 'apache', 'plugin', 
or 'japan') usually solves this problem entirely.  

Since most of our users are probably quite used to this form of "overloading", 
and since our frameworks also target two entirely different Java domains, I do 
not really see a problem with the current situation, especially considering the 
'costs' associated with renaming any of them. 

Please let me know if you have a better solution to the problem.

Thanks,
Ralf

Original comment by r.biedert on 29 Nov 2011 at 5:53

• Changed state: Started
• Added labels: Priority-Low, Type-Other, Usability
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by r.biedert on 5 Dec 2011 at 9:41

• Changed state: WontFix