Create installer file + separation of css and JS

Some copy-paste issues and permissions missing as discussed in IRC.

Yeah, maybe initiative issue tags is not a great name for possible other uses. Also, an upgrade path would likely be great for at least me :D I have lots of content in books (like http://hojtsy.hu/d8mi/base-language-features and parent and children) and would hate to loose them to regenerate the whole thing. So if you can write an update that assumes people used book node types for pages and the other hard-coded things, that would be great :)

Also, the lead user thing will need to be configurable and/or removable. I filter that out in D8MI because it would give me proportionately very big visibility int the list and that is exactly counter to the goal :)

A follow up patch, but maybe getting out of scope: i'm planning on using this so i can easily track all projects i'm involved in, so i added a 'project' taxonomy and fields to both issues and pages.

I tried to keep it backwards compatible with the original version, but if you want to collect issues from multiple url's you can use something like

    $issue_page = "http://drupal.org/project/issues/flot?version=7.x";
      rocketship_parse_all($issue_page);
    $issue_page = "http://drupal.org/project/user/829198";
      rocketship_parse_all($issue_page);
    $issue_page = "http://drupal.org/project/issues/user/105002";
      rocketship_parse_all($issue_page);

I added drupalorg_nid as well, easier to link from inside views

Some other ideas:

• Add separate taxonomy for status and maybe even reduce them like the code does, no they are inside the initiative tags as well, kind of hard to filter (see http://rocketship.h001.attiks.com/issues)
• Find a way to get last updated date

Find a way to get last updated date: fixed

demo site re-installed: atix.be/rsdemo

added a check to only update outdated nodes and bail out if no update is required

Ignore #7, use this one

It appears that all the patches after Gabor's first one are diffs from that point, and don't add the installer file itself. This is kind of confusing. Can we get a fresh patch that will work on a fresh branch?

Hm, maybe I'm nuts but I can't get any of these patches to apply properly?

Included a patch against master, maybe this can help.

I made some one-off changes for my hojtsy.hu deployment, which I should probably port upstream (focused on running the D8MI initiative really, and just posted this in a "if you find it useful" capacity :) but I think attiks and swentel jumping on it at the same time discouraged both of them from keeping up because it was hard to sync efforts.

Hi all -

I'm late to the party here. I just started looking at Rocketship last week while attempting to help set up some sites for other D8 initatives. In so doing, I fixed the sitebuilding-related issues you're handling in the patches above in my own way, before I spotted this issue.

If you think that the patch in #12 is still worth pursuing, I'll be glad to assist in getting that completed. However, I just tried to apply it without success.

Here's what I've done on my own - perhaps it will suffice:

I've taken the Rocketship install that @no_angel has built for the WSCCI initiative, based on conversations she had with @svettes and others, and have exported a feature containing the content types for issue and issue (book) page, plus the taxonomy vocabulary. You can find the feature at https://github.com/dsayswhat/rocketship-config if that sounds like a reasonable approach.

I've also added a configuration form to this module allowing the selection of which taxonomy vocab to use for issue tags, and to configure the master tag to pull from d.o. I've got a patch uploaded over at https://drupal.org/node/2106083#comment-7938861.

Let me know if that sounds reasonable, if you want to include the content types in this module directly, with features, without features, or want to go in a different direction.

Setting this to 'needs revew'

IMHO it would be great to do this step by step in a way that is reviewable. #2106083: Make taxonomy and d.o issue tag configurable is a good first step. I think other improvements from this issue would also be great, we should try and go step by step instead of big bangs.

I've split this patch into separate issues so it's more manageable:

#2277743: Create content types, fields and vocabulary on install
#2277745: Create default taxonomy on install
#2277741: Separate CSS and JS files