[Koha-devel] koha ldap for AD (ref)

[long_sam.tw]

Dear all, 
koha ldap for AD (config & test) ref https://koha.wikispaces.com/koha_ldap_en


___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Final stretch before the next release (3.24 | 16.05)

[Brendan Gallagher]

On Mon, Apr 11, 2016 at 3:50 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi devs,
>
> The next Koha release will arrive soon and the feature freeze is
> coming in 2 weeks!
> I'd like to mention some works we really should have in this release:
>
> 1/ Speed improvements
> * Koha::Cache
> Interesting ideas have been implemented recently, but only few have been
> pushed.
> We can expect a real gain of performances, our cache system
> (Koha::Cache) has been improved with bug 11998 and 16044 but is not
> perfect yet. To make it great, we absolutely need patches from 16221
> (Use Storable::dclone() instead of Clone::clone() for L1 cache
> deep-copying mode), and then 16140 (Only clear L1 cache when needed)
> and 16166 (Improve L1 cache performance).
> Bug 16105 (Cache::Memory is loaded even if memcache is used) is also
> cache-related.
>
> * Search
> There are 3 bug reports blocking bug 15262 (Run Koha Run. Koha search
> should be fast again) : bug 15263 (XSLT display fetches sysprefs for
> every result processed) is waiting for QA but 16041 is waiting for
> signoff. Note that I have opened 16167 to discuss about the possible
> removal of authorised value images. If you know someone using them,
> please add a comment on the bug report.
>
> To have an overview of what has been done around the performance
> optimisation during the last months or still need to be done, have a
> look at the bug 15342 (Performance 3.22 - Omnibus).
>

Very important stuff here.  This should be priority for everyone.


>
> 2/ Elastic Search
> A testing day is organised soon (today and tomorrow), stay tuned!
>
> 3/ Rewrite/refactoring
> I have worked a lot on refactoring some parts of Koha the last months.
> There are 5 left waiting for love:
> Bug 15801 - Move the framework related code to Koha::BiblioFramework[s] -
> part 2
> Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4
> Bug 15407 - Move the patron categories related code to
> Koha::Patron::Categories - part 2
> Bug 15498 - Replace ExportWithCsvProfile with ExportCircHistory
> Bug 15451 - Move the CSV related code to Koha::CsvProfile[s]
>
> I really would like to see them included into the next release.
> For the first 3, it's the continuation of parts already pushed, it
> would make sense to have them too.
>
> 4/ jQuery upgrade
> Owen suggested to upgrade our jQuery on bug 15883, it is a nice to
> have for the next release.
>
> 5/ Bug fixes
> * CGI->multi_param
> You have certainly notice the "CGI::param called in list context"
> warnings in the logs. We are going to get rid of them with bug 16154 -
> Replace CGI->param with CGI->multi_param in list context
> * Regression on currency
> This will become a blocker if not signed off soon. See bug 16227 - The
> currencies of vendor and order do not display correctly
> * The OPAC is not accessible if JS is disabled (blocker)!
> See bug 16210 (Bug 15111 breaks the OPAC if JavaScript is disabled) for a
> fix
>
> 6/ Versioning change
> It seems that we voted [1] for changing the versioning to be date
> based. Does someone work on that? There are adjustments to do to the
> codebase to make it work. But we also need to decide how to number the
> 2 annual major versions and the minors.
>

I was thinking 2 majors would be 16.05 and 16.11
minors would be 16.05.01 (for first RMaint of 16.05) and increase
incrementally.
Dev (unstable) would be 16.06 and then 17.00

I am and was willing to work on the patches for the version changes but was
waiting until after the Freeze to do that.  If you have any comments for me
Jonathan that's great - I'll always take them.


>
> Feel free to add more if you think about something.
>
> Note: please sort by severity when you are searching for a bug to sign
> off [2], blocker, critical and major have to be signoff before
> cosmetic bugs ;)
>
> Cheers,
> Jonathan
>
> PS: Note that there are 5 points before the 6th!
>
> [1]
> http://meetings.koha-community.org/2016/genereal_irc_meeting_9_march_2016.2016-03-09-20.00.log.html
> )
> [2]
> https://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=Needs%20Signoff=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity_id=160792=bug_severity%2Cassigned_to%2Cbug_id%20DESC_based_on=Needs%20Signoff_format=advanced
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] International ES sign-off testing day (next Tuesday/Wednesday)

[Nick Clemens]

Tomas has updated kohadevbox/ansible and you should now get a running
elasticsearch instance by adding KOHA_ELASTICSEARCH=1
to your vagrant up as below

KOHA_ELASTICSEARCH=1 vagrant up

The wiki page for getting started has also been updated for those not using
kohadevbox:
https://wiki.koha-community.org/wiki/Elasticsearch#Configuration

I will be in channel and Chris will be in later

-Nick




On Mon, Apr 11, 2016 at 10:08 PM Nick Clemens 
wrote:

> Hello All,
>
> I hit some snags in getting a running elastic server up, but I do have a
> working zebra site up. Turning on elastic here will not work.
>
> One main goal of the testing is to confirm that the patches break nothing
> if Zebra is selected as the search engine with the ES code present, so
> testing on this branch and ensuring that everything works as it should is
> an important part of the work.
>
>
> Staff interface:
> http://staff-elastic.bwsdev.bywatersolutions.com/
>
> OPAC interface:
> http://elastic.bwsdev.bywatersolutions.com/
>
> user/pass: zebra/zebra
>
>
> I will keep working on getting a working elastic installation going and
> will update asap.
>
> -Nick (kidclamp)
>
>
> On Mon, Apr 11, 2016 at 4:10 PM Chris Cormack 
> wrote:
>
>> * Barton Chittenden (bar...@bywatersolutions.com) wrote:
>> > Leading in to the testing -- is there any documentation on
>> >
>> > * Adding indexes for ES?
>>
>> See bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899
>>
>> > * Support for unicode/i18n in ES?
>>
>> You can read the ES documentation for that
>>
>> > * Understanding how ES handles relevance (and how this is configured in
>> Koha)
>> >
>> As above.
>>
>> Basically I don't want people to spend time focusing on these things
>> tomorrow.
>> We want to be sure that all the scaffolding code and the basic ES support
>> does
>> not break current functionality.
>>
>> Once it is in master there are already other bugs to enhance and extend
>> it. But
>> it gets harder and harder to get in the more we try to add to it first.
>>
>> Chris
>>
>>
>> > On Sun, Apr 10, 2016 at 5:58 AM, Katrin Fischer <
>> katrin.fischer...@web.de>
>> > wrote:
>> >
>> > Hi Brendan,
>> >
>> > could you share some link as we have on the agendas for the
>> meetings to
>> > define the time window?
>> >
>> > Have a nice weekend,
>> >
>> > Katrin
>> >
>> > Am 07.04.2016 um 23:52 schrieb Brendan Gallagher:
>> > > Hello All -
>> > >
>> > > I am hoping that we could have a day next week where we are in irc
>> > > channel #koha and do some testing of Elastic.  Ideally target
>> that to be
>> > > Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me.  The
>> idea is
>> > > that we'll have Chris (rangi) in channel to look at problems and
>> fix
>> > > problems that day as we bring them up to him.  Nick (kidclamp)
>> from
>> > > ByWater will also be present as he has done the most testing on
>> our side.
>> > >
>> > > Ideally we'll have some ES installs setup - hopefully (we bywater
>> will
>> > > have 2 identical datasets - 1 running ES and 1 running zebra (but
>> with
>> > > the ES code installed))...  More setups are welcome.
>> > >
>> > > We could hopefully get everything set well so that we could get a
>> > > sign-off that day and get this into QA.  Also another thought is
>> that we
>> > > edit a wiki-page so that we can list things that ES is doing
>> already -
>> > > what system preferences effect it etc.
>> > >
>> > > Thanks,
>> > > Brendan
>> > >
>> > > --
>> > >
>> >
>>  
>> ---
>> > > Brendan A. Gallagher
>> > > ByWater Solutions
>> > > CEO
>> > >
>> > >
>> > >
>> > >
>> > > ___
>> > > Koha-devel mailing list
>> > > Koha-devel@lists.koha-community.org
>> > >
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> > > website : http://www.koha-community.org/
>> > > git : http://git.koha-community.org/
>> > > bugs : http://bugs.koha-community.org/
>> > >
>> >
>> > ___
>> > Koha-devel mailing list
>> > Koha-devel@lists.koha-community.org
>> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> > website : http://www.koha-community.org/
>> > git : http://git.koha-community.org/
>> > bugs : http://bugs.koha-community.org/
>> >
>> >
>>
>> > ___
>> > Koha-devel mailing list
>> > Koha-devel@lists.koha-community.org
>> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> > website : http://www.koha-community.org/
>> > git : http://git.koha-community.org/
>> > bugs : http://bugs.koha-community.org/
>>
>>
>> --
>> Chris Cormack