You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Joachim Dreimann <jo...@wandisco.com> on 2013/06/13 15:52:17 UTC
GSoC Students: BEPs for your projects
I'd like to suggest that Antonia, Hua and Pranay (our Google Summer of Code
students this year) use BEPs to capture their proposals and track their
progress.
"BEP stands for Bloodhound Enhancement Proposal. A BEP is a design document
providing information to the Bloodhound community, or describing a new
feature for Bloodhound or its processes or environment. The BEP should
provide a concise technical specification of the feature and a rationale
for the feature."
https://issues.apache.org/bloodhound/wiki/Proposals <- Find out more here
I've already set up three placeholders:
Antonia: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007
Hua: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008
Pranay: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0009
You can find some inspiration in the existing proposals:
https://issues.apache.org/bloodhound/wiki/Proposals/Index
It'd be a good start just to copy and past your GSoC applications into
these wiki pages, keeping with the structure of the BEP.
Just reply if you've got any questions, or if others would like to comment
on this approach.
Cheers,
Joe
--
Joachim Dreimann | *User Experience Manager*
WANdisco // *Non-Stop Data*
e. joachim.dreimann@wandisco.com
twitter @jdreimann <https://twitter.com/jdreimann>
Re: GSoC Students: BEPs for your projects
Posted by Olemis Lang <ol...@gmail.com>.
On 6/13/13, Joe Dreimann <jo...@wandisco.com> wrote:
> Looks about right to me, what do others think?
>
> It would be great if others could speak up about what they think about the
> project and approach.
>
on the right track ...
--
Regards,
Olemis.
Re: GSoC Students: BEPs for your projects
Posted by Joe Dreimann <jo...@wandisco.com>.
Looks about right to me, what do others think?
It would be great if others could speak up about what they think about the project and approach.
________________________
@jdreimann - Twitter
Sent from my phone
On 13 Jun 2013, at 18:22, Antonia Horincar <an...@gmail.com> wrote:
> Hi Joe,
>
> I've just filled in my BEP, I hope I displayed everything under the
> right sections:
> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007
>
> Thanks,
> Antonia
>
> On Thu, Jun 13, 2013 at 4:52 PM, Joachim Dreimann
> <jo...@wandisco.com> wrote:
>> I'd like to suggest that Antonia, Hua and Pranay (our Google Summer of Code
>> students this year) use BEPs to capture their proposals and track their
>> progress.
>>
>> "BEP stands for Bloodhound Enhancement Proposal. A BEP is a design document
>> providing information to the Bloodhound community, or describing a new
>> feature for Bloodhound or its processes or environment. The BEP should
>> provide a concise technical specification of the feature and a rationale
>> for the feature."
>> https://issues.apache.org/bloodhound/wiki/Proposals <- Find out more here
>>
>> I've already set up three placeholders:
>> Antonia: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007
>> Hua: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008
>> Pranay: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0009
>>
>> You can find some inspiration in the existing proposals:
>> https://issues.apache.org/bloodhound/wiki/Proposals/Index
>>
>> It'd be a good start just to copy and past your GSoC applications into
>> these wiki pages, keeping with the structure of the BEP.
>>
>> Just reply if you've got any questions, or if others would like to comment
>> on this approach.
>>
>> Cheers,
>> Joe
>>
>> --
>> Joachim Dreimann | *User Experience Manager*
>>
>> WANdisco // *Non-Stop Data*
>>
>> e. joachim.dreimann@wandisco.com
>> twitter @jdreimann <https://twitter.com/jdreimann>
Re: GSoC Students: BEPs for your projects
Posted by Antonia Horincar <an...@gmail.com>.
Hi Joe,
I've just filled in my BEP, I hope I displayed everything under the
right sections:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007
Thanks,
Antonia
On Thu, Jun 13, 2013 at 4:52 PM, Joachim Dreimann
<jo...@wandisco.com> wrote:
> I'd like to suggest that Antonia, Hua and Pranay (our Google Summer of Code
> students this year) use BEPs to capture their proposals and track their
> progress.
>
> "BEP stands for Bloodhound Enhancement Proposal. A BEP is a design document
> providing information to the Bloodhound community, or describing a new
> feature for Bloodhound or its processes or environment. The BEP should
> provide a concise technical specification of the feature and a rationale
> for the feature."
> https://issues.apache.org/bloodhound/wiki/Proposals <- Find out more here
>
> I've already set up three placeholders:
> Antonia: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007
> Hua: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008
> Pranay: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0009
>
> You can find some inspiration in the existing proposals:
> https://issues.apache.org/bloodhound/wiki/Proposals/Index
>
> It'd be a good start just to copy and past your GSoC applications into
> these wiki pages, keeping with the structure of the BEP.
>
> Just reply if you've got any questions, or if others would like to comment
> on this approach.
>
> Cheers,
> Joe
>
> --
> Joachim Dreimann | *User Experience Manager*
>
> WANdisco // *Non-Stop Data*
>
> e. joachim.dreimann@wandisco.com
> twitter @jdreimann <https://twitter.com/jdreimann>