From: Jacob Marble <jacobmarble@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] mailing list migration (was: development flow)
Date: Fri, 18 Sep 2009 15:19:32 -0600 [thread overview]
Message-ID: <5161afcd0909181419j24a75484n27791a65e52ac9f1@mail.gmail.com> (raw)
In-Reply-To: <5161afcd0909181414kd78329dvc2617cacff43c591@mail.gmail.com>
On Fri, Sep 18, 2009 at 3:14 PM, Jacob Marble <jacobmarble@gmail.com> wrote:
> On Tue, Sep 8, 2009 at 11:54 AM, Marek Lindner <lindner_marek@yahoo.de> wrote:
>> On Wednesday 09 September 2009 00:01:46 Andrew Lunn wrote:
>>> The steps as i see it:
>>>
>>> 1) Make a decision about which list server to use.
>>
>> I think as soon as we havea short list of options we can make the decision. At
>> the moment I see no need/desire for a long discussion. :-)
>>
>>
>>> 2) Contact the sysadmin and ask for a list to be setup.
>>
>> Volunteer needed here.
>
> I would like to volunteer.
>
>>
>>
>>> 3) Export the list of subscribers.
>>
>> That will be me.
>>
>>
>>> 4) Import the list of subscribers.
>>
>> Probably the same volunteer.
>>
>>
>
> I don't have a server that would work for this, but I think it would
> be nice to find a service that hosts FOSS projects for free, but
> normally charges for the service. That way, no one in the batman
> project has to worry about servers failing/upgrading/migrating/etc.
>
> The first example that comes to mind is XMission because they are my
> ISP. They use Mailman (same as we're using now), so we might even be
> able to transfer the messages on the current Mailman server to the new
> one. I'm not at all familiar with Mailman, but I'll call them today
> and see what they say.
>
> http://mailman.xmission.com/
>
> Jake
>
I just got off the phone with a sales guy at XMission. He says
mailing lists are US$3/month. I can cover this.
How does that sound, Marek? Do you have something else in mind?
next prev parent reply other threads:[~2009-09-18 21:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 1:36 [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Linus Lüssing
2009-08-30 1:59 ` Linus Lüssing
2009-08-30 7:37 ` Andrew Lunn
2009-08-30 20:23 ` Simon Wunderlich
2009-08-31 5:26 ` [B.A.T.M.A.N.] development flow Marek Lindner
2009-08-31 5:50 ` Andrew Lunn
2009-09-01 18:47 ` Marek Lindner
2009-09-02 6:18 ` Andrew Lunn
2009-09-03 6:06 ` Marek Lindner
2009-09-08 16:01 ` Andrew Lunn
2009-09-08 17:54 ` [B.A.T.M.A.N.] mailing list migration (was: development flow) Marek Lindner
2009-09-18 21:14 ` Jacob Marble
2009-09-18 21:19 ` Jacob Marble [this message]
2009-09-19 7:59 ` Andrew Lunn
2009-09-28 3:29 ` Jacob Marble
2009-09-28 3:31 ` Jacob Marble
2009-09-28 5:03 ` Andrew Lunn
2009-09-28 6:12 ` Jacob Marble
2009-09-29 5:06 ` Jacob Marble
2009-09-29 5:25 ` Andrew Lunn
2009-09-29 9:19 ` Marek Lindner
2009-09-29 15:56 ` Jacob Marble
2009-09-29 16:14 ` Sven Eckelmann
2009-09-30 5:39 ` Jacob Marble
2009-09-30 19:27 ` Marek Lindner
2009-09-29 15:38 ` Jacob Marble
2009-08-30 19:55 ` [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Simon Wunderlich
2009-08-30 20:15 ` Andrew Lunn
2009-08-30 21:47 ` Linus Lüssing
2009-08-31 5:28 ` Andrew Lunn
2009-09-01 20:47 ` Linus Lüssing
2009-09-04 18:58 ` Linus Lüssing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5161afcd0909181419j24a75484n27791a65e52ac9f1@mail.gmail.com \
--to=jacobmarble@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).