There is a number of contributors from this domain,
add its own entry to the gitdm domain map.
Cc: Andrew Jenner <andrew@codesourcery.com>
Cc: Daniel Gutson <dgutson@codesourcery.com>
Cc: Joseph Myers <joseph@codesourcery.com>
Cc: Julian Brown <julian@codesourcery.com>
Cc: Kazu Hirata <kazu@codesourcery.com>
Cc: Kwok Cheung Yeung <kcy@codesourcery.com>
Cc: Maciej W. Rozycki <macro@codesourcery.com>
Cc: Meador Inge <meadori@codesourcery.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>
Cc: Paul Brook <paul@codesourcery.com>
Cc: Sandra Loosemore <sandra@codesourcery.com>
Cc: Taimoor Mirza <tmirza@codesourcery.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
One Reviewed-by/Ack-by from someone from this domain
should be sufficient to get this patch merged.
---
contrib/gitdm/domain-map | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/gitdm/domain-map b/contrib/gitdm/domain-map
index 3e9602287a..4850eab4c4 100644
--- a/contrib/gitdm/domain-map
+++ b/contrib/gitdm/domain-map
@@ -21,6 +21,7 @@ ibm.com IBM
igalia.com Igalia
intel.com Intel
linaro.org Linaro
+codesourcery.com Mentor Graphics
microsoft.com Microsoft
nokia.com Nokia
oracle.com Oracle
--
2.26.2
On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: > There is a number of contributors from this domain, > add its own entry to the gitdm domain map. At some point the main branding will be Siemens; not sure how you want to handle that. -- Joseph S. Myers joseph@codesourcery.com
Joseph Myers <joseph@codesourcery.com> writes: > On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: > >> There is a number of contributors from this domain, >> add its own entry to the gitdm domain map. > > At some point the main branding will be Siemens; not sure how you want to > handle that. We've already done something similar with WaveComp who have rolled up the various mips and imgtec contributions into contrib/gitdm/group-map-wavecomp. It's really up to you and which corporate entity would like internet bragging points. The only Siemens contributor I could find is Jan Kiszka but he has contributed a fair amount ;-) -- Alex Bennée
On Mon, 5 Oct 2020, Alex Bennée wrote: > Joseph Myers <joseph@codesourcery.com> writes: > > > On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: > > > >> There is a number of contributors from this domain, > >> add its own entry to the gitdm domain map. > > > > At some point the main branding will be Siemens; not sure how you want to > > handle that. > > We've already done something similar with WaveComp who have rolled up > the various mips and imgtec contributions into > contrib/gitdm/group-map-wavecomp. > > It's really up to you and which corporate entity would like internet > bragging points. The only Siemens contributor I could find is Jan Kiszka > but he has contributed a fair amount ;-) Given that the Mentor branding is going away (and the "Mentor Graphics" version largely has gone away, "Mentor, a Siemens Business" is what's currently used as a Mentor brand), probably it makes sense to use Siemens for both codesourcery.com and mentor.com addresses. -- Joseph S. Myers joseph@codesourcery.com
On 05.10.20 22:52, Joseph Myers wrote: > On Mon, 5 Oct 2020, Alex Bennée wrote: > >> Joseph Myers <joseph@codesourcery.com> writes: >> >>> On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: >>> >>>> There is a number of contributors from this domain, >>>> add its own entry to the gitdm domain map. >>> >>> At some point the main branding will be Siemens; not sure how you want to >>> handle that. >> >> We've already done something similar with WaveComp who have rolled up >> the various mips and imgtec contributions into >> contrib/gitdm/group-map-wavecomp. >> >> It's really up to you and which corporate entity would like internet >> bragging points. The only Siemens contributor I could find is Jan Kiszka >> but he has contributed a fair amount ;-) > > Given that the Mentor branding is going away (and the "Mentor Graphics" > version largely has gone away, "Mentor, a Siemens Business" is what's > currently used as a Mentor brand), probably it makes sense to use Siemens > for both codesourcery.com and mentor.com addresses. > I think the key question is what this map is used for: Is it supposed to document the historic status, who was who at the time of contribution? Or is its purpose to help identifying the copyright holder of a contribution today? Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
On 10/6/20 6:01 AM, Jan Kiszka wrote:
> On 05.10.20 22:52, Joseph Myers wrote:
>> On Mon, 5 Oct 2020, Alex Bennée wrote:
>>
>>> Joseph Myers <joseph@codesourcery.com> writes:
>>>
>>>> On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote:
>>>>
>>>>> There is a number of contributors from this domain,
>>>>> add its own entry to the gitdm domain map.
>>>>
>>>> At some point the main branding will be Siemens; not sure how you want to
>>>> handle that.
>>>
>>> We've already done something similar with WaveComp who have rolled up
>>> the various mips and imgtec contributions into
>>> contrib/gitdm/group-map-wavecomp.
>>>
>>> It's really up to you and which corporate entity would like internet
>>> bragging points. The only Siemens contributor I could find is Jan Kiszka
>>> but he has contributed a fair amount ;-)
>>
>> Given that the Mentor branding is going away (and the "Mentor Graphics"
>> version largely has gone away, "Mentor, a Siemens Business" is what's
>> currently used as a Mentor brand), probably it makes sense to use Siemens
>> for both codesourcery.com and mentor.com addresses.
>>
>
> I think the key question is what this map is used for: Is it supposed to
> document the historic status, who was who at the time of contribution?
> Or is its purpose to help identifying the copyright holder of a
> contribution today?
My understanding is it is useful to document the historic status
(who was who at the time of contribution). The tool support such
granularity [*]:
EmailMap file
Map email addresses onto employers. These files contain lines
like:
[user@]domain employer [< yyyy-mm-dd]
If the "user@" portion is missing, all email from the given domain
will be treated as being associated with the given employer. If a
date is provided, the entry is only valid up to that date;
otherwise it is considered valid into the indefinite future. This
feature can be useful for properly tracking developers' work when
they change employers but do not change email addresses.
[*] https://repo.or.cz/git-dm.git/blob/098408bc4d:/README#l122
Regards,
Phil.
Jan Kiszka <jan.kiszka@siemens.com> writes: > On 05.10.20 22:52, Joseph Myers wrote: >> On Mon, 5 Oct 2020, Alex Bennée wrote: >> >>> Joseph Myers <joseph@codesourcery.com> writes: >>> >>>> On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: >>>> >>>>> There is a number of contributors from this domain, >>>>> add its own entry to the gitdm domain map. >>>> >>>> At some point the main branding will be Siemens; not sure how you want to >>>> handle that. >>> >>> We've already done something similar with WaveComp who have rolled up >>> the various mips and imgtec contributions into >>> contrib/gitdm/group-map-wavecomp. >>> >>> It's really up to you and which corporate entity would like internet >>> bragging points. The only Siemens contributor I could find is Jan Kiszka >>> but he has contributed a fair amount ;-) >> >> Given that the Mentor branding is going away (and the "Mentor Graphics" >> version largely has gone away, "Mentor, a Siemens Business" is what's >> currently used as a Mentor brand), probably it makes sense to use Siemens >> for both codesourcery.com and mentor.com addresses. >> > > I think the key question is what this map is used for: Is it supposed to > document the historic status, who was who at the time of contribution? > Or is its purpose to help identifying the copyright holder of a > contribution today? I don't know what others use them for but for me it was just an easy way to get a survey of the companies and individuals involved over the last year (2y, 3y, 5y... etc) of development. The consolidation of contributions isn't overly distorting IMO. The biggest user is probably the end of year state of the nation surveys wanting to see what impact various organisations are having on a project and consolidation just helps push you up the table a little more. The biggest counter example we have at the moment is RedHat/IBM which AFAICT is because the RedHat guys are treated as a separate business unit with their own unique identity. Either way I don't think it's a major issue - hence it is up to the hackers to make the choice. -- Alex Bennée
On 10/6/20 11:44 AM, Alex Bennée wrote: > > Jan Kiszka <jan.kiszka@siemens.com> writes: > >> On 05.10.20 22:52, Joseph Myers wrote: >>> On Mon, 5 Oct 2020, Alex Bennée wrote: >>> >>>> Joseph Myers <joseph@codesourcery.com> writes: >>>> >>>>> On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: >>>>> >>>>>> There is a number of contributors from this domain, >>>>>> add its own entry to the gitdm domain map. >>>>> >>>>> At some point the main branding will be Siemens; not sure how you want to >>>>> handle that. >>>> >>>> We've already done something similar with WaveComp who have rolled up >>>> the various mips and imgtec contributions into >>>> contrib/gitdm/group-map-wavecomp. >>>> >>>> It's really up to you and which corporate entity would like internet >>>> bragging points. The only Siemens contributor I could find is Jan Kiszka >>>> but he has contributed a fair amount ;-) >>> >>> Given that the Mentor branding is going away (and the "Mentor Graphics" >>> version largely has gone away, "Mentor, a Siemens Business" is what's >>> currently used as a Mentor brand), probably it makes sense to use Siemens >>> for both codesourcery.com and mentor.com addresses. >>> >> >> I think the key question is what this map is used for: Is it supposed to >> document the historic status, who was who at the time of contribution? >> Or is its purpose to help identifying the copyright holder of a >> contribution today? > > I don't know what others use them for but for me it was just an easy way > to get a survey of the companies and individuals involved over the last > year (2y, 3y, 5y... etc) of development. My personal interest is seeing how the corporate/academic/hobbyist contributions are split, and how this evolves over time. Since there were entries for some companies, I added more, but this is not a requisite and we can drop the patches if considered not useful or giving headaches to the contributors. > The consolidation of > contributions isn't overly distorting IMO. The biggest user is probably > the end of year state of the nation surveys wanting to see what impact > various organisations are having on a project and consolidation just > helps push you up the table a little more. > > The biggest counter example we have at the moment is RedHat/IBM which > AFAICT is because the RedHat guys are treated as a separate business > unit with their own unique identity. > > Either way I don't think it's a major issue - hence it is up to the > hackers to make the choice. Totally. In this particular case, we could even keep "Codesourcery" group separate, similarly to RH/IBM. Regards, Phil.
On 06.10.20 14:41, Philippe Mathieu-Daudé wrote: > On 10/6/20 11:44 AM, Alex Bennée wrote: >> >> Jan Kiszka <jan.kiszka@siemens.com> writes: >> >>> On 05.10.20 22:52, Joseph Myers wrote: >>>> On Mon, 5 Oct 2020, Alex Bennée wrote: >>>> >>>>> Joseph Myers <joseph@codesourcery.com> writes: >>>>> >>>>>> On Sun, 4 Oct 2020, Philippe Mathieu-Daudé wrote: >>>>>> >>>>>>> There is a number of contributors from this domain, >>>>>>> add its own entry to the gitdm domain map. >>>>>> >>>>>> At some point the main branding will be Siemens; not sure how you want to >>>>>> handle that. >>>>> >>>>> We've already done something similar with WaveComp who have rolled up >>>>> the various mips and imgtec contributions into >>>>> contrib/gitdm/group-map-wavecomp. >>>>> >>>>> It's really up to you and which corporate entity would like internet >>>>> bragging points. The only Siemens contributor I could find is Jan Kiszka >>>>> but he has contributed a fair amount ;-) >>>> >>>> Given that the Mentor branding is going away (and the "Mentor Graphics" >>>> version largely has gone away, "Mentor, a Siemens Business" is what's >>>> currently used as a Mentor brand), probably it makes sense to use Siemens >>>> for both codesourcery.com and mentor.com addresses. >>>> >>> >>> I think the key question is what this map is used for: Is it supposed to >>> document the historic status, who was who at the time of contribution? >>> Or is its purpose to help identifying the copyright holder of a >>> contribution today? >> >> I don't know what others use them for but for me it was just an easy way >> to get a survey of the companies and individuals involved over the last >> year (2y, 3y, 5y... etc) of development. > > My personal interest is seeing how the corporate/academic/hobbyist > contributions are split, and how this evolves over time. > > Since there were entries for some companies, I added more, > but this is not a requisite and we can drop the patches if > considered not useful or giving headaches to the contributors. > >> The consolidation of >> contributions isn't overly distorting IMO. The biggest user is probably >> the end of year state of the nation surveys wanting to see what impact >> various organisations are having on a project and consolidation just >> helps push you up the table a little more. >> >> The biggest counter example we have at the moment is RedHat/IBM which >> AFAICT is because the RedHat guys are treated as a separate business >> unit with their own unique identity. >> >> Either way I don't think it's a major issue - hence it is up to the >> hackers to make the choice. > > Totally. In this particular case, we could even keep "Codesourcery" > group separate, similarly to RH/IBM. > If there is a way to express also timeline, then I would keep the historic contributions separate and account those since the merger (April 2017) to Siemens. You may even consider adding also the phase when Codesourcery was owned by Mentor. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
© 2016 - 2026 Red Hat, Inc.