Porting to Drupal 8

Awesome to have you part of the team and getting started! We are always available for feedback.

Could you please update this post with a bit of status and strategy detail (next steps / short term goals) on a periodical basis?
The finally ultimate thing would be a roadmap with a timeline. ;-)

Yeah, we're going to make a contrib maintainer out of you ;)

Started a roadmap in the issue summary.

Thank you for the great progress recently and we are happy to have you join our sprints!

As discussed, we recently stumbled upon personalisation again and actually with every single project this topic came up. (And some strange hacks / custom modules where required since simplenews is not really made for it out of the box...) I do like to address this issue with our Drupal 8 release as early as possible.

Possibly missing above is a migrate path and in reference to the issue about the status of 7.x-2.x the question if we support it at all for migration or if we recommend to migrate from 7.x-1.x.

Added migrate path to summary ;-)

With migrations, it would certainly be easier to support both, but there's a lot of stuff that yet needs to be figured out. The default migration would automatically convert the taxonomy terms that we no longer need for example, but I guess you could delete them manually.

There are few reasons to do something special with the target, what we need to provide are sources for all variants that we want to support, process plugins and migration entities to tie it all together.

We have subscriber management working and we're pretty near to Beta.
It's time to have a 8.x branch in Simplenews and a dev release to make this progress visible for the d.o module search and overview pages.
As such i would not wait for the feature "sending newsletters" to complete to merge it in.
As a result, switching to a strict issue based patch + review workflow would be best for future improvements.
What do you think, when is the right time to switch?

I think it's too early for that. IMHO doesn't make sense to do that before most of the existing tests are working again, I can review on github too. patch based processes are too slow for the current phase and testbot is broken anyway it seems.

Understand. Please still reconsider before DrupalCon (Contrib Status) though. :-)

Great progress.

As discussed today:
In Simplenews 7.x we have naming issues due to historic reasons. We thought this was corrected in 7.x-2.x but most importantly for 8.x, we should decide for a clean naming and strictly stick with it. Newsletter, Issue, ...

Also, i would love to have simplytest.me integration ASAP for demo purposes. We push this with all our modules to lower the barriers and people can learn about the module by example. :-)

As discussed, we introduce the concept of a subscriber.
In order to manage subscribers, we have put subscriber management under people.
Similar to Configuration of "Account settings", there should be a "Subscriber settings". The subscriber field management should be there.
The Subscriber settings will then host settings that maintain the relationship between subscribers and users.
This leads to a pretty clean UI / consistent D8 core UX patterns.

Session about Simplenews port status prepared for DrupalCon, together with ifux.

I also requested collaboration with the more recent added newsletter module...
#2346641: Drupal 8 port
Would be great if we find a collaborative consensus for Drupal 8.

BTW: Arla implemented field sync between Subscriber and User.
We are looking forward to merge in full personalisation this week!

Also added an issue about simplytest.me demo data i do like to see:
#2346837: Support simplytest.me

I vote for merging this project in to d.o and start working issue queue based.
What do you think?

Pushed the current code to drupal.org, after some further cleanup. Commented out a handful of failing tests as drupal.org testing is only useful if the branch is green. Opened #2401019: Enable commented out tests in 8.x-1.x as a reminder to uncomment them again.

I would suggest to create follow-up issues for the remaining issues and then close this issue.

https://www.drupal.org/node/2401069

https://qa.drupal.org/pifr/test/937688 came back green!

Awesome!

Will test it soon and start creating issues. :-)

Unassigning ifux from this task.
Opening this task and all followups to other contributor from team and community.

Issues created as discussed. uploading a patch to remove todo.txt

Great. The only task here that did not have an issue yet was migration support, we created that as well.

Marking this as fixed, there is of course still a lot to do, but we will track further progress in separate issues.