Looking for maintainer

[Hallski]

Hi all,

It looks like my time for Loudmouth development and maintenance is
going to continue to be very limited. While Loudmouth can be
considered more or less "done" it could still do with both some
internal refactoring as well as addition of more higher level APIs to
make life as an application developer easier.

The Windows port seems to require some work and preferably an update
to build instructions as well as someone who can maintain it since the
platform is quite different from *nix.

Over the last couple of weeks I have moved the infrastructure of
Loudmouth onto more public services (Google Groups, Github and
Lighthouse) to make it easier for a new maintainer to continue to work
on the project.

If anyone feel interested in stepping up to take over Loudmouth
development, please let me know how I can help make the transition.

Best Regards,
Mikael Hallendal

[Kirk Haines]

On Jan 21, 5:55 am, Hallski <mhallen...@gmail.com> wrote:

> If anyone feel interested in stepping up to take over Loudmouth
> development, please let me know how I can help make the transition.

Good day. At Engine Yard, we are currently using Loudmouth to provide
the XMPP communications for the Ruby side of the Vertebra project.
Over the course of implementing this, we have worked on, and continue
to work on the Loudmouth library to fix bugs and implement some new
features, both in the Loudmouth library itself as well as in the
loudmouth-ruby extensions.

So we (and I, specifically) would be interested in taking over
stewardship of Loudmouth. We aren't going to promise tons of devel
time on new features. We'll fix bugs, address the installation
issues, probably pursue some modest new features, and we'll deal with
community patches and community contributed features, handle releases,
etc....

If, in the long term, someone else steps up who wants to pump lots of
hardcore devel time into it, we'll happily look at transfering
stewardship on, but until then, we can keep the project moving forward
towards greater maturity while using it daily in a significant open
source project.

If this sounds like it will work for you and for Loudmouth, let's talk
when you are available about the details. You can find me in the
freenode.net #vertebra and #loudmouth IRC channels, via Google talk at
wyha...@gmail.com, or via email at kha...@engineyard.com.


Thanks Mikael,

Kirk Haines
Developer
Engine Yard
kha...@engineyard.com
irc: wyhaines

[Hallski]

Hi Kirk,

That's great news!

I'll try to get in contact with you over IRC or email within the near
future to sort out the details.

Cheers,
Micke

> wyhai...@gmail.com, or via email at khai...@engineyard.com.

>
> Thanks Mikael,
>
> Kirk Haines
> Developer
> Engine Yard

> khai...@engineyard.com
> irc: wyhaines

[Arc Riley]

Some advice, whoever takes over needs some experience maintaining a community project, ie, understanding that maintaining is more about leading volunteers and working with contributors than anything.

We've already dropped loudmouth for libstrophe because of a lack of this.