It's worth noting that Discourse will host open source projects for
free: 
http://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-community-friendly-github-projects/
--
Woody Gilk
http://about.me/shadowhand


On Sun, Jul 10, 2016 at 7:31 AM, Daniel Plainview
<daniel.pla...@gmail.com> wrote:
>> For one thing: This mailinglist is already available via a forum-like
>> interface at GoogleGroups.
>
> I find this interface not user-friendly.
>
> Email messages are not really supposed to be parsed automatically,
> they are supposed to be "parsed" by human beings in the first place.
> I think it's fundamental flaw of mailing lists.
> Some features can be implemented only with agreements: tags, quoting, etc.
>
> It's like C++ interfaces, if you want. Yes, they are "enough" for OOP
> modelling.
> However, we know that language-based (Java, PHP, ...) interfaces are more
> handy.
> Clarity of intent is the thing.
>
> On Sunday, June 26, 2016 at 2:36:01 PM UTC+3, Andreas Heigl wrote:
>>
>> Hi Alexander.
>>
>> Perhaps you have seen the thread "[IDEA] Transition  Google Groups to
>> Slack/Gitter/Discourse"
>> (https://groups.google.com/forum/#!msg/php-fig/uN0EykvQkAA/rCHFHLvRAwAJ).
>>
>> That thread is also about moving the current GoogleGroup to a different
>> medium. And during the discussion the move to a forum was discussed as well.
>>
>> For one thing: This mailinglist is already available via a forum-like
>> interface at GoogleGroups.
>>
>> And besides that: I've asked a questions there that are still not
>> answered, but I might as well ask it here again:
>>
>>> So to get down to the point: What actually is the issue with the
>>> mailinglist/GoogleGroups? Is it really the user-base? Or is it a certain
>>> "messyness"? Perhaps we can first try to analyze what exactly the issue
>>> is, before we throw some technology at it.
>>
>>
>> And no, in my eyes the points you raised are not answers to that question
>> but raise the question why you want others to change their habit so that you
>> do not need to change yours.
>> Am Samstag, 25. Juni 2016 16:59:16 UTC+2 schrieb Alexander Makarov:
>>>
>>> Mailing list has many issues:
>>>
>>> 1. Really hard to read conversations since everything is cited and
>>> different mail clients are doing it differently.
>>
>> With a decently configured email-client that works out pretty good.
>>
>>>
>>> 2. Everything is a big sticky pile of mud. In a forum we'll be able to
>>> have separate categories for separate proposals so it will be **much**
>>> easier to focus.
>>
>> That's already available via threading which works fine in the
>> GoogleGroups web-interface and works also fine in my email-clients.
>>
>>>
>>> 3. No permissions management. In a forum we'll be able to have a "voting
>>> members" group with which has permission to post to voting threads.
>>
>> Why do you want a permission management? The point is that everyone can
>> see everything. There's nothing to hide.
>> I'm with you though that it might be an idea to have separate mailinglists
>> for public announcements and for internal affairs so people not interested
>> in the internal affairs do not need to dig through tons of stuff to find the
>> information they want. But that's not something a forum would solve.
>>
>>>
>>> 4. Hard to browse history. In a forum it's all structured so it's much
>>> easier. No need to dig much.
>>
>> If you would have used the search on GoogleGroups you would have found at
>> least two other threads that where discussing movement of the mailinglist to
>> a different medium. So it doesn't seem to be as easy in a forum as you said.
>>
>>>
>>>
>>> These are only the surface, I'm sure other members have their own
>>> concerns about mailing lists.
>>>
>>> What I propose: archive mailing list, create a forum with a good
>>> structure. Choose one which has ability to work as a mailing list so people
>>> who love MLs would be happy.
>>
>>
>> Fine, then we're already done. The GoogleGroup is a forum which also works
>> as a mailinglist. Or the other way around? So what's all this fuss about?
>>
>> Cheers
>>
>> Andreas
>
> --
> You received this message because you are subscribed to the Google Groups
> "PHP Framework Interoperability Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to php-fig+unsubscr...@googlegroups.com.
> To post to this group, send email to php-fig@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/75112073-b7a8-45d7-b6e5-d800245c9615%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "PHP 
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to php-fig+unsubscr...@googlegroups.com.
To post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CAGOJM6JA9KAwX-gnP6LuA28T9TFEgMeB79j15oYVs%3DECjvVGow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
  • Re: Switch to... Andreas Heigl
    • Re: Swit... 'Alexander Makarov' via PHP Framework Interoperability Group
    • Re: Swit... Robert Korulczyk
      • Re: ... Alessandro Pellizzari
        • ... 'Alexander Makarov' via PHP Framework Interoperability Group
          • ... Alessandro Pellizzari
        • ... Robert Korulczyk
          • ... Stefano Torresi
            • ... 'Alexander Makarov' via PHP Framework Interoperability Group
    • Re: Swit... Daniel Plainview
      • Re: ... Woody Gilk
        • ... 'scott molinari' via PHP Framework Interoperability Group
  • Re: Switch to... Dracony
    • Re: Swit... 'scott molinari' via PHP Framework Interoperability Group
  • Re: Switch to... Michael Cullum
    • Re: Swit... 'Alexander Makarov' via PHP Framework Interoperability Group
    • Re: Swit... 'scott molinari' via PHP Framework Interoperability Group
      • Re: ... Michael Cullum
        • ... 'scott molinari' via PHP Framework Interoperability Group
          • ... Stephen Rees-Carter
            • ... 'scott molinari' via PHP Framework Interoperability Group

Reply via email to