Thread: [Openledger-developer] where is everyone?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

just wonder if this project is still running...
please reply!!!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

on 04/05/05 19:24 Ang Tun Chek wrote:

> just wonder if this project is still running... please reply!!!

To me it is. However I believe someone has to find the time (ie.
priorities) to further it.
I will continue scratching my own itch, as I find the time and I HOPE
that others will come along and see the value of a Community Ledger
Software package, and want to spend their time here.

How to further this.. I guess writing something better on the
openledger.sf.net homepage would be a start :)
All ideas are welcome, and if anyone wants to commit code - feel free.

p.s. Ang - pls. do follow the CVS guide on SF - you have CVS access,
so you can happily play along with the current code - and implement
your login code.
p.p.s. I do think it is "wrong" to include SL code for login handling
- - I'd prefer moving the code to the new API - as the old code is
supposed to "go away", once the OpenLedger API supports everything
that is needed.

The code in CVS already, serves me very well every day.

I think, for this project to gain momentum, we would have to get the
attention of some of the projects that could use an accounting backend
- - without having to code it themselves. Much of the code they'd need
is already available in OpenLedger.pm.

[SNIP]

- --
Regards,
Klavs Klavsen, GSEC - kl...@vs... - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8  B8DA 3D3A 0B79 7E06 3C62

"Those who do not understand Unix are condemned to reinvent it, poorly."
  --Henry Spencer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCUl0kPToLeX4GPGIRAoshAJ4inYBtZZ2Z4kF6PfEquCen/gNEVgCfRxI+
F853sbzYec5vomymPKFsZvI=
=87ps
-----END PGP SIGNATURE-----

>p.s. Ang - pls. do follow the CVS guide on SF - you have CVS access,
>so you can happily play along with the current code - and implement
>your login code.
>  
>
Ok i will try that

>p.p.s. I do think it is "wrong" to include SL code for login handling
>- - I'd prefer moving the code to the new API - as the old code is
>supposed to "go away", once the OpenLedger API supports everything
>that is needed.
>
>The code in CVS already, serves me very well every day.
>  
>
well i will just stick with this login function first until we found a 
new way.

On Tue, 2005-04-05 at 17:24 +0000, Ang Tun Chek wrote:
> just wonder if this project is still running...
> please reply!!!

Thanks Ang, I was wondering the same thing.

I too am interested in helping this project along. I could go approach
other SL forks, other projects in need of a backend, and hopefully in
the future attract dollars to support ongoing development.

I see some hurdles though. 

Hurdle 1 - Decision making
How do we decide on issues like archetecture and commit priviledges.
Sooner or later we'll have a conflict arise and without some process for
deciding we're screwed. I'd propose that Klavs and two other people form
an initial leadership team. I'd want most discussion and decision making
to come from this list, but for tough decisions I'd want a clear process
for reaching a decision

Hurdle 2 - Nah, the rest of the hurdles are bumps compared to the issue
of our own self governance... what do people think about that first
hurdle?

David

On Wed, 2005-04-06 at 10:36 -0700, David Pool wrote:
> 
> Hurdle 1 - Decision making
> How do we decide on issues like archetecture and commit priviledges.
> Sooner or later we'll have a conflict arise and without some process
> for
> deciding we're screwed. I'd propose that Klavs and two other people
> form
> an initial leadership team. I'd want most discussion and decision
> making
> to come from this list, but for tough decisions I'd want a clear
> process
> for reaching a decision

I'm not a developer (I could write instruction manual for the rest of
us) but the best approach would be democratic one via voting between
those who contribute.
If somebody is against one approach or another he/she should point the
problem and suggest better solution.

Just my 0.2  

-- 
#Joseph

On Wed, 2005-04-06 at 12:02 -0600, Joseph wrote:
> On Wed, 2005-04-06 at 10:36 -0700, David Pool wrote:
> > 
> > Hurdle 1 - Decision making
> > How do we decide on issues like archetecture and commit priviledges.
> > Sooner or later we'll have a conflict arise and without some process
> > for
> > deciding we're screwed. I'd propose that Klavs and two other people
> > form
> > an initial leadership team. I'd want most discussion and decision
> > making
> > to come from this list, but for tough decisions I'd want a clear
> > process
> > for reaching a decision
> 
> I'm not a developer (I could write instruction manual for the rest of
> us) but the best approach would be democratic one via voting between
> those who contribute.

"those who contribute" is too ambiguous for dealing with contentious
issues. I'd agree with the concept but suggest a model like Apache where
the initial team nominates and votes in people who have shown that they
are contributing to the project.

> If somebody is against one approach or another he/she should point the
> problem and suggest better solution.

This is the heart of open source and independent of having a decision
making group. Most issues should be hashed out on the Openledger-
developer list just as you suggest. If it comes down to two conflicting
patches against the core project there should be a decision making group
that can decide.

This group's functioning should be fair game for discussion. The SQL
Ledger leader's decision to squelch conversation about the direction of
that project is what brought me to Open Ledger. To me Free Software
implies Free Speech.

David

To all
i am happy to see some responses here, at least we are not alone. well, 
i will just keep going with my code because i am believe we have to get 
the fundamental done first then modify as needed. ok, this is what i am 
going to do now.

1) Complete Customer, Vendor class
2) upload sql tables
3) enhance User class

currently i will stick with what SL has and probably import some feature 
from my OBA projects (fork of SL)
http://oba.sourceforge.net

btw, i want to know who can do what in this projects, like joseph , he 
can write a manual! if anyone of you want to contribute something but 
dont know how. please let us know. we will give you some job to do  :)

cheers
Ang

Thread: [Openledger-developer] where is everyone?

openledger-developer