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/04/02 16:20:57 UTC
Re: Ideas for Google Summer of Code
On 3/23/13, Branko Čibej <br...@wandisco.com> wrote:
> In accordance with instructions from Uli, I started creating issues in
> Jira for our GSoC candidate tasks. I started with the svnpubsub task:
>
> https://issues.apache.org/bloodhound/ticket/478
> https://issues.apache.org/jira/browse/COMDEV-84
>
> If anyone wants to help out, please do so. :) COMDEV-84 can serve as a
> template for the rest of the submissions. Please make sure that we get
> all the entries in Jira cross-referenced in our tracker, and the other
> way around.
>
> (And here's a feature proposal for ticket relations: allow
> cross-references to issues in other issue trackers.)
>
jftr ... if relationships are designed in terms of resources then
resource neighborhoods proposal [2]_ might help to get things like
this done (i.e. similar to Trac resources proposal [1]_ but with
neighborhood ID added in resource_main and resource_dest)
.. [1] TracRelations
(http://trac.edgewall.org/wiki/TracDev/Proposals/TracRelations)
.. [2] Apache™ Bloodhound resource neighborhoods proposal
(https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=33&old_version=31)
--
Regards,
Olemis.
Re: Ideas for Google Summer of Code
Posted by Olemis Lang <ol...@gmail.com>.
Good point . I just added a quick comment jftr for people following
this thread in the ML archives .
IMHO this is a bit OT when it comes to the target ticket:478 (i.e. svn
pubsub vs ticket relations) . I searched i.a.o/bh for a ticket related
to ticket relations and found nothing o.O
... so I added a note in bep:0006 , which seems to be the most related
resource we have created so far for this subject . Any other
suggestions will be welcome .
On 4/2/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> I'd be great if you could add this as a comment to the relevant ticket
> Olemis, since that's where Summer of Code applications would most likely
> check.
>
>
> On 2 April 2013 15:20, Olemis Lang <ol...@gmail.com> wrote:
>
>> On 3/23/13, Branko Čibej <br...@wandisco.com> wrote:
>> > In accordance with instructions from Uli, I started creating issues in
>> > Jira for our GSoC candidate tasks. I started with the svnpubsub task:
>> >
>> > https://issues.apache.org/bloodhound/ticket/478
>> > https://issues.apache.org/jira/browse/COMDEV-84
>> >
>> > If anyone wants to help out, please do so. :) COMDEV-84 can serve as a
>> > template for the rest of the submissions. Please make sure that we get
>> > all the entries in Jira cross-referenced in our tracker, and the other
>> > way around.
>> >
>> > (And here's a feature proposal for ticket relations: allow
>> > cross-references to issues in other issue trackers.)
>> >
>>
>> jftr ... if relationships are designed in terms of resources then
>> resource neighborhoods proposal [2]_ might help to get things like
>> this done (i.e. similar to Trac resources proposal [1]_ but with
>> neighborhood ID added in resource_main and resource_dest)
>>
>> .. [1] TracRelations
>> (http://trac.edgewall.org/wiki/TracDev/Proposals/TracRelations)
>>
>> .. [2] Apache™ Bloodhound resource neighborhoods proposal
>> (
>> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=33&old_version=31
>> )
>>
>> --
>> Regards,
>>
>> Olemis.
>>
>
>
>
> --
> Joe Dreimann | *User Experience Designer* |
> WANdisco<http://www.wandisco.com/>
>
> @jdreimann <https://twitter.com/jdreimann>
> *
> *
> *Join one of our free daily demo sessions on* *Scaling Subversion for the
> Enterprise <http://www.wandisco.com/training/webinars>*
>
> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE
> PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its
> subsidiaries, ("WANdisco") does not waive any confidentiality or privilege.
> If you are not the intended recipient, please notify us immediately and
> destroy the message without disclosing its contents to anyone. Any
> distribution, use or copying of this e-mail or the information it contains
> by other than an intended recipient is unauthorized. The views and
> opinions expressed in this e-mail message are the author's own and may not
> reflect the views and opinions of WANdisco, unless the author is authorized
> by WANdisco to express such views or opinions on its behalf. All email
> sent to or from this address is subject to electronic storage and review by
> WANdisco. Although WANdisco operates anti-virus programs, it does not
> accept responsibility for any damage whatsoever caused by viruses being
> passed.
>
--
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: Ideas for Google Summer of Code
Posted by Joachim Dreimann <jo...@wandisco.com>.
I'd be great if you could add this as a comment to the relevant ticket
Olemis, since that's where Summer of Code applications would most likely
check.
On 2 April 2013 15:20, Olemis Lang <ol...@gmail.com> wrote:
> On 3/23/13, Branko Čibej <br...@wandisco.com> wrote:
> > In accordance with instructions from Uli, I started creating issues in
> > Jira for our GSoC candidate tasks. I started with the svnpubsub task:
> >
> > https://issues.apache.org/bloodhound/ticket/478
> > https://issues.apache.org/jira/browse/COMDEV-84
> >
> > If anyone wants to help out, please do so. :) COMDEV-84 can serve as a
> > template for the rest of the submissions. Please make sure that we get
> > all the entries in Jira cross-referenced in our tracker, and the other
> > way around.
> >
> > (And here's a feature proposal for ticket relations: allow
> > cross-references to issues in other issue trackers.)
> >
>
> jftr ... if relationships are designed in terms of resources then
> resource neighborhoods proposal [2]_ might help to get things like
> this done (i.e. similar to Trac resources proposal [1]_ but with
> neighborhood ID added in resource_main and resource_dest)
>
> .. [1] TracRelations
> (http://trac.edgewall.org/wiki/TracDev/Proposals/TracRelations)
>
> .. [2] Apache™ Bloodhound resource neighborhoods proposal
> (
> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=33&old_version=31
> )
>
> --
> Regards,
>
> Olemis.
>
--
Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/>
@jdreimann <https://twitter.com/jdreimann>
*
*
*Join one of our free daily demo sessions on* *Scaling Subversion for the
Enterprise <http://www.wandisco.com/training/webinars>*
THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE
PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its
subsidiaries, ("WANdisco") does not waive any confidentiality or privilege.
If you are not the intended recipient, please notify us immediately and
destroy the message without disclosing its contents to anyone. Any
distribution, use or copying of this e-mail or the information it contains
by other than an intended recipient is unauthorized. The views and
opinions expressed in this e-mail message are the author's own and may not
reflect the views and opinions of WANdisco, unless the author is authorized
by WANdisco to express such views or opinions on its behalf. All email
sent to or from this address is subject to electronic storage and review by
WANdisco. Although WANdisco operates anti-virus programs, it does not
accept responsibility for any damage whatsoever caused by viruses being
passed.