Re: CVS access or Project Progress

* Tiger!P <[email protected]> [2007-02-14 18:57]:
> On Wed, Feb 14, 2007 at 05:03:36PM +0100, David Riebenbauer wrote:
> > * Stéphane Bisinger <metal_kj-/[email protected]> [2007-02-14 15:25]:
> > > --- Jayjay <[email protected]> wrote:
> > > > - If that is not possible, should we startup a
> > > > SourceForge project with a 
> > > > few primary maintainers and get the project rolling
> > > > again?
> > > 
> > > Good as a secondo option, IMHO
> > 
> > I played with that thought for quite some time now and I decided to go
> > for it.
> > 
> > You can expect a repository and an updated tarball shortly. Most
> > likely by tomorow evening.
> 
> That's good to hear :-)
> 
> > I will elaborate my plans in another mail.
> 
> Please do :-)

My main motivivation to do this is seeing the situation current
situation that there are more and more patches for centericq floating
around with no release in sight. So that is fixing bugs, reviewing and
applying patches and doing a release from time to time. 

Making centericq more usable in UTF-8 environments is another thing I
want to do. More and more Linux distributions are using UTF-8 as
default encoding. So supporting it should really be done. And I hope
that in the process of doing that problems with other encodings can be
fixed too. It really should work with all of them

When it comes to protocols my main interest is Jabber. Unfortunately
this is the only protocol I have detailed knowledge of. And the only
other protocol I use is ICQ.

This doesn't mean I won't do bugfixes for other protocols it just
won't be my top priority.

When it comes to Jabber I want to make it more standards-compliant.
I think that that will involve throwing out libjabber which doesn't
seem to exist any more out of centericq and replacing it with
something else. I think libgloox would be a good candidate.

Currently you can only have only one account per protocol I think this
is annoying many people including myself. I want to change that.

I also think that centericq could use some ui improvements. Though I
am not talking of radical changes here. The user interface is quite
good and is one of the reasons why I like centericq. But I think small
improvements can be made.

I would like centericq to be more configurable. This is obviously rather low
priority compared to some of the other things, but still something I
want to do some time.
This should include more possibilities to adjust keybindings and maybe
a more flexible configuration file format.



I haven't yet decided which name I will use for that project. And as
far as I know Konst hasn't decided yet if he wants let me use the name
centericq.

Maybe this would be a good point to change the name to something
reflecting the multi-protocol nature of the program a bit better.
"CenterIm" comes to mind. A name that has already been discussed on
this list.


As a version control system I want to use git. I already have imported
the current cvs repository into git and also have my current changes
in there.

The reasons for git are that it has a good repository format, allows
to work with external patches very easily and of course it's
distributed nature.

I plane to have the repository at repo.or.cz.


The work I have until now is mostly some cleanup one the autotools
files and I have applied some patches. Most of them are taken from the
centericq Debian package.

I still have to write up a changelog.


I am still looking for a location where I can use for a wiki and a bug
tracker. Maybe Sourceforge is a good location for that. But I am open
for other suggestions.

Unfortunately I don't have the money to rent my own server/vserver for
that at the moment.


Of course I welcome everyones contributions.

Please let me know what you think about all this




-- 
David Riebenbauer
Jabber: [email protected] - ICQ: 322056002

_______________________________________________
Cicq mailing list
Cicq-xGejAJT2w6wWP6gT/[email protected]
http://mailman.linuxpl.org/mailman/listinfo/cicq
Questions? Check the FAQ first: http://centericq.de/faq/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF043VMM9MqQG0tAARAkjUAJ9HuQ+0OepcMcV9Evq0RhgaC21y8gCgkvx5
2cj6IORJ8CEgLd24WifJrCw=
=RKTY
-----END PGP SIGNATURE-----