Elastic 社ã«ã‚ˆã‚‹ Elasticsearch ãŠã‚ˆã³ Kibana ã®ãƒ©ã‚¤ã‚»ãƒ³ã‚¹å¤‰æ›´ã«ã¨ã‚‚ãªã† AWS ã®å¯¾å¿œæ–¹é‡ã®ã”案内 | Amazon Web Services
Amazon Web Services ブãƒã‚° Elastic 社ã«ã‚ˆã‚‹ Elasticsearch ãŠã‚ˆã³ Kibana ã®ãƒ©ã‚¤ã‚»ãƒ³ã‚¹å¤‰æ›´ã«ã¨ã‚‚ãªã† AWS ã®å¯¾å¿œæ–¹é‡ã®ã”案内 先週ã€Elastic 社㌠Elasticsearch ãŠã‚ˆã³ Kibana ã®ãƒ©ã‚¤ã‚»ãƒ³ã‚¹å¤‰æ›´ã«é–¢ã™ã‚‹ã‚¢ãƒŠã‚¦ãƒ³ã‚¹ã‚’実施ã—ã¾ã—ãŸã€‚ã“ã‚Œã«ã‚ˆã‚Šãƒãƒ¼ã‚¸ãƒ§ãƒ³ 7.11 以é™ã® Elasticsearch 㨠Kibana ã¯ã€Apache License, Version 2.0 (ALv2) ã§ã®æä¾›ãŒè¡Œã‚ã‚Œã¾ã›ã‚“。ã“れをå—ã‘㦠AWS ã¯ã€2021/1/21 (PST) ã«å¯¾å¿œæ–¹é‡ã‚’発表ã„ãŸã—ã¾ã—ãŸã€‚本発表ã®è¦ç‚¹ã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚ AWS 㯠Elasticsearch 㨠Kibana ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ 7.10 をベース㫠fork ã—㟠Elasticsearch 㨠Kibana ã‚’ ALv2 ライセンスã«ã¦å…¬
[PATCH 000/190] Revertion of all of the umn.edu commits - Greg Kroah-Hartman
linux-kernel.vger.kernel.org archive mirror help / color / mirror / Atom feedFrom: Greg Kroah-Hartman <gregkh@linuxfoundation.org> To: linux[email protected] Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Linus Torvalds <torvalds@linux-foundation.org>, Aditya Pakki <[email protected]>, Kangjie Lu <[email protected]>, Qiushi Wu <[email protected]>, [email protected], Bjorn Helgaas <bhelgaas@googl
Subaru | Veoneer OSS
OSS generally means everyone is free to use it as long as you comply with the OSS license agreement. You must agree to the OSS license agreements of the copyright holders as listed in the product declarations if you want to use the source code for other purposes. OSS generally means everyone is free to use it as long as you comply with the OSS license agreement. You must agree to the OSS license a
最近見ã‹ã‘ã‚‹æ–°ã—ã„ライセンスã«ã¤ã„㦠- Kengo's blog
Elastic社ã®ãƒ–ãƒã‚°ã‚’ãã£ã‹ã‘ã«ã€æœ€è¿‘見ã‹ã‘ã‚‹æ–°ã—ã„ライセンスã«ã¤ã„ã¦å€‹äººçš„ã«èª¿ã¹ã¦ã¿ãŸã€‚ç§ã¯å°‚門家ã§ã¯ãªã„ã®ã§è¦æ³¨æ„ã€‚å…¬é–‹æƒ…å ±ã‚‚éš…ã€…ã¾ã§è¿½ãˆã¦ã„ã‚‹ã‚ã‘ã§ã¯ãªã„ã—。 ãªãŠä¸€éƒ¨ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã¯Open Source Initiative (OSI)ã«ã‚ˆã‚‹æ‰¿èªã‚’å—ã‘ã¦ã„ãªã„ã®ã§ã€ã“ã“ã§ã¯ã‚ªãƒ¼ãƒ—ンソースライセンスã§ã¯ãªãå˜ã«ã€Œãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã€ã¨æ›¸ãã“ã¨ã«ã™ã‚‹ã€‚ æ–°ã—ã„ライセンスãŒèª•ç”Ÿã—ã¦ã„る背景 従æ¥ã®ã‚ªãƒ¼ãƒ—ンソースライセンスãŒå†é ’布以外ã®åˆ©ç”¨ã‚’ã‚ã¾ã‚Šæƒ³å®šã—ã¦ã„ãªã‹ã£ãŸã€‚ Open-core modelãªã„ã—完全オープンソース戦略を採るä¼æ¥ãŒè‡ªè¡›ç–ã‚’å¿…è¦ã¨ã—ãŸã€‚ æ—¢å˜ã®ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ãŒé›£è§£ãªãŸã‚ã€ç†è§£ã—ã‚„ã™ã„ライセンスãŒæ±‚ã‚られãŸã€‚ OSS活動をåŽå…¥ã«ç¹‹ã’ã‚‹ãŸã‚ã®ãƒ¢ãƒ‡ãƒ«ãŒè©¦è¡ŒéŒ¯èª¤ã•ã‚Œã¦ã„る。 æ–°ã—ã„ライセンスを導入ã—ã¦ã„るプãƒã‚¸ã‚§ã‚¯ãƒˆï¼ˆä¸€ä¾‹ï¼‰ プãƒã‚¸ã‚§ã‚¯ãƒˆ ライセンス Elastic SSPLã¨ç‹¬è‡ªãƒ©ã‚¤
Amazon: NOT OK - why we had to change Elastic licensing
Search and analytics, data ingestion, and visualization – all at your fingertips.
ï¼»é€Ÿå ±ï¼½Googleã€å¤§æ‰‹ã‚¯ãƒ©ã‚¦ãƒ‰ã«ä¸æº€ã‚’表明ã—ã¦ã„ãŸMongoDBã€RedisらOSSベンダã¨æˆ¦ç•¥çš„ææºã€‚Google Cloudã«OSSベンダã®ãƒžãƒãƒ¼ã‚¸ãƒ‰ã‚µãƒ¼ãƒ“スを統åˆã€‚Google Cloud Next '19
ï¼»é€Ÿå ±ï¼½Googleã€å¤§æ‰‹ã‚¯ãƒ©ã‚¦ãƒ‰ã«ä¸æº€ã‚’表明ã—ã¦ã„ãŸMongoDBã€RedisらOSSベンダã¨æˆ¦ç•¥çš„ææºã€‚Google Cloudã«OSSベンダã®ãƒžãƒãƒ¼ã‚¸ãƒ‰ã‚µãƒ¼ãƒ“スを統åˆã€‚Google Cloud Next '19 Googleã¯ã‚µãƒ³ãƒ•ãƒ©ãƒ³ã‚·ã‚¹ã‚³ã§ã‚¤ãƒ™ãƒ³ãƒˆã€ŒGoogle Cloud Next '19ã€ã‚’開催。4月9日（日本時間4月10日未明）ã«è¡Œã£ãŸã‚ªãƒ¼ãƒ—ニングã‚ーノートã§ã€MongoDBã€Redisã€Confluentã€Elasticã‚’ã¯ã˜ã‚ã¨ã™ã‚‹ã‚ªãƒ¼ãƒ—ンソースソフトウェアベンダã¨ã®æˆ¦ç•¥çš„ææºã‚’発表ã—ã¾ã—ãŸã€‚ ææºç›¸æ‰‹ã¯Confluentã€DataStaxã€Elasticã€InfluxDataã€MongoDBã€Neo4jã€Redis Labsã®7社。 ã“ã®ææºã®ä¸‹ã§ã€Googleã¯ã‚ªãƒ¼ãƒ—ンソースソフトウェアベンダãŒæä¾›ã™ã‚‹ãƒžãƒãƒ¼ã‚¸ãƒ‰ã‚µãƒ¼ãƒ“スをGoogle Cloudã«çµ±åˆã€‚ユーザーã¯G
AWS and Open Source: It's Complicated - Redis
It’s that time of the year again. No, I’m not referring to the winter holidays, but to the reverberations of the announcements coming out of AWS re:Invent. Oftentimes when AWS makes a big move, IT ecosystems get shaken. In the database space, this year the effect focused on Apache Cassandra, after AWS announced a Cassandra-compatible serverless managed solution. Along with the announcement, AWS al
NGINX強制æœæŸ»ã‚ãã‚‹éžé›£å—ã‘ã€RamblerãŒåˆ‘事告訴を撤回ã¸
å°åˆ·ã™ã‚‹ メールã§é€ã‚‹ テã‚スト HTML é›»åæ›¸ç± PDF ダウンãƒãƒ¼ãƒ‰ テã‚スト é›»åæ›¸ç± PDF クリップã—ãŸè¨˜äº‹ã‚’Myページã‹ã‚‰èªã‚€ã“ã¨ãŒã§ãã¾ã™ Ramblerã¯ã€ã‚ªãƒ¼ãƒ—ンソースコミュニティやãƒã‚·ã‚¢å›½å†…ã®æŠ€è¡“コミュニティã‹ã‚‰ã®æ¿€ã—ã„å発をå—ã‘ã¦ã€ä¸–界的ã«åˆ©ç”¨ã•ã‚Œã¦ã„るウェブサーãƒãƒ¼ã®é–‹ç™ºå…ƒã§ã‚ã‚‹NGINX, Incã«å¯¾ã™ã‚‹åˆ‘事告訴を撤回ã™ã‚‹ã“ã¨ã«ãªã£ãŸã¨ã„ã†ã€‚ åŒç¤¾ã¯ä»Šå¾Œã€æ°‘事訴訟ã§NGINXã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã®æ‰€æœ‰æ¨©ã‚’追求ã™ã‚‹è€ƒãˆã ã¨Ramblerã®åºƒå ±æ‹…当者ã¯ç±³ZDNetã«è¿°ã¹ãŸã€‚ ã“ã®æ±ºå®šã¯ã€ç¾åœ°æ™‚é–“12月16æ—¥åˆå‰ã«é–‹å‚¬ã•ã‚ŒãŸRamblerã®å–ç· å½¹ä¼šã§ä¸‹ã•ã‚ŒãŸã€‚ã“ã®å–ç· å½¹ä¼šã¯ã€ãƒã‚·ã‚¢æœ€å¤§ã®éŠ€è¡Œã®1ã¤ã§ã‚ã‚Šã€Ramblerã®ç†é æ ªä¸»ï¼ˆæŒã¡æ ªæ¯”率46.5％）ã§ã‚‚ã‚ã‚‹Sberbankã®æ±‚ã‚ã§é–‹ã‹ã‚ŒãŸã‚‚ã®ã 。 SberbankãŒæ‹›é›†ã—ãŸå–ç· å½¹ä¼šã«å…ˆç«‹ã¤é€±æœ«ã«ã¯ã€ãƒã‚·ã‚¢ã®æŠ€è¡“コミュニテ
ã»ã“ã‚ã³ã¦ã„ãコミュニティã¨ãªã‹ãªã‹ã§ããªã„世代交代ã€ãã—ã¦ã•ã‚ˆãªã‚‰ã‚¢ãƒ‰ãƒ™ãƒ³ãƒˆã‚«ãƒ¬ãƒ³ãƒ€ãƒ¼ - Qiita
追記: 以下ã®æ–‡ç« ã«å¯¾ã—ã¦ä½è—¤åºƒç”Ÿå…ˆç”ŸãŒè‡ªã‚‰ã®ä½“験ã«å³ã—ãŸæ„見を述ã¹ã¦ãŠã‚‰ã‚Œã¾ã™ã€‚ãœã²ä¸€èªã‚’ãŠå‹§ã‚ã—ã¾ã™ã€‚ 昨年2015å¹´ã«jp.freebsd.orgドメインã®çµ‚焉ã«ä¼´ã„地域技術コミュニティã®å½¹å‰²ã¨ã„ã†ãƒã‚¨ãƒ を書ã„ãŸã€‚今年ã®ã¯ãã®ç¶šç·¨ã§ã‚る。ã“ã‚“ãªãƒã‚¨ãƒ を書ãã®ã‚‚今年ã§æœ€å¾Œã«ã—ãŸã„。 51æ³ã‚’越ãˆãŸã‚ªãƒƒã‚µãƒ³ãŒPort maintainerã‚’ã‚„ã‚‹çŠ¶æ³ ä»Šå¹´2016å¹´ã¯åˆã‚ã¦FreeBSDã®Port maintainerã«ãªã£ãŸã€‚devel/git-lfsã¨japanese/dbskkd-cdbã®2ã¤ã«ã¤ã„ã¦ã§ã‚る。ã©ã¡ã‚‰ã‚‚自分ã®ä»•äº‹ã«å¿…è¦ã ã£ãŸãŒã€å‰ã®maintainerãŒä½œæ¥ã‚’ã—ãªã„ã¾ã¾ã‹ã€ã‚ã‚‹ã„ã¯ä»–ã®äº‹æƒ…ã§maintainerä¸åœ¨ã®çŠ¶æ…‹ã«ãªã£ãŸã‹ã€ã¨ã„ã†äº‹æƒ…ã‹ã‚‰ã§ã‚ã‚‹1。 Port maintainerã‚’ã‚„ã‚‹ã“ã¨è‡ªèº«ã«ã¯ç•°å˜ã¯ãªã„。日本ã«ã‚‚TeXLiveã®Portsを仕切ã£ã¦ãŠã‚‰ã‚Œã‚‹ä½
é–“é•ã£ãŸPerlコミュニティã®å¥³æ€§ã®ç›®ç«‹ãŸã›ã‹ãŸ - ã©ã‚“ãžã“日誌(2012-07-29)
* [Perl] é–“é•ã£ãŸPerlコミュニティã®å¥³æ€§ã®ç›®ç«‹ãŸã›ã‹ãŸ 今月åˆã‚ã€CPANã‹ã‚‰ã‚ã‚‹AcmeモジュールãŒå‰Šé™¤ã•ã‚Œã¾ã—ãŸã€‚ãã—ã¦ExtUtils::MakeMakerãªã©ã§æœ‰åãªSchwernæ°ãŒãã®ã“ã¨ã«ã¤ã„ã¦How Not To Highlight Women In Perlã¨ã„ã†è¨˜äº‹ã‚’書ã„ã¦ã„ã¾ã—ãŸã€‚ç§ã¯ã€ŽAcme大全2012ã€ã‚’ã¤ãる準備ã®éŽç¨‹ã§ã“ã®ä¸€é€£ã®ã‚„ã‚Šã¨ã‚Šã‚’ã¿ã¦ã€è€ƒãˆã•ã›ã‚‰ã‚Œã€ç´¹ä»‹ã—ãŸã„ãªã¨æ€ã„ã¾ã—ãŸã€‚ãã“ã§æœ¬äººã®äº†è§£ã‚’å¾—ã¦ã“ã“ã«ç¿»è¨³ã—ãŸã‚‚ã®ã‚’掲載ã—ã¾ã™ï¼ˆã€ŽAcme大全2012ã€ã®ä»˜éŒ²ã«ã‚‚掲載ã—ã¦ã„ã¾ã™ï¼‰ã€‚モジュールåãŒAcmeã¾ã§å‡ºã¦ã—ã¾ã£ã¦æœ¬æ¥ã®è¨˜äº‹ã®è¶£æ—¨ã«åŽ³å¯†ã«ã¯åã—ã¦ã„ã‚‹ã®ã§ã™ãŒã€ã”寛æ•ãã ã•ã„（本人ã«ã¯ã©ã¡ã‚‰ã«ã‚‚掲載ã™ã‚‹ã“ã¨ã®äº†è§£ã‚’å—ã‘ã¦ã¾ã™ï¼‰ã€‚ é–“é•ã£ãŸPerlコミュニティã®å¥³æ€§ã®ç›®ç«‹ãŸã›ã‹ãŸ è¦ç´„：ジェンダーã®åŒ¿å性ã¯é˜²å¾¡ã§ã‚る。男性ãŒå„ªä½ãªã‚³ãƒŸãƒ¥ãƒ‹ãƒ†
How Not To Highlight Women In Perl | Schwern [blogs.perl.org]
Here's the short version: gender anonymity is protection, and in a male-dominated community many women prioritize safety. A machine parsible list of female CPAN authors threatens their anonymity even if they're not on it. Here's the even shorter version: highlighting gender is advanced and should not be done lightly. A module was recently uploaded to CPAN whose aim was to provide a big list of fem
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Understanding the History of Linux - Tero Roponen (tero141209.ppt)
Elastic and Amazon Reach Agreement on Trademark Infringement Lawsuit
GitHub Copilot · Your AI pair programmer
Domain error
Doubling down on open, Part II
Managed Cassandra on AWS, Our Take
Linux tako's homepage
386BSD
Geek Women Japan keynote
{{#tags}}- {{label}}
{{/tags}}