You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Menaka Madushanka <me...@gmail.com> on 2015/03/13 21:10:40 UTC
GSOC project proposal
Hi Stian,
I would like to know the structure of the project proposal. Because, from
organization to organization the proposal structure changes.
I'd be very grateful if you give me some guidelines.
Thank you very much.
Menaka.
--
Menaka Madushanka Jayawardena
Faculty of Engineering, <http://www.pdn.ac.lk/eng>
University of Peradeniyaya.
LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
Re: GSOC project proposal
Posted by Menaka Madushanka <me...@gmail.com>.
Yeah....
That's better I think. But sometimes the structure could vary according to
the organization.
Cheers.
On 16 March 2015 at 02:27, Денис Карякин <sa...@gmail.com> wrote:
> I found this three examples from mozilla org:
> https://wiki.mozilla.org/SummerOfCode/SampleApplications/1
> https://wiki.mozilla.org/SummerOfCode/SampleApplications/2
> https://wiki.mozilla.org/SummerOfCode/SampleApplications/3
>
> I think, it's a good point to start write up our own proposal
>
> 2015-03-14 0:03 GMT+03:00 Larry Akah <la...@gmail.com>:
>
> > yeah,. i also need some sample structure used for GSOC proposals here.
> >
> > 2015-03-13 15:10 GMT-05:00 Menaka Madushanka <me...@gmail.com>:
> >
> > > Hi Stian,
> > >
> > > I would like to know the structure of the project proposal. Because,
> from
> > > organization to organization the proposal structure changes.
> > >
> > > I'd be very grateful if you give me some guidelines.
> > >
> > > Thank you very much.
> > > Menaka.
> > >
> > >
> > > --
> > > Menaka Madushanka Jayawardena
> > > Faculty of Engineering, <http://www.pdn.ac.lk/eng>
> > > University of Peradeniyaya.
> > > LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
> > >
> >
> >
> >
> > --
> > *Akah Larry N.H*
> >
> > *Lead Software Engineer @ GiftedMom*
> > *Software Engineer @ IceTech Inc*
> > *Web And Mobile Software Developer*
> >
>
--
Menaka Madushanka Jayawardena
Faculty of Engineering, <http://www.pdn.ac.lk/eng>
University of Peradeniyaya.
LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
Re: GSOC project proposal
Posted by Денис Карякин <sa...@gmail.com>.
I found this three examples from mozilla org:
https://wiki.mozilla.org/SummerOfCode/SampleApplications/1
https://wiki.mozilla.org/SummerOfCode/SampleApplications/2
https://wiki.mozilla.org/SummerOfCode/SampleApplications/3
I think, it's a good point to start write up our own proposal
2015-03-14 0:03 GMT+03:00 Larry Akah <la...@gmail.com>:
> yeah,. i also need some sample structure used for GSOC proposals here.
>
> 2015-03-13 15:10 GMT-05:00 Menaka Madushanka <me...@gmail.com>:
>
> > Hi Stian,
> >
> > I would like to know the structure of the project proposal. Because, from
> > organization to organization the proposal structure changes.
> >
> > I'd be very grateful if you give me some guidelines.
> >
> > Thank you very much.
> > Menaka.
> >
> >
> > --
> > Menaka Madushanka Jayawardena
> > Faculty of Engineering, <http://www.pdn.ac.lk/eng>
> > University of Peradeniyaya.
> > LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
> >
>
>
>
> --
> *Akah Larry N.H*
>
> *Lead Software Engineer @ GiftedMom*
> *Software Engineer @ IceTech Inc*
> *Web And Mobile Software Developer*
>
Re: GSOC project proposal
Posted by Larry Akah <la...@gmail.com>.
yeah,. i also need some sample structure used for GSOC proposals here.
2015-03-13 15:10 GMT-05:00 Menaka Madushanka <me...@gmail.com>:
> Hi Stian,
>
> I would like to know the structure of the project proposal. Because, from
> organization to organization the proposal structure changes.
>
> I'd be very grateful if you give me some guidelines.
>
> Thank you very much.
> Menaka.
>
>
> --
> Menaka Madushanka Jayawardena
> Faculty of Engineering, <http://www.pdn.ac.lk/eng>
> University of Peradeniyaya.
> LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
>
--
*Akah Larry N.H*
*Lead Software Engineer @ GiftedMom*
*Software Engineer @ IceTech Inc*
*Web And Mobile Software Developer*
Re: GSOC project proposal
Posted by Menaka Madushanka <me...@gmail.com>.
Thank you very much....!!!
:-)
On 17 March 2015 at 00:04, Stian Soiland-Reyes <st...@apache.org> wrote:
> http://community.apache.org/gsoc.html#applying-for-gsoc
>
> Lists the points to cover, which you could easily turn onto a template:
>
> # About me
>
> What relevant experience have you got, including university, work and hobby
> activities?
>
> # Background
>
> What exists already? What is the identified need? What can you reuse, what
> needs to he replaced?
>
> # Design / description of work
>
> Brief list of things you will do / create, in some rough chronological
> order.
>
> E.g. "Investigate Android REST client libraries" or "Develop JavaScript
> functions for browsing files"
>
> Show which bits are essential, and which are optional.
>
> Also highlight what is new, what is modifications, and how your work fits
> into the existing architecture.
>
> # Results for the Apache community
>
> Benefit of your work to Apache Taverna users and developers. What will be
> the legacy of your work after you finish?
>
> # Deliverables
>
> Including milestones, components, documentation, tests
>
> # Scheduling
>
> Not too detailed, but some milestones and checkpoints. Rough estimates per
> work item (weeks/days). Remember to leave time for slack and bugfixing!
>
> ## other commitments
>
> Exams, part time work, holidays, lectures.
>
> # Community engagement
>
> In particular with Apache Taverna.
>
> This should show a rough understanding of working with open source
> communities.
>
> Both before start (e.g. this email) and during the project. This includes
> mailing lists, wikis, issue trackers, test systems.
>
> Any planned user testing, prototypes, code review.
> On 16 Mar 2015 15:38, "Stian Soiland-Reyes" <st...@apache.org> wrote:
>
> > I don't think Apache has set any fixed structure for the proposal
> > text, but I shall check.
> >
> > On 13 March 2015 at 20:10, Menaka Madushanka <me...@gmail.com>
> > wrote:
> > > Hi Stian,
> > >
> > > I would like to know the structure of the project proposal. Because,
> from
> > > organization to organization the proposal structure changes.
> > >
> > > I'd be very grateful if you give me some guidelines.
> > >
> > > Thank you very much.
> > > Menaka.
> > >
> > >
> > > --
> > > Menaka Madushanka Jayawardena
> > > Faculty of Engineering,
> > > University of Peradeniyaya.
> > > LinkedIn
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > Apache Taverna (incubating), Apache Commons RDF (incubating)
> > http://orcid.org/0000-0001-9842-9718
> >
>
--
Menaka Madushanka Jayawardena
Faculty of Engineering, <http://www.pdn.ac.lk/eng>
University of Peradeniyaya.
LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
Re: GSOC project proposal
Posted by Stian Soiland-Reyes <st...@apache.org>.
http://community.apache.org/gsoc.html#applying-for-gsoc
Lists the points to cover, which you could easily turn onto a template:
# About me
What relevant experience have you got, including university, work and hobby
activities?
# Background
What exists already? What is the identified need? What can you reuse, what
needs to he replaced?
# Design / description of work
Brief list of things you will do / create, in some rough chronological
order.
E.g. "Investigate Android REST client libraries" or "Develop JavaScript
functions for browsing files"
Show which bits are essential, and which are optional.
Also highlight what is new, what is modifications, and how your work fits
into the existing architecture.
# Results for the Apache community
Benefit of your work to Apache Taverna users and developers. What will be
the legacy of your work after you finish?
# Deliverables
Including milestones, components, documentation, tests
# Scheduling
Not too detailed, but some milestones and checkpoints. Rough estimates per
work item (weeks/days). Remember to leave time for slack and bugfixing!
## other commitments
Exams, part time work, holidays, lectures.
# Community engagement
In particular with Apache Taverna.
This should show a rough understanding of working with open source
communities.
Both before start (e.g. this email) and during the project. This includes
mailing lists, wikis, issue trackers, test systems.
Any planned user testing, prototypes, code review.
On 16 Mar 2015 15:38, "Stian Soiland-Reyes" <st...@apache.org> wrote:
> I don't think Apache has set any fixed structure for the proposal
> text, but I shall check.
>
> On 13 March 2015 at 20:10, Menaka Madushanka <me...@gmail.com>
> wrote:
> > Hi Stian,
> >
> > I would like to know the structure of the project proposal. Because, from
> > organization to organization the proposal structure changes.
> >
> > I'd be very grateful if you give me some guidelines.
> >
> > Thank you very much.
> > Menaka.
> >
> >
> > --
> > Menaka Madushanka Jayawardena
> > Faculty of Engineering,
> > University of Peradeniyaya.
> > LinkedIn
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>
Re: GSOC project proposal
Posted by Stian Soiland-Reyes <st...@apache.org>.
I don't think Apache has set any fixed structure for the proposal
text, but I shall check.
On 13 March 2015 at 20:10, Menaka Madushanka <me...@gmail.com> wrote:
> Hi Stian,
>
> I would like to know the structure of the project proposal. Because, from
> organization to organization the proposal structure changes.
>
> I'd be very grateful if you give me some guidelines.
>
> Thank you very much.
> Menaka.
>
>
> --
> Menaka Madushanka Jayawardena
> Faculty of Engineering,
> University of Peradeniyaya.
> LinkedIn
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718