Hello there,

The previous maintainer/owner was not up to task and I've been trying to get in contact with the owner. Now I've obtained ownership of Default Content and I'll do my best to fix all the issues we have here.
Now Default Content currently supports exports of nodes to a Features module after manually filling out the machine names for every node to be exported, while UUID Features Integration makes use of UUIDs (Universally Unique IDentifiers) generated automatically by the Universally Unique IDentifier module. The latter option saves a lot of time since you don't have to manually enter the machine names for every node you want to add to the Features exportable. Also, with UUID Features, you can export taxonomy and fields beside nodes.
Earlier I decided to mark this module as deprecated in favor of UUID Features, but after seeing there are so many passionate users/developers providing patches and all those features requests I feel that it's unfair to put the development to a stop. I've used UUID Features and even the latest alpha release doesn't work. So I created an issue for UUID Features and asked to merge those two modules together. If the maintainer of it is not responding, I'll request to take the module over and the merging process will be way easier since the two modules are under my control.
The 7.x-1.x branch will basically stay the same with some more features added from those feature requests in the issue RTBC and eventually cease development.
The 7.x-2.x branch will implement UUID to ease the processs of manually entering machine names. An upgrade path from 1.x to 2.x is not the top priority, but if anyone's willing to work on it, it will do. Developers for the 2.x branch wanted! I'm not familiar with UUID so providing patches will be a great help.

UUID Features implements in a way that is more flexible than Default Content. Therefore, Default Content is deprecated in favor of UUID Features. UUID Features should also be considered first on fresh projects. There will only be bug fixes.
Thank you all so much for your contribution.

Comments

Jeffrey C.’s picture

Issue summary: View changes

Fixed the typo.

Jeffrey C.’s picture

Title: Words from the New Maintainer and the Future Plan » Future Plan
Jeffrey C.’s picture

Issue summary: View changes

Some modifications.

Jeffrey C.’s picture

Issue summary: View changes

Updated.

Jeffrey C.’s picture

Issue summary: View changes

Updated.

Jeffrey C.’s picture

Issue summary: View changes

Fixed the typo.

Sheldon Rampton’s picture

Hi Jeffrey. I think I understand what is happening here but would like to make sure. It appears that there has been no new development on the UUID Features Integration module for the past six months. Based on the discussion here, it appears to me that you are planning to either take over development of the UUID Features Integration module or else work with its maintainer to ensure that it receives further development love. Is that correct?

I just had a fairly difficult experience using UUID Features Integration to export taxonomy terms. I hope that I can count on it to receive future updates so that its quality will improve.

Jeffrey C.’s picture

Hi Sheldon,

Yes, in fact, I've already taken over the UUID Features module and will put all my efforts on it, you can surely count on it for future development. While there are still some problems with UUID Features at the moment, you may want to follow its issue queue and apply some patches to get the functionality you need working.

Jeffrey C.’s picture

Issue summary: View changes

Updated version.

andypost’s picture

According #3 there's no future plans for the module namespace.
So closing this one as duplicate in #2344517-5: Consider merging github.com/larowlan/default_content as Drupal 8 solution

Feel free to re-open if any thoughts of other co-maintainers
PS: 7.x has 8k users!

andypost’s picture

Status: Active » Closed (duplicate)