This is tricky, simply because we need communication to reach out to devs - I am not a dev so you guys know best what would attract you, and what is needed. As for Developer Edition with dev tools we could have Neon split into "Unstable", "Stable" and "Developer Edition" and split the page properly into three sections, three individual pages. One Normal ("Stable" former User edition), one with inverted colours (so its dark and scary) which is unstable - and the this. That page need to be marketdly different, not shy away from being technical and provide links and information to development relevant pages as well as contacts to KDE Devs in general.
(which would be interesting having "mentor devs" who's job it is to try to guide people to the right place, or right person to talk to - like welcoming devs or whatever)

@jensreuterberg We'd have 4-5 editions though.

• Neon Developer Edition Unstable (this is from-master builds)
• Neon Developer Edition Stable (this is from-maintenance branch builds. more stable than master, but still not quite user focused also see T4169 for a discussion on it being a misleading name)
• Neon Developer Dev Edition (i.e. thing at hand. with as yet undecided build quality, probably a version of user edition builds though)
• Neon User Edition (i.e. for end-users; using released software only)
• Neon User Edition LTS (end-user, plasma LTS, if anyone ever does work on this)

I am still stoked for the color-inversion idea, but the names need changes beyond recycling "Developer Edition" for the new ISO at hand. 2 immediate thoughts would be to change them from Developer Editions to Testing Editions

• Neon Testing (former dev stable; maybe could be Testing Stable, as for T4169 I'd almost be content in avoiding the word stable though)
• Neon Testing Unstable (former dev unstable)
• Neon Developer Edition (new thing)
• Neon User Edition (end-users)
• Neon User Edition LTS (plasma lts)

The other is going with the names Riddell apparently changed the download buttons to.

• Developer Edition Git-Unstable Branch
• Developer Edition Git-Stable Branch
• Devleoper Edition
• User Edition
• User Edition LTS

(I don't particularly like those because they are long AF names and are technically not even correct)

Currently proposal on the table:

• Neon User Edition
• Neon Testing Edition [formerly stable]
• Neon Unstable Edition [formerly unstable]
• Neon Developer Edition [new]

I like these new names, although to add confusion we have the LTS due in User and presuamble stable/testing which I'm working on now.

@jriddell what's stable/testing?

stable/testing being dev/stable which is also due to get LTS builds.

Looks good to me, sry for being away was away for a few days for family stuff. It all seems to make sense.

I mean we WANT to push users to the User Edition, and as long as we make sure to communicate to any casual reader that "User Edition" is waaaaaay safer than say "Testing" or "Unstable" we're golden.,

Get this to pass and get some QA so it keeps passing
https://build.neon.kde.org/view/iso/job/iso_neon-development_bionic_devedition-gitunstable-development_amd64/

Now that I see this is happening (yay!) I have some ideas, based on my own use of the current Neon Dev Unstable ISO:

• Pre-install all necessary packages (KDE and 3rd-party alike) that are build or runtime dependencies of KDE Frameworks, Applications, and Plasma
• Ship with git source checkouts of all KDE Frameworks, Applications, and Plasma in ~/kde/src/
• Pre-install a symlink to ~/kde/src/kdesrc-build/kdesrc-build in /bin or ~/bin (or otherwise ensure it's in $PATH), and ship with a sane ~/.kdesrc-buildrc file