Hi to all,
At 12.19 17/03/2010, Zeno Tajoli wrote:
>with specific patches for 3.0.x now is important to install the
>modules Text::CSV::Encoded.
I have done same seach on the topic.
The module Text::CSV::Encoded is not available in Debian lenny.
We need to install it with CPAN.
For 3.2 I have u
Hi to all,
[sorry for the previous post, this the post with all info]
At 12.19 17/03/2010, Zeno Tajoli wrote:
>with specific patches for 3.0.x now is important to install the
>modules Text::CSV::Encoded.
I have done same seach on the topic.
The module Text::CSV::Encoded is not available in Debi
*Hello all,
I just wanted to know who Koha uses MARC21 exactly. I mean where is it
installed in Koha, how to develop and maintain the formats of MARC21 in
Koha.
Thanks,
Musab*
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org
Dear Sirs
I
would like to deploy the software library koha at the institution where
I work, I saw that it has support for LDAP but I installed version
3.00.4 and aunteticação this does not work, and my mapping information
is correct. Someone please tell me know if you already got it authenticates
Hi all,
I know that we're all busy, but this idea is for the best of the
future of Koha - with better documentation for developers we can
attract more skilled developers - and improve the work of those trying
to help with development now ... so is anyone interested in being on a
committee?
Thanks
On Thu, Mar 18, 2010 at 10:47 AM, Nicole Engard wrote:
> Hi all,
>
> I know that we're all busy, but this idea is for the best of the
> future of Koha - with better documentation for developers we can
> attract more skilled developers - and improve the work of those trying
> to help with developme
I'll volunteer for this. Documentation is crucial, sometimes moreso than
the code itself.
-Ian Walls
On Thu, Mar 18, 2010 at 10:57 AM, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:
> On Thu, Mar 18, 2010 at 10:47 AM, Nicole Engard wrote:
> > Hi all,
> >
> > I know that we're all bus
Hi,
On Mon, Mar 8, 2010 at 1:20 PM, Nicole Engard wrote:
> This manual will of course be available via git and written using
> docbook - this means that others can help me write (in fact I
> encourage it). My first step is to review the wiki and pull out tips
> and articles and guidelines that s
On 18/03/10 14:47, Nicole Engard wrote:
> Hi all,
>
> I know that we're all busy, but this idea is for the best of the
> future of Koha - with better documentation for developers we can
> attract more skilled developers - and improve the work of those trying
> to help with development now ... so is
On Thu, Mar 18, 2010 at 11:15 AM, Galen Charlton wrote:
> Developer documentation is a good thing, but I don't think that a
> DocBook document is necessarily the best way to present it - it does
> not encourage on-the-fly updates, and the idea of a Koha developer
> documentation committee that a
Hi,
On Thu, Mar 18, 2010 at 11:43 AM, Nicole Engard wrote:
> The wiki is not organized - it's way too hard to navigate for someone
> who is not familiar with is and adding more links is not going to help
> - in my opinion - and the point is to make it easy for those who are
> not familiar with th
On Thu, Mar 18, 2010 at 11:55 AM, Galen Charlton wrote:
> And not all people interested in development will read a manual. :)
> Some will, of course, but ultimately, we'll have to be sensitive to
> the fact that there will be a lot of paths for people to become Koha
> developers. In any event, m
On 19 March 2010 04:59, Nicole Engard wrote:
> On Thu, Mar 18, 2010 at 11:55 AM, Galen Charlton wrote:
>
>> And not all people interested in development will read a manual. :)
>> Some will, of course, but ultimately, we'll have to be sensitive to
>> the fact that there will be a lot of paths for
It's a thorny problem, there are several distinct classes of
documentation and each are least worst served by different schemes.
- style guides and other "how to do business" -- something formal but
easy to edit like a well sorted wiki section with a designated
caretaker to keep it nice
- design
Of course I can :) It was Nicolas at BibLibre - and maybe some others
over there. Also it was something I asked for first ;) so I could
find documentation on how to participate and it was suggested that as
doc manager I could work on that - but I can't do it alone cause I
don't know the rules :) -
Hi Reed
As we want to bridge the gap between developers and users and assist users
to become (or engage more with) developers and developers to become better
users, is it wise to repeat something you say "I've never seen it done
well"?
My suggestion is that one adds to the 4 categories of develop
On 19 March 2010 11:44, Irma Birchall wrote:
> Hi Reed
>
> As we want to bridge the gap between developers and users and assist users
> to become (or engage more with) developers and developers to become better
> users, is it wise to repeat something you say "I've never seen it done
> well"?
>
Wha
On Fri, 2010-03-19 at 11:51 +1300, Chris Cormack wrote:
> It's building that culture that is the tricky bit. Dev changes so fast
> that we need to make sure the doc changes with it, having it in the
> same place as the code and having an expectation that patches that
> change code, change the doc t
On Fri, Mar 19, 2010 at 11:44 AM, Irma Birchall wrote:
> Hi Reed
>
> As we want to bridge the gap between developers and users and assist users
> to become (or engage more with) developers and developers to become better
> users, is it wise to repeat something you say "I've never seen it done
> we
19 matches
Mail list logo
