Re: Sample Forum
Bump. The forum will only be up for another week. Paul, any more thoughts on this? -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: Sample Forum
The delay can be removed, no worries :). The posts from the forums do not show up on the mailing list, but they show up as emails as if they were part of a mailing list. Basically the idea is that people don't have to leave their email client if they don't want to. Apologies if that was unclear. -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: Sample Forum
Let me clarify the two minute delay. When you start composing your post (on the forums, not from email) you of course have an unlimited amount of time for writing your post. Once you post it on the forums, it is posted to the forum instantly, but the email to people receiving emails alerts is not yet sent. After two minutes the email alert will be sent. This gives you time to fix a mistake , if you made one, before the email is sent out. When you post directly from your email client, there is no intentional delay. I see your post in my email! Thanks for giving it a try :) -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Sample Forum
Hi guys, today I have set up a sample Discourse forum for everyone to use. You can find it here: http://groovy.trydiscourse.com/ This forum is configured to behave almost exactly like a mailing list, for those who want it. You can mail in topics. For example, send an email to: groovy+us...@discoursemail.com - you should not have to create an account for this to work. It will create one for you. In addition, if you create an account on the forums, you are by default subscribed to the categories of the forums, just like the mailing list. New topics will trigger an email sent straight to your inbox, to which you can reply. Obviously you can reply to them on the forum as well. When replying via your email client, you should take advantage of using Markdown syntax. I've also created a sample topic (copied from the mailing list) for you to view on the forum, so you can appreciate the modern forum experience that Discourse offers: http://groovy.trydiscourse.com/t/improving-named-argument-support/15. I encourage you to look at the current equivalent here: http://groovy.329449.n5.nabble.com/Improving-named-argument-support-tp5746753.html for comparison. Please feel free to make your own topics and see how they interact with your email client and let me know if you have any problems. Quick note: when you post a topic, there is a 2 minute window in which you can make edits before it is sent out to email subscribers, so if you experience delay that is why. -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: Improving named-argument support
MG's approach is the one I favor, although I am not sure I like using = in the calling syntax; the colon makes more sense to me. Small detail, though. -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: Improving named-argument support
Paul, I am very much in favor of this idea, but I do not like the execution. The need for those annotations makes it quite verbose and it seems a bit too complex. I agree with Daniil that having the "required" flag is also unnecessary. @NamedParam seems like it should be assumed. I understand the use case of @NamedDelegate but again, it adds complexity. Ideally you would only need one annotation to the method for a sensible default case. -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: [ANN] Announcing CodeNarc 1.1
I'll have to try this out! Is the IntelliJ plugin still under development? -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: Start a forum - continued
I personally use Nabble. It does not compare to a real forum system. The formatting constantly breaks, you can't mention users, embed media, embed code... the list goes on and on. -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Re: Start a forum - continued
Hi Jochen, I would like to once again stress the flow you can expect with Discourse. You sign up one time, and check a box that you want to receive emails. You will receive emails for every new post, and you can reply straight from email. In this it is exactly like a mailing list and would integrate with your workflow perfectly, while offering the option to use a feature rich forum for those who want it. Conversations can take place entirely within emails. Remember, this forum software was developed by people who are used to mailing lists, and they take this behavior into account. Having the forum send something to the mailing list would just help promote the forum, it is not meant for users to be able to interact with. I think actually a weekly digest sent to the mailing list would be better. You can read more about Discourse's policies on free hosting for open source projects here: https://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/ -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html
Start a forum - continued
Once again I would like to bring up the idea of starting a forum using Discourse. In particular, I would like to highlight some of the features Discourse offers that are relevant to the mailing list, for those concerned about making the switch: - Supports replying to conversations and PMs via email out of the box - Can be configured to allow starting conversations and private messages via email - Support SSO via numerous providers, so no need to create a separate account Discourse inherits all of the functionality of the mailing list (some assembly required), and on top of that offers all the modern features you would expect from a forum. It's free and it's open source. The Discourse team will even offer free hosting and setup for open source projects like Groovy. Many other projects like Kotlin utilize this system. As for the problem of having "too many channels to manage" it would be feasible to set up the forums to alert mailing list users that a new topic has been started. This would help bridge the gap between the two platforms. Many community members I have talked to would like a forum. If you agree, please make your voice heard by responding. There is one problem left to tackle with a forum, and that is Apache policy. According to Paul King, "apache mandates the use of their own mailing lists for all official discussions" although having a forum is of course allowed. To have an official forum, we'd need "Apache approval" which presents "significant obstacles." In my mind, this makes the path forward obvious: we need a public forum, but it NEEDS support from higher-ups on the Groovy team as well. It needs to be advertised and linked to from the groovy site and things of that nature. It should be pushed as much as possible. Otherwise, it seems nearly pointless. Once again I think this can only happen with a large amount of support from the community, so please chime in.
