You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Branko Čibej <br...@wandisco.com> on 2013/03/22 10:21:16 UTC
Ideas for Google Summer of Code
Hey,
On the topic of trying to get more people interested in Bloodhound, we
should get involved in GSoC. I've been a GSoC mentor in the past (for
Subversion) and can help.
I'm sure there are any number of tasks that can be worked on without
deep knowledge of Trac internals and would take a 6-8 week project to
complete. Please take time today to list them here:
https://issues.apache.org/jira/issues/?filter=12323652
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
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.
Re: Ideas for Google Summer of Code
Posted by Olemis Lang <ol...@gmail.com>.
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 Peter Koželj <pe...@digiverse.si>.
Thx, fixed.
On 27 March 2013 08:24, Branko Čibej <br...@wandisco.com> wrote:
> On 27.03.2013 08:18, Peter Koželj wrote:
> > This is now also in jira:
> https://issues.apache.org/jira/browse/COMDEV-96
>
> Nice, but the label shoudl be "gsoc2013", not "gsoc". You'll have to
> change that, as I can't modify the ticket.
>
> -- Brane
>
> >
> > On 27 March 2013 07:57, Peter Koželj <pe...@digiverse.si> wrote:
> >
> >> Agreed, I have updated the ticket.
> >>
> >>
> >> On 27 March 2013 07:45, Branko Čibej <br...@wandisco.com> wrote:
> >>
> >>> On 27.03.2013 07:40, Peter Koželj wrote:
> >>>> I was thinking about that but each one alone does not warrant 2 months
> >>>> coding effort.
> >>> I meant split into two goals within one GSoC project.
> >>>
> >>> The thing is, I suspect that the WYSIWYG workflow editor might be just
> a
> >>> bit too much for two months. So, it needs some infrastructure -- I
> >>> expect the internal API will be table-based in any case -- and exposing
> >>> that in the UI should be close to trivial, so that the project would
> >>> have something to show relatively early.
> >>>
> >>> -- Brane
> >>>
> >>>> On 27 March 2013 07:30, Branko Čibej <br...@wandisco.com> wrote:
> >>>>
> >>>>> On 27.03.2013 07:19, Peter Koželj wrote:
> >>>>>> I hope I am not to late, I have added
> >>>>>> https://issues.apache.org/bloodhound/ticket/490 to the list.
> >>>>>> What do you think?
> >>>>> Not bad, but I'd split it in two; the first step (required) would be
> a
> >>>>> table-based workflow editor, modelled after Redmine's, for example.
> The
> >>>>> second step (optional) would be the WSYWIG thing.
> >>>>>
> >>>>> -- Brane
> >>>>>
> >>>>> --
> >>>>> Branko Čibej
> >>>>> Director of Subversion | WANdisco | www.wandisco.com
> >>>>>
> >>>>>
> >>>
> >>> --
> >>> Branko Čibej
> >>> Director of Subversion | WANdisco | www.wandisco.com
> >>>
> >>>
>
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
>
Re: Ideas for Google Summer of Code
Posted by Branko Čibej <br...@wandisco.com>.
On 27.03.2013 08:18, Peter Koželj wrote:
> This is now also in jira: https://issues.apache.org/jira/browse/COMDEV-96
Nice, but the label shoudl be "gsoc2013", not "gsoc". You'll have to
change that, as I can't modify the ticket.
-- Brane
>
> On 27 March 2013 07:57, Peter Koželj <pe...@digiverse.si> wrote:
>
>> Agreed, I have updated the ticket.
>>
>>
>> On 27 March 2013 07:45, Branko Čibej <br...@wandisco.com> wrote:
>>
>>> On 27.03.2013 07:40, Peter Koželj wrote:
>>>> I was thinking about that but each one alone does not warrant 2 months
>>>> coding effort.
>>> I meant split into two goals within one GSoC project.
>>>
>>> The thing is, I suspect that the WYSIWYG workflow editor might be just a
>>> bit too much for two months. So, it needs some infrastructure -- I
>>> expect the internal API will be table-based in any case -- and exposing
>>> that in the UI should be close to trivial, so that the project would
>>> have something to show relatively early.
>>>
>>> -- Brane
>>>
>>>> On 27 March 2013 07:30, Branko Čibej <br...@wandisco.com> wrote:
>>>>
>>>>> On 27.03.2013 07:19, Peter Koželj wrote:
>>>>>> I hope I am not to late, I have added
>>>>>> https://issues.apache.org/bloodhound/ticket/490 to the list.
>>>>>> What do you think?
>>>>> Not bad, but I'd split it in two; the first step (required) would be a
>>>>> table-based workflow editor, modelled after Redmine's, for example. The
>>>>> second step (optional) would be the WSYWIG thing.
>>>>>
>>>>> -- Brane
>>>>>
>>>>> --
>>>>> Branko Čibej
>>>>> Director of Subversion | WANdisco | www.wandisco.com
>>>>>
>>>>>
>>>
>>> --
>>> Branko Čibej
>>> Director of Subversion | WANdisco | www.wandisco.com
>>>
>>>
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Ideas for Google Summer of Code
Posted by Peter Koželj <pe...@digiverse.si>.
This is now also in jira: https://issues.apache.org/jira/browse/COMDEV-96
On 27 March 2013 07:57, Peter Koželj <pe...@digiverse.si> wrote:
> Agreed, I have updated the ticket.
>
>
> On 27 March 2013 07:45, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 27.03.2013 07:40, Peter Koželj wrote:
>> > I was thinking about that but each one alone does not warrant 2 months
>> > coding effort.
>>
>> I meant split into two goals within one GSoC project.
>>
>> The thing is, I suspect that the WYSIWYG workflow editor might be just a
>> bit too much for two months. So, it needs some infrastructure -- I
>> expect the internal API will be table-based in any case -- and exposing
>> that in the UI should be close to trivial, so that the project would
>> have something to show relatively early.
>>
>> -- Brane
>>
>> > On 27 March 2013 07:30, Branko Čibej <br...@wandisco.com> wrote:
>> >
>> >> On 27.03.2013 07:19, Peter Koželj wrote:
>> >>> I hope I am not to late, I have added
>> >>> https://issues.apache.org/bloodhound/ticket/490 to the list.
>> >>> What do you think?
>> >> Not bad, but I'd split it in two; the first step (required) would be a
>> >> table-based workflow editor, modelled after Redmine's, for example. The
>> >> second step (optional) would be the WSYWIG thing.
>> >>
>> >> -- Brane
>> >>
>> >> --
>> >> Branko Čibej
>> >> Director of Subversion | WANdisco | www.wandisco.com
>> >>
>> >>
>>
>>
>> --
>> Branko Čibej
>> Director of Subversion | WANdisco | www.wandisco.com
>>
>>
>
Re: Ideas for Google Summer of Code
Posted by Peter Koželj <pe...@digiverse.si>.
Agreed, I have updated the ticket.
On 27 March 2013 07:45, Branko Čibej <br...@wandisco.com> wrote:
> On 27.03.2013 07:40, Peter Koželj wrote:
> > I was thinking about that but each one alone does not warrant 2 months
> > coding effort.
>
> I meant split into two goals within one GSoC project.
>
> The thing is, I suspect that the WYSIWYG workflow editor might be just a
> bit too much for two months. So, it needs some infrastructure -- I
> expect the internal API will be table-based in any case -- and exposing
> that in the UI should be close to trivial, so that the project would
> have something to show relatively early.
>
> -- Brane
>
> > On 27 March 2013 07:30, Branko Čibej <br...@wandisco.com> wrote:
> >
> >> On 27.03.2013 07:19, Peter Koželj wrote:
> >>> I hope I am not to late, I have added
> >>> https://issues.apache.org/bloodhound/ticket/490 to the list.
> >>> What do you think?
> >> Not bad, but I'd split it in two; the first step (required) would be a
> >> table-based workflow editor, modelled after Redmine's, for example. The
> >> second step (optional) would be the WSYWIG thing.
> >>
> >> -- Brane
> >>
> >> --
> >> Branko Čibej
> >> Director of Subversion | WANdisco | www.wandisco.com
> >>
> >>
>
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
>
Re: Ideas for Google Summer of Code
Posted by Branko Čibej <br...@wandisco.com>.
On 27.03.2013 07:40, Peter Koželj wrote:
> I was thinking about that but each one alone does not warrant 2 months
> coding effort.
I meant split into two goals within one GSoC project.
The thing is, I suspect that the WYSIWYG workflow editor might be just a
bit too much for two months. So, it needs some infrastructure -- I
expect the internal API will be table-based in any case -- and exposing
that in the UI should be close to trivial, so that the project would
have something to show relatively early.
-- Brane
> On 27 March 2013 07:30, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 27.03.2013 07:19, Peter Koželj wrote:
>>> I hope I am not to late, I have added
>>> https://issues.apache.org/bloodhound/ticket/490 to the list.
>>> What do you think?
>> Not bad, but I'd split it in two; the first step (required) would be a
>> table-based workflow editor, modelled after Redmine's, for example. The
>> second step (optional) would be the WSYWIG thing.
>>
>> -- Brane
>>
>> --
>> Branko Čibej
>> Director of Subversion | WANdisco | www.wandisco.com
>>
>>
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Ideas for Google Summer of Code
Posted by Peter Koželj <pe...@digiverse.si>.
I was thinking about that but each one alone does not warrant 2 months
coding effort.
Peter
On 27 March 2013 07:30, Branko Čibej <br...@wandisco.com> wrote:
> On 27.03.2013 07:19, Peter Koželj wrote:
> > I hope I am not to late, I have added
> > https://issues.apache.org/bloodhound/ticket/490 to the list.
> > What do you think?
>
> Not bad, but I'd split it in two; the first step (required) would be a
> table-based workflow editor, modelled after Redmine's, for example. The
> second step (optional) would be the WSYWIG thing.
>
> -- Brane
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
>
Re: Ideas for Google Summer of Code
Posted by Branko Čibej <br...@wandisco.com>.
On 27.03.2013 07:19, Peter Koželj wrote:
> I hope I am not to late, I have added
> https://issues.apache.org/bloodhound/ticket/490 to the list.
> What do you think?
Not bad, but I'd split it in two; the first step (required) would be a
table-based workflow editor, modelled after Redmine's, for example. The
second step (optional) would be the WSYWIG thing.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Ideas for Google Summer of Code
Posted by Peter Koželj <pe...@digiverse.si>.
I hope I am not to late, I have added
https://issues.apache.org/bloodhound/ticket/490 to the list.
What do you think?
Peter
On 25 March 2013 12:24, Joachim Dreimann <jo...@wandisco.com>wrote:
> On 23 March 2013 14:41, Branko Čibej <br...@wandisco.com> wrote:
>
> > On 23.03.2013 09:19, Branko Čibej 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.
> >
> > These issues can now be found in Jira here:
> >
> > https://issues.apache.org/jira/issues/?filter=12323779
>
>
> The requested filter doesn't exist or is private.
>
> That's the error message I receive. According to Atlassian you need special
> permissions to share publicly: https://jira.atlassian.com/browse/JRA-2054
>
> This link should work for everyone:
>
> https://issues.apache.org/jira/issues/?filter=12323652&jql=labels%20in%20(%22gsoc2013%2C%22%2C%20bloodhound)
>
> - Joe
>
>
> >
> >
> > Note that they all have the labels "gsoc2013" and "bloodhound", which
> > the filter uses.
>
>
> > -- Brane
> >
> > --
> > Branko Čibej
> > Director of Subversion | WANdisco | www.wandisco.com
> >
>
Re: Ideas for Google Summer of Code
Posted by Branko Čibej <br...@wandisco.com>.
On 25.03.2013 12:24, Joachim Dreimann wrote:
> On 23 March 2013 14:41, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 23.03.2013 09:19, Branko Čibej 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.
>> These issues can now be found in Jira here:
>>
>> https://issues.apache.org/jira/issues/?filter=12323779
>
> The requested filter doesn't exist or is private.
>
> That's the error message I receive. According to Atlassian you need special
> permissions to share publicly: https://jira.atlassian.com/browse/JRA-2054
>
> This link should work for everyone:
> https://issues.apache.org/jira/issues/?filter=12323652&jql=labels%20in%20(%22gsoc2013%2C%22%2C%20bloodhound)
I made the query a bit smarter, because I merged COMDEV-84 into
COMDEV-86 and closed the former:
https://issues.apache.org/jira/issues/?filter=12323652&jql=project%20%3D%20COMDEV%20AND%20resolution%20%3D%20Unresolved%20AND%20labels%20in%20(%22gsoc2013%2C%22%2C%20bloodhound)
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Ideas for Google Summer of Code
Posted by Joachim Dreimann <jo...@wandisco.com>.
On 23 March 2013 14:41, Branko Čibej <br...@wandisco.com> wrote:
> On 23.03.2013 09:19, Branko Čibej 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.
>
> These issues can now be found in Jira here:
>
> https://issues.apache.org/jira/issues/?filter=12323779
The requested filter doesn't exist or is private.
That's the error message I receive. According to Atlassian you need special
permissions to share publicly: https://jira.atlassian.com/browse/JRA-2054
This link should work for everyone:
https://issues.apache.org/jira/issues/?filter=12323652&jql=labels%20in%20(%22gsoc2013%2C%22%2C%20bloodhound)
- Joe
>
>
> Note that they all have the labels "gsoc2013" and "bloodhound", which
> the filter uses.
> -- Brane
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
Re: Ideas for Google Summer of Code
Posted by Branko Čibej <br...@wandisco.com>.
On 23.03.2013 09:19, Branko Čibej 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.
These issues can now be found in Jira here:
https://issues.apache.org/jira/issues/?filter=12323779
Note that they all have the labels "gsoc2013" and "bloodhound", which
the filter uses.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Ideas for Google Summer of Code
Posted by Branko Čibej <br...@wandisco.com>.
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.)
-- Brane
On 22.03.2013 19:41, Joachim Dreimann wrote:
> After a brief discussion on IRC Brane suggested to create a tag for our
> suggestions on our issue tracker, which I have done now:
> https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc
>
> Please raise suggestions using that "gsoc" tag.
> I will add several more today and post a summary on Monday of all
> suggestions for awareness. Comments are welcome too, as always.
>
> [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2013
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] http://s.apache.org/gsoc2013ideas
> [4] http://community.apache.org/gsoc.html
> [5] http://s.apache.org/gsoclabels
>
>
>
> On 22 March 2013 09:21, Branko Čibej <br...@wandisco.com> wrote:
>
>> Hey,
>>
>> On the topic of trying to get more people interested in Bloodhound, we
>> should get involved in GSoC. I've been a GSoC mentor in the past (for
>> Subversion) and can help.
>>
>> I'm sure there are any number of tasks that can be worked on without
>> deep knowledge of Trac internals and would take a 6-8 week project to
>> complete. Please take time today to list them here:
>>
>> https://issues.apache.org/jira/issues/?filter=12323652
>>
>> -- Brane
>>
>>
>> --
>> Branko Čibej
>> Director of Subversion | WANdisco | www.wandisco.com
>>
>>
>
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Ideas for Google Summer of Code
Posted by Olemis Lang <ol...@gmail.com>.
On 3/22/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> After a brief discussion on IRC Brane suggested to create a tag for our
> suggestions on our issue tracker, which I have done now:
> https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc
>
> Please raise suggestions using that "gsoc" tag.
I have tagged some but I'd like to hear some opinions on whether those
are good targets for GSoC .
[...]
--
Regards,
Olemis.
Re: Ideas for Google Summer of Code
Posted by Joachim Dreimann <jo...@wandisco.com>.
After a brief discussion on IRC Brane suggested to create a tag for our
suggestions on our issue tracker, which I have done now:
https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc
Please raise suggestions using that "gsoc" tag.
I will add several more today and post a summary on Monday of all
suggestions for awareness. Comments are welcome too, as always.
[1] http://www.google-melange.com/gsoc/homepage/google/gsoc2013
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2013ideas
[4] http://community.apache.org/gsoc.html
[5] http://s.apache.org/gsoclabels
On 22 March 2013 09:21, Branko Čibej <br...@wandisco.com> wrote:
> Hey,
>
> On the topic of trying to get more people interested in Bloodhound, we
> should get involved in GSoC. I've been a GSoC mentor in the past (for
> Subversion) and can help.
>
> I'm sure there are any number of tasks that can be worked on without
> deep knowledge of Trac internals and would take a 6-8 week project to
> complete. Please take time today to list them here:
>
> https://issues.apache.org/jira/issues/?filter=12323652
>
> -- Brane
>
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
>
--
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.