From: David B. <da...@da...> - 2009-03-12 11:30:49
|
>> I would be more than happy to have the Wiki move someplace else---and maybe to something with a more modern interface. It would be one less thing for me to worry about and free up more time to focus on other things (like coding :-). However, the wiki spam problem is something that will have to be addressed one way or another on whatever system is used. Maybe we'll need user logins, captchas, or some other mechanism. Cheers, Dave > Looks good. Actually I've been pondering moving the main SWIG wiki to > SourceForge for a more up to date wiki and one that doesn't have the > web > link limitation. Something for the future. > > We need an application template for the students. My proposed template > is below. The goal is to encourage quality applications from students > who have the required knowledge and put in the effort up front to > research their project and communicate with us. Any suggested > modifications (needed before Friday afternoon)? Any prospective > students > reading this can use this as advanced information for your > application. > > > Name > > Abstract > * A short description of your proposed project > > Detailed Description > * Background and full description of the problem and what it is > going to > solve > * What are the main benefits for SWIG users/developers of your > project? > * What motivates you about doing the proposed project? > * Detailed design of how it will be implemented including the > areas/files that will need modifying > * Please include use cases so that we can see how a user will be > able to > use the new feature. The more of these the better as we'd expect a > test > driven development approach. These use cases should form the > backbone of > the regression tests and we'd like to know how these tests will fit in > with the current regression testing that SWIG has. > > Implementation timeline > * Detailed outline of milestones and when they will be achieved during > the course of the project > * State clearly periods that you expect that you will not be available > to work on the project, eg time needed for study, exams, holidays etc. > * How would you like to demonstrate and communicate regular progress? > > Future work > * Describe what could/will need doing once your project deliverables > have been finished. > > Relevant knowledge > * Describe what experience you have already had of SWIG. If you are > new, > we'd expect you to list the areas you understand and have > experimented with. > * Detail any bug fixes that you have submitted to SWIG. Students who > browse the current bugs and submit a good patch to fix one of them > will > be looked on most favourably. > * Describe what experience you have in the project specific area. > Include technologies that you are implementing such as C/C++, the > target > language, any courses you have been on or actual code completed. > * Which toolchains and platforms do you use? > * Please list here any recent interaction you have had with the SWIG > community (IRC, mailing lists etc). > > About Me > * Describe yourself, where you work/play/study and your relevant > interests > * Include any web links to pages that might exist about you > > Although a different template is required this year, a Model > application > from last year is available > http://www.dabeaz.com/cgi-bin/wiki.pl?GSoCPython3Proposal. > > William > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) > are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly > and > easily build your RIAs with Flex Builder, the Eclipse(TM)based > development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel |