I’ll volunteer to write up a spec for the user-customizable tabs. I don’t think it’s necessarily that complicated and may be doable as part of GSoC (but we can defer that discussion until there is a spec to review). I’ll keep the scope of what a first iteration might look like in mind as well.
It’s just hellishly complex to do natural language processing. That alone is a giant red flag for me.
And let’s compare:
(typical discourse reply to a topic)
Hi this is DiscourseBot! Please upload an image and make it your logo!
Welcome to Discourse! Please click the button (the only button that’s on the screen right now), to upload a logo for your forum.
I think the former is completely awful compared to a simple full screen setup wizard, to the point that I oppose it violently.
Anyway this gets into first run setup which is massively strategic for us this year, and there’s no way in hell I would outsource that. It’s deserving of a much deeper conversation far outside the scope of Google SoC.
I’m a Googler who’s worked with AMP last week and I believe it is quite ready for prime time. More and more publishers have been providing article versions abiding by the spec, and it’s supported by Google, Twitter, LinkedIn etc. If there are specific issues I could help with, I’d be happy to do so or refer to my colleagues.
capabilities to connect between multiple Discourse communities and having some overview of recent post, the posts of the persons I follow, something like a RSS reader just for Discourse
(of course with opt-out/opt-in function for users and admins)
An even more elegant way how group members could work together:
In past years, there was a set date by which you needed to inform Google of how many slots you wanted, based upon how many “good” applications/proposals each org got. Sounds like they will be sending out an email later this week about how the process will work this time around.