committers call!

[James Stuart]

Topics:

1) internationalization

2) putting together a 3.4 release

3) bootstrap/ui talk

4) any other miscellaneous topics post LDCX drunken haze.

1pm EST/ 10am PST Monday!

plus many more, suggested by you.

Instructions for skype:

Add freeconferencecallhd.5308811400 as a contact in your skype account:

* copy and paste freeconferencecallhd.5308811400 (the entire name)

into your contact search area

* add as a contact

After freeconferencecallhd.5308811400 is listed in your contact list,

simply call that contact:

* Enter the following code through the Skype keypad (not by just

typing in the numbers on your keyboard): 651025 (you will prompted to

add the # sign). Note: you must enter the code in the Skype keypad,

not your keyboard number pad.

Instructions for Phone:

Dial:  +1 (530) 881-1400

Access Code: 651025

[Jonathan Rochkind]

I'd like to talk about the document fetch config Chris committed; I'd like to make sure we talk about before releasing a BL that includes it. I'll try to make a Github Issue before the meeting. I have some concerns.

--
You received this message because you are subscribed to the Google Groups "Blacklight Development" group.
To post to this group, send email to blacklight-...@googlegroups.com.
To unsubscribe from this group, send email to blacklight-develo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blacklight-development?hl=en.

[Chris Beer]

Can we hash out the commit in a Github issue? I'm probably not going
to make the call today.

Here is the commit at issue:
https://github.com/projectblacklight/blacklight/commit/018196f3e33028bc4e8a0ae78fe1488298bc8ef6

It was the least disruptive way I could think of to make it easier to
work with arbitrary solr indexes, though I'm certainly open to other
approaches (or, general rethinking of the
multiple-request-handler-by-default approach, although that's
definitely a more significant change) .

Thanks,
Chris

[Jonathan Rochkind]

Sure, I'll make a Github Issue.

Just want to make sure we don't do a release with this in it until
others have had some input at least.

Thanks for the commit hash so I don't need to find it.

[James Stuart]

Committers call! Next monday:

We really should resolve the outstanding solr request handler. (See Jonathan Rochkind's email)

Let me know if you've got any other topics of interest.

blacklight-development@googlegroups.com.

To unsubscribe from this group, send email to

blacklight-development+unsub...@googlegroups.com.

For more options, visit this group at
http://groups.google.com/group/blacklight-development?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Blacklight Development" group.
To post to this group, send email to

blacklight-development@googlegroups.com.

To unsubscribe from this group, send email to

blacklight-development+unsub...@googlegroups.com.

For more options, visit this group at
http://groups.google.com/group/blacklight-development?hl=en.

--
You received this message because you are subscribed to the Google Groups "Blacklight Development" group.

To post to this group, send email to blacklight-development@googlegroups.com.
To unsubscribe from this group, send email to blacklight-development+unsub...@googlegroups.com.

[Jonathan Rochkind]

* Current Hudson build failure.

* Latest version of Rails changes defaults for mass assignment. Release a patch version of BL with a fix for these defaults? I _think_ the fix is already committed to master.

On 4/13/2012 7:17 PM, James Stuart wrote:

Committers call! Next monday:

We really should resolve the outstanding solr request handler. (See Jonathan Rochkind's email)

Let me know if you've got any other topics of interest.

On Mon, Apr 2, 2012 at 10:59 AM, Jonathan Rochkind <roch...@jhu.edu> wrote:

Sure, I'll make a Github Issue.

Just want to make sure we don't do a release with this in it until others have had some input at least.

Thanks for the commit hash so I don't need to find it.

On 4/2/2012 10:55 AM, Chris Beer wrote:

Can we hash out the commit in a Github issue? I'm probably not going
to make the call today.

Here is the commit at issue:
https://github.com/ projectblacklight/blacklight/ commit/ 018196f3e33028bc4e8a0ae78fe148 8298bc8ef6

It was the least disruptive way I could think of to make it easier to
work with arbitrary solr indexes, though I'm certainly open to other
approaches (or, general rethinking of the

multiple-request-handler-by- default approach, although that's

To post to this group, send email to blacklight-...@googlegroups.com.
To unsubscribe from this group, send email to blacklight-develo...@googlegroups.com.