Offering to co-maintain Feeds Extensible Parsers

Thanks for your offer! I've added you as a maintainer. I left out the "administer releases" permission for now, because sometimes I'd like to coordinate these with a Feeds release. There have been cases where I added a new feature to Feeds that required changes in Feeds Extensible Parsers and therefore the dev release of Feeds Extensible Parsers sometimes depends on the dev release of Feeds.

Every Thursday there is a Feeds meeting on Drupal Slack in the #feeds channel. From November until near the end of March this is from 19:00 to 20:00 UTC and from April until near the end of October this is from 18:00 to 19:00 UTC. These meetings are a moment to discuss progress on the project.

Are you able to join these meetings at that time?

I've just added you to the #feeds channel on Slack.

Thank you! I am so happy to help you with module maintenance stuff.

About meetings, I'm not sure if I will be able to join them due to the timezone, a bit late for me, but I'll try to stay in tune with the latest changes, discussions, etc.

@_shY
I see that timezone can be an issue, I see that it would be quite late in the evening for you. It is also possible to respond later, although then it will probably take a little longer before I reply. You also don't have to participate in the meetings necessarily every week. It's just a place/moment to ask questions about the project ("What does this code do?" or "How does feature X work?") and to make plans about what feature or task to work on. And each week there is an opportunity to talk about the project.

At the moment, I'm not actively working on Feeds myself as I need to take some more rest. But I still like to assist or discuss development at least that one moment in the week (and other moments in the week if I can).

Thanks again for offering your help. :)

Ok, I got it, thanks for the clarification.

I also currently don't have much time to spend on this kind of thing but will try to investigate the module codebase for better understanding.

Automatically closed - issue fixed for 2 weeks with no activity.