lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Vesse <>
Subject Re: updating content.
Date Thu, 10 Apr 2014 23:13:31 GMT
I would strongly recommend you guys update the website rather than the
wiki.  Remember that the website is your projects primary entry point and
presence at Apache.  It¹s the top search result for "Lucene .Net² in
Google whereas the wiki isn¹t even in the first 10 pages of results

The Apache CMS is actually very easy to use plus it has the advantage that
you can check out your sites content locally on your machine and edit in
your favourite editor.  Plus Markdown is much more developer friendly than
Confluence wiki syntax IMO


On 10/04/2014 16:38, "Itamar Syn-Hershko" <> wrote:

>Go ahead!
>I'm going to have a few more cycles before I'll write a Java to C# porting
>guide I can feel comfortable with, but I'm all in for showing some
>Itamar Syn-Hershko
> | @synhershko <>
>Freelance Developer & Consultant
>Author of RavenDB in Action <>
>On Thu, Apr 10, 2014 at 3:45 PM, michael herndon <
>> wrote:
>> Its getting near that time of year when there is more interest in
>> involved with code projects.
>> I suggest we update the main website, twitter feed, and wiki to reflect
>> that we are working on porting Lucene 4x in hopes to generate interest
>> contributions.
>> Then we should try to put together some materials on the wiki and point
>> there for:
>>  * navigating the source code
>>  * which branch to port from
>>  * porting Java to C# tips
>>  * working with git
>>  * working within Apache
>>  * roadmap for 4x.
>>  * decisions made. i.e. the outcome of CLS compliance.
>> The wiki is easier to manage than the public site.
>> -M

View raw message