2015-03-02 11:40 GMT+01:00 Sergei Ivanov <sergei_iva...@mail.ru>: > 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. >
For 1, just checked and you can indeed have a global view of the issues in an organization (you must switch context for that). Example for jenkinsci: https://github.com/pulls?user=jenkinsci For 3, we indeed currently receive all the JIRA notifications, and so on. IMO this is close to a must if we want to stay as a whole and not just some repos patched together wo any form of consistency. I'll check if we can do more. For 2 I agree this should be sufficient, as our main doc is currently published as maven-site, this cannot really be an issue. Don't think we currently have really used wiki pages. -- Baptiste [1] https://github.com/blog/959-issues-dashboard-for-organizations > -- > Sergei > > > > Monday, 2 March 2015 10:32 +0000 from Lennart Jörelid < > lennart.jore...@gmail.com>: > 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? > * Is the GitHub issue tracker sufficient for our needs? If not - what is > missing? > * Is the GitHub Wiki documentation feature sufficient for our needs? Can > it publish Maven site documentation? > * Is the GitHub notification feature sufficient for our needs? Or do we > need another location for actual mailing lists which are > Discussion-oriented and not related to a particular commit? > > 2015-03-02 11:06 GMT+01:00 Sergei Ivanov < sergei_iva...@mail.ru > : > >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 > product team, I am pretty sure they will be listening to the voice of a > large developer community. > >-- > >Sergei > >> > >>Monday, 2 March 2015 09:54 +0000 from Baptiste Mathus < > bmat...@batmat.net >: > >> > >>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 < sergei_iva...@mail.ru > : > >>>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 +0000 from Trygve Laugstøl < > tryg...@codehaus.org >: > >>>> > >>>>On Sun, Mar 01, 2015 at 12:14:19AM -0800, Dan Tran wrote: > >>>>> Apache process may send some new potential committers away :) > >>>>> > >>>>> +1 for Github, but stay together under on umbrella of org.code.mojo > >>>>> groupId. > >>>>+1 > >>>>The concern with moving to Github is their lack of mailing lists, but > I guess a Google group is the best choice these days. > >>>>> > >>>>> -D > >>>>> > >>>>> btw, i found this https://github.com/codehaus-plexus > >>>>> > >>>>> so we may something similar like that? > >>>>> > >>>>> > >>>>> > >>>>> On Sat, Feb 28, 2015 at 11:26 PM, Tony Chemit < che...@codelutin.com > > wrote: > >>>>> > >>>>> > On Fri, 27 Feb 2015 12:51:18 +0100 > >>>>> > Lennart Jörelid < lennart.jore...@gmail.com > wrote: > >>>>> > > >>>>> > > I second the opinions for moving to GitHub (or Bitbucket) > instead of > >>>>> > > remaining in SVN. > >>>>> > > If doing so, I suggest we reuse as much as possible of the GitHub > >>>>> > > infrastructure - Wiki, Issue Tracker, Mailing lists etc. > >>>>> > > If we are already bound for some major migrations, let's make > the best of > >>>>> > > them - and a Distributed version control system is a > productivity boost. > >>>>> > > > >>>>> > > Also - is there really a point to maintain a particular GroupID > (i.e. > >>>>> > > org.codehaus). > >>>>> > > I belive we could/should move Mojo's development efforts into > the Apache > >>>>> > > umbrella (why have 2 sources of normative plugins - apache and > codehaus) > >>>>> > to > >>>>> > > simplify for users. > >>>>> > > >>>>> > I really like this idea to *merge* mojo projets with maven plugins > one or > >>>>> > something at apache house. > >>>>> > > >>>>> > I guess there is some legal issue about it ? or not ? > >>>>> > > >>>>> > > >>>>> > > >>>>> > -- > >>>>> > Tony Chemit > >>>>> > -------------------- > >>>>> > tél: +33 (0) 2 40 50 29 28 > >>>>> > http://www.codelutin.com > >>>>> > email: che...@codelutin.com > >>>>> > twitter: https://twitter.com/tchemit > >>>>> > > >>>>> > > --------------------------------------------------------------------- > >>>>> > To unsubscribe from this list, please visit: > >>>>> > > >>>>> > http://xircles.codehaus.org/manage_email > >>>>> > > >>>>> > > >>>>> > > >>>>--------------------------------------------------------------------- > >>>>To unsubscribe from this list, please visit: > >>>> http://xircles.codehaus.org/manage_email > >>-- > >>Baptiste <Batmat> MATHUS - http://batmat.net > >>Sauvez un arbre, > >>Mangez un castor ! > -- > -- > +==============================+ > | Bästa hälsningar, > | [sw. "Best regards"] > | > | Lennart Jörelid > | EAI Architect & Integrator > | > | jGuru Europe AB > | Mölnlycke - Kista > | > | Email: l...@jguru.se > | URL: www.jguru.se > | Phone > | (skype): jgurueurope > | (intl): +46 708 507 603 > | (domestic): 0708 - 507 603 > +==============================+nbsp;! > >
