https://issues.apache.org/jira/browse/HADOOP-17169
I don't really know who the people are to review this patch, but it removes
all non-inclusive terminology from Hadoop Common. This ends up changing
some things in some other projects (mostly HDFS) as well since they depend
on stuff from hadoop-com
Hi Eric and Carlo,
Thanks for taking the initiative! I am willing to take this task up for
improving the Ozone codebase.
I have cloned the task and sub-tasks for Ozone -
https://issues.apache.org/jira/browse/HDDS-4050
- Vivek Subramanian
On Thu, Jul 30, 2020 at 3:54 PM Eric Badger
wrote:
> Th
Thanks for the responses, Jon and Carlo!
It makes sense to me to prevent future patches from re-introducing the
terminology. I can file a JIRA to add the +1/-1 functionality to the
precommit builds.
As for splitting up the work, I think it'll probably be easiest and
cleanest to have an umbrella f
Thanks again Eric for leading the charge. As for whether to chop it up or
keep it in fewer patches, I think it primarily impact the conflict surface
with dev branches and other in-flight development. More patches are likely
creating more localized clashes (as in I clash with a smaller patch, which
Thanks, Eric. I like this proposal and I'm glad this work is getting
traction. A few thoughts on implementation.
Once the fix is done, I think it will be necessary to ensure these language
restrictions are enforced at the patch level. This will +1/-1 patches that
introduce terminology that violate
I have created https://issues.apache.org/jira/browse/HADOOP-17168 to remove
non-inclusive terminology from Hadoop. However I would like input on how to
go about putting up patches. This umbrella JIRA is under Hadoop Common, but
there are sure to be instances in YARN, HDFS, and Mapreduce. Should I
c
RE Mentorship: I think the Mentorship program is an interesting idea. The
concerns with these efforts is always the follow-through. If you can find a
group of folks that are motivated and will work on this I think it could be
a great idea, especially if you focus on a diverse set of mentees, and th
+1, this is great folks.
In addition to that initiative, Do you think there is a chance to
launch a "*Hadoop
Mentorship Program for Minority Students*"
*The program will work as follows:*
- Define a programme committee to administrate and mentor candidates.
- The Committee defines a timeli
Thanks Carlo and Eric for the initiative.
I am all for it and I'll do my part to mind the code. This is a small yet
meaningful step we can take. Meanwhile, I'd like to take this opportunity
to open up conversation around the Diversity & Inclusion within the
community.
If you read this quarter's H
Eric,
Thank you so much for the support and for stepping up offering to work on
this. I am super +1 on this. Let's give folks a few more days to chime in,
in case there is anything to discuss before we get cracking!
(Really) Thanks,
Carlo
On Fri, Jul 10, 2020, 10:38 AM Eric Badger wrote:
> Tha
Thanks for writing this up, Carlo. I'm +1 (idk if I'm technically binding
on this or not) for the changes moving forward and I think we refactor away
any instances that are internal to the code (i.e. not APIs or other things
that would break compatibility) in all active branches and then also chang
Hello Folks,
I hope you are all doing well...
*The problem*
The recent protests made me realize that we are not just a bystanders of
the systematic racism that affect our society, but we are active
participants of it. Being "non-racist" is not enough, I strongly feel we
should be actively "anti-r
12 matches
Mail list logo
