Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Greeting Drupal Contributors!
The Flag project is looking for additional maintainers and preferably a new project owner. I ("quicksketch") have been maintaining the project since it's creation, and I maintained its predecessor (Views Bookmark) after Earl Miles originally wrote that code. The project has been through some pretty major changes, including Objectification of our APIs; updating 3rd-party integration with Views, Services, and other modules; support for Session API and anonymous users; the port to Drupal 7; etc. Since the departure of Flag's other maintainer mooffie, I've been hard-pressed to find time to support Flag module adequately on my own. Flag module has been fully ported to Drupal 7 for months and months, but we're just shy of making a final release for D7.
After the D7 port though, we've got some pretty major changes that need to be implemented, including:
#1035410: Flag any entity
#871064: Making flaggings fieldable
Flag module has been successful through balancing core features with flexible APIs and lots of 3rd-party integrating modules. If you think you'd be a good maintainer who shares this vision and direction of Flag module, post here or contact me via my Drupal.org contact form.
Comments
Comment #1
rafamd CreditAttribution: rafamd commentedShouldn't this be planet material ?
Edit: quicksketch, thanks for your work on Flag and for taking the lead in handling over the baby.
Comment #2
joachim CreditAttribution: joachim commentedI'd love to help, but I fear I am already spread pretty thin...
Very tempting though. Flag's a super module, and it so happens that I'm going to be using it on a project I'm on at the moment. We're going to be looking at #1035410: Flag any entity, if not both those issues mentioned above.
If anyone else throws their hat in the ring and wants a co-maintainer, count me in, but don't think I can carry this one on my own.
Comment #3
socketwench CreditAttribution: socketwench commented*throws in a hat*
I may not have a module to my name (started one on 5, another on 6, and two on 7, but none ever released), but I could make the time to maintain this module.
Comment #4
quicksketchHi, thanks socketwench! I looked over your existing projects on d.o (specifically http://drupal.org/sandbox/rashfeather/1540322). Before I hand the project over to another maintainer, I'd like to see that it continues being developed inline with Drupal's coding standards (http://drupal.org/coding-standards). It looks like your code is pretty good but poorly formatted. Could you run the http://drupal.org/project/coder module on your ReMarkable module, and update it to match the standards that it recommends (when running on "Strict" mode)? I'll feel much better knowing that the existing (Drupal) standards of coding are applied to the Flag project going forward.
Comment #5
joachim CreditAttribution: joachim commented@quicksketch: I'm a total stickler for coding standards; I'd definitely keep any co-maintainers in line :)
Comment #6
socketwench CreditAttribution: socketwench commentedYou just set my weekend agenda. :-D
EDIT: Also, I'd like to point out that the vast majority of ReMarkable's code is a direct import from another developer. It's most certainly not coded to standard. The fact that it's the major functional component of the module has prevented me from submitting it as a public project until I rewrite it.
A better example might be http://drupal.org/sandbox/rashfeather/1509078
It's all my code, but very much not in a solidified state.
Comment #7
quicksketchThis looks really good. Thanks @socketwench for updating all that code! Combined with @joachim, I think this sounds like a great combination. Based on the feedback above, I've made socketwench the "owner" of the project and added joachim as a co-maintainer. Probably the most important thing to do is to just make a new release of the current devs. The impatient have started making issues: #1676376: Release 7.x-2.0-beta7 ;)
Comment #8
dwwGlad to hear this is resolved.
Note to the new maintainers: Flag is used on Drupal.org to provide the issue following functionality (see Stop subscribing, start following for more). We're in the process of porting this to D7 over at #1560010: [META] Port issue following functionality to D7. It's important that Flag remain stable, secure, and performant enough to handle the massive load on Drupal.org. ;) If you're planning any major changes (e.g. new dependencies, big architectural refactoring, etc), it'd be much appreciated if you pinged the Drupal.org Infrastructure issue queue to let us know so we can review things and know what's coming if we upgrade. ;)
Thanks!
-Derek
Comment #9
joachim CreditAttribution: joachim commentedThanks quicksketch!
And dww, yup, we'll bear that in mind.
Comment #10
socketwench CreditAttribution: socketwench commented@dww For the time being, I have no major changes in mind at all. My thought is to start going through the issue queue (which will have the knock-on effect of familiarizing myself with the code in detail). I'd like to start with smaller bugs and submitted patches and work forward to trickier bugs and feature requests. Only afterward will I want to start thinking about major changes, if any.
Sound good to you, joachim?
Comment #11
socketwench CreditAttribution: socketwench commented@quicksketch And here I thought there was much more to be done with bringing my code up to standard. ^^; I would have started last night, but Spouse #1 just got back from Australia, and then I got caught up in a WSCCI issue. #1676376 is the first thing I'll look at tonight.
Comment #12
joachim CreditAttribution: joachim commented@socketwench: That sounds good to me. My impression is that the biggie is #1035410: Flag any entity, and I feel that should block a 2.0 release. I plan to work on that one as a priority, so if you want to deal with the smaller bugs, that's great.
The next big thing on the roadmap is making flags themselves entities (#871064: Making flaggings fieldable). That could either go in 2.0, or in a 3.0 -- we can figure that out when we come to it.
I'm usually on IRC UK daytimes, so hope to chat to you sometime there. Howdy, co-maintainer! :D