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. [email protected] twitter @jdreimann <https://twitter.com/jdreimann>
