From jgb at bitergia.com Thu Feb 1 07:59:25 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Thu, 01 Feb 2018 08:59:25 +0100 Subject: [GrimoireLab-disc] New release: elasticgirl.30 Message-ID: <1517471965.2786.92.camel@bitergia.com> Hi all, We have a new release of GrimoireLab [1]. Well, in fact we have had several, since elasticgirl.29, which was the latest one with pypi packages, but they have been minor fixes. This release is intended to provide complete support for Elasticsearch and Kibiter/Kibana 6.x (5.x are still supported as well). Please, check it, and open issue reports if you find any problem. This is also the release that we intend to demonstrate during CHAOSSCon/GrimoireCon, on Friday. The corresponding packages have been uploaded to pypi (so they're installable with pip). I've tested most of the examples in the GrimoireLab Tutorial [2] with this new release, and everything seems to work. This release of pypi packages was generated with docker containers, to ensure platform independence. This is still WIP, although it is getting more mature. If you want to use or help to debug the new containers, have a look at [3] You also have updated containers in DockerHub, which you can pull and run straight away: grimoirelab/factory, grimoirelab/installed, grimoirelab/full. More info about them also in [3]. At the end of this message, the list of new stuff, from the NEWS file [4] (in this case, for elasticgirl.29.1 to elasticgirl.30). [1] https://github.com/chaoss/grimoirelab/tree/master/releases [2] https://grimoirelab.gitbooks.io/tutorial [3] https://github.com/chaoss/grimoirelab/tree/master/docker [4] https://github.com/chaoss/grimoirelab/blob/master/releases/NEWS Saludos, Jesus. -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From jgb at bitergia.com Mon Feb 5 17:44:59 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Mon, 05 Feb 2018 18:44:59 +0100 Subject: [GrimoireLab-disc] CHAOSS twitter channel Message-ID: <1517852699.3182.103.camel@bitergia.com> The Twitter channel for CHAOSS is in operation. Follow us!!!! https://twitter.com/CHAOSSproj (and retweet us, if you feel like that ;-) ) And remember, GrimoireLab too: https://twitter.com/GrimoireLab Saludos, Jesus -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From acs at bitergia.com Wed Feb 7 21:43:49 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 07 Feb 2018 22:43:49 +0100 Subject: [GrimoireLab-disc] Proposal (new repository) Hatstall Message-ID: <1518039829.4306.22.camel@bitergia.com> Hi all, I have a proposal for a new repository in GrimoireLab: Hatstall. Name: Hatstall Description:?Hatstall is a web interface for SortingHat databases developed mainly with Django. Long Description: Dealing with contributors with multi-identities in a development community is an issue in order to get the right metrics about their contributions in the whole project. For example: * they might be using several usernames in the same data source (i.e. different emails for git commits) * to get a whole view, you need to take into account their contribution in different data sources (git, issues, chats, etc.). You need to merge multiple usernames under a single unique identity * they might be working for several organizations during project life SortingHat is the GrimoireLab tool to deal with all that stuff, but it's CLI might not be very intuitive. So, the learning curve is high, and it takes a long time for a non-tech user to give the right information to the right identity. So, Hatstall tries to make easier to deal with multi-identities management in development communities. Current repository:?https://github.com/acs/django-hatstall Notes: In a preliminary review, Hatstall needs pip packaging, and better testing. Proposal: To move the current repository to chaoss/grimoirelab-hatstall with a README.md that clearly states: "Module in the process of joining GrimoireLab. Issues pending:" (and a list of issues with the formal problems that need to be fixed (for now, those mentioned in the "Notes" section above). Any feedback is appreciated. Cheers -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From jgb at bitergia.com Wed Feb 7 23:34:16 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Thu, 08 Feb 2018 00:34:16 +0100 Subject: [GrimoireLab-disc] Proposal (new repository) Hatstall In-Reply-To: <1518039829.4306.22.camel@bitergia.com> References: <1518039829.4306.22.camel@bitergia.com> Message-ID: <1518046456.3182.312.camel@bitergia.com> +1 Jesus On Wed, 2018-02-07 at 22:43 +0100, Alvaro del Castillo wrote: > Hi all, > > I have a proposal for a new repository in GrimoireLab: Hatstall. > > Name: Hatstall > > Description: Hatstall is a web interface for SortingHat databases > developed mainly with Django. > > Long Description: > > Dealing with contributors with multi-identities in a development > community is an issue in order to get the right metrics about their > contributions in the whole project. For example: > > * they might be using several usernames in the same data source (i.e. > different emails for git commits) > * to get a whole view, you need to take into account their > contribution > in different data sources (git, issues, chats, etc.). You need to > merge > multiple usernames under a single unique identity > * they might be working for several organizations during project life > SortingHat is the GrimoireLab tool to deal with all that stuff, but > it's CLI might not be very intuitive. So, the learning curve is high, > and it takes a long time for a non-tech user to give the right > information to the right identity. > > So, Hatstall tries to make easier to deal with multi-identities > management in development communities. > > Current repository: https://github.com/acs/django-hatstall > > Notes: In a preliminary review, Hatstall needs pip packaging, and > better testing. > > Proposal: > > To move the current repository to chaoss/grimoirelab-hatstall with a > README.md that clearly states: "Module in the process of joining > GrimoireLab. Issues pending:" (and a list of issues with the formal > problems that need to be fixed (for now, those mentioned in the > "Notes" > section above). > > Any feedback is appreciated. > > Cheers > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From jsmanrique at gmail.com Thu Feb 8 09:54:01 2018 From: jsmanrique at gmail.com (Jose Manrique Lopez de la Fuente) Date: Thu, 8 Feb 2018 10:54:01 +0100 Subject: [GrimoireLab-disc] Proposal (new repository) Hatstall In-Reply-To: <1518046456.3182.312.camel@bitergia.com> References: <1518039829.4306.22.camel@bitergia.com> <1518046456.3182.312.camel@bitergia.com> Message-ID: +1 (but I am little biased here. I started the development in Flask some time ago and my good friend ?lvaro with the help of some colleagues ported it to something more "robust" like Django) --- Manrique 2018-02-08 0:34 GMT+01:00 Jesus M. Gonzalez-Barahona : > +1 > > Jesus > > On Wed, 2018-02-07 at 22:43 +0100, Alvaro del Castillo wrote: > > Hi all, > > > > I have a proposal for a new repository in GrimoireLab: Hatstall. > > > > Name: Hatstall > > > > Description: Hatstall is a web interface for SortingHat databases > > developed mainly with Django. > > > > Long Description: > > > > Dealing with contributors with multi-identities in a development > > community is an issue in order to get the right metrics about their > > contributions in the whole project. For example: > > > > * they might be using several usernames in the same data source (i.e. > > different emails for git commits) > > * to get a whole view, you need to take into account their > > contribution > > in different data sources (git, issues, chats, etc.). You need to > > merge > > multiple usernames under a single unique identity > > * they might be working for several organizations during project life > > SortingHat is the GrimoireLab tool to deal with all that stuff, but > > it's CLI might not be very intuitive. So, the learning curve is high, > > and it takes a long time for a non-tech user to give the right > > information to the right identity. > > > > So, Hatstall tries to make easier to deal with multi-identities > > management in development communities. > > > > Current repository: https://github.com/acs/django-hatstall > > > > Notes: In a preliminary review, Hatstall needs pip packaging, and > > better testing. > > > > Proposal: > > > > To move the current repository to chaoss/grimoirelab-hatstall with a > > README.md that clearly states: "Module in the process of joining > > GrimoireLab. Issues pending:" (and a list of issues with the formal > > problems that need to be fixed (for now, those mentioned in the > > "Notes" > > section above). > > > > Any feedback is appreciated. > > > > Cheers > > > -- > Bitergia: http://bitergia.com > /me at Twitter: https://twitter.com/jgbarah > > _______________________________________________ > Grimoirelab-discussions mailing list > Grimoirelab-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/grimoirelab-discussions > -- [image: Jos? Manrique L?pez de la Fuente on about.me] Jos? Manrique L?pez de la Fuente about.me/jsmanrique -------------- next part -------------- An HTML attachment was scrubbed... URL: From boris at chrysalice.org Thu Feb 8 10:43:37 2018 From: boris at chrysalice.org (Boris Baldassari) Date: Thu, 8 Feb 2018 11:43:37 +0100 Subject: [GrimoireLab-disc] Proposal (new repository) Hatstall In-Reply-To: <1518039829.4306.22.camel@bitergia.com> References: <1518039829.4306.22.camel@bitergia.com> Message-ID: Le 07/02/2018 ? 22:43, Alvaro del Castillo a ?crit?: > Hi all, Hi, > I have a proposal for a new repository in GrimoireLab: Hatstall. +1 ! We saw the presentation at chaoss con, it's cool! :-) -- boris > Name: Hatstall > > Description:?Hatstall is a web interface for SortingHat databases > developed mainly with Django. > > Long Description: > > Dealing with contributors with multi-identities in a development > community is an issue in order to get the right metrics about their > contributions in the whole project. For example: > > * they might be using several usernames in the same data source (i.e. > different emails for git commits) > * to get a whole view, you need to take into account their contribution > in different data sources (git, issues, chats, etc.). You need to merge > multiple usernames under a single unique identity > * they might be working for several organizations during project life > SortingHat is the GrimoireLab tool to deal with all that stuff, but > it's CLI might not be very intuitive. So, the learning curve is high, > and it takes a long time for a non-tech user to give the right > information to the right identity. > > So, Hatstall tries to make easier to deal with multi-identities > management in development communities. > > Current repository:?https://github.com/acs/django-hatstall > > Notes: In a preliminary review, Hatstall needs pip packaging, and > better testing. > > Proposal: > > To move the current repository to chaoss/grimoirelab-hatstall with a > README.md that clearly states: "Module in the process of joining > GrimoireLab. Issues pending:" (and a list of issues with the formal > problems that need to be fixed (for now, those mentioned in the "Notes" > section above). > > Any feedback is appreciated. > > Cheers > From me at olblak.com Thu Feb 8 12:01:31 2018 From: me at olblak.com (Olblak) Date: Thu, 08 Feb 2018 13:01:31 +0100 Subject: [GrimoireLab-disc] Proposal (new repository) Hatstall In-Reply-To: References: <1518039829.4306.22.camel@bitergia.com> Message-ID: <1518091291.4011943.1263899152.3C710954@webmail.messagingengine.com> It sounds great --- -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Thu, Feb 8, 2018, at 11:43 AM, Boris Baldassari wrote: > Le 07/02/2018 ? 22:43, Alvaro del Castillo a ?crit?: > > Hi all, > Hi, > > > I have a proposal for a new repository in GrimoireLab: Hatstall. > +1 ! We saw the presentation at chaoss con, it's cool! :-) > > -- > boris > > > > Name: Hatstall > > > > Description:?Hatstall is a web interface for SortingHat databases > > developed mainly with Django. > > > > Long Description: > > > > Dealing with contributors with multi-identities in a development > > community is an issue in order to get the right metrics about their > > contributions in the whole project. For example: > > > > * they might be using several usernames in the same data source (i.e. > > different emails for git commits) > > * to get a whole view, you need to take into account their contribution > > in different data sources (git, issues, chats, etc.). You need to merge > > multiple usernames under a single unique identity > > * they might be working for several organizations during project life > > SortingHat is the GrimoireLab tool to deal with all that stuff, but > > it's CLI might not be very intuitive. So, the learning curve is high, > > and it takes a long time for a non-tech user to give the right > > information to the right identity. > > > > So, Hatstall tries to make easier to deal with multi-identities > > management in development communities. > > > > Current repository:?https://github.com/acs/django-hatstall > > > > Notes: In a preliminary review, Hatstall needs pip packaging, and > > better testing. > > > > Proposal: > > > > To move the current repository to chaoss/grimoirelab-hatstall with a > > README.md that clearly states: "Module in the process of joining > > GrimoireLab. Issues pending:" (and a list of issues with the formal > > problems that need to be fixed (for now, those mentioned in the "Notes" > > section above). > > > > Any feedback is appreciated. > > > > Cheers > > > > _______________________________________________ > Grimoirelab-discussions mailing list > Grimoirelab-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/grimoirelab-discussions From jgb at bitergia.com Tue Feb 13 23:42:46 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Wed, 14 Feb 2018 00:42:46 +0100 Subject: [GrimoireLab-disc] Repositories moved to CHAOSS Message-ID: <1518565366.11342.17.camel@bitergia.com> Almost all the repositories have already been moved to the CHAOSS GitHub organization. Please, let me know in case of problems. Please remember that we're using an issue for tracking the process: https://github.com/chaoss/grimoirelab/issues/47 There is a new README in the main GrimoireLab repo with the list of repos (well, in fact right now is still a pull request): https://github.com/chaoss/grimoirelab/pull/66 Saludos, Jesus. -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From acs at bitergia.com Wed Feb 14 00:54:55 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 14 Feb 2018 01:54:55 +0100 Subject: [GrimoireLab-disc] Repositories moved to CHAOSS In-Reply-To: <1518565366.11342.17.camel@bitergia.com> References: <1518565366.11342.17.camel@bitergia.com> Message-ID: <1518569695.11551.64.camel@bitergia.com> El mi?, 14-02-2018 a las 00:42 +0100, Jesus M. Gonzalez-Barahona escribi?: > Almost all the repositories have already been moved to the CHAOSS > GitHub organization. Please, let me know in case of problems. Please > remember that we're using an issue for tracking the process: > > https://github.com/chaoss/grimoirelab/issues/47 > > There is a new README in the main GrimoireLab repo with the list of > repos (well, in fact right now is still a pull request): > > https://github.com/chaoss/grimoirelab/pull/66 Merged! > > Saludos, > > Jesus. > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From jgb at bitergia.com Wed Feb 21 11:39:08 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Wed, 21 Feb 2018 12:39:08 +0100 Subject: [GrimoireLab-disc] Proposal for new general committer: Valerio Cosentino Message-ID: <1519213148.18395.32.camel@bitergia.com> Hi all, This message is to propose Valerio Cosentino (in CC) as new general committer for GrimoireLab. Valerio has been contributing for several months to several components (mainly Perceval and Elk, but also in some others), and is in my opinion a reliable developer. Have a look at his activity in his personal dashboard: https://chaoss.biterg.io/goto/ab2a8e55b3f4a505b1ddc8afae8c8ae2 Please, vote on this proposal, or ask for more information if needed. Reminder: anyone in this list can express their opinion, and is welcome to do so, but only votes by current general committers will be definite to make a decission. Saludos, Jesus. -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From sduenas at bitergia.com Wed Feb 21 11:40:10 2018 From: sduenas at bitergia.com (Santiago =?ISO-8859-1?Q?Due=F1as?=) Date: Wed, 21 Feb 2018 12:40:10 +0100 Subject: [GrimoireLab-disc] Proposal for new general committer: Valerio Cosentino In-Reply-To: <1519213148.18395.32.camel@bitergia.com> References: <1519213148.18395.32.camel@bitergia.com> Message-ID: <1519213210.3689.0.camel@bitergia.com> El mi?, 21-02-2018 a las 12:39 +0100, Jesus M. Gonzalez-Barahona escribi?: > Hi all, > > This message is to propose Valerio Cosentino (in CC) as new general > committer for GrimoireLab. Valerio has been contributing for several > months to several components (mainly Perceval and Elk, but also in > some > others), and is in my opinion a reliable developer. > > Have a look at his activity in his personal dashboard: > > https://chaoss.biterg.io/goto/ab2a8e55b3f4a505b1ddc8afae8c8ae2 > > > Please, vote on this proposal, or ask for more information if needed. > > Reminder: anyone in this list can express their opinion, and is > welcome > to do so, but only votes by current general committers will be > definite > to make a decission. +1 > > Saludos, > > Jesus. > From jgb at bitergia.com Wed Feb 21 12:02:14 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Wed, 21 Feb 2018 13:02:14 +0100 Subject: [GrimoireLab-disc] [Results] Proposal (new repository) Hatstall In-Reply-To: <1518039829.4306.22.camel@bitergia.com> References: <1518039829.4306.22.camel@bitergia.com> Message-ID: <1519214534.18395.37.camel@bitergia.com> Summary of results (counting the proposal as +1 by the proposer): +1: 4 votes (3 are general commmitters) "It sounds great": 1 vote ;-) So, the proposal passes. We will move the crepo to the CHAOSS GitHub organization, as "grimoirelab-chaoss", as soon as possible. Saludos, Jesus. On Wed, 2018-02-07 at 22:43 +0100, Alvaro del Castillo wrote: > Hi all, > > I have a proposal for a new repository in GrimoireLab: Hatstall. > > Name: Hatstall > > Description: Hatstall is a web interface for SortingHat databases > developed mainly with Django. > > Long Description: > > Dealing with contributors with multi-identities in a development > community is an issue in order to get the right metrics about their > contributions in the whole project. For example: > > * they might be using several usernames in the same data source (i.e. > different emails for git commits) > * to get a whole view, you need to take into account their > contribution > in different data sources (git, issues, chats, etc.). You need to > merge > multiple usernames under a single unique identity > * they might be working for several organizations during project life > SortingHat is the GrimoireLab tool to deal with all that stuff, but > it's CLI might not be very intuitive. So, the learning curve is high, > and it takes a long time for a non-tech user to give the right > information to the right identity. > > So, Hatstall tries to make easier to deal with multi-identities > management in development communities. > > Current repository: https://github.com/acs/django-hatstall > > Notes: In a preliminary review, Hatstall needs pip packaging, and > better testing. > > Proposal: > > To move the current repository to chaoss/grimoirelab-hatstall with a > README.md that clearly states: "Module in the process of joining > GrimoireLab. Issues pending:" (and a list of issues with the formal > problems that need to be fixed (for now, those mentioned in the > "Notes" > section above). > > Any feedback is appreciated. > > Cheers > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From jgb at bitergia.com Wed Feb 21 12:05:30 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Wed, 21 Feb 2018 13:05:30 +0100 Subject: [GrimoireLab-disc] [Results] Proposal (new repository) Bestiary In-Reply-To: <1516963093.32310.11.camel@bitergia.com> References: <1516963093.32310.11.camel@bitergia.com> Message-ID: <1519214730.18395.39.camel@bitergia.com> Summary of results (counting the proposal as +1 by the proposer): +1: 3 votes (3 are general committers) So, the proposal passes. We will move the crepo to the CHAOSS GitHub organization, as "grimoirelab-bestiary", as soon as possible. Saludos, Jesus. On Fri, 2018-01-26 at 11:38 +0100, Jesus M. Gonzalez-Barahona wrote: > Hi all, > > ?lvaro, in CC, has a proposal for a new repository in GrimoireLab: > Bestiary. > > Name: Bestiary > > Description: Tool for managing the Mordred projects.json > configuration > > Long Description: > For knowing about the data sources needed to produce a dashboard, > Mordred is using a file, projects.json, which specifies the urls of > those data sources, and the structure of the projects, as they will > be > shown in the dashboard. Bestiary provides a web-based interface for > maintaining this information in a more user friendly way. It is based > on Django, and maintains its own database with the same information > provided by the projects.json file. It provides this information via > a > simple REST interface, that mordred and other tools could consume. > > Current repository: https://github.com/acs/bestiary > > Notes: In a preliminary review, Bestiary needs a much more complete > README.md file, pip packaging, and better testing. > > Proposal: > > To move the current repository to chaoss/grimoirelab-bestiary with a > README.md that clearly states: "Module in the process of joining > GrimoireLab. Issues pending:" (and a list of issues with the formal > problems that need to be fixed (for now, those mentioned in the > "Notes" > section above). > > Any feedback is appreciated. > > Saludos, > > Jesus. > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From jgb at bitergia.com Wed Feb 21 12:06:16 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Wed, 21 Feb 2018 13:06:16 +0100 Subject: [GrimoireLab-disc] [Results] Proposal (new repository) Hatstall In-Reply-To: <1519214534.18395.37.camel@bitergia.com> References: <1518039829.4306.22.camel@bitergia.com> <1519214534.18395.37.camel@bitergia.com> Message-ID: <1519214776.18395.41.camel@bitergia.com> On Wed, 2018-02-21 at 13:02 +0100, Jesus M. Gonzalez-Barahona wrote: > Summary of results (counting the proposal as +1 by the proposer): > > +1: 4 votes (3 are general commmitters) > "It sounds great": 1 vote ;-) > > So, the proposal passes. We will move the crepo to the CHAOSS GitHub > organization, as "grimoirelab-chaoss", as soon as possible. Ooops. It was: "grimoirelab-hatstall" Jesus. > > Saludos, > > Jesus. > > On Wed, 2018-02-07 at 22:43 +0100, Alvaro del Castillo wrote: > > Hi all, > > > > I have a proposal for a new repository in GrimoireLab: Hatstall. > > > > Name: Hatstall > > > > Description: Hatstall is a web interface for SortingHat databases > > developed mainly with Django. > > > > Long Description: > > > > Dealing with contributors with multi-identities in a development > > community is an issue in order to get the right metrics about their > > contributions in the whole project. For example: > > > > * they might be using several usernames in the same data source > > (i.e. > > different emails for git commits) > > * to get a whole view, you need to take into account their > > contribution > > in different data sources (git, issues, chats, etc.). You need to > > merge > > multiple usernames under a single unique identity > > * they might be working for several organizations during project > > life > > SortingHat is the GrimoireLab tool to deal with all that stuff, but > > it's CLI might not be very intuitive. So, the learning curve is > > high, > > and it takes a long time for a non-tech user to give the right > > information to the right identity. > > > > So, Hatstall tries to make easier to deal with multi-identities > > management in development communities. > > > > Current repository: https://github.com/acs/django-hatstall > > > > Notes: In a preliminary review, Hatstall needs pip packaging, and > > better testing. > > > > Proposal: > > > > To move the current repository to chaoss/grimoirelab-hatstall with > > a > > README.md that clearly states: "Module in the process of joining > > GrimoireLab. Issues pending:" (and a list of issues with the formal > > problems that need to be fixed (for now, those mentioned in the > > "Notes" > > section above). > > > > Any feedback is appreciated. > > > > Cheers > > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From boris at chrysalice.org Wed Feb 21 12:09:10 2018 From: boris at chrysalice.org (Boris Baldassari) Date: Wed, 21 Feb 2018 13:09:10 +0100 Subject: [GrimoireLab-disc] Proposal for new general committer: Valerio Cosentino In-Reply-To: <1519213210.3689.0.camel@bitergia.com> References: <1519213148.18395.32.camel@bitergia.com> <1519213210.3689.0.camel@bitergia.com> Message-ID: <27f5dab3-0f3a-ff74-8aaf-80ca6b858872@chrysalice.org> Hi, +1 although I'm not a committer Activity speaks by itself. :-) -- boris On 21/02/18 12:40, Santiago Due?as wrote: > El mi?, 21-02-2018 a las 12:39 +0100, Jesus M. Gonzalez-Barahona > escribi?: >> Hi all, >> >> This message is to propose Valerio Cosentino (in CC) as new general >> committer for GrimoireLab. Valerio has been contributing for several >> months to several components (mainly Perceval and Elk, but also in >> some >> others), and is in my opinion a reliable developer. >> >> Have a look at his activity in his personal dashboard: >> >> https://chaoss.biterg.io/goto/ab2a8e55b3f4a505b1ddc8afae8c8ae2 >> >> >> Please, vote on this proposal, or ask for more information if needed. >> >> Reminder: anyone in this list can express their opinion, and is >> welcome >> to do so, but only votes by current general committers will be >> definite >> to make a decission. > > > +1 > > >> >> Saludos, >> >> Jesus. >> > _______________________________________________ > Grimoirelab-discussions mailing list > Grimoirelab-discussions at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/grimoirelab-discussions > From assad.montasser at ow2.org Wed Feb 21 13:02:23 2018 From: assad.montasser at ow2.org (Assad Montasser) Date: Wed, 21 Feb 2018 14:02:23 +0100 Subject: [GrimoireLab-disc] Proposal for new general committer: Valerio Cosentino In-Reply-To: <1519213148.18395.32.camel@bitergia.com> References: <1519213148.18395.32.camel@bitergia.com> Message-ID: <3a895cc4-e691-b4a9-4a9a-df322cc0cc40@ow2.org> Hi, With great pleasure I vote for, so +1 Kind regards, Assad Le 21/02/2018 ? 12:39, Jesus M. Gonzalez-Barahona a ?crit?: > Hi all, > > This message is to propose Valerio Cosentino (in CC) as new general > committer for GrimoireLab. Valerio has been contributing for several > months to several components (mainly Perceval and Elk, but also in some > others), and is in my opinion a reliable developer. > > Have a look at his activity in his personal dashboard: > > https://chaoss.biterg.io/goto/ab2a8e55b3f4a505b1ddc8afae8c8ae2 > > > Please, vote on this proposal, or ask for more information if needed. > > Reminder: anyone in this list can express their opinion, and is welcome > to do so, but only votes by current general committers will be definite > to make a decission. > > Saludos, > > Jesus. > -- Assad Montasser Software Engineer OW2 www.ow2.org C: +33 6 61 82 31 75 S: assad.montasser at ow2.org The Open Source Community for Infrastructure Software OW2con?18, June 7-8, 2018. Save the date! From acs at bitergia.com Wed Feb 21 16:22:55 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 21 Feb 2018 17:22:55 +0100 Subject: [GrimoireLab-disc] Proposal for new general committer: Valerio Cosentino In-Reply-To: <1519213148.18395.32.camel@bitergia.com> References: <1519213148.18395.32.camel@bitergia.com> Message-ID: <1519230175.22072.0.camel@bitergia.com> El mi?, 21-02-2018 a las 12:39 +0100, Jesus M. Gonzalez-Barahona escribi?: > Hi all, > > This message is to propose Valerio Cosentino (in CC) as new general > committer for GrimoireLab. Valerio has been contributing for several > months to several components (mainly Perceval and Elk, but also in > some > others), and is in my opinion a reliable developer. > > Have a look at his activity in his personal dashboard: > > https://chaoss.biterg.io/goto/ab2a8e55b3f4a505b1ddc8afae8c8ae2 > > > Please, vote on this proposal, or ask for more information if needed. > > Reminder: anyone in this list can express their opinion, and is > welcome > to do so, but only votes by current general committers will be > definite > to make a decission. +1 > > Saludos, > > Jesus. > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Wed Feb 21 16:52:53 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 21 Feb 2018 17:52:53 +0100 Subject: [GrimoireLab-disc] [Results] Proposal (new repository) Hatstall In-Reply-To: <1519214776.18395.41.camel@bitergia.com> References: <1518039829.4306.22.camel@bitergia.com> <1519214534.18395.37.camel@bitergia.com> <1519214776.18395.41.camel@bitergia.com> Message-ID: <1519231973.22072.4.camel@bitergia.com> Hi folks! El mi?, 21-02-2018 a las 13:06 +0100, Jesus M. Gonzalez-Barahona escribi?: > On Wed, 2018-02-21 at 13:02 +0100, Jesus M. Gonzalez-Barahona wrote: > > > > Summary of results (counting the proposal as +1 by the proposer): > > > > +1: 4 votes (3 are general commmitters) > > "It sounds great": 1 vote ;-) > > > > So, the proposal passes. We will move the crepo to the CHAOSS > > GitHub > > organization, as "grimoirelab-chaoss", as soon as possible. > Ooops. It was: "grimoirelab-hatstall" The repository was transferred: https://github.com/chaoss/grimoirelab-hatstall Cheers! > > Jesus. > > > > > > > Saludos, > > > > Jesus. > > > > On Wed, 2018-02-07 at 22:43 +0100, Alvaro del Castillo wrote: > > > > > > Hi all, > > > > > > I have a proposal for a new repository in GrimoireLab: Hatstall. > > > > > > Name: Hatstall > > > > > > Description: Hatstall is a web interface for SortingHat databases > > > developed mainly with Django. > > > > > > Long Description: > > > > > > Dealing with contributors with multi-identities in a development > > > community is an issue in order to get the right metrics about > > > their > > > contributions in the whole project. For example: > > > > > > * they might be using several usernames in the same data source > > > (i.e. > > > different emails for git commits) > > > * to get a whole view, you need to take into account their > > > contribution > > > in different data sources (git, issues, chats, etc.). You need to > > > merge > > > multiple usernames under a single unique identity > > > * they might be working for several organizations during project > > > life > > > SortingHat is the GrimoireLab tool to deal with all that stuff, > > > but > > > it's CLI might not be very intuitive. So, the learning curve is > > > high, > > > and it takes a long time for a non-tech user to give the right > > > information to the right identity. > > > > > > So, Hatstall tries to make easier to deal with multi-identities > > > management in development communities. > > > > > > Current repository: https://github.com/acs/django-hatstall > > > > > > Notes: In a preliminary review, Hatstall needs pip packaging, and > > > better testing. > > > > > > Proposal: > > > > > > To move the current repository to chaoss/grimoirelab-hatstall > > > with > > > a > > > README.md that clearly states: "Module in the process of joining > > > GrimoireLab. Issues pending:" (and a list of issues with the > > > formal > > > problems that need to be fixed (for now, those mentioned in the > > > "Notes" > > > section above). > > > > > > Any feedback is appreciated. > > > > > > Cheers > > > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Wed Feb 21 16:55:32 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Wed, 21 Feb 2018 17:55:32 +0100 Subject: [GrimoireLab-disc] [Results] Proposal (new repository) Bestiary In-Reply-To: <1519214730.18395.39.camel@bitergia.com> References: <1516963093.32310.11.camel@bitergia.com> <1519214730.18395.39.camel@bitergia.com> Message-ID: <1519232132.22072.5.camel@bitergia.com> Hi folks! El mi?, 21-02-2018 a las 13:05 +0100, Jesus M. Gonzalez-Barahona escribi?: > Summary of results (counting the proposal as +1 by the proposer): > > +1: 3 votes (3 are general committers) > > So, the proposal passes. We will move the crepo to the CHAOSS GitHub > organization, as "grimoirelab-bestiary", as soon as possible. The repository was transferred: https://github.com/chaoss/grimoirelab-bestiary Cheers! > > Saludos, > > Jesus. > > On Fri, 2018-01-26 at 11:38 +0100, Jesus M. Gonzalez-Barahona wrote: > > > > Hi all, > > > > ?lvaro, in CC, has a proposal for a new repository in GrimoireLab: > > Bestiary. > > > > Name: Bestiary > > > > Description: Tool for managing the Mordred projects.json > > configuration > > > > Long Description: > > ? For knowing about the data sources needed to produce a dashboard, > > Mordred is using a file, projects.json, which specifies the urls of > > those data sources, and the structure of the projects, as they will > > be > > shown in the dashboard. Bestiary provides a web-based interface for > > maintaining this information in a more user friendly way. It is > > based > > on Django, and maintains its own database with the same information > > provided by the projects.json file. It provides this information > > via > > a > > simple REST interface, that mordred and other tools could consume. > > > > Current repository: https://github.com/acs/bestiary > > > > Notes: In a preliminary review, Bestiary needs a much more complete > > README.md file, pip packaging, and better testing. > > > > Proposal: > > > > To move the current repository to chaoss/grimoirelab-bestiary with > > a > > README.md that clearly states: "Module in the process of joining > > GrimoireLab. Issues pending:" (and a list of issues with the formal > > problems that need to be fixed (for now, those mentioned in the > > "Notes" > > section above). > > > > Any feedback is appreciated. > > > > Saludos, > > > > Jesus. > > ? -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From jgb at bitergia.com Fri Feb 23 00:10:03 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Fri, 23 Feb 2018 01:10:03 +0100 Subject: [GrimoireLab-disc] Help wanted: testing a new container image Message-ID: <1519344603.2729.55.camel@bitergia.com> Hi all, I'm working with a new Docker container image, which I intend to use to easy the demonstration of GrimoireLab. You can pull it from DockerHub. It is grimoirelab/secured. This container image includes GrimoireLab with everything needed to run it (ElasticSearch 6.1, Kibiter 6.1, MariaDB), and when run, produces a dashboard with an analysis of CHAOSS activity, including GrimoireLab (by running mordred). The access to both Kibiter and ElasticSearch is secured with SearchGuard, and Kibiter is accessible via SSL. You can run it as: docker run -p 127.0.0.1:5601:5601 -p 127.0.0.1:9200:9200 \ -p 127.0.0.1:3306:3306 -v $(pwd)/credentials.cfg:/override.cfg \ -v $(pwd)/logs:/logs grimoirelab/secured:latest You need to have ports 5601, 9200, and 3306 free in your host (or map to other ports, or map only 5601, which exposing Kibiter, and really the only one needed to see the dashboard). You need a file credentials.cfg with the following content: [github] api-token = XXX XXX is a valid GitHub token, with permissions for reading public repos. logs is a directory where logs for mordred will be produced. When run, expect some messages about problems with BeautifulSoup: they are already fixed, but the version of Perceval in which they are fixed is right now incompatible with other GrimoireLab stuff, and therefore i could not include it in the container (I hope that will be fixed soon). Once the container is up and starts gathering data, you can point your browser to https://localhost:5601. You will get a warning by the broser, because the container is using a self-signed certificate. Give permisions, and go on. When asked for credentials, use admin/admin (same can be used to access Elasticsearch at https://localhost:9200). You should see a dashboard pretty similar to https://chaoss.biterg.io Please, let me know if you experience any problems with it. If you're curious about how it is produced, have a look at https://github.com/chaoss/grimoirelab/pull/77 You can tinker with it in the same way you would do with grimoirelab/installed, for example to override its configuration files and analyze a different set of repositories. Documentation about that is in https://github.com/chaoss/grimoirelab/blob/master/docker/README.md WARNING: This container, as such, is not for deploying in a way that is accesible directly from the Internet. Credentials are set by default, and are easy to get form the pr above (or from the SearchGuard documentation, since I'm using the same defaults). Saludos, Jesus. -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From acs at bitergia.com Fri Feb 23 05:40:30 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Fri, 23 Feb 2018 06:40:30 +0100 Subject: [GrimoireLab-disc] A proposal for GrimoireLab release names Message-ID: <1519364430.22072.30.camel@bitergia.com> Dear community, Until now in GrimoireLab an informal process was used for naming the releases. https://github.com/chaoss/grimoirelab/blob/master/releases/README.md I propose to change it to a new scheme using dates. For example, for the new release which will be the first one in Feb 2018: 18.02.1 For the second release in February: 18.02.2 And for the first release in March: 18.03.1 The first release in 2019, if it is in January, it will be: 19.01.1 The advantages of this schema are: * The ordering of the release names is the same than the time ordering in which releases were published. * It is predictable * It is easy to remember (use the first release of June) * It is homogeneous and short * It is easy to parse? * It is natural to have a lot of different releases something needed in continuos integration, which is preferred integration model in GrimoireLab. * It is used in large projects like Ubuntu [1] * A release alias could be used to have more cool names for specific versions. I have doubts about: * 18.02.1 or 2018.02.1 * 18.02.1 or 18.02-1 (it is more clear that 1 does not refer to the day 1 on February). Any objections to change to this format? Cheers! [1]?https://wiki.ubuntu.com/Releases -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From jgb at bitergia.com Fri Feb 23 07:57:20 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Fri, 23 Feb 2018 08:57:20 +0100 Subject: [GrimoireLab-disc] Proposal for new general committer: Valerio Cosentino In-Reply-To: <1519213148.18395.32.camel@bitergia.com> References: <1519213148.18395.32.camel@bitergia.com> Message-ID: <1519372640.2729.58.camel@bitergia.com> Thanks a lot! The result of the vote is: +1: 5 votes (3 from committers) So, Valerio is approved as new general committer for GrimoireLab. Congratulations, Valerio! Jesus. On Wed, 2018-02-21 at 12:39 +0100, Jesus M. Gonzalez-Barahona wrote: > Hi all, > > This message is to propose Valerio Cosentino (in CC) as new general > committer for GrimoireLab. Valerio has been contributing for several > months to several components (mainly Perceval and Elk, but also in > some > others), and is in my opinion a reliable developer. > > Have a look at his activity in his personal dashboard: > > https://chaoss.biterg.io/goto/ab2a8e55b3f4a505b1ddc8afae8c8ae2 > > > Please, vote on this proposal, or ask for more information if needed. > > Reminder: anyone in this list can express their opinion, and is > welcome > to do so, but only votes by current general committers will be > definite > to make a decission. > > Saludos, > > Jesus. > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From jgb at bitergia.com Fri Feb 23 08:12:24 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Fri, 23 Feb 2018 09:12:24 +0100 Subject: [GrimoireLab-disc] A proposal for GrimoireLab release names In-Reply-To: <1519364430.22072.30.camel@bitergia.com> References: <1519364430.22072.30.camel@bitergia.com> Message-ID: <1519373544.2729.69.camel@bitergia.com> On Fri, 2018-02-23 at 06:40 +0100, Alvaro del Castillo wrote: > Dear community, > > Until now in GrimoireLab an informal process was used for naming the > releases. > > https://github.com/chaoss/grimoirelab/blob/master/releases/README.md > > I propose to change it to a new scheme using dates. For example, for > the new release which will be the first one in Feb 2018: > > 18.02.1 > > For the second release in February: > > 18.02.2 > > And for the first release in March: > > 18.03.1 > > The first release in 2019, if it is in January, it will be: > > 19.01.1 > > The advantages of this schema are: > > * The ordering of the release names is the same than the time > ordering > in which releases were published. > * It is predictable > * It is easy to remember (use the first release of June) > * It is homogeneous and short > * It is easy to parse > * It is natural to have a lot of different releases something needed > in > continuos integration, which is preferred integration model in > GrimoireLab. > * It is used in large projects like Ubuntu [1] > * A release alias could be used to have more cool names for specific > versions. > > I have doubts about: > > * 18.02.1 or 2018.02.1 > * 18.02.1 or 18.02-1 (it is more clear that 1 does not refer to the > day > 1 on February). > > Any objections to change to this format? > > Cheers! > > [1] https://wiki.ubuntu.com/Releases Well, I'm a bit attached to the "elasticgirl"-like names, they seem more funny to me. But I can live with releases based on dates ;-) (I support having nicknames for releases too, as you suggest, in addition to the official release name, though). With respect to how to name, I prefer 10.02-1, because as you say, it is clear that "-1" is not the first day of the month. But I think we also need a way of making a difference between "real" releases, and fix releases (such as the "elasticsearch.30.3" that we have now). So, I suggest: Releases: 18.02-01 (note two digits for the sequential number: not that I think we're going to have ten releases a month, but well, that makes it more uniform, and who knows how far continuous releasing could lead us) Fix releases: 18.02-01-a (using letters instead of numbers to make it crystal clear that it is a fix release, and not a "real" release). What do you think? Jesus. > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From sduenas at bitergia.com Fri Feb 23 13:22:25 2018 From: sduenas at bitergia.com (Santiago =?ISO-8859-1?Q?Due=F1as?=) Date: Fri, 23 Feb 2018 14:22:25 +0100 Subject: [GrimoireLab-disc] A proposal for GrimoireLab release names In-Reply-To: <1519373544.2729.69.camel@bitergia.com> References: <1519364430.22072.30.camel@bitergia.com> <1519373544.2729.69.camel@bitergia.com> Message-ID: <1519392145.3117.3.camel@bitergia.com> El vie, 23-02-2018 a las 09:12 +0100, Jesus M. Gonzalez-Barahona escribi?: > On Fri, 2018-02-23 at 06:40 +0100, Alvaro del Castillo wrote: > > > > Dear community, > > > > Until now in GrimoireLab an informal process was used for naming > > the > > releases. > > > > https://github.com/chaoss/grimoirelab/blob/master/releases/README.m > > d > > > > I propose to change it to a new scheme using dates. For example, > > for > > the new release which will be the first one in Feb 2018: > > > > 18.02.1 > > > > For the second release in February: > > > > 18.02.2 > > > > And for the first release in March: > > > > 18.03.1 > > > > The first release in 2019, if it is in January, it will be: > > > > 19.01.1 > > > > The advantages of this schema are: > > > > * The ordering of the release names is the same than the time > > ordering > > in which releases were published. > > * It is predictable > > * It is easy to remember (use the first release of June) > > * It is homogeneous and short > > * It is easy to parse? > > * It is natural to have a lot of different releases something > > needed > > in > > continuos integration, which is preferred integration model in > > GrimoireLab. > > * It is used in large projects like Ubuntu [1] > > * A release alias could be used to have more cool names for > > specific > > versions. > > > > I have doubts about: > > > > * 18.02.1 or 2018.02.1 > > * 18.02.1 or 18.02-1 (it is more clear that 1 does not refer to the > > day > > 1 on February). > > > > Any objections to change to this format? > > > > Cheers! > > > > [1] https://wiki.ubuntu.com/Releases > Well, I'm a bit attached to the "elasticgirl"-like names, they seem > more funny to me. But I can live with releases based on dates ;-) (I > support having nicknames for releases too, as you suggest, in > addition > to the official release name, though). > > With respect to how to name, I prefer 10.02-1, because as you say, it > is clear that "-1" is not the first day of the month. But I think we > also need a way of making a difference between "real" releases, and > fix > releases (such as the "elasticsearch.30.3" that we have now). > > So, I suggest: > > Releases: 18.02-01 > ? (note two digits for the sequential number: not that I think we're > going to have ten releases a month, but well, that makes it more > uniform, and who knows how far continuous releasing could lead us)? > > Fix releases: 18.02-01-a > ? (using letters instead of numbers to make it crystal clear that it > is > a fix release, and not a "real" release). > > What do you think? I agree with acs proposal and with your amendments, Jes?s. > > Jesus. > > > > > From benp at osg.samsung.com Fri Feb 23 16:49:51 2018 From: benp at osg.samsung.com (Ben Lloyd Pearson) Date: Fri, 23 Feb 2018 10:49:51 -0600 Subject: [GrimoireLab-disc] Help wanted: testing a new container image In-Reply-To: <1519344603.2729.55.camel@bitergia.com> References: <1519344603.2729.55.camel@bitergia.com> Message-ID: <23d577a7-3f91-b96b-d8a3-5f86fffeedc7@osg.samsung.com> This is really awesome Jesus! I've used the previous docker instructions you had for GrimoireLab on the Bitergia docker hub with varying success, so I'd be interested to see how well the new stuff stacks up to the old. I'll try to spend some time with it in the next week and let you know of any issues I run into. On 02/22/2018 06:10 PM, Jesus M. Gonzalez-Barahona wrote: > Hi all, > > I'm working with a new Docker container image, which I intend to use to > easy the demonstration of GrimoireLab. You can pull it from DockerHub. > It is grimoirelab/secured. > > This container image includes GrimoireLab with everything needed to run > it (ElasticSearch 6.1, Kibiter 6.1, MariaDB), and when run, produces a > dashboard with an analysis of CHAOSS activity, including GrimoireLab > (by running mordred). The access to both Kibiter and ElasticSearch is > secured with SearchGuard, and Kibiter is accessible via SSL. > > You can run it as: > > docker run -p 127.0.0.1:5601:5601 -p 127.0.0.1:9200:9200 \ > -p 127.0.0.1:3306:3306 -v $(pwd)/credentials.cfg:/override.cfg \ > -v $(pwd)/logs:/logs grimoirelab/secured:latest > > You need to have ports 5601, 9200, and 3306 free in your host (or map > to other ports, or map only 5601, which exposing Kibiter, and really > the only one needed to see the dashboard). > > You need a file credentials.cfg with the following content: > > [github] > api-token = XXX > > XXX is a valid GitHub token, with permissions for reading public repos. > > logs is a directory where logs for mordred will be produced. > > When run, expect some messages about problems with BeautifulSoup: they > are already fixed, but the version of Perceval in which they are fixed > is right now incompatible with other GrimoireLab stuff, and therefore i > could not include it in the container (I hope that will be fixed soon). > > Once the container is up and starts gathering data, you can point your > browser to https://localhost:5601. You will get a warning by the > broser, because the container is using a self-signed certificate. Give > permisions, and go on. When asked for credentials, use admin/admin > (same can be used to access Elasticsearch at https://localhost:9200). > > You should see a dashboard pretty similar to https://chaoss.biterg.io > > Please, let me know if you experience any problems with it. If you're > curious about how it is produced, have a look at > > https://github.com/chaoss/grimoirelab/pull/77 > > You can tinker with it in the same way you would do with > grimoirelab/installed, for example to override its configuration files > and analyze a different set of repositories. Documentation about that > is in > > https://github.com/chaoss/grimoirelab/blob/master/docker/README.md > > WARNING: This container, as such, is not for deploying in a way that is > accesible directly from the Internet. Credentials are set by default, > and are easy to get form the pr above (or from the SearchGuard > documentation, since I'm using the same defaults). > > Saludos, > > Jesus. > -- Ben Lloyd Pearson - Open Source Operations & Strategy Samsung Open Source Group benp at osg.samsung.com From acs at bitergia.com Fri Feb 23 19:20:32 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Fri, 23 Feb 2018 20:20:32 +0100 Subject: [GrimoireLab-disc] A proposal for GrimoireLab release names In-Reply-To: <1519373544.2729.69.camel@bitergia.com> References: <1519364430.22072.30.camel@bitergia.com> <1519373544.2729.69.camel@bitergia.com> Message-ID: <1519413632.22814.17.camel@bitergia.com> El vie, 23-02-2018 a las 09:12 +0100, Jesus M. Gonzalez-Barahona escribi?: > On Fri, 2018-02-23 at 06:40 +0100, Alvaro del Castillo wrote: > > > > Dear community, > > > > Until now in GrimoireLab an informal process was used for naming > > the > > releases. > > > > https://github.com/chaoss/grimoirelab/blob/master/releases/README.m > > d > > > > I propose to change it to a new scheme using dates. For example, > > for > > the new release which will be the first one in Feb 2018: > > > > 18.02.1 > > > > For the second release in February: > > > > 18.02.2 > > > > And for the first release in March: > > > > 18.03.1 > > > > The first release in 2019, if it is in January, it will be: > > > > 19.01.1 > > > > The advantages of this schema are: > > > > * The ordering of the release names is the same than the time > > ordering > > in which releases were published. > > * It is predictable > > * It is easy to remember (use the first release of June) > > * It is homogeneous and short > > * It is easy to parse? > > * It is natural to have a lot of different releases something > > needed > > in > > continuos integration, which is preferred integration model in > > GrimoireLab. > > * It is used in large projects like Ubuntu [1] > > * A release alias could be used to have more cool names for > > specific > > versions. > > > > I have doubts about: > > > > * 18.02.1 or 2018.02.1 > > * 18.02.1 or 18.02-1 (it is more clear that 1 does not refer to the > > day > > 1 on February). > > > > Any objections to change to this format? > > > > Cheers! > > > > [1] https://wiki.ubuntu.com/Releases > Well, I'm a bit attached to the "elasticgirl"-like names, they seem > more funny to me. But I can live with releases based on dates ;-) (I > support having nicknames for releases too, as you suggest, in > addition > to the official release name, though). > > With respect to how to name, I prefer 10.02-1, because as you say, it > is clear that "-1" is not the first day of the month. But I think we > also need a way of making a difference between "real" releases, and > fix > releases (such as the "elasticsearch.30.3" that we have now). > > So, I suggest: > > Releases: 18.02-01 > ? (note two digits for the sequential number: not that I think we're > going to have ten releases a month, but well, that makes it more > uniform, and who knows how far continuous releasing could lead us)? > > Fix releases: 18.02-01-a > ? (using letters instead of numbers to make it crystal clear that it > is > a fix release, and not a "real" release). > > What do you think? +1 Let's wait for other opinions and the next week we can take the decision and adopt the new release name schema. Thanks! > > Jesus. > > > > > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From acs at bitergia.com Sun Feb 25 17:52:03 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Sun, 25 Feb 2018 18:52:03 +0100 Subject: [GrimoireLab-disc] [Fwd: Domain Availability Notification: grimoirelab.com] References: <20180225154909.1.01E2540D29582C5E@acting-integrator.com> Message-ID: <1519581123.22814.26.camel@bitergia.com> Dear community, Not sure how feasible is trying to get the domain or if it useful at all the ".com" domain. Cheers! -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" -------------- next part -------------- An embedded message was scrubbed... From: Support Subject: Domain Availability Notification: grimoirelab.com Date: Sun, 25 Feb 2018 15:49:09 +0000 Size: 3593 URL: From jgb at bitergia.com Sun Feb 25 23:38:49 2018 From: jgb at bitergia.com (Jesus M. Gonzalez-Barahona) Date: Mon, 26 Feb 2018 00:38:49 +0100 Subject: [GrimoireLab-disc] Help wanted: testing a new container image In-Reply-To: <23d577a7-3f91-b96b-d8a3-5f86fffeedc7@osg.samsung.com> References: <1519344603.2729.55.camel@bitergia.com> <23d577a7-3f91-b96b-d8a3-5f86fffeedc7@osg.samsung.com> Message-ID: <1519601929.2729.85.camel@bitergia.com> Thanks!!!! Jesus. On Fri, 2018-02-23 at 10:49 -0600, Ben Lloyd Pearson wrote: > This is really awesome Jesus! > > I've used the previous docker instructions you had for GrimoireLab > on > the Bitergia docker hub with varying success, so I'd be interested > to > see how well the new stuff stacks up to the old. I'll try to spend > some > time with it in the next week and let you know of any issues I run > into. > > > On 02/22/2018 06:10 PM, Jesus M. Gonzalez-Barahona wrote: > > Hi all, > > > > I'm working with a new Docker container image, which I intend to > > use to > > easy the demonstration of GrimoireLab. You can pull it from > > DockerHub. > > It is grimoirelab/secured. > > > > This container image includes GrimoireLab with everything needed to > > run > > it (ElasticSearch 6.1, Kibiter 6.1, MariaDB), and when run, > > produces a > > dashboard with an analysis of CHAOSS activity, including > > GrimoireLab > > (by running mordred). The access to both Kibiter and ElasticSearch > > is > > secured with SearchGuard, and Kibiter is accessible via SSL. > > > > You can run it as: > > > > docker run -p 127.0.0.1:5601:5601 -p 127.0.0.1:9200:9200 \ > > -p 127.0.0.1:3306:3306 -v $(pwd)/credentials.cfg:/override.cfg \ > > -v $(pwd)/logs:/logs grimoirelab/secured:latest > > > > You need to have ports 5601, 9200, and 3306 free in your host (or > > map > > to other ports, or map only 5601, which exposing Kibiter, and > > really > > the only one needed to see the dashboard). > > > > You need a file credentials.cfg with the following content: > > > > [github] > > api-token = XXX > > > > XXX is a valid GitHub token, with permissions for reading public > > repos. > > > > logs is a directory where logs for mordred will be produced. > > > > When run, expect some messages about problems with BeautifulSoup: > > they > > are already fixed, but the version of Perceval in which they are > > fixed > > is right now incompatible with other GrimoireLab stuff, and > > therefore i > > could not include it in the container (I hope that will be fixed > > soon). > > > > Once the container is up and starts gathering data, you can point > > your > > browser to https://localhost:5601. You will get a warning by the > > broser, because the container is using a self-signed certificate. > > Give > > permisions, and go on. When asked for credentials, use admin/admin > > (same can be used to access Elasticsearch at https://localhost:9200 > > ). > > > > You should see a dashboard pretty similar to https://chaoss.biterg. > > io > > > > Please, let me know if you experience any problems with it. If > > you're > > curious about how it is produced, have a look at > > > > https://github.com/chaoss/grimoirelab/pull/77 > > > > You can tinker with it in the same way you would do with > > grimoirelab/installed, for example to override its configuration > > files > > and analyze a different set of repositories. Documentation about > > that > > is in > > > > https://github.com/chaoss/grimoirelab/blob/master/docker/README.md > > > > WARNING: This container, as such, is not for deploying in a way > > that is > > accesible directly from the Internet. Credentials are set by > > default, > > and are easy to get form the pr above (or from the SearchGuard > > documentation, since I'm using the same defaults). > > > > Saludos, > > > > Jesus. > > > > -- Bitergia: http://bitergia.com /me at Twitter: https://twitter.com/jgbarah From dizquierdo at bitergia.com Tue Feb 27 13:37:08 2018 From: dizquierdo at bitergia.com (Daniel Izquierdo) Date: Tue, 27 Feb 2018 14:37:08 +0100 Subject: [GrimoireLab-disc] Proposal for a new project: Ceres Message-ID: <4c5db999-eeeb-3fd1-6e59-227363b4dc55@bitergia.com> Hello everyone, This email is a proposal to add Ceres[1] as a new project part of the GrimoireLab toolchain. 1. What is Ceres? Ceres is a library that aims at dealing with data in general, and software development data in particular. The initial goal of Ceres is to parse information in several ways from the Perceval tool in the GrimoireLab project. However, the more code is added to this project, the more generic methods are found to be useful in other areas of analysis. And this is leading this project to a data analysis tool with a lot of methods interesting from a software development perspective such as the structure of the community, pair programming, calculating time differences, gender, and others. There are three main areas of work: 'eventize', enrich and format. * Eventize: this receives as input a Perceval JSON document and produces as output a Pandas dataframe. There are several granularities depending on the needs of the outcome. For instance, when dealing with commits, this may returns a new row in the dataframe (granularity 1, relationship of 1 JSON to 1 row in the dataframe) or several rows as there is a need to retrieve information at the level of files, so the resultant dataframe will contain N rows coming from a single JSON document. * Enrich: this contains a set of classes that transforms dataframes to dataframes adding, removing or updating the existing information. An example is the timedifference[2] class where this returns a new dataframe with a new column that applies certain function on two existing columns. * Format and Filter: this helps to deal with the usual issues when curating data: dates, strings, filter non-required fields, and others. 2. Where is this being used? One of the goals of this tool is to be efficient when dealing with large datasets, produce less code so this is potentially more maintainable (we can have a lot of discussions here of course!! :) ),? and have a library to massage and curate data that can potentially be used in some other scenarios given its modularity. As an example of the work done by this library, this is used by the D&I working group[3] whose piece of code is currently based on Ceres. And the OpenStack Gender Report[4] source code is partially based on Ceres. 3. Why Ceres and not Cereslib as seen in the code? It seems that there is an existing Ceres project in Pypi, so we moved from 'ceres' to 'cereslib' in the code, but Ceres[5] is the original name. Comments or concerns are welcome :). Regards, Daniel. [1] https://github.com/dicortazar/ceres [2] https://github.com/dicortazar/ceres/blob/master/cereslib/enrich/enrich.py#L770 [3] https://github.com/chaoss/wg-diversity-inclusion [4] http://superuser.openstack.org/articles/bitergia-intel-report/ [5] https://en.wikipedia.org/wiki/Ceres_(mythology) -- Daniel Izquierdo Cortazar, PhD Chief Data Officer --------- "Software Analytics for your peace of mind" www.bitergia.com @bitergia From acs at bitergia.com Tue Feb 27 17:10:15 2018 From: acs at bitergia.com (Alvaro del Castillo) Date: Tue, 27 Feb 2018 18:10:15 +0100 Subject: [GrimoireLab-disc] Proposal for a new project: Ceres In-Reply-To: <4c5db999-eeeb-3fd1-6e59-227363b4dc55@bitergia.com> References: <4c5db999-eeeb-3fd1-6e59-227363b4dc55@bitergia.com> Message-ID: <1519751415.13824.7.camel@bitergia.com> +1 El mar, 27-02-2018 a las 14:37 +0100, Daniel Izquierdo escribi?: > Hello everyone, > > This email is a proposal to add Ceres[1] as a new project part of > the? > GrimoireLab toolchain. > > > 1. What is Ceres? > > Ceres is a library that aims at dealing with data in general, and? > software development data in particular. > > The initial goal of Ceres is to parse information in several ways > from? > the Perceval tool in the GrimoireLab project. > > However, the more code is added to this project, the more generic? > methods are found to be useful in other areas of analysis. > > And this is leading this project to a data analysis tool with a lot > of? > methods interesting from a software development perspective such as > the? > structure of the community, pair programming, calculating time? > differences, gender, and others. > > > There are three main areas of work: 'eventize', enrich and format. > > * Eventize: this receives as input a Perceval JSON document and > produces? > as output a Pandas dataframe. There are several granularities > depending? > on the needs of the outcome. For instance, when dealing with > commits,? > this may returns a new row in the dataframe (granularity 1, > relationship? > of 1 JSON to 1 row in the dataframe) or several rows as there is a > need? > to retrieve information at the level of files, so the resultant? > dataframe will contain N rows coming from a single JSON document. > > * Enrich: this contains a set of classes that transforms dataframes > to? > dataframes adding, removing or updating the existing information. An? > example is the timedifference[2] class where this returns a new? > dataframe with a new column that applies certain function on two? > existing columns. > > * Format and Filter: this helps to deal with the usual issues when? > curating data: dates, strings, filter non-required fields, and > others. > > > 2. Where is this being used? > > One of the goals of this tool is to be efficient when dealing with > large? > datasets, produce less code so this is potentially more maintainable > (we? > can have a lot of discussions here of course!! :) ),? and have a > library? > to massage and curate data that can potentially be used in some > other? > scenarios given its modularity. > > As an example of the work done by this library, this is used by the > D&I? > working group[3] whose piece of code is currently based on Ceres. > And? > the OpenStack Gender Report[4] source code is partially based on > Ceres. > > > 3. Why Ceres and not Cereslib as seen in the code? > > It seems that there is an existing Ceres project in Pypi, so we > moved? > from 'ceres' to 'cereslib' in the code, but Ceres[5] is the original > name. > > > Comments or concerns are welcome :). > > > Regards, > Daniel. > > > [1] https://github.com/dicortazar/ceres > > [2]? > https://github.com/dicortazar/ceres/blob/master/cereslib/enrich/enric > h.py#L770 > > [3] https://github.com/chaoss/wg-diversity-inclusion > > [4] http://superuser.openstack.org/articles/bitergia-intel-report/ > > [5] https://en.wikipedia.org/wiki/Ceres_(mythology) > > -- Alvaro del Castillo San F?lix acs at bitergia.com - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind" From benp at osg.samsung.com Wed Feb 28 18:48:31 2018 From: benp at osg.samsung.com (Ben Lloyd Pearson) Date: Wed, 28 Feb 2018 12:48:31 -0600 Subject: [GrimoireLab-disc] Help wanted: testing a new container image In-Reply-To: <1519601929.2729.85.camel@bitergia.com> References: <1519344603.2729.55.camel@bitergia.com> <23d577a7-3f91-b96b-d8a3-5f86fffeedc7@osg.samsung.com> <1519601929.2729.85.camel@bitergia.com> Message-ID: <920e7afd-0739-856b-04cc-815282d45a7e@osg.samsung.com> Hi Jesus, I took some time to test this out and I'm really impressed by what you've done. I think these docker setups can be a really great way for users like me to keep up with all of the changes you guys make. Something that I think would further reduce admin complexity would be a setup that protects edits to the kibiter dashboard behind authentication to the kibiter setup in the grimoirelab/secured container while also providing unauthenticated, read-only access to the grimoirelab/full version of kibiter. I suspect the only way to do this is to run two separate kibiter services, so that might be a challenge. The only way I've found to do this currently is to create two separate web server proxies that filter POST/GET messages for one virtual host (e.g. unauthenticated.user.com) to prevent changes, and the 2nd virtual host (e.g. authenticated.user.com) requires authentication to access and provides full access to POST/GET messages. So anything that simplifies this would be awesome. On 02/25/2018 05:38 PM, Jesus M. Gonzalez-Barahona wrote: > Thanks!!!! > > Jesus. > > On Fri, 2018-02-23 at 10:49 -0600, Ben Lloyd Pearson wrote: >> This is really awesome Jesus! >> >> I've used the previous docker instructions you had for GrimoireLab >> on >> the Bitergia docker hub with varying success, so I'd be interested >> to >> see how well the new stuff stacks up to the old. I'll try to spend >> some >> time with it in the next week and let you know of any issues I run >> into. >> >> >> On 02/22/2018 06:10 PM, Jesus M. Gonzalez-Barahona wrote: >>> Hi all, >>> >>> I'm working with a new Docker container image, which I intend to >>> use to >>> easy the demonstration of GrimoireLab. You can pull it from >>> DockerHub. >>> It is grimoirelab/secured. >>> >>> This container image includes GrimoireLab with everything needed to >>> run >>> it (ElasticSearch 6.1, Kibiter 6.1, MariaDB), and when run, >>> produces a >>> dashboard with an analysis of CHAOSS activity, including >>> GrimoireLab >>> (by running mordred). The access to both Kibiter and ElasticSearch >>> is >>> secured with SearchGuard, and Kibiter is accessible via SSL. >>> >>> You can run it as: >>> >>> docker run -p 127.0.0.1:5601:5601 -p 127.0.0.1:9200:9200 \ >>> -p 127.0.0.1:3306:3306 -v $(pwd)/credentials.cfg:/override.cfg \ >>> -v $(pwd)/logs:/logs grimoirelab/secured:latest >>> >>> You need to have ports 5601, 9200, and 3306 free in your host (or >>> map >>> to other ports, or map only 5601, which exposing Kibiter, and >>> really >>> the only one needed to see the dashboard). >>> >>> You need a file credentials.cfg with the following content: >>> >>> [github] >>> api-token = XXX >>> >>> XXX is a valid GitHub token, with permissions for reading public >>> repos. >>> >>> logs is a directory where logs for mordred will be produced. >>> >>> When run, expect some messages about problems with BeautifulSoup: >>> they >>> are already fixed, but the version of Perceval in which they are >>> fixed >>> is right now incompatible with other GrimoireLab stuff, and >>> therefore i >>> could not include it in the container (I hope that will be fixed >>> soon). >>> >>> Once the container is up and starts gathering data, you can point >>> your >>> browser to https://localhost:5601. You will get a warning by the >>> broser, because the container is using a self-signed certificate. >>> Give >>> permisions, and go on. When asked for credentials, use admin/admin >>> (same can be used to access Elasticsearch at https://localhost:9200 >>> ). >>> >>> You should see a dashboard pretty similar to https://chaoss.biterg. >>> io >>> >>> Please, let me know if you experience any problems with it. If >>> you're >>> curious about how it is produced, have a look at >>> >>> https://github.com/chaoss/grimoirelab/pull/77 >>> >>> You can tinker with it in the same way you would do with >>> grimoirelab/installed, for example to override its configuration >>> files >>> and analyze a different set of repositories. Documentation about >>> that >>> is in >>> >>> https://github.com/chaoss/grimoirelab/blob/master/docker/README.md >>> >>> WARNING: This container, as such, is not for deploying in a way >>> that is >>> accesible directly from the Internet. Credentials are set by >>> default, >>> and are easy to get form the pr above (or from the SearchGuard >>> documentation, since I'm using the same defaults). >>> >>> Saludos, >>> >>> Jesus. >>> >> -- Ben Lloyd Pearson - Open Source Operations & Strategy Samsung Open Source Group benp at osg.samsung.com