I think many will agree that Lettuce needs another maintainer.
I'm willing to give write permissions to this repository for someone who:
Please comment here if you are interested in becoming a new maintainer for lettuce and why.
Thank you so much :)
Hello. I would be interested in helping maintaining this repo if possible.
In working with lettuce i have learned a lot and i am highly dedicated to testing for the sake of the code.
I have gone through: testing/doc writing and development throughout my career as a professional.
I would also be available for doing the documentation work as well/features/bug fixing.
@adaschevici would you like to merge some specific pull request or close an issue?
I just wanna have a sense of how you code, then we discuss the merge, and I give you commit access to the repo.
How does that sound?
Also @danni just joined as co-maintainer
@gabrielfalcao : sounds good.
I started checking the issues
I have 2 pull requests: #413, #414 for issues #58 and #245.
Also i would like to close #282, #170 as they no longer reproduce as far as i can tell.
For #198 i haven't found any elegant solutions but since jython is almost at 2.7 i propose closing this one as well.
@danni and @adaschevici are co-maintainers now.
Now we need a way to keep in touch to circle up things before releases.
@gabrielfalcao and @danni
email/skype/hangouts whatever works i'm fine with it.
Hi guys, I just wanted to see whether there's likely to be a new package on pypi any time soon, as the last package was uploaded 2013-08-26 and there have been a reasonable number of changes since then - I'm currently stuck with -e git+https://github.com/gabrielfalcao/lettuce.git#egg=lettuce in my requirements files.
@danni that sounds good to me. Should I make the release?
There are pull requests that could be merged before this new release, what do you think? I'm specially interested in the #437 and #445 but there are some typo fixes that would be easy to merge too.
Any update on the new 2.x package?
@gabrielfalcao @michelts any clue as to whether we might get a package soon? Id be happy to have a second release one some pull requests have been merged, but currently installing from github is interfering with a workflow involving using pip2pi
Sorry, I couldn't find a way to change #437 approach, as @danni suggested. In that case, I think we must go ahead without it...
I just released 0.2.20, sorry for the delay.
The integration tests are not working in my computer and it was intriguing me since the travis build is green.
It turns out that the integration tests were not running in travis anyways. So just released it considering that unit and functional tests work.
Hi, I am also interested in reviewing / maintaining lettuce.
Just to know, the project is being worked on infoxchange/lettuce:new-parser, isn't it? (+ #430) There are lot's of PR waiting and the project seems dead. Maybe a note in README.md would help. I was thinking to fix two issues I've found but I'm not sure if it's worth it, or if it'll better to directly work on infoxchange repo.
Anyway, I really appreciate the work done so far.
@dnozay, @doup I'll be glad to give you commit access on lettuce.
I feel really bad because I haven't used lettuce myself in so long.
I built this project because I needed it and I used it for years, but lately I've been working on project where pure unit and functional tests are all I need. I used to use lettuce only for acceptance tests
What I have seen done with other projects: create an organization (e.g. "lettuce") and transfer ownership to the organization, then add folks to the organization.
@dnozay, @doup on what danielle said. The new parser is really nice and i've tried for a while to get it to pass with the tests but no luck.
This needs to be done somehow to return lettuce to the stable status. I haven't really had time to work on it...for the past year but i am planning to start working on this again as well.
If you guys want to help you are really welcome to it and i want to help if i can. I have been keeping an eye out on what is going on.
Are there any plans to add the ability to generate a cucumber.json for use in Jenkins? If not, I might be interested in adding it.
@gabrielfalcao - could i please have committer access?
@danni - since you have committer access, can you please push the new parser branch to this repo (e.g. a new-parser branch)?