You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Olemis Lang <ol...@gmail.com> on 2013/07/18 20:38:09 UTC
Provide XmlRpcPlugin in default installation WAS: [GSoC - Embeddable
Objects] Question regarding ticket queries and ticket changes
On 7/18/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> On 18 July 2013 04:55, Olemis Lang <ol...@gmail.com> wrote:
>> On 7/17/13, Antonia Horincar <an...@gmail.com> wrote:
>> > Hi,
>> >
>>
>> :)
>>
>> > Sorry for the late reply. By using the two methods mentioned above
>> > (changeLog and query) I managed to get what I wanted. However, I'm not
>> sure
>> > if I'm supposed to integrate the entire Bloodhound RPC plugin in my
>> > project, or just extract the methods?
>> >
>>
>> I recommend to declare Bloodhound RPC plugin as a dependency in
>> setup.py just like any other (Python) library you might choose to
>> build your project. There is a case for including it in default
>> installation (eventually) e.g. quick ticket shortcut in Bloodhound
>> theme .
>>
>
> I seem to remember there was also a case against it previously
I can not find the exact messages but now I recall this might be the case .
> - how has
> that been addressed?
>
We have not had discussions on the subject recently. Nevertheless if
the solution implemented by Antonia will cover (eventually) any
objects in core then she'll end-up doing one of two things :
- Reimplementing the very same RPC methods
- Copying almost all RPC methods
* Should improvements be committed in Bloodhound RPC
plugin those modifications will be hard to maintain
trachacks:XmlRpcPlugin may be used as a data access layer by core and
plugins . That's the case even for trac-dev (citation needed)
--
Regards,
Olemis.
Re: Provide XmlRpcPlugin in default installation WAS: [GSoC -
Embeddable Objects] Question regarding ticket queries and ticket changes
Posted by Olemis Lang <ol...@gmail.com>.
On 7/21/13, Olemis Lang <ol...@gmail.com> wrote:
> Hi !
> :)
>
> On 7/20/13, Antonia Horincar <an...@gmail.com> wrote:
>> I'm a bit confused now, should I declare the BloodhoundRPC plugin as a
>> dependency then?
>
> Requested inclusion should be similar to ThemeEnginePlugin ,
> AccountManagerPlugin ... i.e. by including the plugin in pip-spec file
> requirements-dev.txt
>
... but let's wait for other opinions so that you can move forward
with this subject . It deserves more thinking and comments .
--
Regards,
Olemis.
Re: Provide XmlRpcPlugin in default installation WAS: [GSoC -
Embeddable Objects] Question regarding ticket queries and ticket changes
Posted by Olemis Lang <ol...@gmail.com>.
Hi !
:)
On 7/20/13, Antonia Horincar <an...@gmail.com> wrote:
> I'm a bit confused now, should I declare the BloodhoundRPC plugin as a
> dependency then?
Requested inclusion should be similar to ThemeEnginePlugin ,
AccountManagerPlugin ... i.e. by including the plugin in pip-spec file
requirements-dev.txt
> Or should I mention in my api that the query() and
> changeLog() methods were created by Olemis?
>
That's gray area ... Those are not indeed *my* methods . See the list
of authors and contributors [1]_
.. [1] http://trac-hacks.org/wiki/XmlRpcPlugin#AuthorContributors
--
Regards,
Olemis.
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Provide XmlRpcPlugin in default installation WAS: [GSoC -
Embeddable Objects] Question regarding ticket queries and ticket changes
Posted by Antonia Horincar <an...@gmail.com>.
I'm a bit confused now, should I declare the BloodhoundRPC plugin as a
dependency then? Or should I mention in my api that the query() and
changeLog() methods were created by Olemis?
Thanks,
Antonia
On Thu, Jul 18, 2013 at 9:38 PM, Olemis Lang <ol...@gmail.com> wrote:
> On 7/18/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> > On 18 July 2013 04:55, Olemis Lang <ol...@gmail.com> wrote:
> >> On 7/17/13, Antonia Horincar <an...@gmail.com> wrote:
> >> > Hi,
> >> >
> >>
> >> :)
> >>
> >> > Sorry for the late reply. By using the two methods mentioned above
> >> > (changeLog and query) I managed to get what I wanted. However, I'm not
> >> sure
> >> > if I'm supposed to integrate the entire Bloodhound RPC plugin in my
> >> > project, or just extract the methods?
> >> >
> >>
> >> I recommend to declare Bloodhound RPC plugin as a dependency in
> >> setup.py just like any other (Python) library you might choose to
> >> build your project. There is a case for including it in default
> >> installation (eventually) e.g. quick ticket shortcut in Bloodhound
> >> theme .
> >>
> >
> > I seem to remember there was also a case against it previously
>
> I can not find the exact messages but now I recall this might be the case .
>
> > - how has
> > that been addressed?
> >
>
> We have not had discussions on the subject recently. Nevertheless if
> the solution implemented by Antonia will cover (eventually) any
> objects in core then she'll end-up doing one of two things :
>
> - Reimplementing the very same RPC methods
> - Copying almost all RPC methods
> * Should improvements be committed in Bloodhound RPC
> plugin those modifications will be hard to maintain
>
> trachacks:XmlRpcPlugin may be used as a data access layer by core and
> plugins . That's the case even for trac-dev (citation needed)
>
> --
> Regards,
>
> Olemis.
>