That name must have been my largest contribution to the cause so far :)
--
Sergei
>
>Saturday, 14 March 2015 12:43 + from Hervé BOUTEMY
>:
>ok, we have a clear winner: MojoHaus
>(and we'll have a statement like "formerly known as Codehaus Mojo project" on
>our website once migrated)
>I creat
Another idea for a GitHub org that I recently had was a MojoHaus mash-up. That
would have at least some heritage of CodeHaus Mojo brand preserved. A quick
google search reveals that the name is only used on the music scene, so should
be clear to use in software world.
--
Sergei
>
>Tuesday, 10 M
I think the community needs a unique and recognisable name. If CodeHaus is
subject to copyright or any other rights outside of public domain, then we need
a replacement. To please the French people on this list, I was about to suggest
CodeMaison as a replacement for CodeHaus brand, but it looks
IMHO the Apache Maven team should focus on Maven Core, (java)-build
lifecycle plugins, plugin-development tools, transport (SCM, Wagon) and
project-health tools.
There are probably a couple of Codehaus-Mojo plugins which might be
interesting to move Apache Maven (assuming legal issues will
2015-03-02 11:40 GMT+01:00 Sergei Ivanov :
> I believe the answers to 1. and 2. are yes and yes. Maven sites can be
> published to gh-pages, which is separate to the wikis. As for 3. I think it
> requires investigation. There is a need for a mailing list like this, and I
> am not sure if such case
I believe the answers to 1. and 2. are yes and yes. Maven sites can be
published to gh-pages, which is separate to the wikis. As for 3. I think it
requires investigation. There is a need for a mailing list like this, and I am
not sure if such case is covered by the GitHub offering.
--
Sergei
>
Fair point.
I would aim at getting the best of both worlds. If I absolutely *have* to
move to Apache, I would. But GitHub is currently the better infrastructure
and process, I feel.
So ... what do we need which is missing from GitHub presently?
1. Is the GitHub issue tracker sufficient for o
Mailing lists _are_ important. I was not trying to imply that mailing lists
should be dropped, merely stating the fact that the functionality could be
procured elsewhere and plugged into GitHub. If GitHub does not provide enough
flexibility in that respect, then we need to talk to GitHub produ
Even if I agree ML shouldn't be an issue. It's not so unimportant for us as
a developer community. We need a wee bit more than just pushing and
reviewing code.
2015-03-02 9:46 GMT+01:00 Sergei Ivanov :
> Mailing lists are a completely orthogonal feature to the development
> stack. I am struggling
Mailing lists are a completely orthogonal feature to the development stack. I
am struggling to understand why can they not be hosted somewhere else and why
the lack of mailing lists is an impediment to migration to git and GitHub.
--
Sergei
>
>Monday, 2 March 2015 08:38 + from Trygve Laugstø
Hi,
I should say, if Codehaus is no more, GitHub would be my obvious first choice
of an alternative platform.
1. Version control.
SVN is a dinosaur and a major impediment for contributing and integrating
patches. Git provides a much more streamlined workflow from both committer's
and contribu
11 matches
Mail list logo
