I just wanted to state that I have a developer that I am working with in
house who is pretty good, but would like to better understand how all the
"pieces" work together. .tmpl, .pl, inc - there are statements that refer
to things that he can't find, I don't konw if that is because it is part of
I'd like to help if I can. I am not a programmer per se, but would like to
help make Koha more accessible. I often have questions that lead to dead
ends and more questions, like my experience yesterday on the Koha IRC. My
standpoint is somewhat between the developer and the librarian. I try to
On Sat, Mar 20, 2010 at 11:43 AM, Nicole Engard wrote:
> I'm looking for a guide for those new to programming for Koha - rules
> on how to participate, rules on what to do and not do, rules on where
> to start - so a newbie guide to jumping into Koha as a developer.
>
> Nicole
Ah! Sorry, I misse
On 20 March 2010 11:43, Nicole Engard wrote:
> I'm looking for a guide for those new to programming for Koha - rules
> on how to participate, rules on what to do and not do, rules on where
> to start - so a newbie guide to jumping into Koha as a developer.
>
If you substitute the world guideline f
I'm looking for a guide for those new to programming for Koha - rules
on how to participate, rules on what to do and not do, rules on where
to start - so a newbie guide to jumping into Koha as a developer.
Nicole
On Fri, Mar 19, 2010 at 4:03 PM, Chris Cormack wrote:
> On 20 March 2010 01:11, Nic
On 20 March 2010 01:11, Nicole Engard wrote:
> On Thu, Mar 18, 2010 at 6:51 PM, Chris Cormack
> wrote:
>
>> Yep, that's the easy bit, getting developers to write it is the trick.
>
> That's what I was trying to do - to do the writing for the developers
> based on info I gathered by talking to th
On Thu, Mar 18, 2010 at 6:51 PM, Chris Cormack wrote:
> Yep, that's the easy bit, getting developers to write it is the trick.
That's what I was trying to do - to do the writing for the developers
based on info I gathered by talking to them ... the problem with
developer written documentation is
Hi,
On Fri, Mar 19, 2010 at 4:47 AM, LAURENT Henri-Damien
wrote:
> Another thing we have to consider is to document and formalize the way
> things could be done.
> a) Make more packages,
> b) Should we Should we make API changes ? If so Is there a concensus to
> gather about those ?
[snip]
Good
Chris Cormack a écrit :
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 i
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
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 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
ayered manual.
Cheers,
Irma
CALYX
-Original Message-
From: koha-devel-boun...@lists.koha.org
[mailto:koha-devel-boun...@lists.koha.org] On Behalf Of Reed Wade
Sent: Friday, 19 March 2010 7:32 AM
To: Koha Devel
Subject: Re: [Koha-devel] Developer Documentation
It's a thorny proble
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 :) -
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
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
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
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: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
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
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
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
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
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
24 matches
Mail list logo
