As per our email exchange outside of the forum.. I won't complicate things / distract you guys by seeking my own read access to the repository.
I will however keenly await the public 1.4 release build to be posted here on SourceForge and proceed to offer up donated time / modules / code extensions from there.
Alex - What is your project's approach to assertaining what feature request (As listed here on SF or received via allocPSA.org) would be of broad interest to the entire (Or at least a majority) of the user-base, without negativly impacting on a significant other constituentcy of the same user-base?
The question behind the question is - There are things that "I" think are 'useful' features because they suit how I want to structure / operate my own Professional Services Business... But such modification may not be everyone's (or a least a majority of everyone's) cup of tea, So such 'mods' may be run on our install - but not be of use to the AllocPSA project overall.
I would like to work on and contribute some requested features which you guys deem to be of use to the AllocPSA project and it's user-base, hopefully things that we also immediately benefit from as part of the user-base group.
So.. Will there be some features not part of the 1.4 release that have been requested but you have not have time to work on yet?
I know it's a little crystal ball gazing - I apologise for the vagueness of the question. Any imput warmly welcomed (When you have a moment)
Regards,
JW.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's really a question of taking each piece of functionality and examining it independantly.
But in all probability, if you've made a change, and it helps your PSA company, then it is likely to help other PSA's as well. And thus it's likely to be included with minimum of fuss. I need to actually see some of the stuff you've worked on though :)
In terms of criteria for accepting new code:
it must not tread on Cybersources toes (they created allocPSA, and continue to put funds into it)
if the code gets moved over to GPLv3/AGPL we may ask you to sign a copyright disclaimer
I realise that's probably not a lot of help, but it should give you an idea of where my priorities are in terms of accepting new code. If you are contemplating working on a new feature, and you give us a yell first, we may well be able to give you a well directed shove in the "right" direction..
Don't hesitate to let me know if I can be of more assistance.
Cheers,
Alex Lance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
we're still working on about 30 or so functional improvements in the current release candidate, so it's likely to be a few weeks yet. We're also undergoing an office relocation, which merely adds to the challenge... Bear with us ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just to let you know we are going to be pushing out 1.4 sometime this week. It is great to hear that you have done some changes. Would you like read access to the developer repository? (we use darcs for source code version control).
Alternatively you might like to submit diff/patches and we can try and integrate the changes for you. Please note that although we will try and integrate your new features, generally we will only incorporate changes that look to benefit the entire allocPSA community. So any company specific changes probably won't make it in.
You can email me directly if you like alex at allocpsa.com, but it's probably preferable to continue the dialog on the forums so that other developers can benefit from any discussion.
Cheers,
Alex Lance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Guys
When is 1.4 scheduled to be released? What are the major features planned for this release. I'm looking at deploying this in our small firm.
The current version though looks good is not sufficient on Reports and time sheets part. They need overhauling interms of input and output.
Thanks
itboffin
Alex,
As per our email exchange outside of the forum.. I won't complicate things / distract you guys by seeking my own read access to the repository.
I will however keenly await the public 1.4 release build to be posted here on SourceForge and proceed to offer up donated time / modules / code extensions from there.
Alex - What is your project's approach to assertaining what feature request (As listed here on SF or received via allocPSA.org) would be of broad interest to the entire (Or at least a majority) of the user-base, without negativly impacting on a significant other constituentcy of the same user-base?
The question behind the question is - There are things that "I" think are 'useful' features because they suit how I want to structure / operate my own Professional Services Business... But such modification may not be everyone's (or a least a majority of everyone's) cup of tea, So such 'mods' may be run on our install - but not be of use to the AllocPSA project overall.
I would like to work on and contribute some requested features which you guys deem to be of use to the AllocPSA project and it's user-base, hopefully things that we also immediately benefit from as part of the user-base group.
So.. Will there be some features not part of the 1.4 release that have been requested but you have not have time to work on yet?
I know it's a little crystal ball gazing - I apologise for the vagueness of the question. Any imput warmly welcomed (When you have a moment)
Regards,
JW.
Hi JW,
It's really a question of taking each piece of functionality and examining it independantly.
But in all probability, if you've made a change, and it helps your PSA company, then it is likely to help other PSA's as well. And thus it's likely to be included with minimum of fuss. I need to actually see some of the stuff you've worked on though :)
In terms of criteria for accepting new code:
I realise that's probably not a lot of help, but it should give you an idea of where my priorities are in terms of accepting new code. If you are contemplating working on a new feature, and you give us a yell first, we may well be able to give you a well directed shove in the "right" direction..
Don't hesitate to let me know if I can be of more assistance.
Cheers,
Alex Lance
Hi itboffin.
We're in the last stages of inhouse testing of allocPSA 1.4. Our hope is to have it out the door over the coming few weeks.
Good to hear. I too am looking forward to the next release. I know there will be an invoices module which will be great.
How has your internal testing gone?
I am looking forward to using time before Christmas to contribute some code.
Have you earmarked a day to post to the CVS ?
Very Supportive,
J.W
Howdy,
we're still working on about 30 or so functional improvements in the current release candidate, so it's likely to be a few weeks yet. We're also undergoing an office relocation, which merely adds to the challenge... Bear with us ;-)
M.C & H.N.Y :
Hope the office move went well. 1.4 Is keenly awaited by us users & interested parties.
I personally spent a good deal of time modding and hacking at our installed 1.3.
My hope is to roll my fundamental application level knowledge into useful extensions to 1.4.
Any of these which are useful will be made avaiable to all under GPL.
When do you anticipate circulating a 1.4 Alpha/Beta/RC ?
Regards,
J.W
Hi J.W,
Just to let you know we are going to be pushing out 1.4 sometime this week. It is great to hear that you have done some changes. Would you like read access to the developer repository? (we use darcs for source code version control).
Alternatively you might like to submit diff/patches and we can try and integrate the changes for you. Please note that although we will try and integrate your new features, generally we will only incorporate changes that look to benefit the entire allocPSA community. So any company specific changes probably won't make it in.
You can email me directly if you like alex at allocpsa.com, but it's probably preferable to continue the dialog on the forums so that other developers can benefit from any discussion.
Cheers,
Alex Lance