Closed (fixed)
Project:
References
Version:
7.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2012 at 20:28 UTC
Updated:
17 Jan 2013 at 15:30 UTC
Hi there,
I am working on a project that does require a number of allready submited,tested and reviewed patches applied ( e.g. #506654: Autocomplete for nodereference Views exposed filter & #1064544: Node reference doesn't work when title exceeds 128 characters) and some sort of stable release existing on d.o. I'm willing to help getting some pace back into this issue queue.
Please consider this request for co-maintainership.
Thank you
Alex
Comments
Comment #1
Alex Andrascu commentedComment #2
Alex Andrascu commentedComment #3
jonanthony commentedWorking with Alex on a multilingual NGO project that needs this.
Alex I am willing to support you maintaining this.
Jon
Comment #4
yched commentedThanks for the offer, Alex :-)
So, the thing with References is that, as mentioned on the project page, it was targeted for deprecation in favor of Entity Reference.
I think Entity reference now includes all the features of References, and is clearly the future-proof way, so it's probably the one we should encourage new sites to start out with. It's also being considered for inclusion in D8 core, so D8 migration would probably be easier if your D7 site uses it rather than References (although the D8 inclusion thing is not fully settled yet)
This being said - I do understand the need for an official release, and apologize for failing to do so.
I discussed with Entity Reference maintainers, and they're fine with having References live alongside.
In short : References module is yours, you'll be granted commit and administration grants briefly.
Aside from polishing a release and fixing bugs, I'd suggest refraining from adding too much new features that would make eventual migration to Entity References difficult - or maybe synchronize with Entity Reference maintainers to try and keep feature parity ?
But well, you have the keys, you'll do what you see fit :-)
Comment #5
fgmConfirming what yched said: References was something we wrote based on CCK 6, but which was never intended as a long-term solution, expecting some new refactored solution with a better architecture, which EntityReference and Relation, each in its own way, have brought to fruition.
But since experience shows new users keep accumulating, and you are willing to spend time on a new release, I've added you as a maintainer: you may now edit the project, commit, prepare releases and manage the issue queue. Hopefully heading towards EntityReference compatibility, but that's your call.
Merry Christmas!
Comment #6
Alex Andrascu commentedHi Frederic, Yves
Happy New Year ! Thanks for adding me as a maintainer. I totally agree that Entity Reference is the way to go for new sites, and we will fully support and advise so, but as we can see there's quite a community out there that is still using References. Somehow they will need migration guidance, maintenance and support and we allready have to provide this for some of our clients.
Many thanks
Alex