Your Gump Build(s)

[Stefan Bodewig]

Dear Community

Apache Gump builds some of your projects and it is quite possible you
don't know or have by now forgotten about it.

More than half a year ago a technical problem has forced us to turn off
emails on build failures as we would have been sending out lots of false
alarms.

Before we re-enable emails we'd like to know whether you are still
interested in the service Gump provides, so please tell us. :-)

Metadata for many projects have been neglected for a long time and it is
quite possible they'd need some love for results to be meaningful.  All
Apache committers have write access to Gump's metadata.

In case you don't know what this Gump stuff is about:

Apache Gump builds the full stack of the latest commits of software in
order to ensure integrity over releases.  Build failures surface API
discontinuities between projects before they impact releases, and Gump's
e-mail notifications hope to promote the conversations between teams to
resolve those discontinuities.

When responding to this mail please shorten the CC list as appropriate.

Cheers

Stefan

 on behalf of the Gump PMC

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

Re: including external code under apache 2.0

[Stefan Bodewig]

On 2012-04-28, Itamar Syn-Hershko wrote:

> That mail from  Stephan got lost in my inbox, so I never followed up on
> that. I guess now would be a good chance to tie up all loose ends.

> How do I "do the ICLA"?

In addition to what Troy said, you can also fill in the text form and
PGP-sign it when you send it by email.

See 

Stefan

Re: [Lucene.Net] Merging 3.0.3 into Trunk

[Stefan Bodewig]

On 2012-02-29, Stefan Bodewig wrote:

> On 2012-02-28, Christopher Currens wrote:

>> Alright, it's done!  3.0.3 is now merged in with Trunk!

> I'll see to running RAT and looking at the line-ends over the next few
> days so we can get them fixed once and not run into it with the release.

I went for EOLs first and there are 621 files outside of lib and doc
that need to be fixed.  What I have now is not just a patch (of more
than 200k lines), but also a list of 621 files that need their
svn:eol-style property to be set.

I can create a JIRA ticket for that attaching my patch and the list of
files to fix or - since I technically am a committer - could just commit
my cleaned up workspace as is (plus JIRA ticket that I'd open and close
myself).

What would you prefer?

RAT doesn't really make sense before the line feeds are correct (I've
seen quite a few files without license headers by manual inspection).

Stefan

Re: [Lucene.Net] Site / docs

[Stefan Bodewig]

On 2012-02-14, Prescott Nasser wrote:

> I've been trying to use the upload a tar.gz file to add docs to the
> site to solve the publish takes forever problem. This actually doesn't
> solve the problem at all - when uploading the tar file, it just untars
> it and commits all the files for you (saving no time whatsoever).

8-(

At least is saves some network bandwidth for you.

Given that all projects will have to move website content into svn
sooner or later (the maven generated sites are currently cursing this as
well) I expect a solution will be found cases where a single release
changes thousands of files.  But it isn't there, yet.

The only alternative would be to not create thousands of pages.  CHMs, I
guess, or running a dynamic server on a dedicated VM.  The later would
be easier to negotiate for a top level project.

> At the moment I'm trying to solve another issue - it seems that the
> Index.html page doesn't load:
> http://lucene.net.staging.apache.org/lucene.net/docs/2.9.4/Index.html
> -> loads nothing for me, view source and it's some corrupted
> text.

wget obtains a four byte binary (the byte 3 and three zeros).

> However, viewing this through the svn links showing source, the source
> seems fine:
> https://svn.apache.org/repos/asf/incubator/lucene.net/site/trunk/content/lucene.net/docs/2.9.4/Index.html.
>  Does
> anyone have any idea why this is?

The file itself has the svn:executable property set, but I don't expect
that to cause any issues.

The only other thing I notice with a quick scan is the BOM.  Does the
CMS try to process static files in any way?  Maybe it chokes on the BOM
(RAT did before I fixed it)?

Can you try to remove the BOM and see whether the problem goes away?
This won't be a permanent solution as I expect all the generated files
to contain BOMs and so we'd need to investigate with infra help what is
causing problems.

Stefan

[Lucene.Net] Blog Setup

[Stefan Bodewig]

Hi all,

If we want a blog for Lucene.Net on blogs.apache.org, the instructions
to request one are at

Mainly we should have a list of ASF ids of the initial set of admins and
authors.

I had a look at how the RSS snippets are added to www.apache.org's index
page and it doesn't look to difficult to adapt.

In

there is

{% for e in blog.list %}
{{ e.title }}
{{ e.content|safe|truncatewords_html:50 }}

{% endfor %}

which iterates over a blogs collection created in path.pm via

[qr!^/index\.html$!, news_page =>
  {
blog => ASF::Value::Blogs->new(blog => "foundation", limit=> 3),
  },
],

and uses the ASF::Value::Blog package that is part of the CMS.


So getting content from the blog to the main page is pretty easy.  I
think the main site is re-created every fifteen minutes to ensure things
are fresh, not sure how one would go about this for a page that doesn't
change that often (manually triggering buildbot might be an option).
We'd need to ask this on the site-dev mailing list which is dedicated to
the CMS.

Stefan

[Lucene.Net] Infrastructure Choices/Issues (was Re: [Lucene.Net] Graduation)

[Stefan Bodewig]

On 2012-02-02, Simone Chiaretta wrote:

> I've seen that moving to a more "social" source control helps, like moving
> to git or mercurial. Lucene.net is still on Subversion, and that makes
> difficult for people to contribute sporadically.

There already is a git-mirror (of trunk) on github at
<https://github.com/apache/lucene.net> and I think it is possible to
arrange for github pull requests to go to the project's mailing list.
If there is any interest I can try to dig out the details.

But as with all contributions there is the bar of licensing the code to
the ASF, so for anything that is more than a few lines JIRA with the
simple checkbox is more effective.

Furthermore if the team wanted to go with git as primary SCM then
Lucene.Net could join the club of testers (if anybody volunteers to help
out infra).

> Actually hosting the source on something like github would definitely
> help: but I think both solutions are against the rules of the ASF: no
> external tools allowed.

Not quite "no external tools" but certainly no external SCM.  As for
other tools, the ASF prefers people to use what is here and help out if
this is not adequate.

> But what about a CI environment? with a public output?

<http://ci.apache.org/> with options of buildbot, Continuum and Jenkins.

There even are some builds for Lucene.Net, see
e.g. <https://builds.apache.org/job/Lucene.Net-Trunk-All-Nightly/> but
my understanding is the team isn't happy with the setup, yet.

Likely this is a case of missing communication.

> Also the CMS, from my understanding, is kind of difficult to work with.

Not the CMS per se, but the restriction to "CMS or static files", I
think.  We'll need to find a better solution for the generated
documentation, that's true.

[OT: just stumbled upon
http://www.apache.org/dev/cmsref.html#generated-docs which may provide a
solution (the "upload a tarball rather than use svn" approach).]

> On Thu, Feb 2, 2012 at 1:30 PM, Stefan Bodewig  wrote:

>> What would you suggest?

> Having a blog on the site, and have posts on what's going on, plans for the
> future, to start discussions: I agree, probably the same thing already
> happen on this or the user ML, but they definitely have much bigger
> visibility than just something came straight from the '90s (the ML).

OK.  Technically this could be done immediately.  There is a Roller
instance set up for ASF projects and it should be possible to embed blog
content into the sity dynamically.

Many thanks

 Stefan

Re: [Lucene.Net] Graduation

[Stefan Bodewig]

[I started to write a really long response and then figured I should
split it to keep this thread focussed.]

On 2012-02-02, Simone Chiaretta wrote:

> On Thu, Feb 2, 2012 at 1:30 PM, Stefan Bodewig  wrote:

>> On 2012-02-01, Simone Chiaretta wrote:

>>> As other said, while the user base is pretty big, the dev community is
>>> relatively small and still relying on just a few people.

>> Can you recommend an approach that would draw in more developers?  Is
>> there anything the current team should be doing or stop doing?

> It think there is little that can be done here:
> finding committees dedicated to help open source project is difficult,
> especially if it is not something "cool" but just a server side library
> nobody see.

Yes, true.

> Also, but that's again something we cannot change, working on a line by
> line port of a java library, with no space to creativity is not super
> exciting :)

This I fully agree with.

> I'm not a committer, just someone that cares about Lucene.net but with not
> much time.

And both your time and thoughts are very much appreciated.

>>> Also, there must be an official way of communicating to the user base,
>>> which is not the ML or some sporadic news on the site or on other
>>> blogs.

>> What would you suggest?

> I know probably all this sounds silly from a hard-core developer/OSS
> fanatic/linux hacker point of view, but nowadays marketing and
> documenting an OSS project is as important (if not more) as developing it.

It doesn't sound silly at all, I agree with you.  Writing good
"marketing" material requires a certain skill, though, a skill quite
different from writing decent C# code.

>>> But the main point is a lack of long term strategy that is shared by
>>> everyone: most OSS can go along without such things, but Lucene.net is
>>> in a position where such strategy is needed.

>> I agree the strategy must get decided on and be documented at one point,
>> but does this need to get solved before graduation?

> For this I think yes: otherwise we risk that Lucene.net "graduates",
> whatever that means, and than committers are split by the decision to
> take, and the project dies again, for the same reasons it was dying
> last year.

Understood.  I tend to agree with that.  This also resonates with what
Prescott says.

> But the final word is to people that really spend their time on code and
> administrative stuff.

Whether it feels ready to leave the Incubator is on the Lucene.Net
community with those who actually do the work having to take the final
decision.

Many thanks

 Stefan

Re: [Lucene.Net] [VOTE] Apache-Lucene-2.9.4g-incubating-RC1 Release (take 2)

[Stefan Bodewig]

On 2012-01-23, Prescott Nasser wrote:

> I've created a wiki page with the checklist:
> https://cwiki.apache.org/confluence/display/LUCENENET/Release+Checklist+and+steps+once+a+release+is+approved.

Thanks, I've added the points from my list.

> I've also called a vote in general for 2.9.4g.

Personally I would have preferred it if you had waited until you got
three +1s from this list.  So far I've only seen Christopher's (and
imply yours even though you didn't vote explicitly ;-).

Once/if Michael gets around voting I'll throw in my +1 as well (on
general and here).

Stefan

[Lucene.Net] [jira] [Commented] (LUCENENET-451) Missing License Headers in trunk

[Stefan Bodewig (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/LUCENENET-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140066#comment-13140066
 ] 

Stefan Bodewig commented on LUCENENET-451:
--

I will re-create the patch on a Windows machine so there is less noise in it.

> Missing License Headers in trunk
> 
>
> Key: LUCENENET-451
> URL: https://issues.apache.org/jira/browse/LUCENENET-451
> Project: Lucene.Net
>  Issue Type: Bug
>    Reporter: Stefan Bodewig
> Attachments: LUCENENET-451.trunk.patch
>
>
> Many files lack the ASF license headers, I'll attach a patch against trunk 
> shortly.
> I can provide patches against branches as well if this seems easier than 
> merging from trunk.
> So far I have deliberately skipped the docs and lib directories as docs seems 
> to contain generated files only and the lib folder is something that needs to 
> be talked about separately anyway.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Lucene.Net] Comparing APIs of two DLLs (something like Clirr for .NET)?

[Stefan Bodewig]

On 2011-09-07, Prescott Nasser wrote:

> I have heard people use http://www.bitwidgets.com/ to success. I have
> not used it myself though.

This looks useful at first glance.  Unless anything else is mentioned
I'm going to apply for a free license for Open Source projects and share
my experience here.

Stefan

Re: [Lucene.Net] Board Report Nudge

[Stefan Bodewig]

On 2011-08-10, Michael Herndon wrote:

> On Wed, Aug 10, 2011 at 11:20 AM, Stefan Bodewig  wrote:

>> On 2011-08-10, Michael Herndon wrote:

>>> Updated: http://wiki.apache.org/incubator/August2011: anyone looking
>> into
>>> this thread feel free to tweak.

>> Thanks a lot, looks good to me but I have a few questions to ask - which
>> may or may not get answered inside the report.

>>> * Lucene.Net 2.9.4 & 2.9.4g are being worked on and tested

>> 2.9.4g is a variant of 2.9.4 using generics, correct?  I don't think
>> anybody outside of this list would know.

>> The logo itself and how it came to be the new logo may be newsworthy.


> I've now expounded on both of those.

Thanks a lot.


>>> Goals for graduation:

>>> * Have a nearly fully automated process to convert Java Lucene to C#.
>>> * Release Lucene.Net 3.0.3 (port of Java Lucene 3.0.3)
>>> * Have a new .NET version of Lucene utilizing .NET constructs and idioms

>> Why do you feel this needs to happen before you can graduate out of the
>> Incubator?  I know this are short/mid-term goals for Lucene.NET but
>> neither of them must happen while you are incubating IMHO.

> - copied & pasted from may's report for consistency. open to changing.

OK, I guess we should discuss this outside of the context of reports
after vacation season is over.

Cheers

Stefan

Re: [Lucene.Net] Board Report Nudge

[Stefan Bodewig]

On 2011-08-10, Michael Herndon wrote:

> Updated: http://wiki.apache.org/incubator/August2011: anyone looking into
> this thread feel free to tweak.

Thanks a lot, looks good to me but I have a few questions to ask - which
may or may not get answered inside the report.

> * Lucene.Net 2.9.4 & 2.9.4g are being worked on and tested

2.9.4g is a variant of 2.9.4 using generics, correct?  I don't think
anybody outside of this list would know.

> * New site design per new Lucene.Net logo.

The logo itself and how it came to be the new logo may be newsworthy.

> Goals for graduation:

> * Have a nearly fully automated process to convert Java Lucene to C#.
> * Release Lucene.Net 3.0.3 (port of Java Lucene 3.0.3)
> * Have a new .NET version of Lucene utilizing .NET constructs and idioms

Why do you feel this needs to happen before you can graduate out of the
Incubator?  I know this are short/mid-term goals for Lucene.NET but
neither of them must happen while you are incubating IMHO.

Stefan

Re: [Lucene.Net] Procedure for Commiting

[Stefan Bodewig]

On 2011-03-14, Scott Lombard wrote:

> I wanted to get a final agreement on how we want to handle commits to the
> repository.  There have been discussions in a couple of different threads
> about this topic.  I know patches, branches and just go for it has been
> discussed and different people have different ideas.  I just wanted to know
> what the group thinks is the way to handle commits in our project.

Inside the ASF we have varying ideas about how to handle it.

Many if not most projects use commit-then-review (CTR[1]) as their main
model where you just commit and your peers review it later (that's why
the commits mailing list exists).  This is probably the quickest way to
move forward but may lead to slipped-through problems.

At the other extreme there are projects that require JIRA items for each
and every commit with automated pre-build CI checks that reject patches
attached to JIRA tickets if they break the
build/tests/coding-standards/whatever[2].  This is probably the "safe"
way but may keep people from contributing because the effort to get a
patch in seems to big.

Other projects live in some sort of middle ground where some branch is
open for CTR and other branches (the "stable" branch) requires
review-then-commit (RTC[3]).  Many projects have written down policies
like Hadoop which I've already cited or Solr[4].

I guess what I'm trying to say is there is no policy that would force
you to do it one way or the other, it is your decision.

Stefan

[1] http://www.apache.org/foundation/glossary.html#CommitThenReview

[2] http://wiki.apache.org/hadoop/HowToContribute

[3] http://www.apache.org/foundation/glossary.html#ReviewThenCommit

[4] http://wiki.apache.org/solr/CommitPolicy

Re: [Lucene.Net] ndepend license requirements - apache rules

[Stefan Bodewig]

On 2011-03-07, Michael Herndon wrote:

> Does the following violate any of the rules put forth by apache or
> give anyone pause?

>> If you could put our Powered by NDepend logo on your OSS project
>> website we'd be happy to sponsor Apache Lucene.Net.

Yes it does.

You can't sponsor individual projects at the ASF, only the ASF as a
whole.

Other people and companies have donated licenses - committer only link
 -
and not received this sort of backlink.

Any sort of "thank you" link had to be cleared with fundraising@apache,
see http://www.apache.org/foundation/sponsorship.html and
http://www.apache.org/foundation/thanks.html

Stefan

[Lucene.Net] Nudge: Your Board Report Needs Content (was Re: Incubator PMC/Board report for March 2011)

[Stefan Bodewig]

On 2011-03-01, Stefan Bodewig wrote:

> this is one of the pain^H^H^H^Hjoys you've taken on yourself by entering
> the incubator 8-)

> Lucene.NET will be on a monthly schedule the first three month and then
> change to a quarterly schedule for as long as you need to graduate.

> On 2011-03-01,  wrote:

>> The board meeting is scheduled for Wed, 16 March 2011, 10 am
>> Pacific. The report for your podling will form a part of the Incubator
>> PMC report. The Incubator PMC requires your report to be submitted one
>> week before the board meeting, to allow sufficient time for review.

> This means the report has to be ready in
> <http://wiki.apache.org/incubator/March2011> by the 9th.  Please let us
> mentors know when you deem it ready so we can review it.

Still looks empty.

Stefan

Re: [Lucene.Net] irc chanel

[Stefan Bodewig]

On 2011-03-04, Michael Herndon wrote:

> Anything that should be on the mailing list, in the cms, on a wiki
> page, on twitter, or in a jira should be persuaded to find the right
> medium to do so.

That's fine, but as Digy already said IRC (or any synchronous medium
like a phone call, face to face meeting or IM) discriminates people
based on timezone, network connectivity or ability to travel.

There may be good uses for IRC like a quick question - I must admit I'm
no big fan of IRC myself - but in the end all discussions and in
particular all decisions have to be made on this mailing list.

Use what you feel is most appropriate for a given conversation but
please always report back here - and never make decisions anywhere else.

Stefan

Re: [Lucene.Net] Incubator PMC/Board report for March 2011 (lucene-net-...@lucene.apache.org)

[Stefan Bodewig]

Hi all,

this is one of the pain^H^H^H^Hjoys you've taken on yourself by entering
the incubator 8-)

Lucene.NET will be on a monthly schedule the first three month and then
change to a quarterly schedule for as long as you need to graduate.

On 2011-03-01,  wrote:

> The board meeting is scheduled for Wed, 16 March 2011, 10 am
> Pacific. The report for your podling will form a part of the Incubator
> PMC report. The Incubator PMC requires your report to be submitted one
> week before the board meeting, to allow sufficient time for review.

This means the report has to be ready in
 by the 9th.  Please let us
mentors know when you deem it ready so we can review it.

While you are at it it would be great if you could also update the
status page at  -
I have made some initial edits early on, but it is fra from complete.

Thanks

Stefan

Re: [Lucene.Net] Lucene.Net Tasks due by 2/28

[Stefan Bodewig]

On 2011-02-23, Michael Herndon wrote:

> Also, I'm already leaning towards hudson since we're limited to CI choices
> supported by apache.

This is likely to become Jenkins rather than Hudson soon.

Stefan

Re: [Lucene.Net] [VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC1

[Stefan Bodewig]

On 2011-02-23, Troy Howard wrote:

> I'm happy to announce that Lucene.Net 2.9.2-incubating-RC1 is
> available and ready for your testing and voting.

Great.

I could successfully verify your PGP signature.

> Release candidate artifacts:

> http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC1/dist/

I found some issues, some really only cosmetic and maybe even a matter
of taste, and some that may lead Incubator PMC members to vote -1.  It
may be better to fix those even if it means you'd lose against your
schedule and have the release slip a day.

Not only cosmetic:

* The NOTICE file contains a bad copyright year and doesn't talk about
  Lucene.NET at all.  Make that Lucene.NET rather than Lucene and
  2006-2011.

* LICENSE talks about src/java/org/apache/lucene/util/UnicodeUtil.java
  and src/java/org/apache/lucene/util/ArrayUtil.java that certainly
  don't exist while there are files with different names that the
  corresponding license entry applies to.

* Quite a few files that could contain the ASF license don't.
  I've run RAT[1] over the distribution archives and the results are
  here 

  I dont think the .txt files need a license, but the .html, .cs, .xml
  (at least the ones that are not generated), .config, .nunit and
  .resources files can and should.  One could even argue the .sln and
  .c[ds]proj files should (the build.xml or pom.xml files of Java
  projects also do).

* some snowball files need to get relicensed under Apache Software
  License 2.0 (the are still at 1.1).

Cosmetic of low importance, feel free to ignore some:

* The top level directories of the bin and src archives are different,
  which is confusing (Apache-Lucene.Net-2.9.2-incubating-RC1.bin vs
  2.9.2).

* The layout of the bin archive is, uhm, surprising.  You wouldn't
  expect to find a top level src directory when you look for DLLs only.

* I wouldn't include the .user files in the src ZIP.

* The file names inside the .md5 and .sha1 files are all lowercase while
  the real filenames ar not.  This may lead automated integrity checks
  to flag them as not matching.

Stefan

[1] http://incubator.apache.org/rat/

Re: [Lucene.Net] Re: Signing Binary Releases

[Stefan Bodewig]

On 2011-02-21, Ayende Rahien wrote:

> There are many situations where you _have_ to have a strong key, or
> example, gac deployments.  In those cases, anything in the chain also
> have to have strong key.

Yes, I knew that.  Sorry if I sounded stupid.  In most cases I try to
avoid the GAC and my personal use-case (XMLUnit) is quite different from
Lucene (i.e. it is less likely to end up as a dependency of something
that gets deployed to the GAC).

Fortunately my opinion is pretty unimportant here anyway 8-)

> Most OSS in .NET have signed binary releases, and the snk is usually
> in the source code.

Do you educate your users that there is no security promise attached to
the strong name in this case?  I've always shied away from using strong
names in OSS because of the illusion of verified-publisher they provide
in such a setup.

Thanks

Stefan

Can I remove access of Lucene.NET committers to Lucene infrastructure now?

[Stefan Bodewig]

Hi,

as far as I can tell Digy has moved over everything that was in svn or
on the site.  Is there still anything left that you need access to or
can I modify permission so that the Lucene.NET committers no longer have
write access to it?

Stefan

Confluence Wiki is there

[Stefan Bodewig]

Hi,

the Wiki instance can be reached at
.  Michael,
Benson and myself are admins and can grant people access to the pages as
needed.

AFAIU there will be a static export of the pages to
 once there is actual content (I may
be wrong and we need to tweak some settings to make it happen).

Anyway, the two pages of the old wiki could now be moved over.

Stefan

Re: Old website redirects?

[Stefan Bodewig]

On 2011-02-12, Prescott Nasser wrote:

> The file is here :
> https://svn.apache.org/repos/asf/lucene/site/publish/.htaccess

> I don't have the ability to update it. Once I get commit status would
> that allow me to update it?

Likely not since I'll remove access for Lucene.NET committers to the
Lucene site once all is there.

> # Lucene.Net has moved to the incubator,
> # site strcuture has changed, do don't use $1 in redirect...
> RedirectMatch Permanent ^/lucene.net/(.*)$ 
> http://incubator.apache.org/lucene.net

Yes, that would have worked.  Of course Digy's solution does so as well
(or my redirect line which does the same as the above just without
regulare expressions).

Stefan

Re: Confluence Wiki Volunteer(s) needed

[Stefan Bodewig]

On 2011-02-10, Michael Herndon wrote:

> Morning Stefan (or afternoon),

Late afternoon, yes 8-)

> I can help with this.

Great, thanks.  With Benson and you that should be enough to get the
instance created.  We can supply more people with admin rights later.

> Would we need to create an account name or any of the instances, like
> maven per say?

Yes, the account is for the whole wiki farm.

Stefan

Confluence Wiki Volunteer(s) needed

[Stefan Bodewig]

Hi all,

in order to set up the new wiki we need a few people who help out with
administrating the Lucene.NET instance (basically user and permission
management IIUC).

If anybody of the initial committers or mentors can help, please drop me
a note with your CWIKI account name[1].

Thanks

Stefan

[1] The only way I have found to create one was to go to one of the
existing instances, click edit page and then created an account.
There must be an easier way but I didn't find it.

.

Re: [jira] Commented: (LUCENENET-392) Arabic Analyzer

[Stefan Bodewig]

On 2011-02-10, Digy wrote:

> I don't see it as a "request for permission". It is rather to inform people
> about the change who may have different ideas and give a chance to comment
> on it if this change breaks something in their own local copy.

That's what I understood as well.

I realize that you currently are the only one who could revert any
change that could break anything but this will hopefully change soon.

In general if a change breaks anything, it can get reverted.  In my
experience if you ask for objections you won't hear any until after
you've committed the change anyway 8-)

In this particular case you are adding a piece of ported contrib code
that hasn't been there before at all so the danger shouldn't be too big
IIUC.

Anyway, what I was trying to say is that you should not fear breaking
each other local copies too much since it can get fixed after the fact.
Glitches happen, whether you asked for objections/permission or not.

Of course there are big changes that need to be discussed, but that's a
different story.

Stefan

Re: Umlauts as Char

[Stefan Bodewig]

On 2011-02-08, Prescott Nasser wrote:

> So I can take the source codes word that 'ü' is the u with dots over
> it (becuase it says replace umlauts in the source notes). But, I
> guess, is that really true? Is that perhaps u with a carrot over it
> instead?

I think the case has been settled by now, but I forgot to add that I am
German so if in doubt, feel free to ask.  We don't have any "funny"
characters except for äöüÄÖÜß in German.

Stefan

Re: Incubator Infrastructure: Wiki

[Stefan Bodewig]

On 2011-02-01, Michael Herndon wrote:

> either wiki
> * set up to support code syntax highlighting/coloring ?

Not sure for Confluence; I don't think Moin has it.

> * attachments ?

Both support attachments.  I know attachments have become a spam target
at least on the Moin installation (the projects I'm involved in all use
Moin) and we've disabled attachments for some of the wikis.

Stefan

Re: Incubator Infra: JIRA

[Stefan Bodewig]

On 2011-02-01, digy digy wrote:

> Lucene.Net users sometimes discuss the same issue in both JIRA and dev
> mailing list. And people mostly don't subscribe to commit list

In this case it might be a good thing to send JIRA notifications to the
commits list.  People would be forced to use a single place for
discussion, the dev list 8-)

Your collective choice.  It can be changed at any later point in time
anyway.

Stefan

Re: Incubator Infra: mailing lists

[Stefan Bodewig]

On 2011-02-01, digy digy wrote:

> I am the current moderator of the mailing lists.

All three of them?

> It is not much work than "reply" or "delete"

I know.  The good thing is you don't need to do anything to keep out the
spam - other than ignoring it.

> but having more than one moderator would be good.

OK, I'll sign up as well.

Stefan

Re: Icubator Infra: svn and Committers

[Stefan Bodewig]

On 2011-02-01, digy digy wrote:

> I think I don't have write access to "../incubator/lucene.net".

Not yet.  I'll grant access to you as soon as the vote is closed (and I
am awake enough to see it).

Stefan

Re: Proposal Status, Initial Committors List, Contributors List

[Stefan Bodewig]

On 2011-01-26, Michael Herndon wrote:

> Is there anything else that needs to be submitted or that we are waiting on
> to call for a vote?

Everything is in place, IMHO.  I've seen Grant thinks you need one more
mentor but other proposals have passed the vote with two mentors before
(like the currently voted on EasyAnt proposal).

If you really think you need a third mentor, ask again on the incubator
general mailing list but change the subject ;-) [otherwise people will
ignore it since it seems to be discussing details of the proposal].

> Anything we should be looking at doing in short term/mean time while that is
> taking place ?

Hopefully the restart will attract new people so prepare to answer a few
question that you think you have already discusses to death in the past.
People will not go and read the archives.  It might be best to put some
answers into a FAQ you can point people to.

Newbie questions I considered to ask but deferred until I find time to
search the archives (you are giving me a free ride right now, thanks):

  * have you considered IKVM rather than a line-by-line translation?

  * what is the target C#/.NET version?

  * is Mono support a goal?

and there'll be more common questions.

Stefan

Adding Myself as Mentor to the Incubator Proposal

[Stefan Bodewig]

Hi all,

I'm in the process of signing up as mentor on the Incubator wiki and
thought I'd better introduce myself since I don't expect anybody around
here to know me.

Like many people I came to the ASF to scratch a few itches I encountered
with an existing project I used at work.  In my case it was JServ in
around 1998 but I mainly remained a pure user with the occasional bug
report back then.  But I gradually became more involved over time.  In
2000 I was voted in as a committer to Ant and later the year as a member
of the ASF.

Today I still am an active committer to Ant, the PMC chairman of Gump
and involved in a few smaller parts of Commons and the remainings of
Jakarta.  A few years ago I mentored Apache Ivy through incubation so I
already wear my Incubator scars.

During work hours the .NET platform has become my main development
target since 2005.  Even though all the ASF projects I'm involved in are
Java projects I'm very familiar with C# and the platform in general.

Early last year I coded up a prototype for a customer project (that
never took off) using Lucene.NET and recall how "wrong" it felt so I
fully understand and appreciate the need for an idiomatic API.

It's my goal to keep out of any technical decisions, that's really up to
the committers to decide.  I may find time to participate in the
discussions and even provide a patch or two but won't promise anything.

I hope I can contribute a small part to a successful reboot of the
project.  Let's enjoy the ride.

Stefan

-- 
http://stefan.samaflost.de/