-
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, We now know we will get 5 slots from Google. This means as we currently stand the following projects will be accepted: Component Registry Introspector and Zope 2 / Plone integration. Non-AT membrane, a new plone authentication scheme and ldap Event-Based Incoming and Outgoing E-mail for Plone Faceted search and navigation core and interface Buildout Builder - An automated buildout configuration system. These will not: Plone Batch Editing Develop Search System for East Asian Languages. Leveraging the Plone external indexing and searching story Portlet Infrastructure Improvements Integrate new templating engine into Plone and others with no mentors assigned. Any opinions on if this should change should be voiced immediately. Personally, while I'd like to have seen external indexing and portlets I can't think of any of the above I'd want to move. Does anyone else? Matt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFIB929ZnKd+ctxHMoRAqGVAJ9upW+HgMkqGivQvZZ8VgflWjkuQACfVWKE axezDgzEJqfRa0UDIJZ4Q1o= =M1vD -----END PGP SIGNATURE-----
- Thread Outline:
-
Matthew Wilkes <matthew@...> writes: > We now know we will get 5 slots from Google. This means as we > currently stand the following projects will be accepted: > > Component Registry Introspector and Zope 2 / Plone integration. > Non-AT membrane, a new plone authentication scheme and ldap > Event-Based Incoming and Outgoing E-mail for Plone > Faceted search and navigation core and interface > Buildout Builder - An automated buildout configuration system. > > These will not: > > Plone Batch Editing > Develop Search System for East Asian Languages. > Leveraging the Plone external indexing and searching story > Portlet Infrastructure Improvements > Integrate new templating engine into Plone > > and others with no mentors assigned. > > Any opinions on if this should change should be voiced immediately. > Personally, while I'd like to have seen external indexing and portlets > I can't think of any of the above I'd want to move. Does anyone else? I'd be disappointed if "Develop Search System for East Asian Languages" wouldn't go in. Imagine you install Plone and the search is broken. Which is the case today if you're speaking Chinese, Japanese or Korean. According to Wikipedia, Mandarin Chinese has more speakers than any other language. Therefore I'd say that this is more important than *any* of the other applications, including the one I'm assigned for as a mentor. Daniel
-
Thanks Daniel. I am glad that there is someone who understands the importance of search that works on East Asian language（Chinese, Japanese or Korean）. I think search is one of the basic function that Plone must guarantee to market before any funcy functions. I hope other personal in this mailing list would reconsider the fact that GSoC is the best chance to implement that CJK search function to plone. If I have not introduced enough, May I introduce myself a bit. I am an author of Plone witch is publish in Japan. <http://www.amazon.co.jp/%E3%82%AA%E3%83%BC%E3%83%97%E3%83%B3%E3%82%BD%E3%83%BC%E3%82%B9%E5%BE%B9%E5%BA%95%E6%B4%BB%E7%94%A8-Plone%E3%81%AB%E3%82%88%E3%82%8B%E7%B0%A1%E5%8D%98Web%E3%82%B3%E3%83%B3%E3%83%86%E3%83%B3%E3%83%84%E7%AE%A1%E7%90%86-%E5%AF%BA%E7%94%B0-%E5%AD%A6/dp/4798012696/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1208492538> Aslo, constaracted many major plone site in Japan including SPing-8<http://www.spring8.or.jp/en/>. Thanks. Daniel Nouri : > Matthew Wilkes <matthew@...> writes: > >> We now know we will get 5 slots from Google. This means as we >> currently stand the following projects will be accepted: >> >> Component Registry Introspector and Zope 2 / Plone integration. >> Non-AT membrane, a new plone authentication scheme and ldap >> Event-Based Incoming and Outgoing E-mail for Plone >> Faceted search and navigation core and interface >> Buildout Builder - An automated buildout configuration system. >> >> These will not: >> >> Plone Batch Editing >> Develop Search System for East Asian Languages. >> Leveraging the Plone external indexing and searching story >> Portlet Infrastructure Improvements >> Integrate new templating engine into Plone >> >> and others with no mentors assigned. >> >> Any opinions on if this should change should be voiced immediately. >> Personally, while I'd like to have seen external indexing and portlets >> I can't think of any of the above I'd want to move. Does anyone else? > > I'd be disappointed if "Develop Search System for East Asian Languages" > wouldn't go in. > > Imagine you install Plone and the search is broken. Which is the case > today if you're speaking Chinese, Japanese or Korean. According to > Wikipedia, Mandarin Chinese has more speakers than any other language. > Therefore I'd say that this is more important than *any* of the other > applications, including the one I'm assigned for as a mentor. > > > Daniel > > > -- > Archive: http://www.openplans.org/projects/plone-summer-of-code-2008/lists/plone-soc-2008-mentors/archive/2008/04/1208477770965 > To unsubscribe send an email with subject unsubscribe to plone-soc-mentors@.... Please contact plone-soc-mentors-manager@... for questions. > >
-
-
On Fri, Apr 18, 2008 at 1:31 AM, Matthew Wilkes <matthew@...> wrote: > Any opinions on if this should change should be voiced immediately. > Personally, while I'd like to have seen external indexing and portlets I > can't think of any of the above I'd want to move. Does anyone else? Yes. I think the better search for east-asian languages are important, but haven't voted, as I couldn't see that anyone was better than the other. I'm now going to vote for the top one. Which means it will tie for 3-6 place with Faceted search and buildout builder. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
-
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Heisei 0020-04-18, at 073704BST, Lennart Regebro wrote: > Which means it will tie > for 3-6 place with Faceted search and buildout builder. Ok, well we need to pick the one that loses out then. I agree, east- asian support needs to be done, should have mentioned that in the first mail. Oops. My preferences out of the current top 6: non-at membrane buildout builder compontent registry east asian faceted search event based email i.e. I'd think about swopping event based email for east asian support, especially as singing and dancing now exists. Matt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFICFW5ZnKd+ctxHMoRAlqNAKCczTk86FURfzW73XiaQ+3lueePqACfeejy XNogXYHjj70/xE57bbVK+Hk= =HFMR -----END PGP SIGNATURE-----
-
Matthew Wilkes wrote: > [..] > Ok, well we need to pick the one that loses out then. I agree, > east-asian support needs to be done, should have mentioned that in the > first mail. Oops. > I just increased my scoring for this from +1 to +2 so it advanced a bit more still. > My preferences out of the current top 6: > non-at membrane > buildout builder > compontent registry > east asian > faceted search > event based email > > i.e. I'd think about swopping event based email for east asian > support, especially as singing and dancing now exists. > Not sure I follow here. The existence of singing and dancing makes the 'Event based mail handling' more feasible I'd say. I see this rather as a decision between contributions which make Plone more accessible (like the buildout builder) versus more feature rich (incoming mail handling; faceted search) As a (somewhat experienced ;-) ) Plone user myself, I'd prefer the new features but as a community member I should have a different preference I guess. (and the fact that I offer to mentor the buildout builder project makes me somewhat biased of course) Raphael > Matt
-
I think in the event, given that we have more "desirable" proposals than we have slots, we should make a judgement based on the quality of the student and his/her proposal, rather than our subjective idea of what we think is most useful. In the past, at least, it's been fairly clear which students are more likely to deliver. To me, the ideal candidate is one that is currently a peripheral community member who is at least known on the mailing lists and/or has some proven capability, who has submitted a well-written proposal that looks realistic and which he/she seems passionate about. It's hard to make choices, but this is a "nice" problem to have. :) Martin On 18/04/2008, Raphael Ritz <raphael.ritz@...> wrote: > Matthew Wilkes wrote: > > > [..] > > Ok, well we need to pick the one that loses out then. I agree, east-asian > support needs to be done, should have mentioned that in the first mail. > Oops. > > > > > > I just increased my scoring for this from +1 to +2 so > it advanced a bit more still. > > > > My preferences out of the current top 6: > > non-at membrane > > buildout builder > > compontent registry > > east asian > > faceted search > > event based email > > > > i.e. I'd think about swopping event based email for east asian support, > especially as singing and dancing now exists. > > > > > > Not sure I follow here. The existence of singing and dancing makes the > 'Event based mail handling' more feasible I'd say. > I see this rather as a decision between contributions which > make Plone more accessible (like the buildout builder) versus > more feature rich (incoming mail handling; faceted search) > > As a (somewhat experienced ;-) ) Plone user myself, I'd prefer > the new features but as a community member I should have > a different preference I guess. (and the fact that I offer to > mentor the buildout builder project makes me somewhat > biased of course) > > Raphael > > > > > Matt > > > > > > -- > Archive: > http://www.openplans.org/projects/plone-summer-of-code-2008/lists/plone-soc-2008-mentors/archive/2008/04/1208508000600 > > To unsubscribe send an email with subject unsubscribe to > plone-soc-mentors@.... Please contact > plone-soc-mentors-manager@... for > questions. > >
-
Martin Aspeli wrote: > I think in the event, given that we have more "desirable" proposals > than we have slots, we should make a judgement based on the quality of > the student and his/her proposal, rather than our subjective idea of > what we think is most useful. In the past, at least, it's been fairly > clear which students are more likely to deliver. > > To me, the ideal candidate is one that is currently a peripheral > community member who is at least known on the mailing lists and/or has > some proven capability, who has submitted a well-written proposal that > looks realistic and which he/she seems passionate about. > > It's hard to make choices, but this is a "nice" problem to have. :) > > Hi Martin, good points and I only realize now that I should have been more clear in my recent posting. Of course student and proposal quality are the number one criteria but now we are facing a situation where we need to differentiate between proposals that came out as (almost) equal based on that. And this is were IMHO such "strategic" considerations do have some value. Just my 2 cents Raphael > Martin > > On 18/04/2008, Raphael Ritz <raphael.ritz@...> wrote: > >> Matthew Wilkes wrote: >> >> >>> [..] >>> Ok, well we need to pick the one that loses out then. I agree, east-asian >>> >> support needs to be done, should have mentioned that in the first mail. >> Oops. >> >>> >> I just increased my scoring for this from +1 to +2 so >> it advanced a bit more still. >> >> >> >>> My preferences out of the current top 6: >>> non-at membrane >>> buildout builder >>> compontent registry >>> east asian >>> faceted search >>> event based email >>> >>> i.e. I'd think about swopping event based email for east asian support, >>> >> especially as singing and dancing now exists. >> >>> >> Not sure I follow here. The existence of singing and dancing makes the >> 'Event based mail handling' more feasible I'd say. >> I see this rather as a decision between contributions which >> make Plone more accessible (like the buildout builder) versus >> more feature rich (incoming mail handling; faceted search) >> >> As a (somewhat experienced ;-) ) Plone user myself, I'd prefer >> the new features but as a community member I should have >> a different preference I guess. (and the fact that I offer to >> mentor the buildout builder project makes me somewhat >> biased of course) >> >> Raphael >> >> >> >> >>> Matt >>> >>> >> >> -- >> Archive: >> http://www.openplans.org/projects/plone-summer-of-code-2008/lists/plone-soc-2008-mentors/archive/2008/04/1208508000600 >> >> To unsubscribe send an email with subject unsubscribe to >> plone-soc-mentors@.... Please contact >> plone-soc-mentors-manager@... for >> questions. >> >> >> > > > -- > Archive: http://www.openplans.org/projects/plone-summer-of-code-2008/lists/plone-soc-2008-mentors/archive/2008/04/1208516147021 > To unsubscribe send an email with subject unsubscribe to plone-soc-mentors@.... Please contact plone-soc-mentors-manager@... for questions. > >
-
-
-
-
-
Hi Matt, On balance, I would second Daniel's sentiment that East Asian Languages should go in. I would swap the Buildout Builder for this, personally. To my mind, Batch Editing is more important than Event-Based Email. I think Plone's email story needs some work, but incoming email in particular is a specialist use case that not everyone needs. That said, the student has been very active and good at seeking input, so I suspect we'd get a strong performance from him; the Batch Editing proposal is less developed than the Email one. Portlet Infrastructure Improvements are probably more important as well, but also easier to get wrong for a less experienced developer. I would suggest: - Component Registry Introspector - East Asian Languages - Non-AT membrane - Event-base email - Facted search I would also suggest that we contact the authors of - Batch Editing - Portlet Improvements - Buildout Builder - Searching/Indexing - New Template Languages and tell them very clearly that we would've picked them if we could. I'd like to offer them informal mentorship and help if they choose to work on these proposals without Google funding - if mentors agree, of course! Martin > We now know we will get 5 slots from Google. This means as we > currently stand the following projects will be accepted: > > Component Registry Introspector and Zope 2 / Plone integration. > Non-AT membrane, a new plone authentication scheme and ldap > Event-Based Incoming and Outgoing E-mail for Plone > Faceted search and navigation core and interface > Buildout Builder - An automated buildout configuration system. > > These will not: > > Plone Batch Editing > Develop Search System for East Asian Languages. > Leveraging the Plone external indexing and searching story > Portlet Infrastructure Improvements > Integrate new templating engine into Plone > > and others with no mentors assigned. > > Any opinions on if this should change should be voiced immediately. > Personally, while I'd like to have seen external indexing and portlets > I can't think of any of the above I'd want to move. Does anyone else? > > Matt > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (Darwin) > > iD8DBQFIB929ZnKd+ctxHMoRAqGVAJ9upW+HgMkqGivQvZZ8VgflWjkuQACfVWKE > axezDgzEJqfRa0UDIJZ4Q1o= > =M1vD > -----END PGP SIGNATURE----- > > > -- > Archive: http://www.openplans.org/projects/plone-summer-of-code-2008/lists/plone-soc-2008-mentors/archive/2008/04/1208475087875 > To unsubscribe send an email with subject unsubscribe to plone-soc-mentors@.... Please contact plone-soc-mentors-manager@... for questions. > >