Here is a proposal to cut the 47 teams into only 28:
https://docs.google.com/spreadsheets/d/15aVznH-4ploi7d6yPvchyh5ZplzewbA2qYmDLDfndqU/edit?usp=sharing
Some teams have only empty repos and have been inactive.
Not sure it it's worth to create them on GitHub, but I haven't removed
them from the list.
Regards
/DR
Quoting Joël Grand-Guillaume <joel.grandguilla...@camptocamp.com>:
Dear all,
Thanks a lot for all your feedback here. So, to summarize
opinions here:
* Version <= 7.0 keep Launchpad as a reference. We
eventually setup a replication in github (lp -> gituhub) in a couple
of weeks
* We do use one organization on github for the whole community work
* We create one team on github per area of expertize (so
that means like it is now on LP). I tried to see if we can lower the
number of team, but wasn't able to decide how to merge them. Any
though here, the list is here
:https://launchpad.net/~openerp-community-reviewer/+participation ?
* Every LP project become a repository on github. The
branches hosted under the community reviewer team (bazaar extractor,
etc..) will have a new repo called something like "community toolkit".
* Branches represent the serie (like OpenERP did with odoo)
The only disadvantage I see here is that we cannot include a
team in a team on github. So that means, we'll no longer have a
community reviewer team that is part of all other team. We'll need
to add in every team the right people, but apart from a bit of
"administrative" work, it'll be ok.
As Nhomar pointed out, I already took the time to create this
organization on github : https://github.com/OdooCommunity
It was a first test from me, but if you agree, I'll spend some time
to create the team and repos. I suggest also that I make an
OCA-board team with the administration right on the organization. So
current OCA board member will be able to administrate the
organization as well.
As some of you already notice, I also took the liberty to make a new
logo, keeping the ant ;) Hope it please you all !
Regards,
Joël
On Tue, May 20, 2014 at 9:16 AM, Alejandro Catalina
<alecat...@gmail.com> wrote:
Hi there,
I also agree with the last proposal, one github organization and
several repositories, one for each launchpad project.
So let's move on. I think the best way to move all those projects
and branches is to divide the work between all of us. We could make
a list of all launchpad URL involved and begin the job.
What do you think about?
2014-05-20 8:33 GMT+02:00 Quentin THEURET <q...@tempo-consulting.fr>:
On 16/05/14 18:43, Maxime Chambreuil wrote:
> We agree with Stefan here.
I'm also agree with Stefan point of view.
Regards,
--
Quentin THEURET
TeMPO Consulting
20, Avenue de la paix
67000 Strasbourg
France
http://www.tempo-consulting.fr
Tel : +33 3 88 56 82 18[1]
Fax : +33 3 88 56 46 64[2]
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
--
CAMPTOCAMP
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
JOëL GRAND-GUILLAUME
Division Manager
Business Solutions
+41 21 619 10 28
www.camptocamp.com[3]
Ligações:
---------
[1] <a href="tel:%2B33%203%2088%2056%2082%2018">
tel:%2B33%203%2088%2056%2082%2018</a>
[2] <a href="tel:%2B33%203%2088%2056%2046%2064">
tel:%2B33%203%2088%2056%2046%2064</a>
[3] <a href="http://www.camptocamp.com/";> http://www.camptocamp.com/</a>
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp
