Very nice! Thank you! Best Regards, Mohamed Afifi
On Mon, May 1, 2017 at 3:50 PM, Muse M <[email protected]> wrote: > All of your points have been discussed and some of us will prefer > Discourse to generate mailing format. I remember there is an option for > "Mailing > List mode" in Discourse. > > You can trace from this discussion and there were a long separate threads > few months back which you can trace manually. > https://lists.swift.org/pipermail/swift-evolution/ > Week-of-Mon-20170206/031657.html > > On Mon, May 1, 2017 at 8:40 PM, Mohamed Ebrahim Afifi via swift-evolution > <[email protected]> wrote: > >> Thanks for your reply! I think that is very good news that the burden of >> the mailing list is so obvious for everyone! >> >> I think Github issues would be better though, the community is used to it >> and it makes more sense as it needs almost no configurations, no operation >> costs or maintenance. If the community decided to move to it we can move to >> it immediately, we don't need to wait. It is a natural next step since the >> proposals are maintained there and Swift itself is maintained there. >> >> >> Do you have a link to that discussion? >> >> >> >> >> Best Regards, >> Mohamed Afifi >> >> On Mon, May 1, 2017 at 1:33 PM, Adrian Zubarev < >> [email protected]> wrote: >> >>> Hi there, >>> >>> you’re a bit too late. A forum will come at some point (Discourse). >>> >>> Best regards, >>> >>> >>> >>> -- >>> Adrian Zubarev >>> Sent with Airmail >>> >>> Am 1. Mai 2017 um 13:30:55, Mohamed Ebrahim Afifi via swift-evolution ( >>> [email protected]) schrieb: >>> >>> Hi, >>> >>> This is actually not a proposal to improve Swift, it is actually a >>> proposal to improve the way we use it to improve Swift. :) >>> >>> It is extremely hard to monitor discussions going over e-mails. >>> >>> 1. I always get lost between e-mails especially if there are so many >>> replies >>> 2. It is extremely hard to reach the original idea/first e-mail. >>> 3. New people (like me) usually get lost between e-mails and only >>> focus on their own idea and don't care about other's ideas because for >>> example, I don't know how to reply to an idea if I'm not subscribed to >>> the >>> mailing list. In other words, It’s not a system that encourages follow-up >>> actions. >>> 4. You can not browse subjects and all replies in one place. >>> 5. You cannot follow a specific topic and ignore others. >>> >>> That was the problem! >>> >>> My suggestion is to move all discussions from this mailing list to >>> GitHub issues. For the following reasons. >>> >>> 1. Easier to browse all topics. >>> 2. You can see open topics and closed topics. So, if a topic is done >>> we can close it. >>> 3. You can subscribe to a topic and follow all replies and reply. >>> 4. Markdown support. Currently, I see people create a markdown page >>> on Github and send a link to it on the mailing list. But having the >>> markdown inline in the topic is a great benefit. Also, replies can be in >>> markdown as well. >>> 5. It's closer to Proposals (Since we already using Github for >>> tracking proposals why don't we use it also to track pitching ideas). >>> People like to have everything gathered together in one place and don't >>> need to remember the Github repo and mailing list. >>> 6. Github has https://developer.github.com/v3/issues/ >>> >>> >>> I think using Github issues instead of the mailing lists will increase >>> the engagement of the Swift community with proposals. >>> >>> >>> Best Regards, >>> Mohamed Afifi >>> _______________________________________________ >>> swift-evolution mailing list >>> [email protected] >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> >>> >> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution >> >> >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
