Re: Apache Atlas Discovery Session

[Furkan KAMACI]

Hi Tricia,

Thanks for reaching out! Would you send your e-mail to the Apache Atlas
user list, which is u...@atlas.apache.org? It will be more appropriate to
ask at the project's user mail list.

Kind Regards,
Furkan KAMACI

On Tue, May 11, 2021 at 12:29 AM Patricia Robinson <
patricia.robin...@bbc.co.uk> wrote:

> Good Afternoon,
>
> My name in Tricia Robinson and I am a Data Manager at the BBC, based in
> UK.  My team have recently been investigating a number of open source data
> catalog options and we are very interested in the capabilities that Apache
> Atlas can offer.  We have been reviewing documentation online but would
> welcome a face to face session with someone with Apache Atlas expertise
> that could provide an overview and then perhaps answer some questions,
> which could be provided ahead of the session.
>
> Would it be possible to arrange a zoom meeting to discuss Apache Atlas,
> ideally it would include a quick overview of the product and then a more
> general discussion regarding how we might use the tool as a Data Catalog
> for our Audience Data Warehouse which resides across a Data Lake in Amazon
> S3 and a Data Warehouse in Amazon Redshift.
>
> Thanks in advance for any support you can provide, if you are able to
> attend a session could you please provide me with contact names and
> availability.  If you have any questions on the request please email me.
> As noted above we can provide any questions we have ahead of our session.
>
> Kind Regards,
> Tricia
>
> Tricia Robinson
> Data Manager | Audience Data | Audience Platform
> E. patricia.robin...@bbc.co.uk | M.
> 07756918801
> 4th Floor, Dock House, MediacityUK, Salford, M50 2LH
>
>
>

Re: Rust development process and the Apache Way

[Julian Hyde]

I wanted to thank everyone for their detailed & thoughtful replies in this 
thread. The Arrow-Rust community feel that they can streamline the release 
process to do a source release every two weeks or so, similar to the processes 
for SkyWalking and Airflow mentioned in the thread.

Julian

On 2021/05/02 09:00:05, Sheng Wu  wrote: 
> Hi Jarek
> 
> SkyWalking and Airflow communities always share some similar patterns due
> to our modulization pattern for building systems.
> I think your way should be good from the foundation perspective.
> Meaningwhile in SkyWalking, we rely on auto e2e/unit tests a lot rather
> than manual testing.
> SkyWalking's backend/UI/javaagent with protocols release every 1-1.5
> months, and all PMC would be involved in.
> But other agents and tools are on their own, and which of them have more
> than 3 PMC members, so, after all, we could avoid overheating of voting by
> this way.
> 
> Arrow community friends, you could choose which ways you prefer and want to
> do an experiment.
> 
> After all, from my understanding, manual testing and over PMC testing are
> not restricted rules for a release.
> PMC approved with compilable and no(or minimal) LICENSE issues are
> expected by the foundation.
> Software always has bugs, the robustness of your release could be
> determined with time, and this is on PMC's call.
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> 
> Jarek Potiuk  于2021年5月2日周日 下午4:26写道：
> 
> > Hi Sheng,
> >
> > We had a similar discussion recently in Apache Airflow, and I think there
> > are ways you can still follow the Apache Way spirit, follow the
> > voting process and keep the community involved. And I personally think
> > involving your community in the release process is the true embodiment of
> > the "community-over-code".
> >
> > In Airflow we used to have one release every few months, but as of Airflow
> > 2.0 we split it into 60+ independent packages (Core Airflow +  60+
> > providers - independent add-ons for Airflow). We also recently started to
> > release a "Python API client" and very soon we will release Helm Chart.
> > Those are all independent releases.
> >
> > Our release process is now that Core Airflow is released every ~ 2 months
> > and the 60+ providers are released with monthly cadence. Roughly every
> > month there are significant "non-doc" changes in  20-30 packages or so so
> > this means that every month we have 20-30 packages to vote on.
> >
> > And yeah, having 30+ voting threads a month would be impossible to handle.
> >
> > So we figured something else.
> >
> > We had a rather heated discussion on how to do it and experimented a bit
> > with it but the very important topic that was raised was the "manual
> > testing" part. We have a very comprehensive, automated testing process -
> > that not only run the tests, but also builds the packages, installs them on
> > top of released Airflow versions, checks if all the modules are importing
> > cleanly and even verify if the automated discovery of those add-ons
> > provides expected results after they are installed. However some of the
> > members of the community (rightfully) thought it is not enough. There needs
> > to be a human factor involved, and it's rather difficult to have one or
> > even few people testing 20-30 different packages every month. And involving
> > the community is the solution.
> >
> > This is what we do now (we are already doing it for the 4th time):
> >
> > 1) we release all the 20-30 packages with a single voting thread. We accept
> > the situation that if someone raises an issue with a specific package, it
> > can be dropped from the release without invalidating the whole voting (this
> > is at the discretion of the release manager who has the ultimate power
> > there - and it's perfectly ok IMHO with ASF rules).
> > 2) the release manager not only announces the release but also prepares an
> > Issue in GitHub where contributors who contributed the fixes are
> > `@mentioned` and asked to test the package being released - for every
> > provider "package" there is a list of people who 'contributed' to it (this
> > is not yet fully automated but can be). Also in some cases the release
> > manager decides that change is very simple and needs no testing other than
> > installing the new package.
> > 3) we ask those contributors for help and verify of their fixes/new feature
> > in the RC of the provider they contributed to and keep track via comments /
> > updating github issue
> > 4) the PMCs nor release manager does not have to test all those providers -
> > if the contributors confirm that the new RC works, we trust it.
> > 5) PMC member's main role is to verify if the packages are
> > signed/checksummed properly, if the sources have all the licences (all that
> > is mostly semi-automated) and to be aware of the testing status.
> > 6) The release manager is mostly responsible for the "mechanics" of the
> > release, reminders etc. but with single issue/voting thread it is
>

Apache Atlas Discovery Session

[Patricia Robinson]

Good Afternoon,

My name in Tricia Robinson and I am a Data Manager at the BBC, based in UK.  My 
team have recently been investigating a number of open source data catalog 
options and we are very interested in the capabilities that Apache Atlas can 
offer.  We have been reviewing documentation online but would welcome a face to 
face session with someone with Apache Atlas expertise that could provide an 
overview and then perhaps answer some questions, which could be provided ahead 
of the session.

Would it be possible to arrange a zoom meeting to discuss Apache Atlas, ideally 
it would include a quick overview of the product and then a more general 
discussion regarding how we might use the tool as a Data Catalog for our 
Audience Data Warehouse which resides across a Data Lake in Amazon S3 and a 
Data Warehouse in Amazon Redshift.

Thanks in advance for any support you can provide, if you are able to attend a 
session could you please provide me with contact names and availability.  If 
you have any questions on the request please email me.  As noted above we can 
provide any questions we have ahead of our session.

Kind Regards,
Tricia

Tricia Robinson
Data Manager | Audience Data | Audience Platform
E. patricia.robin...@bbc.co.uk | M. 
07756918801
4th Floor, Dock House, MediacityUK, Salford, M50 2LH

Re: Update to ICLA to include github id

[Matt Sicker]

PMCs can already use the account request form directly with a link to
the vote thread. That doesn't help when the person submitting the ICLA
doesn't have one on file yet. It doesn't help when I get an ICLA
without a project and userid included. It doesn't help when PMCs make
vote threads for new committers using their GitHub username instead of
a real name. These are the general problems being solved here as far
as I can tell.

On Mon, 10 May 2021 at 08:07, Sheng Wu  wrote:
>
> +0.2 to have ONLY optional GitHub ID on the ICLA.
> As an account of a commercial vendor, I don't think all of the contributors
> would always use the same GitHub IDs,
> Sometimes, they change before they don't want people to know what they were
> doing in OSS. Or they just simply forget the ID/password.
>
> If this was starting from helping the secretary, why don't we recommend the
> PMCs to share the private mail list perm list when sending the invitation?
> And provide an ICLA submission mail template to include this link for the
> secretary?
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Mike Drob  于2021年5月10日周一 下午8:50写道：
>
> > -1 the ICLA is a document that lives forever in our records and I’m much
> > less confident in the permanence of GH ids
> >
> > On Mon, May 10, 2021 at 4:12 AM Jarek Potiuk  wrote:
> >
> > > +1 for optional Github Id
> > >
> > > On Mon, May 10, 2021 at 11:08 AM Willem Jiang 
> > > wrote:
> > >
> > > > +1 to make it optional.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Mon, May 10, 2021 at 4:32 PM Bertrand Delacretaz
> > > >  wrote:
> > > > >
> > > > > On Sun, May 9, 2021 at 5:47 AM Justin Mclean <
> > jus...@classsoftware.com
> > > >
> > > > wrote:
> > > > > > ...Since recent projects trend to use GitHub and GitHub names
> > instead
> > > > of real
> > > > > > names. It can make it hard to match ICLAs to real people so I think
> > > it
> > > > > > makes sense to have it on the ICLA form. Best to probably make it
> > > > optional
> > > > > > as not everyone have a GitHub account...
> > > > >
> > > > > I agree that an optional GitHub username field might be useful but
> > IMO
> > > > > making it optional is a MUST.
> > > > >
> > > > > Requiring someone to have a GitHub account before they can get an
> > > > > Apache ID would be very wrong.
> > > > >
> > > > > -Bertrand
> > > > >
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > > >
> > >
> > > --
> > > +48 660 796 129
> > >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Update to ICLA to include github id

[Ismaël Mejía]

+1 for optional Github Id


On Mon, May 10, 2021 at 3:07 PM Sheng Wu  wrote:

> +0.2 to have ONLY optional GitHub ID on the ICLA.
> As an account of a commercial vendor, I don't think all of the contributors
> would always use the same GitHub IDs,
> Sometimes, they change before they don't want people to know what they were
> doing in OSS. Or they just simply forget the ID/password.
>
> If this was starting from helping the secretary, why don't we recommend the
> PMCs to share the private mail list perm list when sending the invitation?
> And provide an ICLA submission mail template to include this link for the
> secretary?
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Mike Drob  于2021年5月10日周一 下午8:50写道：
>
> > -1 the ICLA is a document that lives forever in our records and I’m much
> > less confident in the permanence of GH ids
> >
> > On Mon, May 10, 2021 at 4:12 AM Jarek Potiuk  wrote:
> >
> > > +1 for optional Github Id
> > >
> > > On Mon, May 10, 2021 at 11:08 AM Willem Jiang 
> > > wrote:
> > >
> > > > +1 to make it optional.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Mon, May 10, 2021 at 4:32 PM Bertrand Delacretaz
> > > >  wrote:
> > > > >
> > > > > On Sun, May 9, 2021 at 5:47 AM Justin Mclean <
> > jus...@classsoftware.com
> > > >
> > > > wrote:
> > > > > > ...Since recent projects trend to use GitHub and GitHub names
> > instead
> > > > of real
> > > > > > names. It can make it hard to match ICLAs to real people so I
> think
> > > it
> > > > > > makes sense to have it on the ICLA form. Best to probably make it
> > > > optional
> > > > > > as not everyone have a GitHub account...
> > > > >
> > > > > I agree that an optional GitHub username field might be useful but
> > IMO
> > > > > making it optional is a MUST.
> > > > >
> > > > > Requiring someone to have a GitHub account before they can get an
> > > > > Apache ID would be very wrong.
> > > > >
> > > > > -Bertrand
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > > >
> > >
> > > --
> > > +48 660 796 129
> > >
> >
>

Re: Update to ICLA to include github id

[Sheng Wu]

+0.2 to have ONLY optional GitHub ID on the ICLA.
As an account of a commercial vendor, I don't think all of the contributors
would always use the same GitHub IDs,
Sometimes, they change before they don't want people to know what they were
doing in OSS. Or they just simply forget the ID/password.

If this was starting from helping the secretary, why don't we recommend the
PMCs to share the private mail list perm list when sending the invitation?
And provide an ICLA submission mail template to include this link for the
secretary?

Sheng Wu 吴晟
Twitter, wusheng1108


Mike Drob  于2021年5月10日周一 下午8:50写道：

> -1 the ICLA is a document that lives forever in our records and I’m much
> less confident in the permanence of GH ids
>
> On Mon, May 10, 2021 at 4:12 AM Jarek Potiuk  wrote:
>
> > +1 for optional Github Id
> >
> > On Mon, May 10, 2021 at 11:08 AM Willem Jiang 
> > wrote:
> >
> > > +1 to make it optional.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Mon, May 10, 2021 at 4:32 PM Bertrand Delacretaz
> > >  wrote:
> > > >
> > > > On Sun, May 9, 2021 at 5:47 AM Justin Mclean <
> jus...@classsoftware.com
> > >
> > > wrote:
> > > > > ...Since recent projects trend to use GitHub and GitHub names
> instead
> > > of real
> > > > > names. It can make it hard to match ICLAs to real people so I think
> > it
> > > > > makes sense to have it on the ICLA form. Best to probably make it
> > > optional
> > > > > as not everyone have a GitHub account...
> > > >
> > > > I agree that an optional GitHub username field might be useful but
> IMO
> > > > making it optional is a MUST.
> > > >
> > > > Requiring someone to have a GitHub account before they can get an
> > > > Apache ID would be very wrong.
> > > >
> > > > -Bertrand
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> >
> > --
> > +48 660 796 129
> >
>

Re: Update to ICLA to include github id

[Mike Drob]

-1 the ICLA is a document that lives forever in our records and I’m much
less confident in the permanence of GH ids

On Mon, May 10, 2021 at 4:12 AM Jarek Potiuk  wrote:

> +1 for optional Github Id
>
> On Mon, May 10, 2021 at 11:08 AM Willem Jiang 
> wrote:
>
> > +1 to make it optional.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, May 10, 2021 at 4:32 PM Bertrand Delacretaz
> >  wrote:
> > >
> > > On Sun, May 9, 2021 at 5:47 AM Justin Mclean  >
> > wrote:
> > > > ...Since recent projects trend to use GitHub and GitHub names instead
> > of real
> > > > names. It can make it hard to match ICLAs to real people so I think
> it
> > > > makes sense to have it on the ICLA form. Best to probably make it
> > optional
> > > > as not everyone have a GitHub account...
> > >
> > > I agree that an optional GitHub username field might be useful but IMO
> > > making it optional is a MUST.
> > >
> > > Requiring someone to have a GitHub account before they can get an
> > > Apache ID would be very wrong.
> > >
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>
> --
> +48 660 796 129
>

[PROPOSAL] homepages + mailing lists for communities of interests

[Bertrand Delacretaz]

Hi,

Following up on recent discussions I have created a proposal here:

https://cwiki.apache.org/confluence/display/COMDEV/Communities+of+Interests+hosted+by+the+comdev+PMC

Feedback is welcome and I'm planning to put it up for vote by the
comdev PMC members once discussion is over, ideally next Monday.

The gist of it is: comdev offers a homepage under
community.apache.org/c/ and a mailing list at
@community.apache.org for communities of interests of ASF
projects if they can provide 3 ASF Members to oversee those resources.

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Comdev web pages for our communities of interests?

[Bertrand Delacretaz]

Hi,

On Wed, May 5, 2021 at 12:10 AM Daniel Ruggeri  wrote:
> I am reminded that projects.apache.org has metadata classifications as well. 
> Perhaps using that data more effectively could be another option? ..

I think projects.a.o is really about metadata - it could include links
to a project's communities of interests once those are created, but
for the communities homepages I think community.apache.org/c/ is
better, especially as it's very easy to manage.

I have now prepared a proposal on the wiki, will point to it in a new thread.

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Comdev web pages for our communities of interests?

[Javi Roman]

Greg,

The healthc...@apache.org request (selfservice) has been my fault, I have
asked a PMC Chair to create the list. I apologize, I thought it was
something proposed to create and to begin with.

--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Mon, May 10, 2021 at 11:34 AM Bertrand Delacretaz 
wrote:

> On Mon, May 10, 2021 at 11:16 AM Greg Stein  wrote:
> > ...Also please note that a mailing list named healthc...@apache.org was
> > requested. Infra has deleted that request. Please keep requests within
> > the @community space...
>
> I assume by "within the @community space" you mean that
> healthc...@community.apache.org is ok, assuming oversight by the
> comdev PMC.
>
> ( and we can create that ourselves via
> https://selfserve.apache.org/mail.html )
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: Comdev web pages for our communities of interests?

[Bertrand Delacretaz]

On Mon, May 10, 2021 at 11:16 AM Greg Stein  wrote:
> ...Also please note that a mailing list named healthc...@apache.org was
> requested. Infra has deleted that request. Please keep requests within
> the @community space...

I assume by "within the @community space" you mean that
healthc...@community.apache.org is ok, assuming oversight by the
comdev PMC.

( and we can create that ourselves via https://selfserve.apache.org/mail.html )

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Comdev web pages for our communities of interests?

[Greg Stein]

On Tue, May 04, 2021 at 09:45:36AM +0200, Bertrand Delacretaz wrote:
> Hi,
> 
> Recent discussions around a website for our projects which are in the
> healthcare "space" make me think that it would be useful to provide a
> space for such "project groups" which share common goals.
> 
> How about providing web pages, under the oversight of the Comdev PMC,
> for such things?
> 
> We could have community.apache.org/c/healthcare,
> community.apache.org/c/osgi, community.apache.org/c/buildtools, etc.,
> reserving community.apache.org/c as the root for that (as in
> "communities").

>From an Infrastructure perspective, this is basically your only
option.  Communities/PMCs only get one website/hostname for their
activities -- community.apache.org in this case.

An additional hostname is provided if the PMC requests a VM.
Typically, we provide up to one VM per PMC, but there are exceptions
(for example: I think that ComDev has more than one, and I know AOO
has several).

The basic reason is ownership. Infra and the world know who is
represented by community.a.o ... but creating something like
healthcare.a.o does not lead to an obvious owner.

Also please note that a mailing list named healthc...@apache.org was
requested. Infra has deleted that request. Please keep requests within
the @community space.

Cheers,
Greg Stein
Infrastructure Administrator, ASF

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Update to ICLA to include github id

[Jarek Potiuk]

+1 for optional Github Id

On Mon, May 10, 2021 at 11:08 AM Willem Jiang 
wrote:

> +1 to make it optional.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, May 10, 2021 at 4:32 PM Bertrand Delacretaz
>  wrote:
> >
> > On Sun, May 9, 2021 at 5:47 AM Justin Mclean 
> wrote:
> > > ...Since recent projects trend to use GitHub and GitHub names instead
> of real
> > > names. It can make it hard to match ICLAs to real people so I think it
> > > makes sense to have it on the ICLA form. Best to probably make it
> optional
> > > as not everyone have a GitHub account...
> >
> > I agree that an optional GitHub username field might be useful but IMO
> > making it optional is a MUST.
> >
> > Requiring someone to have a GitHub account before they can get an
> > Apache ID would be very wrong.
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

-- 
+48 660 796 129

Re: Update to ICLA to include github id

[Willem Jiang]

+1 to make it optional.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, May 10, 2021 at 4:32 PM Bertrand Delacretaz
 wrote:
>
> On Sun, May 9, 2021 at 5:47 AM Justin Mclean  wrote:
> > ...Since recent projects trend to use GitHub and GitHub names instead of 
> > real
> > names. It can make it hard to match ICLAs to real people so I think it
> > makes sense to have it on the ICLA form. Best to probably make it optional
> > as not everyone have a GitHub account...
>
> I agree that an optional GitHub username field might be useful but IMO
> making it optional is a MUST.
>
> Requiring someone to have a GitHub account before they can get an
> Apache ID would be very wrong.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Update to How it Works for developers/contributors

[Bertrand Delacretaz]

Hi,

On Sun, May 9, 2021 at 2:58 AM Craig Russell  wrote:
> ...So perhaps we could add a section on "contributors" that covers the other 
> categories of non-developer contributors?..

Note that the "developer" section at [1] already says "A developer is
a user who contributes to a project in the form of code or
documentation." so I think it can just be extended with a note that
mentions other types of contributions besides code and documentation.

And maybe also in the committer section mention that it's not
necessarily about committing code but also being "committed" to the
project by making other forms of contributions. Although the vast
majority of our committers do write code, those who don't are not
"second-class citizens".

> ...2. I believe that we should ask contributors for an ICLA long before they 
> are invited to become committers...

If you want to make that recommendation I think it belongs to
https://www.apache.org/dev/pmc.html - that's a PMC concern, not
directly related to how we work.

-Bertrand

[1] https://www.apache.org/foundation/how-it-works.html

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Update to ICLA to include github id

[Bertrand Delacretaz]

On Sun, May 9, 2021 at 5:47 AM Justin Mclean  wrote:
> ...Since recent projects trend to use GitHub and GitHub names instead of real
> names. It can make it hard to match ICLAs to real people so I think it
> makes sense to have it on the ICLA form. Best to probably make it optional
> as not everyone have a GitHub account...

I agree that an optional GitHub username field might be useful but IMO
making it optional is a MUST.

Requiring someone to have a GitHub account before they can get an
Apache ID would be very wrong.

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org