|
Ideas to improve vtiger / feedback to bugs on trac
Hello there,
I’m from a company in Germany.
We’re currently starting to use vtiger. We’re really happy with vtiger, but
we’ve found some bugs, which we already reported at the bug-tracker (bugs 6291
and 6292). Additionally, we have some ideas for enhancements, which we also
reported (bugs 6293, 6315, 6316, 6317). Unfortunately we didn’t get any feedback
yet. Some of these issues are already implemented by me (patch is attached to
the bug), others could be implemented in the near future.
We’re really willing to provide some
code for fixing those bugs and to implement the enhancements. But we would need
the feedback, that those issue will be integrated into one of the next vtiger
releases. Otherwise our coding would be in vain. Or we would have to patch our
enhancements into the official vtiger releases every time we’re running an
update of vtiger, which would be very annoying.
Maybe these enhancements could also
be usable for others? Especially the webservice upgrading (bug 6318, 6319, 6320) could be suitable for many
others.
If you agree with me I would implement those enhancements and offer
them to you. If you are at variance with some points please let me know. We
could adapt things to meet your needs.
I would be really glad to get any
feedback (Bug x will (not) be integrated into the official release / could be
integrated, if you also implement additional feature y / …). We really would
like to work on vtiger and help improving it!
Regards,
Stefan
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi Stefan, Thanks for your contributions towards bug fixed and
enhancement patches. Sorry to not give you quick updates on the
contributions. We would definitely like to consider your contributions
for integration.
Right now we are slightly tied up with development task and
couldn't review the trac tickets. We will be taking up this task soon
and will update you in a time span of 2-3 weeks. On 9/17/09, Paproth, Stefan <paproth@...> wrote:
Hello there,
I’m from a company in Germany.
We’re currently starting to use vtiger. We’re really happy with vtiger, but
we’ve found some bugs, which we already reported at the bug-tracker (bugs 6291
and 6292). Additionally, we have some ideas for enhancements, which we also
reported (bugs 6293, 6315, 6316, 6317). Unfortunately we didn’t get any feedback
yet. Some of these issues are already implemented by me (patch is attached to
the bug), others could be implemented in the near future.
We’re really willing to provide some
code for fixing those bugs and to implement the enhancements. But we would need
the feedback, that those issue will be integrated into one of the next vtiger
releases. Otherwise our coding would be in vain. Or we would have to patch our
enhancements into the official vtiger releases every time we’re running an
update of vtiger, which would be very annoying.
Maybe these enhancements could also
be usable for others? Especially the webservice upgrading (bug 6318, 6319, 6320) could be suitable for many
others.
If you agree with me I would implement those enhancements and offer
them to you. If you are at variance with some points please let me know. We
could adapt things to meet your needs.
I would be really glad to get any
feedback (Bug x will (not) be integrated into the official release / could be
integrated, if you also implement additional feature y / …). We really would
like to work on vtiger and help improving it!
Regards,
Stefan
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
--
Regards, Asha vtiger Team
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Quoting "Paproth, Stefan" < paproth@...>:
> Hello there,
>
> I'm from a company in Germany. We're currently starting to use vtiger.
> We're really happy with vtiger, but we've found some bugs, which we
> already reported at the bug-tracker (bugs 6291 and 6292). Additionally,
> we have some ideas for enhancements, which we also reported (bugs 6293,
> 6315, 6316, 6317). Unfortunately we didn't get any feedback yet. Some of
> these issues are already implemented by me (patch is attached to the
> bug), others could be implemented in the near future.
>
There are also instances where the reported bugs are closed without
contacting the reporter/requester for feedback or providing amble
description.
Please have a look at this bug:
http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001IMHO, these kind of responses are not suitable for a community project.
--
Manilal K M
eJyothi Services
http://www.ejyothi.com_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Hi Manilal, http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001
Kindly note that milestone of this bug has been droped but its not closed.
We will update comment before closing the ticket.
Regards,
Prasad
vtiger Team
On 9/18/09, Manilal K M <manilal@...> wrote:
Quoting "Paproth, Stefan" <paproth@...>:
> Hello there,
>
> I'm from a company in Germany. We're currently starting to use vtiger.
> We're really happy with vtiger, but we've found some bugs, which we
> already reported at the bug-tracker (bugs 6291 and 6292). Additionally,
> we have some ideas for enhancements, which we also reported (bugs 6293,
> 6315, 6316, 6317). Unfortunately we didn't get any feedback yet. Some of
> these issues are already implemented by me (patch is attached to the
> bug), others could be implemented in the near future.
>
There are also instances where the reported bugs are closed without
contacting the reporter/requester for feedback or providing amble
description.
Please have a look at this bug:
http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001
IMHO, these kind of responses are not suitable for a community project.
--
Manilal K M
eJyothi Services
http://www.ejyothi.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Prasad,
Thanks for the clarification. Instead of deleting the milestone it
may be nice if it has been changed(I'm not sure about whether trac
permits such actions). A bug/issue without a milestone implicates that
it's never going to be fixed. Note that this issue was opened three
years ago and LDAP integration is a critical component in the
enterprise.
thanks
Manilal
Quoting Prasad < prasad@...>:
> Hi Manilal,
>
> http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001>
>
> Kindly note that milestone of this bug has been droped but its not closed.
>
> We will update comment before closing the ticket.
>
> Regards,
> Prasad
> vtiger Team
>
> On 9/18/09, Manilal K M < manilal@...> wrote:
>>
>>
>> Quoting "Paproth, Stefan" < paproth@...>:
>>
>> > Hello there,
>> >
>> > I'm from a company in Germany. We're currently starting to use vtiger.
>> > We're really happy with vtiger, but we've found some bugs, which we
>> > already reported at the bug-tracker (bugs 6291 and 6292). Additionally,
>> > we have some ideas for enhancements, which we also reported (bugs 6293,
>> > 6315, 6316, 6317). Unfortunately we didn't get any feedback yet. Some of
>> > these issues are already implemented by me (patch is attached to the
>> > bug), others could be implemented in the near future.
>> >
>>
>>
>> There are also instances where the reported bugs are closed without
>> contacting the reporter/requester for feedback or providing amble
>> description.
>>
>> Please have a look at this bug:
>> http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001>>
>> IMHO, these kind of responses are not suitable for a community project.
>>
>>
>> --
>> Manilal K M
>> eJyothi Services
>> http://www.ejyothi.com>>
>>
>> _______________________________________________
>> Reach hundreds of potential candidates - http://jobs.vtiger.com>>
>
--
Manilal K M
eJyothi Services
http://www.ejyothi.com_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Hi Manilal,
A bug/issue without a milestone implicates that it's never going to be fixed. Note that this issue was opened three
years ago and LDAP integration is a critical component in the enterprise.
We review all the open issue without milestone before start of bug-fixing cycle, so do not worry.
LDAP contributions and discussion are being done on the forums regularly.
Our team is reviewing the integration but are also tied up with other features development. We will update you on that shortly.
Regards,
Prasad
vtiger Team
On 9/18/09, Manilal K M <manilal@...> wrote:
Prasad,
Thanks for the clarification. Instead of deleting the milestone it
may be nice if it has been changed(I'm not sure about whether trac
permits such actions). A bug/issue without a milestone implicates that
it's never going to be fixed. Note that this issue was opened three
years ago and LDAP integration is a critical component in the
enterprise.
thanks
Manilal
Quoting Prasad <prasad@...>:
> Hi Manilal,
>
> http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001
>
>
> Kindly note that milestone of this bug has been droped but its not closed.
>
> We will update comment before closing the ticket.
>
> Regards,
> Prasad
> vtiger Team
>
> On 9/18/09, Manilal K M <manilal@...> wrote:
>>
>>
>> Quoting "Paproth, Stefan" <paproth@...>:
>>
>> > Hello there,
>> >
>> > I'm from a company in Germany. We're currently starting to use vtiger.
>> > We're really happy with vtiger, but we've found some bugs, which we
>> > already reported at the bug-tracker (bugs 6291 and 6292). Additionally,
>> > we have some ideas for enhancements, which we also reported (bugs 6293,
>> > 6315, 6316, 6317). Unfortunately we didn't get any feedback yet. Some of
>> > these issues are already implemented by me (patch is attached to the
>> > bug), others could be implemented in the near future.
>> >
>>
>>
>> There are also instances where the reported bugs are closed without
>> contacting the reporter/requester for feedback or providing amble
>> description.
>>
>> Please have a look at this bug:
>> http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/2001
>>
>> IMHO, these kind of responses are not suitable for a community project.
>>
>>
>> --
>> Manilal K M
>> eJyothi Services
>> http://www.ejyothi.com
>>
>>
>> _______________________________________________
>> Reach hundreds of potential candidates - http://jobs.vtiger.com
>>
>
--
Manilal K M
eJyothi Services
http://www.ejyothi.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Hi Prasad,
> We review all the open issue without milestone before start of
> bug-fixing cycle, so do not worry.
What do you think about a new bug-state meaning something like "will not
be fixed by vtiger.com, but if the community fixes this it will be
integrated into the official vtiger release"? As my colleague Stefan
already mentioned, we would like to add some enhancements and could also
provide the source code. But we don't want to spent the time for coding
the enhancements, if they will not be integrated into vtiger. So it
would be great, if we don't have to wait until vtiger starts the
bug-fixing cycle - we could start coding earlier. The new bug-state
would also clarify the responsibility for coding the issues (vitger.com
or community), so hopefully bugs aren't fixed twice.
Regards,
Christian
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Hi Christian
Sounds like a food idea, but why not just ask vtiger to add a developer from you company onto the bug tracking system and the ticket can be assigned to you?
It might be a better way to solve the problem
Steve
-----Original Message-----
From: vtigercrm-developers-bounces@... [mailto: vtigercrm-developers-bounces@...] On Behalf Of Christian Koch
Sent: 21 September 2009 10:01 AM
To: vtigercrm-developers@...
Subject: Re: [Vtigercrm-developers] Ideas to improve vtiger / feedback to bugs on trac
Hi Prasad,
> We review all the open issue without milestone before start of
> bug-fixing cycle, so do not worry.
What do you think about a new bug-state meaning something like "will not
be fixed by vtiger.com, but if the community fixes this it will be
integrated into the official vtiger release"? As my colleague Stefan
already mentioned, we would like to add some enhancements and could also
provide the source code. But we don't want to spent the time for coding
the enhancements, if they will not be integrated into vtiger. So it
would be great, if we don't have to wait until vtiger starts the
bug-fixing cycle - we could start coding earlier. The new bug-state
would also clarify the responsibility for coding the issues (vitger.com
or community), so hopefully bugs aren't fixed twice.
Regards,
Christian
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Hi Steven,
you're right! This should be the best solution. It seems we could
assign bugs to our accounts ourself, but that wouldn't solve our
problem. We would like to get the feedback from vtiger, that it's OK to
fix the bugs / code the enhancements.
@vtiger-team: If you want the bugs reported by "paproth" to be
implemented, you could assgin them to eiher Stefan Paproth or me
(Christian Koch). Many thanks!!!
Regards,
Christian
Steven Sher schrieb:
Hi Christian
Sounds like a food idea, but why not just ask vtiger to add a developer from you company onto the bug tracking system and the ticket can be assigned to you?
It might be a better way to solve the problem
Steve
-----Original Message-----
From: vtigercrm-developers-bounces@... [vtigercrm-developers-bounces@...] On Behalf Of Christian Koch
Sent: 21 September 2009 10:01 AM
To: vtigercrm-developers@...
Subject: Re: [Vtigercrm-developers] Ideas to improve vtiger / feedback to bugs on trac
Hi Prasad,
We review all the open issue without milestone before start of
bug-fixing cycle, so do not worry.
What do you think about a new bug-state meaning something like "will not
be fixed by vtiger.com, but if the community fixes this it will be
integrated into the official vtiger release"? As my colleague Stefan
already mentioned, we would like to add some enhancements and could also
provide the source code. But we don't want to spent the time for coding
the enhancements, if they will not be integrated into vtiger. So it
would be great, if we don't have to wait until vtiger starts the
bug-fixing cycle - we could start coding earlier. The new bug-state
would also clarify the responsibility for coding the issues (vitger.com
or community), so hopefully bugs aren't fixed twice.
Regards,
Christian
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
|
Re: Ideas to improve vtiger / feedback to bugs on trac
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Hi Christian, Thanks a lot for your support. If you have a solution to the trac ticket, please do attach a patch on it. This will help us analyze the fix and integrate it if its working fine. Regards,
Prasad On 9/21/09, Christian Koch <chri.koch.vier@...> wrote:
Hi Steven,
you're right! This should be the best solution. It seems we could
assign bugs to our accounts ourself, but that wouldn't solve our
problem. We would like to get the feedback from vtiger, that it's OK to
fix the bugs / code the enhancements.
@vtiger-team: If you want the bugs reported by "paproth" to be
implemented, you could assgin them to eiher Stefan Paproth or me
(Christian Koch). Many thanks!!!
Regards,
Christian
Steven Sher schrieb:
Hi Christian
Sounds like a food idea, but why not just ask vtiger to add a developer from you company onto the bug tracking system and the ticket can be assigned to you?
It might be a better way to solve the problem
Steve
-----Original Message-----
From: vtigercrm-developers-bounces@... [vtigercrm-developers-bounces@...] On Behalf Of Christian Koch
Sent: 21 September 2009 10:01 AM
To: vtigercrm-developers@...
Subject: Re: [Vtigercrm-developers] Ideas to improve vtiger / feedback to bugs on trac
Hi Prasad,
We review all the open issue without milestone before start of
bug-fixing cycle, so do not worry.
What do you think about a new bug-state meaning something like "will not
be fixed by vtiger.com, but if the community fixes this it will be
integrated into the official vtiger release"? As my colleague Stefan
already mentioned, we would like to add some enhancements and could also
provide the source code. But we don't want to spent the time for coding
the enhancements, if they will not be integrated into vtiger. So it
would be great, if we don't have to wait until vtiger starts the
bug-fixing cycle - we could start coding earlier. The new bug-state
would also clarify the responsibility for coding the issues (vitger.com
or community), so hopefully bugs aren't fixed twice.
Regards,
Christian
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
_______________________________________________
Reach hundreds of potential candidates - http://jobs.vtiger.com
|
