I also think it's important to note that just because things like mailman have existed for years and will continue to exist for years does not mean they're always the best tool for the job. As open source developers it's also important to be _open_ to change, and always to evaluate what the best tool to get the job done is. A false dichotomy for sure, but: can I continue running CentOS 5 or Solaris 10? Sure, but it probably will stagnate me from doing what I want to do. It's like doing "DevOps" by using clusterssh to run commands on all your servers instead of a config management tool.
Greg is right--many would-be new developers _are_ turned off from things like mailing lists. I know because I used to be turned off by them--and to a certain extent, still am. There's nothing worse than finding a `-dev` list on google for an issue you're having and not being able to find or indeed _know_ if there's a response to a thread: Forum-type solutions don't have that issue, and as long as they support email, even if it's not "first", then I think any distruption in workflow, if limited, is worth it to encourage new voices. I recently graduated from University, and know a lot of people that wouldn't step near a mailing list for development--and would be especially reluctant to contribute to them. To many "next gen" developers, email is not the workflow they will choose to adopt, and sticking with listservs because they have always been and will always be is not a good enough reason in my opinion. (Please note this is mostly random rambling on my behalf, and entirely opinion based to attempt to give insight from someone who's only recently joined the whole process) On Fri, Nov 3, 2017 at 1:45 PM Greg Sutcliffe <g...@emeraldreverie.org> wrote: > One more thought occurred to me while I was out on the nursery pickup, so > I'll drop here before I bow out for the weekend. > > Lukas, I think part of our disagreement is our different goals. As I > highlighted in the last mail, users behave differently to devs. These days > I consider myself more user than dev (when did I last contribute code), so > I have a different world view. > > You want to protect a tried and trusted workflow, likely used by many here > - that's fine. My job is to promote and develop the user community, so I > see room for improvement. > > Here's the catch though... Our future devs, as a community, *come from* > the user community. If we don't focus there, then we risk stagnating the > dev community too. > > I won't deny this change is a larger net benefit for the user group. The > case for the dev community is harder to argue. But there *is* benefit, and > compared to running a list (for dev) and a forum (for users) I think the > better argument is to use a forum for both. > > I don't expect to convince everyone, so this is going to come down to a > group decision - but not for a while yet. We need to do more tests. > > Have a great weekend all, > Greg > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
