Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lsp4e-dev] [soc-dev] For reviewing proposal idea for GSoC

Hi,

I trully agree with having a flexible timeline but GSoC suggest here to have a weekly timeline. I didn't find any specific rules/format of proposal for Eclipse on Eclipse wiki. If there is any format for Eclipse, please provide that will be very helpful.   

I wrote a draft proposal. I will elaborate the milestone and add timeline part soon. In timeline, should i write describing every week or phase. It is challenging to write a weekly timeline for a flexible idea. Need help. 
Is it mandatory to describe in weeks or have a rigid timeline for writing proposal to Eclipse?  
Please review it.

Thanks

On Tue, Mar 26, 2019 at 1:48 PM Mickael Istria <mistria@xxxxxxxxxx> wrote:
Hi,

Support for snippets is a good and complete topic and affects several Eclipse.org projects, so that's cool to work on it and 7 weeks seems to be a good estimation. But like all estimation, it may as well be way too short or way too long ;) It can also be that with 2 weeks of work, you get a partial support that is already covering the vast majority of cases, and that we decide that some other issues are now more valuable to work on instead of spending 5 more weeks on corner-cases...
About the additional features, I'd suggest avoiding https://bugs.eclipse.org/bugs/show_bug.cgi?id=509052 which doens't seem very "trendy" at the moment (ie there are not so many requests for it), and https://bugs.eclipse.org/bugs/show_bug.cgi?id=545005 which is IMHO a corner-case of the API that's not so profitable in the vast majority of cases. I closed https://bugs.eclipse.org/bugs/show_bug.cgi?id=508920 which was most likely fixed in last release.
What I think would be better candidates are the missing LSP features in LSP4E (like prepareRename). It would be nice if you could cover some of them as part of your GSoC proposal. I don't think you need to sort out the exact features right now and detail them in your proposal (I may be wrong, I didn't read the details); so you could write something like "Once the support for completion snippets and choice is implements, we'll audit LSP4E compliance with the LSP specification, and find out the missing features. Then, depending on the results of this audit, we'll try to implement the most important ones.". Even if you discover 15 missing features and can only implement one, the fact that you open 15 bugs to the project that weren't open before is a valuable contribution that can be highlighted as part of the GSoC.

Cheers,
_______________________________________________
lsp4e-dev mailing list
lsp4e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lsp4e-dev

Back to the top