<div dir="ltr"><div class="gmail_extra"><div><div>On Fri, Oct 2, 2015 at 4:04 PM, Berk Hess <span dir="ltr"><<a href="mailto:hess@kth.se" target="_blank">hess@kth.se</a>></span> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>This depends on where we want to keep
information related to how to contribute to Gromacs. If this lives
somewhere else on the wiki, a long blog history is not so
important. We might need to copy parts of useful posts to the wiki
then.<br></div></div></blockquote><div><br></div><div>This is not meant to be a blog or wiki; the goal is to have an interactive chat-like channel where you see who's online, can have ad-hoc or organized discussions, share code, thoughts, ideas in a main or dedicated per-topic discussion streams/channels.</div><div><br></div><div>Additionally, allowing new people to just drop by and ask questions is also important, I believe.</div><div><br></div><div>I have been checking out slack in a sandbox account, whoever is interested can get access by dropping me a mail!</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div>
<br>
Cheers,<br>
<br>
Berk<div><div><br>
<br>
On 10/02/2015 04:00 PM, Szilárd Páll wrote:<br>
</div></div></div><div><div>
<blockquote type="cite">
<div dir="ltr">
<div>I personally think that starting to use a collaborative
platform by severely restricting who can participate partly
defeats the purpose of the new tool. Such a restriction will
severely limit the possibilities for interaction with new
people. Whatever we choose, I think it's crucial to allow wide
participation with as low barrier as possible while ensuring
that the features code-devs want are well-supported.</div>
<div><br>
</div>
<div><br>
</div>
I wonder how important is a saving history for very long
periods?
<div><br>
<div>I see a few use cases:
<div>- Casual and semi-formal dev interaction on various
channels; typically short-term chats, I imagine e.g.
discussing a/some of changes (e.g. switching form gerrit
for more interactivity, starting a quick hangout from
there if needed)</div>
</div>
<div>- Help and support channel for non-core/code devs, e.g.
method developers, people interested in using the code for
their research, infrequent contributors, HPC center
sysadmins, distro maintainers, etc.</div>
<div>- Longer-term planning, decision-making and discussion
e.g. on a planned feature.</div>
<div><br>
</div>
<div>It seems to me that some of this, in particular the first
two do not necessarily need archival (or information could
be dumped from the lack channel when it seems
useful/necessary).</div>
<div><br>
</div>
<div>Cheers,</div>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>--<br>
Szilárd</div>
</div>
<br>
<div class="gmail_quote">On Fri, Oct 2, 2015 at 12:41 AM, Erik
Lindahl <span dir="ltr"><<a href="mailto:erik.lindahl@gmail.com" target="_blank">erik.lindahl@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi,<span>
<div><br>
<div>
<blockquote type="cite">
<div>On 01 Oct 2015, at 23:33, Roland Schulz <<a href="mailto:roland@utk.edu" target="_blank"></a><a href="mailto:roland@utk.edu" target="_blank">roland@utk.edu</a>>
wrote:</div>
<br>
<div>
<div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Oct 1, 2015
at 5:32 AM, Szilárd Páll<span> </span><span dir="ltr"><<a href="mailto:pall.szilard@gmail.com" target="_blank">pall.szilard@gmail.com</a>></span><span> </span>wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div dir="ltr">
<div class="gmail_extra"><span>
<div>
<div>On Wed, Sep 30, 2015 at
4:08 PM, Roland Schulz<span> </span><span dir="ltr"><<a href="mailto:roland@utk.edu" target="_blank"></a><a href="mailto:roland@utk.edu" target="_blank">roland@utk.edu</a>></span><span> </span>wrote:<br>
</div>
</div>
</span>
<div class="gmail_quote"><span>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">There are a
couple see for example:
<div><a href="http://beebom.com/2015/04/slack-alternatives-for-team-communication" target="_blank"></a><a href="http://beebom.com/2015/04/slack-alternatives-for-team-communication" target="_blank">http://beebom.com/2015/04/slack-alternatives-for-team-communication</a></div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>I've seen this list,
unfortunately none of those
listed seemed to offer a great
deal more/better functionality
than slack - except perhaps
HipChat with 25k history
limit, or Pie with no limits
_but_ data lock-in due to
lack of export in the free
version - , but I have to
admit, I only browsed briefly.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I think the pricing structure for
slack is quite bad for us. I think the
10,000 is not sufficient in the medium
term. And it is probably to expensive to
use anything other than their free plan.
And if we hit the limit and can't afford
upgrading, then even if they let us
allow to export data, we would loose all
experience, integration, and training
with that system.</div>
<div><br>
</div>
<div>Bitrix24 has a first paid plan which
might be affordable and a limit which is
probably sufficient even in the medium
term. The free plan is sufficient to
test. </div>
<div><br>
</div>
<div>We might want to ask for some of them
whether they would be willing to offer
us a plan as a academic open-source
project which is discounted. And we
should make sure that the pricing plan
is sustainable for the long term so that
we don't need to switch later.</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</span>
<div>Slack appears to offer educational plans with 85%
discount, which might work.</div>
<div><br>
</div>
<div>To keep the number of accounts manageable, I think we
could do something where active developers (basically
those who frequently commit code) get personal/paid
slack accounts on our tab, and then there are features
where we can invite guest users into open channels so
anybody can participate in those discussions even though
they might not be as active developing.</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Erik</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a>
before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" rel="noreferrer" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a>
or send a mail to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote>
<br>
</div></div></div>
<br>--<br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" rel="noreferrer" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br></div></div>