Hi,

I just read about the Summer of code program and i was happily suprised that improving the searching facilities of Lenya was listed. I have been working a bit with lenya the last couple of months and noticed quite a lot of improvements that could easily be made. I would be delighted to work on the searching facilities of lenya, implementing the proposals as posted and possibly adding some of my own ideas.

Are there any other applications made for this project and who would be interested in mentoring my development efforts, if it isn't too late to make a decent proposal?

Kind Regards,

Robert Goen�


Andreas Hartmann wrote:
[EMAIL PROTECTED] wrote:

I already made search a usecase for Lenya 1.2


this refers to the new-style usecases in 1.4.


I am uncertain when I will look at 1.4. Will 1.2 Usecases not work in 1.4?


They basically will (the infrastructure will be available),
but some changes will be necessary due to API changes.

[...]

I tend to keep my own list of itches to be scratched, then either fix
them myself or assign them to employees.  I have yet to become
comfortable with the collaborative development model.
- Will I become annoying if I submit all the possible improvements I notice?


No, quite the contrary!
Improvement suggestions are always welcome, especially when they're
added directly to Bugzilla - preferrably a separate bug for each
improvement.


- Do I need to search existing bugs before submitting each one, or
will the devs notice duplicates?  The extra time to search, and fear
of posting duplicates would really slow me down.


IMO it would be nice if you display the list of all bugs and use
the browser's page search on one or two keywords. But nobody will mind
marking a new bug as a duplicate, don't worry.

- When do I switch from 1.2.2 (with a project almost released for
production) to 1.4, which is not ready for production and seems to
have upgrade issues, so that my improvements are compatible and can
become part of the project?


IMO you should just do what you can, if 1.4 doesn't suit your project
plans (it's really not ready for production), submit your patches
for 1.2. Even if they won't go in the code base, people can download
and apply them to benefit. My personal opinion is that major changes
should be done only in 1.4, but I can't predict how difficult it is
to port a patch to 1.4 (it depends on the affected code).

-- Andreas




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Robert Goen�

Kadijksplein 14-II
1018 AC Amsterdam
06 26090816

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to