url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://opensource.guide/ro/starting-a-project/ | Pornind un proiect cu sursă deschisă | Open Source Guides Despre Contribuie العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Pornind un proiect cu sursă deschisă Învață mai multe despre lumea open source și pregătește-te să-ți lansezi primul proiect. Cuprins „Care”-urile și „de ce”-urile open source Ar trebui să-mi lansez propriul meu proiect cu sursă deschisă? Lansându-ți propriul tău proiect cu sursă deschisă Numirea și marcarea proiectului tău Lista ta de verificări înainte de lansare „Care”-urile și „de ce”-urile open source Deci te gândești la a începe cu open source? Felicitări! Lumea îți apreciază contribuția. Haide să discutăm despre ce este open source și de ce oamenii fac asta. Ce înseamnă „open source”? Când un proiect este cu sursă deschisă, aceasta înseamnă că oricine poate vizualiza, utiliza, modifica și distribui proiectul tău în orice scop. Aceste permisiuni sunt impuse printr-o licență open source . Open source este puternic deoarece coboară barierele în calea adoptării, permițând ideilor să se răspândească repede. Pentru a înțelege cum funcționează, imaginează-ți că prietenul tău la cină are ghiveci, și tu aduci o plăcintă cu cireșe. Toată lumea încearcă plăcinta ( folosește ) Plăcinta este un hit! Ei îți cer rețeta, pe care o furnizezi ( vizualizează ) Un prieten, Alex, care este un bucătar de patiserie, sugerează reducerea zahărului ( modifică ) Un alt prieten, Lisa, cere să o folosească pentru o cină săptămâna viitoare ( distribuie ) Prin comparație, într-un proces cu sursă închisă mergi la un restaurant și comanzi o felie de plăcintă cu cireșe. Trebuie să plătești o taxă pentru a mânca plăcinta, și restaurantul probabil nu-ți va da rețeta lui. Dacă ai copia plăcinta lui exact și ai vinde-o cu un nume al tău, restaurantul ar putea lua măsuri împotriva ta. De ce oamenii deschid sursa muncii lor? Cele mai recompensante experiențe pe care le scot din folosirea și colaborarea pe open source vin din relațiile pe care le construiesc cu alți dezvoltatori care fac față la multe din aceleași probleme pe care le întâmpin eu. One of the most rewarding experiences I get out of using and collaborating on open source comes from the relationships that I build with other developers facing many of the same problems I am. — @kentcdodds, “How getting into Open Source has been awesome for me” Există numeroase motive pentru care o persoană sau o organizație ar dori să deschidă sursa unui proiect. Exemplele includ: Colaborarea: Proiectele cu sursă deschisă pot accepta schimbări de la oricine din lume. Exercism , de exemplu, este o platformă de exerciții de programare cu peste 350 de contributori. Adoptarea și remixarea: Proiectele cu sursă deschisă pot fi folosite de oricine pentru aproape orice scop. Oamenii le pot folosi chiar și pentru a construi alte lucruri. WordPress , de exemplu, a început ca o bifurcație a unui proiect existent numit b2 . Transparența: Oricine poate inspecta un proiect cu sursă deschisă pentru erori sau neconcordanțe. Transparența contează pentru guverne, cum ar fi Bulgaria sau Statele Unite , industrii reglementate cum ar fi sectorul bancar sau asistența medicală, și software-uri de securitate cum ar fi Let’s Encrypt . Open source nici nu este doar pentru software. Poți deschide sursa a orice de la seturi de date la cărți. Aruncă o privire la GitHub Explore pentru idei despre sursa a ce altceva poți deschide. Cu sursă deschisă înseamnă „gratuit”? Una dintre cele mai mari remize ale open source este că nu costă bani. Cu toate acestea, „gratuit” este un produs secundar al valorii totale a open source. Deoarece o licență de sursă deschisă cere ca oricine să poată folosi, modifica, și distribui proiectul tău pentru aproape orice scop, proiectele însele tind să fie gratuite. Dacă un proiect costă bani pentru a fi folosit, oricine ar putea face o copie în mod legal și să folosească versiunea gratuită în loc. Ca rezultat, cele mai multe proiecte cu sursă deschisă sunt gratuite, dar „gratuit” nu este parte din definiția open source. Există căi de a taxa pentru proiecte cu sursă deschisă indirect prin licențiere duală sau facilități limitate, în timp ce încă respectă definiția oficială a sursei deschise. Ar trebui să-mi lansez propriul meu proiect cu sursă deschisă? Răspunsul scurt este da, deoarece indiferent de rezultat, lansarea propriului tău proiect este o modalitate excelentă de a învăța cum open source lucrează. Dacă nu ai deschis sursa niciunui proiect înainte, ai putea fi stresat de ce oamenii vor spune, sau dacă măcar cineva va observa. Dacă aceasta sună ca tine, nu ești singur! Munca pe sursă deschisă este ca oricare altă activitate creativă, fie că este scriere sau pictură. Poate părea înfricoșător să împarți munca ta cu lumea, dar singura cale de a deveni mai bun este să practici - chiar dacă nu ai o audiență. Dacă nu ești încă convins, fă-ți o clipă să te gândești la care ar putea fi scopurile tale. Stabilirea obiectivelor Scopurile pot să te ajute să-ți dai seama pe ce să lucrezi, la ce să spui nu, și unde să ceri ajutor de la alții. Începe prin a te întreba, de ce deschid sursa acestui proiect? Nu există un răspuns singur corect la această întrebare. Ai putea avea multiple scopuri pentru un singur proiect, sau proiecte diferite cu scopuri diferite. Dacă propriul tău scop este să îți arăți munca, poate nici nu vei vrea contribuții, și poate chiar vei spune asta în README. Pe de altă parte, dacă tu vrei contributori, vei investi timp într-o documentație clară și în a face noii veniți să se simtă bineveniți. La un moment dat am creat un UIAlertView personalizat pe care îl foloseam... și am decis să-i deschid sursa. Astfel că l-am modificat să fie mai dinamic și l-am încărcat pe GitHub. De asemenea am scris prima mea documentație explicând altor dezvoltatori cum să-l folosească în proiectele lor. Probabil nimeni nu l-a folosit deoarce era un proiect simplu dar m-am simțit bine din cauza contribuției mele. At some point I created a custom UIAlertView that I was using...and I decided to make it open source. So I modified it to be more dynamic and uploaded it to GitHub. I also wrote my first documentation explaining to other developers how to use it on their projects. Probably nobody ever used it because it was a simple project but I was feeling good about my contribution. — @mavris, “Self-taught Software Developers: Why Open Source is important to us” Pe măsură ce proiectul tău crește, comunitatea ta poate avea nevoie de mai mult decât doar cod din partea ta. Răspunzând la probleme, analizând cod, și promovând proiectul sunt toate sarcini importante într-un proiect cu sursă deschisă. În timp ce timpul pe care îl cheltuiți pe sarcini care nu sunt legate de programare va depinde de mărimea și scopul proiectului tău, tu ar trebui să fii pregătit în calitate de întreținător să te adresezi lor tu însuți sau să găsești pe cineva să te ajute. Dacă ești parte dintr-o companie care deschide sursa unui proiect, asigurați-vă că proiectul vostru are resursele interne de care are nevoie să prospere. Veți dori să identificați cine este responsabil pentru întreținerea proiectului după lansare, și cum veți împărți aceste sarcini cu comunitatea voastră. Dacă aveți nevoie de un buget dedicat sau de personal pentru promovare, logistică și menținerea proiectului, începeți aceste conversații devreme. Pe măsură ce începi să deschizi sursa proiectului tău, este important să te asiguri că procesele tale de gestionare iau în considerare contribuțiile și abilitățile comunității din jurul proiectului tău. Nu-ți fie frică să implici contributori care nu sunt angajați în afacerea ta în aspecte cheie ale proiectului — în special dacă ei contribuie frecvent. As you begin to open source the project, it's important to make sure that your management processes take into consideration the contributions and abilities of the community around your project. Don't be afraid to involve contributors who are not employed in your business in key aspects of the project — especially if they are frequent contributors. — @captainsafia, “So you wanna open source a project, eh?” Contribuind pe alte proiecte Dacă obiectivul tău este să înveți cum să colaborezi cu alții sau să înțelegi cum funcționează open source, consideră contribuirea la un proiect existent. Începe cu un proiect pe care deja îl folosești și iubești. Contribuind la un proiect poate fi atât de simplu ca și corectarea greșelilor gramaticale sau actualizarea documentației. Dacă nu ești sigur cum să începi ca un contributor, aruncă o privire peste Cum să contribui la open source? . Lansându-ți propriul tău proiect cu sursă deschisă Nu există timpul perfect pentru a deschide sursa muncii tale. Poți deschide o idee, o muncă în progres, sau după ani în care a fost cu sursă închisă. În general, ar trebui să deschizi sursa proiectului tău când te simți confortabil lăsându-i pe alții să vadă munca ta, să dea feedback asupra muncii tale. Indiferent de stadiul în care decizi să deschizi sursa proiectului, oricare proiect ar trebui să includă următoarea documentație: Licența de sursă deschisă README Direcții de contribuție Codul de conduită Ca și întreținător, aceste componente te vor ajuta să comunici așteptări, să gestionezi contribuții, și să protejezi drepturile legale ale tuturor (inclusiv ale tale). Ele cresc semnificativ șansele de a avea o experiență pozitivă. Dacă proiectul tău este pe GitHub, punerea acestor fișiere în directorul rădăcină cu numele de fișiere recomandate va ajuta GitHub să recunoască și automat să le ridice la suprafață pentru cititorii tăi. Alegerea unei licențe O licență de sursă deschisă garantează că alții pot folosi, copia, modifica, și contribui înapoi la proiectul tău fără repercursiuni. De asemenea te protejează de situații juridice lipicioase. Tu trebuie să incluzi o licență când lansezi un proiect cu sursă deschisă. Munca judiciară nu este distractivă. Veștile bune sunt că tu poți copia și lipi o licență existentă în depozitul tău. Îți va lua doar un minut pentru a proteja munca ta grea. MIT , Apache 2.0 , și GPLv3 sunt cele mai populare licențe de sursă deschisă, dar sunt și alte opțiuni din care să alegi. Când creezi un nou proiect pe GitHub, ți se dă opțiunea de a selecta o licență. Incluzând o licență de sursă deschisă îți va face proiectul GitHub open source. Dacă ai alte întrebări sau îngrijorări în legătură cu aspectele juridice de gestionare a unui proiect cu sursă deschisă, te-am acoperit . Scrierea unui README README-urile fac mai mult decât să explice cum să se folosească proiectul tău. Ele de asemenea explică de ce proiectul tău contează, și ce pot face utilizatorii cu acesta. În README-ul tău, încearcă să răspunzi următoarelor întrebări: Ce face acest proiect? De ce acest proiect este folositor? Cum să încep? Unde pot obține mai mult ajutor, dacă am nevoie de el? Poți să-ți folosești README-ul pentru a răspunde altor întrebări, cum ar fi cum tratezi contribuțiile, care sunt scopurile proiectului, și informații despre licențe și drepturi. Dacă tu nu vrei să accepți contribuții, sau proiectul tău nu este pregătit încă pentru producție, scrie aceste informații. Documentație mai bună înseamnă mai mulți utilizatori, mai puține cereri de asistență, și mai mulți contributori. (...) Ține minte că cititorii tăi nu sunt tu. Sunt oameni care ar putea veni la un proiect care au experiențe complet diferite. Better documentation means more users, less support requests, and more contributors. (...) Remember that your readers aren't you. There are people who might come to a project who have completely different experiences. — @tracymakes, “Writing So Your Words Are Read (video)” Uneori, oamenii evită scrierea unui README deoarece simt că proiectul este nefinalizat, sau ei nu vor contribuții. Acestea sunt toate motive foarte bune pentru a scrie unul. Pentru mai multă inspirație, încearcă să folosești ghidul „Make a README” al lui @dguo sau șablonul README al lui @PurpleBooth pentru a scrie un README complet. Când incluzi un fișier README în directorul rădăcină, GitHub îl va afișa automat pe pagina acasă a depozitului. Scrierea direcțiilor tale de contribuție Un fișier CONTRIBUTING spune audienței tale cum să participe în proiectul tău. De exemplu, tu ai putea include informații despre: Cum se înregistrează un raport de bug (încearcă folosirea șabloanelor de probleme și cereri de pull ) Cum se sugerează o nouă facilitate Cum se configurează mediul și se rulează testele În plus pe lângă detalii tehnice, un fișier CONTRIBUTING este o oportunitate de a comunica așteptările tale de la contribuții, cum ar fi: Tipurile de contribuții pe care le cauți Planul sau viziunea pentru proiect Cum contributorii ar trebui (sau nu) să ia legătura cu tine Folosind un ton cald și prietenos și oferind sugestii specifice pentru contribuții (cum ar fi scrierea documentației, sau facerea unui site web) poate parcurge o cale lungă pentru a face nou-veniții să se simtă bineveniți și entuziasmați să participe. De exemplu, Active Admin începe ghidul său de contribuire cu: Mai întâi de toate, îți mulțumesc pentru că ai considerat să contribui la Active Admin. Oamenii ca voi sunt cei care fac Active Admin o unealtă grozavă. First off, thank you for considering contributing to Active Admin. It’s people like you that make Active Admin such a great tool. În primele etape ale proiectului tău, fișierul tău CONTRIBUTING poate fi simplu. Ar trebui mereu să explici cum se raportează bug-uri sau înregistrează probleme, și oricare cerință tehnică (cum ar fi teste) pentru a face o contribuție. Cu timpul, ai putea adăuga alte întrebări puse des în fișierul tău CONTRIBUTING. Scriind aceste informații înseamnă că mai puțini oameni vă vor întreba aceleași întrebări de mai multe ori. Pentru mai mult ajutor cu scrierea fișierului tău CONTRIBUTING, aruncă o privire la șablonul de ghid de contribuire al @nayafia sau „How to Build a CONTRIBUTING.md” al @mozilla. Leagă către fișierul tău CONTRIBUTING din README-ul tău, astfel încât mai mulți oameni îl văd. Dacă amplasezi fișierul tău CONTRIBUTING în depozitul proiectului tău , GitHub va lega automat către fișierul tău când un contributor creează o problemă sau deschide o cerere de pull. Stabilirea unui cod de conduită Toți am avut experiențe în care am făcut față la ceva ce probabil era abuz fie ca un întreținător încercând să explice de ce ceva trebuia să fie într-un anumit fel, sau ca un utilizator... punând o întrebare simplă. (...) Un cod de conduită devine un document ușor referit și la care se poate lega, care indică faptul că echipa ta ia discursul constructiv foarte în serios. We’ve all had experiences where we faced what was probably abuse either as a maintainer trying to explain why something had to be a certain way, or as a user...asking a simple question. (...) A code of conduct becomes an easily referenced and linkable document that indicates that your team takes constructive discourse very seriously. — @mlynch, “Making Open Source a Happier Place” În cele din urmă, un cod de conduită ajută la stabilirea unor reguli de bază pentru comportament pentru participanții la proiectul tău. Acest lucru este valoros în special dacă lansezi un proiect cu sursă deschisă pentru o comunitate sau o companie. Un cod de conduită te împuternicește să facilitezi comportamentul sănătos, constructiv al comunității, ceea ce îți va reduce stresul în calitate de întreținător. Pentru mai multe informații, aruncă o privire la ghidul nostru privind codul de conduită . Pe lângă comunicarea modului în care te aștepți ca participanții să se comporte, un cod de conduită tinde să descrie de asemenea la cine se aplică aceste așteptări, când se aplică, și ce se face dacă o încălcare are loc. Aproape la fel ca licențele de sursă deschisă, sunt de asemenea și standarde în curs de dezvoltare pentru coduri de conduită, deci nu trebuie să vă scrieți propriul cod de conduită. Contributor Covenant este un cod de conduită care se introduce cu o singură mutare în proiecte și este utilizat de peste 40.000 de proiecte cu sursă deschisă , incluzând Kubernetes, Rails, și Swift. Indiferent de textul folosit, tu trebuie să fii pregătit să impui codul de conduită când e necesar. Lipește textul direct într-un fișier CODE_OF_CONDUCT în depozitul tău. Păstrează fișierul în directorul rădăcină al proiectului tău ca să fie ușor de găsit, și leagă înspre el din README-ul tău. Numirea și marcarea proiectului tău Marcarea este mai mult decât o siglă pâlpâitoare sau un nume de proiect atrăgător. Este despre cum vorbești despre proiectul tău, și la cine ajungi cu mesajul tău. Alegerea numelui potrivit Alege un nume care este ușor de memorat și, în mod ideal, dă o idee despre ce face proiectul. De exemplu: Sentry monitorizează aplicații pentru raportarea de accidente Thin este un server web Ruby rapid și simplu Dacă construiești peste un proiect existent, folosind numele lor ca prefix poate ajuta să clarifice ce face proiectul tău (de exemplu, node-fetch aduce window.fetch la Node.js). Consideră claritatea mai presus de toate. Jocurile de cuvinte sunt distractive, dar ține minte că unele glume ar putea să nu se traducă pentru alte culturi sau oameni cu experiențe diferite de ale tale. Unii din utilizatorii tăi potențiali ar putea fi angajați din companii: nu vrei să îi faci stânjeniți când trebuie să explice proiectul tău la muncă! Evitarea conflictelor de nume Caută proiecte cu sursă deschisă cu un nume asemănător , în special dacă împărțiți aceeași limbă sau ecosistem. Dacă numele tău se suprapune cu un proiect popular existent, ai putea confuziona audiența. Dacă dorești un site web, un Twitter, sau alte proprietăți să-ți reprezinte proiectul, asigură-te că poți obține numele dorite. În mod ideal, rezervă aceste nume acum pentru pacea minții, chiar dacă nu intenționezi să le folosești încă. Asigură-te că numele proiectului tău nu încalcă nicio marcă comercială. O companie ar putea să-ți ceară să dobori proiectul mai târziu, sau chiar să ia măsuri legale împotriva ta. Pur și simplu, nu merită riscul. Puteți verifica WIPO Global Brand Database pentru conflicte de mărci comerciale. Dacă ești la o companie, aceasta este una din lucrurile cu care echipa juridică te poate ajuta . În cele din urmă, fă o căutare Google rapidă pentru numele proiectului tău. Vor putea oamenii să găsească ușor proiectul tău? Apare alt lucru în rezultatele căutării pe care ai dori ca ei să nu îl vadă? Cum scrii (și programezi) îți afectează marca, de asemenea! De-a lungul vieții proiectului tău, veți face multă scriere: README-uri, tutoriale, documente pentru comunitate, răspunderea la probleme, poate chiar buletine informative și liste de email-uri. Fie că este vorba de documentație oficială sau de un email obișnuit, stilul tău de scriere este parte a mărcii proiectului tău. Consideră cum ai putea să ajungi la audiență și dacă acesta este tonul pe care dorești să-l transmiți. Am încercat să mă implic în toate firele de discuție din lista de email-uri, și să arăt comportament exemplar, fiind drăguț cu oamenii, luându-le în serios problemele și încercând în ansamblu să fiu de ajutor. După un timp, oamenii au rămas în jur nu doar pentru a pune întrebări, ci de asemenea pentru a ajuta cu răspunsurile, și spre bucuria mea completă, ei mi-au imitat stilul. I tried to be involved with every thread on the mailing list, and showing exemplary behaviour, being nice to people, taking their issues seriously and trying to be helpful overall. After a while, people stuck around not to only ask questions, but to help with the answering as well, and to my complete delight, they mimicked my style. — @janl despre CouchDB , “Sustainable Open Source” Folosirea unui limbaj cald și incluziv (cum ar fi „ei”, chiar când mă refeream la o singură persoană) poate face un drum lung în a face proiectul tău să fie simțit primitor de noii contributori. Lipește-te de limbajul simplu, fiindcă mulți din cititorii tăi ar putea să nu fie vorbitori nativi de engleză. Dincolo de modul în care scrii cuvinte, stilul tău de programare poate de asemenea deveni parte din marca proiectului tău. Angular și jQuery sunt două exemple de proiecte cu stiluri de programare și direcții de ghidare riguroase. Nu este necesar să scrii un ghid de stil pentru proiectul tău la început, și tu poți afla că te bucuri de a incorpora diferite stiluri de programare în proiectul tău oricum. Dar ar trebui să anticipezi cum stilurile de scriere și programare pot atrage sau descuraja diferite tipuri de oameni. Primele etape ale proiectului tău sunt oportunitatea ta de a stabili precedentul pe care dorești să îl vezi. Lista ta de verificări înainte de lansare Ești pregătit să deschizi sursa proiectului tău? Iată o listă de verificare pentru a te ajuta. Bifezi toate cutiile? Ești gata să pornești! Dă clic pe „publish” și mângâie-te pe spate. Documentație Proiectul are un fișier LICENSE cu o licență de sursă deschisă Proiectul are documentație de bază (README, CONTRIBUTING, CODE_OF_CONDUCT) Numele este ușor de memorat, dă o idee despre ce face proiectul tău, și nu intră în conflict cu un proiect existent, nici nu încalcă mărcile comerciale Coada de probleme este actualizată, cu problemele clar organizate și etichetate Cod Proiectul folosește convenții de cod consecvente și nume clare de funcții/metode/variabile Codul este clar comentat, documentând intenții și cazuri marginale Nu există materiale sensibile în istoria reviziilor, probleme, sau cereri de pull (de exemplu, parole sau alte informații non-publice) Oameni Dacă ești persoană fizică: Ai vorbit cu departamentul juridic și/sau înțelegi proprietatea intelectuală și politicile open source ale companiei tale (dacă ești un angajat undeva) Dacă sunteți o companie sau organizație: Ați vorbit cu departamentul juridic Aveți un plan de comercializare pentru a anunța și promova proiectul Cineva este angajat să gestioneze interacțiunile comunității (răspunderea la probleme, analizarea și îmbinarea cererilor de pull) Cel puțin două persoane au acces administrativ la proiect Ai făcut-o! Felicitări pentru prima ta deschidere a sursei unui proiect. Indiferent de rezultat, a lucra în public este un dar pentru comunitate. Cu fiecare commit, comentariu, și cerere de pull, tu creezi oportunități pentru tine și pentru alții de a învăța și a crește. Înapoi la toate ghidurile Ghiduri relevante Găsirea de utilizatori pentru proiectul tău Ajută-ți proiectul cu sursă deschisă să crească punându-l în mâinile utilizatorilor fericiți. Clădirea comunităților primitoare Construirea unei comunități care încurajează oamenii să folosească, să contribuie la, și să promoveze proiectul tău Scroll to Top Contribuie Dorești să sugerezi ceva? Acest conținut este cu sursă deschisă. Ajută-ne să-l îmbunătățim. Contribuie Păstrează legătura Fii primul care să audă despe ultimele sfaturi și resurse despre open source ale GitHub. Adresă de email fine print cu de și prieteni | 2026-01-13T09:29:14 |
https://opensource.guide/it/leadership-and-governance/ | Leadership e governo | Open Source Guides Chi siamo Contribuire العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Leadership e governo I progetti open source in crescita possono trarre vantaggio da regole formali per prendere decisioni. Contenuto Comprendere la gestione del tuo progetto in crescita Quali sono esempi di ruoli formali utilizzati nei progetti open source? Come formalizzo questi ruoli di leadership? Quando dovrei dare a qualcuno l’accesso per impegnarsi? Quali sono alcune delle strutture di governance comuni per i progetti open source? Ho bisogno di documenti gestionali quando inizio il mio progetto? Cosa succede se i dipendenti aziendali iniziano a inviare contributi? Comprendere la gestione del tuo progetto in crescita Il tuo progetto sta crescendo, le persone sono coinvolte e tu ti impegni a mantenere questa cosa. A questo punto, ti starai chiedendo come includere contributori regolari al progetto nel tuo flusso di lavoro, sia che si tratti di fornire accesso al commit o di risolvere i dibattiti della comunità. Se hai domande, abbiamo le risposte. Quali sono esempi di ruoli formali utilizzati nei progetti open source? Molti progetti seguono una struttura simile per quanto riguarda i ruoli dei contributori e il riconoscimento. Il significato effettivo di questi ruoli, tuttavia, dipende interamente da te. Ecco alcuni tipi di ruoli che potresti riconoscere: Supporto Associato Committente Per alcuni progetti, i “sostenitori” sono le uniche persone in un progetto con accesso come commit. In altri progetti, sono semplicemente le persone elencate nel README come manutentori. Un manutentore non deve essere qualcuno che scrive il codice per il tuo progetto. Potrebbe essere qualcuno che ha svolto molto lavoro per evangelizzare il tuo progetto o documentazione scritta che ha reso il progetto più accessibile agli altri. Indipendentemente da ciò che fa quotidianamente, un manutentore è probabilmente qualcuno che si sente responsabile della direzione del progetto e si impegna a migliorarlo. Un “Collaboratore” può essere chiunque commenti un problema o una richiesta pull, persone che aggiungono valore al progetto (che si tratti di valutare problemi, scrivere codice o organizzare eventi) o chiunque abbia una richiesta pull combinata (magari la definizione più ristretta di contributore). [Per Node.js,] ogni persona che sembra commentare un problema o inviare codice è un membro della comunità del progetto. Il solo fatto di poterli vedere significa che hanno superato il limite da utente a collaboratore. — @mikeal, “Healthy Open Source” Il termine “agente” può essere utilizzato per distinguere l’accesso all’impegno, che è un tipo specifico di responsabilità, da altre forme di contributo. Sebbene tu possa definire i ruoli del tuo progetto come desideri, considera l’utilizzo di definizioni più ampie per incoraggiare più forme di contributo. Puoi utilizzare i ruoli di leadership per riconoscere formalmente le persone che hanno apportato contributi eccezionali al tuo progetto, indipendentemente dalle loro competenze tecniche. Potresti conoscermi come l’“inventore” di Django… ma in realtà sono la persona che è stata assunta per lavorare su qualcosa un anno dopo che era già stato realizzato. (…) La gente sospetta che io abbia successo grazie alle mie capacità di programmazione… ma nella migliore delle ipotesi sono un programmatore medio. — @jacobian, “Nota chiave di PyCon 2015” (video) Come formalizzo questi ruoli di leadership? Formalizzare i ruoli di leadership aiuta le persone a sentirsi proprietarie e dice agli altri membri della comunità a chi rivolgersi per chiedere aiuto. Per un progetto più piccolo, designare i leader può essere semplice come aggiungere i loro nomi al file di testo README o CONTRIBUTORS. Per un progetto più ampio, se hai un sito web, crea una pagina del team o elenca lì i tuoi project manager. Ad esempio, Postgres ha una pagina completa del team con brevi profili di ciascun contributore. Se il tuo progetto ha una comunità di contributori molto attiva, puoi formare un “core team” di manutentori o anche sottocomitati di persone che si assumono la responsabilità di diverse aree problematiche (ad esempio sicurezza, classificazione dei problemi o comportamento della comunità). Consentire alle persone di auto-organizzarsi e fare volontariato per i ruoli che li appassionano di più, piuttosto che esternalizzarli. [Noi] integriamo la squadra principale con diverse “sotto-squadre”. Ogni sottoteam si concentra su un’area specifica, come la progettazione del linguaggio o le biblioteche. (…) Per garantire un coordinamento globale e una visione forte e coerente per il progetto nel suo insieme, ogni sotto-team è guidato da un membro del team principale. — “RFC per la gestione di Rust” I team dirigenti potrebbero voler creare un canale designato (come su IRC) o incontrarsi regolarmente per discutere del progetto (come su Gitter o Google Hangout). Puoi anche rendere pubbliche queste riunioni in modo che altre persone possano ascoltarle. Cucumber-ruby , ad esempio, prende ore di lavoro ogni settimana . Una volta stabiliti i ruoli di leadership, assicurati di documentare come le persone possono raggiungerli! Stabilisci un processo chiaro su come qualcuno può diventare un sostenitore o unirsi a un sottocomitato nel tuo progetto e scrivilo nel tuo GOVERNANCE.md. Strumenti come Vossibility possono aiutarti a tenere traccia pubblicamente chi sta (o non sta) contribuendo al progetto. Documentare queste informazioni evita la percezione della comunità secondo cui i manutentori sono una cricca che prende le proprie decisioni in privato. Infine, se il tuo progetto è su GitHub, valuta la possibilità di spostare il progetto dal tuo account personale a un’organizzazione e di aggiungere almeno un amministratore di backup. GitHub Organizations semplifica la gestione delle autorizzazioni e di più repository e protegge l’eredità del tuo progetto tramite proprietà condivisa . Quando dovrei dare a qualcuno l’accesso per impegnarsi? Alcune persone pensano che dovresti dare accesso al coinvolgimento a tutti coloro che danno un contributo. Ciò può incoraggiare più persone a sentirsi proprietarie del tuo progetto. D’altra parte, soprattutto per progetti più grandi e complessi, potresti voler concedere l’accesso al coinvolgimento solo alle persone che hanno dimostrato il proprio impegno. Non esiste un modo giusto per farlo: fai ciò che ti fa sentire più a tuo agio! Se il tuo progetto è su GitHub, puoi utilizzare rami protetti per gestire chi può puntare a un particolare ramo e in quali circostanze. Ogni volta che qualcuno ti invia una richiesta pull, consentigli l’accesso al tuo progetto. Anche se all’inizio può sembrare incredibilmente sciocco, l’utilizzo di questa strategia ti consentirà di liberare il vero potere di GitHub. (…) Una volta che le persone hanno accesso al commit, non si preoccupano più che la loro correzione possa essere disgregata… il che li porta a dedicarci molto più lavoro. — @felixge, “Хакът на заявка за изтегляне” Quali sono alcune delle strutture di governance comuni per i progetti open source? Esistono tre strutture di governance generale associate ai progetti open source. BDFL: BDFL sta per “Dittatore benevolo per la vita”. In questa struttura, una persona (di solito l’autore originale del progetto) ha l’ultima parola su tutte le principali decisioni del progetto. Python è un classico esempio. I progetti più piccoli probabilmente utilizzano BDFL per impostazione predefinita perché ci sono solo uno o due manutentori. Anche un progetto che nasce da un’azienda può rientrare nella categoria BDFL. Meritocrazia: (Nota: il termine “meritocrazia” ha connotazioni negative per alcune comunità e ha una storia sociale e politica complessa .) ** Nella meritocrazia ai partecipanti attivi al progetto (coloro che dimostrano “merito”) viene assegnato un ruolo decisionale formale. Le decisioni vengono solitamente prese sulla base del voto per puro consenso. Il concetto di meritocrazia è stato introdotto dalla Fondazione Apache ; tutti i progetti Apache sono meritocrazie. I contributi possono essere versati solo da individui che rappresentano se stessi e non da un’azienda. Contributo liberale: In un modello di contribuzione liberale, le persone che lavorano di più sono riconosciute come le più influenti, ma questo si basa sul lavoro attuale, non sul contributo storico. Le decisioni sui grandi progetti vengono prese sulla base di un processo di ricerca del consenso (discussione delle principali lamentele) piuttosto che sul puro voto, e cercano di includere quante più prospettive comunitarie possibile. Esempi popolari di progetti che utilizzano un modello di contribuzione liberale includono Node.js e Rust . Quale dovresti usare? Sta a te! Ogni modello presenta vantaggi e compromessi. E anche se a prima vista possono sembrare molto diversi, tutti e tre i modelli hanno più cose in comune di quanto sembri. Se sei interessato ad adottare uno di questi modelli, dai un’occhiata a questi modelli: BDFL model template Meritocracy model template Node.js’s liberal contribution policy Ho bisogno di documenti gestionali quando inizio il mio progetto? Non esiste un momento giusto per scrivere la gestione del tuo progetto, ma è molto più semplice definirlo una volta che hai visto svolgersi le dinamiche della tua comunità. La parte migliore (e più difficile) della gestione open source è che è modellata dalla comunità! Tuttavia, alcuni dei primi documenti contribuiranno inevitabilmente alla gestione del progetto, quindi inizia a registrare ciò che puoi. Ad esempio, puoi definire aspettative chiare sul comportamento o sul funzionamento del processo di collaborazione, anche all’inizio del tuo progetto. Se fai parte di un’azienda che lancia un progetto open source, vale la pena tenere una discussione interna prima del lancio su come la tua azienda prevede di supportare e prendere decisioni sui progressi del progetto. Potresti anche voler spiegare pubblicamente qualcosa di specifico su come la tua azienda sarà (o non sarà!) coinvolta nel progetto. Assegniamo a piccoli team la gestione dei progetti GitHub che effettivamente lavorano su di essi su Facebook. Ad esempio, React è gestito da un ingegnere React. — @caabernathy, “An inside look at open source at Facebook” Cosa succede se i dipendenti aziendali iniziano a inviare contributi? I progetti open source di successo vengono utilizzati da molte persone e aziende e alcune aziende potrebbero finire per avere flussi di entrate che sono in definitiva legati al progetto. Ad esempio, un’azienda può utilizzare il codice di progetto come componente nell’offerta di un servizio commerciale. Man mano che il progetto diventa più diffuso, le persone con esperienza in esso diventano più richieste: potresti essere uno di loro! - e talvolta verranno pagati per il lavoro svolto sul progetto. È importante considerare l’attività commerciale come una cosa normale e semplicemente come un’altra fonte di energia per lo sviluppo. Naturalmente, gli sviluppatori pagati non dovrebbero ricevere un trattamento speciale rispetto a quelli non pagati; ogni contributo dovrebbe essere giudicato in base ai suoi meriti tecnici. Tuttavia, le persone dovrebbero sentirsi a proprio agio nell’impegnarsi in attività commerciali e sentirsi a proprio agio nel citare i propri casi d’uso quando si discute a favore di un particolare miglioramento o funzionalità. “Commerciale” è pienamente compatibile con “open source”. “Commerciale” significa semplicemente che da qualche parte sono coinvolti dei soldi, che il software viene utilizzato commercialmente, il che è sempre più probabile man mano che un progetto ottiene l’accettazione. (Quando il software open source viene utilizzato come parte di un prodotto non open source, il prodotto complessivo è ancora software “proprietario”, sebbene, come l’open source, possa essere utilizzato per scopi commerciali e non commerciali.) Come chiunque altro, gli sviluppatori motivati dal punto di vista commerciale ottengono influenza nel progetto attraverso la qualità e la quantità del loro contributo. Ovviamente, un programmatore che viene pagato per il suo tempo può essere in grado di guadagnare più di qualcuno che non lo fa, ma va bene così: il pagamento è solo uno dei tanti possibili fattori che possono influenzare quanto qualcuno guadagna. Mantieni le discussioni del tuo progetto focalizzate sul contributo, non sui fattori esterni che consentono alle persone di dare quel contributo. Ho bisogno di una persona giuridica per sostenere il mio progetto? Non hai bisogno di un’entità legale per supportare il tuo progetto open source a meno che non gestisci denaro. Ad esempio, se desideri avviare un’attività commerciale, ti consigliamo di costituire una C Corp o LLC (se risiedi negli Stati Uniti). Se stai solo lavorando a un contratto relativo al tuo progetto open source, puoi accettare denaro come unico proprietario o formare una LLC (se risiedi negli Stati Uniti). Se desideri accettare donazioni per il tuo progetto open source, puoi impostare un pulsante di donazione (utilizzando PayPal o Stripe, ad esempio), ma il denaro non sarà deducibile dalle tasse a meno che tu non sia un’organizzazione no-profit qualificata (501c3, se sei sono negli Stati Uniti). Molti progetti non vogliono prendersi la briga di creare un’organizzazione no-profit, quindi trovano invece uno sponsor fiscale senza scopo di lucro. Uno sponsor fiscale accetta donazioni per tuo conto, solitamente in cambio di una percentuale della donazione. Software Freedom Conservancy , Apache Foundation , Eclipse Foundation , Linux Foundation e Open Collective sono esempi di organizzazioni che fungono da sponsor fiscali per progetti open source. Il nostro obiettivo è fornire infrastrutture che le comunità possano utilizzare per essere autosostenibili, creando così un ambiente in cui tutti — contributori, sostenitori, sponsor — ne traggano benefici concreti. — @piamancini, “Andare oltre la beneficenza” Se il tuo progetto è strettamente correlato a un particolare linguaggio o ecosistema, potrebbe esserci anche una base software associata con cui puoi lavorare. Ad esempio, la Python Software Foundation aiuta a supportare PyPI , il gestore pacchetti Python e [Node.js Foundation] (https://foundation.nodejs.org/) aiuta a mantenere Express.js , un framework basato su Node. Torna a tutte le guide Guide correlate Buone pratiche per i manutentori del codice. Semplificarti la vita come sostenitore dell’open source, dal processo di documentazione fino a ottenere il massimo dalla community. Metriche Open Source Prendi decisioni informate per aiutare il tuo progetto open source a prosperare misurando e monitorandone il successo. Scroll to Top Contribuire Vuoi dare un suggerimento? Questo contenuto è open source. Aiutaci a migliorarlo. Contribuire Rimani in contatto Sii il primo a conoscere gli ultimi suggerimenti e risorse open source su GitHub. Email fine print con da e [amici] | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/proxmox-ve/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Proxmox Virtual Environment | LinkedIn Skip to main content LinkedIn Proxmox Server Solutions in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Proxmox Virtual Environment Server Virtualization Software by Proxmox Server Solutions See who's skilled in this Add as skill Learn more Report this product About Proxmox Virtual Environment (Proxmox VE) is is the leading open-source platform for all-inclusive enterprise virtualization. With the central web interface, you can easily run VMs and containers, manage software-defined storage and networking functionality, high-availability clustering, and multiple integrated out-of-the-box tools like backup/restore, live migration, replication, and the firewall. Enterprises use the powerful all-in-one solution to meet the core requirements of today’s modern data centers. Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Proxmox Server Solutions products Proxmox Backup Server Proxmox Backup Server Server Backup Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/oracle-linux-oracle-virtualization/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | Oracle Virtualization | LinkedIn Skip to main content LinkedIn Oracle Linux in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Oracle Virtualization Server Virtualization Software by Oracle Linux See who's skilled in this Add as skill Learn more Report this product About Backed by affordable enterprise support for hybrid environments, Oracle Virtualization reduces operation and support costs while increasing IT efficiency and agility—on premises and in the cloud. This product is intended for Information Technology Manager System Administrator System Manager Director of Information Technology Chief Security Officer Chief Technology Officer Senior Information Technology Specialist Vice President Information Technology Media Products media viewer No more previous content Cisco cryptographic services team reduces cost of virtualization Learn more: https://oracle.com/linux Learn how the Cisco cryptographic services team lowered their virtualization cost, increased their uptime using Ksplice live patching, increased performance, and streamlined support by switching to Oracle Linux KVM and Virtualization Manager. Kata Containers and Security with Oracle Linux Learn about the differences between Kata Containers and other types of containers such as Docker and containerd, and when best to use them. Kata container support is included with Oracle Linux Premier support. Accelerate Your DevOps Processes with Oracle VM VirtualBox Oracle VM VirtualBox is an open source high-performance desktop virtualization software that makes it quick and easy to operate multi-platform test environments on a single machine, secure VMs, and easily deploy them to any cloud. No more next content Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Sign in to see more Show more Show less Oracle Linux products Oracle Autonomous Linux Oracle Autonomous Linux Operating Systems Oracle Linux Oracle Linux Operating Systems Oracle VirtualBox Oracle VirtualBox Virtual Desktop Infrastructure (VDI) Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://opensource.guide/ar/how-to-contribute/ | كيف تساهم في مشروع مفتوح المصدر ؟ | Open Source Guides عن المشروع ساهِم العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides كيف تساهم في مشروع مفتوح المصدر ؟ هل تريد أن تساهم في مشاريع مفتوحة المصدر؟ دليل للمبتدئين والمحترفين حول كيفية المساهمة فيها قائمة المحتويات لماذا تساهم في مشروع مفتوح المصدر؟ ما معنى المساهمة التعرف على مشروع جديد إيجاد مشروع للمساهمة فيه كيف ترسل المساهمة؟ ماذا يحدث بعد تقديم مساهمتك؟ لماذا تساهم في مشروع مفتوح المصدر؟ العمل على Freenode ساعدني على اكتساب الكثير من المهارات التي استخدمتها لاحقًا في دراستي الجامعية وفي عملي الفعلي. أعتقد أن العمل على مشاريع مفتوحة المصدر يساعدني بقدر ما يساعد المشروع! — @errietta , “Why cd opensourceI love contributing to open source software” المساهمة في مشاريع مفتوحة المصدر يمكن أن تكون تجربة مُجزية للتعلّم، والتعليم، واكتساب الخبرة في أيّ مهارة تقريبًا. لماذا يساهم الناس في مشاريع مفتوحة المصدر؟ هناك الكثير من الأسباب. تحسين البرمجيات التي تعتمد عليها يبدأ العديد من المساهمين كمستخدمين للبرامج التي يشاركون فيها. عندما تكتشف خطأً في برنامج مفتوح المصدر تستخدمه، قد ترغب في الاطّلاع على المصدر لترى إذا كان بإمكانك إصلاحه بنفسك. إذا كان هذا هو الحال، فإن تقديم التصحيح للمشروع هو أفضل وسيلة لضمان استفادة أصدقائك (وأنت نفسك عند التحديث إلى الإصدار التالي) من هذا الإصلاح. تطوير المهارات الحالية سواء كان الأمر يتعلق بالبرمجة، أو تصميم واجهة المستخدم، أو التصميم الجرافيكي، أو الكتابة، أو التنظيم — إذا كنت تبحث عن فرصة للتدريب، فهناك مهمة بانتظارك في أحد المشاريع مفتوحة المصدر. التعرف على أشخاص مهتمين في أشياء متشابهة المشاريع مفتوحة المصدر التي تمتلك مجتمعات لطيفة ومرّحبة تجذب الناس للاستمرار لسنوات. كثير من الأشخاص كوّنوا صداقات قويّة من خلال مشاركتهم في هذه المشاريع، سواء بلقائهم في المؤتمرات أو عبر محادثاتهم الليلية على الإنترنت. إيجاد مرشدين وتعليم الآخرين العمل مع الآخرين على مشروع مشترك، يعني أنك ستحتاج إلى شرح طريقة عملك، كما ستحتاج إلى طلب المساعدة من الآخرين. فإن عمليتَي التعلّم والتعليم يمكن أن تشكّلا نشاطًا مُرضيًا لجميع الأطراف. بناء أعمال عامة تساعدك على بناء سمعتك ومسارك المهني كل مساهماتك في المشاريع مفتوحة المصدر تكون عامة ومتاحة للجميع، مما يمنحك أمثلة عملية مجانية يمكنك استخدامها في أي مكان كدليل ملموس على مهاراتك وقدراتك. تعلُّم مهارات التعامل مع الآخرين تُقدّم المشاريع مفتوحة المصدر فرصاً ثمينة لممارسة مهارات القيادة والإدارة، مثل حل التعارضات، وتنظيم فرق العمل، وتحديد أولويات المهام. الشعور بالقدرة على إجراء تغييرات، حتى لو صغيرة، يعطيك إحساس بالقوة لا حاجة لأن تصبح مساهمًا مدى الحياة حتى تستمتع بالمشاركة في عالم المشاريع مفتوحة المصدر. هل سبق أن رأيت خطأً مطبعيًّا على موقع إلكتروني، وتمنيت لو أن أحدًا ما سيصححه؟ في مشروع مفتوح المصدر يمكنك أنت القيام بذلك. تساعد المشاريع مفتوحة المصدر الناس على الشعور بأن لديهم قدرة على التأثير في حياتهم وكيفية تجربتهم للعالم، وهذا بحد ذاته مُجزٍ. ما معنى المساهمة إذا كنت مساهمًا جديدًا في المشاريع مفتوحة المصدر، فقد تكون العملية مخيفة بعض الشيء. كيف تجد المشروع المناسب؟ ماذا لو كنت لا تعرف البرمجة؟ ماذا لو حدث خطأ ما؟ لا تقلق! هناك العديد من الطرق للمشاركة في مشروع مفتوح المصدر، وبعض النصائح البسيطة ستساعدك على تحقيق أقصى استفادة من تجربتك. لا تحتاج إلى المساهمة بالبرمجة من المفاهيم الخاطئة الشائعة حول المساهمة في المشاريع مفتوحة المصدر هو أنك بحاجة إلى المساهمة بالكود. في الواقع، غالبًا ما تكون الأجزاء الأخرى من المشروع هي الأكثر إهمالًا أو تجاهلًا . ستقدّم خدمة كبيرة للمشروع إذا عرضت المساعدة في هذا النوع من المساهمات! أنا معروف بعملي على CocoaPods لكن في الواقع، معظم الناس لا يعلمون أنني لا أقوم بأيّ عمل حقيقيّ على أداة CocoaPods نفسها. معظم وقتي في المشروع يُقضى في أمور مثل توثيق المشروع والعمل على (branding) بناء هُويّته. — @orta , “Moving to OSS by default” حتى لو كنت تحب كتابة الكود، فأنواع المساهمات الأخرى تُعد طريقة ممتازة للمشاركة في المشروع والتعرف على أعضاء المجتمع الآخرين. بناء هذه العلاقات سيفتح أمامك فرصًا للعمل على أجزاء أخرى من المشروع. هل تحب تنظيم الأحداث (events) ؟ نظّم ورش عمل، أو لقاءات حول المشروع , @fzamperin did for NodeSchool نظّم مؤتمر المشروع (إذا كان لديهم واحد) ساعد أعضاء المجتمع في العثور على المؤتمرات المناسبة وتقديم مقترحات للحديث فيها هل تحب التصميم؟ أعِد هيكلة التصاميم لتحسين قابلية استخدام المشروع نفّذ أبحاث تجربة المستخدم (user research) لإعادة تصميم هيكل التنقّل (navigation structure) والقوائم، like Drupal suggests أنشئ Style Guide لمساعدة المشروع على الحفاظ على تصميم بصري متّسق صمّم رسومات لل t-shirts أو شعارًا جديدًا للمشروع، like hapi.js’s contributors did هل تحب الكتابة؟ اكتُب وطوّر توثيق المشروع, like @CBID2 did for OpenSauced’s documentation نظّم مجلدًا يحتوي على أمثلة توضح كيفية استخدام المشروع أطلِق نشرة إخبارية للمشروع، أو نظّم أبرز المحتويات من قائمة البريد الإلكتروني, like @opensauced did for their product اكتب شروحات (Tutorials) للمشروع, like PyPA’s contributors did اكتب ترجمة لتوثيق المشروع, like @frontendwizard did for the instructions for freeCodeCamp’s CSS Flexbox challenge بجديّة، [التوثيق] مهم جدًّا. حتى الآن، كان التوثيق ممتازًا وكان ميزة قوية في Babel . هناك أقسام بالتأكيد يمكن تحسينها، وحتى إضافة فقرة هنا أو هناك تُقدّر كثيرًا. — @kittens, “Call for contributors” هل تحب التنظيم؟ اربط المشاكل المكررة واقترح تسميات جديدة للمشاكل (Issue Labels) ، للحفاظ على تنظيم المشروع راجع المشاكل المفتوحة (Open Issues) ، واقترح إغلاق المشاكل القديمة, like @nzakas did for ESLint اطرح أسئلة توضيحية على المشاكل التي فُتحت مؤخرًا لدفع النقاش قدمًا. هل تحب البرمجة؟ ابحث عن مشكلة مفتوحة لتعمل عليها, like @dianjin did for Leaflet اسأل إذا كان بإمكانك المساعدة في كتابة ميزة جديدة أتمتة إعداد المشروع (Project Setup) تحسين الأدوات أو الاختبارات (Tooling and Testing) هل تحب مساعدة الآخرين؟ أجب عن الأسئلة المتعلقة بالمشروع، على سبيل المثال: Stack Overflow ( like this Postgres example ) أو Reddit أجب على أسئلة الأشخاص المتعلقة بالمشاكل المفتوحة ساعد في إدارة ومراقبة قنوات التواصل والمجتمعات التقنية هل تحب مساعدة الآخرين في البرمجة؟ اجع الكود في مساهمات الآخرين اكتب شروحات حول كيفية استخدام المشروع اعرض الإشراف أو التوجيه على مساهم آخر, like @ereichert did for @bronzdoc on Rust لست مضطرًا للعمل على مشاريع برمجية فقط! رغم أن مصطلح (Open Source) غالبًا ما يشير إلى البرمجيات، إلا أنه يمكنك المساهمة في أي شيء تقريبًا. هناك كتب، وصفات، قوائم، ودروس يتم تطويرها كمشاريع مفتوحة المصدر. على سبيل المثال: @sindresorhus curates a list of “awesome” lists @h5bp maintains a list of potential interview questions for front-end developer candidates @stuartlynn and @nicole-a-tesla made a collection of fun facts about puffins حتى لو كنت مطور برمجيات، العمل على مشروع توثيق يمكن أن يساعدك على البدء في عالم المشاريع مفتوحة المصدر. غالبًا ما يكون العمل على المشاريع التي لا تتضمن كود أقل رعبًا، وعملية التعاون ستزيد من ثقتك وخبرتك. التعرف على مشروع جديد إذا ذهبت إلى متتبع المشكلات (issue tracker) وبدا الأمر محيرًا، فأنت لست وحدك. هذه الأدوات تتطلب الكثير من المعرفة الضمنية، لكن يمكن للناس مساعدتك في التنقل خلالها ويمكنك طرح الأسئلة عليهم. — @shaunagm, “How to Contribute to Open Source” بالنسبة لأي مساهمة تتعدى مجرد تصحيح خطأ مطبعي، فإن المساهمة في المشاريع مفتوحة المصدر تشبه الاقتراب من مجموعة غرباء في حفلة. إذا بدأت بالحديث عن حيوان اللاما بينما هم منغمسون في مناقشة حول أسماك الزينة، فغالبًا سينظرون إليك بنظرة محيرة بعض الشيء. قبل أن تندفع بتقديم اقتراحاتك بشكل عشوائي، ابدأ أولاً بتعلّم “قراءة الجو العام” للمناقشة. فعل ذلك يزيد من فرص أن تُلاحَظ أفكارك ويُصغَى لها. مكونات المشروع مفتوح المصدر كل مجتمع مفتوح المصدر ينطلق من رؤيته الخاصة. قضاء سنوات في مشروع مفتوح المصدر واحد يعني أنك لم تتعرّف سوى على مشروع واحد فقط. لكن إن انتقلت إلى مشروع آخر، فقد تكتشف أن المصطلحات والعادات وأساليب التواصل مختلفة تمامًا. ومع ذلك، فإن العديد من المشاريع مفتوحة المصدر تتبع هيكلًا تنظيميًا متشابهًا. فهم الأدوار المختلفة داخل المجتمع وطريقة العمل سيساعدك على التأقلم بسرعة مع أي مشروع جديد. عادةً ما يحتوي المشروع مفتوح المصدر على الأنواع التالية من الأدوار: المؤلف: الشخص أو الأشخاص، أو الجهة التي أنشأت المشروع المالك: الشخص أو الأشخاص، الذين يملكون صلاحيات الإدارة على المنظمة أو المستودع (وليسوا دائمًا نفس مؤلف المشروع الأصلي) المشرفون: المساهمون المسؤولون عن توجيه رؤية المشروع وإدارة الجوانب التنظيمية له (وقد يكونون أيضًا من مؤلفي المشروع أو مالكيه) المساهمون: كل من قدّم مساهمة ما للمشروع أعضاء المجتمع: الأشخاص الذين يستخدمون المشروع، وقد يشاركون في النقاشات أو يعبّرون عن آرائهم حول مسار المشروع. قد تحتوي المشاريع الأكبر أيضًا على لجان فرعية أو مجموعات عمل تركز على مهام مختلفة، مثل أدوات التطوير، وفرز المشكلات، وإدارة المجتمع، وتنظيم الفعاليات. ابحث في موقع المشروع عن صفحة الفريق (Team) أو في المستودع عن وثائق إدارة المشروع (governance documentation) لمعرفة هذه المعلومات. يحتوي المشروع أيضًا على وثائق. تكون هذه الملفات عادةً موجودة في المستوى الأعلى من المستودع (أي في المجلد الرئيسي). LICENSE: الترخيص؛ كل مشروع مفتوح المصدر يجب أن يكون له ترخيص مفتوح المصدر .إذا لم يكن للمشروع ترخيص، فهو ليس مفتوح المصدر. README: ملف الترحيب؛ هو دليل التعليمات الذي يرحب بأعضاء المجتمع الجدد ويشرح لماذا المشروع مفيد وكيفية البدء به. CONTRIBUTING: دليل المساهمة؛ بينما تساعد ملفات ال README الناس على استخدام المشروع، فإن ملفات ال CONTRIBUTING تساعد الناس على المساهمة في المشروع. يشرح أنواع المساهمات المطلوبة وكيفية سير العملية. وجود هذا الملف يشير إلى أن المشروع مُرحّب بالمساهمين الجدد. مثال جيد لدليل المساهمة الفعّال الموجود في Codecademy’s Docs repository . CODE_OF_CONDUCT: قواعد السلوك؛ تحدد قواعد السلوك الأساسية لسلوك المشاركين وتساعد على خلق بيئة ودية. على الرغم من أن ليس كل مشروع يحتوي على هذا الملف، إلا أن وجوده يشير إلى أن المشروع مُرحّب بالمساهمين الجدد. Other documentation: قد تكون هناك وثائق إضافية، مثل الدروس التعليمية، الشروحات خطوة بخطوة، أو سياسات إدارة المشروع، خصوصًا في المشاريع الكبيرة مثل: Astro Docs . أخيرًا، تستخدم المشاريع مفتوحة المصدر الأدوات التالية لتنظيم النقاشات. قراءة الأرشيفات ستمنحك فكرة جيدة عن كيفية تفكير المجتمع وطريقة عمله. Issue tracker: المكان الذي يناقش فيه الناس المشاكل المتعلقة بالمشروع. Pull/Merge requests: المكان الذي يناقش فيه الناس التغييرات الجاري العمل عليها ويستعرضونها، سواء كان ذلك لتحسين سطر كود لمساهم، أو استخدام القواعد اللغوية، أو الصور، وغيرها. بعض المشاريع، مثل MDN Web Docs ، تستخدم بعض GitHub Action لتسريع وأتمتة مراجعات الكود. Discussion forums or mailing lists: قد تستخدم بعض المشاريع هذه القنوات للمواضيع الحوارية (على سبيل المثال، “كيف أفعل…“ أو “ما رأيك في…“ بدلاً من تقارير الأخطاء أو طلبات المزايا). بينما يستخدم البعض الآخر الـ Issue tracker لجميع المحادثات. مثال جيد على ذلك هو CHAOSS’ weekly Newsletter . Synchronous chat channel: تستخدم بعض المشاريع قنوات الدردشة (مثل Slack أو IRC) للمحادثات غير الرسمية، والتعاون، والتبادل السريع للأفكار. مثال جيد على ذلك هو EddieHub’s Discord community . إيجاد مشروع للمساهمة فيه الآن بعد أن فهمت كيف تعمل المشاريع مفتوحة المصدر، حان الوقت للعثور على مشروع للمساهمة فيه! إذا لم تكن قد ساهمت في المشاريع مفتوحة المصدر من قبل، خذ بعض النصائح من الرئيس الأمريكي جون إف. كينيدي، الذي قال مرة: “لا تسأل ماذا يمكن لبلدك أن يفعل لك، بل اسأل ماذا يمكنك أن تفعل لبلدك.” Ask not what your country can do for you - ask what you can do for your country. — John F. Kennedy Library تحدث المساهمة في المصادر المفتوحة على جميع المستويات وفي مختلف المشاريع. لا تحتاج إلى التفكير كثيرًا فيما ستكون عليه مساهمتك الأولى بالضبط، أو كيف ستبدو. بدلاً من ذلك، ابدأ بالتفكير في المشاريع التي تستخدمها بالفعل، أو ترغب في استخدامها. المشاريع التي ستساهم فيها بنشاط هي تلك التي تجد نفسك تعود إليها باستمرار. ضمن تلك المشاريع، كلما شعرت أن شيئًا ما يمكن أن يكون أفضل أو مختلفًا، تصرف بناءً على حدسك. المشاريع مفتوحة المصدر ليست ناديًا حصريًا؛ فهي مصنوعة من أشخاص مثلك تمامًا. مصطلح “المشاريع مفتوحة المصدر” هو مجرد تعبير أنيق للتعامل مع مشاكل العالم على أنها قابلة للحل. قد تتصفح ملف README وتجد رابطًا معطلًا أو خطأً مطبعيًا. أو ربما تكون مستخدمًا جديدًا ولاحظت شيئًا لا يعمل، أو مشكلة تعتقد أنها يجب أن تكون موثقة. بدلًا من تجاهلها والمضي قدمًا، أو طلب مساعدة شخص آخر لإصلاحها، تحقق مما إذا كان بإمكانك المساهمة بالمساعدة. هذا هو جوهر مشاريع البرمجيات مفتوحة المصدر! وفقًا لدراسة أجراها Igor Steinmacher وباحثون آخرون في علوم الحاسوب، فإن 28٪ من المساهمات الصغيرة في مشاريع البرمجيات مفتوحة المصدر تتعلق بالتوثيق، مثل تصحيح الأخطاء المطبعية، إعادة التنسيق، أو كتابة ترجمة. إذا كنت تبحث عن المشاكل الموجودة التي يمكنك إصلاحها، فإن كل مشروع من مشاريع البرمجيات مفتوحة المصدر يحتوي على صفحة /contribute التي تبرز الـ beginner-friendly issues التي يمكنك البدء بها. انتقل إلى الصفحة الرئيسية للمستودع على GitHub، وأضف /contribute في نهاية الـ URL (على سبيل المثال https://github.com/facebook/react/contribute ). يمكنك أيضًا استخدام أحد المصادر التالية لمساعدتك في اكتشاف مشاريع جديدة والمساهمة فيها: GitHub Explore جمعة المصادر المفتوحة First Timers Only CodeTriage 24 Pull Requests Up For Grabs First Contributions SourceSort OpenSauced GitLab Explore قائمة تحقّق قبل أن تساهم عندما تجد مشروعًا ترغب في المساهمة فيه، قم بمراجعة سريعة للتأكد من أن المشروع مناسب لقبول المساهمات. وإلا، فقد لا يحصل عملك الجاد على أي رد. إليك قائمة مرجعية مفيدة لتقييم ما إذا كان المشروع مناسبًا للمساهمين الجدد. يتوافق مع تعريف المشاريع مفتوحة المصدر هل يحتوي على رخصة؟ عادةً، يوجد ملف باسم LICENSE في جذر المستودع. المشروع يقبل المساهمات بشكل فعّال اطلع على نشاط الـ commit على الفرع الرئيسي. على GitHub، يمكنك رؤية هذه المعلومات في تبويب Insights على الصفحة الرئيسية للمستودع، مثل Virtual-Coffee متى كان أحدث (commit)؟ كم عدد المساهمين في المشروع؟ كم مرة يقوم الناس بالـ (commit)؟ (على GitHub، يمكنك معرفة ذلك بالنقر على "Commits" في الشريط العلوي.) بعد ذلك، اطلع على الـ issues الخاصة بالمشروع. كم عدد الـ open issues الموجودة؟ هل يرد القائمون بالصيانة (maintainers) بسرعة على الـ issues عند فتحها؟ هل هناك نقاش نشط على الـ issues؟ هل الـ issues حديثة؟ هل يتم إغلاق الـ issues؟ (على GitHub، انقر على تبويب "closed" في صفحة الـ Issues لرؤية الـ issues المغلقة.) الآن افعل الشيء نفسه بالنسبة للـ pull requests الخاصة بالمشروع. كم عدد الـ open pull/merge requests الموجودة؟ هل يرد القائمون بالصيانة (maintainers) بسرعة على الـ pull requests عند فتحها؟ هل هناك نقاش نشط على الـ pull requests؟ هل الـ pull requests حديثة؟ متى تم دمج أي من الـ pull requests مؤخرًا؟ (على GitHub، انقر على تبويب "closed" في صفحة الـ Pull Requests لرؤية الـ PRs المغلقة.) المشروع مرحّب بالمساهمين المشروع الذي يكون ودودًا ومرحّبًا يشير إلى أنه سيكون متقبلًا للمساهمين الجدد. هل يرد القائمون بالصيانة (maintainers) بشكل مفيد على الأسئلة في الـ issues؟ هل يتعامل الناس بودّ في الـ issues، والمنتديات النقاشية، وقنوات الدردشة (مثل IRC أو Slack)؟ هل يتم مراجعة Pull Requests؟ هل يشكر القائمون على المشروع الأشخاص على مساهماتهم؟ كلما رأيت سلسلة طويلة من النقاشات، تحقق عشوائيًا من ردود المطورين الأساسيين التي تأتي في أواخر السلسلة. هل يقومون بتلخيص الأمور بشكل بنّاء، ويتخذون خطوات لتوجيه النقاش نحو اتخاذ قرار مع البقاء مهذبين؟ إذا رأيت الكثير من النزاعات الحادة، فهذا غالبًا علامة على أن الطاقة تُستهلك في الجدال بدلًا من تطوير المشروع. — @kfogel, Producing OSS كيف ترسل المساهمة؟ لقد وجدت مشروعًا يعجبك، وأنت جاهز لتقديم مساهمة. أخيرًا! إليك كيفية تقديم مساهمتك بالطريقة الصحيحة. التواصل بفعالية سواء كنت مساهمًا لمرة واحدة أو تحاول الانضمام إلى مجتمع، فإن العمل مع الآخرين هو من أهم المهارات التي ستطورها في المشاريع مفتوحة المصدر. [كمساهم جديد،] أدركت بسرعة أنه يجب علي طرح الأسئلة إذا كنت أرغب في القدرة على إغلاق الـ issue. تصفحت الكود سريعًا. بمجرد أن حصلت على فكرة عما يجري، طلبت توجيهًا إضافيًا. وأخيرًا! تمكنت من حل الـ issue بعد حصولي على كل التفاصيل ذات الصلة التي كنت بحاجة إليها. — @shubheksha, A Beginner’s Very Bumpy Journey Through The World of Open Source قبل أن تفتح (issue) أو (pull request)، أو تطرح سؤالًا في المحادثة، ضع هذه النقاط في اعتبارك لمساعدتك على توصيل أفكارك بفعالية. ساعد الآخرين على فهم الموقف ؛ إذا واجهت خطأً فاشرح ما الذي تحاول فعله وكيف يمكن إعادة إنتاج المشكلة، أما إذا كنت تقترح فكرة جديدة فاشرح لماذا تعتقد أنها ستكون مفيدة للمشروع (وليس لك فقط!). 😇 “لا يحدث X عندما أقوم بـ Y” 😢 “X لا يعمل! من فضلك أصلحه.” قُم بواجبك مُسبقًا. لا بأس ألا تعرف كل شيء، لكن أظهر أنك حاولت. قبل أن تطلب المساعدة، تأكد من مراجعة (README)، و(issues) “المشاكل المفتوحة أو المغلقة”، والقائمة البريدية، وابحث في الإنترنت عن إجابة. سيقدّر الناس ذلك عندما تُظهر أنك تحاول التعلم. 😇 “لست متأكدًا من كيفية تنفيذ X. راجعت مستندات المساعدة ولم أجد أي ذكر لها.” 😢 “كيف أفعل X؟” اجعل طلباتك قصيرة ومباشرة. تمامًا مثل إرسال بريد إلكتروني، كل مساهمة، مهما كانت بسيطة أو مفيدة، تحتاج إلى مراجعة من شخص آخر. العديد من المشاريع لديها طلبات أكثر من عدد الأشخاص المتاحين للمساعدة. كن موجزًا، فهذا سيزيد من فرص أن يتمكن شخص ما من مساعدتك. 😇 “أود أن أكتب درسًا تعليميًا حول كيفية إنشاء API .” 😢 “كنت أقود على الطريق السريع في اليوم الآخر وتوقفت لتعبئة الوقود، ثم خطرت لي فكرة رائعة حول شيء يجب أن نفعله. لكن قبل أن أشرح ذلك، دعني أريك…“ اجعل كل تواصلك علنيًا. مع أن الرغبة قد تدفعك، لا تتوجه إلى القائمين على المشروع بشكل خاص إلا إذا كنت بحاجة لمشاركة معلومات حساسة (مثل مشكلة أمنية أو انتهاك خطير للسلوك). عندما تبقي النقاش علنيًا، يمكن للمزيد من الأشخاص التعلم والاستفادة من تبادلك. النقاشات بحد ذاتها يمكن أن تكون مساهمات. 😇 (as a comment) “@-maintainer أهلاً! كيف يجب أن نتابع في هذا PR؟” 😢 (as an email) “أهلاً، آسف للإزعاج عبر البريد الإلكتروني، لكني كنت أتساءل إذا كانت لديك فرصة لمراجعة الـ PR الخاص بي” لا بأس في طرح الأسئلة (ولكن كن صبورًا!). كان الجميع جديدين على المشروع في وقت ما، وحتى المساهمين ذوي الخبرة يحتاجون إلى الوقت لاستيعاب المشروع الجديد. وبالمثل، حتى القائمون على المشروع منذ فترة طويلة ليسوا دائمًا على دراية بكل جزء منه. اظهر لهم نفس الصبر الذي تريدهم أن يظهروه لك. 😇 “شكراً للنظر في هذا الخطأ. لقد اتبعت اقتراحاتك. إليك الناتج:” 😢 “لماذا لا يمكنك إصلاح مشكلتي؟ أليس هذا مشروعك؟” احترم قرارات المجتمع. قد تختلف أفكارك عن أولويات المجتمع أو رؤيته. قد يقدمون ملاحظات أو يقررون عدم متابعة فكرتك. بينما يجب عليك النقاش ومحاولة الوصول إلى حل وسط، يجب على القائمين بالصيانة (maintainers) التعايش مع قرارك لفترة أطول منك. إذا لم تتفق مع اتجاههم، يمكنك دائمًا العمل على نسخة Fork خاصة بك أو بدء مشروعك الخاص. 😇 “أنا مستاء لأنكم لا تستطيعون دعم فكرتي، لكن كما أوضحتم، فهي تؤثر فقط على جزء صغير من المستخدمين، لذلك أفهم السبب. شكرًا لاستماعكم.” 😢 “لماذا لن تدعموا فكرتي؟ هذا أمر غير مقبول!” قبل كل شيء، حافظ على الاحترام. يتكون مجتمع المشاريع مفتوحة المصدر من متعاونين من جميع أنحاء العالم. يُفقد السياق عبر اللغات والثقافات والجغرافيا والمناطق الزمنية. بالإضافة إلى ذلك، يجعل التواصل الكتابي من الصعب نقل النبرة أو المزاج. افترض النوايا الحسنة في هذه المحادثات. لا بأس في الاعتراض بأدب على فكرة، أو طلب المزيد من السياق، أو توضيح موقفك. فقط حاول أن تترك الإنترنت مكانًا أفضل مما وجدته عليه. جمع المعلومات قبل القيام بأي شيء، قم بإجراء فحص سريع للتأكد من أن فكرتك لم تُناقش في مكان آخر. تصفح README المشروع، و issues (المفتوحة والمغلقة)، وقوائم البريد، وStack Overflow. لا تحتاج لقضاء ساعات في مراجعة كل شيء، لكن البحث السريع عن بعض الكلمات المفتاحية يكون ذا فائدة كبيرة. إذا لم تتمكن من إيجاد فكرتك في مكان آخر، فأنت جاهز لاتخاذ خطوة. إذا كان المشروع على GitHub، فمن المرجح أن تتواصل عن طريق القيام بما يلي: Raising an Issue: هذه مثل بدء محادثة أو نقاش Pull requests: مخصصة لبدء العمل على حل Communication Channels: إذا كان للمشروع قناة مخصصة على Discord، IRC، أو Slack، فكر في بدء محادثة أو طلب توضيح حول مساهمتك. قبل أن تفتح issue أو pull request، تحقق من مستندات المساهمة في المشروع (عادةً ملف يسمى CONTRIBUTING، أو في README)، لتعرف ما إذا كنت بحاجة لتضمين أي شيء محدد. على سبيل المثال، قد يطلبون منك اتباع قالب معين، أو يشترطون أن تستخدم الاختبارات. إذا كنت تريد تقديم مساهمة كبيرة، افتح issue للسؤال قبل البدء بالعمل عليها. من المفيد متابعة المشروع لفترة (على GitHub، يمكنك الضغط على “Watch” لتصلك إشعارات بكل النقاشات)، والتعرف على أعضاء المجتمع، قبل القيام بعمل قد لا يتم قبوله. ستتعلم الكثير من خلال اختيار مشروع واحد تستخدمه بانتظام، ومتابعته على GitHub وقراءة كل issue و pull request . — @gaearon on joining projects الإبلاغ عن مشكلة (issue) عادةً ما يجب عليك فتح issue (مشكلة والإبلاغ عنها) في الحالات التالية: الإبلاغ عن خطأ لا تستطيع حله بنفسك مناقشة موضوع أو فكرة على مستوى عالٍ (على سبيل المثال: المجتمع، الرؤية، أو السياسات) اقتراح ميزة جديدة أو فكرة مشروع أخرى نصائح للتواصل حول issues : إذا رأيت issue مفتوحة تريد التعامل معها، قم بالتعليق على الـ issue لإعلام الآخرين بأنك تعمل عليها. بهذه الطريقة، تقل احتمالية تكرار عملك من قبل الآخرين. إذا كانت issue مفتوحة منذ فترة، فمن الممكن أن يتم التعامل معها في مكان آخر أو أنها حُلّت بالفعل، لذا قم بالتعليق لطلب التأكيد قبل البدء بالعمل. إذا فتحت issue بنفسك، ثم اكتشفت الحل لاحقًا بنفسك، قم بالتعليق على الـ issue لإعلام الآخرين، ثم أغلق الـ issue. حتى توثيق هذه النتيجة يُعد مساهمة في المشروع. فتح طلب دمج (pull request) عادةً ما يُفضّل فتح (pull request) في الحالات التالية: إرسال إصلاحات بسيطة مثل الأخطاء الإملائية، أو الروابط المعطلة، أو الأخطاء الواضحة. البدء بالعمل على مساهمة تم طلبها مسبقًا، أو تم مناقشتها بالفعل في إحدى المشاكل (issues). ليش شرطًا أن يُمثّل طلب (Pull Request) عملًا منتهيًا بالكامل. في العادة من الأفضل فتح (Pull Request) في وقتٍ مبكر، حتى يتمكن الآخرون من متابعة تقدمك أو تقديم ملاحظاتهم حوله. يمكنك فتحه كـ “مسودة (Draft)” أو وضع علامة “WIP” (عمل قيد التنفيذ) في عنوان الطلب أو في قسم “Notes to Reviewers” إن وُجد (أو يمكنك إنشاء قسمك الخاص مثل: ## Notes to Reviewer ).ويمكنك دائمًا إضافة المزيد من التعديلات (commits) لاحقًا. إذا كان المشروع موجودًا على GitHub، فإليك كيفية تقديم (Pull Request): قم بعمل Fork للمستودع ونسخه إلى جهازك محليًا (clone). اربط نسختك المحلية بالمستودع الأصلي “upstream” عن طريق إضافته كـ remote. قم بسحب التحديثات من “upstream” بشكل دوري لتبقى محدثًا، حتى تقل احتمالية حدوث تعارضات (merge conflicts) عند تقديم طلب السحب (pull request). (راجع التعليمات التفصيلية هنا .) قم بإنشاء فرع (branch) لإجراء تعديلاتك. قم بالإشارة إلى أي Issues ذات صلة أو مستندات داعمة في طلب (PR) الخاص بك (على سبيل المثال: “Closes #37.”). أضف لقطات شاشة قبل وبعد إذا كانت تغييراتك تتضمن فروقات في HTML/CSS. اسحب الصور وأفلتها داخل محتوى طلب (pull request) الخاص بك. اختبر تغييراتك! شغّل تغييراتك مقابل أي اختبارات موجودة مسبقًا إذا كانت موجودة، وأنشئ اختبارات جديدة عند الحاجة. من المهم التأكد أن تغييراتك لا تؤدي إلى كسر المشروع الحالي. ساهم بأسلوب المشروع قدر استطاعتك. قد يعني هذا استخدام المسافات البادئة (indents)، الفواصل المنقوطة (semi-colons) أو التعليقات (comments) بشكل مختلف عما اعتدت عليه في مستودعك الخاص، لكن هذا يسهل على المسؤول عن المشروع الدمج، وعلى الآخرين فهم الكود وصيانته في المستقبل. إذا كان هذا أول pull request لك، اطلع على Make a Pull Request ، الذي أنشأه @kentcdodds كدليل فيديو تعليمي. يمكنك أيضًا التدريب على عمل pull request في مستودع First Contributions الذي أنشأه @Roshanjossey. ماذا يحدث بعد تقديم مساهمتك؟ قبل أن نبدأ بالاحتفال، سيحدث أحد الأمور التالية بعد تقديم مساهمتك: 😭 لم تتلقَّ أيَّ ردّ نأمل أن تكون قد تحققت من نشاط المشروع قبل تقديم مساهمتك. ومع ذلك، حتى في المشاريع النشطة، من الممكن ألا تتلقى مساهمتك أي رد. إذا لم تتلقَ ردًا خلال أكثر من أسبوع، من المقبول أن ترد بأدب في نفس threads ، طالبًا مراجعة من شخص ما. إذا كنت تعرف اسم الشخص المناسب لمراجعة مساهمتك، يمكنك الإشارة إليه باستخدام @ في تلك threads . لا تتواصل مع ذلك الشخص بشكل خاص ؛ تذكر أن التواصل العام مهم جدًا في المشاريع مفتوحة المصدر. إذا أعطيت تذكيرًا مهذبًا وما زلت لم تتلقَ ردًا، فمن الممكن ألا يرد أحد أبدًا. قد لا يكون شعورًا رائعًا، لكن لا تدع ذلك يثنيك عن المشاركة! 😄 هناك العديد من الأسباب المحتملة لعدم حصولك على رد، بما في ذلك الظروف الشخصية التي قد تكون خارجة عن إرادتك. حاول إيجاد مشروع آخر أو طريقة أخرى للمساهمة. على الأقل، هذا سبب جيد لعدم استثمار الكثير من الوقت في تقديم مساهمة قبل أن يكون أعضاء المجتمع الآخرون منخرطين ومستجيبين. 🚧 أحدهم يطلب إجراء تعديلات على مساهمتك من الشائع أن يُطلب منك إجراء تعديلات على مساهمتك، سواء كان ذلك ملاحظات حول نطاق فكرتك، أو تغييرات في الكود الذي كتبته. عندما يطلب منك أحد إجراء تغييرات، كن مستجيبًا. لقد أخذوا وقتهم لمراجعة مساهمتك. فتح Pull Request ثم الابتعاد عنه يُعد سلوكًا سيئًا. إذا لم تكن تعرف كيفية إجراء التغييرات، قم بالبحث عن المشكلة، ثم اطلب المساعدة إذا احتجت. مثال جيد على ذلك هو التعليقات التي قدمها أحد المساهمين لـ @a-m-lamb على Pull Request الخاص بهم في مستندات Codecademy . إذا لم يعد لديك وقت للعمل على المشكلة لعدة أسباب مثل استمرار النقاش لأشهر، أو تغيُّر ظروفك، أو عدم قدرتك على إيجاد حل، فأخبر المسؤول عن المشروع حتى يتمكن من فتح المشكلة لشخص آخر. مثل ما فعلت @RitaDee مع مشكلة في مستودع تطبيق OpenSauced . 👎 لم تُقبَل مساهمَتَك مساهمتك قد تُقبل في النهاية أو قد لا تُقبل. نأمل أنك لم تبذل جهدًا كبيرًا فيها بالفعل. إذا كنت غير متأكد من سبب عدم قبولها، فمن المعقول تمامًا أن تطلب توضيحًا وتغذية راجعة من المشرف. في النهاية، عليك أن تحترم أن هذا قرارهم. لا تجادل أو تتصرف بعدائية. أنت مرحب بك دائمًا في إنشاء نسخة مستقلة والعمل على إصدارك الخاص إذا كنت لا توافق! 🎉 قُبِلت مساهمَتَك رائع! لقد قمت بإجراء مساهمة ناجحة في مشروع مفتوح المصدر! لقد فَعَلتها 🎉 سواء كنت قد قدّمت مساهمتك الأولى في مشروع مفتوح المصدر، أو كنت تبحث عن طرق جديدة للمساهمة، نأمل أن تكون متحمسًا لاتخاذ خطوة. حتى لو لم تُقبل مساهمتك، لا تنسَ أن تشكر المشرفين الذين بذلوا جهدًا لمساعدتك. المشاريع مفتوحة المصدر يطورها أشخاص مثلك: مشكلة (One Issue) ، pull request ، تعليق، أو تشجيع بسيط في كل مرة. رجوع للأدلة أدلة ذات صلة البدء بمشروع مفتوح المصدر تعلّم المزيد عن عالم المصادر المفتوحة واستعد لإطلاق مشروعك الخاص بناء مُجتمعات مُرحِّبة إنشاء مجتمع يدعم مشاركة الناس في مشروعك، ويحفّزهم على استخدامه والمساهمة فيه والترويج له Scroll to Top ساهِم هل تريد تقديم اقتراح؟ هذا المحتوى مفتوح المصدر. ساعدنا على تحسينه ساهِم ابقَ على تواصل GitHubكُن أول من يطّلِع على أحدث نصائح وموارد البريد الإلكتروني fine print with by and friends | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/oracle-linux-oracle-virtualization/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Oracle Virtualization | LinkedIn Skip to main content LinkedIn Oracle Linux in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Oracle Virtualization Server Virtualization Software by Oracle Linux See who's skilled in this Add as skill Learn more Report this product About Backed by affordable enterprise support for hybrid environments, Oracle Virtualization reduces operation and support costs while increasing IT efficiency and agility—on premises and in the cloud. This product is intended for Information Technology Manager System Administrator System Manager Director of Information Technology Chief Security Officer Chief Technology Officer Senior Information Technology Specialist Vice President Information Technology Media Products media viewer No more previous content Cisco cryptographic services team reduces cost of virtualization Learn more: https://oracle.com/linux Learn how the Cisco cryptographic services team lowered their virtualization cost, increased their uptime using Ksplice live patching, increased performance, and streamlined support by switching to Oracle Linux KVM and Virtualization Manager. Kata Containers and Security with Oracle Linux Learn about the differences between Kata Containers and other types of containers such as Docker and containerd, and when best to use them. Kata container support is included with Oracle Linux Premier support. Accelerate Your DevOps Processes with Oracle VM VirtualBox Oracle VM VirtualBox is an open source high-performance desktop virtualization software that makes it quick and easy to operate multi-platform test environments on a single machine, secure VMs, and easily deploy them to any cloud. No more next content Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Sign in to see more Show more Show less Oracle Linux products Oracle Autonomous Linux Oracle Autonomous Linux Operating Systems Oracle Linux Oracle Linux Operating Systems Oracle VirtualBox Oracle VirtualBox Virtual Desktop Infrastructure (VDI) Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/tencentglobal-cloud-native-database-tdsqlc/ | Cloud Native Database TDSQL-C | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloud Native Database TDSQL-C Relational Database Management Systems by Tencent See who's skilled in this Add as skill Learn more Report this product About A cloud native database with high performance, storage capacity, and compatibility Similar products Amazon Aurora Amazon Aurora Relational Database Management Systems Amazon RDS Amazon RDS Relational Database Management Systems Google Cloud SQL Google Cloud SQL Relational Database Management Systems Teradata Vantage Teradata Vantage Relational Database Management Systems SQL Server SQL Server Relational Database Management Systems CockroachDB CockroachDB Relational Database Management Systems Sign in to see more Show more Show less Tencent products Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/scalecomputing-hc3-edge/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | SC//Platform | LinkedIn Skip to main content LinkedIn Scale Computing in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in SC//Platform Server Virtualization Software by Scale Computing See who's skilled in this Add as skill Learn more Report this product About With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. The award winning Scale Computing brings on-premises edge computing with high availability and disaster recovery to remote locations at an affordable entry level cost. All edge appliances can be deployed quickly, managed locally or remotely, and can self-heal almost instantly. Enjoy affordable edge computing infrastructure that is reliable, easy to deploy, and easy to use. This product is intended for Chief Information Officer Vice President Information Technology Director of Information Technology Head of Innovation Software Architect Enterprise Architect Network Engineer Media Products media viewer No more previous content Scale Computing HC3 Edge: Compute from Beyond the Datacenter With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. No more next content Featured customers of SC//Platform Telford Offshore Oil and Gas 45,517 followers Maritime Paper Products Limited Packaging and Containers Manufacturing 3,201 followers Jerry's Enterprises Retail 1,514 followers Harrison Steel Castings Co. Mining 2,061 followers Ahold Delhaize Retail 180,797 followers GOODWILL CENTRAL COAST Retail 404 followers Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Scale Computing products SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//HyperCore SC//HyperCore LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://opensource.guide/el/how-to-contribute/ | Πώς να Συνεισφέρετε στον Ανοιχτό Κώδικα | Open Source Guides Σχετικά με Συνεισφορά العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Πώς να Συνεισφέρετε στον Ανοιχτό Κώδικα Θέλετε να συνεισφέρετε σε πρότζεκτς ανοιχτού κώδικα; Ένας οδηγός για τη συνεισφορά στον ανοιχτό κώδικα, για αρχάριους και βετεράνους. Πίνακας Περιεχομένων Γιατί να συνεισφέρετε στον ανοιχτό κώδικα; Τι σημαίνει να συνεισφέρετε Προσανατολισμός σε ένα νέο έργο Βρίσκοντας ένα έργο για να συνεισφέρετε Πώς να υποβάλετε μια συνεισφορά Τι συμβαίνει μετά την υποβολή μιας συνεισφοράς Γιατί να συνεισφέρετε στον ανοιχτό κώδικα; Η εργασία στο [freenode] με βοήθησε να αποκτήσω πολλές από τις δεξιότητες που χρησιμοποίησα αργότερα για τις σπουδές μου στο πανεπιστήμιο και την πραγματική μου δουλειά. Νομίζω ότι η εργασία σε έργα ανοιχτού κώδικα βοηθάει εμένα όσο βοηθάει και το έργο! - @errietta, “Why I love contributing to open source software” Η συνεισφορά σε λογισμικό ανοικτού κώδικα μπορεί να είναι ένας ικανοποιητικός τρόπος για να μάθετε, να διδάξετε και να αποκτήσετε εμπειρία σε σχεδόν οποιαδήποτε δεξιότητα μπορείτε να φανταστείτε. Γιατί οι άνθρωποι συνεισφέρουν στον ανοικτό κώδικα; Πολλοί λόγοι! Βελτιώνουν το λογισμικό στο οποίο βασίζονται Πολλοί συνεισφέροντες σε λογισμικό ανοικτού κώδικα ξεκινούν ως χρήστες του λογισμικού στο οποίο συνεισφέρουν. Όταν βρίσκετε ένα σφάλμα σε ένα λογισμικό ανοικτού κώδικα που χρησιμοποιείτε, ίσως θελήσετε να κοιτάξετε τον πηγαίο κώδικα για να δείτε αν μπορείτε να το διορθώσετε μόνοι σας. Αν είναι έτσι, τότε η συνεισφορά του διορθωτικού είναι ο καλύτερος τρόπος για να διασφαλίσετε ότι οι φίλοι σας (και εσείς οι ίδιοι όταν κάνετε ενημέρωση στην επόμενη έκδοση) θα μπορέσουν να επωφεληθούν από αυτό. Βελτιώστε τις υπάρχουσες δεξιότητες Είτε πρόκειται για προγραμματισμό, είτε για σχεδιασμό διεπαφής χρήστη, είτε για γραφιστική, είτε για συγγραφή, είτε για οργάνωση, αν ψάχνετε για εξάσκηση, υπάρχει μια εργασία για εσάς σε ένα έργο ανοιχτού κώδικα. Γνωρίστε ανθρώπους που ενδιαφέρονται για παρόμοια πράγματα Τα έργα ανοιχτού κώδικα με θερμές, φιλόξενες κοινότητες κρατούν τους ανθρώπους να επιστρέφουν για χρόνια. Πολλοί άνθρωποι δημιουργούν φιλίες ζωής μέσα από τη συμμετοχή τους στον ανοιχτό κώδικα, είτε πρόκειται για συναντήσεις σε συνέδρια είτε για διαδικτυακές συζητήσεις αργά το βράδυ για μπουρίτος. Βρείτε μέντορες και διδάξτε άλλους Η συνεργασία με άλλους σε ένα κοινό έργο σημαίνει ότι θα πρέπει να εξηγείτε πώς κάνετε τα πράγματα, καθώς και να ζητάτε βοήθεια από άλλους ανθρώπους. Οι πράξεις μάθησης και διδασκαλίας μπορεί να είναι μια ικανοποιητική δραστηριότητα για όλους τους εμπλεκόμενους. Δημιουργήστε δημόσια αντικείμενα που σας βοηθούν να αναπτύξετε τη φήμη σας (και την καριέρα σας) Εξ ορισμού, όλη η εργασία σας με ανοιχτό κώδικα είναι δημόσια, πράγμα που σημαίνει ότι έχετε δωρεάν παραδείγματα για να τα πάρετε οπουδήποτε ως επίδειξη του τι μπορείτε να κάνετε. Μάθετε δεξιότητες ανθρώπινου δυναμικού Ο ανοικτός κώδικας προσφέρει ευκαιρίες για να εξασκήσετε ηγετικές και διοικητικές δεξιότητες, όπως η επίλυση συγκρούσεων, η οργάνωση ομάδων ανθρώπων και η ιεράρχηση προτεραιοτήτων εργασίας. Είναι ενδυναμωτικό να μπορείς να κάνεις αλλαγές, ακόμη και μικρές Δεν χρειάζεται να γίνετε ισόβιος συνεργάτης για να απολαύσετε τη συμμετοχή σας στον ανοικτό κώδικα. Έχετε δει ποτέ ένα τυπογραφικό λάθος σε έναν ιστότοπο και ευχηθήκατε κάποιος να το διορθώσει; Σε ένα έργο ανοιχτού κώδικα, μπορείτε να κάνετε ακριβώς αυτό. Ο ανοικτός κώδικας βοηθά τους ανθρώπους να αισθάνονται ότι έχουν εξουσία στη ζωή τους και στο πώς βιώνουν τον κόσμο, και αυτό από μόνο του είναι ευχάριστο. Τι σημαίνει να συνεισφέρετε Αν είστε νέος συνεισφέρων σε έργα ανοικτού κώδικα, η διαδικασία μπορεί να είναι εκφοβιστική. Πώς μπορείτε να βρείτε το κατάλληλο έργο; Τι γίνεται αν δεν ξέρετε να προγραμματίζετε; Τι γίνεται αν κάτι πάει στραβά; Μην ανησυχείτε! Υπάρχουν διάφοροι τρόποι για να συμμετάσχετε σε ένα έργο ανοικτού κώδικα και μερικές συμβουλές θα σας βοηθήσουν να αξιοποιήσετε στο έπακρο την εμπειρία σας. Δεν χρειάζεται να συνεισφέρετε κώδικα Μια κοινή παρανόηση σχετικά με τη συνεισφορά σε έργα ανοικτού κώδικα είναι ότι πρέπει να συνεισφέρετε κώδικα. Στην πραγματικότητα, είναι συχνά τα άλλα μέρη ενός έργου που παραμελούνται ή παραβλέπονται περισσότερο . Θα κάνετε στο έργο μια τεράστια χάρη προσφέροντας να συνεισφέρετε με τέτοιου είδους συνεισφορές! Έχω γίνει γνωστός για τη δουλειά μου στο CocoaPods, αλλά οι περισσότεροι άνθρωποι δεν γνωρίζουν ότι στην πραγματικότητα δεν κάνω καμία πραγματική δουλειά στο ίδιο το εργαλείο CocoaPods. Ο χρόνος μου για το έργο αναλώνεται κυρίως σε πράγματα όπως η τεκμηρίωση και η εργασία πάνω στο branding. - @orta, “Moving to OSS by default” Σας αρέσει να προγραμματίζετε εκδηλώσεις; Οργανώστε εργαστήρια ή συναντήσεις για το έργο, όπως έκανε ο @fzamperin για το NodeSchool Διοργανώνετε το συνέδριο του έργου (αν έχουν) Βοηθήστε τα μέλη της κοινότητας να βρουν τα κατάλληλα συνέδρια και να υποβάλουν προτάσεις για ομιλία Σας αρέσει να σχεδιάζετε; Να αναδιαρθρώνετε τις διατάξεις για να βελτιώσετε τη χρηστικότητα του έργου Διεξαγωγή έρευνας χρηστών για την αναδιοργάνωση και βελτίωση της πλοήγησης ή των μενού του έργου, όπως προτείνει το Drupal Να συντάσσετε έναν οδηγό στυλ για να βοηθήσετε το έργο να έχει έναν συνεπή οπτικό σχεδιασμό Δημιουργήστε τέχνη για μπλουζάκια ή ένα νέο λογότυπο, όπως έκαναν οι συντελεστές του hapi.js Σας αρέσει να γράφετε; Γράφετε και βελτιώνετε την τεκμηρίωση του έργου Επιμεληθείτε έναν φάκελο με παραδείγματα που δείχνουν πώς χρησιμοποιείται το έργο Ξεκινήστε ένα ενημερωτικό δελτίο για το έργο, ή επιμεληθείτε τα σημαντικότερα σημεία από τη λίστα αλληλογραφίας Γράφετε εκπαιδευτικά προγράμματα για το έργο, όπως έκαναν οι συντελεστές του PyPA Γράψτε μια μετάφραση για την τεκμηρίωση του έργου Σοβαρά, το [documentation] είναι μέγα-σημαντικό. Η τεκμηρίωση μέχρι στιγμής είναι εξαιρετική και είναι ένα φονικό χαρακτηριστικό της Babel. Υπάρχουν τμήματα που σίγουρα χρειάζονται λίγη δουλειά και ακόμα και η προσθήκη μιας παραγράφου εδώ ή εκεί είναι εξαιρετικά ευπρόσδεκτη. - @kittens, “Call for contributors” Σας αρέσει η οργάνωση; Συνδέστε τα διπλά θέματα και προτείνετε νέες ετικέτες θεμάτων, για να διατηρήσετε τα πράγματα οργανωμένα Ψάξτε τα ανοιχτά θέματα και προτείνετε το κλείσιμο των παλιών, όπως έκανε ο @nzakas για το ESLint Να κάνετε διευκρινιστικές ερωτήσεις σε πρόσφατα ανοιχτά θέματα για να προχωρήσει η συζήτηση. Σας αρέσει να γράφετε κώδικα; Βρείτε ένα ανοιχτό θέμα για να ασχοληθείτε, όπως έκανε ο @dianjin για το Leaflet Ρωτήστε αν μπορείτε να βοηθήσετε στη συγγραφή ενός νέου χαρακτηριστικού. Αυτοματοποιήστε την εγκατάσταση του έργου Βελτιώστε τα εργαλεία και τις δοκιμές Σας αρέσει να βοηθάτε τους ανθρώπους; Απαντήστε σε ερωτήσεις σχετικά με το έργο π.χ. στο Stack Overflow ( όπως αυτό το παράδειγμα Postgres ) ή στο Reddit. Απαντάτε σε ερωτήσεις για ανθρώπους σε ανοιχτά θέματα Βοηθήστε να συντονίσετε τους πίνακες συζητήσεων ή τα κανάλια συζήτησης Σας αρέσει να βοηθάτε άλλους να προγραμματίζουν; Αναθεωρείτε τον κώδικα σε υποβολές άλλων ανθρώπων Γράφετε σεμινάρια για το πώς μπορεί να χρησιμοποιηθεί ένα έργο Προσφερθείτε να γίνετε μέντορας ενός άλλου συνεισφέροντα, όπως έκανε ο @ereichert για τον @bronzdoc στο Rust Δεν χρειάζεται να εργάζεστε μόνο σε έργα λογισμικού! Αν και ο όρος “ανοικτός κώδικας” αναφέρεται συχνά στο λογισμικό, μπορείτε να συνεργαστείτε σχεδόν σε οτιδήποτε. * Απαντήστε σε ερωτήσεις σχετικά με το έργο π.χ. στο Stack Overflow ( όπως αυτό το παράδειγμα Postgres ) ή στο Reddit. Για παράδειγμα: @sindresorhus επιμελείται μια λίστα με “φοβερές” λίστες Ο @h5bp διατηρεί μια λίστα με πιθανές ερωτήσεις συνέντευξης για υποψήφιους front-end προγραμματιστές Ο @stuartlynn και η @nicole-a-tesla δημιούργησαν μια συλλογή με διασκεδαστικά στοιχεία για τους πιθήκους Ακόμα και αν είστε προγραμματιστής λογισμικού, η εργασία σε ένα έργο τεκμηρίωσης μπορεί να σας βοηθήσει να ξεκινήσετε στον ανοιχτό κώδικα. Είναι συχνά λιγότερο τρομακτικό να εργάζεστε σε έργα που δεν περιλαμβάνουν κώδικα, και η διαδικασία της συνεργασίας θα ενισχύσει την αυτοπεποίθηση και την εμπειρία σας. Προσανατολισμός σε ένα νέο έργο Αν πηγαίνετε σε έναν ανιχνευτή ζητημάτων και τα πράγματα φαίνονται συγκεχυμένα, δεν φταίτε μόνο εσείς. Αυτά τα εργαλεία απαιτούν πολλές σιωπηρές γνώσεις, αλλά οι άνθρωποι μπορούν να σας βοηθήσουν να περιηγηθείτε σε αυτά και μπορείτε να τους κάνετε ερωτήσεις. - @shaunagm, “How to Contribute to Open Source” Για οτιδήποτε περισσότερο από μια διόρθωση τυπογραφικού λάθους, η συνεισφορά στον ανοιχτό κώδικα είναι σαν να πηγαίνεις σε μια ομάδα αγνώστων σε ένα πάρτι. Αν αρχίσετε να μιλάτε για λάμα, ενώ αυτοί ήταν βαθιά χωμένοι σε μια συζήτηση για χρυσόψαρα, μάλλον θα σας κοιτάξουν λίγο περίεργα. Πριν πέσετε στα τυφλά με τις δικές σας προτάσεις, ξεκινήστε μαθαίνοντας πώς να διαβάζετε το δωμάτιο. Με αυτόν τον τρόπο αυξάνονται οι πιθανότητες να προσέξουν και να ακούσουν τις ιδέες σας. Ανατομία ενός έργου ανοικτού κώδικα Κάθε κοινότητα ανοικτού κώδικα είναι διαφορετική. Το να περάσετε χρόνια σε ένα έργο ανοιχτού κώδικα σημαίνει ότι έχετε γνωρίσει ένα έργο ανοιχτού κώδικα. Αν μετακινηθείτε σε ένα άλλο έργο, μπορεί να διαπιστώσετε ότι το λεξιλόγιο, οι κανόνες και οι τρόποι επικοινωνίας είναι εντελώς διαφορετικοί. Τούτου λεχθέντος, πολλά έργα ανοικτού κώδικα ακολουθούν μια παρόμοια οργανωτική δομή. Η κατανόηση των διαφορετικών ρόλων της κοινότητας και της συνολικής διαδικασίας θα σας βοηθήσει να προσανατολιστείτε γρήγορα σε οποιοδήποτε νέο έργο. Ένα τυπικό έργο ανοικτού κώδικα έχει τους ακόλουθους τύπους ανθρώπων: Συγγραφέας: Το άτομο/τα άτομα ή ο οργανισμός που δημιούργησε το έργο Δικαιούχος: Το άτομο/α που έχει/ουν τη διοικητική κυριότητα του οργανισμού ή του αποθετηρίου (δεν είναι πάντα το ίδιο με τον αρχικό συγγραφέα) Διαχειριστές: Συντελεστές που είναι υπεύθυνοι για την προώθηση του οράματος και τη διαχείριση των οργανωτικών πτυχών του έργου (μπορεί επίσης να είναι συγγραφείς ή ιδιοκτήτες του έργου). Συντελεστές: Όλοι όσοι έχουν συνεισφέρει κάτι στο έργο Μέλη της κοινότητας: Άνθρωποι που χρησιμοποιούν το έργο. Μπορεί να συμμετέχουν ενεργά σε συζητήσεις ή να εκφράζουν τη γνώμη τους για την κατεύθυνση του έργου Τα μεγαλύτερα έργα μπορεί επίσης να έχουν υποεπιτροπές ή ομάδες εργασίας που επικεντρώνονται σε διαφορετικά καθήκοντα, όπως η δημιουργία εργαλείων, η ταξινόμηση, ο συντονισμός της κοινότητας και η διοργάνωση εκδηλώσεων. Αναζητήστε στον ιστότοπο ενός έργου μια σελίδα “ομάδας” ή στο αποθετήριο για την τεκμηρίωση διακυβέρνησης, για να βρείτε αυτές τις πληροφορίες. Ένα έργο διαθέτει επίσης τεκμηρίωση. Αυτά τα αρχεία συνήθως παρατίθενται στο κορυφαίο επίπεδο ενός αποθετηρίου. LICENSE: Εξ ορισμού, κάθε έργο ανοικτού κώδικα πρέπει να έχει μια άδεια ανοικτού κώδικα . Εάν το έργο δεν έχει άδεια χρήσης, δεν είναι ανοικτού κώδικα. README: Το README είναι το εγχειρίδιο οδηγιών που καλωσορίζει τα νέα μέλη της κοινότητας στο έργο. Εξηγεί γιατί το έργο είναι χρήσιμο και πώς να ξεκινήσετε. CONTRIBUTING: Ενώ τα README βοηθούν τους ανθρώπους να χρησιμοποιήσουν το έργο, τα έγγραφα συνεισφοράς βοηθούν τους ανθρώπους να εισφέρουν στο έργο. Εξηγεί τι είδους συνεισφορές χρειάζονται και πώς λειτουργεί η διαδικασία. Αν και δεν έχει κάθε έργο ένα αρχείο CONTRIBUTING, η παρουσία του σηματοδοτεί ότι το έργο είναι φιλόξενο για συνεισφορά. CODE_OF_CONDUCT: Ο κώδικας δεοντολογίας θέτει βασικούς κανόνες για τη συμπεριφορά των συμμετεχόντων που σχετίζονται και βοηθά στη διευκόλυνση ενός φιλικού, φιλόξενου περιβάλλοντος. Αν και δεν έχει κάθε έργο ένα αρχείο CODE_OF_CONDUCT, η παρουσία του σηματοδοτεί ότι πρόκειται για ένα φιλόξενο έργο στο οποίο μπορείτε να συνεισφέρετε. Άλλη τεκμηρίωση: Ενδέχεται να υπάρχει πρόσθετη τεκμηρίωση, όπως σεμινάρια, οδηγίες χρήσης ή πολιτικές διακυβέρνησης, ειδικά σε μεγαλύτερα έργα. Τέλος, τα έργα ανοικτού κώδικα χρησιμοποιούν τα ακόλουθα εργαλεία για την οργάνωση της συζήτησης. Η ανάγνωση των αρχείων θα σας δώσει μια καλή εικόνα για το πώς σκέφτεται και λειτουργεί η κοινότητα. Issue tracker: Όπου οι άνθρωποι συζητούν θέματα που σχετίζονται με το έργο. Pull requests: Όπου οι άνθρωποι συζητούν και αναθεωρούν τις αλλαγές που βρίσκονται σε εξέλιξη. Φόρουμ συζητήσεων ή λίστες αλληλογραφίας: Ορισμένα έργα μπορεί να χρησιμοποιούν αυτά τα κανάλια για θέματα συζήτησης (για παράδειγμα, “Πώς μπορώ να…“ ή “Τι πιστεύετε για…“ αντί για αναφορές σφαλμάτων ή αιτήσεις για χαρακτηριστικά). Άλλα χρησιμοποιούν τον ανιχνευτή ζητημάτων για όλες τις συζητήσεις. Σύγχρονο κανάλι συνομιλίας: Ορισμένα έργα χρησιμοποιούν κανάλια συνομιλίας (όπως το Slack ή το IRC) για περιστασιακή συζήτηση, συνεργασία και γρήγορες ανταλλαγές. Βρίσκοντας ένα έργο για να συνεισφέρετε Τώρα που έχετε καταλάβει πώς λειτουργούν τα έργα ανοικτού κώδικα, ήρθε η ώρα να βρείτε ένα έργο για να συνεισφέρετε! Αν δεν έχετε συνεισφέρει ποτέ στο παρελθόν σε έργα ανοικτού κώδικα, ακολουθήστε τη συμβουλή του προέδρου των ΗΠΑ Τζον Φ. Κένεντι, ο οποίος είπε κάποτε: _“Μη ρωτάτε τι μπορεί να κάνει η χώρα σας για εσάς - ρωτήστε τι μπορείτε να κάνετε εσείς για τη χώρα σας”. Η συνεισφορά στον ανοικτό κώδικα γίνεται σε όλα τα επίπεδα, σε όλα τα έργα. Δεν χρειάζεται να σκεφτείτε υπερβολικά ποια ακριβώς θα είναι η πρώτη σας συνεισφορά ή πώς θα φαίνεται. Αντ’ αυτού, ξεκινήστε σκεπτόμενοι τα έργα που ήδη χρησιμοποιείτε ή θέλετε να χρησιμοποιήσετε. Τα έργα στα οποία θα συνεισφέρετε ενεργά είναι αυτά στα οποία θα βρίσκεστε να επιστρέφετε. Μέσα σε αυτά τα έργα, όποτε πιάνετε τον εαυτό σας να σκέφτεται ότι κάτι θα μπορούσε να είναι καλύτερο ή διαφορετικό, ακολουθήστε το ένστικτό σας. Ο ανοιχτός κώδικας δεν είναι μια αποκλειστική λέσχη- φτιάχνεται από ανθρώπους σαν εσάς. Ο “ανοικτός κώδικας” είναι απλώς ένας φανταχτερός όρος για να αντιμετωπίζεις τα προβλήματα του κόσμου ως επιλύσιμα. Μπορεί να σκανάρετε ένα README και να βρείτε έναν σπασμένο σύνδεσμο ή ένα τυπογραφικό λάθος. Ή είστε νέος χρήστης και παρατηρήσατε ότι κάτι είναι σπασμένο ή ένα θέμα που πιστεύετε ότι θα έπρεπε πραγματικά να υπάρχει στην τεκμηρίωση. Αντί να το αγνοήσετε και να προχωρήσετε ή να ζητήσετε από κάποιον άλλο να το διορθώσει, δείτε αν μπορείτε να βοηθήσετε με τη συμμετοχή σας. Αυτό είναι το νόημα του ανοιχτού κώδικα! Το 28% των περιστασιακών συνεισφορών στον ανοικτό κώδικα είναι τεκμηρίωση, όπως διόρθωση τυπογραφικών λαθών, αναδιαμόρφωση ή συγγραφή μετάφρασης. Αν ψάχνετε για υπάρχοντα θέματα που μπορείτε να διορθώσετε, κάθε έργο ανοιχτού κώδικα έχει μια σελίδα /contribute που επισημαίνει θέματα φιλικά προς τους αρχάριους με τα οποία μπορείτε να ξεκινήσετε. Πλοηγηθείτε στην κεντρική σελίδα του αποθετηρίου στο GitHub και προσθέστε /contribute στο τέλος της διεύθυνσης URL (για παράδειγμα https://github.com/facebook/react/contribute ). Μπορείτε επίσης να χρησιμοποιήσετε έναν από τους παρακάτω πόρους για να σας βοηθήσει να ανακαλύψετε και να συνεισφέρετε σε νέα έργα: GitHub Explore Open Source Friday First Timers Only CodeTriage 24 Pull Requests Up For Grabs First Contributions SourceSort OpenSauced Μια λίστα ελέγχου πριν συνεισφέρετε Όταν έχετε βρει ένα έργο στο οποίο θα θέλατε να συνεισφέρετε, κάντε ένα γρήγορο έλεγχο για να βεβαιωθείτε ότι το έργο είναι κατάλληλο για να δέχεται συνεισφορές. Διαφορετικά, η σκληρή δουλειά σας μπορεί να μην βρει ποτέ ανταπόκριση. Ακολουθεί ένας εύχρηστος κατάλογος ελέγχου για να αξιολογήσετε αν ένα έργο είναι κατάλληλο για νέους συνεισφέροντες. Meets the definition of open source Έχει άδεια; Συνήθως, υπάρχει ένα αρχείο που ονομάζεται LICENSE στη ρίζα του αποθετηρίου. Το έργο δέχεται ενεργά συνεισφορές Κοιτάξτε τη δραστηριότητα των δεσμεύσεων στον κύριο κλάδο. Στο GitHub, μπορείτε να δείτε αυτές τις πληροφορίες στην αρχική σελίδα ενός αποθετηρίου. Πότε έγινε το τελευταίο commit; Πόσους συνεισφέροντες έχει το πρότζεκτ; Πόσο συχνά κάνει commit ο κόσμος; (Στο GitHub, μπορείτε να βρείτε αυτή την πληροφορία κάνοντας κλίκ στο "Commits" στην επάνω μπάρα.) Στη συνέχεια, εξετάστε τα ζητήματα του πρότζεκτ. Πόσα ζητήματα υπάρχουν; Ανταποκρίνονται οι συντηρητές γρήγορα στα θέματα που ανοίγουν; Υπάρχει ενεργή συζήτηση επί των θεμάτων; Είναι τα θέματα πρόσφατα; Κλείνουν τα θέματα; (Στο GitHub, κάντε κλικ στην καρτέλα "closed" στη σελίδα Issues για να δείτε τα κλειστά ζητήματα. Τώρα κάντε το ίδιο για τις αιτήσεις έλξης του έργου. Πόσες ανοιχτές αιτήσεις έλξης υπάρχουν; Οι συντηρητές ανταποκρίνονται γρήγορα στις αιτήσεις έλξης όταν ανοίγουν; Υπάρχει ενεργή συζήτηση σχετικά με τα pull requests; Είναι πρόσφατες οι αιτήσεις έλξης; Πόσο πρόσφατα συγχωνεύτηκαν κάποια pull requests; (Στο GitHub, κάντε κλικ στην καρτέλα "closed" στη σελίδα Pull Requests για να δείτε τα κλειστά PRs.) Το έργο είναι φιλόξενο Ένα έργο που είναι φιλικό και φιλόξενο σηματοδοτεί ότι θα είναι δεκτικό σε νέους συνεισφέροντες. Ανταποκρίνονται οι συντηρητές βοηθητικά στις ερωτήσεις στα θέματα; Είναι οι άνθρωποι φιλικοί στα θέματα, στο φόρουμ συζητήσεων και στη συνομιλία (για παράδειγμα, στο IRC ή στο Slack); Επανεξετάζονται τα pull requests; Οι συντηρητές ευχαριστούν τους ανθρώπους για τις συνεισφορές τους; Κάθε φορά που βλέπετε ένα μακρύ νήμα, ελέγξτε επιτόπου τις απαντήσεις από τους προγραμματιστές του πυρήνα που έρχονται αργά στο νήμα. Συνοψίζουν εποικοδομητικά και λαμβάνουν μέτρα για να οδηγήσουν το νήμα σε μια απόφαση παραμένοντας ευγενικοί; Αν βλέπετε να γίνονται πολλοί πόλεμοι φλογών, αυτό είναι συχνά σημάδι ότι η ενέργεια πηγαίνει σε επιχειρήματα αντί για την ανάπτυξη. — @kfogel, Producing OSS Πώς να υποβάλετε μια συνεισφορά Βρήκατε ένα έργο που σας αρέσει και είστε έτοιμοι να συνεισφέρετε. Επιτέλους! Εδώ θα δείτε πώς θα στείλετε τη συνεισφορά σας με τον σωστό τρόπο. Αποτελεσματική επικοινωνία Είτε συνεισφέρετε μια φορά είτε προσπαθείτε να ενταχθείτε σε μια κοινότητα, η συνεργασία με άλλους είναι μια από τις σημαντικότερες δεξιότητες που θα αναπτύξετε στον ανοιχτό κώδικα. [Ως νέος συνεισφέρων,] γρήγορα συνειδητοποίησα ότι έπρεπε να κάνω ερωτήσεις αν ήθελα να μπορέσω να κλείσω το θέμα. Ξεφύλλισα τη βάση κώδικα. Μόλις κατάλαβα τι συνέβαινε, ζήτησα περισσότερες οδηγίες. Και ιδού! Μπόρεσα να λύσω το ζήτημα αφού πήρα όλες τις σχετικές λεπτομέρειες που χρειαζόμουν. - @shubheksha, A Beginner’s Very Bumpy Journey Through The World of Open Source Προτού ανοίξετε ένα θέμα ή ένα pull request ή κάνετε μια ερώτηση στη συνομιλία, έχετε υπόψη σας αυτά τα σημεία για να βοηθήσετε τις ιδέες σας να περάσουν αποτελεσματικά. Δώστε πλαίσιο. Βοηθήστε τους άλλους να ενημερωθούν γρήγορα. Αν αντιμετωπίζετε ένα σφάλμα, εξηγήστε τι προσπαθείτε να κάνετε και πώς να το αναπαράγετε. Αν προτείνετε μια νέα ιδέα, εξηγήστε γιατί πιστεύετε ότι θα ήταν χρήσιμη για το έργο (όχι μόνο για εσάς!). 😇 “Το Χ δεν συμβαίνει όταν κάνω το Υ” 😢 “Το X είναι χαλασμένο! Σε παρακαλώ, διόρθωσέ το.” Κάντε την έρευνα σας εκ των προτέρων. Δεν πειράζει να μην ξέρετε πράγματα, αλλά δείξτε ότι προσπαθήσατε. Πριν ζητήσετε βοήθεια, φροντίστε να ελέγξετε το README ενός έργου, την τεκμηρίωση, τα θέματα (ανοικτά ή κλειστά), τη λίστα αλληλογραφίας και να ψάξετε στο διαδίκτυο για μια απάντηση. Οι άνθρωποι θα το εκτιμήσουν όταν δείχνετε ότι προσπαθείτε να μάθετε. 😇 “Δεν είμαι σίγουρος πώς να υλοποιήσω το X. Έλεγξα τα έγγραφα βοήθειας και δεν βρήκα καμία αναφορά.” 😢 “Πώς μπορώ να κάνω το X;” Κρατήστε τα αιτήματα σύντομα και άμεσα. Όπως και με την αποστολή ενός email, κάθε συνεισφορά, όσο απλή ή χρήσιμη κι αν είναι, απαιτεί την εξέταση κάποιου άλλου. Πολλά έργα έχουν περισσότερα εισερχόμενα αιτήματα από άτομα που είναι διαθέσιμα να βοηθήσουν. Να είστε συνοπτικοί. Θα αυξήσετε την πιθανότητα να μπορέσει κάποιος να σας βοηθήσει. 😇 “Θα ήθελα να γράψω ένα tutorial για API.” 😢 “Οδηγούσα στον αυτοκινητόδρομο τις προάλλες και σταμάτησα για βενζίνη, και τότε μου ήρθε αυτή η καταπληκτική ιδέα για κάτι που πρέπει να κάνουμε, αλλά πριν σας το εξηγήσω, επιτρέψτε μου να σας δείξω…“ Κρατήστε όλη την επικοινωνία δημόσια. Αν και είναι δελεαστικό, μην επικοινωνείτε με τους συντηρητές ιδιωτικά, εκτός αν πρέπει να μοιραστείτε ευαίσθητες πληροφορίες (όπως ένα ζήτημα ασφάλειας ή μια σοβαρή παραβίαση συμπεριφοράς). Όταν κρατάτε τη συζήτηση δημόσια, περισσότεροι άνθρωποι μπορούν να μάθουν και να επωφεληθούν από την ανταλλαγή σας. Οι συζητήσεις μπορούν να είναι, από μόνες τους, συνεισφορές. 😇 (ως σχόλιο) “@-maintainer Γεια σας! Πώς θα πρέπει να προχωρήσουμε σε αυτή τη δημοσιότητα;” 😢 (ως email) “Γεια σου, συγγνώμη που σε ενοχλώ μέσω email, αλλά αναρωτιόμουν αν είχες την ευκαιρία να αναθεωρήσεις το PR μου” Δεν πειράζει να κάνετε ερωτήσεις (αλλά να είστε υπομονετικοί!). Όλοι ήταν νέοι στο έργο κάποια στιγμή, και ακόμη και οι έμπειροι συνεισφέροντες πρέπει να ενημερωθούν όταν βλέπουν ένα νέο έργο. Με την ίδια λογική, ακόμη και οι μακροχρόνιοι συντηρητές δεν είναι πάντα εξοικειωμένοι με κάθε μέρος του έργου. Δείξτε τους την ίδια υπομονή που θα θέλατε να δείξουν και αυτοί σε εσάς. 😇 “Ευχαριστώ που εξετάσατε αυτό το σφάλμα. Ακολούθησα τις προτάσεις σας. Εδώ είναι η έξοδος.” 😢 “Γιατί δεν μπορείτε να διορθώσετε το πρόβλημά μου; Αυτό δεν είναι το έργο σας;” Σεβαστείτε τις αποφάσεις της κοινότητας. Οι ιδέες σας μπορεί να διαφέρουν από τις προτεραιότητες ή το όραμα της κοινότητας. Μπορεί να προσφέρουν ανατροφοδότηση ή να αποφασίσουν να μην ακολουθήσουν την ιδέα σας. Ενώ θα πρέπει να συζητάτε και να αναζητάτε συμβιβασμούς, οι συντηρητές πρέπει να ζουν με την απόφασή σας περισσότερο από ό,τι εσείς. Αν διαφωνείτε με την κατεύθυνσή τους, μπορείτε πάντα να δουλέψετε πάνω στο δικό σας fork ή να ξεκινήσετε το δικό σας έργο. 😇 “Απογοητεύομαι που δεν μπορείτε να υποστηρίξετε την περίπτωση χρήσης μου, αλλά όπως εξηγήσατε επηρεάζει μόνο ένα μικρό μέρος των χρηστών, καταλαβαίνω γιατί. Ευχαριστώ που με ακούσατε.” 😢 “Γιατί δεν υποστηρίζετε την περίπτωση χρήσης μου; Αυτό είναι απαράδεκτο!” Πάνω απ’ όλα, κρατήστε το κομψό. Ο ανοικτός κώδικας αποτελείται από συνεργάτες από όλο τον κόσμο. Τα συμφραζόμενα χάνονται μεταξύ γλωσσών, πολιτισμών, γεωγραφικών περιοχών και ζωνών ώρας. Επιπλέον, η γραπτή επικοινωνία δυσκολεύει τη μετάδοση του τόνου ή της διάθεσης. Υποθέστε καλές προθέσεις σε αυτές τις συζητήσεις. Δεν πειράζει να απορρίψετε ευγενικά μια ιδέα, να ζητήσετε περισσότερα συμφραζόμενα ή να διευκρινίσετε περαιτέρω τη θέση σας. Απλά προσπαθήστε να αφήσετε το διαδίκτυο σε ένα καλύτερο μέρος από αυτό που βρήκατε. Συγκέντρωση περιεχομένου Πριν κάνετε οτιδήποτε, κάντε έναν γρήγορο έλεγχο για να βεβαιωθείτε ότι η ιδέα σας δεν έχει συζητηθεί αλλού. Ξεφυλλίστε το README του έργου, τα θέματα (ανοικτά και κλειστά), τη λίστα αλληλογραφίας και το Stack Overflow. Δεν χρειάζεται να ξοδέψετε ώρες για να ψάξετε τα πάντα, αλλά μια γρήγορη αναζήτηση για μερικούς όρους-κλειδιά θα σας βοηθήσει πολύ. Αν δεν μπορείτε να βρείτε την ιδέα σας αλλού, είστε έτοιμοι να κάνετε μια κίνηση. Αν το έργο βρίσκεται στο GitHub, πιθανότατα θα επικοινωνήσετε ανοίγοντας ένα ζήτημα ή ένα pull request: Τα θέματα είναι σαν να ξεκινάτε μια συζήτηση ή μια συζήτηση Αιτήματα μετακίνησης είναι για την έναρξη της εργασίας πάνω σε μια λύση Για ελαφριά επικοινωνία , όπως μια διευκρινιστική ερώτηση ή μια ερώτηση για το πώς να κάνετε, δοκιμάστε να ρωτήσετε στο Stack Overflow, στο IRC, στο Slack ή σε άλλα κανάλια συνομιλίας, αν το έργο διαθέτει τέτοιο κανάλι. Πριν ανοίξετε ένα θέμα ή ένα αίτημα έλξης, ελέγξτε τα έγγραφα συνεισφοράς του έργου (συνήθως ένα αρχείο που ονομάζεται ΣΥΝΔΡΟΜΗ ή στο README), για να δείτε αν πρέπει να συμπεριλάβετε κάτι συγκεκριμένο. Για παράδειγμα, μπορεί να σας ζητούν να ακολουθήσετε ένα πρότυπο ή να απαιτείται η χρήση δοκιμών. Αν θέλετε να κάνετε μια ουσιαστική συνεισφορά, ανοίξτε ένα θέμα για να ρωτήσετε πριν εργαστείτε πάνω σε αυτό. Είναι χρήσιμο να παρακολουθείτε το έργο για λίγο (στο GitHub, μπορείτε να κάνετε κλικ στο “Watch” για να ενημερώνεστε για όλες τις συζητήσεις), και να γνωρίσετε τα μέλη της κοινότητας, πριν κάνετε εργασία που μπορεί να μην γίνει αποδεκτή. You’ll learn a lot from taking a single project you actively use, “watching” it on GitHub and reading every issue and PR. — @gaearon on joining projects Άνοιγμα ενός θέματος Συνήθως πρέπει να ανοίγετε ένα θέμα στις ακόλουθες περιπτώσεις: Αναφέρετε ένα σφάλμα που δεν μπορείτε να λύσετε μόνοι σας Συζητήστε ένα θέμα ή μια ιδέα υψηλού επιπέδου (για παράδειγμα, κοινότητα, όραμα ή πολιτικές) Προτείνετε ένα νέο χαρακτηριστικό ή μια άλλη ιδέα έργου Συμβουλές για την επικοινωνία σχετικά με θέματα: Αν δείτε ένα ανοιχτό ζήτημα που θέλετε να αντιμετωπίσετε, σχολιάστε το ζήτημα για να ενημερώσετε τους άλλους ότι ασχολείστε με αυτό. Με αυτόν τον τρόπο, οι άνθρωποι είναι λιγότερο πιθανό να αντιγράψουν τη δουλειά σας. Αν ένα θέμα έχει ανοίξει πριν από καιρό, είναι πιθανό να αντιμετωπίζεται κάπου αλλού ή να έχει ήδη επιλυθεί, οπότε σχολιάστε για να ζητήσετε επιβεβαίωση πριν ξεκινήσετε την εργασία. Αν ανοίξατε ένα θέμα, αλλά βρήκατε την απάντηση αργότερα μόνοι σας, σχολιάστε το θέμα για να ενημερώσετε τους άλλους και, στη συνέχεια, κλείστε το θέμα. Ακόμα και η τεκμηρίωση αυτού του αποτελέσματος αποτελεί συμβολή στο έργο. Άνοιγμα ενός αιτήματος αλλαγής κειμένου Συνήθως θα πρέπει να ανοίγετε ένα pull request στις ακόλουθες περιπτώσεις: Υποβολή ασήμαντων διορθώσεων (για παράδειγμα, ένα τυπογραφικό λάθος, ένας σπασμένος σύνδεσμος ή ένα προφανές σφάλμα) Ξεκινήστε να εργάζεστε σε μια συνεισφορά που σας έχει ήδη ζητηθεί, ή που έχετε ήδη συζητήσει, σε ένα θέμα Ένα pull request δεν χρειάζεται να αντιπροσωπεύει ολοκληρωμένη εργασία. Συνήθως είναι καλύτερο να ανοίξετε ένα pull request νωρίς, ώστε οι άλλοι να μπορούν να παρακολουθήσουν ή να δώσουν ανατροφοδότηση σχετικά με την πρόοδό σας. Απλά σημειώστε το ως “WIP” (Work in Progress) στη γραμμή θέματος. Μπορείτε πάντα να προσθέσετε περισσότερα commits αργότερα. Αν το έργο βρίσκεται στο GitHub, δείτε πώς μπορείτε να υποβάλετε ένα pull request: Κάντε fork το πρότζεκτ και κλωνοποιήστε το τοπικά. Συνδέστε το τοπικό σας με το αρχικό “upstream” αποθετήριο προσθέτοντάς το ως απομακρυσμένο. Τραβήξτε συχνά αλλαγές από το “upstream” ώστε να παραμένετε ενημερωμένοι, ώστε όταν υποβάλετε το pull request σας, οι συγκρούσεις συγχώνευσης να είναι λιγότερο πιθανές. (Δείτε πιο λεπτομερείς οδηγίες εδώ .) Δημιουργήστε έναν κλάδο για τις επεξεργασίες σας. Αναφέρετε οποιαδήποτε σχετικά θέματα ή υποστηρικτική τεκμηρίωση στο PR σας (για παράδειγμα, “Κλείνει το #37.”) Περιλάβετε στιγμιότυπα οθόνης του πριν και του μετά αν οι αλλαγές σας περιλαμβάνουν διαφορές στην HTML/CSS. Σύρετε και αφήστε τις εικόνες στο σώμα του αιτήματος έλξης σας. Δοκιμάστε τις αλλαγές σας! Ελέγξτε τις αλλαγές σας με τυχόν υπάρχουσες δοκιμές, αν υπάρχουν, και δημιουργήστε νέες, όταν χρειάζεται. Είτε υπάρχουν δοκιμές είτε όχι, βεβαιωθείτε ότι οι αλλαγές σας δεν καταστρέφουν το υπάρχον έργο. Συνεισφέρετε στο ύφος του έργου στο μέτρο των δυνατοτήτων σας. Αυτό μπορεί να σημαίνει ότι χρησιμοποιείτε εσοχές, άνω και κάτω τελεία ή σχόλια διαφορετικά από ό,τι θα κάνατε στο δικό σας αποθετήριο, αλλά διευκολύνει τον συντηρητή να συγχωνεύσει, άλλους να καταλάβουν και να συντηρήσουν στο μέλλον. Αν αυτό είναι το πρώτο σας pull request, ελέγξτε το Make a Pull Request , το οποίο δημιούργησε ο @kentcdodds ως ένα βίντεο με οδηγίες. Μπορείτε επίσης να εξασκηθείτε στο να κάνετε ένα pull request στο αποθετήριο First Contributions , που δημιουργήθηκε από τον @Roshanjossey. Τι συμβαίνει μετά την υποβολή μιας συνεισφοράς Τα καταφέρατε! Συγχαρητήρια που γίνατε συνεργάτης ανοιχτού κώδικα. Ελπίζουμε να είναι η πρώτη από τις πολλές. Αφού υποβάλετε μια συνεισφορά, θα συμβεί ένα από τα ακόλουθα: 😭 Δεν λαμβάνετε απάντηση. Ελπίζουμε ότι ελέγξατε το έργο για σημάδια δραστηριότητας πριν κάνετε μια συνεισφορά. Ακόμα και σε ένα ενεργό έργο, ωστόσο, είναι πιθανό η συνεισφορά σας να μην λάβει απάντηση. Αν δεν έχετε λάβει απάντηση για πάνω από μια εβδομάδα, είναι δίκαιο να απαντήσετε ευγενικά στο ίδιο θέμα, ζητώντας από κάποιον να το αξιολογήσει. Αν γνωρίζετε το όνομα του κατάλληλου ατόμου που θα αξιολογήσει τη συνεισφορά σας, μπορείτε να τον @-αναφέρετε στο ίδιο θέμα. Μην απευθυνθείτε σε αυτό το άτομο ιδιωτικά- να θυμάστε ότι η δημόσια επικοινωνία είναι ζωτικής σημασίας για τα έργα ανοικτού κώδικα. Αν κάνετε ένα ευγ | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/tencentglobal-cloud-virtual-machine-cvm/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Cloud Virtual Machine (CVM) | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloud Virtual Machine (CVM) Server Virtualization Software by Tencent See who's skilled in this Add as skill Learn more Report this product About Tencent Cloud Virtual Machine offers stable, secure, resilient, and high-performance cloud computing service Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://opensource.guide/el/leadership-and-governance/ | Ηγεσία και Διοίκηση | Open Source Guides Σχετικά με Συνεισφορά العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Ηγεσία και Διοίκηση Τα αναπτυσσόμενα πρότζεκτς ανοιχτού κώδικα μπορούν να επωφεληθούν από επίσημους κανόνες για τη λήψη αποφάσεων. Πίνακας Περιεχομένων Κατανόηση της διακυβέρνησης για το αναπτυσσόμενο πρότζεκτ σας Ποια είναι παραδείγματα επίσημων ρόλων που χρησιμοποιούνται σε πρότζεκτ ανοικτού κώδικα; Πώς μπορώ να επισημοποιήσω αυτούς τους ηγετικούς ρόλους; Πότε θα πρέπει να δώσω σε κάποιον πρόσβαση στα commits; Ποιες είναι μερικές από τις συνήθεις δομές διακυβέρνησης για πρότζεκτ ανοικτού κώδικα; Χρειάζομαι έγγραφα διακυβέρνησης όταν ξεκινάω το πρότζεκτ μου; Τι θα συμβεί αν οι εταιρικοί υπάλληλοι αρχίσουν να υποβάλλουν συνεισφορές; Κατανόηση της διακυβέρνησης για το αναπτυσσόμενο πρότζεκτ σας Το πρότζεκτ σας αναπτύσσεται, οι άνθρωποι είναι αφοσιωμένοι και είστε αποφασισμένοι να το συνεχίσετε. Σε αυτό το στάδιο, μπορεί να αναρωτιέστε πώς να ενσωματώσετε τους τακτικούς συνεργάτες του πρότζεκτ στη ροή εργασίας σας, είτε πρόκειται για την παροχή σε κάποιον πρόσβασης στη δέσμευση είτε για την επίλυση των συζητήσεων της κοινότητας. Αν έχετε απορίες, έχουμε απαντήσεις. Ποια είναι παραδείγματα επίσημων ρόλων που χρησιμοποιούνται σε πρότζεκτ ανοικτού κώδικα; Πολλά πρότζεκτ ακολουθούν μια παρόμοια δομή για τους ρόλους και την αναγνώριση των συνεισφερόντων. Το τι σημαίνουν στην πραγματικότητα αυτοί οι ρόλοι, όμως, εξαρτάται αποκλειστικά από εσάς. Ακολουθούν μερικοί τύποι ρόλων που μπορεί να αναγνωρίσετε: Συντηρητής Contributor Committer Για ορισμένα πρότζεκτ, οι “συντηρητές” είναι τα μόνα άτομα σε ένα πρότζεκτ με πρόσβαση στa commits. Σε άλλα πρότζεκτ, είναι απλά τα άτομα που αναφέρονται στο README ως συντηρητές. Ένας συντηρητής δεν χρειάζεται απαραίτητα να είναι κάποιος που γράφει κώδικα για το πρότζεκτ σας. Θα μπορούσε να είναι κάποιος που έχει κάνει πολλή δουλειά για να ευαγγελιστεί το πρότζεκτ σας, ή έχει γράψει τεκμηρίωση που έκανε το πρότζεκτ πιο προσιτό σε άλλους. Ανεξάρτητα από το τι κάνει καθημερινά, ένας συντηρητής είναι πιθανότατα κάποιος που αισθάνεται την ευθύνη για την κατεύθυνση του πρότζεκτ και δεσμεύεται να το βελτιώσει. Ένας “contributor” θα μπορούσε να είναι οποιοσδήποτε που σχολιάζει ένα θέμα ή ένα pull request, άνθρωποι που προσθέτουν αξία στο πρότζεκτ (είτε πρόκειται για τη διαχείριση θεμάτων, τη συγγραφή κώδικα ή τη διοργάνωση εκδηλώσεων), ή οποιοσδήποτε με ένα συγχωνευμένο pull request (ίσως ο στενότερος ορισμός ενός contributor). [Για το Node.js,] κάθε άτομο που εμφανίζεται για να σχολιάσει ένα θέμα ή να υποβάλει κώδικα είναι μέλος της κοινότητας ενός πρότζεκτ. Και μόνο το γεγονός ότι είναι σε θέση να τους βλέπεις σημαίνει ότι είναι πια συνεισφέροντες και όχι απλώς χρήστες. - @mikeal, “Healthy Open Source” Ο όρος “committer” θα μπορούσε να χρησιμοποιηθεί για να διακρίνει την πρόσβαση στα commits, η οποία είναι ένας συγκεκριμένος τύπος ευθύνης, από άλλες μορφές συνεισφοράς. Ενώ μπορείτε να ορίσετε τους ρόλους του πρότζεκτ σας με όποιον τρόπο θέλετε, εξετάστε το ενδεχόμενο να χρησιμοποιήσετε ευρύτερους ορισμούς για να ενθαρρύνετε περισσότερες μορφές συνεισφοράς. Μπορείτε να χρησιμοποιήσετε τους ρόλους ηγεσίας για να αναγνωρίσετε επίσημα τους ανθρώπους που έχουν συνεισφέρει εξαιρετικά στο πρότζεκτ σας, ανεξάρτητα από τις τεχνικές τους δεξιότητες. Μπορεί να με ξέρετε ως τον “εφευρέτη” του Django… αλλά στην πραγματικότητα είμαι ο τύπος που προσλήφθηκε για να δουλέψει πάνω σε ένα πράγμα ένα χρόνο αφότου είχε ήδη φτιαχτεί. (…) Οι άνθρωποι υποψιάζονται ότι είμαι επιτυχημένος λόγω των προγραμματιστικών μου ικανοτήτων… αλλά είμαι στην καλύτερη περίπτωση ένας μέτριος προγραμματιστής. - @jacobian, “PyCon 2015 Keynote” (video) Πώς μπορώ να επισημοποιήσω αυτούς τους ηγετικούς ρόλους; Η επισημοποίηση των ηγετικών σας ρόλων βοηθάει τους ανθρώπους να αισθάνονται ιδιοκτησία και λέει στα άλλα μέλη της κοινότητας σε ποιον να απευθυνθούν για βοήθεια. Για ένα μικρότερο πρότζεκτ, ο ορισμός των ηγετών μπορεί να είναι τόσο απλός όσο η προσθήκη των ονομάτων τους στο README ή σε ένα αρχείο κειμένου CONTRIBUTORS. Για ένα μεγαλύτερο πρότζεκτ, αν έχετε έναν ιστότοπο, δημιουργήστε μια σελίδα ομάδας ή αναφέρετε εκεί τους επικεφαλής του πρότζεκτ σας. Για παράδειγμα, το Postgres έχει μια ολοκληρωμένη σελίδα ομάδας με σύντομα προφίλ για κάθε συνεισφέροντα. Εάν το πρότζεκτ σας έχει μια πολύ ενεργή κοινότητα συνεισφερόντων, μπορείτε να δημιουργήσετε μια “βασική ομάδα” συντηρητών ή ακόμη και υποεπιτροπές ατόμων που αναλαμβάνουν την ευθύνη για διαφορετικούς τομείς θεμάτων (για παράδειγμα, ασφάλεια, διαχείριση θεμάτων ή συμπεριφορά της κοινότητας). Αφήστε τους ανθρώπους να αυτοοργανωθούν και να αναλάβουν εθελοντικά τους ρόλους που τους ενθουσιάζουν περισσότερο, αντί να τους αναθέσετε. [Εμείς] συμπληρώνουμε τη βασική ομάδα με διάφορες “υποομάδες”. Κάθε υποομάδα επικεντρώνεται σε έναν συγκεκριμένο τομέα, π.χ. στο σχεδιασμό γλωσσών ή στις βιβλιοθήκες. (…) Για να εξασφαλιστεί ο συνολικός συντονισμός και ένα ισχυρό, συνεκτικό όραμα για το πρότζεκτ ως σύνολο, κάθε υποομάδα καθοδηγείται από ένα μέλος της βασικής ομάδας. - “Rust Governance RFC” Οι ηγετικές ομάδες μπορεί να θέλουν να δημιουργήσουν ένα καθορισμένο κανάλι (όπως στο IRC) ή να συναντώνται τακτικά για να συζητούν το πρότζεκτ (όπως στο Gitter ή στο Google Hangout). Μπορείτε ακόμη και να κάνετε αυτές τις συναντήσεις δημόσιες ώστε να μπορούν να τις ακούνε και άλλοι. Το Cucumber-ruby , για παράδειγμα, φιλοξενεί ώρες γραφείου κάθε εβδομάδα . Αφού καθιερώσετε ηγετικούς ρόλους, μην ξεχάσετε να τεκμηριώσετε πώς οι άνθρωποι μπορούν να τους αποκτήσουν! Καθορίστε μια σαφή διαδικασία για το πώς κάποιος μπορεί να γίνει συντηρητής ή να ενταχθεί σε μια υποεπιτροπή του πρότζεκτ σας και γράψτε την στο GOVERNANCE.md. Εργαλεία όπως το Vossibility μπορούν να σας βοηθήσουν να παρακολουθείτε δημόσια ποιος συνεισφέρει (ή δεν συνεισφέρει) στο πρότζεκτ. Η τεκμηρίωση αυτών των πληροφοριών αποφεύγει την αντίληψη της κοινότητας ότι οι συντηρητές είναι μια κλίκα που παίρνει τις αποφάσεις της ιδιωτικά. Τέλος, αν το πρότζεκτ σας βρίσκεται στο GitHub, εξετάστε το ενδεχόμενο να μεταφέρετε το πρότζεκτ σας από τον προσωπικό σας λογαριασμό σε έναν Οργανισμό και να προσθέσετε τουλάχιστον έναν εφεδρικό διαχειριστή. Οι Οργανισμοί του GitHub διευκολύνουν τη διαχείριση των δικαιωμάτων και των πολλαπλών αποθετηρίων και προστατεύουν την κληρονομιά του πρότζεκτ σας μέσω της κοινής ιδιοκτησίας . Πότε θα πρέπει να δώσω σε κάποιον πρόσβαση στα commits; Κάποιοι πιστεύουν ότι πρέπει να δίνετε πρόσβαση στα commits σε όλους όσους συνεισφέρουν. Κάτι τέτοιο θα μπορούσε να ενθαρρύνει περισσότερους ανθρώπους να νιώσουν ιδιοκτησία του πρότζεκτ σας. Από την άλλη πλευρά, ειδικά για μεγαλύτερα, πιο σύνθετα πρότζεκτ, μπορεί να θέλετε να δώσετε πρόσβαση στη δέσμευση μόνο σε άτομα που έχουν αποδείξει τη δέσμευσή τους. Δεν υπάρχει ένας μόνο σωστός τρόπος - κάντε αυτό που σας κάνει να αισθάνεστε πιο άνετα! Αν το πρότζεκτ σας βρίσκεται στο GitHub, μπορείτε να χρησιμοποιήσετε το protected branches για να διαχειριστείτε ποιος μπορεί να προωθήσει σε ένα συγκεκριμένο κλάδο και υπό ποιες συνθήκες. Κάθε φορά που κάποιος σας στέλνει ένα pull request, δώστε του πρόσβαση στα commits στο πρότζεκτ σας. Αν και μπορεί να ακούγεται απίστευτα ανόητο στην αρχή, η χρήση αυτής της στρατηγικής θα σας επιτρέψει να απελευθερώσετε την πραγματική δύναμη του GitHub. (…) Μόλις οι άνθρωποι έχουν πρόσβαση στα commits, δεν ανησυχούν πλέον ότι η διόρθωσή τους μπορεί να μην ενσωματωθεί… με αποτέλεσμα να βάλουν πολύ περισσότερη δουλειά σε αυτήν. - @felixge, “The Pull Request Hack” Ποιες είναι μερικές από τις συνήθεις δομές διακυβέρνησης για πρότζεκτ ανοικτού κώδικα; Υπάρχουν τρεις κοινές δομές διακυβέρνησης που σχετίζονται με πρότζεκτ ανοικτού κώδικα. BDFL: Το BDFL σημαίνει “καλοπροαίρετος δικτάτορας για όλη τη ζωή” (Benevolent Dictator For Life). Σύμφωνα με αυτή τη δομή, ένα άτομο (συνήθως ο αρχικός ιδιοκτήτης του πρότζεκτ) έχει τον τελικό λόγο σε όλες τις σημαντικές αποφάσεις του πρότζεκτ. Η Python είναι ένα κλασικό παράδειγμα. Τα μικρότερα πρότζεκτ είναι πιθανώς εξ ορισμού BDFL, επειδή υπάρχουν μόνο ένας ή δύο συντηρητές. Ένα πρότζεκτ που προέρχεται από μια εταιρεία μπορεί επίσης να εμπίπτει στην κατηγορία BDFL. Μεριτοκρατία: (Σημείωση: ο όρος “αξιοκρατία” έχει αρνητική χροιά για ορισμένες κοινότητες και έχει μια πολύπλοκη κοινωνική και πολιτική ιστορία .) Στο πλαίσιο μιας αξιοκρατίας, στους ενεργούς συνεισφέροντες στο πρότζεκτ (αυτούς που επιδεικνύουν “αξία”) δίνεται επίσημος ρόλος στη λήψη αποφάσεων. Οι αποφάσεις λαμβάνονται συνήθως με βάση την καθαρή συναίνεση της ψηφοφορίας. Η έννοια της αξιοκρατίας πρωτοπορήθηκε από το Apache Foundation - όλα τα πρότζεκτ του Apache είναι αξιοκρατίες. Οι συνεισφορές μπορούν να γίνουν μόνο από άτομα που εκπροσωπούν τον εαυτό τους, όχι από μια εταιρεία. Φιλελεύθερη συνεισφορά: Σύμφωνα με το μοντέλο της φιλελεύθερης συνεισφοράς, τα άτομα που κάνουν τη μεγαλύτερη δουλειά αναγνωρίζονται ως τα άτομα με τη μεγαλύτερη επιρροή, αλλά αυτό βασίζεται στην τρέχουσα δουλειά και όχι στις ιστορικές συνεισφορές. Οι σημαντικές αποφάσεις για το πρότζεκτ λαμβάνονται με βάση μια διαδικασία αναζήτησης συναίνεσης (συζήτηση των σημαντικότερων παραπόνων) και όχι με καθαρή ψηφοφορία, και επιδιώκεται να συμπεριληφθούν όσο το δυνατόν περισσότερες προοπτικές της κοινότητας. Δημοφιλή παραδείγματα πρότζεκτ που χρησιμοποιούν ένα φιλελεύθερο μοντέλο συνεισφοράς περιλαμβάνουν το Node.js και το Rust . Ποιο από τα δύο πρέπει να χρησιμοποιήσετε; Εξαρτάται από εσάς! Κάθε μοντέλο έχει πλεονεκτήματα και συμβιβασμούς. Και παρόλο που μπορεί να φαίνονται αρκετά διαφορετικά στην αρχή, και τα τρία μοντέλα έχουν περισσότερα κοινά απ’ όσα φαίνονται. Αν ενδιαφέρεστε να υιοθετήσετε ένα από αυτά τα μοντέλα, δείτε αυτά τα πρότυπα: Πρότυπο μοντέλου BDFL Πρότυπο μοντέλου αξιοκρατίας Η φιλελεύθερη πολιτική συνεισφοράς του Node.js Χρειάζομαι έγγραφα διακυβέρνησης όταν ξεκινάω το πρότζεκτ μου; Δεν υπάρχει σωστή στιγμή για να καταγράψετε τη διακυβέρνηση του πρότζεκτ σας, αλλά είναι πολύ πιο εύκολο να την ορίσετε μόλις δείτε τη δυναμική της κοινότητάς σας να εξελίσσεται. Το καλύτερο (και δυσκολότερο) μέρος της διακυβέρνησης του ανοιχτού κώδικα είναι ότι διαμορφώνεται από την κοινότητα! Ωστόσο, κάποια πρώιμη τεκμηρίωση θα συμβάλει αναπόφευκτα στη διακυβέρνηση του πρότζεκτ σας, οπότε αρχίστε να γράφετε ό,τι μπορείτε. Για παράδειγμα, μπορείτε να ορίσετε σαφείς προσδοκίες για τη συμπεριφορά ή τον τρόπο λειτουργίας της διαδικασίας συνεισφοράς σας, ακόμη και κατά την έναρξη του πρότζεκτ σας. Αν ανήκετε σε μια εταιρεία που εγκαινιάζει ένα πρότζεκτ ανοιχτού κώδικα, αξίζει να κάνετε μια εσωτερική συζήτηση πριν από την έναρξη σχετικά με το πώς η εταιρεία σας αναμένει να συντηρεί και να λαμβάνει αποφάσεις σχετικά με το πρότζεκτ που προχωράει. Μπορεί επίσης να θέλετε να εξηγήσετε δημόσια οτιδήποτε ιδιαίτερο σχετικά με τον τρόπο με τον οποίο η εταιρεία σας θα συμμετέχει (ή δεν θα συμμετέχει!) στο πρότζεκτ. Αναθέτουμε τη διαχείριση πρότζεκτ στο GitHub σε μικρές ομάδες που εργάζονται πραγματικά σε αυτά στο Facebook. Για παράδειγμα, το React διευθύνεται από έναν μηχανικό του React. - @caabernathy, “An inside look at open source at Facebook” Τι θα συμβεί αν οι εταιρικοί υπάλληλοι αρχίσουν να υποβάλλουν συνεισφορές; Τα επιτυχημένα πρότζεκτ ανοικτού κώδικα χρησιμοποιούνται από πολλούς ανθρώπους και εταιρείες, και ορισμένες εταιρείες μπορεί τελικά να έχουν ροές εσόδων που συνδέονται τελικά με το πρότζεκτ. Για παράδειγμα, μια εταιρεία μπορεί να χρησιμοποιήσει τον κώδικα του πρότζεκτ ως ένα συστατικό στοιχείο σε μια εμπορική προσφορά υπηρεσιών. Καθώς το πρότζεκτ χρησιμοποιείται ευρύτερα, οι άνθρωποι που έχουν εμπειρία σε αυτό γίνονται πιο περιζήτητοι - ίσως είστε ένας από αυτούς! - και μερικές φορές θα πληρώνονται για τη δουλειά που κάνουν στο πρότζεκτ. Είναι σημαντικό να αντιμετωπίζετε την εμπορική δραστηριότητα ως φυσιολογική και ως μια ακόμη πηγή ενέργειας ανάπτυξης. Φυσικά, οι αμειβόμενοι προγραμματιστές δεν πρέπει να τυγχάνουν ιδιαίτερης μεταχείρισης σε σχέση με τους μη αμειβόμενους- κάθε συνεισφορά πρέπει να αξιολογείται με βάση την τεχνική της αξία. Ωστόσο, οι άνθρωποι θα πρέπει να αισθάνονται άνετα να συμμετέχουν σε εμπορική δραστηριότητα και να αισθάνονται άνετα να αναφέρουν τις περιπτώσεις χρήσης τους όταν επιχειρηματολογούν υπέρ μιας συγκεκριμένης βελτίωσης ή λειτουργίας. Το “εμπορικό” είναι απολύτως συμβατό με το “ανοιχτό κώδικα”. “Εμπορικό” σημαίνει απλώς ότι κάπου εμπλέκονται χρήματα - ότι το λογισμικό χρησιμοποιείται στο εμπόριο, κάτι που είναι όλο και πιο πιθανό καθώς ένα πρότζεκτ κερδίζει την αποδοχή του. (Όταν το λογισμικό ανοικτού κώδικα χρησιμοποιείται ως μέρος ενός προϊόντος μη ανοικτού κώδικα, το συνολικό προϊόν εξακολουθεί να είναι “ιδιόκτητο” λογισμικό, αν και, όπως και ο ανοικτός κώδικας, μπορεί να χρησιμοποιηθεί για εμπορικούς ή μη εμπορικούς σκοπούς). Όπως όλοι οι άλλοι, οι προγραμματιστές με εμπορικά κίνητρα αποκτούν επιρροή στο πρότζεκτ μέσω της ποιότητας και της ποσότητας των συνεισφορών τους. Προφανώς, ένας προγραμματιστής που πληρώνεται για το χρόνο του μπορεί να είναι σε θέση να κάνει περισσότερα από κάποιον που δεν πληρώνεται, αλλά αυτό δεν πειράζει: η πληρωμή είναι απλώς ένας από τους πολλούς πιθανούς παράγοντες που θα μπορούσαν να επηρεάσουν το πόσο κάνει κάποιος. Κρατήστε τις συζητήσεις σας για το πρότζεκτ επικεντρωμένες στις συνεισφορές και όχι στους εξωτερικούς παράγοντες που επιτρέπουν στους ανθρώπους να κάνουν αυτές τις συνεισφορές. Χρειάζομαι μια νομική οντότητα για να υποστηρίξω το πρότζεκτ μου; Δεν χρειάζεστε μια νομική οντότητα για την υποστήριξη του πρότζεκτ σας ανοικτού κώδικα, εκτός αν διαχειρίζεστε χρήματα. Για παράδειγμα, αν θέλετε να δημιουργήσετε μια εμπορική επιχείρηση, θα πρέπει να δημιουργήσετε μια C Corp ή LLC (αν έχετε την έδρα σας στις ΗΠΑ). Αν απλά κάνετε εργασίες συμβολαίου που σχετίζονται με το πρότζεκτ σας ανοικτού κώδικα, μπορείτε να δεχτείτε χρήματα ως ατομική επιχείρηση ή να δημιουργήσετε μια LLC (αν έχετε την έδρα σας στις ΗΠΑ). Αν θέλετε να δέχεστε δωρεές για το ανοικτού κώδικα πρότζεκτ σας, μπορείτε να δημιουργήσετε ένα κουμπί δωρεάς (χρησιμοποιώντας το PayPal ή το Stripe, για παράδειγμα), αλλά τα χρήματα δεν θα εκπίπτουν από τη φορολογία, εκτός αν είστε αναγνωρισμένος μη κερδοσκοπικός οργανισμός (501c3, αν είστε στις ΗΠΑ). Πολλά πρότζεκτ δεν επιθυμούν να μπουν στον κόπο να δημιουργήσουν έναν μη κερδοσκοπικό οργανισμό, οπότε βρίσκουν έναν μη κερδοσκοπικό φορολογικό χορηγό. Ένας φορολογικός χορηγός δέχεται δωρεές εκ μέρους σας, συνήθως με αντάλλαγμα ένα ποσοστό της δωρεάς. Software Freedom Conservancy , Apache Foundation , Eclipse Foundation , Linux Foundation και Open Collective είναι παραδείγματα οργανισμών που λειτουργούν ως φορολογικοί χορηγοί για πρότζεκτ ανοικτού κώδικα. Στόχος μας είναι να παρέχουμε μια υποδομή που οι κοινότητες μπορούν να χρησιμοποιήσουν για να είναι αυτοσυντηρούμενες, δημιουργώντας έτσι ένα περιβάλλον όπου όλοι - συνεισφέροντες, υποστηρικτές, χορηγοί - θα έχουν συγκεκριμένα οφέλη. - @piamancini, “Moving beyond the charity framework” Εάν το πρότζεκτ σας συνδέεται στενά με μια συγκεκριμένη γλώσσα ή οικοσύστημα, μπορεί επίσης να υπάρχει ένα σχετικό ίδρυμα λογισμικού με το οποίο μπορείτε να συνεργαστείτε. Για παράδειγμα, το Python Software Foundation βοηθά στην υποστήριξη του PyPI , του διαχειριστή πακέτων Python, και το Node.js Foundation βοηθά στην υποστήριξη του Express.js , ενός πλαισίου βασισμένου στο Node. Επιστροφή σε όλους τους οδηγούς Σχετικοί Οδηγοί Βέλτιστες Πρακτικές για Συντηρητές Διευκολύνοντας την ζωή σας ως συντηρητής ανοιχτού κώδικα, από την τεκμηρίωση των διαδικασιών μέχρι και την αξιοποίηση της κοινότητάς σας. Στατιστικά Ανοικτού Κώδικα Λάβετε τεκμηριωμένες αποφάσεις για να βοηθήσετε το πρότζεκτ ανοιχτού κώδικά σας να ευημερήσει, μετρώντας και παρακολουθώντας την επιτυχία του. Scroll to Top Συνεισφορά Θέλετε να κάνετε μια πρόταση; Αυτό το περιεχόμενο είναι ανοιχτού κώδικα. Βοηθήστε μας να το βελτιώσουμε. Συνεισφορά Μείνετε σε επαφή Ενημερωθείτε πρώτοι για τις πιο πρόσφατες συμβουλές ανοιχτού κώδικα του GitHub. Ηλεκτρονική διεύθυνση fine print με από το και φίλους | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/cloudflare-ddos-protection/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click#main-content | Cloudflare DDoS Protection | LinkedIn Skip to main content LinkedIn Cloudflare in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloudflare DDoS Protection DDoS Protection Software by Cloudflare See who's skilled in this Add as skill Get started Report this product About Comprehensive DDoS Protection Built for anything connected to the Internet Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised. Cloudflare’s 51 Tbps network blocks an average of 72 billion threats per day, including some of the largest DDoS attacks in history. Media Products media viewer No more previous content DDoS Protection, WAF, CDN and more from Cloudflare Built for anything connected to the Internet Cloudflare offers three DDoS protection solutions designed to protect everything on your cloud and on-premise networks. How Cloudflare protects network infrastructure from DDoS attacks Cloudflare Magic Transit uses our entire anycast network, which spans hundreds of global cities, to detect and mitigate DDoS attacks at the network edge. What Is A DDoS Attack? DDoS attacks represent one of the greatest threats to websites and services. No more next content Featured customers of Cloudflare DDoS Protection Chrono24 Retail Luxury Goods and Jewelry 15,639 followers Upwork Software Development 3,294,409 followers Carousell Group Software Development 129,533 followers Hemnet Real Estate 12,582 followers Trendyol Group Technology, Information and Internet 536,123 followers BookMyShow Entertainment Providers 125,692 followers 早稲田大学 WASEDA University Higher Education 112,057 followers Axios Internet News 75,402 followers Wongnai.com Information Services 5,546 followers Show more Show less Similar products Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kona DDoS Defender Kona DDoS Defender DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Sign in to see more Show more Show less Cloudflare products Argo Smart Routing Argo Smart Routing Network Management Software Cloudflare DNS Cloudflare DNS Managed DNS Services Software Cloudflare Load Balancing Cloudflare Load Balancing Load Balancing Software Cloudflare Registrar Cloudflare Registrar Managed DNS Services Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Cloudflare SSL / TLS Cloudflare SSL / TLS SSL Certificates Software Cloudflare WAF Cloudflare WAF Web Application Firewalls (WAF) Cloudflare Web Analytics Cloudflare Web Analytics Digital Analytics Software Cloudflare Workers Cloudflare Workers Server Virtualization Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Ftencentglobal-cloud-native-database-tdsqlc%2F&fromSignIn=true&trk=products_details_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/categories/content-delivery-network-software?trk=organization_guest_products_modal_category_link | Best Content Delivery Network (CDN) Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Chief Technology Officer (7) Software Engineer (5) Chief Executive Officer (4) Information Technology Manager (3) Director of Operations (3) See all products Find top products in Content Delivery Network (CDN) Software category Software used to scale Internet bandwidth to improve delivery speed and reliability. - Access a geographically distributed network of proxy servers - Distribute content to users by location - Perform web caching, request routing, and load balancing - Monitor and optimize delivery speed of online content and media 73 results Google Cloud CDN Content Delivery Network (CDN) Software by Google Cloud Cloud CDN provides fast, reliable web and video content delivery with global scale and reach. View product Cloudflare CDN Content Delivery Network (CDN) Software by Cloudflare A fast, agile, and secure global network Cloudflare offers ultra-fast static and dynamic content delivery over our global edge network. Exercise precise control over how your content is cached, reduce bandwidth costs and take advantage of built-in unmetered DDoS protection. View product Aura Managed CDN Content Delivery Network (CDN) Software by Akamai Technologies Akamai Managed CDN Solutions provide network operators dedicated CDN capacity for streaming video & content applications or third party CDN services. View product Fastly CDN Content Delivery Network (CDN) Software by Fastly Fastly’s CDN provides the real-time observability, baked-in security, and programmatic control needed to deliver the fast, personalized experiences today’s global audiences demand. View product Imperva Secure CDN Content Delivery Network (CDN) Software by Imperva Imperva Secure CDN dynamically profiles website resources and identifies all cacheable content (dynamic and static) including content that other CDNs cannot. All Imperva PoPs are full-stack and globally dispersed to ensure the lowest latency possible. The global Imperva network lets organizations not only prevent unforeseen disruptions to their business, but also mitigate risk. Critical applications are secured against all OWASP Top 10 threats and the malicious effects of bad bots are mitigated through Imperva Cloud WAF. DDoS traffic is diverted to the global CDN with guaranteed 3-second mitigation, and load balancing ensures an optimal user experience. Load Balancer supports a variety of load balancing algorithms—with or without a persistence override option—to optimize traffic distribution across servers, maximize application performance and reduce server load. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Fastly Streaming Media Delivery Content Delivery Network (CDN) Software by Fastly Fastly helps the world’s leading media and entertainment brands — like A+E, Spotify, and Fox — reliably deliver live and on-demand streaming media experiences, quickly, securely, and at scale. View product CDNetworks CDN Content Delivery Network (CDN) Software by CDNetworks CDNetworks CDN guarantees fast, reliable, and secure delivery of web content, video, applications, and other digital resources, ensuring low-latency and high-speed content delivery. Powered by over 2,800 global PoPs in 87 countries and regions, CDNetworks CDN runs on a 200 Tbps+ network backbone, offering unmatched scalability and performance for businesses across the globe. View product Bunny CDN Content Delivery Network (CDN) Software by bunny.net Performance like never before. Supercharge your content delivery with a global distribution network with unparalleled speed, security, and stability. Deliver exceptional performance. For every request. Every time. Bunny CDN is powered by 108+ Global PoPs and runs on an 80 Tbps+ Network Backbone. Deliver your content worldwide with a sub 29 ms average latency. View product Squiz Delivery Content Delivery Network (CDN) Software by Squiz Squiz Delivery maximizes the impact of your experiences by delivering them the way users expect – securely, consistently, and lightning-fast – across web, mobile, IoT devices, and more. Features: - Accelerate site performance: Supercharge performance with Cloudflare’s vast Content Delivery Network (CDN). Increase load speed with content cached locally. Optimize performance, even during peak traffic, with a reverse proxy. - Safeguard your sites and data: Automatically identify and block malicious traffic with our Web Application Firewall (WAF). Get full threat protection against cyberattacks such as DDoS. The built-in Cloudflare shield ensures that your sites don’t get taken down by an attack. - Uninterrupted, secure access: Ensure legitimate users always have consistent, secure access to your sites. Squiz DXP takes a multi-layered approach, with the WAF, CDN, reverse proxy, and more, working together to safeguard your experiences and ensure they are always available. View product Leaseweb Multi-CDN (Content Delivery Network) Content Delivery Network (CDN) Software by Leaseweb We know that uptime, reliability, and speed are important for your business to deliver high-quality content and the best user experience. The Leaseweb Multi-CDN combines multiple Content Delivery Network (CDN) providers to increase your global reach. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/tencentglobal-tencent-realtime-communication-trtc/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click | Tencent Real-Time Communication (TRTC) | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Tencent Real-Time Communication (TRTC) Live Streaming Software by Tencent See who's skilled in this Add as skill Learn more Report this product About Enable audio/video calls and interactive live streaming in your application in 30 minutes Similar products Cloudflare Stream Cloudflare Stream Live Streaming Software Tango Tango Live Streaming Software BOCC BOCC Live Streaming Software Media Services Live Media Services Live Live Streaming Software Liveu Liveu Live Streaming Software Kaltura AI Video Experience Cloud Kaltura AI Video Experience Cloud Live Streaming Software Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/tencentglobal-tencent-effect-sdk/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click#main-content | Tencent Effect SDK | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Tencent Effect SDK Software Development Kits (SDK) by Tencent See who's skilled in this Add as skill Learn more Report this product About Tencent Effect SDK leverages YouTu's accurate AI capabilities and Pitu's rich real-time effects to offer a wealth of services for many video processing use cases. Similar products Meta Business SDK Meta Business SDK Software Development Kits (SDK) MantHANA MantHANA Software Development Kits (SDK) Elevate Elevate Software Development Kits (SDK) Lyzr AI Lyzr AI Software Development Kits (SDK) RevenueCat RevenueCat Software Development Kits (SDK) Ready Player Me Ready Player Me Software Development Kits (SDK) Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://opensource.guide/hi/starting-a-project/ | एक ओपन सोर्स प्रोजेक्ट शुरू करना | Open Source Guides बारे में योगदान करें العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides एक ओपन सोर्स प्रोजेक्ट शुरू करना ओपन सोर्स की दुनिया के बारे में और जानें और अपना खुद का प्रोजेक्ट लॉन्च करने के लिए तैयार हो जाएं। सामग्री की सूची खुले स्रोत का “क्या” और “क्यों”। क्या मुझे अपना स्वयं का ओपन सोर्स प्रोजेक्ट लॉन्च करना चाहिए? अपना स्वयं का ओपन सोर्स प्रोजेक्ट लॉन्च करना अपने प्रोजेक्ट का नामकरण और ब्रांडिंग करना आपकी प्री-लॉन्च चेकलिस्ट खुले स्रोत का “क्या” और “क्यों”। तो क्या आप ओपन सोर्स के साथ शुरुआत करने के बारे में सोच रहे हैं? बधाई हो! दुनिया आपके योगदान की सराहना करती है. आइए बात करें कि ओपन सोर्स क्या है और लोग ऐसा क्यों करते हैं। “ओपन सोर्स” का क्या मतलब है? जब कोई प्रोजेक्ट ओपन सोर्स होता है, तो इसका मतलब है कि कोई भी किसी भी उद्देश्य के लिए आपके प्रोजेक्ट का उपयोग, अध्ययन, संशोधन और वितरण करने के लिए स्वतंत्र है। ये अनुमतियाँ एक ओपन सोर्स लाइसेंस के माध्यम से लागू की जाती हैं। खुला स्रोत शक्तिशाली है क्योंकि यह अपनाने और सहयोग की बाधाओं को कम करता है, जिससे लोगों को परियोजनाओं को तेजी से फैलाने और सुधारने की अनुमति मिलती है। इसके अलावा, क्योंकि यह उपयोगकर्ताओं को बंद स्रोत के सापेक्ष, अपने स्वयं के कंप्यूटिंग को नियंत्रित करने की क्षमता देता है। उदाहरण के लिए, ओपन सोर्स सॉफ़्टवेयर का उपयोग करने वाले व्यवसाय के पास किसी बंद स्रोत विक्रेता के उत्पाद निर्णयों पर विशेष रूप से निर्भर रहने के बजाय सॉफ़्टवेयर में कस्टम सुधार करने के लिए किसी को नियुक्त करने का विकल्प होता है। मुफ़्त सॉफ़्टवेयर परियोजनाओं के उसी सेट को संदर्भित करता है जो ओपन सोर्स है। कभी-कभी आप इन शर्तों को “फ्री और ओपन सोर्स सॉफ्टवेयर” (FOSS) या “फ्री, लिब्रे और ओपन सोर्स सॉफ्टवेयर” के रूप में भी देखेंगे। (दाँत साफ करने का धागा)। मुक्त और मुक्ति का तात्पर्य स्वतंत्रता से है, कीमत से नहीं । लोग अपना काम ओपन सोर्स क्यों करते हैं? ओपन सोर्स का उपयोग करने और सहयोग करने से मुझे जो सबसे फायदेमंद अनुभव मिलता है, वह उन रिश्तों से आता है जो मैं उन अन्य डेवलपर्स के साथ बनाता हूं जो मेरे जैसी ही कई समस्याओं का सामना कर रहे हैं। — @kentcdodds, “ओपन सोर्स में आना मेरे लिए कितना अद्भुत रहा है” इसके कई कारण हैं कोई व्यक्ति या संगठन किसी प्रोजेक्ट को ओपन सोर्स क्यों करना चाहेगा। कुछ उदाहरणों में शामिल हैं: सहयोग: ओपन सोर्स प्रोजेक्ट दुनिया में किसी से भी बदलाव स्वीकार कर सकते हैं। व्यायाम , उदाहरण के लिए, 350 से अधिक योगदानकर्ताओं वाला एक प्रोग्रामिंग अभ्यास मंच है। अडॉप्टेशन और रीमिक्सिंग: ओपन सोर्स प्रोजेक्ट्स का उपयोग कोई भी लगभग किसी भी उद्देश्य के लिए कर सकता है। लोग इसका उपयोग अन्य चीजें बनाने में भी कर सकते हैं। WordPress , उदाहरण के लिए, किसी मौजूदा प्रोजेक्ट के फोर्क के रूप में शुरू किया गया, b2 । पारदर्शिता: त्रुटियों या विसंगतियों के लिए कोई भी ओपन सोर्स प्रोजेक्ट का निरीक्षण कर सकता है। पारदर्शिता Bulgaria या United States जैसी सरकारों, बैंकिंग या स्वास्थ्य देखभाल जैसे विनियमित उद्योगों और Let’s Encrypt , जैसे सुरक्षा सॉफ़्टवेयर के लिए मायने रखती है। ओपन सोर्स सिर्फ सॉफ्टवेयर के लिए ही नहीं है। आप डेटा सेट से लेकर किताबों तक सब कुछ ओपन सोर्स कर सकते हैं। आप और क्या स्रोत खोल सकते हैं, इस बारे में विचारों के लिए गिटहब एक्सप्लोर देखें। क्या ओपन सोर्स का मतलब “निःशुल्क” है? ओपन सोर्स का सबसे बड़ा आकर्षण यह है कि इसमें पैसा खर्च नहीं होता है। हालाँकि, “निःशुल्क”, खुले स्रोत के समग्र मूल्य का एक उपोत्पाद है। क्योंकि एक ओपन सोर्स लाइसेंस के लिए आवश्यक है कि कोई भी आपके प्रोजेक्ट को लगभग किसी भी उद्देश्य के लिए उपयोग, संशोधित और साझा कर सकता है, प्रोजेक्ट स्वयं निःशुल्क होते हैं। यदि प्रोजेक्ट के उपयोग में पैसे खर्च होते हैं, तो कोई भी कानूनी तौर पर इसकी प्रतिलिपि बना सकता है और इसके बजाय मुफ़्त संस्करण का उपयोग कर सकता है। परिणामस्वरूप, अधिकांश ओपन सोर्स प्रोजेक्ट मुफ़्त हैं, लेकिन “निःशुल्क” ओपन सोर्स परिभाषा का हिस्सा नहीं है। ओपन सोर्स की आधिकारिक परिभाषा का अनुपालन करते हुए, दोहरे लाइसेंसिंग या सीमित सुविधाओं के माध्यम से अप्रत्यक्ष रूप से ओपन सोर्स परियोजनाओं के लिए शुल्क लेने के कई तरीके हैं। क्या मुझे अपना स्वयं का ओपन सोर्स प्रोजेक्ट लॉन्च करना चाहिए? संक्षिप्त उत्तर हां है, क्योंकि परिणाम चाहे जो भी हो, अपना खुद का प्रोजेक्ट लॉन्च करना यह सीखने का एक शानदार तरीका है कि ओपन सोर्स कैसे काम करता है। यदि आपने पहले कभी कोई प्रोजेक्ट ओपन सोर्स नहीं किया है, तो आप इस बात से घबरा सकते हैं कि लोग क्या कहेंगे, या कोई नोटिस करेगा या नहीं। यदि यह आपके जैसा लगता है, तो आप अकेले नहीं हैं! ओपन सोर्स कार्य किसी भी अन्य रचनात्मक गतिविधि की तरह है, चाहे वह लेखन हो या पेंटिंग। अपने काम को दुनिया के साथ साझा करना डरावना लग सकता है, लेकिन बेहतर होने का एकमात्र तरीका अभ्यास करना है - भले ही आपके पास दर्शक न हों। यदि आप अभी तक आश्वस्त नहीं हैं, तो एक क्षण रुककर सोचें कि आपके लक्ष्य क्या हो सकते हैं। अपने लक्ष्य निर्धारित करना लक्ष्य आपको यह पता लगाने में मदद कर सकते हैं कि किस पर काम करना है, किस चीज़ को ना कहना है और आपको कहाँ दूसरों से मदद की ज़रूरत है। अपने आप से यह पूछकर शुरुआत करें, मैं इस प्रोजेक्ट का ओपन सोर्सिंग क्यों कर रहा हूँ? इस प्रश्न का कोई भी सही उत्तर नहीं है। आपके पास एक ही प्रोजेक्ट के लिए कई लक्ष्य हो सकते हैं, या अलग-अलग लक्ष्यों वाली अलग-अलग परियोजनाएँ हो सकती हैं। यदि आपका एकमात्र लक्ष्य अपना काम दिखाना है, तो हो सकता है कि आप योगदान भी न चाहें, और अपने README में ऐसा कहें भी नहीं। दूसरी ओर, यदि आप योगदानकर्ता चाहते हैं, तो आप स्पष्ट दस्तावेज़ीकरण और नए लोगों का स्वागत महसूस कराने में समय लगाएंगे। किसी बिंदु पर मैंने एक कस्टम UIAlertView बनाया जिसका मैं उपयोग कर रहा था…और मैंने इसे खुला स्रोत बनाने का निर्णय लिया। इसलिए मैंने इसे अधिक गतिशील बनाने के लिए संशोधित किया और GitHub पर अपलोड किया। मैंने अपना पहला दस्तावेज़ अन्य डेवलपर्स को यह समझाते हुए लिखा कि इसे अपनी परियोजनाओं पर कैसे उपयोग किया जाए। संभवतः किसी ने कभी इसका उपयोग नहीं किया क्योंकि यह एक साधारण परियोजना थी लेकिन मैं अपने योगदान के बारे में अच्छा महसूस कर रहा था। — @mavris, “स्व-सिखाया गया सॉफ़्टवेयर डेवलपर्स: ओपन सोर्स हमारे लिए क्यों महत्वपूर्ण है” जैसे-जैसे आपका प्रोजेक्ट बढ़ता है, आपके समुदाय को आपसे कोड के अलावा और भी बहुत कुछ की आवश्यकता हो सकती है। मुद्दों पर प्रतिक्रिया देना, कोड की समीक्षा करना और अपने प्रोजेक्ट का प्रचार-प्रसार करना एक ओपन सोर्स प्रोजेक्ट में सभी महत्वपूर्ण कार्य हैं। जबकि आप गैर-कोडिंग कार्यों पर कितना समय बिताएंगे, यह आपके प्रोजेक्ट के आकार और दायरे पर निर्भर करेगा, आपको उन्हें स्वयं संबोधित करने या आपकी सहायता के लिए किसी को ढूंढने के लिए एक अनुरक्षक के रूप में तैयार रहना चाहिए। यदि आप किसी प्रोजेक्ट की ओपन सोर्सिंग करने वाली कंपनी का हिस्सा हैं, सुनिश्चित करें कि आपके प्रोजेक्ट के पास आंतरिक संसाधन हैं जो उसे आगे बढ़ाने के लिए आवश्यक हैं। आप यह पहचानना चाहेंगे कि लॉन्च के बाद प्रोजेक्ट को बनाए रखने के लिए कौन ज़िम्मेदार है, और आप उन कार्यों को अपने समुदाय के साथ कैसे साझा करेंगे। यदि आपको परियोजना के प्रचार, संचालन और रखरखाव के लिए समर्पित बजट या स्टाफिंग की आवश्यकता है, तो बातचीत जल्दी शुरू करें। जैसे ही आप प्रोजेक्ट को ओपन सोर्स करना शुरू करते हैं, यह सुनिश्चित करना महत्वपूर्ण है कि आपकी प्रबंधन प्रक्रियाएं आपके प्रोजेक्ट के आसपास के समुदाय के योगदान और क्षमताओं को ध्यान में रखती हैं। परियोजना के प्रमुख पहलुओं में उन योगदानकर्ताओं को शामिल करने से न डरें जो आपके व्यवसाय में कार्यरत नहीं हैं - खासकर यदि वे लगातार योगदानकर्ता हैं। — @captainsafia, “तो आप एक प्रोजेक्ट को ओपन सोर्स करना चाहते हैं, है ना?” अन्य परियोजनाओं में योगदान देना यदि आपका लक्ष्य यह सीखना है कि दूसरों के साथ कैसे सहयोग करें या यह समझें कि ओपन सोर्स कैसे काम करता है, तो किसी मौजूदा प्रोजेक्ट में योगदान देने पर विचार करें। उस प्रोजेक्ट से शुरुआत करें जिसे आप पहले से ही उपयोग करते हैं और पसंद करते हैं। किसी प्रोजेक्ट में योगदान देना टाइप की त्रुटियों को ठीक करने या दस्तावेज़ीकरण को अपडेट करने जितना आसान हो सकता है। यदि आप निश्चित नहीं हैं कि योगदानकर्ता के रूप में शुरुआत कैसे करें, तो हमारी जाँच करें ओपन सोर्स गाइड में योगदान कैसे करें . अपना स्वयं का ओपन सोर्स प्रोजेक्ट लॉन्च करना अपने काम का स्रोत खोलने का कोई सही समय नहीं है। आप किसी विचार का स्रोत खोल सकते हैं, कोई कार्य प्रगति पर है, या वर्षों तक बंद स्रोत रहने के बाद। आम तौर पर कहें तो, आपको अपने प्रोजेक्ट को तब ओपन सोर्स करना चाहिए जब आप दूसरों को अपने काम को देखने और उस पर फीडबैक देने में सहज महसूस करें। इससे कोई फर्क नहीं पड़ता कि आप अपने प्रोजेक्ट को किस चरण में खोलने का निर्णय लेते हैं, प्रत्येक प्रोजेक्ट में निम्नलिखित दस्तावेज़ शामिल होने चाहिए: Open source license README Contributing guidelines Code of conduct एक अनुरक्षक के रूप में, ये घटक आपको अपेक्षाओं को संप्रेषित करने, योगदान प्रबंधित करने और सभी के कानूनी अधिकारों (आपके अपने अधिकारों सहित) की रक्षा करने में मदद करेंगे। वे आपके सकारात्मक अनुभव प्राप्त करने की संभावनाओं को उल्लेखनीय रूप से बढ़ा देते हैं। यदि आपका प्रोजेक्ट GitHub पर है, तो इन फ़ाइलों को अनुशंसित फ़ाइल नामों के साथ अपनी रूट निर्देशिका में डालने से GitHub को उन्हें पहचानने और स्वचालित रूप से आपके पाठकों के सामने लाने में मदद मिलेगी। लाइसेंस चुनना एक ओपन सोर्स लाइसेंस यह गारंटी देता है कि अन्य लोग बिना किसी प्रभाव के आपके प्रोजेक्ट का उपयोग, प्रतिलिपि, संशोधन और योगदान कर सकते हैं। यह आपको जटिल कानूनी स्थितियों से भी बचाता है। ओपन सोर्स प्रोजेक्ट लॉन्च करते समय आपको एक लाइसेंस शामिल करना होगा। क़ानूनी काम कोई मज़ेदार नहीं है. अच्छी खबर यह है कि आप मौजूदा लाइसेंस को कॉपी करके अपने रिपॉजिटरी में पेस्ट कर सकते हैं। आपकी मेहनत की रक्षा करने में केवल एक मिनट लगेगा। MIT , Apache 2.0 , और GPLv3 सबसे लोकप्रिय ओपन सोर्स लाइसेंस हैं, लेकिन अन्य विकल्प भी हैं . जब आप GitHub पर एक नया प्रोजेक्ट बनाते हैं, तो आपको लाइसेंस चुनने का विकल्प दिया जाता है। ओपन सोर्स लाइसेंस शामिल करने से आपका GitHub प्रोजेक्ट ओपन सोर्स बन जाएगा। यदि आपके पास ओपन सोर्स प्रोजेक्ट के प्रबंधन के कानूनी पहलुओं के बारे में अन्य प्रश्न या चिंताएं हैं, हमने आपका ध्यान रखा है . एक रीडमी लिखना READMEs आपके प्रोजेक्ट का उपयोग कैसे करें यह समझाने के अलावा और भी बहुत कुछ करते हैं। वे यह भी बताते हैं कि आपका प्रोजेक्ट क्यों मायने रखता है, और आपके उपयोगकर्ता इसके साथ क्या कर सकते हैं। अपने README में निम्नलिखित प्रश्नों के उत्तर देने का प्रयास करें: यह प्रोजेक्ट क्या करता है? यह प्रोजेक्ट उपयोगी क्यों है? मैं कैसे शुरू करूँ? यदि मुझे आवश्यकता हो तो मुझे और सहायता कहां से मिल सकती है? आप अपने README का उपयोग अन्य प्रश्नों के उत्तर देने के लिए कर सकते हैं, जैसे कि आप योगदान कैसे संभालते हैं, परियोजना के लक्ष्य क्या हैं, और लाइसेंस और एट्रिब्यूशन के बारे में जानकारी। यदि आप योगदान स्वीकार नहीं करना चाहते हैं, या आपका प्रोजेक्ट अभी तक उत्पादन के लिए तैयार नहीं है, तो इस जानकारी को लिख लें। बेहतर दस्तावेज़ीकरण का अर्थ है अधिक उपयोगकर्ता, कम समर्थन अनुरोध और अधिक योगदानकर्ता। (…) याद रखें कि आपके पाठक आप नहीं हैं। ऐसे लोग भी हो सकते हैं जो किसी प्रोजेक्ट में आ सकते हैं जिनके पास पूरी तरह से अलग अनुभव हों। — @tracymakes, “लिखें ताकि आपके शब्द पढ़े जा सकें (वीडियो)” कभी-कभी, लोग README लिखने से बचते हैं क्योंकि उन्हें लगता है कि परियोजना अधूरी है, या वे योगदान नहीं चाहते हैं। इसे लिखने के ये सभी बहुत अच्छे कारण हैं। अधिक प्रेरणा के लिए, @dguo’s का “एक README बनाएं” मार्गदर्शिका उपयोग करने का प्रयास करें या @PurpleBooth’s README टेम्पलेट संपूर्ण README लिखने के लिए। जब आप रूट डायरेक्टरी में एक README फ़ाइल शामिल करते हैं, तो GitHub स्वचालित रूप से इसे रिपॉजिटरी होमपेज पर प्रदर्शित करेगा। अपने योगदान संबंधी दिशानिर्देश लिखना एक योगदान फ़ाइल आपके दर्शकों को बताती है कि आपके प्रोजेक्ट में कैसे भाग लेना है। उदाहरण के लिए, आप निम्न पर जानकारी शामिल कर सकते हैं: बग रिपोर्ट कैसे दर्ज करें ( इश्यू और पुल रिक्वेस्ट टेम्प्लेट्स का उपयोग ) करने का प्रयास करें। नई सुविधा का सुझाव कैसे दें अपना वातावरण कैसे स्थापित करें और परीक्षण कैसे चलाएं तकनीकी विवरण के अलावा, योगदान फ़ाइल योगदान के लिए आपकी अपेक्षाओं को संप्रेषित करने का एक अवसर है, जैसे: आप जिस प्रकार के योगदान की तलाश कर रहे हैं परियोजना के लिए आपका रोडमैप या विज़न योगदानकर्ताओं को आपसे कैसे संपर्क करना चाहिए (या नहीं करना चाहिए)। गर्मजोशीपूर्ण, मैत्रीपूर्ण लहजे का उपयोग करना और योगदान के लिए विशिष्ट सुझाव देना (जैसे दस्तावेज़ लिखना, या वेबसाइट बनाना) नवागंतुकों को भाग लेने के लिए स्वागत और उत्साहित महसूस कराने में काफी मदद कर सकता है। उदाहरण के लिए, सक्रिय व्यवस्थापक प्रारंभ होता है इसकी योगदान मार्गदर्शिका के साथ: सबसे पहले, सक्रिय व्यवस्थापक में योगदान देने पर विचार करने के लिए धन्यवाद। यह आप जैसे लोग ही हैं जो एक्टिव एडमिन को इतना बढ़िया टूल बनाते हैं। आपके प्रोजेक्ट के शुरुआती चरणों में, आपकी CONTRIBUTING फ़ाइल सरल हो सकती है। योगदान देने के लिए आपको हमेशा यह समझाना चाहिए कि बग या फ़ाइल समस्याओं की रिपोर्ट कैसे करें, और कोई तकनीकी आवश्यकताएं (जैसे परीक्षण) कैसे करें। समय के साथ, आप अपनी योगदान फ़ाइल में अन्य अक्सर पूछे जाने वाले प्रश्न जोड़ सकते हैं। इस जानकारी को लिखने का मतलब है कि कम लोग आपसे वही प्रश्न बार-बार पूछेंगे। अपनी CONTRIBUTING फ़ाइल लिखने में अधिक सहायता के लिए, देखें @nayafia’s contributing गाइड टेम्पलेट या @mozilla’s “CONTRIBUTING.md कैसे बनाएं।” . अपनी CONTRIBUTING फ़ाइल को अपने README से लिंक करें, ताकि अधिक लोग इसे देख सकें। यदि आप CONTRIBUTING फ़ाइल को अपने प्रोजेक्ट के भंडार में रखते हैं , जब कोई योगदानकर्ता कोई समस्या उत्पन्न करता है या पुल अनुरोध खोलता है तो GitHub स्वचालित रूप से आपकी फ़ाइल से लिंक हो जाएगा। आचार संहिता की स्थापना हम सभी के पास ऐसे अनुभव हैं जहां हमें संभवतः दुरुपयोग का सामना करना पड़ा है या तो एक अनुरक्षक के रूप में यह समझाने की कोशिश कर रहा है कि कुछ को एक निश्चित तरीके से क्यों होना चाहिए, या एक उपयोगकर्ता के रूप में… एक साधारण प्रश्न पूछना। (…) आचार संहिता एक आसानी से संदर्भित और लिंक करने योग्य दस्तावेज़ बन जाती है जो इंगित करती है कि आपकी टीम रचनात्मक चर्चा को बहुत गंभीरता से लेती है। — @mlynch, “ओपन सोर्स को एक खुशहाल जगह बनाना” अंत में, एक आचार संहिता आपके प्रोजेक्ट के प्रतिभागियों के लिए व्यवहार के लिए बुनियादी नियम निर्धारित करने में मदद करती है। यह विशेष रूप से मूल्यवान है यदि आप किसी समुदाय या कंपनी के लिए एक ओपन सोर्स प्रोजेक्ट लॉन्च कर रहे हैं। आचार संहिता आपको स्वस्थ, रचनात्मक सामुदायिक व्यवहार की सुविधा प्रदान करने का अधिकार देती है, जो एक अनुरक्षक के रूप में आपके तनाव को कम करेगा। अधिक जानकारी के लिए, हमारी जाँच करें आचार संहिता मार्गदर्शिका . यह बताने के अलावा कि आप प्रतिभागियों से कैसे व्यवहार करने की अपेक्षा करते हैं, आचार संहिता यह भी बताती है कि ये अपेक्षाएं किस पर लागू होती हैं, कब लागू होती हैं और उल्लंघन होने पर क्या करना चाहिए। ओपन सोर्स लाइसेंस की तरह, आचार संहिता के लिए भी उभरते मानक हैं, इसलिए आपको अपना खुद का लिखने की ज़रूरत नहीं है। योगदानकर्ता वाचा एक ड्रॉप-इन आचार संहिता है जिसका उपयोग 40,000 से अधिक ओपन सोर्स प्रोजेक्ट्स द्वारा किया जाता है। कुबेरनेट्स, रेल्स और स्विफ्ट सहित। इससे कोई फर्क नहीं पड़ता कि आप किस पाठ का उपयोग करते हैं, आपको आवश्यकता पड़ने पर अपनी आचार संहिता लागू करने के लिए तैयार रहना चाहिए। टेक्स्ट को सीधे अपने रिपॉजिटरी में एक Code_OF_CONDUCT फ़ाइल में पेस्ट करें। फ़ाइल को अपने प्रोजेक्ट की रूट डायरेक्टरी में रखें ताकि इसे ढूंढना आसान हो, और इसे अपने README से लिंक करें। अपने प्रोजेक्ट का नामकरण और ब्रांडिंग करना ब्रांडिंग एक आकर्षक लोगो या आकर्षक प्रोजेक्ट नाम से कहीं अधिक है। यह इस बारे में है कि आप अपने प्रोजेक्ट के बारे में कैसे बात करते हैं, और आप अपना संदेश किस तक पहुंचाते हैं। सही नाम चुनना ऐसा नाम चुनें जो याद रखने में आसान हो और, आदर्श रूप से, प्रोजेक्ट क्या करता है, इसका कुछ अंदाज़ा देता हो। उदाहरण के लिए: Sentry क्रैश रिपोर्टिंग के लिए ऐप्स पर नज़र रखता है Thin एक तेज़ और सरल रूबी वेब सर्वर है यदि आप किसी मौजूदा प्रोजेक्ट पर निर्माण कर रहे हैं, तो उपसर्ग के रूप में उनके नाम का उपयोग करने से यह स्पष्ट करने में मदद मिल सकती है कि आपका प्रोजेक्ट क्या करता है (उदाहरण के लिए, node-fetch window.fetch` को Node.js पर लाता है)। स्पष्टता को सर्वोपरि मानें। चुटकुले मजेदार हैं, लेकिन याद रखें कि कुछ चुटकुले अन्य संस्कृतियों या आपसे अलग अनुभव वाले लोगों पर लागू नहीं हो सकते हैं। आपके कुछ संभावित उपयोगकर्ता कंपनी के कर्मचारी हो सकते हैं: जब उन्हें कार्यस्थल पर आपके प्रोजेक्ट के बारे में बताना हो तो आप उन्हें असहज नहीं करना चाहेंगे! नाम टकराव से बचना समान नाम वाले ओपन सोर्स प्रोजेक्ट की जांच करें , खासकर यदि आप एक ही भाषा या पारिस्थितिकी तंत्र साझा करते हैं। यदि आपका नाम किसी लोकप्रिय मौजूदा प्रोजेक्ट से मेल खाता है, तो आप अपने दर्शकों को भ्रमित कर सकते हैं। यदि आप अपने प्रोजेक्ट का प्रतिनिधित्व करने के लिए एक वेबसाइट, ट्विटर हैंडल या अन्य संपत्तियां चाहते हैं, तो सुनिश्चित करें कि आपको अपने इच्छित नाम मिल सकें। आदर्श रूप से, मन की शांति के लिए अभी उन नामों को आरक्षित करें , भले ही आप अभी उनका उपयोग करने का इरादा नहीं रखते हों। सुनिश्चित करें कि आपके प्रोजेक्ट का नाम किसी भी ट्रेडमार्क का उल्लंघन नहीं करता है। कोई कंपनी बाद में आपसे अपना प्रोजेक्ट वापस लेने के लिए कह सकती है, या आपके खिलाफ कानूनी कार्रवाई भी कर सकती है। यह जोखिम के लायक ही नहीं है। आप ट्रेडमार्क विवादों के लिए WIPO ग्लोबल ब्रांड डेटाबेस की जांच कर सकते हैं। यदि आप किसी कंपनी में हैं, तो यह उन चीजों में से एक है जिसमें आपकी कानूनी टीम आपकी मदद कर सकती है। अंत में, अपने प्रोजेक्ट के नाम के लिए त्वरित Google खोज करें। क्या लोग आपका प्रोजेक्ट आसानी से ढूंढ पाएंगे? क्या खोज परिणामों में कुछ और दिखाई देता है जो आप नहीं चाहेंगे कि वे देखें? आप कैसे लिखते हैं (और कोड) आपके ब्रांड को भी प्रभावित करता है! अपने प्रोजेक्ट के पूरे जीवनकाल में, आप बहुत सारा लेखन करेंगे: रीडमी, ट्यूटोरियल, सामुदायिक दस्तावेज़, मुद्दों पर प्रतिक्रिया देना, शायद न्यूज़लेटर और मेलिंग सूचियाँ भी। चाहे वह आधिकारिक दस्तावेज हो या कोई आकस्मिक ईमेल, आपकी लेखन शैली आपके प्रोजेक्ट के ब्रांड का हिस्सा है। इस बात पर विचार करें कि आप अपने दर्शकों के सामने कैसे आ सकते हैं और क्या आप यही लहजा बताना चाहते हैं। मैंने मेलिंग सूची के हर सूत्र में शामिल होने और अनुकरणीय व्यवहार दिखाने, लोगों के साथ अच्छा व्यवहार करने, उनके मुद्दों को गंभीरता से लेने और समग्र रूप से मददगार बनने की कोशिश की। थोड़ी देर के बाद, लोग न केवल प्रश्न पूछने के लिए, बल्कि उत्तर देने में भी मदद करने के लिए इधर-उधर रुके और मुझे पूरी खुशी हुई, उन्होंने मेरी शैली की नकल की। — @janl CouchDB , “सतत खुला स्रोत” पर। गर्मजोशीपूर्ण, समावेशी भाषा (जैसे कि “उन्हें”, यहां तक कि जब एक व्यक्ति का जिक्र हो) का उपयोग करना आपके प्रोजेक्ट को नए योगदानकर्ताओं का स्वागत करने में काफी मदद कर सकता है। सरल भाषा पर कायम रहें, क्योंकि हो सकता है कि आपके कई पाठक मूल अंग्रेजी बोलने वाले न हों। शब्दों को लिखने के तरीके के अलावा, आपकी कोडिंग शैली भी आपके प्रोजेक्ट के ब्रांड का हिस्सा बन सकती है। Angular और jQuery कठोर कोडिंग शैलियों और दिशानिर्देशों वाली परियोजनाओं के दो उदाहरण हैं। जब आप अभी शुरुआत कर रहे हों तो अपने प्रोजेक्ट के लिए स्टाइल गाइड लिखना आवश्यक नहीं है, और आप पाएंगे कि आप वैसे भी अपने प्रोजेक्ट में विभिन्न कोडिंग शैलियों को शामिल करने का आनंद लेते हैं। लेकिन आपको यह अनुमान लगाना चाहिए कि आपकी लेखन और कोडिंग शैली विभिन्न प्रकार के लोगों को कैसे आकर्षित या हतोत्साहित कर सकती है। आपके प्रोजेक्ट के शुरुआती चरण आपके लिए वह मिसाल कायम करने का अवसर हैं जो आप देखना चाहते हैं। आपकी प्री-लॉन्च चेकलिस्ट क्या आप अपना प्रोजेक्ट ओपन सोर्स करने के लिए तैयार हैं? मदद के लिए यहां एक चेकलिस्ट दी गई है। सभी बक्सों की जाँच करें? आप जाने के लिए तैयार हैं! “प्रकाशित करें” पर क्लिक करें और अपनी पीठ थपथपाएं। दस्तावेज़ीकरण प्रोजेक्ट में ओपन सोर्स लाइसेंस के साथ LICENSE फ़ाइल है। प्रोजेक्ट में बुनियादी दस्तावेज़ हैं (README, CONTRIBUTING, Code_OF_CONDUCT)। नाम याद रखना आसान है, प्रोजेक्ट क्या करता है इसका कुछ अंदाजा देता है, और किसी मौजूदा प्रोजेक्ट के साथ टकराव नहीं करता है या ट्रेडमार्क का उल्लंघन नहीं करता है। समस्या कतार अद्यतन है, जिसमें मुद्दे स्पष्ट रूप से व्यवस्थित और लेबल किए गए हैं। Code प्रोजेक्ट सुसंगत कोड सम्मेलनों और स्पष्ट फ़ंक्शन/विधि/चर नामों का उपयोग करता है। इरादों और किनारे के मामलों का दस्तावेजीकरण करते हुए कोड पर स्पष्ट रूप से टिप्पणी की गई है। पुनरीक्षण इतिहास, मुद्दों या पुल अनुरोधों में कोई संवेदनशील सामग्री नहीं है (उदाहरण के लिए, पासवर्ड या अन्य गैर-सार्वजनिक जानकारी)। लोग यदि आप एक व्यक्ति हैं: आपने कानूनी विभाग से बात की है और/या अपनी कंपनी की आईपी और ओपन सोर्स नीतियों को समझा है (यदि आप कहीं कर्मचारी हैं)। यदि आप एक कंपनी या संगठन हैं: आपने अपने कानूनी विभाग से बात की है। आपके पास परियोजना की घोषणा और प्रचार के लिए एक मार्केटिंग योजना है। कोई व्यक्ति सामुदायिक अंतःक्रियाओं के प्रबंधन के लिए प्रतिबद्ध है (issues का जवाब देना, reviewing और merging pull requests) कम से कम दो लोगों के पास परियोजना तक प्रशासनिक पहुंच है। तुमने यह किया! आपके पहले प्रोजेक्ट की ओपन सोर्सिंग के लिए बधाई। परिणाम चाहे जो भी हो, सार्वजनिक रूप से काम करना समुदाय के लिए एक उपहार है। प्रत्येक प्रतिबद्धता, टिप्पणी और अनुरोध के साथ, आप अपने लिए और दूसरों के लिए सीखने और बढ़ने के अवसर पैदा कर रहे हैं। सभी मार्गदर्शिकाओं पर वापस जाएं संबंधित मार्गदर्शिकाएं अपने प्रोजेक्ट के लिए उपयोगकर्ता ढूँढना अपने ओपन �� | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/tencentglobal-tencent-cloud-block-storage?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Tencent Cloud Block Storage | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Tencent Cloud Block Storage Block Storage Software by Tencent See who's skilled in this Add as skill Learn more Report this product About A stable, low-latency, scalable, and persistent block storage service. Similar products OVHcloud Block Storage OVHcloud Block Storage Block Storage Software DigitalOcean Block Storage DigitalOcean Block Storage Block Storage Software Vultr Vultr Block Storage Software Vultr Bare Metal Vultr Bare Metal Block Storage Software DataCore SANsymphony DataCore SANsymphony Block Storage Software Vultr Block Storage Vultr Block Storage Block Storage Software Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
http://www.jmlr.org/ | Journal of Machine Learning Research Home Page Papers Submissions News Scope --> Editorial Board Special Issues Open Source Software Proceedings (PMLR) Data (DMLR) Transactions (TMLR) Search Statistics Login Frequently Asked Questions Contact Us Journal of Machine Learning Research The Journal of Machine Learning Research (JMLR), established in 2000 , provides an international forum for the electronic and paper publication of high-quality scholarly articles in all areas of machine learning. All published papers are freely available online. JMLR has a commitment to rigorous yet rapid reviewing. Final versions are published electronically (ISSN 1533-7928) immediately upon receipt. Until the end of 2004, paper volumes (ISSN 1532-4435) were published 8 times annually and sold to libraries and individuals by the MIT Press. Paper volumes (ISSN 1532-4435) are now published and sold by Microtome Publishing . News 2025.02.10 : Volume 25 completed; Volume 26 began. 2024.02.18 : Volume 24 completed; Volume 25 began. 2023.01.20 : Volume 23 completed; Volume 24 began. 2022.07.20 : New special issue on climate change . 2022.02.18 : New blog post: Retrospectives from 20 Years of JMLR . 2022.01.25 : Volume 22 completed; Volume 23 began. 2021.12.02 : Message from outgoing co-EiC Bernhard Schölkopf . 2021.02.10 : Volume 21 completed; Volume 22 began. More news ... Latest papers Towards Understanding Gradient Flow Dynamics of Homogeneous Neural Networks Beyond the Origin Akshay Kumar, Jarvis Haupt , 2025. [ abs ][ pdf ][ bib ] [ code ] Optimal Complexity in Byzantine-Robust Distributed Stochastic Optimization with Data Heterogeneity Qiankun Shi, Jie Peng, Kun Yuan, Xiao Wang, Qing Ling , 2025. [ abs ][ pdf ][ bib ] Towards Unified Native Spaces in Kernel Methods Xavier Emery, Emilio Porcu, Moreno Bevilacqua , 2025. [ abs ][ pdf ][ bib ] TorchCP: A Python Library for Conformal Prediction Jianguo Huang, Jianqing Song, Xuanning Zhou, Bingyi Jing, Hongxin Wei , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Hopfield-Fenchel-Young Networks: A Unified Framework for Associative Memory Retrieval Saul Santos, Vlad Niculae, Daniel McNamee, Andre F.T. Martins , 2025. [ abs ][ pdf ][ bib ] [ code ] Identifiability of Causal Graphs under Non-Additive Conditionally Parametric Causal Models Juraj Bodik, Valérie Chavez-Demoulin , 2025. [ abs ][ pdf ][ bib ] [ code ] Fundamental Limits of Membership Inference Attacks on Machine Learning Models Eric Aubinais, Elisabeth Gassiat, Pablo Piantanida , 2025. [ abs ][ pdf ][ bib ] On the Robustness of Kernel Goodness-of-Fit Tests Xing Liu, François-Xavier Briol , 2025. [ abs ][ pdf ][ bib ] [ code ] Efficient Online Prediction for High-Dimensional Time Series via Joint Tensor Tucker Decomposition Zhenting Luan, Defeng Sun, Haoning Wang, Liping Zhang , 2025. [ abs ][ pdf ][ bib ] Fast Computation of Superquantile-Constrained Optimization Through Implicit Scenario Reduction Jake Roth, Ying Cui , 2025. [ abs ][ pdf ][ bib ] [ code ] Collaborative likelihood-ratio estimation over graphs Alejandro de la Concha, Nicolas Vayatis, Argyris Kalogeratos , 2025. [ abs ][ pdf ][ bib ] [ code ] On the Utility of Equal Batch Sizes for Inference in Stochastic Gradient Descent Rahul Singh, Abhinek Shukla, Dootika Vats , 2025. [ abs ][ pdf ][ bib ] [ code ] Differentially Private Bootstrap: New Privacy Analysis and Inference Strategies Zhanyu Wang, Guang Cheng, Jordan Awan , 2025. [ abs ][ pdf ][ bib ] [ code ] Convergence and Sample Complexity of Natural Policy Gradient Primal-Dual Methods for Constrained MDPs Dongsheng Ding, Kaiqing Zhang, Jiali Duan, Tamer Basar, Mihailo R. Jovanovic , 2025. [ abs ][ pdf ][ bib ] Differentially Private Multivariate Medians Kelly Ramsay, Aukosh Jagannath, Shoja'eddin Chenouri , 2025. [ abs ][ pdf ][ bib ] [ code ] VFOSA: Variance-Reduced Fast Operator Splitting Algorithms for Generalized Equations Quoc Tran-Dinh , 2025. [ abs ][ pdf ][ bib ] Scaling Capability in Token Space: An Analysis of Large Vision Language Model Tenghui Li, Guoxu Zhou, Xuyang Zhao, Qibin Zhao , 2025. [ abs ][ pdf ][ bib ] Minimax Optimal Two-Sample Testing under Local Differential Privacy Jongmin Mun, Seungwoo Kwak, Ilmun Kim , 2025. [ abs ][ pdf ][ bib ] [ code ] Jackpot: Approximating Uncertainty Domains with Adversarial Manifolds Nathanaël Munier, Emmanuel Soubies, Pierre Weiss , 2025. [ abs ][ pdf ][ bib ] [ code ] An Asymptotically Optimal Coordinate Descent Algorithm for Learning Bayesian Networks from Gaussian Models Tong Xu, Simge Küçükyavuz, Ali Shojaie, Armeen Taeb , 2025. [ abs ][ pdf ][ bib ] [ code ] Convergence Rates for Non-Log-Concave Sampling and Log-Partition Estimation David Holzmüller, Francis Bach , 2025. [ abs ][ pdf ][ bib ] [ code ] A Unified Framework to Enforce, Discover, and Promote Symmetry in Machine Learning Samuel E. Otto, Nicholas Zolman, J. Nathan Kutz, Steven L. Brunton , 2025. [ abs ][ pdf ][ bib ] [ code ] Infinite-dimensional Mahalanobis Distance with Applications to Kernelized Novelty Detection Nikita Zozoulenko, Thomas Cass, Lukas Gonon , 2025. [ abs ][ pdf ][ bib ] [ code ] Stable learning using spiking neural networks equipped with affine encoders and decoders A. Martina Neuman, Dominik Dold, Philipp Christian Petersen , 2025. [ abs ][ pdf ][ bib ] [ code ] Efficient Knowledge Deletion from Trained Models Through Layer-wise Partial Machine Unlearning Vinay Chakravarthi Gogineni, Esmaeil S. Nadimi , 2025. [ abs ][ pdf ][ bib ] General Loss Functions Lead to (Approximate) Interpolation in High Dimensions Kuo-Wei Lai, Vidya Muthukumar , 2025. [ abs ][ pdf ][ bib ] Piecewise deterministic sampling with splitting schemes Andrea Bertazzi, Paul Dobson, Pierre Monmarché , 2025. [ abs ][ pdf ][ bib ] [ code ] Hierarchical and Stochastic Crystallization Learning: Geometrically Leveraged Nonparametric Regression with Delaunay Triangulation Jiaqi Gu, Guosheng Yin , 2025. [ abs ][ pdf ][ bib ] Gold-medalist Performance in Solving Olympiad Geometry with AlphaGeometry2 Yuri Chervonyi, Trieu H. Trinh, Miroslav Olšák, Xiaomeng Yang, Hoang H. Nguyen, Marcelo Menegali, Junehyuk Jung, Junsu Kim, Vikas Verma, Quoc V. Le, Thang Luong , 2025. [ abs ][ pdf ][ bib ] [ code ] Decentralized Bilevel Optimization: A Perspective from Transient Iteration Complexity Boao Kong, Shuchen Zhu, Songtao Lu, Xinmeng Huang, Kun Yuan , 2025. [ abs ][ pdf ][ bib ] Fair Text Classification via Transferable Representations Thibaud Leteno, Michael Perrot, Charlotte Laclau, Antoine Gourru, Christophe Gravier , 2025. [ abs ][ pdf ][ bib ] [ code ] Stochastic Interior-Point Methods for Smooth Conic Optimization with Applications Chuan He, Zhanwang Deng , 2025. [ abs ][ pdf ][ bib ] [ code ] Revisiting Gradient Normalization and Clipping for Nonconvex SGD under Heavy-Tailed Noise: Necessity, Sufficiency, and Acceleration Tao Sun, Xinwang Liu, Kun Yuan , 2025. [ abs ][ pdf ][ bib ] Generalized multi-view model: Adaptive density estimation under low-rank constraints Julien Chhor, Olga Klopp, Alexandre B. Tsybakov , 2025. [ abs ][ pdf ][ bib ] [ code ] (De)-regularized Maximum Mean Discrepancy Gradient Flow Zonghao Chen, Aratrika Mustafi, Pierre Glaser, Anna Korba, Arthur Gretton, Bharath K. Sriperumbudur , 2025. [ abs ][ pdf ][ bib ] On Probabilistic Embeddings in Optimal Dimension Reduction Ryan Murray, Adam Pickarski , 2025. [ abs ][ pdf ][ bib ] Physics Informed Kolmogorov-Arnold Neural Networks for Dynamical Analysis via Efficient-KAN and WAV-KAN Subhajit Patra, Sonali Panda, Bikram Keshari Parida, Mahima Arya, Kurt Jacobs, Denys I. Bondar, Abhijit Sen , 2025. [ abs ][ pdf ][ bib ] [ code ] Graph-accelerated Markov Chain Monte Carlo using Approximate Samples Leo L. Duan, Anirban Bhattacharya , 2025. [ abs ][ pdf ][ bib ] [ code ] Online Quantile Regression Yinan Shen, Dong Xia, Wen-Xin Zhou , 2025. [ abs ][ pdf ][ bib ] Statistical Inference of Random Graphs With a Surrogate Likelihood Function Dingbo Wu, Fangzheng Xie , 2025. [ abs ][ pdf ][ bib ] [ code ] On the Representation of Pairwise Causal Background Knowledge and Its Applications in Causal Inference Zhuangyan Fang, Ruiqi Zhao, Yue Liu, Yangbo He , 2025. [ abs ][ pdf ][ bib ] An Augmentation Overlap Theory of Contrastive Learning Qi Zhang, Yifei Wang, Yisen Wang , 2025. [ abs ][ pdf ][ bib ] [ code ] Algorithms for ridge estimation with convergence guarantees Wanli Qiao, Wolfgang Polonik , 2025. [ abs ][ pdf ][ bib ] Talent: A Tabular Analytics and Learning Toolbox Si-Yang Liu, Hao-Run Cai, Qi-Le Zhou, Huai-Hong Yin, Tao Zhou, Jun-Peng Jiang, Han-Jia Ye , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Inferring Change Points in High-Dimensional Regression via Approximate Message Passing Gabriel Arpino, Xiaoqi Liu, Julia Gontarek, Ramji Venkataramanan , 2025. [ abs ][ pdf ][ bib ] [ code ] Universality of Kernel Random Matrices and Kernel Regression in the Quadratic Regime Parthe Pandit, Zhichao Wang, Yizhe Zhu , 2025. [ abs ][ pdf ][ bib ] Lexicographic Lipschitz Bandits: New Algorithms and a Lower Bound Bo Xue, Ji Cheng, Fei Liu, Yimu Wang, Lijun Zhang, Qingfu Zhang , 2025. [ abs ][ pdf ][ bib ] On the Natural Gradient of the Evidence Lower Bound Nihat Ay, Jesse van Oostrum, Adwait Datar , 2025. [ abs ][ pdf ][ bib ] [ code ] Geometry and Stability of Supervised Learning Problems Facundo Mémoli, Brantley Vose, Robert C. Williamson , 2025. [ abs ][ pdf ][ bib ] Understanding Deep Representation Learning via Layerwise Feature Compression and Discrimination Peng Wang, Xiao Li, Can Yaras, Zhihui Zhu, Laura Balzano, Wei Hu, Qing Qu , 2025. [ abs ][ pdf ][ bib ] [ code ] Optimal Rates of Kernel Ridge Regression under Source Condition in Large Dimensions Haobo Zhang, Yicheng Li, Weihao Lu, Qian Lin , 2025. [ abs ][ pdf ][ bib ] A Hybrid Weighted Nearest Neighbour Classifier for Semi-Supervised Learning Stephen M. S. Lee, Mehdi Soleymani , 2025. [ abs ][ pdf ][ bib ] Scalable and Adaptive Variational Bayes Methods for Hawkes Processes Deborah Sulem, Vincent Rivoirard, Judith Rousseau , 2025. [ abs ][ pdf ][ bib ] Biological Sequence Kernels with Guaranteed Flexibility Alan N. Amin, Debora S. Marks, Eli N. Weinstein , 2025. [ abs ][ pdf ][ bib ] [ code ] Unified Discrete Diffusion for Categorical Data Lingxiao Zhao, Xueying Ding, Lijun Yu, Leman Akoglu , 2025. [ abs ][ pdf ][ bib ] [ code ] Reinforcement Learning for Infinite-Dimensional Systems Wei Zhang, Jr-Shin Li , 2025. [ abs ][ pdf ][ bib ] Deep Neural Networks are Adaptive to Function Regularity and Data Distribution in Approximation and Estimation Hao Liu, Jiahui Cheng, Wenjing Liao , 2025. [ abs ][ pdf ][ bib ] Generation of Geodesics with Actor-Critic Reinforcement Learning to Predict Midpoints Kazumi Kasaura , 2025. [ abs ][ pdf ][ bib ] [ code ] Learning-to-Optimize with PAC-Bayesian Guarantees: Theoretical Considerations and Practical Implementation Michael Sucker, Jalal Fadili, Peter Ochs , 2025. [ abs ][ pdf ][ bib ] [ code ] Sparse Semiparametric Discriminant Analysis for High-dimensional Zero-inflated Data Hee Cheol Chung, Yang Ni, Irina Gaynanova , 2025. [ abs ][ pdf ][ bib ] [ code ] Stochastic Interpolants: A Unifying Framework for Flows and Diffusions Michael Albergo, Nicholas M. Boffi, Eric Vanden-Eijnden , 2025. [ abs ][ pdf ][ bib ] Efficient Methods for Non-stationary Online Learning Peng Zhao, Yan-Feng Xie, Lijun Zhang, Zhi-Hua Zhou , 2025. [ abs ][ pdf ][ bib ] Decentralized Asynchronous Optimization with DADAO allows Decoupling and Acceleration Adel Nabli, Edouard Oyallon , 2025. [ abs ][ pdf ][ bib ] [ code ] Mixtures of Gaussian Process Experts with SMC^2 Teemu Härkönen, Sara Wade, Kody Law, Lassi Roininen , 2025. [ abs ][ pdf ][ bib ] [ code ] Robust Point Matching with Distance Profiles YoonHaeng Hur, Yuehaw Khoo , 2025. [ abs ][ pdf ][ bib ] BoFire: Bayesian Optimization Framework Intended for Real Experiments Johannes P. Dürholt, Thomas S. Asche, Johanna Kleinekorte, Gabriel Mancino-Ball, Benjamin Schiller, Simon Sung, Julian Keupp, Aaron Osburg, Toby Boyne, Ruth Misener, Rosona Eldred, Chrysoula Kappatou, Robert M. Lee, Dominik Linzner, Wagner Steuer Costa, David Walz, Niklas Wulkow, Behrang Shafei , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Reliever: Relieving the Burden of Costly Model Fits for Changepoint Detection Chengde Qian, Guanghui Wang, Changliang Zou , 2025. [ abs ][ pdf ][ bib ] Variational Inference for Uncertainty Quantification: an Analysis of Trade-offs Charles C. Margossian, Loucas Pillaud-Vivien, Lawrence K. Saul , 2025. [ abs ][ pdf ][ bib ] [ code ] Are Ensembles Getting Better All the Time? Pierre-Alexandre Mattei, Damien Garreau , 2025. [ abs ][ pdf ][ bib ] [ code ] An Adaptive Parameter-free and Projection-free Restarting Level Set Method for Constrained Convex Optimization Under the Error Bound Condition Qihang Lin, Negar Soheili, Runchao Ma, Selvaprabu Nadarajah , 2025. [ abs ][ pdf ][ bib ] Operator Learning for Hyperbolic PDEs Christopher Wang, Alex Townsend , 2025. [ abs ][ pdf ][ bib ] [ code ] Optimal subsampling for high-dimensional partially linear models via machine learning methods Yujing Shao, Lei Wang, Heng Lian, Haiying Wang , 2025. [ abs ][ pdf ][ bib ] Decentralized Sparse Linear Regression via Gradient-Tracking Marie Maros, Gesualdo Scutari, Ying Sun, Guang Cheng , 2025. [ abs ][ pdf ][ bib ] Calibrated Inference: Statistical Inference that Accounts for Both Sampling Uncertainty and Distributional Uncertainty Yujin Jeong, Dominik Rothenhäusler , 2025. [ abs ][ pdf ][ bib ] Relaxed Gaussian Process Interpolation: a Goal-Oriented Approach to Bayesian Optimization Sébastien J. Petit, Julien Bect, Emmanuel Vazquez , 2025. [ abs ][ pdf ][ bib ] [ code ] Linear Separation Capacity of Self-Supervised Representation Learning Shulei Wang , 2025. [ abs ][ pdf ][ bib ] On the Convergence of Projected Policy Gradient for Any Constant Step Sizes Jiacai Liu, Wenye Li, Dachao Lin, Ke Wei, Zhihua Zhang , 2025. [ abs ][ pdf ][ bib ] Learning with Linear Function Approximations in Mean-Field Control Erhan Bayraktar, Ali Devran Kara , 2025. [ abs ][ pdf ][ bib ] A New Random Reshuffling Method for Nonsmooth Nonconvex Finite-sum Optimization Junwen Qiu, Xiao Li, Andre Milzarek , 2025. [ abs ][ pdf ][ bib ] Model-free Change-Point Detection Using AUC of a Classifier Rohit Kanrar, Feiyu Jiang, Zhanrui Cai , 2025. [ abs ][ pdf ][ bib ] [ code ] EF21 with Bells & Whistles: Six Algorithmic Extensions of Modern Error Feedback Ilyas Fatkhullin, Igor Sokolov, Eduard Gorbunov, Zhize Li, Peter Richtárik , 2025. [ abs ][ pdf ][ bib ] [ code ] Multiple Instance Verification Xin Xu, Eibe Frank, Geoffrey Holmes , 2025. [ abs ][ pdf ][ bib ] [ code ] Learning from Similar Linear Representations: Adaptivity, Minimaxity, and Robustness Ye Tian, Yuqi Gu, Yang Feng , 2025. [ abs ][ pdf ][ bib ] [ code ] Exponential Family Graphical Models: Correlated Replicates and Unmeasured Confounders, with Applications to fMRI Data Yanxin Jin, Yang Ning, Kean Ming Tan , 2025. [ abs ][ pdf ][ bib ] Optimizing Return Distributions with Distributional Dynamic Programming Bernardo Ávila Pires, Mark Rowland, Diana Borsa, Zhaohan Daniel Guo, Khimya Khetarpal, André Barreto, David Abel, Rémi Munos, Will Dabney , 2025. [ abs ][ pdf ][ bib ] Imprecise Multi-Armed Bandits: Representing Irreducible Uncertainty as a Zero-Sum Game Vanessa Kosoy , 2025. [ abs ][ pdf ][ bib ] Early Alignment in Two-Layer Networks Training is a Two-Edged Sword Etienne Boursier, Nicolas Flammarion , 2025. [ abs ][ pdf ][ bib ] [ code ] Hierarchical Decision Making Based on Structural Information Principles Xianghua Zeng, Hao Peng, Dingli Su, Angsheng Li , 2025. [ abs ][ pdf ][ bib ] Generative Adversarial Networks: Dynamics Matias G. Delgadino, Bruno B. Suassuna, Rene Cabrera , 2025. [ abs ][ pdf ][ bib ] "What is Different Between These Datasets?" A Framework for Explaining Data Distribution Shifts Varun Babbar*, Zhicheng Guo*, Cynthia Rudin , 2025. [ abs ][ pdf ][ bib ] [ code ] Assumption-lean and data-adaptive post-prediction inference Jiacheng Miao, Xinran Miao, Yixuan Wu, Jiwei Zhao, Qiongshi Lu , 2025. [ abs ][ pdf ][ bib ] [ code ] Bagged Regularized k-Distances for Anomaly Detection Yuchao Cai, Hanfang Yang, Yuheng Ma, Hanyuan Hang , 2025. [ abs ][ pdf ][ bib ] Four Axiomatic Characterizations of the Integrated Gradients Attribution Method Daniel Lundstrom, Meisam Razaviyayn , 2025. [ abs ][ pdf ][ bib ] Fast Algorithm for Constrained Linear Inverse Problems Mohammed Rayyan Sheriff, Floor Fenne Redel, Peyman Mohajerin Esfahani , 2025. [ abs ][ pdf ][ bib ] [ code ] High-Rank Irreducible Cartesian Tensor Decomposition and Bases of Equivariant Spaces Shihao Shao, Yikang Li, Zhouchen Lin, Qinghua Cui , 2025. [ abs ][ pdf ][ bib ] [ code ] Best Linear Unbiased Estimate from Privatized Contingency Tables Jordan Awan, Adam Edwards, Paul Bartholomew, Andrew Sillers , 2025. [ abs ][ pdf ][ bib ] [ code ] Interpretable Global Minima of Deep ReLU Neural Networks on Sequentially Separable Data Thomas Chen, Patrícia Muñoz Ewald , 2025. [ abs ][ pdf ][ bib ] Enhanced Feature Learning via Regularisation: Integrating Neural Networks and Kernel Methods Bertille FOLLAIN, Francis BACH , 2025. [ abs ][ pdf ][ bib ] [ code ] Data-Driven Performance Guarantees for Classical and Learned Optimizers Rajiv Sambharya, Bartolomeo Stellato , 2025. [ abs ][ pdf ][ bib ] [ code ] Contextual Bandits with Stage-wise Constraints Aldo Pacchiano, Mohammad Ghavamzadeh, Peter Bartlett , 2025. [ abs ][ pdf ][ bib ] Boosting Causal Additive Models Maximilian Kertel, Nadja Klein , 2025. [ abs ][ pdf ][ bib ] [ code ] Frequentist Guarantees of Distributed (Non)-Bayesian Inference Bohan Wu, César A. Uribe , 2025. [ abs ][ pdf ][ bib ] Asymptotic Inference for Multi-Stage Stationary Treatment Policy with Variable Selection Daiqi Gao, Yufeng Liu, Donglin Zeng , 2025. [ abs ][ pdf ][ bib ] [ code ] EMaP: Explainable AI with Manifold-based Perturbations Minh Nhat Vu, Huy Quang Mai, My T. Thai , 2025. [ abs ][ pdf ][ bib ] Autoencoders in Function Space Justin Bunker, Mark Girolami, Hefin Lambley, Andrew M. Stuart, T. J. Sullivan , 2025. [ abs ][ pdf ][ bib ] [ code ] Nonparametric Regression on Random Geometric Graphs Sampled from Submanifolds Paul Rosa, Judith Rousseau , 2025. [ abs ][ pdf ][ bib ] System Neural Diversity: Measuring Behavioral Heterogeneity in Multi-Agent Learning Matteo Bettini, Ajay Shankar, Amanda Prorok , 2025. [ abs ][ pdf ][ bib ] [ code ] Distribution Estimation under the Infinity Norm Aryeh Kontorovich, Amichai Painsky , 2025. [ abs ][ pdf ][ bib ] Extending Temperature Scaling with Homogenizing Maps Christopher Qian, Feng Liang, Jason Adams , 2025. [ abs ][ pdf ][ bib ] [ code ] Density Estimation Using the Perceptron Patrik Róbert Gerber, Tianze Jiang, Yury Polyanskiy, Rui Sun , 2025. [ abs ][ pdf ][ bib ] Simplex Constrained Sparse Optimization via Tail Screening Peng Chen, Jin Zhu, Junxian Zhu, Xueqin Wang , 2025. [ abs ][ pdf ][ bib ] [ code ] Score-Based Diffusion Models in Function Space Jae Hyun Lim, Nikola B. Kovachki, Ricardo Baptista, Christopher Beckham, Kamyar Azizzadenesheli, Jean Kossaifi, Vikram Voleti, Jiaming Song, Karsten Kreis, Jan Kautz, Christopher Pal, Arash Vahdat, Anima Anandkumar , 2025. [ abs ][ pdf ][ bib ] [ code ] Regularized Rényi Divergence Minimization through Bregman Proximal Gradient Algorithms Thomas Guilmeau, Emilie Chouzenoux, Víctor Elvira , 2025. [ abs ][ pdf ][ bib ] WEFE: A Python Library for Measuring and Mitigating Bias in Word Embeddings Pablo Badilla, Felipe Bravo-Marquez, María José Zambrano, Jorge Pérez , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Frontiers to the learning of nonparametric hidden Markov models Kweku Abraham, Elisabeth Gassiat, Zacharie Naulet , 2025. [ abs ][ pdf ][ bib ] On Non-asymptotic Theory of Recurrent Neural Networks in Temporal Point Processes Zhiheng Chen, Guanhua Fang, Wen Yu , 2025. [ abs ][ pdf ][ bib ] Classification in the high dimensional Anisotropic mixture framework: A new take on Robust Interpolation Stanislav Minsker, Mohamed Ndaoud, Yiqiu Shen , 2025. [ abs ][ pdf ][ bib ] Universal Online Convex Optimization Meets Second-order Bounds Lijun Zhang, Yibo Wang, Guanghui Wang, Jinfeng Yi, Tianbao Yang , 2025. [ abs ][ pdf ][ bib ] Sample Complexity of the Linear Quadratic Regulator: A Reinforcement Learning Lens Amirreza Neshaei Moghaddam, Alex Olshevsky, Bahman Gharesifard , 2025. [ abs ][ pdf ][ bib ] Randomization Can Reduce Both Bias and Variance: A Case Study in Random Forests Brian Liu, Rahul Mazumder , 2025. [ abs ][ pdf ][ bib ] skglm: Improving scikit-learn for Regularized Generalized Linear Models Badr Moufad, Pierre-Antoine Bannier, Quentin Bertrand, Quentin Klopfenstein, Mathurin Massias , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Losing Momentum in Continuous-time Stochastic Optimisation Kexin Jin, Jonas Latz, Chenguang Liu, Alessandro Scagliotti , 2025. [ abs ][ pdf ][ bib ] Latent Process Models for Functional Network Data Peter W. MacDonald, Elizaveta Levina, Ji Zhu , 2025. [ abs ][ pdf ][ bib ] [ code ] Dynamic Bayesian Learning for Spatiotemporal Mechanistic Models Sudipto Banerjee, Xiang Chen, Ian Frankenburg, Daniel Zhou , 2025. [ abs ][ pdf ][ bib ] [ code ] On the Ability of Deep Networks to Learn Symmetries from Data: A Neural Kernel Theory Andrea Perin, Stephane Deny , 2025. [ abs ][ pdf ][ bib ] [ code ] Fine-grained Analysis and Faster Algorithms for Iteratively Solving Linear Systems Michal Dereziński, Daniel LeJeune, Deanna Needell, Elizaveta Rebrova , 2025. [ abs ][ pdf ][ bib ] Deep Generative Models: Complexity, Dimensionality, and Approximation Kevin Wang, Hongqian Niu, Yixin Wang, Didong Li , 2025. [ abs ][ pdf ][ bib ] [ code ] ClimSim-Online: A Large Multi-Scale Dataset and Framework for Hybrid Physics-ML Climate Emulation Sungduk Yu, Zeyuan Hu, Akshay Subramaniam, Walter Hannah, Liran Peng, Jerry Lin, Mohamed Aziz Bhouri, Ritwik Gupta, Björn Lütjens, Justus C. Will, Gunnar Behrens, Julius J. M. Busecke, Nora Loose, Charles I Stern, Tom Beucler, Bryce Harrop, Helge Heuer, Benjamin R Hillman, Andrea Jenney, Nana Liu, Alistair White, Tian Zheng, Zhiming Kuang, Fiaz Ahmed, Elizabeth Barnes, Noah D. Brenowitz, Christopher Bretherton, Veronika Eyring, Savannah Ferretti, Nicholas Lutsko, Pierre Gentine, Stephan Mandt, J. David Neelin, Rose Yu, Laure Zanna, Nathan M. Urban, Janni Yuval, Ryan Abernathey, Pierre Baldi, Wayne Chuang, Yu Huang, Fernando Iglesias-Suarez, Sanket Jantre, Po-Lun Ma, Sara Shamekh, Guang Zhang, Michael Pritchard , 2025. [ abs ][ pdf ][ bib ] [ code ] Conditional Wasserstein Distances with Applications in Bayesian OT Flow Matching Jannis Chemseddine, Paul Hagemann, Gabriele Steidl, Christian Wald , 2025. [ abs ][ pdf ][ bib ] [ code ] Deep Variational Multivariate Information Bottleneck - A Framework for Variational Losses Eslam Abdelaleem, Ilya Nemenman, K. Michael Martini , 2025. [ abs ][ pdf ][ bib ] [ code ] Diffeomorphism-based feature learning using Poincaré inequalities on augmented input space Romain Verdière, Clémentine Prieur, Olivier Zahm , 2025. [ abs ][ pdf ][ bib ] Finite Expression Method for Solving High-Dimensional Partial Differential Equations Senwei Liang, Haizhao Yang , 2025. [ abs ][ pdf ][ bib ] [ code ] Randomly Projected Convex Clustering Model: Motivation, Realization, and Cluster Recovery Guarantees Ziwen Wang, Yancheng Yuan, Jiaming Ma, Tieyong Zeng, Defeng Sun , 2025. [ abs ][ pdf ][ bib ] Minimax Optimal Deep Neural Network Classifiers Under Smooth Decision Boundary Tianyang Hu, Ruiqi Liu, Zuofeng Shang, Guang Cheng , 2025. [ abs ][ pdf ][ bib ] Optimal and Efficient Algorithms for Decentralized Online Convex Optimization Yuanyu Wan, Tong Wei, Bo Xue, Mingli Song, Lijun Zhang , 2025. [ abs ][ pdf ][ bib ] Characterizing Dynamical Stability of Stochastic Gradient Descent in Overparameterized Learning Dennis Chemnitz, Maximilian Engel , 2025. [ abs ][ pdf ][ bib ] PREMAP: A Unifying PREiMage APproximation Framework for Neural Networks Xiyue Zhang, Benjie Wang, Marta Kwiatkowska, Huan Zhang , 2025. [ abs ][ pdf ][ bib ] Score-Aware Policy-Gradient and Performance Guarantees using Local Lyapunov Stability Céline Comte, Matthieu Jonckheere, Jaron Sanders, Albert Senen-Cerda , 2025. [ abs ][ pdf ][ bib ] [ code ] On the O(sqrt(d)/T^(1/4)) Convergence Rate of RMSProp and Its Momentum Extension Measured by l_1 Norm Huan Li, Yiming Dong, Zhouchen Lin , 2025. [ abs ][ pdf ][ bib ] [ code ] Categorical Semantics of Compositional Reinforcement Learning Georgios Bakirtzis, Michail Savvas, Ufuk Topcu , 2025. [ abs ][ pdf ][ bib ] Transformers from Diffusion: A Unified Framework for Neural Message Passing Qitian Wu, David Wipf, Junchi Yan , 2025. [ abs ][ pdf ][ bib ] [ code ] Optimal Sample Selection Through Uncertainty Estimation and Its Application in Deep Learning Yong Lin, Chen Liu, Chenlu Ye, Qing Lian, Yuan Yao, Tong Zhang , 2025. [ abs ][ pdf ][ bib ] [ code ] Actor-Critic learning for mean-field control in continuous time Noufel FRIKHA, Maximilien GERMAIN, Mathieu LAURIERE, Huyen PHAM, Xuanye SONG , 2025. [ abs ][ pdf ][ bib ] Modelling Populations of Interaction Networks via Distance Metrics George Bolt, Simón Lunagómez, Christopher Nemeth , 2025. [ abs ][ pdf ][ bib ] BitNet: 1-bit Pre-training for Large Language Models Hongyu Wang, Shuming Ma, Lingxiao Ma, Lei Wang, Wenhui Wang, Li Dong, Shaohan Huang, Huaijie Wang, Jilong Xue, Ruiping Wang, Yi Wu, Furu Wei , 2025. [ abs ][ pdf ][ bib ] Physics-informed Kernel Learning Nathan Doumèche, Francis Bach, Gérard Biau, Claire Boyer , 2025. [ abs ][ pdf ][ bib ] [ code ] Last-iterate Convergence of Shuffling Momentum Gradient Method under the Kurdyka-Lojasiewicz Inequality Yuqing Liang, Dongpo Xu , 2025. [ abs ][ pdf ][ bib ] Posterior and Variational Inference for Deep Neural Networks with Heavy-Tailed Weights Paul Egels, Ismaël Castillo , 2025. [ abs ][ pdf ][ bib ] Maximum Causal Entropy IRL in Mean-Field Games and GNEP Framework for Forward RL Berkay Anahtarci, Can Deha Kariksiz, Naci Saldi , 2025. [ abs ][ pdf ][ bib ] Degree of Interference: A General Framework For Causal Inference Under Interference Yuki Ohnishi, Bikram Karmakar, Arman Sabbaghi , 2025. [ abs ][ pdf ][ bib ] Quantifying the Effectiveness of Linear Preconditioning in Markov Chain Monte Carlo Max Hird, Samuel Livingstone , 2025. [ abs ][ pdf ][ bib ] Sparse SVM with Hard-Margin Loss: a Newton-Augmented Lagrangian Method in Reduced Dimensions Penghe Zhang, Naihua Xiu, Hou-Duo Qi , 2025. [ abs ][ pdf ][ bib ] On Model Identification and Out-of-Sample Prediction of PCR with Applications to Synthetic Controls Anish Agarwal, Devavrat Shah, Dennis Shen , 2025. [ abs ][ pdf ][ bib ] [ code ] Bayesian Scalar-on-Image Regression with a Spatially Varying Single-layer Neural Network Prior Ben Wu, Keru Wu, Jian Kang , 2025. [ abs ][ pdf ][ bib ] DRM Revisited: A Complete Error Analysis Yuling Jiao, Ruoxuan Li, Peiying Wu, Jerry Zhijian Yang, Pingwen Zhang , 2025. [ abs ][ pdf ][ bib ] Principled Penalty-based Methods for Bilevel Reinforcement Learning and RLHF Han Shen, Zhuoran Yang, Tianyi Chen , 2025. [ abs ][ pdf ][ bib ] Precise High-Dimensional Asymptotics for Quantifying Heterogeneous Transfers Fan Yang, Hongyang R. Zhang, Sen Wu, Christopher Re, Weijie J. Su , 2025. [ abs ][ pdf ][ bib ] [ code ] Score-based Causal Representation Learning: Linear and General Transformations Burak Varici, Emre Acartürk, Karthikeyan Shanmugam, Abhishek Kumar, Ali Tajer , 2025. [ abs ][ pdf ][ bib ] [ code ] On the Statistical Properties of Generative Adversarial Models for Low Intrinsic Data Dimension Saptarshi Chakraborty, Peter L. Bartlett , 2025. [ abs ][ pdf ][ bib ] Prominent Roles of Conditionally Invariant Components in Domain Adaptation: Theory and Algorithms Keru Wu, Yuansi Chen, Wooseok Ha, Bin Yu , 2025. [ abs ][ pdf ][ bib ] [ code ] Near-Optimal Nonconvex-Strongly-Convex Bilevel Optimization with Fully First-Order Oracles Lesi Chen, Yaohua Ma, Jingzhao Zhang , 2025. [ abs ][ pdf ][ bib ] Adaptive Distributed Kernel Ridge Regression: A Feasible Distributed Learning Scheme for Data Silos Shao-Bo Lin, Xiaotong Liu, Di Wang, Hai Zhang, Ding-Xuan Zhou , 2025. [ abs ][ pdf ][ bib ] On Global and Local Convergence of Iterative Linear Quadratic Optimization Algorithms for Discrete Time Nonlinear Control Vincent Roulet, Siddhartha Srinivasa, Maryam Fazel, Zaid Harchaoui , 2025. [ abs ][ pdf ][ bib ] [ code ] A Decentralized Proximal Gradient Tracking Algorithm for Composite Optimization on Riemannian Manifolds Lei Wang, Le Bao, Xin Liu , 2025. [ abs ][ pdf ][ bib ] Learning conditional distributions on continuous spaces Cyril Benezet, Ziteng Cheng, Sebastian Jaimungal , 2025. [ abs ][ pdf ][ bib ] [ code ] A Unified Analysis of Nonstochastic Delayed Feedback for Combinatorial Semi-Bandits, Linear Bandits, and MDPs Lukas Zierahn, Dirk van der Hoeven, Tal Lancewicki, Aviv Rosenberg, Nicolò Cesa-Bianchi , 2025. [ abs ][ pdf ][ bib ] [ code ] Error bounds for particle gradient descent, and extensions of the log-Sobolev and Talagrand inequalities Rocco Caprio, Juan Kuntz, Samuel Power, Adam M. Johansen , 2025. [ abs ][ pdf ][ bib ] Linear Hypothesis Testing in High-Dimensional Expected Shortfall Regression with Heavy-Tailed Errors Gaoyu Wu, Jelena Bradic, Kean Ming Tan, Wen-Xin Zhou , 2025. [ abs ][ pdf ][ bib ] Efficient Numerical Integration in Reproducing Kernel Hilbert Spaces via Leverage Scores Sampling Antoine Chatalic, Nicolas Schreuder, Ernesto De Vito, Lorenzo Rosasco , 2025. [ abs ][ pdf ][ bib ] [ code ] Distribution Free Tests for Model Selection Based on Maximum Mean Discrepancy with Estimated Parameters Florian Brück, Jean-David Fermanian, Aleksey Min , 2025. [ abs ][ pdf ][ bib ] [ code ] Statistical field theory for Markov decision processes under uncertainty George Stamatescu , 2025. [ abs ][ pdf ][ bib ] Bayesian Data Sketching for Varying Coefficient Regression Models Rajarshi Guhaniyogi, Laura Baracaldo, Sudipto Banerjee , 2025. [ abs ][ pdf ][ bib ] Bagged k-Distance for Mode-Based Clustering Using the Probability of Localized Level Sets Hanyuan Hang , 2025. [ abs ][ pdf ][ bib ] Linear cost and exponentially convergent approximation of Gaussian Matérn processes on intervals David Bolin, Vaibhav Mehandiratta, Alexandre B. Simas , 2025. [ abs ][ pdf ][ bib ] [ code ] Invariant Subspace Decomposition Margherita Lazzaretto, Jonas Peters, Niklas Pfister , 2025. [ abs ][ pdf ][ bib ] [ code ] Posterior Concentrations of Fully-Connected Bayesian Neural Networks with General Priors on the Weights Insung Kong, Yongdai Kim , 2025. [ abs ][ pdf ][ bib ] Outlier Robust and Sparse Estimation of Linear Regression Coefficients Takeyuki Sasai, Hironori Fujisawa , 2025. [ abs ][ pdf ][ bib ] Affine Rank Minimization via Asymptotic Log-Det Iteratively Reweighted Least Squares Sebastian Krämer , 2025. [ abs ][ pdf ][ bib ] Causal Effect of Functional Treatment Ruoxu Tan, Wei Huang, Zheng Zhang, Guosheng Yin , 2025. [ abs ][ pdf ][ bib ] [ code ] Uplift Model Evaluation with Ordinal Dominance Graphs Brecht Verbeken, Marie-Anne Guerry, Wouter Verbeke, Sam Verboven , 2025. [ abs ][ pdf ][ bib ] High-Dimensional L2-Boosting: Rate of Convergence Ye Luo, Martin Spindler, Jannis Kueck , 2025. [ abs ][ pdf ][ bib ] Feature Learning in Finite-Width Bayesian Deep Linear Networks with Multiple Outputs and Convolutional Layers Federico Bassetti, Marco Gherardi, Alessandro Ingrosso, Mauro Pastore, Pietro Rotondo , 2025. [ abs ][ pdf ][ bib ] How good is your Laplace approximation of the Bayesian posterior? Finite-sample computable error bounds for a variety of useful divergences Mikolaj J. Kasprzak, Ryan Giordano, Tamara Broderick , 2025. [ abs ][ pdf ][ bib ] [ code ] Integral Probability Metrics Meet Neural Networks: The Radon-Kolmogorov-Smirnov Test Seunghoon Paik, Michael Celentano, Alden Green, Ryan J. Tibshirani , 2025. [ abs ][ pdf ][ bib ] [ code ] On Inference for the Support Vector Machine Jakub Rybak, Heather Battey, Wen-Xin Zhou , 2025. [ abs ][ pdf ][ bib ] Random Pruning Over-parameterized Neural Networks Can Improve Generalization: A Training Dynamics Analysis Hongru Yang, Yingbin Liang, Xiaojie Guo, Lingfei Wu, Zhangyang Wang , 2025. [ abs ][ pdf ][ bib ] Causal Abstraction: A Theoretical Foundation for Mechanistic Interpretability Atticus Geiger, Duligur Ibeling, Amir Zur, Maheep Chaudhary, Sonakshi Chauhan, Jing Huang, Aryaman Arora, Zhengxuan Wu, Noah Goodman, Christopher Potts, Thomas Icard , 2025. [ abs ][ pdf ][ bib ] Implicit vs Unfolded Graph Neural Networks Yongyi Yang, Tang Liu, Yangkun Wang, Zengfeng Huang, David Wipf , 2025. [ abs ][ pdf ][ bib ] Towards Optimal Branching of Linear and Semidefinite Relaxations for Neural Network Robustness Certification Brendon G. Anderson, Ziye Ma, Jingqi Li, Somayeh Sojoudi , 2025. [ abs ][ pdf ][ bib ] GraphNeuralNetworks.jl: Deep Learning on Graphs with Julia Carlo Lucibello, Aurora Rossi , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Dynamic angular synchronization under smoothness constraints Ernesto Araya, Mihai Cucuringu, Hemant Tyagi , 2025. [ abs ][ pdf ][ bib ] [ code ] Derivative-Informed Neural Operator Acceleration of Geometric MCMC for Infinite-Dimensional Bayesian Inverse Problems Lianghao Cao, Thomas O'Leary-Roseberry, Omar Ghattas , 2025. [ abs ][ pdf ][ bib ] [ code ] Wasserstein F-tests for Frechet regression on Bures-Wasserstein manifolds Haoshu Xu, Hongzhe Li , 2025. [ abs ][ pdf ][ bib ] Distributed Stochastic Bilevel Optimization: Improved Complexity and Heterogeneity Analysis Youcheng Niu, Jinming Xu, Ying Sun, Yan Huang, Li Chai , 2025. [ abs ][ pdf ][ bib ] Learning causal graphs via nonlinear sufficient dimension reduction Eftychia Solea, Bing Li, Kyongwon Kim , 2025. [ abs ][ pdf ][ bib ] On Consistent Bayesian Inference from Synthetic Data Ossi Räisä, Joonas Jälkö, Antti Honkela , 2025. [ abs ][ pdf ][ bib ] [ code ] Optimization Over a Probability Simplex James Chok, Geoffrey M. Vasil , 2025. [ abs ][ pdf ][ bib ] [ code ] Laplace Meets Moreau: Smooth Approximation to Infimal Convolutions Using Laplace's Method Ryan J. Tibshirani, Samy Wu Fung, Howard Heaton, Stanley Osher , 2025. [ abs ][ pdf ][ bib ] [ code ] Sampling and Estimation on Manifolds using the Langevin Diffusion Karthik Bharath, Alexander Lewis, Akash Sharma, Michael V. Tretyakov , 2025. [ abs ][ pdf ][ bib ] Sharp Bounds for Sequential Federated Learning on Heterogeneous Data Yipeng Li, Xinchen Lyu , 2025. [ abs ][ pdf ][ bib ] [ code ] Local Linear Recovery Guarantee of Deep Neural Networks at Overparameterization Yaoyu Zhang, Leyang Zhang, Zhongwang Zhang, Zhiwei Bai , 2025. [ abs ][ pdf ][ bib ] Stabilizing Sharpness-Aware Minimization Through A Simple Renormalization Strategy Chengli Tan, Jiangshe Zhang, Junmin Liu, Yicheng Wang, Yunda Hao , 2025. [ abs ][ pdf ][ bib ] Fine-Grained Change Point Detection for Topic Modeling with Pitman-Yor Process Feifei Wang, Zimeng Zhao, Ruimin Ye, Xiaoge Gu, Xiaoling Lu , 2025. [ abs ][ pdf ][ bib ] Deletion Robust Non-Monotone Submodular Maximization over Matroids Paul Dütting, Federico Fusco, Silvio Lattanzi, Ashkan Norouzi-Fard, Morteza Zadimoghaddam , 2025. [ abs ][ pdf ][ bib ] Instability, Computational Efficiency and Statistical Accuracy Nhat Ho, Koulik Khamaru, Raaz Dwivedi, Martin J. Wainwright, Michael I. Jordan, Bin Yu , 2025. [ abs ][ pdf ][ bib ] Estimation of Local Geometric Structure on Manifolds from Noisy Data Yariv Aizenbud, Barak Sober , 2025. [ abs ][ pdf ][ bib ] [ code ] Ontolearn---A Framework for Large-scale OWL Class Expression Learning in Python Caglar Demir, Alkid Baci, N'Dah Jean Kouagou, Leonie Nora Sieger, Stefan Heindorf, Simon Bin, Lukas Blübaum, Alexander Bigerl, Axel-Cyrille Ngonga Ngomo , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Continuously evolving rewards in an open-ended environment Richard M. Bailey , 2025. [ abs ][ pdf ][ bib ] Recursive Causal Discovery Ehsan Mokhtarian, Sepehr Elahi, Sina Akbari, Negar Kiyavash , 2025. [ abs ][ pdf ][ bib ] [ code ] Evaluation of Active Feature Acquisition Methods for Time-varying Feature Settings Henrik von Kleist, Alireza Zamanian, Ilya Shpitser, Narges Ahmidi , 2025. [ abs ][ pdf ][ bib ] On Adaptive Stochastic Optimization for Streaming Data: A Newton's Method with O(dN) Operations Antoine Godichon-Baggioni, Nicklas Werge , 2025. [ abs ][ pdf ][ bib ] Determine the Number of States in Hidden Markov Models via Marginal Likelihood Yang Chen, Cheng-Der Fuh, Chu-Lan Michael Kao , 2025. [ abs ][ pdf ][ bib ] Variance-Aware Estimation of Kernel Mean Embedding Geoffrey Wolfer, Pierre Alquier , 2025. [ abs ][ pdf ][ bib ] Scaling ResNets in the Large-depth Regime Pierre Marion, Adeline Fermanian, Gérard Biau, Jean-Philippe Vert , 2025. [ abs ][ pdf ][ bib ] [ code ] A Comparative Evaluation of Quantification Methods Tobias Schumacher, Markus Strohmaier, Florian Lemmerich , 2025. [ abs ][ pdf ][ bib ] [ code ] Lightning UQ Box: Uncertainty Quantification for Neural Networks Nils Lehmann, Nina Maria Gottschling, Jakob Gawlikowski, Adam J. Stewart, Stefan Depeweg, Eric Nalisnick , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Scaling Data-Constrained Language Models Niklas Muennighoff, Alexander M. Rush, Boaz Barak, Teven Le Scao, Aleksandra Piktus, Nouamane Tazi, Sampo Pyysalo, Thomas Wolf, Colin Raffel , 2025. [ abs ][ pdf ][ bib ] [ code ] Curvature-based Clustering on Graphs Yu Tian, Zachary Lubberts, Melanie Weber , 2025. [ abs ][ pdf ][ bib ] Composite Goodness-of-fit Tests with Kernels Oscar Key, Arthur Gretton, François-Xavier Briol, Tamara Fernandez , 2025. [ abs ][ pdf ][ bib ] [ code ] PFLlib: A Beginner-Friendly and Comprehensive Personalized Federated Learning Library and Benchmark Jianqing Zhang, Yang Liu, Yang Hua, Hao Wang, Tao Song, Zhengui Xue, Ruhui Ma, Jian Cao , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] The Effect of SGD Batch Size on Autoencoder Learning: Sparsity, Sharpness, and Feature Learning Nikhil Ghosh, Spencer Frei, Wooseok Ha, Bin Yu , 2025. [ abs ][ pdf ][ bib ] Efficient and Robust Transfer Learning of Optimal Individualized Treatment Regimes with Right-Censored Survival Data Pan Zhao, Julie Josse, Shu Yang , 2025. [ abs ][ pdf ][ bib ] [ code ] DAGs as Minimal I-maps for the Induced Models of Causal Bayesian Networks under Conditioning Xiangdong Xie, Jiahua Guo, Yi Sun , 2025. [ abs ][ pdf ][ bib ] [ code ] Adjusted Expected Improvement for Cumulative Regret Minimization in Noisy Bayesian Optimization Shouri Hu, Haowei Wang, Zhongxiang Dai, Bryan Kian Hsiang Low, Szu Hui Ng , 2025. [ abs ][ pdf ][ bib ] Manifold Fitting under Unbounded Noise Zhigang Yao, Yuqing Xia , 2025. [ abs ][ pdf ][ bib ] Learning Global Nash Equilibrium in Team Competitive Games with Generalized Fictitious Cross-Play Zelai Xu, Chao Yu, Yancheng Liang, Yi Wu, Yu Wang , 2025. [ abs ][ pdf ][ bib ] Wasserstein Convergence Guarantees for a General Class of Score-Based Generative Models Xuefeng Gao, Hoang M. Nguyen, Lingjiong Zhu , 2025. [ abs ][ pdf ][ bib ] Extremal graphical modeling with latent variables via convex optimization Sebastian Engelke, Armeen Taeb , 2025. [ abs ][ pdf ][ bib ] [ code ] On the Approximation of Kernel functions Paul Dommel, Alois Pichler , 2025. [ abs ][ pdf ][ bib ] Efficient and Robust Semi-supervised Estimation of Average Treatment Effect with Partially Annotated Treatment and Response Jue Hou, Rajarshi Mukherjee, Tianxi Cai , 2025. [ abs ][ pdf ][ bib ] [ code ] Nonconvex Stochastic Bregman Proximal Gradient Method with Application to Deep Learning Kuangyu Ding, Jingyang Li, Kim-Chuan Toh , 2025. [ abs ][ pdf ][ bib ] Optimizing Data Collection for Machine Learning Rafid Mahmood, James Lucas, Jose M. Alvarez, Sanja Fidler, Marc T. Law , 2025. [ abs ][ pdf ][ bib ] Unbalanced Kantorovich-Rubinstein distance, plan, and barycenter on nite spaces: A statistical perspective Shayan Hundrieser, Florian Heinemann, Marcel Klatt, Marina Struleva, Axel Munk , 2025. [ abs ][ pdf ][ bib ] Copula-based Sensitivity Analysis for Multi-Treatment Causal Inference with Unobserved Confounding Jiajing Zheng, Alexander D'Amour, Alexander Franks , 2025. [ abs ][ pdf ][ bib ] [ code ] Rank-one Convexification for Sparse Regression Alper Atamturk, Andres Gomez , 2025. [ abs ][ pdf ][ bib ] gsplat: An Open-Source Library for Gaussian Splatting Vickie Ye, Ruilong Li, Justin Kerr, Matias Turkulainen, Brent Yi, Zhuoyang Pan, Otto Seiskari, Jianbo Ye, Jeffrey Hu, Matthew Tancik, Angjoo Kanazawa , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] Statistical Inference of Constrained Stochastic Optimization via Sketched Sequential Quadratic Programming Sen Na, Michael Mahoney , 2025. [ abs ][ pdf ][ bib ] Sliced-Wasserstein Distances and Flows on Cartan-Hadamard Manifolds Clément Bonet, Lucas Drumetz, Nicolas Courty , 2025. [ abs ][ pdf ][ bib ] [ code ] Accelerating optimization over the space of probability measures Shi Chen, Qin Li, Oliver Tse, Stephen J. Wright , 2025. [ abs ][ pdf ][ bib ] Bayesian Multi-Group Gaussian Process Models for Heterogeneous Group-Structured Data Didong Li, Andrew Jones, Sudipto Banerjee, Barbara E. Engelhardt , 2025. [ abs ][ pdf ][ bib ] [ code ] Orthogonal Bases for Equivariant Graph Learning with Provable k-WL Expressive Power Jia He, Maggie Cheng , 2025. [ abs ][ pdf ][ bib ] Optimal Experiment Design for Causal Effect Identification Sina Akbari, Jalal Etesami, Negar Kiyavash , 2025. [ abs ][ pdf ][ bib ] [ code ] Mean Aggregator is More Robust than Robust Aggregators under Label Poisoning Attacks on Distributed Heterogeneous Data Jie Peng, Weiyu Li, Stefan Vlaski, Qing Ling , 2025. [ abs ][ pdf ][ bib ] [ code ] The Blessing of Heterogeneity in Federated Q-Learning: Linear Speedup and Beyond Jiin Woo, Gauri Joshi, Yuejie Chi , 2025. [ abs ][ pdf ][ bib ] depyf: Open the Opaque Box of PyTorch Compiler for Machine Learning Researchers Kaichao You, Runsheng Bai, Meng Cao, Jianmin Wang, Ion Stoica, Mingsheng Long , 2025. (Machine Learning Open Source Software Paper) [ abs ][ pdf ][ bib ] [ code ] The ODE Method for Stochastic Approximation and Reinforcement Learning with Markovian Noise Shuze Daniel Liu, Shuhang Chen, Shangtong Zhang , 2025. [ abs ][ pdf ][ bib ] Improving Graph Neural Networks on Multi-node Tasks with the Labeling Trick Xiyuan Wang, Pan Li, Muhan Zhang , 2025. [ abs ][ pdf ][ bib ] [ code ] Directed Cyclic Graphs for Simultaneous Discovery of Time-Lagged and Instantaneous Causality from Longitudinal Data Using Instrumental Variables Wei Jin, Yang Ni, Amanda B. Spence, Leah H. Rubin, Yanxun Xu , 2025. [ abs ][ pdf ][ bib ] [ code ] Bayesian Sparse Gaussian Mixture Model for Clustering in High Dimensions Dapeng Yao, Fangzheng Xie, Yanxun Xu , 2025. [ abs ][ pdf ][ bib ] Regularizing Hard Examples Improves Adversarial Robustness Hyungyu Lee, Saehyung Lee, Ho Bae, Sungroh Yoon , 2025. [ abs ][ pdf ][ bib ] Random ReLU Neural Networks as Non-Gaussian Processes Rahul Parhi, Pakshal Bohra, Ayoub El Biari, Mehrsa Pourya, Michael Unser , 2025. [ abs ][ pdf ][ bib ] Riemannian Bilevel Optimization Jiaxiang Li, Shiqian Ma , 2025. [ abs ][ pdf ][ bib ] [ code ] Supervised Learning with Evolving Tasks and Performance Guarantees Verónica Álvarez, Santiago Mazuelas, Jose A. Lozano , 2025. [ abs ][ pdf ][ bib ] [ code ] Error estimation and adaptive tuning for unregularized robust M-estimator Pierre C. Bellec, Takuya Koriyama , 2025. [ abs ][ pdf ][ bib ] From Sparse to Dense Functional Data in High Dimensions: Revisiting Phase Transitions from a Non-Asymptotic Perspective Shaojun Guo, Dong Li, Xinghao Qiao, Yizhu Wang , 2025. [ abs ][ pdf ][ bib ] Locally Private Causal Inference for Randomized Experiments Yuki Ohnishi, Jordan Awan , 2025. [ abs ][ pdf ][ bib ] Estimating Network-Mediated Causal Effects via Principal Components Network Regression Alex Hayes, Mark M. Fredrickson, Keith Levin , 2025. [ abs ][ pdf ][ bib ] [ code ] Selective Inference with Distributed Data Sifan Liu, Snigdha Panigrahi , 2025. [ abs ][ pdf ][ bib ] [ code ] Two-Timescale Gradient Descent Ascent Algorithms for Nonconvex Minimax Optimization Tianyi Lin, Chi Jin, Michael I. Jordan , 2025. [ abs ][ pdf ][ bib ] An Axiomatic Definition of Hierarchical Clustering Ery Arias-Castro, Elizabeth Coda , 2025. [ abs ][ pdf ][ bib ] Test-Time Training on Video Streams Renhao Wang, Yu Sun, Arnuv Tandon, Yossi Gandelsman, Xinlei Chen, Alexei A. Efros, Xiaolong Wang , 2025. [ abs ][ pdf ][ bib ] [ code ] Adaptive Client Sampling in Federated Learning via Online Learning with Bandit Feedback Boxin Zhao, Lingxiao Wang, Ziqi Liu, Zhiqiang Zhang, Jun Zhou, Chaochao Chen, Mladen Kolar , 2025. [ abs ][ pdf ][ bib ] [ code ] A Random Matrix Approach to Low-Multilinear-Rank Tensor Approximation Hugo Lebeau, Florent Chatelain, Romain Couillet , 2025. [ abs ][ pdf ][ bib ] Memory Gym: Towards Endless Tasks to Benchmark Memory Capabilities of Agents Marco Pleines, Matthias Pallasch, Frank Zimmer, Mike Preuss , 2025. [ abs ][ pdf ][ bib ] [ code ] Enhancing Graph Representation Learning with Localized Topological Features Zuoyu Yan, Qi Zhao, Ze Ye, Tengfei Ma, Liangcai Gao, Zhi Tang, Yusu Wang, Chao Chen , 2025. [ abs ][ pdf ][ bib ] Deep Out-of-Distribution Uncertainty Quantification via Weight Entropy Maximization Antoine de Mathelin, François Deheeger, Mathilde Mougeot, Nicolas Vayatis , 2025. [ abs ][ pdf ][ bib ] DisC2o-HD: Distributed causal inference with covariates shift for analyzing real-world high-dimensional data Jiayi Tong, Jie Hu, George Hripcsak, Yang Ning, Yong Chen , 2025. [ abs ][ pdf ][ bib ] Bayes Meets Bernstein at the Meta Level: an Analysis of Fast Rates in Meta-Learning with PAC-Bayes Charles Riou, Pierre Alquier, Badr-Eddine Chérief-Abdellatif , 2025. [ abs ][ pdf ][ bib ] Efficiently Escaping Saddle Points in Bilevel Optimization Minhui Huang, Xuxing Chen, Kaiyi Ji, Shiqian Ma, Lifeng Lai , 2025. [ abs ][ pdf ][ bib ] Full list © JMLR 2026. Mastodon | 2026-01-13T09:29:14 |
https://www.linkedin.com/products/scalecomputing-hc3-edge/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | SC//Platform | LinkedIn Skip to main content LinkedIn Scale Computing in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in SC//Platform Server Virtualization Software by Scale Computing See who's skilled in this Add as skill Learn more Report this product About With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. The award winning Scale Computing brings on-premises edge computing with high availability and disaster recovery to remote locations at an affordable entry level cost. All edge appliances can be deployed quickly, managed locally or remotely, and can self-heal almost instantly. Enjoy affordable edge computing infrastructure that is reliable, easy to deploy, and easy to use. This product is intended for Chief Information Officer Vice President Information Technology Director of Information Technology Head of Innovation Software Architect Enterprise Architect Network Engineer Media Products media viewer No more previous content Scale Computing HC3 Edge: Compute from Beyond the Datacenter With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. No more next content Featured customers of SC//Platform Telford Offshore Oil and Gas 45,517 followers Maritime Paper Products Limited Packaging and Containers Manufacturing 3,201 followers Jerry's Enterprises Retail 1,514 followers Harrison Steel Castings Co. Mining 2,061 followers Ahold Delhaize Retail 180,797 followers GOODWILL CENTRAL COAST Retail 404 followers Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Scale Computing products SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//HyperCore SC//HyperCore LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:14 |
https://www.fxn.xyz/points | Function | FBTC About Function Points Program Dashboard Campaign Connect About Dashboard Campaign Connect FBTC Yield & Campaign Deposit or stake your FBTC into 30+ projects to earn Sparks. View Your Points Earn Points Get FBTC $ 0 TVL - BTC Deposited - Holders 30+ Integrations Our Featured Projects View Your Points Company About Blog Protocol Ecosystem Proof of Assets Dune Dashboard Resources Documentation Audits Media Assets Legal Privacy Policy Terms of Service Risk Disclosure Statement Get in Touch Discord Medium Github Linkedin Telegram X © Function 2025. All rights reserved | 2026-01-13T09:29:15 |
https://opensource.guide/sw/starting-a-project/ | Kuanzisha Mradi wa Open Source | Open Source Guides Kuhusu Changia العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Kuanzisha Mradi wa Open Source Jifunze zaidi kuhusu ulimwengu wa Open Source na uwe tayari kuzindua mradi wako mwenyewe. Jedwali la Yaliyomo “Nini” na “Kwa Nini” ya Open Source Je, ni lazima nizindue mradi wangu wa open source? Kuzindua mradi wako wa open source Kutoa jina na kuchapisha ya mradi wako Orodha yako ya ukaguzi kabla ya uzinduzi “Nini” na “Kwa Nini” ya Open Source Basi unafikiria kuanza na open source? Hongera! Ulimwengu unathamini mchango wako. Hebu tuzungumze kuhusu nini open source ni na kwa nini watu huifanya. Nini maana ya “open source”? Wakati mradi ni open source, inamaanisha mtu yeyote yuko huru kutumia, kujifunza, kubadilisha, na kusambaza mradi wako kwa kusudi lolote. Ruhusa hizi zinaimarishwa kupitia leseni ya open source . Open source ni nguvu kwa sababu inashusha vizuizi vya kupitisha na ushirikiano, ikiruhusu watu kueneza na kuboresha miradi haraka. Pia kwa sababu inawapa watumiaji uwezo wa kudhibiti kompyuta zao, ikilinganishwa na mradi usio huria. Kwa mfano, biashara inayotumia programu ya open source ina chaguo la kuajiri mtu kufanya maboresho maalum kwa programu hiyo, badala ya kutegemea maamuzi ya bidhaa ya muuzaji wa mradi usio huria pekee. Programu ya bure inarejelea seti sawa ya miradi kama open source . Wakati mwingine utaona maneno haya yakiwa pamoja kama “free and open source software” (FOSS) au “free, libre, and open source software” (FLOSS). Free na libre zinarejelea uhuru, sio bei . Kwa nini watu wanafungua chanzo cha kazi zao? Moja ya uzoefu wa kuridhisha zaidi ninapata kutokana na kutumia na kushirikiana kwenye open source inatokana na uhusiano ninayounda na wabunifu wengine wanaokabiliwa na matatizo mengi kama mimi. — @kentcdodds, “Jinsi ya kuingia kwenye Open Source imekuwa nzuri kwangu” Kuna sababu nyingi kwa nini mtu au shirika lingetaka kufungua chanzo cha mradi. Baadhi ya mifano ni pamoja na: Ushirikiano: Miradi ya open source inaweza kukubali mabadiliko kutoka kwa mtu yeyote duniani. Exercism , kwa mfano, ni jukwaa la mazoezi ya programu lenye washiriki zaidi ya 350. Kupitishwa na kubadilisha: Miradi ya open source inaweza kutumika na mtu yeyote kwa karibu kusudi lolote. Watu wanaweza hata kuitumia kujenga mambo mengine. WordPress , kwa mfano, ilianza kama fork ya mradi uliopo uitwao b2 . Uwazi: Mtu yeyote anaweza kukagua mradi wa open source kwa makosa au kutokuelewana. Uwazi ni muhimu kwa serikali kama Bulgaria au Marekani , sekta zilizo chini ya udhibiti kama benki au huduma za afya, na programu za usalama kama Let’s Encrypt . Open source si kwa programu tu, pia unaweza kufungua kila kitu kutoka kwa seti za data hadi vitabu. Angalia GitHub Explore kwa mawazo kuhusu nini kingine unaweza kufungua. Je, open source inamaanisha “bila malipo”? Moja ya mvuto mkubwa wa open source ni kwamba haigharimu pesa. “Bila malipo”, hata hivyo, ni matokeo ya thamani ya jumla ya open source. Kwa sababu leseni ya open source inahitaji kwamba mtu yeyote anaweza kutumia, kubadilisha, na kushiriki mradi wako kwa karibu kusudi lolote, miradi yenyewe huwa bila malipo. Ikiwa mradi ungegharimu pesa kutumika, mtu yeyote angeweza kisheria kufanya nakala na kutumia toleo la bure badala yake. Kwa hivyo, miradi mingi ya open source ni bure, lakini “bila malipo” si sehemu ya ufafanuzi wa open source. Kuna njia za kuchaji kwa miradi ya open source kwa njia zisizo za moja kwa moja kupitia leseni mbili au vipengele vilivyopunguzwa, huku bado ukikidhi ufafanuzi rasmi wa open source. Je, ni lazima nizindue mradi wangu wa open source? Jibu fupi ni ndiyo, kwa sababu bila kujali matokeo, kuzindua mradi wako ni njia nzuri ya kujifunza jinsi open source inavyofanya kazi. Ikiwa hujawahi kufungua mradi hapo awali, huenda ukawa na wasiwasi kuhusu kile watu watasema, au ikiwa mtu yeyote atagundua hata kidogo. Ikiwa hii inasikika kama wewe, huenda usiwe peke yako! Kazi ya open source ni kama shughuli nyingine yoyote ya ubunifu, iwe ni uandishi au uchoraji. Inaweza kuonekana kutisha kushiriki kazi yako na ulimwengu, lakini njia pekee ya kuboresha ni kufanya mazoezi - hata kama huna hadhira. Ikiwa bado hujashawishika, chukua muda kufikiria kuhusu malengo yako yanaweza kuwa yapi. Kuweka malengo yako Malengo yanaweza kukusaidia kubaini ni nini cha kufanya, ni nini cha kukatalia, na ni wapi unahitaji msaada kutoka kwa wengine. Anza kwa kujuliza, kwa nini ninafungua mradi huu? Hakuna jibu moja sahihi kwa swali hili. Unaweza kuwa na malengo mengi kwa mradi mmoja, au miradi tofauti yenye malengo tofauti. Ikiwa lengo lako pekee ni kuonyesha kazi yako, huenda usitake hata michango, na hata kusema hivyo katika README yako. Kwa upande mwingine, ikiwa unataka wachangiaji, utawekeza muda katika nyaraka wazi na kuwafanya wapya wajisikie kukaribishwa. Katika hatua fulani nilitengeneza UIAlertView maalum ambayo nilikuwa nikitumia…na nikaamua kuifanya open source. Hivyo, niliifanyia marakebisho na kuiweka kwenye GitHub. Pia nilandika nyaraka zangu za kwanza zikielezea kwa waendelezaji wengine jinsi ya kuitumia kwenye miradi yao. Huenda hakuna mtu aliyewahi kuitumia kwa sababu ilikuwa mradi mdogo lakini nilihisi vizuri kuhusu mchango wangu. — @mavris, “Wanaendelezaji wa Programu Wanaojifunza: Kwa Nini Open Source ni muhimu kwetu” Kadri mradi wako unavyokua, jamii yako inaweza kuhitaji zaidi ya msimbo kutoka kwako. Kujibu masuala, kupitia msimbo, na kuhamasisha mradi wako ni kazi muhimu katika mradi wa open source. Wakati kiasi cha muda unachotumia kwenye kazi zisizo za kuandika kitategemea ukubwa na upeo wa mradi wako, unapaswa kuwa tayari kama mtunza mradi kukabiliana nazo mwenyewe au kupata mtu wa kukusaidia. Ikiwa wewe ni sehemu ya kampuni inayofungua mradi, hakikisha mradi wako una rasilimali za ndani zinazohitajika ili kustawi. Utataka kubaini ni nani anayehusika na kutunza mradi baada ya uzinduzi, na jinsi utakavyoshiriki kazi hizo na jamii yako. Ikiwa unahitaji bajeti maalum au wafanyakazi kwa ajili ya matangazo, operesheni na kutunza mradi, anza mazungumzo hayo mapema. Unapokuwa unafungua mradi, ni muhimu kuhakikisha kwamba michakato yako ya utunzaji inazingatia michango na uwezo wa jamii inayozunguka mradi wako. Usijali kuhusisha wachangiaji ambao hawana ajira katika biashara yako katika nyanja muhimu za mradi - hasa ikiwa ni wachangiaji wa mara kwa mara. — @captainsafia, “Hivyo unataka kufungua mradi, eh?” Kuchangia miradi mingine Ikiwa lengo lako ni kujifunza jinsi ya kushirikiana na wengine au kuelewa jinsi open source inavyofanya kazi, zingatia kuchangia kwenye mradi uliopo. Anza na mradi ambao tayari unautumia na kuupenda. Kuchangia kwenye mradi kunaweza kuwa rahisi kama kurekebisha makosa ya tahajia au kuboresha nyaraka. Ikiwa hujui jinsi ya kuanza kama mchango, angalia mwongozo wetu wa Jinsi ya Kuchangia kwa Open Source . Kuzindua mradi wako wa open source Hakuna wakati mzuri wa kufungua chanzo cha kazi yako. Unaweza kufungua wazo, kazi inayoendelea, au baada ya miaka ya kuwa closed source. Kwa ujumla, unapaswa kufungua mradi wako unapojisikia vizuri kuwa na wengine wanaweza kuangalia, na kutoa maoni kuhusu, kazi yako. Bila kujali hatua gani unachagua kufungua mradi wako, kila mradi unapaswa kujumuisha nyaraka zifuatazo: Leseni ya open source README Miongozo ya kuchangia Kanuni ya tabia Kama mtunza mradi, vipengele hivi vitakusaidia kuwasiliana matarajio, kusimamia michango, na kulinda haki za kisheria za kila mtu (ikiwemo yako mwenyewe). Vinapanua sana nafasi zako za kuwa na uzoefu mzuri. Ikiwa mradi wako uko kwenye GitHub, kuweka faili hizi kwenye saraka yako ya mizizi kwa majina yaliyopendekezwa kutasaidia GitHub kutambua na kuziwasilisha moja kwa moja kwa wasomaji wako. Kuchagua leseni Leseni ya open source inahakikisha kwamba wengine wanaweza kutumia, nakala, kubadilisha, na kuchangia tena kwenye mradi wako bila madhara. Pia inakulinda kutokana na hali ngumu za kisheria. Lazima ujumuisha leseni unapozindua mradi wa open source. Kazi ya kisheria si ya kufurahisha. Habari njema ni kwamba unaweza kunakili na kupaste leseni iliyopo kwenye hazina yako. Itachukua dakika moja kulinda kazi yako ngumu. MIT , Apache 2.0 , na GPLv3 ni leseni maarufu zaidi za open source, lakini kuna chaguzi nyingine za kuchagua. Unapounda mradi mpya kwenye GitHub, unapata chaguo la kuchagua leseni. Kuweka leseni ya open source kutafanya mradi wako wa GitHub kuwa open source. Ikiwa una maswali au wasiwasi mengine kuhusu nyanja za kisheria za kusimamia mradi wa open source, tumeandaa mwongozo kwa ajili yako. Kuandika README READMEs hufanya zaidi ya kuelezea jinsi ya kutumia mradi wako. Pia zinaelezea kwa nini mradi wako ni muhimu, na ni nini watumiaji wako wanaweza kufanya nacho. Katika README yako, jaribu kujibu maswali yafuatayo: Mradi huu unafanya nini? Kwa nini mradi huu ni muhimu? Nitaanzaje? Nitaweza kupata msaada zaidi wapi, ikiwa nahitaji? Unaweza kutumia README yako kujibu maswali mengine, kama vile jinsi unavyoshughulikia michango, ni malengo gani ya mradi, na taarifa kuhusu leseni na kutambua. Ikiwa hutaki kukubali michango, au mradi wako haujawa tayari kwa uzalishaji, andika taarifa hii chini. Nyaraka bora zinamaanisha watumiaji wengi, maombi machache ya msaada, na wachangiaji wengi. (…) Kumbuka kwamba wasomaji wako si wewe. Kuna watu ambao wanaweza kuja kwenye mradi ambao wana uzoefu tofauti kabisa. — @tracymakes, “Kuandika Ili Maneno Yako Yasomwe (video)” Wakati mwingine, watu wanakwepa kuandika README kwa sababu wanahisi mradi haujakamilika, au hawataki michango. Hizi ni sababu nzuri za kuandika moja. Kwa maelezo zaidi, jaribu kutumia mwongozo wa @dguo “Fanya README” au templat ya README ya @PurpleBooth kuandika README kamili. Unapojumuisha faili ya README kwenye saraka ya mizizi, GitHub itaonyesha moja kwa moja kwenye ukurasa wa nyumbani wa hazina. Wakati mwingine, watu huepuka kuandika README kwa sababu wanahisi kama mradi haujakamilika, au hawataki michango. Hizi zote ni sababu nzuri sana za kuandika moja. Kwa msukumo zaidi, jaribu kutumia mwongozo wa @dguo “Tengeneza README” au @PurpleBooth’s README template kuandika SOMA kamili. Unapojumuisha faili ya README kwenye saraka ya mizizi, GitHub itaionyesha kiotomatiki kwenye ukurasa wa nyumbani wa hazina. Kuandika miongozo yako ya kuchangia Faili ya CONTRIBUTING inawaambia wasomaji wako jinsi ya kushiriki katika mradi wako. Kwa mfano, unaweza kujumuisha taarifa kuhusu: Jinsi ya kuwasilisha ripoti za makosa (jaribu kutumia mifano ya masuala na ombi la kuvuta ) Jinsi ya kupendekeza kipengele kipya Jinsi ya kuweka mazingira yako na kuendesha majaribio Mbali na maelezo ya kiufundi, faili ya CONTRIBUTING ni fursa ya kuwasilisha matarajio yako kwa michango, kama vile: Aina za michango unazotafuta Ramani yako au maono ya mradi Jinsi wachangiaji wanavyopaswa (au wasipasa) kuwasiliana nawe Kutumia sauti ya kirafiki na ya kukaribisha na kutoa mapendekezo maalum ya michango (kama vile kuandika nyaraka, au kutengeneza tovuti) kunaweza kusaidia sana katika kuwafanya wapya wajisikie kukaribishwa na kufurahia kushiriki. Kwa mfano, Active Admin huanza miongozo yake ya kuchangia na: Kwanza kabisa, asante kwa kuzingatia kuchangia kwa Active Admin. Ni watu kama wewe wanaofanya Active Admin kuwa chombo bora. Katika hatua za awali za mradi wako, faili yako ya CONTRIBUTING inaweza kuwa rahisi. Unapaswa kila wakati kuelezea jinsi ya kuripoti makosa au kuwasilisha masuala, na mahitaji yoyote ya kiufundi (kama majaribio) ili kufanya mchango. Kadri muda unavyosonga, unaweza kuongeza maswali mengine yanayoulizwa mara kwa mara kwenye faili yako ya CONTRIBUTING. Kuandika habari hii kuna maana kwamba watu wachache watauliza maswali sawa mara kwa mara. Kwa msaada zaidi wa kuandika faili yako ya CONTRIBUTING, angalia mwongozo wa @nayafia template ya kuchangia au “Jinsi ya Kujenga CONTRIBUTING.md” ya @mozilla . Linki kwa faili yako ya CONTRIBUTING kutoka kwenye README yako, ili watu wengi zaidi waione. Ikiwa uweka faili ya CONTRIBUTING kwenye hazina ya mradi wako , GitHub itaunganisha moja kwa moja kwenye faili yako wakati mchangiaji anaunda suala au kufungua ombi la kuvuta. Kuanzisha kanuni ya tabia Tumekuwa na uzoefu ambapo tulikabiliwa na kile ambacho labda kilikuwa unyanyasaji ama kama mtunza mradi akijaribu kueleza kwa nini kitu kinapaswa kuwa njia fulani, au kama mtumiaji…akiuliza swali rahisi. (…) Kanuni ya tabia inakuwa hati inayoweza kurejelea na kuunganishwa ambayo inaonyesha kwamba timu yako inachukulia mazungumzo ya kujenga kwa uzito. — @mlynch, “Kufanya Open Source Kuwa Mahali Pazuri” Hatimaye, kanuni ya tabia husaidia kuweka sheria za msingi za tabia kwa washiriki wa mradi wako. Hii ni muhimu hasa ikiwa unazindua mradi wa open source kwa jamii au kampuni. Kanuni ya tabia inakupa uwezo wa kuwezesha tabia nzuri na ya kujenga katika jamii, ambayo itapunguza msongo wako kama mtunza mradi. Kwa maelezo zaidi, angalia mwongozo wetu wa Kanuni ya Tabia . Mbali na kuwasilisha jinsi unavyotarajia washiriki watende, kanuni ya tabia pia huwa inaelezea ni nani matarajio haya yanatumika, wakati yanatumika, na nini cha kufanya ikiwa ukiukaji unafanyika. Kama leseni za open source, pia kuna viwango vinavyotokea kwa kanuni za tabia, hivyo huna haja ya kuandika yako mwenyewe. Mkataba wa Wachangiaji ni kanuni ya tabia inayoweza kutumika ambayo inatumika na mradi zaidi ya 40,000 wa open source , ikiwa ni pamoja na Kubernetes, Rails, na Swift. Haijalishi ni maandiko gani unayotumia, unapaswa kuwa tayari kutekeleza kanuni yako ya tabia inapohitajika. Pachika maandiko moja kwa moja kwenye faili ya CODE_OF_CONDUCT kwenye hazina yako. Hifadhi faili hiyo kwenye saraka ya mradi wako ili iwe rahisi kuipata, na uunganishe nayo kutoka kwenye README yako. Kutoa jina na kuchapisha ya mradi wako kuchapisha ni zaidi ya nembo ya kuvutia au jina la mradi linalokumbukwa. Ni kuhusu jinsi unavyoongea kuhusu mradi wako, na ni nani unayefikia na ujumbe wako. Kuchagua jina sahihi Chagua jina ambalo ni rahisi kukumbuka na, kwa kawaida, linatoa wazo kuhusu mradi unavyofanya. Kwa mfano: Sentry inafuatilia programu kwa ripoti za ajali Thin ni seva ya wavuti ya Ruby yenye haraka na rahisi Ikiwa unajenga juu ya mradi uliopo, kutumia jina lao kama kiambatisho kunaweza kusaidia kufafanua kile mradi wako unachofanya (kwa mfano, node-fetch inaletee window.fetch Node.js). Fikiria wazi zaidi kuliko yote. Mifano ni ya kufurahisha, lakini kumbuka kwamba baadhi ya vichekesho huenda visitafsiriwe kwa tamaduni nyingine au watu wenye uzoefu tofauti na wewe. Baadhi ya watumiaji wako wanaweza kuwa wafanyakazi wa kampuni: hutaki kuwafanya wajisikie wasumbufu wanapohitajika kuelezea mradi wako kazini! Kuepuka migongano ya majina Angalia miradi ya open source yenye jina sawa , hasa ikiwa unashiriki lugha ya programu au mfumo sawa. Ikiwa jina lako linagongana na mradi maarufu uliopo, unaweza kuchanganya hadhira yako. Ikiwa unataka tovuti, jina la Twitter, au mali nyingine za kuwakilisha mradi wako, hakikisha unaweza kupata majina unayotaka. Kwa kawaida, hifadhi majina hayo sasa kwa amani ya akili, hata kama hujapanga kuyatumia bado. Hakikisha jina la mradi wako halikiuka alama za biashara. Kampuni inaweza kukutaka uondoe mradi wako baadaye, au hata kuchukua hatua za kisheria dhidi yako. Si thamani ya hatari hiyo. Unaweza kuangalia WIPO Global Brand Database kwa migongano ya alama za biashara. Ikiwa uko kwenye kampuni, hii ni moja ya mambo ambayo timu yako ya kisheria inaweza kukusaidia nayo . Hatimaye, fanya utafutaji wa haraka wa jina la mradi wako. Je, watu wataweza kuipata mradi wako kwa urahisi? Je, kuna kitu kingine kinachotokea kwenye matokeo ya utafutaji ambacho huenda hutaki watu waone? Jinsi unavyandika (na kuandika msimbo) inavyoathiri chapa yako pia! Katika maisha ya mradi wako, utakuwa na maandiko mengi: READMEs, mafunzo, nyaraka za jamii, kujibu masuala, labda hata jarida na orodha za barua. Iwe ni nyaraka rasmi au barua ya kawaida, mtindo wako wa uandishi ni sehemu ya chapa ya mradi wako. Fikiria jinsi unavyoweza kuonekana kwa hadhira yako na ikiwa hiyo ndiyo sauti unayotaka kuwasilisha. Nilijaribu kujihusisha na kila mjadala kwenye orodha ya barua, na kuonyesha tabia bora, kuwa na wema kwa watu, kuchukua masuala yao kwa uzito na kujaribu kuwa msaada kwa ujumla. Baada ya muda, watu walibaki si tu kuuliza maswali, bali pia kusaidia na majibu, na kwa furaha yangu kamili, walinakili mtindo wangu. — @janl kwenye CouchDB , “Sustainable Open Source” Kutumia lugha ya kukaribisha (kama “them”, hata wakati ukirejelea mtu mmoja) kunaweza kusaidia sana katika kufanya mradi wako ujisikie unakaribisha kwa wachangiaji wapya. Kaa na lugha rahisi, kwani wengi wa wasomaji wako huenda si wazawa wa lugha ya Kiingereza. Zaidi ya jinsi unavyandika maneno, mtindo wako wa kuandika msimbo pia unaweza kuwa sehemu ya chapa ya mradi wako. Angular na jQuery ni mifano miwili ya miradi yenye mitindo na miongozo ya kuandika. Sio lazima kuandika mwongozo wa mtindo kwa mradi wako unapokuwa unaanza, na unaweza kupata kwamba unafurahia kuunganisha mitindo tofauti ya kuandika msimbo katika mradi wako. Lakini unapaswa kutarajia jinsi mtindo wako wa uandishi na wa kuandika msimbo unaweza kuvutia au kukatisha tamaa aina tofauti za watu. Hatua za awali za mradi wako ni fursa yako ya kuweka mfano unayotaka kuona. Orodha yako ya ukaguzi kabla ya uzinduzi Je, uko tayari kuweka mradi wako open source? Hapa kuna orodha ya ukaguzi ili kusaidia. Je, umekagua masanduku yote? Uko tayari kwenda! Bonyeza “chapisha” na ujipatie sifa. Nyaraka Mradi una faili ya LESENI yenye leseni ya open source Mradi una nyaraka za msingi (README, CONTRIBUTING, CODE_OF_CONDUCT) Jina ni rahisi kukumbuka, linatoa wazo fulani kuhusu kile mradi unafanya, na haligongani na mradi uliopo au kukiuka alama za biashara Orodha ya masuala iko katika hali ya juu, na masuala yameandaliwa na kuwekwa alama wazi Msimbo Mradi unatumia kanuni za msimbo zinazofanana na wazi ya function/method/variable names Msimbo umeandikwa kwa uwazi, ukielezea nia na hali za ukomo Hakuna vifaa nyeti katika historia ya marekebisho, masuala, au ombi la kuvuta (kwa mfano, nywila au taarifa nyingine zisizo za umma) Watu Ikiwa wewe ni mtu binafsi: Umezungumza na idara ya kisheria na/au kuelewa sera za IP na open source za kampuni yako (ikiwa wewe ni mfanyakazi mahali fulani) Ikiwa wewe ni kampuni au shirika: Umezungumza na idara yako ya kisheria Una mpango wa masoko wa kutangaza na kukuza mradi Mtu mmoja amejiandikisha kusimamia mwingiliano wa jamii (kujibu masuala, kupitia na kuunganisha ombi la kuvuta) Angalau watu wawili wana ufikiaji wa utunzaji wa mradi Umefanya! Hongera kwa kuanzisha mradi wako wa kwanza wa open source. Bila kujali matokeo, kufanya kazi hadharani ni zawadi kwa jamii. Kwa kila commit, maoni, na ombi la kuvuta, unaunda fursa kwako mwenyewe na kwa wengine kujifunza na kukua. Rudi kwa miongozo yote Miongozo inayohusiana Kupata Watumiaji kwa Mradi Wako Saidia mradi wako wa open source kukua kwa kuufikisha kwa watumiaji wenye furaha. Kujenga Jamii za Kukaribisha Kujenga jamii inayohamasisha watu kutumia, kuchangia, na kuhubiri mradi wako. Scroll to Top Changia Je, ungependa kutoa pendekezo? Maudhui haya ni open source. Tusaidie kuiboresha. Changia Endeleza kuwasiliana Kuwa wa kwanza kusikia kuhusu vidokezo na nyenzo huria za software za hivi punde zaidi za GitHub Barua Pepe fine print kwa na na marafiki | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/btsgroup-virtualization-platform/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | BTS Sybelle Virtualization Platform | LinkedIn Skip to main content LinkedIn BTS Group in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in BTS Sybelle Virtualization Platform Server Virtualization Software by BTS Group See who's skilled in this Add as skill Learn more Report this product About BTS Sybelle Virtualization Platform is a system virtualization platform that optimizes the management of virtualization infrastructure for organizations of all sizes. With high availability, scalability, advanced networking, and flexible storage capabilities at its core, it delivers reliable, enterprise-grade performance tailored to modern IT environments. Media Products media viewer No more previous content BTS Sybelle Virtualization Platform No more next content Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less BTS Group products BTS Olympos Automation Platform BTS Olympos Automation Platform Cloud Management Platforms (CMP) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://opensource.guide/fr/how-to-contribute/ | Comment contribuer à l’Open Source | Open Source Guides A propos Contribuer العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Comment contribuer à l'Open Source Vous voulez contribuer à l'Open Source ? Un guide pour faire des contributions Open Source, pour les débutants et pour les vétérans. Table des matières Pourquoi contribuer à l’open source Que signifie contribuer S’orienter vers un nouveau projet Trouver un projet auquel contribuer Comment proposer une contribution Que se passe-t-il après avoir proposé une contribution Pourquoi contribuer à l’open source Travailler sur [freenode] m’a aidé à acquérir plusieurs des compétences que j’ai utilisées plus tard pour mes études à l’université et mon travail actuel. Je pense que travailler sur des projets open source m’aide autant que ça aide le projet ! — @errietta, “Why I love contributing to open source software” Contribuer à l’open source peut être une manière enrichissante d’apprendre, d’enseigner et de construire une expérience dans presque toutes les compétences que vous pouvez imaginer. Pourquoi les gens contribuent-ils à l’open source ? Beaucoup de raisons ! Améliorer les compétences existantes Que ce soit le codage, la conception de l’interface utilisateur, la conception graphique, la rédaction ou l’organisation, si vous cherchez de la pratique, il y a une tâche pour vous sur un projet open source. Rencontrez des gens qui s’intéressent à des choses similaires Les projets Open Source avec des communautés chaleureuses et accueillantes font que les gens reviennent pendant des années. Beaucoup de gens forment des amitiés à vie grâce à leur participation à l’open source, que ce soit dans le cadre de conférences ou de bavardages en ligne tard dans la nuit sur les burritos. Trouver des mentors et enseigner aux autres Travailler avec d’autres sur un projet partagé signifie que vous devrez expliquer comment vous faites les choses, ainsi que de demander de l’aide à d’autres personnes. Les actes d’apprentissage et d’enseignement peuvent être une activité enrichissante pour tous ceux qui sont impliqués. Construire des artefacts publics qui vous aident à acquérir une réputation (et une carrière) Par définition, tout votre travail open source est public, ce qui signifie que vous obtenez des exemples gratuits à emporter pour démontrer ce que vous pouvez faire. Apprendre les compétences des personnes L’Open Source offre des opportunités de pratiquer des compétences de leadership et de gestion, telles que la résolution de conflits, l’organisation d’équipes de personnes et la hiérarchisation du travail. Cela permet de faire des changements, même les plus petits Vous n’avez pas besoin de devenir un contributeur permanent pour profiter de la participation à l’open source. Avez-vous déjà vu une faute de frappe sur un site Web et souhaité que quelqu’un la corrige ? Sur un projet open source, vous pouvez le faire. L’Open Source aide les gens à se sentir interpellés par leur vie et leur expérience du monde, ce qui est en soi gratifiant. Que signifie contribuer Si vous êtes un nouveau contributeur open source, le processus peut être intimidant. Comment trouvez-vous le bon projet ? Que faire si vous ne savez pas coder ? Et si quelque chose ne va pas ? Ne pas s’inquiéter ! Il y a toutes sortes de façons de s’impliquer dans un projet open source, et quelques conseils vous aideront à tirer le meilleur parti de votre expérience. Vous n’avez pas à contribuer au code Une idée commune fausse sur la contribution à l’open source est que vous devez contribuer au code. En fait, ce sont souvent les autres parties d’un projet qui sont le plus négligées ou négligées . Vous allez faire une faveur au projet en offrant de participer à ces types de contributions ! Je suis renommé pour mon travail sur CocoaPods, mais la plupart des gens ne savent pas que je ne travaille pas vraiment sur l’outil CocoaPods lui-même. Mon temps sur le projet est principalement passé à faire des choses comme la documentation et à travailler sur l’image de marque. — @orta, “Moving to OSS by default” Même si vous aimez écrire du code, d’autres types de contributions sont un excellent moyen de s’impliquer dans un projet et de rencontrer d’autres membres de la communauté. Construire ces relations vous donnera l’opportunité de travailler sur d’autres parties du projet. Aimez-vous la planification d’événements ? Organiser des ateliers ou des meetups sur le projet, comme @fzamperin a fait pour NodeSchool Organiser la conférence du projet (s’ils en ont une) Aider les membres de la communauté à trouver les bonnes conférences et soumettre des propositions de talk Aimez-vous créer ? Restructurer les mises en page pour améliorer la convivialité du projet Effectuer des recherches utilisateur pour réorganiser et affiner la navigation ou les menus du projet, comme suggère Drupal Mettre en place un guide de style pour aider le projet à avoir un design visuel cohérent Créer de l’art pour des t-shirts ou un nouveau logo, comme les contributeurs de hapi.js l’ont fait Aimez-vous écrire ? Écrire et améliorer la documentation du projet Curate un dossier d’exemples montrant comment le projet est utilisé Démarrer un bulletin d’information pour le projet, ou organiser des faits marquants de la liste de diffusion Rédiger des tutoriels pour le projet, comme les contributeurs de PyPA l’ont fait Écrire une traduction pour la documentation du projet Sérieusement, [documentation] est méga-important. La documentation à ce jour a été excellente et a été une caractéristique de Babel. Il y a des sections qui pourraient certainement utiliser un peu de travail et même l’ajout d’un paragraphe ici ou là est extrêmement apprécié. — @kittens, “Call for contributors” Aimez-vous l’organisation ? Lien vers des questions en double, et suggérer de nouveaux labels pour les issues, pour garder les choses organisées Passer en revue les problèmes ouverts et suggérer de fermer les anciens, comme @nzakas a fait pour ESLint Posez des questions de clarification sur les issues récemment ouvertes pour faire avancer la discussion Aimez-vous le code ? Trouver un problème ouvert à aborder, comme @dianjin a fait pour Leaflet Demandez si vous pouvez aider à écrire une nouvelle fonctionnalité Automatiser la configuration du projet Améliorer l’outillage et les tests Aimez-vous aider les gens ? Répondez aux questions sur le projet sur, par exemple, Stack Overflow ( comme cet exemple Postgres ) ou Reddit Répondre aux questions pour les personnes sur les questions ouvertes Aider à modérer les forums de discussion ou les canaux de conversation Aimez-vous aider les autres ? Réviser le code sur les soumissions d’autres personnes Écrire des tutoriels sur la façon dont un projet peut être utilisé Proposer de parrainer un autre contributeur, comme @ereichert l’a fait pour @bronzdoc sur Rust Il ne suffit pas de travailler sur des projets logiciels ! Alors que “open source” se réfère souvent à un logiciel, vous pouvez collaborer sur à peu près n’importe quoi. Il existe des livres, des recettes, des listes et des classes qui sont développés en tant que projets open source. Par exemple: @sindresorhus gère une liste de listes “géniales” @h5bp tient à jour une liste des questions potentielles lors d’entretiens pour les candidats développeurs @stuartlynn et @nicole-a-tesla ont fait une collection de faits amusants sur les macareux Même si vous êtes un développeur de logiciels, travailler sur un projet de documentation peut vous aider à démarrer en open source. Il est souvent moins intimidant de travailler sur des projets qui n’impliquent pas de code, et le processus de collaboration renforcera votre confiance et votre expérience. S’orienter vers un nouveau projet Si vous allez sur un issue tracker et les choses semblent confuses, ce n’est pas seulement vous. Ces outils nécessitent beaucoup de connaissances implicites, mais les gens peuvent vous aider à les parcourir et vous pouvez leur poser des questions. — @shaunagm, “How to Contribute to Open Source” Pour tout ce qui n’est pas une faute de frappe, contribuer à l’open source, c’est comme aller à un groupe d’étrangers lors d’une fête. Si vous commencez à parler des lamas, alors qu’ils étaient plongés dans une discussion sur les poissons rouges, ils vous regarderont probablement un peu étrangement. Avant de sauter à l’aveuglette avec vos propres suggestions, commencez par apprendre à lire la pièce. Cela augmente les chances que vos idées soient remarquées et entendues. Anatomie d’un projet open source Chaque communauté open source est différente. Passer des années sur un projet open source signifie que vous avez appris à connaître un projet open source. Déplacez-vous vers un projet différent, et vous pourriez trouver le vocabulaire, les normes et les styles de communication complètement différents. Cela dit, de nombreux projets open source suivent une structure organisationnelle similaire. Comprendre les différents rôles de la communauté et le processus global vous aidera à vous orienter rapidement vers tout nouveau projet. Un projet Open Source typique comprend les types de personnes suivants: Auteur : La personne / l’organisation qui a créé le projet Propriétaire : La ou les personnes qui ont la propriété administrative de l’organisation ou du repository (pas toujours les mêmes que l’auteur original) Responsables : Collaborateurs responsables de la vision et de la gestion des aspects organisationnels du projet. (Ils peuvent aussi être auteurs ou propriétaires du projet.) Contributeurs : Tous ceux qui ont contribué au projet. Membres de la communauté : Les personnes qui utilisent le projet. Ils peuvent être actifs dans les conversations ou exprimer leur opinion sur la direction du projet. Les plus grands projets peuvent également avoir des sous-comités ou des groupes de travail axés sur différentes tâches, telles que l’outillage, le triage, la modération communautaire et l’organisation d’événements. Regardez sur le site Web d’un projet pour une page «équipe», ou dans le repository pour la documentation de gouvernance, pour trouver cette information. Un projet a également une documentation. Ces fichiers sont généralement répertoriés à la racine d’un repository. LICENCE : Par définition, chaque projet open source doit avoir une licence open source . Si le projet n’a pas de licence, il n’est pas open source. README : Le README est le manuel d’instructions qui accueille les nouveaux membres de la communauté au projet. Cela explique pourquoi le projet est utile et comment démarrer. CONTRIBUTING : Alors que les fichiers README aident les gens à utiliser le projet, les documents de contribution aident les gens à contribuer au projet. Il explique quels types de contributions sont nécessaires et comment le processus fonctionne. Bien que tous les projets n’aient pas de fichier CONTRIBUTING, sa présence indique qu’il s’agit d’un projet accueillant auquel contribuer. CODE_OF_CONDUCT : Le code de conduite établit des règles de base pour le comportement des participants et contribue à faciliter un environnement amical et accueillant. Bien que tous les projets n’aient pas de fichier CODE_OF_CONDUCT, sa présence indique qu’il s’agit d’un projet accueillant auquel contribuer. Autre documentation : Il pourrait y avoir de la documentation supplémentaire, comme des tutoriels, des procédures pas à pas, ou des politiques de gouvernance, en particulier sur des projets plus importants. Enfin, les projets open source utilisent les outils suivants pour organiser la discussion. La lecture des archives vous donnera une bonne idée de la façon dont la communauté pense et travaille. Suivi des issues : Lorsque les gens discutent des issues liés au projet. Pull Requests : Où les gens discutent et examinent les changements en cours. Forums de discussion ou listes de diffusion : Certains projets peuvent utiliser ces canaux pour des sujets conversationnels (par exemple, “Comment puis-je…“ ou “Que pensez-vous de…“ au lieu d’un rapport de bug ou demandes de fonctionnalités). D’autres utilisent le suivi des issues pour toutes les conversations. Canal de discussion synchrone : Certains projets utilisent des canaux de discussion (tels que Slack ou IRC) pour des conversations informelles, la collaboration et des échanges rapides. Trouver un projet auquel contribuer Maintenant que vous avez compris comment fonctionnent les projets open source, il est temps de trouver un projet auquel contribuer ! Si vous n’avez jamais contribué à l’open source auparavant, prenez quelques conseils du président américain John F. Kennedy, qui a dit: “Ne demandez pas ce que votre pays peut faire pour vous - demandez ce que vous pouvez faire pour votre pays.” Contribuer à l’open source se produit à tous les niveaux, à travers les projets. Vous n’avez pas besoin de trop réfléchir sur ce que sera exactement votre première contribution ou sur ce à quoi elle ressemblera. Au lieu de cela, commencez par penser aux projets que vous utilisez déjà ou que vous voulez utiliser. Les projets auxquels vous contribuez activement sont ceux auxquels vous revenez. Dans ces projets, chaque fois que vous pensez que quelque chose pourrait être meilleur ou différent, agissez selon votre instinct. L’open source n’est pas un club exclusif. C’est fait par des gens comme vous. “Open source” est juste un terme de fantaisie pour traiter les problèmes du monde comme réparable. Vous pouvez scanner un fichier README et trouver un lien cassé ou une faute de frappe. Ou vous êtes un nouvel utilisateur et vous avez remarqué que quelque chose est cassé, ou un problème que vous pensez devrait vraiment être dans la documentation. Au lieu de l’ignorer et de passer à autre chose, ou de demander à quelqu’un d’autre de le réparer, voyez si vous pouvez aider en faisant un descriptif du problème. C’est cela l’open source ! 28% des contributions occasionnelles à l’open source sont de la documentation, une correction de faute de frappe, un reformatage ou l’écriture d’une traduction. Vous pouvez également utiliser l’une des ressources suivantes pour vous aider à découvrir et à contribuer à de nouveaux projets : GitHub Explore Open Source Friday First Timers Only CodeTriage 24 Pull Requests Up For Grabs First Contributions SourceSort OpenSauced Une checklist avant de contribuer Lorsque vous avez trouvé un projet auquel vous souhaitez contribuer, effectuez une analyse rapide pour vous assurer que le projet est adapté à l’acceptation des contributions. Sinon, votre travail acharné pourrait ne jamais avoir de réponse. Voici une liste de contrôle pratique pour évaluer si un projet est bon pour les nouveaux contributeurs. Répondre à la définition de l’open source A-t-il une licence ? Généralement, il s'agit d'un fichier appelé LICENSE à la racine du repository. Le projet accepte activement les contributions Regardez l’activité des commits sur la branche principale. Sur GitHub, vous pouvez voir cette information sur la page d’accueil d’un repository. À quand remonte le dernier commit ? Combien de contributeurs le projet a-t-il ? À quelle fréquence les gens commits ? (Sur GitHub, vous pouvez le trouver en cliquant sur "Commits" dans la barre du haut.) Ensuite, regardez les issues du projet. Combien d'issues sont ouvertes? Les responsables répondent-ils rapidement aux issues lorsqu'elles sont ouvertes ? Y a-t-il une discussion active sur les issues ? Les issues sont-elles récentes ? Les issues sont-elles fermées ? (Sur GitHub, cliquez sur l'onglet "closed" de la page issue pour voir les issues résolues.) Faites la même chose pour les pull requests du projet. Combien de pull requests sont ouvertes ? Les responsables répondent-ils rapidement aux pull requests lorsqu'elles sont ouvertes ? Y a-t-il une discussion active sur les pull requests ? Les pull requests sont récentes ? Dans quelle mesure les pull requests ont-elles été mergées récemment ? (Sur GitHub, cliquez sur l'onglet "Closed" de la page Pull Requests pour voir les PR fermés.) Le projet est accueillant Un projet convivial et accueillant signale qu’il sera réceptif aux nouveaux contributeurs. Les responsables répondent-ils utilement aux questions dans les issues ? Les gens sont-ils amicaux dans les issues, le forum de discussion et le chat (par exemple, IRC ou Slack)? Est-ce que les pull request ont bien une review ? Les responsables remercient-ils les gens pour leurs contributions ? Chaque fois que vous voyez un long fil de discussion, vérifiez les réponses des principaux développeurs arrivant tard dans le fil. Résument-ils de façon constructive la discussion pour prendre une décision tout en restant polis ? Si vous voyez beaucoup de flame wars , c’est souvent un signe que l’énergie est dépensée en dispute plutôt qu’en développements. — @kfogel, Producing OSS Comment proposer une contribution Vous avez trouvé un projet que vous aimez et vous êtes prêt à apporter votre contribution. Enfin ! Voici comment obtenir votre contribution de la bonne façon. Communiquer efficacement Que vous soyez un contributeur ponctuel ou que vous essayiez de rejoindre une communauté, travailler avec les autres est l’une des compétences les plus importantes que vous développerez dans l’open source. [En tant que nouveau contributeur,] je me suis rapidement rendu compte que je devais poser des questions si je voulais pouvoir fermer une issue. J’ai parcouru la code base. Une fois que j’ai eu une idée de ce qui se passait, j’ai demandé plus de pistes. Et voilà! J’ai été capable de résoudre le problème après avoir obtenu tous les détails pertinents dont j’avais besoin. — @shubheksha, A Beginner’s Very Bumpy Journey Through The World of Open Source Avant d’ouvrir une issue ou une pull request, ou de poser une question dans une discussion, gardez ces points à l’esprit pour que vos idées soient bien comprises. Donner le contexte. Aider les autres à se mettre rapidement à jour. Si vous rencontrez une erreur, expliquez ce que vous essayez de faire et comment le reproduire. Si vous suggérez une nouvelle idée, expliquez pourquoi vous pensez que ce serait utile pour le projet (pas seulement pour vous !). 😇 “X n’arrive pas quand je fais Y” 😢 “X est cassé ! Veuillez le réparer.” Faites vos devoirs à l’avance. C’est OK de ne pas savoir des choses, mais montrez que vous avez essayé. Avant de demander de l’aide, assurez-vous de consulter le fichier README, la documentation, les issues (ouvertes ou fermées), la liste de diffusion et la recherche sur Internet pour obtenir une réponse. Les gens apprécieront quand vous démontrerez que vous essayez d’apprendre. 😇 “Je ne sais pas comment implémenter X. J’ai vérifié les documents d’aide et je n’ai trouvé aucune mention.” 😢 “Comment puis-je X ?” Gardez les demandes courtes et directes. Tout comme pour l’envoi d’un courriel, chaque contribution, aussi simple ou utile soit-elle, nécessite l’avis de quelqu’un d’autre. De nombreux projets ont plus de demandes entrantes que de personnes disponibles pour aider. Soyez concis. Vous augmenterez les chances que quelqu’un puisse vous aider. 😇 “J’aimerais écrire un tutoriel sur l’API.” 😢 “Je roulais sur l’autoroute l’autre jour et je me suis arrêté pour faire le plein d’essence, et puis j’ai eu cette idée incroyable pour quelque chose que nous devrions faire, mais avant que j’explique cela, laissez-moi vous montrer…“ Gardez toute communication publique. Bien que cela soit tentant, ne communiquez pas avec les responsables en privé à moins que vous ayez besoin de partager des informations sensibles (comme un problème de sécurité ou une violation grave de la conduite). Lorsque vous maintenez la conversation publique, plus de personnes peuvent apprendre et bénéficier de votre échange. Les discussions peuvent être, en elles-mêmes, des contributions. 😇 (comme un commentaire) “@-mainainer Salut ! Comment devrions-nous procéder sur cette PR ?” 😢 (comme un e-mail) “Hello, désolé de vous déranger par e-mail, mais je me demandais si vous aviez eu l’occasion de revoir mes pull requests ?” Il est acceptable de poser des questions (mais soyez patient!). Tout le monde était nouveau au projet à un moment donné, et même les contributeurs expérimentés ont besoin de se mettre à jour quand ils regardent un nouveau projet. De même, même les responsables de longue date ne sont pas toujours familiers avec chaque partie du projet. Montrez-leur la même patience que vous voudriez qu’ils vous montrent. 😇 “Merci d’avoir examiné cette erreur, j’ai suivi vos suggestions, voici la sortie.” 😢 “Pourquoi ne voulez-vous pas résoudre mon problème, n’est-ce pas votre projet ?” Respectez les décisions de la communauté. Vos idées peuvent différer des priorités ou de la vision de la communauté. Ils peuvent offrir des commentaires ou décider de ne pas poursuivre votre idée. Alors que vous devriez discuter et chercher des compromis, les responsables doivent vivre avec votre décision plus longtemps que vous ne le ferez. Si vous n’êtes pas d’accord avec leur direction, vous pouvez toujours travailler sur votre propre fork ou démarrer votre propre projet. 😇 “Je suis déçu que vous ne puissiez pas supporter mon cas d’utilisation, mais comme vous l’avez expliqué, cela ne concerne qu’une partie mineure des utilisateurs, je comprends pourquoi.” 😢 “Pourquoi ne soutenez-vous pas mon cas d’utilisation ? C’est inacceptable !” Surtout, gardez-le classique. L’open source est composé de collaborateurs du monde entier. Le contexte se perd dans les langues, les cultures, les zones géographiques et les fuseaux horaires. De plus, la communication écrite rend plus difficile la transmission d’un ton ou d’une humeur. Supposer de bonnes intentions dans ces conversations. Il est bon de repousser poliment une idée, de demander plus de contexte ou de clarifier davantage votre position. Juste essayer de laisser l’Internet un meilleur endroit que lorsque vous l’avez trouvé. Rassembler le contexte Avant de faire quoi que ce soit, faites une vérification rapide pour vous assurer que votre idée n’a pas été discutée ailleurs. Parcourez le fichier README du projet, les issues (ouvertes et fermées), la liste de diffusion et Stack Overflow. Vous n’avez pas à passer des heures à tout faire, mais une recherche rapide de quelques termes clés va aider. Si vous ne trouvez pas votre idée ailleurs, vous êtes prêt à faire un geste. Si le projet est sur GitHub, vous communiquerez probablement en ouvrant une issue ou une pull request : Les issues sont comme démarrer une conversation ou une discussion Les Pull Request sont pour commencer à travailler sur une solution Pour une communication légère, comme une question de clarification ou de procédure, essayez de demander sur Stack Overflow, IRC, Slack ou d’autres canaux de discussion, si le projet en a un. Avant d’ouvrir une issue ou une pull request, vérifiez les documents de contribution du projet (généralement un fichier appelé CONTRIBUTING, ou dans le fichier README), pour voir si vous devez inclure quelque chose de spécifique. Par exemple, ils peuvent vous demander de suivre un modèle ou d’exiger que vous utilisiez des tests. Si vous voulez apporter une contribution substantielle, ouvrez une issue pour demander avant de travailler dessus. Il est utile de regarder le projet pendant un moment (sur GitHub, vous pouvez cliquer sur “Watch” pour être averti de toutes les conversations), et arriver à connaître les membres de la communauté, avant de faire un travail qui pourrait ne pas être accepté. Vous apprendrez beaucoup à prendre un seul projet que vous utilisez activement, à le «regarder» sur GitHub et à lire toutes les issues et PR. — @gaearon on joining projects Ouvrir une issue Vous devrez généralement ouvrir une issue dans les situations suivantes: Signaler une erreur que vous ne pouvez pas résoudre vous-même Discuter d’un sujet ou d’une idée de haut niveau (par exemple, communauté, vision ou politiques) Proposer une nouvelle fonctionnalité ou une autre idée de projet Conseils pour communiquer sur les problèmes: Si vous voyez un problème ouvert auquel vous voulez vous attaquer, commentez le problème pour faire savoir aux autres que vous travaillez dessus. De cette façon, les gens seront moins susceptibles de dupliquer votre travail. Si une issue a été ouverte il y a un certain temps, il est possible qu’elle soit adressée ailleurs ou qu’elle ait déjà été résolue, alors commentez pour demander une confirmation avant de commencer le travail. Si vous avez ouvert une issue, mais que vous avez trouvé la réponse plus tard, commentez l’issue pour informer les gens, puis fermez-la. Même documenter ce résultat est une contribution au projet. Ouvrir une Pull Request Vous devrez généralement ouvrir une pull request dans les situations suivantes : Soumettre des corrections triviales (par exemple, une faute de frappe, un lien cassé ou une erreur évidente) Commencer à travailler sur une contribution qui a déjà été demandée, ou dont vous avez déjà discuté, dans une issue Une pull request n’a pas à représenter le travail fini. Il est généralement préférable d’ouvrir une pull request au début afin que les autres puissent regarder ou donner leur avis sur vos progrès. Il suffit de marquer “WIP” (Work in Progress) dans la ligne d’objet. Vous pouvez toujours ajouter plus de commits plus tard. Si le projet est sur GitHub, voici comment soumettre une pull request: Forker le repository et clonez-le localement. Connectez votre repository local au repository original “upstream” en l’ajoutant en tant que remote. Pullez souvent des changements de “upstream” de sorte que vous restiez à jour afin que lorsque vous soumettez votre pull request, les conflits de merge seront moins probables. (Voir plus d’instructions détaillées ici .) Créer une branche pour vos modifications. Faites référence à toutes les questions pertinentes ou aux éléments de documentations dans votre PR (par exemple, «Close #37»). Inclure des captures d’écran avant et après si vos modifications incluent des différences en HTML/CSS. Faites glisser et déposez les images dans le corps de votre pull request. Testez vos modifications ! Exécutez vos modifications par rapport aux tests existants s’ils existent et créez-en de nouveaux si nécessaire. Que les tests existent ou non, assurez-vous que vos modifications ne cassent pas le projet existant. Contribuer dans le style du projet au mieux de vos capacités. Cela peut signifier utiliser des indentations, des points-virgules ou des commentaires différemment de ce que vous feriez dans votre propre repository, mais il est plus facile pour le mainteneur de fusionner, d’autres à comprendre et à maintenir dans le futur. S’il s’agit de votre première Pull Request, consultez Make a Pull Request , que @kentcdodds a créé comme didacticiel vidéo. Vous pouvez également vous entraîner à faire une pull request dans le repository Premières contributions , créé par @Roshanjossey. Que se passe-t-il après avoir proposé une contribution Vous l’avez fait ! Félicitations pour devenir un contributeur open source. Nous espérons que c’est le premier de plusieurs. Après avoir soumis une contribution, l’un des événements suivants se produira: 😭 Vous n’obtenez pas de réponse. J’espère que vous avez vérifié les signes d’activité dans le projet avant de faire une contribution. Même sur un projet actif, il est possible que votre contribution n’obtienne pas de réponse. Si vous n’avez pas reçu de réponse depuis plus d’une semaine, il est juste de répondre poliment dans ce même fil, en demandant à quelqu’un de donner son avis. Si vous connaissez le nom de la bonne personne à consulter votre contribution, vous pouvez @-mentionner dans ce fil. Ne pas tendre la main à cette personne en privé. Rappelez-vous que la communication publique est vitale pour les projets open source. Si vous faites une contribution et que personne ne répond, il est possible que personne ne réponde, jamais. Ce n’est pas génial, mais ne vous laissez pas décourager. C’est arrivé à tout le monde ! Il y a plusieurs raisons possibles pour lesquelles vous n’avez pas reçu de réponse, y compris des circonstances personnelles qui peuvent être hors de votre contrôle. Essayez de trouver un autre projet ou un moyen de contribuer. Si c’est le cas, c’est une bonne raison de ne pas consacrer trop de temps à faire une contribution avant que les autres membres de la communauté soient engagés et réceptifs. 🚧 Quelqu’un demande des modifications à votre contribution. Il est courant que l’on vous demande d’apporter des modifications à votre contribution, qu’il s’agisse de commentaires sur la portée de votre idée ou de modifications apportées à votre code. Quand quelqu’un demande des changements, soyez flexible. Ils ont pris le temps d’examiner votre contribution. Ouvrir une PR et passer à autre chose est une mauvaise idée. Si vous ne savez pas comment faire des changements, recherchez le problème, puis demandez de l’aide si vous en avez besoin. Si vous n’avez plus le temps de travailler sur le problème (par exemple, si la conversation dure depuis des mois et que votre situation a changé), informez le responsable pour qu’il n’attende pas de réponse. Quelqu’un d’autre peut être heureux de prendre le relais. 👎 Votre contribution ne sera pas acceptée. Votre contribution peut ou pas être acceptée à la fin. J’espère que vous n’y avez pas déjà mis trop de travail. Si vous ne savez pas pourquoi cela n’a pas été accepté, il est tout à fait raisonnable de demander des commentaires et des éclaircissements au responsable. En fin de compte, cependant, vous devrez respecter que c’est leur décision. Ne discutez pas et ne soyez pas hostile. Vous êtes toujours le bienvenu pour forker et travailler sur votre propre version si vous n’êtes pas d’accord ! 🎉 Votre contribution est acceptée. Hourra! Vous avez réussi à faire une contribution open source! Vous l’avez fait! Que vous veniez de faire votre première contribution open source, ou que vous cherchiez de nouvelles façons de contribuer, nous espérons que vous êtes inspirés à agir. Même si votre contribution n’a pas été acceptée, n’oubliez pas de dire merci quand un responsable a fait des efforts pour vous aider. L’open source est créé par des personnes comme vous: une issue, une pull request, un commentaire ou une salutation à la fois. Retour à tous les guides Guides liés Lancer un projet Open Source En savoir plus sur le monde de l’Open Source et préparez-vous à lancer votre propre projet. Construire des communautés accueillantes Construire une communauté qui encourage les gens à utiliser, contribuer et évangéliser votre projet. Scroll to Top Contribuer Vous souhaitez faire une suggestion ? Ce contenu est libre. Aidez-nous à l'améliorer. Contribuer Restons en contact Soyez le premier à découvrir les dernières astuces et ressources concernant les logiciels libres avec GitHub. Adresse email fine print avec par et amis | 2026-01-13T09:29:15 |
https://www.eff.org/node/90198 | Hacking the Patent System (2016) | Electronic Frontier Foundation Skip to main content About Contact Press People Opportunities EFF's 35th Anniversary Issues Free Speech Privacy Creativity and Innovation Transparency International Security Our Work Deeplinks Blog Press Releases Events Legal Cases Whitepapers Podcast Annual Reports Take Action Action Center Electronic Frontier Alliance Volunteer Tools Privacy Badger Surveillance Self-Defense Certbot Atlas of Surveillance Cover Your Tracks Street Level Surveillance apkeep Donate Donate to EFF Giving Societies Shop Sponsorships Other Ways to Give Membership FAQ Donate Donate to EFF Shop Other Ways to Give Email updates on news, actions, and events in your area. Join EFF Lists Copyright (CC BY) Trademark Privacy Policy Thanks Electronic Frontier Foundation Donate EFFecting Change: The Human Cost of Online Age Verification on January 15 Electronic Frontier Foundation About Contact Press People Opportunities EFF's 35th Anniversary Issues Free Speech Privacy Creativity and Innovation Transparency International Security Our Work Deeplinks Blog Press Releases Events Legal Cases Whitepapers Podcast Annual Reports Take Action Action Center Electronic Frontier Alliance Volunteer Tools Privacy Badger Surveillance Self-Defense Certbot Atlas of Surveillance Cover Your Tracks Street Level Surveillance apkeep Donate Donate to EFF Giving Societies Shop Sponsorships Other Ways to Give Membership FAQ Donate Donate to EFF Shop Other Ways to Give Hacking the Patent System (2016) DOCUMENT Hacking the Patent System (2016) A guide to alternative patent licensing produced by the Juelsgaard Intellectual Property & Innovation Clinic at Stanford Law School in partnership with EFF and Engine . Revised and expanded for 2016. https://www.eff.org/files/2016/01/26/hacking_the_patent_system_belcher_and_casey_updated_january_2016.pdf hacking_the_patent_system_belcher_and_casey_updated_january_2016.pdf Related Issues Fair Use Patents Creativity & Innovation Back to top Follow EFF: mastodon facebook instagram x Blue Sky youtube flicker linkedin tiktok threads Check out our 4-star rating on Charity Navigator . Contact General Legal Security Membership Press About Calendar Volunteer Victories History Internships Jobs Staff Diversity & Inclusion Issues Free Speech Privacy Creativity & Innovation Transparency International Security Updates Blog Press Releases Events Legal Cases Whitepapers EFFector Newsletter Press Press Contact Donate Join or Renew Membership Online One-Time Donation Online Giving Societies Corporate Giving and Sponsorship Shop Other Ways to Give Copyright (CC BY) Trademark Privacy Policy Thanks JavaScript license information | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/btsgroup-virtualization-platform/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | BTS Sybelle Virtualization Platform | LinkedIn Skip to main content LinkedIn BTS Group in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in BTS Sybelle Virtualization Platform Server Virtualization Software by BTS Group See who's skilled in this Add as skill Learn more Report this product About BTS Sybelle Virtualization Platform is a system virtualization platform that optimizes the management of virtualization infrastructure for organizations of all sizes. With high availability, scalability, advanced networking, and flexible storage capabilities at its core, it delivers reliable, enterprise-grade performance tailored to modern IT environments. Media Products media viewer No more previous content BTS Sybelle Virtualization Platform No more next content Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less BTS Group products BTS Olympos Automation Platform BTS Olympos Automation Platform Cloud Management Platforms (CMP) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/kaltura-video-platform?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Kaltura AI Video Experience Cloud | LinkedIn Skip to main content LinkedIn Kaltura in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Kaltura AI Video Experience Cloud Live Streaming Software by Kaltura See who's skilled in this Add as skill Learn more Report this product About Driving virtual events, communication, learning, and TV experiences for millions of users daily. Similar products Cloudflare Stream Cloudflare Stream Live Streaming Software Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Tango Tango Live Streaming Software BOCC BOCC Live Streaming Software Media Services Live Media Services Live Live Streaming Software Liveu Liveu Live Streaming Software Sign in to see more Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/categories/server-virtualization-software?trk=products_details_guest_other_products_by_org_section_product_link_result-card_subtitle-click#main-content | Best Server Virtualization Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Information Technology Manager (7) Director of Information Technology (5) System Administrator (5) Virtualization Engineer (2) Information Technology Project Manager (2) See all products Find top products in Server Virtualization Software category Software used to emulate computer systems by partitioning resources from physical hosts. - Use hypervisors to run multiple virtual machines from a single physical server - Run platform-independent environments with optimized resource distribution - Consolidate server usage with shared memory and processing - Control independent instances of guest operating systems 40 results Cloudflare Workers Server Virtualization Software by Cloudflare Build your next application with Cloudflare Workers View product Cloud Virtual Machine (CVM) Server Virtualization Software by Tencent Tencent Cloud Virtual Machine offers stable, secure, resilient, and high-performance cloud computing service View product Proxmox Virtual Environment Server Virtualization Software by Proxmox Server Solutions Proxmox Virtual Environment (Proxmox VE) is is the leading open-source platform for all-inclusive enterprise virtualization. With the central web interface, you can easily run VMs and containers, manage software-defined storage and networking functionality, high-availability clustering, and multiple integrated out-of-the-box tools like backup/restore, live migration, replication, and the firewall. Enterprises use the powerful all-in-one solution to meet the core requirements of today’s modern data centers. View product SC//Fleet Manager Server Virtualization Software by Scale Computing We combined servers, storage, and virtualization into a single solution to make IT infrastructure easier for organizations of every size. Whether you have one IT administrator or hundreds, our award winning hyperconverged infrastructure eliminates complexity, lowers costs, and frees up management time. Using an appliance-based approach to virtualization, our Scale Computing Platform infrastructure solution is faster to deploy, easier to manage, and allows you to scale seamlessly as your organization grows. Even in an emergency with the failure of hardware components or entire appliances, Scale Computing infrastructure lets you keep critical apps – and your entire organization – up and running. View product SC//Platform Server Virtualization Software by Scale Computing With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. The award winning Scale Computing brings on-premises edge computing with high availability and disaster recovery to remote locations at an affordable entry level cost. All edge appliances can be deployed quickly, managed locally or remotely, and can self-heal almost instantly. Enjoy affordable edge computing infrastructure that is reliable, easy to deploy, and easy to use. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights BTS Sybelle Virtualization Platform Server Virtualization Software by BTS Group BTS Sybelle Virtualization Platform is a system virtualization platform that optimizes the management of virtualization infrastructure for organizations of all sizes. With high availability, scalability, advanced networking, and flexible storage capabilities at its core, it delivers reliable, enterprise-grade performance tailored to modern IT environments. View product Oracle Virtualization Server Virtualization Software by Oracle Linux Backed by affordable enterprise support for hybrid environments, Oracle Virtualization reduces operation and support costs while increasing IT efficiency and agility—on premises and in the cloud. View product StarWind SAN & NAS Server Virtualization Software by StarWind Inc. StarWind SAN & NAS is a ready-to-go Linux-based virtual machine (VM) that allows you to repurpose existing hypervisor servers into shared storage. Leveraging the power of ZFS, Linux, and StarWind SDS, the solution can transform your hypervisor servers into HCL-certified high-performance storage appliance, shared storage, or backup target. Just deploy it on top of your hypervisor and you’re good to go. View product StarWind NVMe-oF Initiator Server Virtualization Software by StarWind Inc. StarWind NVMe-oF Initiator is the only software solution on the market that brings NVMe-oF connectivity over TCP and RoCE v2 networks to performance-demanding Windows applications. It’s certified with Windows and makes NVMe-oF available for SQL and M&E workloads without the need for fibre channel, rNICs on every host, or wait for a Windows-native solution to get released and mature. View product ZStack ZSphere Server Virtualization Server Virtualization Software by ZStack International ZStack ZSphere offers a VMware vSphere‑like user experience, ready to use without additional training. It scales from 1 to 1,000 servers per cluster and includes a three‑month free trial with full features and unlimited server deployment. Key Features and Capabilities: Compatibility & Reuse: Works with multi‑architecture CPUs and multi‑brand servers, protecting existing investments. SAN Storage Support: Integrates with proprietary storage for specific SLA scenarios. AI‑Ready: Supports GPU passthrough and vGPU for AI and high‑compute workloads. Cross‑Version Hot Upgrade: Maintains business continuity during system upgrades. High Performance: SR‑IOV delivers near bare‑metal networking for demanding I/O, with VM storage performance up to millions of IOPS. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/categories/server-virtualization-software?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_subtitle-click | Best Server Virtualization Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Information Technology Manager (7) Director of Information Technology (5) System Administrator (5) Virtualization Engineer (2) Information Technology Project Manager (2) See all products Find top products in Server Virtualization Software category Software used to emulate computer systems by partitioning resources from physical hosts. - Use hypervisors to run multiple virtual machines from a single physical server - Run platform-independent environments with optimized resource distribution - Consolidate server usage with shared memory and processing - Control independent instances of guest operating systems 40 results Cloudflare Workers Server Virtualization Software by Cloudflare Build your next application with Cloudflare Workers View product Cloud Virtual Machine (CVM) Server Virtualization Software by Tencent Tencent Cloud Virtual Machine offers stable, secure, resilient, and high-performance cloud computing service View product Proxmox Virtual Environment Server Virtualization Software by Proxmox Server Solutions Proxmox Virtual Environment (Proxmox VE) is is the leading open-source platform for all-inclusive enterprise virtualization. With the central web interface, you can easily run VMs and containers, manage software-defined storage and networking functionality, high-availability clustering, and multiple integrated out-of-the-box tools like backup/restore, live migration, replication, and the firewall. Enterprises use the powerful all-in-one solution to meet the core requirements of today’s modern data centers. View product SC//Fleet Manager Server Virtualization Software by Scale Computing We combined servers, storage, and virtualization into a single solution to make IT infrastructure easier for organizations of every size. Whether you have one IT administrator or hundreds, our award winning hyperconverged infrastructure eliminates complexity, lowers costs, and frees up management time. Using an appliance-based approach to virtualization, our Scale Computing Platform infrastructure solution is faster to deploy, easier to manage, and allows you to scale seamlessly as your organization grows. Even in an emergency with the failure of hardware components or entire appliances, Scale Computing infrastructure lets you keep critical apps – and your entire organization – up and running. View product SC//Platform Server Virtualization Software by Scale Computing With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. The award winning Scale Computing brings on-premises edge computing with high availability and disaster recovery to remote locations at an affordable entry level cost. All edge appliances can be deployed quickly, managed locally or remotely, and can self-heal almost instantly. Enjoy affordable edge computing infrastructure that is reliable, easy to deploy, and easy to use. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights BTS Sybelle Virtualization Platform Server Virtualization Software by BTS Group BTS Sybelle Virtualization Platform is a system virtualization platform that optimizes the management of virtualization infrastructure for organizations of all sizes. With high availability, scalability, advanced networking, and flexible storage capabilities at its core, it delivers reliable, enterprise-grade performance tailored to modern IT environments. View product Oracle Virtualization Server Virtualization Software by Oracle Linux Backed by affordable enterprise support for hybrid environments, Oracle Virtualization reduces operation and support costs while increasing IT efficiency and agility—on premises and in the cloud. View product StarWind SAN & NAS Server Virtualization Software by StarWind Inc. StarWind SAN & NAS is a ready-to-go Linux-based virtual machine (VM) that allows you to repurpose existing hypervisor servers into shared storage. Leveraging the power of ZFS, Linux, and StarWind SDS, the solution can transform your hypervisor servers into HCL-certified high-performance storage appliance, shared storage, or backup target. Just deploy it on top of your hypervisor and you’re good to go. View product StarWind NVMe-oF Initiator Server Virtualization Software by StarWind Inc. StarWind NVMe-oF Initiator is the only software solution on the market that brings NVMe-oF connectivity over TCP and RoCE v2 networks to performance-demanding Windows applications. It’s certified with Windows and makes NVMe-oF available for SQL and M&E workloads without the need for fibre channel, rNICs on every host, or wait for a Windows-native solution to get released and mature. View product ZStack ZSphere Server Virtualization Server Virtualization Software by ZStack International ZStack ZSphere offers a VMware vSphere‑like user experience, ready to use without additional training. It scales from 1 to 1,000 servers per cluster and includes a three‑month free trial with full features and unlimited server deployment. Key Features and Capabilities: Compatibility & Reuse: Works with multi‑architecture CPUs and multi‑brand servers, protecting existing investments. SAN Storage Support: Integrates with proprietary storage for specific SLA scenarios. AI‑Ready: Supports GPU passthrough and vGPU for AI and high‑compute workloads. Cross‑Version Hot Upgrade: Maintains business continuity during system upgrades. High Performance: SR‑IOV delivers near bare‑metal networking for demanding I/O, with VM storage performance up to millions of IOPS. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fcloudflare&fromSignIn=true&trk=organization_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://opensource.guide/hi/leadership-and-governance/ | नेतृत्व और शासन | Open Source Guides बारे में योगदान करें العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides नेतृत्व और शासन निर्णय लेने के लिए औपचारिक नियमों से बढ़ते ओपन सोर्स प्रोजेक्ट्स को फायदा हो सकता है। सामग्री की सूची अपने बढ़ते प्रोजेक्ट के लिए प्रशासन को समझना ओपन सोर्स प्रोजेक्ट्स में उपयोग की जाने वाली औपचारिक भूमिकाओं के उदाहरण क्या हैं? मैं इन नेतृत्व भूमिकाओं को कैसे औपचारिक बनाऊं? मुझे किसी को प्रतिबद्ध पहुंच कब देनी चाहिए? ओपन सोर्स परियोजनाओं के लिए कुछ सामान्य शासन संरचनाएँ क्या हैं? क्या मुझे अपना प्रोजेक्ट लॉन्च करते समय शासन दस्तावेज़ों की आवश्यकता होगी? यदि कॉर्पोरेट कर्मचारी अंशदान जमा करना शुरू कर दें तो क्या होगा? अपने बढ़ते प्रोजेक्ट के लिए प्रशासन को समझना आपका प्रोजेक्ट बढ़ रहा है, लोग इसमें लगे हुए हैं और आप इस चीज़ को जारी रखने के लिए प्रतिबद्ध हैं। इस स्तर पर, आप सोच रहे होंगे कि नियमित परियोजना योगदानकर्ताओं को अपने वर्कफ़्लो में कैसे शामिल किया जाए, चाहे वह किसी को प्रतिबद्ध पहुंच प्रदान करना हो या सामुदायिक बहस को हल करना हो। यदि आपके कोई प्रश्न हैं, तो हमें उत्तर मिल गए हैं। ओपन सोर्स प्रोजेक्ट्स में उपयोग की जाने वाली औपचारिक भूमिकाओं के उदाहरण क्या हैं? कई परियोजनाएँ योगदानकर्ता भूमिकाओं और मान्यता के लिए समान संरचना का पालन करती हैं। हालाँकि, इन भूमिकाओं का वास्तव में क्या मतलब है, यह पूरी तरह आप पर निर्भर है। यहां कुछ प्रकार की भूमिकाएं दी गई हैं जिन्हें आप पहचान सकते हैं: रखरखाव योगदान देने वाला कमिटर कुछ परियोजनाओं के लिए, “रखरखावकर्ता” किसी परियोजना में प्रतिबद्ध पहुंच वाले एकमात्र लोग होते हैं। अन्य परियोजनाओं में, वे केवल वे लोग हैं जो रीडमी में अनुरक्षक के रूप में सूचीबद्ध हैं। एक अनुरक्षक आवश्यक रूप से ऐसा व्यक्ति नहीं है जो आपके प्रोजेक्ट के लिए कोड लिखता हो। यह कोई ऐसा व्यक्ति हो सकता है जिसने आपके प्रोजेक्ट को प्रचारित करने के लिए बहुत काम किया हो, या लिखित दस्तावेज़ीकरण किया हो जिसने प्रोजेक्ट को दूसरों के लिए अधिक सुलभ बना दिया हो। चाहे वे दिन-प्रतिदिन कुछ भी करें, एक अनुरक्षक संभवतः वह व्यक्ति होता है जो परियोजना की दिशा में ज़िम्मेदारी महसूस करता है और इसे सुधारने के लिए प्रतिबद्ध है। एक “योगदानकर्ता” कोई भी हो सकता है जो किसी मुद्दे या पुल अनुरोध पर टिप्पणी करता है, जो लोग परियोजना में मूल्य जोड़ते हैं (चाहे वह मुद्दों का परीक्षण करना हो, कोड लिखना हो, या घटनाओं का आयोजन करना हो), या मर्ज किए गए पुल अनुरोध वाला कोई भी व्यक्ति (शायद योगदानकर्ता की सबसे संकीर्ण परिभाषा।) [ Node.js के लिया,] प्रत्येक व्यक्ति जो किसी मुद्दे पर टिप्पणी करने या कोड सबमिट करने के लिए आता है, वह प्रोजेक्ट समुदाय का सदस्य होता है। बस उन्हें देखने में सक्षम होने का मतलब है कि उन्होंने उपयोगकर्ता से योगदानकर्ता बनने की सीमा पार कर ली है। — @mikeal, “Healthy Open Source” शब्द “कमिटर” का उपयोग कमिट एक्सेस, जो एक विशिष्ट प्रकार की जिम्मेदारी है, को योगदान के अन्य रूपों से अलग करने के लिए किया जा सकता है। हालाँकि आप अपनी परियोजना भूमिकाओं को अपनी इच्छानुसार किसी भी तरह परिभाषित कर सकते हैं, व्यापक परिभाषाओं का उपयोग करने पर विचार करें योगदान के और अधिक रूपों को प्रोत्साहित करना। आप उन लोगों को औपचारिक रूप से पहचानने के लिए नेतृत्व की भूमिकाओं का उपयोग कर सकते हैं जिन्होंने आपके प्रोजेक्ट में उत्कृष्ट योगदान दिया है, भले ही उनके तकनीकी कौशल कुछ भी हों। आप शायद मुझे Django के “आविष्कारक” के रूप में जानते होंगे…लेकिन वास्तव में मैं वह व्यक्ति हूं जिसे किसी चीज़ के बनने के एक साल बाद उस पर काम करने के लिए नियुक्त किया गया था। (…) लोगों को संदेह है कि मैं अपने प्रोग्रामिंग कौशल के कारण सफल हूं…लेकिन मैं अधिक से अधिक एक औसत प्रोग्रामर हूं। — @jacobian, “PyCon 2015 Keynote” (video) मैं इन नेतृत्व भूमिकाओं को कैसे औपचारिक बनाऊं? अपनी नेतृत्व भूमिकाओं को औपचारिक बनाने से लोगों को स्वामित्व महसूस करने में मदद मिलती है और समुदाय के अन्य सदस्यों को पता चलता है कि मदद के लिए किससे संपर्क करना चाहिए। एक छोटी परियोजना के लिए, नेताओं को नामित करना आपके README या CONTRIBUTORS टेक्स्ट फ़ाइल में उनके नाम जोड़ने जितना आसान हो सकता है। किसी बड़े प्रोजेक्ट के लिए, यदि आपके पास कोई वेबसाइट है, तो एक टीम पेज बनाएं या वहां अपने प्रोजेक्ट लीडरों की सूची बनाएं। उदाहरण के लिए, Postgres के पास एक comprehensive team page प्रत्येक योगदानकर्ता के लिए संक्षिप्त प्रोफ़ाइल के साथ। यदि आपके प्रोजेक्ट में बहुत सक्रिय योगदानकर्ता समुदाय है, तो आप अनुरक्षकों की एक “कोर टीम” बना सकते हैं, या ऐसे लोगों की उपसमितियां भी बना सकते हैं जो विभिन्न मुद्दे क्षेत्रों (उदाहरण के लिए, सुरक्षा, समस्या निवारण, या सामुदायिक आचरण) का स्वामित्व लेते हैं। लोगों को वे भूमिकाएँ सौंपने के बजाय स्वयं संगठित होने दें और उनके लिए स्वेच्छा से काम करने दें जिनके बारे में वे सबसे अधिक उत्साहित हैं। [हम] कई “उपटीमों” के साथ कोर टीम को पूरक करें। प्रत्येक उपटीम एक विशिष्ट क्षेत्र पर केंद्रित है, जैसे, भाषा डिज़ाइन या पुस्तकालय। (…) समग्र रूप से परियोजना के लिए वैश्विक समन्वय और एक मजबूत, सुसंगत दृष्टिकोण सुनिश्चित करने के लिए, प्रत्येक उपटीम का नेतृत्व कोर टीम के एक सदस्य द्वारा किया जाता है। — “Rust Governance RFC” नेतृत्व दल एक निर्दिष्ट चैनल बनाना चाह सकते हैं (जैसे आईआरसी पर) या परियोजना पर चर्चा करने के लिए नियमित रूप से मिलना चाहते हैं (जैसे गिटर या गूगल हैंगआउट पर)। आप उन बैठकों को सार्वजनिक भी कर सकते हैं ताकि अन्य लोग सुन सकें। Cucumber-ruby , उदाहरण के लिए, hosts office hours every week . एक बार जब आप नेतृत्व की भूमिकाएँ स्थापित कर लें, तो यह दस्तावेज करना न भूलें कि लोग उन्हें कैसे प्राप्त कर सकते हैं! कोई आपके प्रोजेक्ट में अनुरक्षक कैसे बन सकता है या उपसमिति में कैसे शामिल हो सकता है, इसके लिए एक स्पष्ट प्रक्रिया स्थापित करें और इसे अपने में लिखें GOVERNANCE.md. उपकरण जैसे Vossibility आपको सार्वजनिक रूप से ट्रैक करने में मदद मिल सकती है कि प्रोजेक्ट में कौन योगदान दे रहा है (या नहीं दे रहा है)। इस जानकारी का दस्तावेजीकरण करने से समुदाय की इस धारणा से बचा जा सकता है कि रखरखाव करने वाले एक समूह हैं जो निजी तौर पर अपने निर्णय लेते हैं। अंत में, यदि आपका प्रोजेक्ट GitHub पर है, तो अपने प्रोजेक्ट को अपने व्यक्तिगत खाते से किसी संगठन में ले जाने और कम से कम एक बैकअप व्यवस्थापक जोड़ने पर विचार करें। GitHub Organizations अनुमतियों और एकाधिक रिपॉजिटरी को प्रबंधित करना और अपने प्रोजेक्ट की विरासत को सुरक्षित रखना आसान बनाएं shared ownership . मुझे किसी को प्रतिबद्ध पहुंच कब देनी चाहिए? कुछ लोग सोचते हैं कि आपको योगदान देने वाले हर व्यक्ति को प्रतिबद्ध पहुंच देनी चाहिए। ऐसा करने से अधिक लोग आपके प्रोजेक्ट पर स्वामित्व महसूस करने के लिए प्रोत्साहित हो सकते हैं। दूसरी ओर, विशेष रूप से बड़ी, अधिक जटिल परियोजनाओं के लिए, आप केवल उन लोगों को प्रतिबद्ध पहुंच देना चाह सकते हैं जिन्होंने अपनी प्रतिबद्धता प्रदर्शित की है। इसे करने का कोई एक सही तरीका नहीं है - वही करें जो आपको सबसे अधिक आरामदायक लगे! यदि आपका प्रोजेक्ट GitHub पर है, तो आप इसका उपयोग कर सकते हैं protected branches यह प्रबंधित करना कि कौन किसी विशेष शाखा में जा सकता है, और किन परिस्थितियों में। जब भी कोई आपको पुल अनुरोध भेजता है, तो उन्हें अपने प्रोजेक्ट तक पहुंच प्रदान करें। हालाँकि यह पहली बार में अविश्वसनीय रूप से बेवकूफी भरा लग सकता है, इस रणनीति का उपयोग करने से आप GitHub की वास्तविक शक्ति को उजागर कर सकेंगे। (…) एक बार लोगों के पास प्रतिबद्ध पहुंच हो जाने के बाद, उन्हें चिंता नहीं रहती कि उनका पैच अलग हो सकता है…जिससे उन्हें इसमें और अधिक काम करना पड़ेगा। — @felixge, “The Pull Request Hack” ओपन सोर्स परियोजनाओं के लिए कुछ सामान्य शासन संरचनाएँ क्या हैं? ओपन सोर्स परियोजनाओं से जुड़ी तीन सामान्य शासन संरचनाएँ हैं। बीडीएफएल: बीडीएफएल का अर्थ है “जीवन के लिए परोपकारी तानाशाह”। इस संरचना के तहत, सभी प्रमुख परियोजना निर्णयों पर एक व्यक्ति (आमतौर पर परियोजना का प्रारंभिक लेखक) का अंतिम अधिकार होता है। Python एक उत्कृष्ट उदाहरण है. छोटी परियोजनाएँ संभवतः डिफ़ॉल्ट रूप से बीडीएफएल हैं, क्योंकि केवल एक या दो अनुरक्षक होते हैं। किसी कंपनी में शुरू हुआ प्रोजेक्ट भी बीडीएफएल श्रेणी में आ सकता है। मेरिटोक्रेसी: (नोट: शब्द “मेरिटोक्रेसी” कुछ समुदायों के लिए नकारात्मक अर्थ रखता है और इसका एक नकारात्मक प्रभाव है complex social and political history .) योग्यतातंत्र के तहत, सक्रिय परियोजना योगदानकर्ताओं (जो “योग्यता” प्रदर्शित करते हैं) को औपचारिक निर्णय लेने की भूमिका दी जाती है। निर्णय आम तौर पर शुद्ध मतदान सर्वसम्मति के आधार पर किए जाते हैं। योग्यतातंत्र की अवधारणा का सूत्रपात किसके द्वारा किया गया था? Apache Foundation ; all Apache projects योग्यतातंत्र हैं. योगदान केवल अपना प्रतिनिधित्व करने वाले व्यक्तियों द्वारा ही किया जा सकता है, किसी कंपनी द्वारा नहीं। उदार योगदान: उदार योगदान मॉडल के तहत, जो लोग सबसे अधिक काम करते हैं उन्हें सबसे प्रभावशाली माना जाता है, लेकिन यह वर्तमान कार्य पर आधारित है न कि ऐतिहासिक योगदान पर। प्रमुख परियोजना निर्णय शुद्ध वोट के बजाय सर्वसम्मति प्राप्त करने की प्रक्रिया (प्रमुख शिकायतों पर चर्चा) के आधार पर किए जाते हैं, और यथासंभव अधिक से अधिक सामुदायिक दृष्टिकोणों को शामिल करने का प्रयास किया जाता है। उदार योगदान मॉडल का उपयोग करने वाली परियोजनाओं के लोकप्रिय उदाहरणों में शामिल हैं Node.js और Rust . आपको किसका उपयोग करना चाहिए? यह आप पर निर्भर करता है! हर मॉडल के फायदे और फायदे हैं। और यद्यपि वे पहली बार में काफी भिन्न लग सकते हैं, तीनों मॉडलों में जितना वे दिखते हैं उससे कहीं अधिक समानता है। यदि आप इनमें से किसी एक मॉडल को अपनाने में रुचि रखते हैं, तो इन टेम्पलेट्स को देखें: BDFL model template Meritocracy model template Node.js’s liberal contribution policy क्या मुझे अपना प्रोजेक्ट लॉन्च करते समय शासन दस्तावेज़ों की आवश्यकता होगी? आपके प्रोजेक्ट के प्रशासन को लिखने का कोई सही समय नहीं है, लेकिन एक बार जब आप अपने समुदाय की गतिशीलता को देख लेंगे तो इसे परिभाषित करना बहुत आसान हो जाएगा। ओपन सोर्स गवर्नेंस के बारे में सबसे अच्छी (और सबसे कठिन) बात यह है कि इसे समुदाय द्वारा आकार दिया जाता है! हालाँकि, कुछ शुरुआती दस्तावेज़ अनिवार्य रूप से आपके प्रोजेक्ट के प्रशासन में योगदान देंगे, इसलिए आप जो कर सकते हैं उसे लिखना शुरू कर दें। उदाहरण के लिए, आप व्यवहार के लिए स्पष्ट अपेक्षाओं को परिभाषित कर सकते हैं, या आपके प्रोजेक्ट के लॉन्च पर भी आपकी योगदानकर्ता प्रक्रिया कैसे काम करती है। यदि आप एक ओपन सोर्स प्रोजेक्ट लॉन्च करने वाली कंपनी का हिस्सा हैं, तो लॉन्च से पहले इस बारे में आंतरिक चर्चा करना उचित है कि आपकी कंपनी प्रोजेक्ट को आगे बढ़ाने के बारे में कैसे बनाए रखने और निर्णय लेने की उम्मीद करती है। हो सकता है कि आप सार्वजनिक रूप से यह स्पष्ट करना चाहें कि आपकी कंपनी इस परियोजना में कैसे शामिल होगी (या नहीं करेगी!)। हम GitHub पर प्रोजेक्ट प्रबंधित करने के लिए छोटी टीमें नियुक्त करते हैं जो वास्तव में Facebook पर इन पर काम कर रही हैं। उदाहरण के लिए, रिएक्ट एक रिएक्ट इंजीनियर द्वारा चलाया जाता है। — @caabernathy, “An inside look at open source at Facebook” यदि कॉर्पोरेट कर्मचारी अंशदान जमा करना शुरू कर दें तो क्या होगा? सफल ओपन सोर्स परियोजनाओं का उपयोग कई लोगों और कंपनियों द्वारा किया जाता है, और कुछ कंपनियों के पास अंततः राजस्व धाराएं परियोजना से जुड़ी हो सकती हैं। उदाहरण के लिए, कोई कंपनी किसी वाणिज्यिक सेवा पेशकश में परियोजना के कोड को एक घटक के रूप में उपयोग कर सकती है। जैसे-जैसे परियोजना अधिक व्यापक रूप से उपयोग की जाती है, इसमें विशेषज्ञता रखने वाले लोगों की मांग अधिक हो जाती है - आप उनमें से एक हो सकते हैं! - और कभी-कभी उन्हें प्रोजेक्ट में किए गए काम के लिए भुगतान मिलेगा। व्यावसायिक गतिविधि को सामान्य और विकास ऊर्जा के एक अन्य स्रोत के रूप में मानना महत्वपूर्ण है। निःसंदेह, भुगतान किए गए डेवलपर्स को अवैतनिक डेवलपर्स की तुलना में विशेष व्यवहार नहीं मिलना चाहिए; प्रत्येक योगदान का मूल्यांकन उसकी तकनीकी खूबियों के आधार पर किया जाना चाहिए। हालाँकि, लोगों को व्यावसायिक गतिविधि में शामिल होने में सहज महसूस करना चाहिए, और किसी विशेष वृद्धि या सुविधा के पक्ष में बहस करते समय अपने उपयोग के मामलों को बताने में सहज महसूस करना चाहिए। “वाणिज्यिक” “ओपन सोर्स” के साथ पूरी तरह से संगत है। “वाणिज्यिक” का सीधा सा मतलब है कि इसमें कहीं न कहीं पैसा शामिल है - कि सॉफ्टवेयर का उपयोग वाणिज्य में किया जाता है, जो कि एक परियोजना के अपनाने के रूप में तेजी से संभव है। (जब ओपन सोर्स सॉफ़्टवेयर का उपयोग गैर-ओपन-सोर्स उत्पाद के हिस्से के रूप में किया जाता है, तो समग्र उत्पाद अभी भी “मालिकाना” सॉफ़्टवेयर होता है, हालांकि, ओपन सोर्स की तरह, इसका उपयोग वाणिज्यिक या गैर-व्यावसायिक उद्देश्यों के लिए किया जा सकता है।) किसी भी अन्य की तरह, व्यावसायिक रूप से प्रेरित डेवलपर्स अपने योगदान की गुणवत्ता और मात्रा के माध्यम से परियोजना में प्रभाव प्राप्त करते हैं। जाहिर है, एक डेवलपर जिसे उसके समय के लिए भुगतान किया जाता है, वह उस व्यक्ति से अधिक काम करने में सक्षम हो सकता है जिसे भुगतान नहीं किया जाता है, लेकिन यह ठीक है: भुगतान कई संभावित कारकों में से एक है जो किसी के काम को प्रभावित कर सकता है। अपनी परियोजना चर्चाओं को योगदानों पर केंद्रित रखें, न कि उन बाहरी कारकों पर जो लोगों को योगदान देने में सक्षम बनाते हैं। क्या मुझे अपने प्रोजेक्ट का समर्थन करने के लिए एक कानूनी इकाई की आवश्यकता है? जब तक आप पैसे का प्रबंधन नहीं कर रहे हों, आपको अपने ओपन सोर्स प्रोजेक्ट का समर्थन करने के लिए किसी कानूनी इकाई की आवश्यकता नहीं है। उदाहरण के लिए, यदि आप एक वाणिज्यिक व्यवसाय बनाना चाहते हैं, तो आप एक सी कॉर्प या एलएलसी स्थापित करना चाहेंगे (यदि आप अमेरिका में स्थित हैं)। यदि आप केवल अपने ओपन सोर्स प्रोजेक्ट से संबंधित अनुबंध कार्य कर रहे हैं, तो आप एकमात्र मालिक के रूप में धन स्वीकार कर सकते हैं, या एलएलसी स्थापित कर सकते हैं (यदि आप अमेरिका में स्थित हैं)। यदि आप अपने ओपन सोर्स प्रोजेक्ट के लिए दान स्वीकार करना चाहते हैं, तो आप एक दान बटन सेट कर सकते हैं (उदाहरण के लिए पेपैल या स्ट्राइप का उपयोग करके), लेकिन पैसा तब तक कर-कटौती योग्य नहीं होगा जब तक कि आप एक योग्य गैर-लाभकारी संस्था (501c3, यदि आप अमेरिका में हैं)। कई परियोजनाएँ एक गैर-लाभकारी संस्था स्थापित करने की परेशानी से गुज़रना नहीं चाहती हैं, इसलिए वे इसके बजाय एक गैर-लाभकारी राजकोषीय प्रायोजक ढूंढती हैं। एक राजकोषीय प्रायोजक आपकी ओर से दान स्वीकार करता है, आमतौर पर दान के एक प्रतिशत के बदले में। Software Freedom Conservancy , Apache Foundation , Eclipse Foundation , Linux Foundation ओर Open Collective ऐसे संगठनों के उदाहरण हैं जो ओपन सोर्स परियोजनाओं के लिए वित्तीय प्रायोजक के रूप में काम करते हैं। हमारा लक्ष्य एक ऐसा बुनियादी ढाँचा प्रदान करना है जिसका उपयोग समुदाय स्वयं टिकाऊ होने के लिए कर सकें, इस प्रकार एक ऐसा वातावरण तैयार करना है जहाँ सभी — योगदानकर्ताओं, समर्थकों, प्रायोजकों — को इससे ठोस लाभ मिले। — @piamancini, “दान ढांचे से आगे बढ़ना” यदि आपका प्रोजेक्ट किसी निश्चित भाषा या पारिस्थितिकी तंत्र से निकटता से जुड़ा हुआ है, तो एक संबंधित सॉफ़्टवेयर फ़ाउंडेशन भी हो सकता है जिसके साथ आप काम कर सकते हैं। उदाहरण के लिए, Python Software Foundation मदद करता है PyPI , पायथन पैकेज मैनेजर का, और Node.js Foundation मदद करता है Express.js का, एक नोड-आधारित ढांचा। सभी मार्गदर्शिकाओं पर वापस जाएं संबंधित मार्गदर्शिकाएं मेंटेनर्स के लिए सर्वोत्तम प्रैक्टिस आपके जीवन को आसान बनाने के तरीके, संग्रहणिक प्रक्रियाओं से लेकर आपकी समुदाय का उपयोग करने तक, एक ओपन सोर्स मेंटेनर के रूप में। ओपन सोर्स मेट्रिक्स अपने ओपन सोर्स प्रोजेक्ट की सफलता को मापने और ट्रैक करके उसे फलने-फूलने में मदद करने के लिए सोच-समझकर निर्णय लें। Scroll to Top योगदान करें क्या आपका कोई सुझाव है? यह सामग्री ओपन सोर्स है। हमें इसे सुधारने में मदद करें। योगदान करें संपर्क में रहें गिटहब की नवीनतम ओपन सोर्स युक्तियों और संसाधनों की पहली जानकारी पाने के लिए पहले ही सुनें। ईमेल पता fine print के साथ द्वारा और मित्र | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Ftencentglobal-tencent-cloud-lighthouse%3FviewConnections%3Dtrue&trk=products_details_guest_face-pile-cta | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://opensource.guide/ja/how-to-contribute/ | オープンソースにコントリビュートする方法 | Open Source Guides このサイトについて 貢献する العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides オープンソースにコントリビュートする方法 オープンソースにコントリビュートしたいですか？このガイドではオープンソースへのコントリビュートの方法を、初めての人だけでなく熟練の方にも紹介します。 目次 オープンソースにコントリビュートする理由は？ コントリビュートするということが意味するもの 新しいプロジェクトに順応しよう コントリビュートするプロジェクトを見つけよう コントリビュートする方法 コントリビュートを提出した後に起こること オープンソースにコントリビュートする理由は？ [freenode] で働くことで、その後の大学での勉強や実際の仕事をする上で役に立つたくさんのスキルを身につけることができました。オープンソースプロジェクトにコントリビュートすることは、プロジェクトを前進させると共に私自身への助けにもなりました！ — @errietta, “Why I love contributing to open source software” オープンソースにコントリビュートすることはやりがいがあり、あなたが思い描くどんなスキルに対しても、学習し、教え、経験を積むことができます。 なぜ人々はオープンソースにコントリビュートするのでしょう？理由は様々です！ 既に持っているスキルを改善する あなたが練習したいと思っていることが、コーディングであれ、UIデザインやグラフィックデザイン、文章を書くこと、組織を作ることであれ、オープンソースプロジェクトにはあなたのためのタスクがあります。 似たようなことに興味を持っている人に会う 暖かく迎えてくれるコミュニティを持ったオープンソースプロジェクトでは、人々が何年経っても戻って来続けます。多くの人がオープンソースに参加することによって生涯に渡る友好関係を築いています。たとえそれがカンファレンスでばったり会うという形であったり、夜遅くにブリトーについてチャットをしているという形であれ。 メンターを見つけ互いに教えあう 同じプロジェクトで他の人と一緒に働くということは、あなたが仕事をやる方法を説明するだけでなく、他の人に助けを求める必要が出てきます。学習し、教えることは関わる人全てにとって充実した活動となります。 あなたの評判（やキャリア）を育てるのに役立つ成果物を作り上げる その定義からして、すべてのオープンソースはパブリックです。このことはあなたがやっていることをどこでも自由に紹介できる事例を得られるということを意味します。 ピープルスキルを学ぶ オープンソースは、人々の衝突を解消したり、チームを組織したり、仕事の優先順位付けをするなどといったリーダーシップやマネジメントスキルを実践する機会を提供してくれます。 変化を起こせるようになる助けとなる、たとえそれが小さな変化であったとしても あなたは何もオープンソースに生涯に渡って常に参加し続ける必要があるわけではありません。ウェブサイトでタイポを見つけて、直してほしいと思ったことはありませんか？オープンソースプロジェクトでは、あなたがそれをできるのです。オープンソースによって、人々は人生や世界をどう経験するかが自分自身のものだと感じられることを助けてくれます。そしてその事自体が大きな喜びとなるのです。 コントリビュートするということが意味するもの オープンソースコントリビューターになりたてで自信が持てないと感じているかもしれません。どのようにして正しいプロジェクトを見つけるのでしょう？もしコーディングの仕方を知らないとしたらどうでしょう？もし何かが間違ってしまったらどうしましょう？ 心配ありません！オープンソースプロジェクトに関わるにはあらゆる方法があります。そして、少しのコツがあればあなたの経験を最大限活かす事ができるでしょう。 かならずしもコードを書く必要はありません オープンソースへのコントリビュートについてのよくある勘違いとしては、あなたはコードを書く必要があるというものです。実際、それはしばしばプロジェクトの中で最も 無視されるか見落とされている部分 です。この種のコントリビュートを行うことによってプロジェクトに対して 非常に大きな 助けとなります。 私は CocoaPods での仕事で有名になってきましたが、多くの人は私が CocoaPods 自体に対する仕事をほとんどしていないということを知らないのです。このプロジェクトでの私の時間はほとんどがドキュメントを書いたり、ブランディングのしごとをすることに費やされているのです。 — @orta, “Moving to OSS by default” たとえコードを書くことが好きであったとしても、他の種類のコントリビュートはプロジェクトに関わり、他のコミュニティメンバーに会う良いやり方です。このような関係を作ることはそのプロジェクトの他の部分に関わる人と仕事をする機会を与えてくれます。 イベントを計画するのが好きですか？ @fzamperin が NodeSchool でやったように ワークショップやミートアップを開催する (もしあるなら)プロジェクトのカンファレンスを企画する コミュニティメンバーが発表するのにちょうどよいカンファレンスを見つけるのを手伝う デザインをするのが好きですか？ プロジェクトのユーザビリティを向上させるためにレイアウトを再構成する Drupal で提案されているように 、プロジェクトのナビゲーションやメニューを再構成して改善するためにユーザーリサーチを実施する プロジェクトが一貫したビジュアルデザインを保てるようにスタイルガイドを作る hapi.js のコントリビューターがやったように 、Tシャツや新しいロゴのデザインをする 文章を書くのが好きですか？ プロジェクトのドキュメントを書いたり改善する プロジェクトがどのように使われているかの事例を選別する プロジェクトのニュースレターを始めたり、メーリングリストのハイライトを整理する PyPA のコントリビューターがやったように 、プロジェクトのチュートリアルを書く プロジェクトのドキュメントを翻訳する 真面目な話、[ドキュメント]は非常に大事です。これまでの所、 Babel のドキュメントは素晴らしく、 Babel の最高の機能になっています。ただ、まだ作業が必要でものによっては文章を追加したほうが良い節があり、それをやってもらえると非常にありがたいです。 — @kittens, “Call for contributors” 整理するのが好きですか？ 整理するために、重複しているイシューを紐づけたり、新しいイシューのラベルを提案する @nzakas が ESLint でやったように 、オープンなイシューをくまなく調べ、古いものをクローズすることを提案する 議論を前進させるために、最近オープンされたイシューの内容を明確にする質問をする コードを書くのが好きですか？ @dianjin が Leaflet でやったように 、取り組むオープンなイシューを見つける 新しい機能を書く手伝いをできるかどうか聞いてみる プロジェクトのセットアップを自動化する ツールやテストの改善をする 人々を助けるのが好きですか？ Stack Overflow ( この Postgres の例のように )や Reddit でのプロジェクトに対する質問に答える オープンイシューでの質問に答える ディスカッションボードやコンバセーションチャネルでの会話の進行をする 他の人がコードを書くのを助けるのが好きですか？ 他の人のコードをレビューする プロジェクトがどのように使われるのかについてチュートリアルを書く @ereichert が Rust で @bronzdoc にやったように 、他のコントリビューターのメンターをやる 必ずしもソフトウェアプロジェクトで働く必要はありません 「オープンソース」はしばしばソフトウェアのことを指していますが、あなたはどんなものでもコラボレートできるのです。本やレシピ、リストや授業もオープンソースプロジェクトとして開発されているのです。 例えば: @sindresorhus は “素敵なもの”のリストを作っています @h5bp はフロントエンド開発者のための 面接での質問集 をまとめています @stuartlynn と @nicole-a-tesla は ツノメドリについての愉快な事柄のコレクション を作っています たとえあなたがソフトウェアエンジニアだったとしても、ドキュメントを書くことはオープンソース活動を始めるにあたって良いスタートとなります。ときにはコードを書かないプロジェクトに関わることのほうが障壁が低く、コラボレーションのプロセスを通じて自信と経験を身につけることができます。 新しいプロジェクトに順応しよう もしあなたがイシュートラッカーを見て、ごちゃごちゃしていると感じるのであれば、そう感じているのはあなただけではないはずです。こういったツールは多くの暗黙的な知識を必要としますが、人々は助けてくれますし、あなたから質問をすることもできるのです。 — @shaunagm, “How to Contribute to Open Source” タイポの修正以上のものであればなんでも、オープンソースにコントリビュートするというのは知らない人たちのパーティに近づいていくようなものです。もしあなたがラマについて話し始めたとして、一方で彼らは金魚について深い議論をしていたら、おそらくあなたのことを少し奇妙な目で見るでしょう。 盲目的にあなた自身の提案をする前に、部屋の雰囲気を読み取る方法を学びましょう。そうすることによって、あなたのアイデアの存在に気づいてもらい聞き入れてもらうチャンスが増すでしょう。 オープンソースプロジェクトの構造 それぞれのオープンソースコミュニティは異なります。 ある一つのオープンソースプロジェクトで長い時間を過ごしたということは、ある一つのオープンソースプロジェクトについて理解したということを意味します。異なるプロジェクトに移ると、使っている言葉や規範、コミュニケーションスタイルが全く異なることに気づくでしょう。 とはいえ、多くのオープンソースプロジェクトは似たような組織構造を持っています。異なるコミュニティの役割や全体のプロセスを理解することは新しいプロジェクトに早く順応するための助けになるでしょう。 典型的なオープンソースプロジェクトは下記のような種類の人々がいます: オーサー: そのプロジェクトを作った人(たち)もしくは組織 オーナー: 組織やリポジトリに対して管理上の所有権を持っている人(たち)もしくは組織(かならずしも元のオーサーと同じとは限らない) メンテナー: ビジョンを推し進め、プロジェクトの組織的なマネジメントを行うコントリビューター(彼らはオーサーやオーナーであることもある) コントリビューター: プロジェクトに対して何かしらのコントリビュートをするすべての人 コミュニティメンバー: プロジェクトを使っている人々。彼らは議論をしたり、プロジェクトの方向性に対して意見を表明したりする より大きなプロジェクトでは、ツールの整備やコミュニティのモデレートやイベントの運営など異なるタスクに特化した分科会やワーキンググループがあるかもしれません。プロジェクトのウェブサイトの「チーム」についてのページや、リポジトリの運営に関するドキュメントをみて、こういった情報を見つけましょう。 プロジェクトにはドキュメントもあります。これらのファイルはたいていリポジトリのトップレベルに置かれています。 LICENSE: その定義から、すべてのオープンソースプロジェクトは オープンソースライセンス を持っている必要があります。もしそのプロジェクトがライセンスを持っていないのであれば、それはオープンソースではありません。 README: README はそのプロジェクトへの新しいコミュニティメンバーを迎えるための操作マニュアルです。そこではなぜそのプロジェクトが便利で、どのように始めるかの説明があります。 CONTRIBUTING: README が人々がそのプロジェクトを 使う 手助けをする一方、 CONTRIBUTING ドキュメントは人々が コントリビュートする 手助けをします。そこではどういった種類のコントリビュートが必要とされていて、そのプロセスがどうなっているかの説明があります。すべてのプロジェクトが CONTRIBUTING ファイルを持つわけではないですが、そのファイルがあることによって、そのプロジェクトがコントリビュートを歓迎していることの印になります。 CODE_OF_CONDUCT: 行動規範は参加者の振る舞いに対する基本原則を設定し、友好的な環境を作る手助けをします。すべてのプロジェクトが CODE_OF_CONDUCT ファイルを持つわけではないですが、そのファイルがあることによって、そのプロジェクトがコントリビュートを歓迎していることの印になります。 その他のドキュメント: それ以外にも、特に大きなプロジェクトではチュートリアル、ウォークスルー、運営方針などといったドキュメントがあることがあります。 最後に、オープンソースプロジェクトは議論を整理するために次のようなツールを使います。アーカイブを読み通すことで、そのコミュニティがどのように考え動いてきたかを把握することができるでしょう。 イシュートラッカー: そのプロジェクトに関連するイシューを議論する場所 プルリクエスト: 作業中の変更について議論し、レビューをする場所 ディスカッションフォーラムやメーリングリスト: いくつかのプロジェクトではあるトピックについて会話 (例えば、バグの報告や機能要望の代わりに 「これはどうやって・・・すると良いのでしょう？」 や 「・・・についてどう思いますか？」 といったもの) をするのにこれらのチャネルを使うかもしれません。また、すべての会話をイシュートラッカー上で行うプロジェクトもあります。 同期的なチャットチャネル: カジュアルな会話やコラボレーション、簡単なやりとりについては ( Slack や IRC のような) チャットチャネルを使うプロジェクトもあります。 コントリビュートするプロジェクトを見つけよう さてあなたはオープンソースプロジェクトがどのように働くのかを理解しました。次はコントリビュートするプロジェクトを見つける番です！ もしあなたがこれまでにオープンソースプロジェクトにコントリビュートしたことが一度もないのであれば、アメリカ大統領のジョン・F・ケネディのアドバイスを聞いてみましょう。彼はかつて、 「あなたの国があなたのために何をしてくれるのかを問うのではなく、あなたが国のために何ができるかを問いなさい」 と言いました。 オープンソースへのコントリビュートはあらゆる階層で、プロジェクトをまたいで行われています。あなたの最初のコントリビュートが具体的にどういったものであるかや、どのようなものなのかを考えすぎる必要はありません。 代わりにあなたが既に使っていたり使いたいと思っているプロジェクトについて考え始めましょう。活発にコントリビュートすることになるプロジェクトは、何度も戻ってきたいと思うようなものなのです。 そういったプロジェクトの中で、何かをよくできたり違ったものにできると考え始めたときはいつでも、あなたの直感に従って行動しましょう。 オープンソースは排他的なクラブではありません。あなたのような人々からなっているのです。「オープンソース」は世の中の問題が解決可能であると扱うための単なるきらびやかな名前でしかないのです。 README を読んで、壊れたリンクやタイポを見つけるかもしれません。もしくは、あなたは新しいユーザーで、何かが壊れていたり、ドキュメントに書かれているべきと考えるイシューがあるかもしれません。それを無視して先に進んだり、他の誰かに直してとお願いする代わりに、あなたが参加することで手助けができないかどうか確かめてみましょう。これがオープンソースというものなのです！ オープンソースへの ふとしたコントリビュートの28% がタイポの修正やフォーマットの修正や翻訳といったドキュメントに対するものなのです。 また、新しいプロジェクトを見つけてコントリビュートする手助けとして、次のようなリソースのうちの一つを使うこともできます: GitHub Explore Open Source Friday First Timers Only CodeTriage 24 Pull Requests Up For Grabs First Contributions SourceSort OpenSauced コントリビュートする前のチェックリスト コントリビュートしたいプロジェクトを見つけたら、そのプロジェクトがコントリビュートを受け入れる体制ができているかどうかを確かめるために簡単に調べてみましょう。さもないと、あなたの懸命な努力が全くの無反応で終わってしまうかもしれません。 次に、プロジェクトが新しいコントリビューターにとって良いかどうかを評価する簡単なチェックリストを記載しました。 オープンソースの定義に適っているか ライセンスがあるか？たいてい、リポジトリのルートにある LICENSE という名前のファイルがそれに当たります。 プロジェクトがコントリビュートを積極的に受け入れているか master ブランチのコミットアクティビティをみてみましょう。 GitHub ではリポジトリのホームページでこの情報を見ることができます。 最新のコミットはいつか？ そのプロジェクトには何人のコントリビューターがいるか？ どのくらいの頻度でコミットしているか？ ( GitHub では、トップにある "Commits" をクリックすることでこれを見ることができます) 次に、プロジェクトのイシューをみてみましょう。 いくつのイシューがあるか？ メンテナーはイシューがオープンされたらすばやく反応しているか？ イシューでアクティブな議論は行われているか？ イシューは最近のものか？ イシューがクローズされているか？ ( GitHub では、 Issues ページの "closed" タブでクローズされたイシューを見ることができます) 次にプロジェクトのプルリクエストに対して同じことをしましょう。 いくつのプルリクエストがあるか？ メンテナーはプルリクエストがオープンされたらすばやく反応しているか？ プルリクエストでアクティブな議論は行われているか？ プルリクエストは最近のものか？ どのくらい最近プルリクエストがマージされたか？ ( GitHub では、プルリクエストページの "closed" タブをクリックすることでクローズされたプルリクエストを見ることができます) プロジェクトは歓迎してくれるか 友好的で歓迎してくれるプロジェクトは新しいコントリビューターを受け入れてくれる印です。 メンテナーはイシューでの質問に助けとなるような回答をしているか？ 人々はイシューやディスカッションフォーラム、チャット(例えば IRC や Slack )で友好的か)? プルリクエストはレビューされているか？ メンテナーはコントリビュートに対して感謝しているか？ 長いスレッドを見つけたら常に、スレッドの中で遅れてやってくるコア開発者の返答を確認してみましょう。彼らは建設的にまとめて、丁寧な姿勢を保ちつつもスレッドを結論に仕向けるべく一歩を踏み出していますか？もし罵り合いが多くあるのであれば、それはエネルギーが開発に向けられる代わりに議論に使われている兆候です。 — @kfogel, Producing OSS コントリビュートする方法 あなたは好きなプロジェクトを見つけ、コントリビュートをする準備ができています。ついに！次にあなたのコントリビュートを効果的に行う方法を紹介します。 効果的にコミュニケーションする あなたが一度きりのコントリビューターであろうとコミュニティに参加しようとしているのであろうと、他の人と働くことはオープンソースで獲得するスキルの中で最も大事なものの一つです。 [新しいコントリビューターとして、] イシューをクローズできるようになりたいのであれば、質問をする必要があるということにすぐに気づきました。私はコードベースをざっと読んで、一旦何が行われているのか感覚を掴んだら、さらなる方向について質問をしました。そして、ほら！必要だった関連する詳細を全て手に入れて、イシューを解決することができました。 — @shubheksha, A Beginner’s Very Bumpy Journey Through The World of Open Source イシューやプルリクエストをオープンする前に、あなたのアイデアが効果的に扱われる助けのために、これらのことを心にとどめておきましょう。 コンテキストを与えましょう。 他の人がすぐに把握する手助けをしましょう。もしあなたがエラーに遭遇しているのであれば、あなたが何をしようとしていて、どうやって再現させるのかを説明しましょう。もしあなたが新しいアイデアを提案しているのであれば、なぜそれがプロジェクトにとって（あなたにとってだけではなく！）便利だと思うのかを説明しましょう。 😇 “Yを行った時にXが起きません” 😢 “Xが壊れています！直して下さい。” まずは自分の手を動かしましょう。 何かを知らないのは問題ないのですが、トライしたことは示しましょう。助けを求める前に、プロジェクトの README やドキュメント、イシュー（オープンなものもクローズされたものも）、メーリングリストや答えをインターネットで探したか確認しましょう。人々はあなたが学ぼうとしていることを示せば、それを評価してくれるでしょう。 😇 “私は X を実装するやり方がわかりません。ヘルプドキュメントを見たのですが、それについての言及を見つけることができませんでした。” 😢 “わたしはどうやったら X ができますか？” 要求は短く直接的にしましょう。 メールを送るのと同じように、それぞれのコントリビュートは、それがいくらシンプルで役に立つものであっても、他の誰かのレビューを必要とします。多くのプロジェクトでは、人々が助けられる以上の数の要求が来ています。簡潔にしましょう。そうすれば、誰かが助けてくれるチャンスを増やすことができるでしょう。 😇 ” API チュートリアルを書こうと思っています。” 😢 “私は先日高速道路を走っていて、給油のため止まりました。すると、我々がやるべき素晴らしいアイデアが思い浮かんだのです。しかし、それを説明する前に・・・” 全てのコミュニケーションを公開の場でしましょう。 いくらやりたくなったとしても、機密情報（セキュリティイシューや重大な行動指針違反など）を共有するのでもない限り、メンテナーに非公開に接触するのはやめましょう。会話を公開の場で行い続ければ、あなたの会話からより多くの人が学び、利益を得ることができます。会話することはそれ自体がコントリビュートとなりうるのです。 😇 (コメントで) “@メンテナー こんにちは！このプルリクエストはどうやって進めたら良いですか？” 😢 (メールで) “こんにちは、メールを送ってすみませんが、私のプルリクエストをレビューしていただけないかと思いまして。” 質問をするのは問題ありません（ただし、辛抱強く！） 誰しもがある時点ではそのプロジェクトに慣れていなく、経験のあるコントリビューターでさえ新しいプロジェクトを見るときは最新情報が必要となります。同様に、古くからのメンテナーでさえ常にそのプロジェクトのあらゆる部分に詳しいわけではありません。あなたが彼らに望むような辛抱強さをあなたも彼らに対して示しましょう。 😇 “このエラーについて調べてくれてありがとうございます。あなたの提案に従ってみました。こちらがその出力です。” 😢 “なぜ私の問題を解決できないのでしょう？これはあなたのプロジェクトじゃないんですか？” コミュニティの決定を尊重しましょう。 あなたのアイデアはコミュニティの優先事項やビジョンとは異なっているかもしれません。彼らはフィードバックを提供したり、あなたのアイデアを採用しないと決定するかもしれません。あなたは議論したり妥協点を見出したりするべきですが、メンテナーはあなたよりも長い期間あなたのアイデアと付き合っていく必要があるのです。もしあなたが彼らの方向性に賛成出来ないのなら、あなたはいつでもあなた自身のフォークやあなた自身のプロジェクトを始めることができるのです。 😇 “あなたが私のユースケースを支持できないのは残念ですが、あなたが説明してくれたようにそれはユーザーのうちの一部にしか影響しませんし、私も理由を理解できます。意見を聞いてくださりありがとうございます。” 😢 “なぜあなたは私のユースケースを支持しないのですか？これは受け入れられません！” なにより常にポジティブでいましょう。 オープンソースは世界中のコラボレータによって成り立っています。言語や文化、地理、タイムゾーンをまたぐことでコンテキストが失われてしまいます。加えて、テキストコミュニケーションでは調子や雰囲気を伝えるのが難しいです。これらの会話では相手は前向きであると仮定しましょう。丁寧にアイデアを先送りしたり、さらなるコンテキストを聞いたり、あなたのポジションを更に明確にするのは良いことです。インターネットがあなたが見つけたときよりもよりよい場所であるように心がけましょう。 コンテキストを集める 何かをする前に、あなたのアイデアが他の場所で既に議論されていないか確かめましょう。そのプロジェクトの README やイシュー（オープンなものもクローズされたものも）、メーリングリストやスタックオーバーフローにざっと目を通しましょう。全てに目を通すのに何時間もかける必要はありませんが、いくつかのキーワードで検索するので十分です。 もしあなたのアイデアが他で見つけられないのであれば、動き出す準備ができたことになります。そのプロジェクトが GitHub 上にあるのであれば、あなたはおそらくイシューやプルリクエストをオープンすることでコミュニケーションするでしょう。 イシュー は会話や議論を始めるようなものです プルリクエスト は解決に向けて仕事を始めることです 確認や方法を聞く質問のような、 軽いコミュニケーションには 、もしそのプロジェクトが使っているのであれば、スタックオーバーフロー、 IRC 、 Slack や他のチャットで質問してみましょう。 イシューやプルリクエストをオープンする前に、そのプロジェクトのコントリビュートの方法についてのドキュメント（大抵は CONTRIBUTING と呼ばれるファイルや README の中にあります）を確認し、なにか特定の情報を含める必要があるか確かめましょう。例えば、あなたはテンプレートを使ったり、テストを実行する必要があるかもしれません。 もしあなたが大きなコントリビュートをしたいのであれば、その仕事に取り掛かる前にイシューをオープンしましょう。受け入れられないかもしれない仕事に取り掛かる前に、暫くの間そのプロジェクトをウォッチし（ GitHub では、 “Watch” をクリックすることで 全ての会話の通知を受け取ることができます)、コミュニティメンバーを知ることは役に立つでしょう。 あなたが活発に使っている一つのプロジェクトを選び、 GitHub 上で”ウォッチ”し、全てのイシューやプルリクエストに目を通すことで 多くのことを 学ぶでしょう。 — @gaearon on joining projects イシューをオープンする 下記のような状況では大抵イシューをオープンすべきです： あなただけで解決できないエラーの報告 高レベルなトピックやアイデア（例えば、コミュニティやビジョンや方針）についての議論 新しい機能や他のプロジェクトへのアイデアの提案 イシュー上でのコミュニケーションのコツ： あなたが取り組みたいオープンイシューを見つけたら、 そのイシュー上であなたがそれに取り掛かる事を人々に知らせるためにコメントしましょう。そうすることで、あなたの仕事と重複する可能性が減ります。 イシューがしばらく前にオープンされたのであれば、 それは他の場所で取り組まれていたり、既に解決されている可能性があります。なので、仕事に取り掛かる前に確認するコメントをしましょう。 もしあなたがイシューをオープンしたのに、あとになって自分で解決策を見つけたのであれば、 そのイシューで人々に知らせるためにコメントしましょう。そして、イシューをクローズしましょう。成果をドキュメントにするだけでもそのプロジェクトに対するコントリビュートとなります。 プルリクエストをオープンする 下記のような状況では大抵プルリクエストをオープンすべきです： 明確な修正（例えばタイポや壊れたリンクや明らかなエラー）の提出 既に要求されているコントリビュートや既にイシュー上で議論された仕事を始める際 プルリクエストでは、仕事が完了している必要はありません。大抵の場合、早い段階でプルリクエストを開き、他の人があなたの進捗を確認したり、フィードバックを与えられるようにしたほうが望ましいです。タイトルに “WIP” (Work in Progress) とつけましょう。いつでもさらなるコミットを追加できます。 そのプロジェクトが GitHub 上にあるのであれば、下記がプルリクエストを提出する方法です： リポジトリをフォークし ローカルにクローンしましょう。あなたのローカルと元の “upstream” リポジトリを remote として追加することで紐づけましょう。 “upstream” からの変更を頻繁にプルすることで、プルリクエストを提出する時にマージコンフリクトが起きづらくなるように、最新に追いついているようにしましょう。（より詳細な手順は こちら を確認して下さい)。 あなたの変更のための ブランチを切りましょう 。 プルリクエストの中で あらゆる関連するイシュー や関連するドキュメントを参照しましょう （例えば、 “Closes #37.” のように)。 もしあなたが HTML/CSS を変更するのであれば、 前後のスクリーンショットを含めましょう 。あなたのプルリクエストの本文に画像をドラッグアンドドロップしましょう。 あなたの変更をテストしましょう！ もし既存のテストがあるのであれば、あなたの変更に対してそのテストを実行したり、必要であれば新しいテストを作りましょう。既存のテストの有無にかかわらず、あなたの変更が既存のプロジェクトを壊さないことを確かめましょう。 できる限り そのプロジェクトのスタイルに従ってコントリビュートしましょう 。これによってインデントやセミコロン、コメントがあなた自身のリポジトリの使い方とは異なるかもしれないということを意味します。しかし、メンテナーがマージしやすくしたり、他の人が理解して将来もメンテナンスしやすいようにしましょう。 もしこれがあなたの初めてのプルリクエストであれば、 Make a Pull Request という、 @kentcdodds が作成したビデオチュートリアルを確認しましょう。また、プルリクエストを作る練習を First Contributions という、 @Roshanjossey によって作成されたリポジトリで行うこともできます。 コントリビュートを提出した後に起こること やりました！おめでとう、あなたはオープンソースコントリビューターになりました。これからも多数のコントリビュートを行う第一歩になることを願っています。 コントリビュートを提出した後、下記のうちのどれかが起きるでしょう： 😭 返事をもらえない あなたはコントリビュートを行う前に、 そのプロジェクトの活動の様子を調べていると思います 。しかしながら、アクティブなプロジェクトだったとしても、あなたのコントリビュートに対して返事が無いことがおき得ます。 一週間以上返事がないようであれば、同じスレッドにて、誰かにレビューを丁寧にお願いするのは妥当でしょう。あなたのコントリビュートをレビューするのに適切な人の名前を知っているのであれば、そのスレッドにて@メンションを使うことができます。 その人に非公開の場で接触するのは やめましょう 。オープンソースプロジェクトにとって、公開の場でコミュニケーションすることは必要不可欠であるということを思い出しましょう。 もしあなたが丁寧につついてもまだ誰も反応しないのであれば、ずっと誰も反応しない可能性があります。良い気分ではないでしょうが、落胆しないようにしましょう。それは誰に対しても起こることなのです！返事をもらえない理由はたくさんあり、それにはあなたがコントロールできない個人的な状況も含まれます。他のプロジェクトや他のコントリビュートの方法を探しましょう。いずれにしても、他のコミュニティメンバーが携わってくれて反応してくれるようになる前にコントリビュートをするのに大きな時間を投資しないほうが良いのです。 🚧 あなたのコントリビュートに対して変更を要求する人がいる あなたのコントリビュートに対して変更を要求されるのはよくあることです。その要求はあなたのアイデア自体に対してのフィードバックであることもあれば、コードに対する変更であることもあります。 変更を要求する人が居たら、すぐに返事をしましょう。彼らはあなたのコントリビュートに対して時間をとってレビューしてくれたのです。プルリクエストを開いて居なくなってしまうのは良くないやり方です。もしあなたが変更の仕方を知らないのであれば、その問題を調査し、必要であれば助けを求めましょう。 もしあなたがその問題に対してそれ以上の時間をかけることができない（例えばその会話が何ヶ月にも渡り、あなたの状況が変わったなど）場合は、メンテナーにそれを伝え、返答ができない旨を伝えましょう。他の誰かが喜んで引き継いでくれるはずです。 👎 あなたのコントリビュートが受け入れられない あなたのコントリビュートは最終的に受け入れられるかもしれないし、受け入れられないかもしれません。既に多大なコストを払っていないとよいのですが。もしなぜ受け入れられないかわからないのであれば、メンテナーにフィードバックや確認をするのは全くもって理にかなっています。しかし、究極的にはそれが彼らの決定であると尊重する必要があるでしょう。異議を唱えたり、敵意を示さないようにしましょう。もし彼らに賛成出来ないのであれば、あなたはいつでもフォークしてあなた自身のプロジェクトを始めることができるのです。 🎉 あなたのコントリビュートが受け入れられた バンザイ！あなたは無事にオープンソースにコントリビュートできました！ やりました！ 初めてのオープンソースへのコントリビュートをしたのであれ、他のコントリビュートの方法を探しているのであれ、あなたがなにか行動を起こそうという気持ちになっていたら嬉しいです。たとえあなたのコントリビュートが受け入れられなかったとしても、メンテナーがあなたを助けるために労力を割いてくれたことに対して感謝を伝えるのを忘れないようにしましょう。オープンソースはあなたのような、イシュー、プルリクエスト、コメントや挨拶をするような、人々で成り立っているのです。 すべてのガイドに戻る 関連するガイド オープンソースプロジェクトを始めよう オープンソースの世界のことをもっと学び、あなた自身のプロジェクトを立ち上げる準備をしましょう。 居心地の良いコミュニティを築こう 人々があなたのプロジェクトを使ったり、コントリビュートしたり、人に伝えたくなるようなコミュニティを築きましょう。 Scroll to Top 貢献する 提案したいことがありますか？このコンテンツはオープンソースです。改善にご協力ください。 貢献する 情報を受け取る GitHub の最新のオープンソースに関するヒントや情報をすぐに受け取りましょう。 メールアドレス fine print と 友達 による のこもった | 2026-01-13T09:29:15 |
https://opensource.guide/fa/starting-a-project/ | شروع یک پروژهی متن باز / منبع باز / اوپن سورس | Open Source Guides درباره پروژه مشارکت العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides شروع یک پروژهی متن باز / منبع باز / اوپن سورس در این مقاله چیزهای زیادی دربارهی دنیای متن بازها میآموزید و آمادهی انتشار پروژهی متن باز خودتان میشوید. فهرست مطالب چیستی و چرایی متن باز آیا پروژهی متن باز خودم را باید منتشر کنم؟ انتشار پروژهی متن باز خودتان نامگذاری و برندسازی پروژه مرور (چک لیست / لیست بررسی) قبل از انتشار پروژهی متن باز چیستی و چرایی متن باز اگر به این فکر میکنید که پروژهی متن باز خودتان را شروع کنید؟ به شما تبریک میگوییم! دنیا قدردان کمک و مشارکت شماست. اجازه دهید در ادامه درباره پروژههای متن باز بیشتر صحبت کنیم و ببینیم چرا مردم پروژههایشان را متن باز میکنند. متن باز به چه معناست؟ زمانی که یک پروژه متن باز یا اوپن سورس باشد، هر کسی میتواند و اجازه دارد به صورت رایگان از آن استفاده، مطالعه، ویرایش و برای هر هدفی که میخواهد، توزیع کند . این اجازهها در لایسنس متن باز قید شده و قابل اجراست پروژههای متن باز قدرتمند هستند، چون موانعی که در اختیارات و مشارکتها دیده میشود را کاهش و به افراد اجازه میدهد پروژههای خود را به سرعت گستردش و بهبود دهند. یکی دیگر از دلایل قدرتمند بودن متن بازها این است که پتانسیل کنترل محاسبه را بسته به منابع محدود به کاربران میدهد. اگر بخواهیم برای روشن شدن مطلب نمونهای بیاوریم، میتوانیم به کسبوکارهایی اشاره کنیم که به جای تکیه بر منابع محصور و محدود محصولات انحصاری فروشندههای نرمافزار، از نرمافزارهای متن بازی استفاده میکنند که به آنها اجازه میدهد شخصی را استخدام کنند تا آن نرمافزار را برای آنها شخصیسازی یا بهینه کند. نرمافزارهای رایگان همچنین به پروژههای متن باز منسوب میشود. گاهی هم ممکن است برنامههایی ببینید که ترکیبی از اصلاحات «نرمافزار متن باز و رایگان» (FOSS) یا «نرمافزار متن باز، آزاد و رایگان» (FLOSS) استفاده میکنند. خب، باید بگوییم که کلمهی Free (رایگان) و libre (آزاد / رایگان) هر دو به معنای آزادی در استفاده و دسترسی اطلاق میشود، نه قیمت آن چرا مردم پروژههایشان را متن باز میکنند؟ یکی از رضایتبخشترین تجربههایی که از استفاده و مشارکت در پروژههای متن باز به دست آوردم، آشنایی با افراد و توسعهدهندههایی بود که همان مشکلاتی را داشتند که من با آنها مواجه شده بودم. — @kentcdodds, “How getting into Open Source has been awesome for me” دلایل زیادی وجود دارد که یک شخص یا سازمان بخواهد پروژههای خود را متن باز کند. این دلایل عبارتند از: مشارکت: هر فردی در دنیا میتواند پروژههای متن باز را تغییر دهد و در ویرایش آن مشارکت داشته باشد. به عنوان نمونه، Exercism که به عنوان یک پلتفرم متن باز برای تمرین برنامهنویسی شناخته میشود، با مشارکت افراد مختلف تا به الان بیش از 350 توزیع و ویرایش داشته است. اقتباس و تغییر مجدد: هر فردی تقریباً با هر هدفی میتواند از پروژههای متن باز استفاده کند. افراد حتی میتوانند از یک پروژه، پروژههای دیگری به وجود بیاورند. به عنوان مثال میتوانیم به وردپرس اشاره کنیم که از پروژه موجودی به نام b2 منشعب شده است. شفافیت: هرکسی میتواند خطاها و تناقض پروژههای متن باز را بازرسی کند. از این رو، شفافیت برای دولتهایی مانند دولت بلغارستان یا ایالات متحده آمریکا و صنایع مقرراتی مانند بانکداری، مراکز بهداشت وُ درمانی و نرمافزار امنیتی مانند Let’s Encrypt اهمیت بالایی پیدا میکند تا زمان بازرسی خطاها توسط افراد مختلف، دچار مشکل نشوند. ویژگی متن باز فقط مختص به نرمافزارها نیست، شما هر چیزی حتی مجموعهای از دادههای یک کتابخانه را میتوانید متن باز کنید. اگر میخواهید بیشتر بدانید که چه چیزهای دیگری را میشود متن باز کرد، میتوانید به GitHub Explore مراجعه کنید. آیا پروژهای متن باز «مجانی / رایگان» هستند؟ یکی از بزرگترین جذابیتهای متن بازها این است که پولی نیستند. هرچند، رایگان بودن، یک محصول جانبی با ارزش کلی یک پروژهی متن باز است. به عبارت دیگر، در لایسنس و گواهینامهی پروژههای متن بازها آورده شده است که هر کسی میتواند آنها را استفاده، ویرایش و تقریباً با هر هدفی به اشتراک بگذارد. از این رو، پروژههای متن باز به صورت رایگان عرضه میشوند و اگر هم استفاده از این پروژهها پولی شود، هر کسی به صورت قانونی میتواند از آن کپی بگیرد و درعوض، از نسخهی رایگان آن استفاده کند در نتیجه، بیشتر پروژههای متن باز به صورت رایگان ارائه میشوند و از طرفی هم «رایگان بودن / مجانی بودن» به عنوان بخشی از تعریف پروژههای متن باز به حساب نمیآید، یعنی پروژههای متن باز هم به صورت رایگان و هم به صورت پولی هستند. البته راههایی سازگار با مجوزهای متن باز مثل ارائه مجوز دوگانه یا محدودکردن ویژگی ها به دو دسته رایگان و پولی برای کسب درآمد غیرمستقیم از پروژههای متن باز وجود دارد. آیا پروژهی متن باز خودم را باید منتشر کنم؟ اگر بخواهیم کوتاه جواب بدهیم، بله. چون خروجی پروژهی شما مهم نیست. مهم این است که پروژهتان منتشر شود و بهترین راه برای یاد گرفتن نحوهی کار پروژههای متن باز انتشار آنهاست. اگر هیچوقت پروژهی متن بازتان را منتشر نکردهاید، ممکن است این نگرانی برایتان پیش بیاید افراد مختلف چه چیزی دربارهی پروژهتان میگویند یا اصلا به پروژهی شما توجه میکنند یا خیر. اگر چنین احساسی دارید، باید بگوییم که تنها نیستید. کار یک پروژهی متن باز مانند هر فعالیت خلاقانهی دیگری مثل نویسندگی و نقاشی است. زمانی که شما به عنوان یک هنرمند اولین اثر خود را با دنیا به اشتراک میگذارید، احساس ترس به سراغتان میآید. اما این کار را باید انجام دهید، چون تمرین تنها راه بهتر شدن است؛ حتی اگر یک مخاطب هم نداشته باشید. اگر هنوز هم متقاعد نشدید، به این فکر کنید که اهدافتان چه چیزهایی میتوانند باشند. اهدافتان را مشخص کنید اهداف میتواند به شما کمک کند تا متوجه شوید که بر روی چه چیزی کار کنید، به چه چیزی نه بگویید و کجا به کمک دیگران نیاز دارید. با سوال کردن از خودتان شروع کنید. از خودتان بپرسید: چرا میخواهم این پروژه را متن باز کنم؟ خب، واضح است که هیچ کس جواب درستی برای این سوال ندارد. چون ممکن است چندین هدف برای یک پروژه یا پروژههای مختلفی با اهداف متفاوتی وجود داشته باشد. اگر نمایش دادن کارتان تنها هدف برای متن باز کردن پروژهتان باشد، احتمالاً مشارکت دیگران را نمیخواهید و این نخواستن مشارکت را هم در فایل README پروژهتان نیز میآورید. از طرف دیگر، اگر واقعاً مشارکت دیگران را بخواهید، زمان خود را صرف مرتب کردن اسناد و صرف خوشامدگویی به افرادی میکنید که تازه وارد این حوزه شدند. زمانی که پروژهی UIAlertView شخصی را تولید و استفاده کردم …. و تصمیم گرفتم آن را متن باز کنم، تغییراتی در آن اعمال کردم تا پویایی بیشتری داشته باشد و آن را در GitHub آپلود کردم. من همچنین اولین سندی (که توضیح پروژه در آن نوشته میشود) را برای سایر توسعهدهندهها نوشتم که نحوهی کار با پروژهی من چگونه است. احتمالاً به خاطر اینکه پروژهی سادهای بود، هیچکس از آن استفاده نکرد. هرچند، اما به خاطر مشارکتم به سایر توسعهدهندهها احساس خوبی داشتم. — @mavris, “Self-taught Software Developers: Why Open Source is important to us” وقتی که پروژهی شما رشد میکند، جامعهی مخاطب پروژههایتان احتمالاً بیشتر از یک کد به شما نیاز خواهند داشت. وظایف مهمی که در یک پروژهی متن باز به شما محول میشود این است که برای مشکلات پاسخی داشته باشید، کدها را بررسی کنید و مژدهی پروژهی متن بازتان را به دیگران بدهید. اگرچه مدت زمانی که صرف کارهای غیرکدنویسی میکنید، به اندازه و دامنهی پروژهیتان بستگی دارد، اما به عنوان یک مسئولنگهداری پروژه باید خودتان را آماده کنید آنها را انجام دهید یا حداقل شخصی را پیدا کنید که در کارهای غیرکدنویسی به شما کمک کند. اگر جزئی از یک پروژهی متن باز یک شرکت هستید، مطمئن شوید پروژهیتان منابع لازم داخلی برای پیشرفت را داشته باشد. از این رو، باید بدانید که چه کسی مسئول نگهداری پروژهی متن بازتان است و چگونه میخواهید این وظایف را با جامعهی خود به اشتراک بگذارید اگر برای ارتقاء، بهرهبرداری و نگهداری پروژه به بودجه خاص یا کارمند نیاز دارید، میتوانید این نیازها را در ابتدا اعلام کنید. زمانی که پروژهی متن بازتان را شروع میکنید، مهم است که اطمینان حاصل کنید که فرآیندهای مدیریتی شما ظرفیت مشارکتها و تواناییهای جامعهی پیرامونی و مخاطب پروژهتان را در برگیرد. از مشارکت دادن مشارکتکنندههایی نترسید که از جنبههای کلیدی پروژه، کارمند کسب و کارتان نیستند، به خصوص اگر مشارکت آنها با شما مکرر باشد. — @captainsafia, “So you wanna open source a project, eh?” مشارکت در سایر پروژهها اگر هدفتان این باشد که با دیگران در پروژههای متن باز همکاری کنید یا میخواهید نحوهی عملکرد یک پروژهی متن باز را درک کنید، همکاری و مشارکت با پروژههای موجود را در نظر بگیرید. با پروژهای شروع کنید که قبلا به آن علاقهمند بودید و از آن استفاده میکردید. مشارکت در یک پروژهی متن باز میتواند به سادگی اصلاح یک کد اشتباه یا آپدیت / بهروزرسانی اسناد باشد. اگر مطمئن نیستید که چگونه میتوانید در سایر پروژهها مشارکت کنید، به مقالهی راهنمای نحوهی همکاری در پروژهی متن باز مراجعه کنید انتشار پروژهی متن باز خودتان زمان مناسبی برای متن باز کردن پروژهتان وجود ندارد. از این رو، میتوانید یک ایده، کارهایی در دست اقدام یا پروژههایی که بعد از سالها بسته ماندند، را متن باز کنید. به طور کلی، هر زمان که احساس کردید با دیدگاهها و بازخوردهای دیگران راحت هستید، باید پروژهیتان را متن باز کنید. مهم نیست در چه مرحلهای تصمیم گرفتید پروژهتان را متن باز کنید. هر پروژهای باید حاوی اسناد زیر باشد: لایسنس متن باز README راهنمای مشارکت آیین نامه رفتار این مؤلفهها به شما به عنوان مسئولنگهداری پروژه کمک میکند تا انتظاراتتان را بیان، مشارکتها را مدیریت و از حقوق قانونی خود و دیگران محافظت کنید. این موارد شانس شما را برای داشتن یک تجربهی خوب افزایش میدهد. اگر پروژهی شما در GitHub قرار دارد، قرار دادن فایلهای فوق به همراه نام فایلهای توصیهشده در پوشه ریشه (root) میتواند به GitHub کمک کند تا آنها را به صورت خودکار به مخاطبانتان شناسایی کند و نمایش دهد. انتخاب لایسنس یا مجوز لایسنسِ یا مجوز یک پروژهی متن باز به دیگران ضمانت میدهد از پروژهی متن باز استفاده، کپی، ویرایش و بدون هیچ عواقبی در آن مشارکت کنند. لایسنس همچنین از شما در برابر موقعیتهای سخت قانونی محافظت میکند. زمانی که میخواهید پروژهی متن بازتان را منتشر کنید، حتما لایسنس آن را هم ضمیمه کنید . کارهای ادارای و حقوقی برای گرفتن لایسنس هیچ جذابیتی ندارد، اما خبر خوب اینجاست که میتوانید لایسنسهای موجود و در دسترس را که از قبل توسط دیگران تدوین شده را در repository (مخزن) خود کپی و پیست کنید. برای محافظت از تلاشی که برای متن باز کردن پروژهتان انجام دادید، این کار تنها یک دقیقه وقت شما را میگیرد. MIT ، Apache 2.0 و GPLv3 جزء محبوبترین لایسنسهای متن باز هستند. هرچند، لایسنسهای دیگری هم وجود دارد که میتوانید از آنها استفاده کنید. زمانی که پروژهی جدیدی در GitHub ایجاد میکنید، به شما امکان انتخاب لایسنس داده میشود. انتخاب کردن لایسنس باعث میشود GitHub پروژهی شما را متن باز نشان دهد. در ادامهی مقاله، سایر سوالات و نگرانیهایتان دربارهی جنبههای قانونی مدیریت پروژهی متن بازتان را بررسی خواهیم کرد. نوشتن فایل «README» (فایلی که توضیحات پروژه در آن آورده میشود) فایل README اطلاعات بیشتری نسبت به این دارد که نحوهی استفاده از پروژهتان را به کاربر توضیح دهد. این فایل همچنین توضیح میدهد که پروژهی شما چه اهمیتی دارد و کاربرانتان با این پروژه چه کارهای میتوانند انجام دهند. سعی کنید در فایل README خودتان به سوالات زیر پاسخ دهید و جواب آنها را در فایل بیاورید: پروژهی شما چه کاری انجام میدهد؟ چرا این پروژه مفید است؟ چگونه شروع کردم؟ در صورت نیاز، از کجا میتوانم کمک بیشتری دریافت کنم؟ شما با فایل README میتوانید به سایر سوالات نیز پاسخ دهید؛ سوالاتی مانند اینکه چگونه مشارکتتان را مدیریت میکنید، اهداف پروژهتان چیست و اطلاعات لایسنس و اختیارات پروژهتان را هم میتوانید بیاورید. اگر مشارکت کسی را نمیخواهید قبول کنید، یا پروژهی شما هنوز برای ارائه آماده نشده باشد، میتوانید این توضیحات را در فایل README بیاورید هرچه اسنادتان اعم از فایل README، راهنمای مشارکت، آیین نامه رفتار و لایسنس در پروژهی متن باز شما بهتر باشد، کاربران بیشتری به شما جذب میشود، پشتیبانی کمتری درخواست میشود و مشارکتکنندههای بیشتری در پروژه مشارکت میکنند. به یاد داشته باشید که مخاطبانتان جای شما نیستند و افرادی ممکن است وارد پروژهی شما شوند که تجربههای کاملاً متفاوتی دارند. — @tracymakes, “Writing So Your Words Are Read (video)” بعضی از افراد از نوشتن فایل README خودداری میکنند، چون فکر میکنند پروژهی آنها هنوز تکمیل نشده یا اینکه نمیخواهند کسی مشارکتی داشته باشد. همینها دلایل خیلی خوبی برای نوشتن یک فایل README محسوب میشوند. برای نوشتن یک فایل README کامل، میتوانید به مقالات @dguo’s “Make a README” guide یا @PurpleBooth’s README template مراجعه کنید و از آنها الهام بگیرید زمانی که فایل README را در دایرکتوری ریشه خود قرار میدهید، GitHub به صورت خودکار آن را در صفحهی اصلی repository (انبار) نشان میدهد. نوشتن راهنمای مشارکت فایل CONTRIBUTING (مشارکت) به مخاطبانتان میگوید که چگونه در پروژهی شما مشارکت کنند. به عنوان مثال، میتوانید اطلاعات زیر را در آن قید کنید: چگونه یک باگ یا مشکل گزارش شود چگونه ویژگی جدیدی پیشنهاد دهند چگونه محیط پروژهتان را تنظیم و آن را برای تست اجرا کنند به علاوه، در فایل CONTRIBUTING میتوانید جزئیات فنی و انتظاراتتان را برای مشارکتکنندهها بیان کنید. به عنوان مثال: نوع مشارکتی که به دنبال آن هستید نقشهی راه یا دیدگاهی که به پروژه دارید چگونه مشارکتکنندهها باید (یا نباید) با شما در تماس باشند زمانی که با خونگرمی، حس دوستانه و دادن پیشنهادهای خاص (مانند نوشتن اسناد، یا طراحی وبسایت) با مشارکتکنندههایتان برخورد میکنید، بیشتر راه را برای استقبال از تازهواردها رفتهاید و همین کار شما باعث میشود آنها برای همکاری با شما هیجانزده شوند. برای روشن شدن مطلب اجازه دهید نمونهای بیاوریم. به عنوان مثال، Active Admin راهنمای مشارکت خود به مشارکتکنندهها را اینگونه شروع میکند در ابتدا، از شما ممنون هستم که میخواهید با Active Admin مشارکت کنید. افرادی مثل شما هستند که باعث میشوند Active Admin عملکرد خوبی داشته باشد. در ابتداییترین مرحلهی پروژهتان، فایل CONTRIBUTING میتواند ساده باشد. شما در این فایل همیشه باید نحوهی گزارش دادن باگها (خطاها) یا مشکلات فایل و هر نیاز فنی مانند تست کردن را برای مشارکتکنندهها توضیح دهید. در طول زمان، ممکن است اطلاعات و سوالات مکرر زیادی به فایل CONTRIBUTING خود اضافه کنید. از این رو، افراد کمتری پیدا میشوند که سوالات تکراری از شما بپرسند. برای اینکه بدانید چگونه اطلاعات فایل CONTRIBUTING خود را بنویسید، میتوانید به مقالات @nayafia’s contributing guide template یا @mozilla’s “How to Build a CONTRIBUTING.md” مراجعه کنید. لینک فایل CONTRIBUTING خود را در فایل README قرار دهید تا افرادی که آن را مطالعه میکنند این فایل مشارکت را هم ببینند. اگر فایل CONTRIBUTING خود را در repository (انبار) (مخزن) پروژهتان قرار داده باشید، زمانی که یک مشارکتکننده طرح مشکل یا گزارش یک باگ یا درخواست ادغام کند، GitHub به صورت خودکار او را به لینک فایل CONTRIBUTING هدایت میکند تعیین آیین نامهی رفتاری (Code of Conduct) همهی ما به عنوان یک مسئولنگهداری پروژه با سوءاستفادههایی مواجه شدهایم که در آن سعی میکردیم توضیح دهیم چرا چیزی را باید از مسیر خاص خودش طی کنیم، یا به عنوان یک کاربر تلاش میکردیم یک سوال ساده بپرسیم. آیین نامهی رفتاری به سندی قابل ارجاع و پیوندی تبدیل شده که نشان میدهد تیم شما اجرای گفتمان سازنده را بسیار جدی میگیرد. — @mlynch, “Making Open Source a Happier Place” بالاخره، آیین نامهی رفتاری به ما کمک میکند برای رفتارهای مشارکتکنندههای پروژهتان قوائدی تعیین کنید. زمانی که بخواهید یک پروژهی متن بازی را برای انجمن یا یک شرکت منتشر کنید، این قوائد میتواند ارزشمند باشد. آیین نامهی رفتاری یا (Code of Conduct) این قدرت را به شما میدهد تا رفتارهای سازنده و سالم را در بین جامعه کاربران ترویج کنید که در آینده به عنوان یک مسئولنگهداری پروژه احساس استرس کمتری داشته باشید. برای اطلاعات بیشتر میتوانید به راهنمای آیین نامهی رفتاری مراجعه کنید. علاوه بر اینکه یک آیین نامهی رفتاری رفتارهایی که از شرکتکنندهایتان انتظار دارید را باید به آنها بگوید، این را هم باید تعریف کنید که اجرای این انتظارات به چه کسانی و در چه زمانهایی باید انجام میشود. آیین نامهی رفتاری همچنین مشخص میکند که درصورت بروز تخلف چه کاری باید انجام شود. مشابه استفاده از مجوزهایی که از قبل توسط دیگران تدوین شده استانداردهای نوظهوری برای آیین نامهی رفتاری وجود دارد که لازم نیست خودتان آن را بنویسید. Contributor Covenant یکی از جاهایی است که آیین نامههایی در همین خصوص ارائه میکند و حاصل کار آن در بیش از 40.000 پروژهی متن باز مانند Kubernetes، Rails و Swift استفاده میشود. مهم نیست متن آیین نامهی رفتاری شما چیست، مهم این است که در صورت لزوم باید از آیین نامهی رفتاری خودتان استفاده کنید متن آیین نامهی رفتاری خود را مستقیما در فایل CODE_OF_CONDUCT در مخزن گیت هاب خودتان کپی و پیست کنید. فایل را در دایرکتوری روت پروژهتان ذخیره کنید تا پیدا کردن و لینک دادن آن به فایل README راحت باشد. نامگذاری و برندسازی پروژه برندسازی چیزی فراتر از یک لوگوی پُر زرق وُ برق یا یک نام جذاب برای پروژهتان است. برندسازی نحوهی صبحت کردن دربارهی پروژه و نحوه رساندن پیام به مخاطبتان را نشان میدهد. انتخاب نام درست برای پروژهتان از نامی استفاده کنید که یادآوری آن ساده باشد. به طور ایده آل، میتوانید بعضی از ایدهها را از پروژههای زیر مشاهده کنید. به عنوان نمونه: Sentry اپ ها را با هدف گزارش خطاهای رخ داده در آنها پایش می کند Thin یک وب سرور ساده و سریع روبی است اگر در حال طراحی پروژهتان هستید، به کارگیری نام آنها به عنوان پیشوند میتواند به شفاف کردن پروژهتان کمک کند. به عنوان نمونه، ( node-fetch ، Window.fetch را به Node.js میآورد). با در نظر گرفتن توصیه بالا. میتوان عناوین بامزه یا خوب زیادی ساخت، اما این را به یاد داشته باشید که بعضی از بازی با کلمات و جناسها ممکن است در سایر فرهنگها یا افرادی که تجربههای متفاوتی نسبت به شما دارند، مفهوم یا ترجمهی نادرستی داشته باشد. برخی از کاربران بالقوه شما هم ممکن است کارمندان یک شرکت باشند و حتما نمیخواهید زمانی که در حال توضیح دادن نحوهی پروژهتان در محل کارشان هستند، احساس نامساعدی داشته باشند. از نامگذاریهای دارای منافات خودداری کنید اگر پروژهی شما زبان و اکوسیستم یکسانی دارد، میتوانید نام پروژههای مشابه با پروژهتان را بررسی کنید . اگر نام پروژهی شما با پروژهی دیگری شباهت زیادی داشته باشد، مخاطب شما ممکن است سردرگم شود. اگر در یک وبسایت، توئیتر یا دیگر شبکههای اجتماعی میخواهید پروژهتان را نشان دهید، مطمئن شوید همان نامی را انتخاب کنید که میخواهید. به طور ایده آل، حتی اگر هنوز نمیخواهید از آن نام استفاده کنید و برای اینکه خیالتان راحت باشد، آن نام را وارونه کنید مطمئن شوید نام پروژهی شما هیچ برند تجاری را نقض نمیکند. اگر چنین باشد، آن شرکت میتواند بعدها از شما درخواست کند پروژهتان را کنسل کرده یا حتی به صورت قانونی با شما برخورد کند. بنابراین، ارزش این همه ریسک را ندارد و برای جلوگیری از چنین مشکلاتی حتما از نام مناسبی استفاده کنید. برای بررسی تضاد و منافات برندهای تجاری میتوانید به پایگاه داده برندهای جهانی WIPO Global Brand Database مراجعه کنید. اگر شما یک شخص حقوقی هستید و در یک شرکت فعالیت میکنید، این یکی از چیزهایی است که تیم حقوقیتان میتواند به شما کمک کند در نهایت، نام پروژهتان را به سرعت در گوگل جستجو کنید. ببینید که افراد به راحتی میتوانند پروژهتان را پیدا کنند؟ در نتایج جستجوی شما چیزی دیگر پیدا میشود که نمیخواهید کاربران آن را مشاهده کنند؟ چگونه نوشتن و کدنویسی شما روی برندتان اثر میگذارد! در طول عمر پروژهتان، در حال نوشتن چیزهای زیادی خواهید بود که میتوان به نوشتن فایلهای README، آموزشها، اسناد انجمن، نوشتن پاسخ به مشکلات، حتی شاید نوشتن و پاسخ دادن به خبرنامه و فهرست پستی، اشاره کرد. سبک نویسندگی شما چه در اسناد رسمی و چه در ایمیلهای محاورهای بخشی از برند پروژهتان است. به این فکر کنید چگونه میخواهید با مخاطبتان برخورد کنید و ببینید این لحن نوشتاری همان چیزی است که میخواهید به مخاطب فرستاده شود یا خیر. زمان ارسال هر پست، تلاش میکردم رفتار ستودهای داشته باشم، با مردم درست رفتار کنم، مشکلاتشان را جدی بگیرم و در کل سعی میکردم مفید باشم. بعد از مدتی، افراد نه تنها سوال میپرسیدند، بلکه در جواب دادن در برخی سوالات به من کمک میکردند و در نهایت لذت آنها از سبک نویسندگی من تقلید میکردند — @janl on CouchDB , “Sustainable Open Source” زمانی که از یک زبان جامع و گرم استفاده میکنید و حتی زمانی که با یک فرد صحبت میکنید، به جای کلمهی «تو» کلمهی «شما» را به کار میبرید، کمک زیادی به شما میکند تا مشارکتکنندههای جدید از پروژهی شما استقبال کنند. اگر میخواهید به زبان انگلیسی بنویسید، سعی کنید ساده باشد. چون زبان بیشتر خوانندههای شما بومی نیست. جدا از کلماتی که در نوشتن اسناد مختلف استفاده میکنید، سبک کدنویسی شما هم ممکن است به بخشی از برند پروژهتان تبدیل شود. به عنوان مثال میتوانیم به دو نمونه پروژه به نامهای Angular و jQuery اشاره کنیم که راهنما و سبک کدنویسی سختی دارند در ابتدای کار لازم نیست از راهنمای سبک نویسندگی استفاده کنید. به هر حال، به مرور از ترکیب سبک متفاوت کدنویسی خود در پروژهتان لذت خواهید برد. هرچند، این را باید پیشبینی کنید که نحوهی نویسندگی و سبک کدنویسی شما ممکن است انواع مختلف افراد را جذب یا دفع کند. در ابتدایترین مرحلهی پروژهتان فرصت دارید مقدماتی که میخواهید مخاطبان ببنند را ارائه دهید. مرور (چک لیست / لیست بررسی) قبل از انتشار پروژهی متن باز خب، آماده هستید تا پروژهتان را متن باز کنید؟ چک لیست در این مرحله میتواند به شما کمک کند. تمام گزینهها و تیکها را بررسی کردهاید؟ به محض آماده شدن، روی انتشار publish کلیک کنید و به خودتان تبریک بگویید. مستندات پروژه حاوی فایل (LICENSE) لایسنس متن باز است پروژه حاوی اسناد پایه اعم از (فایل README، CONTRIBUTING و فایل CODE_OF_CONDUCT) است نام پروژه ساده است، میتوان آن را به راحتی به خاطر سپرد، نام پروژه این ایده را به مخاطب میدهد که پروژه چه کارهایی انجام میدهد و نام پروژه با هیچ پروژه موجودی منافات ندارد یا هیچ برند تجاری را نقض نمیکند. صف مشکلات و مسائل گزارش شده با زدن برچسب های مناسب سازماندهی شده و بروز است. کد پروژه از توافقهای از پیش تعیین شده در خصوص نامهای متغیر/متدها و توابع استفاده میکند کد به خوبی کامنتگذاری شده و تو رفتگیها و کوچکی و بزرگی حروف در جای لازم رعایت شده است. There are no sensitive materials in the revision history, issues, or pull requests (for example, passwords or other non-public information) اطلاعات حساسی مثل کلمه های عبور یا کلیدهای خصوصی از طریق Pull Request یا گزارش مشکل و... برای عموم آشکار نشود افراد اگر شما شخص حقیقی هستید: (اگر در جایی کارمند هستید)، با دپارتمان / بخش حقوقی خود صحبت کردهاید، IP و شرایط و قوانین متن باز شرکت را متوجه شدهاید. اگر شخص حقوقی هستید و در یک سازمان یا یک شرکت فعالیت میکنید: با دپارتمان / بخش حقوقی صحبت کردهاید. برای اطلاع رسانی و ترویج پروژهام برنامهی بازاریابی دارم. یک شخص برای مدیریت تعاملات اجتماعی (پاسخ به مشکلات، بررسی و درخواست ادغام) که متعهد باشد حضور دارد. حداقل دو نفر دسترسی مدیریتی (Admin) به پروژه داشته باشند انجامش دادی! اولین پروژهی متن بازتان را تبریک میگوییم. بهتر است بدانید که خروجی آن مهم نیست، فقط با این کار تجربهی کار در فضای جامعه را به دست آوردید. با هر کامیت (Commit)، کامنت (Comment) و پاسخ به درخواست ادغام فرصتی برای رشد و یادگیری خود و دیگران ایجاد میکنید. بازگشت به راهنمای اصلی راهنما های مشابه پیدا کردن کاربر برای پروژههایتان با داشتن کاربرانی راضی و خوشحال، به پروژهی اوپن سورس خود کمک کنید تا رشد کند.. ساخت انجمن های پذیرا ساخت یک انجمن که افراد را به استفاده کردن ، اشتراک گذاری و تبلیغ کردن پروژه تان ترغیب کند. Scroll to Top مشارکت کنید آیا پیشنهاد یا نظری دارید؟ این مطلب متن باز است. به ما کمک کنید تا بهبودش دهیم. مشارکت درارتباط باشید اولین نفری باشید که در خصوص آخرین نکات و ترفندهای متن باز در گیتهاب باخبر می شود. آدرس ایمیل fine print با توسط و دوستان | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/amazon-web-services-amazon-rds/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Amazon RDS | LinkedIn Skip to main content LinkedIn Amazon Web Services (AWS) in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Amazon RDS Relational Database Management Systems by Amazon Web Services (AWS) See who's skilled in this Add as skill Learn more Report this product About With Amazon RDS, set up, operate and scale a commercial or open source relational database in the cloud in just a few clicks while automating time-consuming administrative tasks. Similar products Amazon Aurora Amazon Aurora Relational Database Management Systems Google Cloud SQL Google Cloud SQL Relational Database Management Systems Teradata Vantage Teradata Vantage Relational Database Management Systems Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems SQL Server SQL Server Relational Database Management Systems CockroachDB CockroachDB Relational Database Management Systems Sign in to see more Show more Show less Amazon Web Services (AWS) products Amazon Aurora Amazon Aurora Relational Database Management Systems Amazon DynamoDB Amazon DynamoDB NoSQL Database Software Amazon EC2 Amazon EC2 Infrastructure as a Service (IaaS) Amazon Lightsail Amazon Lightsail Platform as a Service (PaaS) Software Amazon SageMaker Amazon SageMaker Data Science & Machine Learning Platforms Amazon Simple Storage Service (S3) Amazon Simple Storage Service (S3) Object Storage Software Amazon Virtual Private Cloud Amazon Virtual Private Cloud Virtual Private Cloud (VPC) Software AWS Lambda AWS Lambda Platform as a Service (PaaS) Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?fromSignIn=true&session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fcloudflare&trk=top-card_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=COMPANY&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://www.linkedin.com/legal/cookie-policy?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2FshareArticle%3Fmini%3Dtrue%26url%3Dhttps%253A%252F%252Fdev%2Eto%252Faditya_singh_172b37651201%252F30-core-algorithm-ep-06-prefix-sum-1ii0%26title%3D30%2520Core%2520Algorithm%2520%253A%2520Ep-06%2520%253APrefix%2520Sum%26summary%3DWhy%2520Prefix%2520Sum%2520Is%2520Really%2520About%2520Making%2520Accumulated%2520Cost%2520Explicit%2520%2520%2520Many%2520performance%2E%2E%2E%26source%3DDEV%2520Community&trk=registration-frontend_join-form-cookie-policy | Cookie Policy | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Cookie Policy Effective on June 3, 2022 At LinkedIn, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any LinkedIn product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy. What technologies are used? ENTER A SUMMARY Type of technology Description Cookies A cookie is a small file placed onto your device that enables LinkedIn features and functionality. Any browser visiting our sites may receive cookies from us or cookies from third parties such as our customers, partners or service providers. We or third parties may also place cookies in your browser when you visit non-LinkedIn sites that display ads or that host our plugins or tags . We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and is used for many purposes, such as recognizing you as an existing user, so it’s easier to return to LinkedIn and interact with our Services without signing in again. Since a persistent cookie stays in your browser, it will be read by LinkedIn when you return to one of our sites or visit a third party site that uses our Services. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Pixels A pixel is a tiny image that may be embedded within web pages and emails, requiring a call (which provides device and visit information) to our servers in order for the pixel to be rendered in those web pages and emails. We use pixels to learn more about your interactions with email content or web content, such as whether you interacted with ads or posts. Pixels can also enable us and third parties to place cookies on your browser. Local storage Local storage enables a website or application to store information locally on your device(s). Local storage may be used to improve the LinkedIn experience, for example, by enabling features, remembering your preferences and speeding up site functionality. Other similar technologies We also use other tracking technologies, such as mobile advertising IDs and tags for similar purposes as described in this Cookie Policy. References to similar technologies in this policy includes pixels, local storage, and other tracking technologies. Our cookie tables lists cookies and similar technologies that are used as part of our Services. Please note that the names of cookies and similar technologies may change over time. What are these technologies used for? Below we describe the purposes for which we use these technologies. ENTER SUMMARY Purpose Description Authentication We use cookies and similar technologies to recognize you when you visit our Services. If you’re signed into LinkedIn, these technologies help us show you the right information and personalize your experience in line with your settings. For example, cookies enable LinkedIn to identify you and verify your account. Security We use cookies and similar technologies to make your interactions with our Services faster and more secure. For example, we use cookies to enable and support our security features, keep your account safe and to help us detect malicious activity and violations of our User Agreement. Preferences, features and services We use cookies and similar technologies to enable the functionality of our Services, such as helping you to fill out forms on our Services more easily and providing you with features, insights and customized content in conjunction with our plugins. We also use these technologies to remember information about your browser and your preferences. For example, cookies can tell us which language you prefer and what your communications preferences are. We may also use local storage to speed up site functionality. Customized content We use cookies and similar technologies to customize your experience on our Services. For example, we may use cookies to remember previous searches so that when you return to our services, we can offer additional information that relates to your previous search. Plugins on and off LinkedIn We use cookies and similar technologies to enable LinkedIn plugins both on and off the LinkedIn sites. For example, our plugins, including the "Apply with LinkedIn" button or the "Share" button may be found on LinkedIn or third-party sites, such as the sites of our customers and partners. Our plugins use cookies and other technologies to provide analytics and recognize you on LinkedIn and third-party sites. If you interact with a plugin (for instance, by clicking "Apply"), the plugin will use cookies to identify you and initiate your request to apply. You can learn more about plugins in our Privacy Policy . Advertising Cookies and similar technologies help us show relevant advertising to you more effectively, both on and off our Services and to measure the performance of such ads. We use these technologies to learn whether content has been shown to you or whether someone who was presented with an ad later came back and took an action (e.g., downloaded a white paper or made a purchase) on another site. Similarly, our partners or service providers may use these technologies to determine whether we've shown an ad or a post and how it performed or provide us with information about how you interact with ads. We may also work with our customers and partners to show you an ad on or off LinkedIn, such as after you’ve visited a customer’s or partner’s site or application. These technologies help us provide aggregated information to our customers and partners. For further information regarding the use of cookies for advertising purposes, please see Sections 1.4 and 2.4 of the Privacy Policy . As noted in Section 1.4 of our Privacy Policy, outside Designated Countries , we also collect (or rely on others who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. For further information, please see Section 1.4 of the Privacy Policy . Analytics and research Cookies and similar technologies help us learn more about how well our Services and plugins perform in different locations. We or our service providers use these technologies to understand, improve, and research products, features and services, including as you navigate through our sites or when you access LinkedIn from other sites, applications or devices. We or our service providers, use these technologies to determine and measure the performance of ads or posts on and off LinkedIn and to learn whether you have interacted with our websites, content or emails and provide analytics based on those interactions. We also use these technologies to provide aggregated information to our customers and partners as part of our Services. If you are a LinkedIn member but logged out of your account on a browser, LinkedIn may still continue to log your interaction with our Services on that browser until the expiration of the cookie in order to generate usage analytics for our Services. We may share these analytics in aggregate form with our customers. What third parties use these technologies in connection with our Services? Third parties such as our customers, partners and service providers may use cookies in connection with our Services. For example, third parties may use cookies in their LinkedIn pages, job posts and their advertisements on and off LinkedIn for their own marketing purposes. For an illustration, please visit LinkedIn’s Help Center . Third parties may also use cookies in connection with our off-site Services, such as LinkedIn ad services. Third parties may use cookies to help us to provide our Services. We may also work with third parties for our own marketing purposes and to enable us to analyze and research our Services. Your Choices You have choices on how LinkedIn uses cookies and similar technologies. Please note that if you limit the ability of LinkedIn to set cookies and similar technologies, you may worsen your overall user experience, since it may no longer be personalized to you. It may also stop you from saving customized settings like login information. Opt out of targeted advertising As described in Section 2.4 of the Privacy Policy , you have choices regarding the personalized ads you may see. LinkedIn Members can adjust their settings here . Visitor controls can be found here . Some mobile device operating systems such as Android provide the ability to control the use of mobile advertising IDs for ads personalization. You can learn how to use these controls by visiting the manufacturer’s website. We do not use iOS mobile advertising IDs for targeted advertising. Browser Controls Most browsers allow you to control cookies through their settings, which may be adapted to reflect your consent to the use of cookies. Further, most browsers also enable you to review and erase cookies, including LinkedIn cookies. To learn more about browser controls, please consult the documentation that your browser manufacturer provides. What is Do Not Track (DNT)? DNT is a concept that has been promoted by regulatory agencies such as the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites by using browser settings. As such, LinkedIn does not generally respond to “do not track” signals. Other helpful resources To learn more about advertisers’ use of cookies, please visit the following links: Internet Advertising Bureau (US) European Interactive Digital Advertising Alliance (EU) Internet Advertising Bureau (EU) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T09:29:15 |
http://tom.preston-werner.com/ | Tom Preston-Werner Tom Preston-Werner home Blog Posts 22 Oct 2025 » Announcing PWV Fund I 30 May 2023 » RedwoodJS’ Next Epoch: All In on React Server Components 23 May 2022 » Major Version Numbers are Not Sacred 07 Apr 2022 » Introducing the Redwood Startup Fund 04 Apr 2022 » Announcing RedwoodJS 1.0 and $1M Funding 15 Jun 2020 » Committing $250k this Year to Racial Justice Efforts 23 Mar 2020 » We Are Giving $1M Toward San Francisco COVID-19 Response 04 Mar 2020 » Joining the Netlify Board to Help Shape the Future of the JAMstack 10 Nov 2016 » Snyk - Automatically Scan and Fix Ruby and Nodejs Vulnerabilities 19 Jun 2015 » Replicated - An Easier Path from SaaS to Enterprise 21 Apr 2014 » Farewell GitHub, Hello Immersive Computing 22 Nov 2011 » Open Source (Almost) Everything 03 May 2011 » Rejected Bio from The Setup 29 Mar 2011 » Ten Lessons from GitHub's First Year 11 Dec 2010 » Designer, Architect, Developer 18 Oct 2010 » Optimize for Happiness 23 Aug 2010 » Readme Driven Development 11 May 2010 » TomDoc - Reasonable Ruby Documentation 19 May 2009 » The Git Parable 17 Nov 2008 » Blogging Like a Hacker 03 Nov 2008 » How to Meet Your Next Cofounder 27 Oct 2008 » Looking back on Selling Gravatar to Automattic 18 Oct 2008 » How I Turned Down $300,000 from Microsoft to go Full-Time on GitHub Highlighted Media 02 Sep 2013 » Article: WIRED - GitHub Is Going Mainstream 09 Nov 2011 » Video: RubyConf Argentina - Optimizing For Happiness 01 Oct 2011 » Video: RubyConf - GitHub Flavored Ruby 23 Nov 2010 » Video: Erlang Factory - Mastering Git Basics Other Interviews, Talks, Etc 12 Sep 2013 » Video: Fox Business News interview 02 Sep 2013 » Article: WIRED - GitHub Is Going Mainstream 25 Jul 2013 » Video: O'Reilly Media - OSCON 2013 Interview 28 Dec 2012 » Article: NYTimes - Dreams of ‘Open’ Everything 20 Oct 2012 » Video: Startup School 2012 - People, Product, Philosophy 27 Sep 2012 » Video (Panel): Orrick - How to Build a Great Startup Culture 18 Jun 2012 » Article: GigaOm - 10 Innovators Changing the Game for Internet Infrastructure 02 Dec 2011 » Video: Northern Lights Conference - Leveling Up 12 Nov 2011 » Slides: RubyConf Uruguay - GitHub Flavored Ruby 09 Nov 2011 » Slides: RubyConf Argentina - Optimizing For Happiness 14 Apr 2011 » Video: ACCU Conference - Optimizing For Happiness 09 Apr 2011 » SitePoint Podcast: Social Coding with GitHub’s Tom Preston-Werner 10 Feb 2011 » Video: NCAR SEA: Unlocking the Secrets of Git 12 Jan 2011 » Maestros del Web: Tom Preston-Werner fundador de GitHub 11 Nov 2010 » Video: RubyConf 2010 - The Road from Ruby Hacker to Entrepreneur 16 Oct 2010 » Lambdaphant interview with Tom Preston-Werner 16 Oct 2010 » Video: Startup School - Optimize for Happiness 16 Sep 2010 » Video: @mail.ru Office Presentation 14 Sep 2010 » Video: @mail.ru Tech Forum in Moscow 11 Sep 2010 » Photo: FunConf Speech in Ireland 07 Sep 2010 » SchnitzelConf: Virality and Community 27 Aug 2010 » Video: Lone Star Ruby Conf Keynote 16 Aug 2010 » InfoQ: Erlang Factory Interview - Tom Preston-Werner and Kenneth Lundin 03 Aug 2010 » 37signals: Bootstrapped, Profitable, & Proud: GitHub 17 Jun 2010 » WebPulp.tv: Interview with GitHub CTO Tom Preston-Werner 27 Apr 2010 » The Next Web 2010: Interview about Gravatar and Online Reputation 27 Apr 2010 » TNW 2010: What I Learned From Bootstrapping a Side Project Into GitHub 19 Nov 2009 » RubyConf 2009 Talk: BERT and Ernie: Scaling your Ruby site with Erlang 21 Aug 2009 » Linux Magazine: The GitHub Hall of Fame - Jekyll Review 27 Jul 2009 » Yahoo Developer Talk: Git, GitHub, and Social Coding 22 Jul 2009 » Envy Labs: 5 Days of OSCON Interview 30 Apr 2009 » Erlang Factory 09: Mixing Erlang and Ruby with Erlectricity 23 Apr 2009 » BusinessWeek: Best Young Tech Entrepreneurs of 2009 17 Jan 2009 » RubyFringe 2008: Conceptual Algorithms 09 Oct 2008 » InfoQ: Tom Preston-Werner on Powerset, GitHub, Ruby and Erlang 11 Jul 2008 » Rubyology 65: Powerset Stars 2 of 2 05 Jul 2008 » Rubyology 65: Powerset Stars 1 of 2 13 Jun 2008 » Web 2.0 Show: GitHub (Tom Preston-Werner & Chris Wanstrath) 02 Jun 2008 » Gregg Pollack: Dave Fayram and Tom Preston-Werner at RailsConf 29 May 2008 » RailsConf 08: Two talks 18 Oct 2007 » Gravatar Blog: Automattic Acquires Gravatar 16 Aug 2007 » Steve Newcomb Blog: Interview with Tom Preston-Werner 26 Dec 2006 » WordPress Podcast: Interview with Tom Werner 02 Apr 2005 » JoshuaInk: Seven and a half questions for Tom Werner Noteworthy Open Source Projects and Specifications Jekyll: A simple, blog aware, static site generator (used for this site). Semantic Versioning: A meaningful method for incrementing version numbers. TOML: Tom's Obvious, Minimal Language. God: Ruby process monitoring framework with easy extensibility. Chronic: Ruby natural language date/time parser. TomDoc: Code documentation for humans. ProxyMachine: Layer 7 routing proxy in Ruby with Event Machine. Gollum: A simple, Git-powered wiki with a sweet API and local frontend. Grit: Object oriented Ruby bindings for Git (used by GitHub). Ernie: Ruby/Erlang Hybrid BERT-RPC server. Tom Preston-Werner Cofounder of GitHub , Chatterbug tom@mojombo.com github.com/mojombo twitter.com/mojombo | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Ftencentglobal-cloud-native-database-tdsqlc%3FviewConnections%3Dtrue&trk=products_details_guest_face-pile-cta | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/mogi-i-o-liveu/#main-content | Liveu | LinkedIn Skip to main content LinkedIn Mogi I/O : OTT/Podcast/Short Video Apps for you in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Liveu Live Streaming Software by Mogi I/O : OTT/Podcast/Short Video Apps for you See who's skilled in this Add as skill Contact us Report this product About Reach millions of users, with effortless and lightweight streams accessible anywhere! Media Products media viewer No more previous content Liveu Reach millions of users, with effortless and lightweight streams accessible anywhere! No more next content Similar products Cloudflare Stream Cloudflare Stream Live Streaming Software Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Tango Tango Live Streaming Software BOCC BOCC Live Streaming Software Media Services Live Media Services Live Live Streaming Software Kaltura AI Video Experience Cloud Kaltura AI Video Experience Cloud Live Streaming Software Sign in to see more Show more Show less Mogi I/O : OTT/Podcast/Short Video Apps for you products MOTT MOTT OTT Platforms Photu Photu Stock Photo Websites Videu Videu Video Hosting Platforms LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Ftencentglobal-tencent-effect-sdk%2F&fromSignIn=true&trk=products_details_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://opensource.guide/id/how-to-contribute/ | Bagaimana Berkontribusi pada Open Source | Open Source Guides Tentang Kontribusi العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Bagaimana Berkontribusi pada Open Source Ingin berkontribusi pada open source? Sebuah panduan untuk melakukan kontribusi open source, untuk pemula dan veteran. Daftar Isi Mengapa berkontribusi pada open source? Apa artinya berkontribusi Berorientasi pada proyek baru Menemukan sebuah proyek untuk melakukan kontribusi Bagaimana mengajukan kontribusi Apa yang terjadi setelah Anda mengajukan sebuah kontribusi Mengapa berkontribusi pada open source? Bekerja pada [freenode] membantu saya mendapatkan banyak ketrampilan yang saya gunakan pada pembelajaran di universitas dan pekerjaan saya nantinya. Saya pikir bekerja pada proyek open source membantu saya sebanyak saya membantu proyek itu sendiri.! — @errietta, “Why I love contributing to open source software” Berkontribusi pada open source bisa jadi merupakan cara yang bermanfaat untuk belajar, mengajar, dan membangun pengalaman pada segala ketrampilan yang dapat Anda bayangkan. Mengapa orang-orang berkontribusi pada open source? Banyak alasannya! Meningkatkan ketrampilan yang sudah ada Baik pemrograman, perancangan antar muka, desain grafis, menulis, maupun mengelola, jika Anda mencari tempat berlatih, terdapat tugas bagi Anda pada proyek open source. Bertemu orang yang tertarik pada hal yang sama Proyek open source dengan komunitas yang hangat membuat orang-orang kembali selama bertahun-tahun. Banyak orang membentuk pertemanan jangka panjang melalui partisipasi mereka pada open source, baik pertemuan pada konferensi atau chat tengah malam tentang burrito. Mencari mentor dan mengajarkan ke pihak lain Bekerja dengan banyak orang pada proyek berarti Anda harus menjelaskan bagaimana Anda melakukan segala sesuatu, sekaligus meminta orang lain untuk bantuan. Kegiatan belajar dan mengajar bisa menjadi aktivitas yang menyenangkan bagi semua orang yang terlibat. Membangun koleksi publik yang membantu Anda mengembangkan reputasi (dan karir) Secara definisi, semua pekerjaan open source bersifat publik, artinya Anda mendapatkan contoh gratis untuk dibawa kemana saja sebagai demonstrasi tentang apa saja yang dapat Anda lakukan. Belajar ketrampilan tentang orang Open source menawarkan kesempatan untuk belajar ketrampilan kepemimpinan dan manajemen, seperti menyelesaikan konflik, mengelola sekelompok orang, dan memprioritaskan pekerjaan. Memberdayakan untuk membuat perubahan, meskipun kecil Anda tidak perlu menjadi kontributor jangka panjang untuk menikmati partisipasi pada open source. Apakah Anda melihat sebuah kesalahan ketik pada website, dan berharap seseorang akan memperbaikinya? Pada proyek open source, Anda bisa melakukannya. Open source membantu orang merasa memiliki hak atas hidup mereka dan bagaimana mereka merasakan bahwa dunia, dan segala isinya sangatlah memuaskan. Apa artinya berkontribusi Jika Anda merupakan kontributor open source yang baru, proses ini bisa jadi menakutkan. Bagaimana Anda menemukan proyek yang sesuai? Bagaimana jika Anda tidak tahu bagaimana membuat kode program? Bagaimana jika terjadi kesalahan? Tidak perlu khawatir! Terdapat banyak cara untuk bisa ikut terlibat pada proyek open source, dan beberapa tips akan membantu Anda memaksimalkan pengalaman Anda. Anda tidak perlu memberikan kontribusi dalam bentuk kode Kesalahpahaman yang sering terjadi tentang berkontribusi pada open source adalah Anda harus memberikan kontribusi dalam bentuk kode. Kenyataannya, seringkali banyak bagian lain dari proyek yang seringkali terabaikan atau diabaikan . Anda bisa memberikan bantuan besar bagi proyek dengan menawarkan diri untuk jenis kontribusi semacam ini. Saya menjadi terkenal karena pekerjaan saya pada CocoaPods, tetapi banyak orang tidak tahu bahwa saya tidak melakukan pekerjaan yang berarti pada perangkat CocoaPods itu sendiri. Waktu saya pada proyek lebih banyak dihabiskan untuk melakukan kegiatan seperti dokumentasi dan pencitraan. — @orta, “Moving to OSS by default” Meskipun Anda suka untuk menulis kode program, kontribusi jenis lain merupakan cara yang baik untuk bisa berpartisipasi pada proyek dan bertemu dengan anggota komunitas lainnya. Membangun hubungan tersebut akan memberikan Anda kesempatan untuk bekerja pada bagian lain dari proyek. Apakah Anda suka merencanakan kegiatan? Mengelola workshop atau acara pertemuan tentang proyek, seperti yang dilakukan @fzamperin untuk NodeSchool Mengelola konferensi sebuah proyek (jika ada) Membantu anggota komunitas menemukan konferensi yang sesuai dan mengirimkan proposal untuk berbicara Apakah Anda suka mendesain? Restrukturisasi layout untuk meningkatkan usabilitas proyek Melakukan penelitian pengguna untuk menata ulang dan meningkatkan navigasi atau menu proyek, seperti yang disarankan Drupal Membuat panduan untuk membantu proyek memiliki desain visual yang konsisten Membuat hasil seni untuk pakaian atau logo baru, seperti kontributor hapi.js Apakah Anda suka menulis? Menulis dan meningkatkan dokumentasi proyek Buatlah sebuah folder contoh yang menunjukkan bagaimana proyek dapat digunakan Memulai laporan berkala untuk proyek atau buat hal-hal penting dari mailing list Menulis tutorial untuk proyek, seperti kontributor pypa Menulis terjemahan untuk dokumentasi proyek Serius, [dokumentasi] sangatlah penting. Dokumentasi sejauh ini sudah sangat bagus dan merupakan fitur utama dari Babel. Terdapat beberapa bagian yang bisa dikembangkan dan bahkan penambahan sebuah paragraf disini dan disana akan sangat dihargai. — @kittens, “Call for contributors” Apakah Anda suka mengelola? Menghubungkan masalah-masalah yang duplikat dan memberikan label pada masalah untuk menjaga pengelolaan Menyarankan menghapus laporan masalah yang lama, seperti yang dilakukan @nzakas untuk eslint Menanyakan pertanyaan klarifikasi pada laporan masalah yang baru saja dibuat untuk diskusi kedepannya Apakah Anda suka membua kode program? Mencari laporan masalah yang ingin diselesaikan, seperti yang dilakukan @dianjin untuk Leaflet Bertanya jika Anda hendak membantu menuliskan fitur baru Melakukan otomatisasi setup proyek Meningkatkan perlengkapan dan pengujian Apakah Anda suka membantu orang lain? Menjawab pertanyaan tentang proyek, pada (misalnya) Stack Overflow ( seperti contoh Postgres ini ) atau reddit Menjawab pertanyaan pada permasalahaan terbuka Membantu memoderasi halaman diskusi atau chanel diskusi Apakah Anda suka membantu orang lain dalam membuat program? Me-review kode dari pengajuan orang lain Menulis tutorial bagaimana proyek bisa digunakan Menawarkan diri untuk menjadi mentor bagi kontributor lainnya, seperti yang dilakukan @ereichert untuk @bronzdoc pada Rust Anda tidak harus bekerja pada proyek perangkat lunak! Meskipun “open source” seringkali merujuk pada perangkat lunak, Anda bisa berkolaborasi pada segala sesuatu. Terdapat buku, resep makanan, daftar, dan kelas yang dapat dikembangkan sebagai proyek open source. Sebagai contoh: @sindresorhus menghasilkan daftar “awesome” @h5bp mengelola daftar pertanyaan potensial untuk wawancara bagi kandidat developer front-end @stuartlynn dan @nicole-a-tesla membuat kumpulan fakta lucu tentang puffin Meskipun Anda seorang pengembang perangkat lunak, bekerja pada proyek dokumentasi bisa membantu Anda untuk memulai pada open source. Seringkali bekerja pada proyek yang tidak melibatkan kode tidak terlalu menakutkan dan proses kolaborasi ini akan membangun rasa percaya diri dan pengalaman Anda. Berorientasi pada proyek baru Jika Anda mengunjungi issue tracker dan tampaknya membingungkan, hal itu terjadi bukan hanya kepada Anda saja. Perangkat ini membutuhkan banyak pemahaman implisit, tetapi orang lain mampu membantu Anda dalam mengeksplorasi dan Anda bisa bertanya kepada mereka. — @shaunagm, “How to Contribute to Open Source” Untuk aktivitas yang lebih dari sekedar kesalahan penulisan, berkontribusi pada open source seperti berjalan pada sebuah kelompok orang asing pada sebuah pesta. Jika Anda berbicara tentang hewan llamas, sedangkan mereka sedang membicarakan tentang ikan mas, mungkin mereka akan memandang Anda dengan aneh. Sebelum memberikan masukan, pelajari bagaimana membaca situasi ruangan. Dengan melakukan hal ini akan meningkatkan peluang ide Anda akan dilihat dan didengarkan. Anatomi proyek open source Setiap komunitas open source memiliki perbedaan. Menghabiskan waktu bertahun-tahun pada satu proyek open source berarti Anda terbiasa pada satu proyek open source. Dengan berpindah pada proyek yang berbeda maka Anda akan mendapati bahwa kosa kata, norma, dan gaya komunikasi yang digunakan sangatlah berbeda. Meski demikian, banyak proyek open source mengikuti struktur organisasi yang sama. Memahami perbedaan peran komunitas yang berbeda-beda dan proses secara luas akan membantu Anda untuk beradaptasi dengan setiap proyek baru. Proyek open source pada umumnya memiliki beberapa jenis orang sebagai berikut: Pencipta (Author): Orang atau organisasi yang menciptakan proyek Pemilik (Owner): Orang atau organisasi yang memiliki kepemilikan administratif terhadap organisasi atau repositori (tidak selalu sama dengan pencipta awal) Pengelola (Maintainers): Kontributor yang bertanggung jawab untuk menggerakan visi dan mengelola aspek organisasi dari proyek. (Mereka juga bisa merupakan pencipta atau pemilik dari proyek.) Kontributor (Contributors): Semua orang yang telah mengkontribusikan sesuatu kepada proyek. Anggota Komunitas (Community Members): Orang-orang yang menggunakan proyek. Mereka mungkin aktif pada diskusi atau mengungkapkan opini mereka pada arah sebuah proyek. Proyek yang lebih besar mungkin memiliki sub komite atau kelompok kerja yang berfokus pada tugas yang berbeda-beda, seperti peralatan, pengujian, moderasi komunitas, dan pengelola kegiatan. Lihat pada website proyek untuk halaman “anggota”, atau pada repositori untuk dokumentasi organisasi, untuk menemukan informasi ini. Sebuah proyek juga memiliki dokumentasi. Dokumentasi ini biasanya ditempatkan pada posisi teratas dari sebuah repositori. LICENSE: Secara definisi, setiap proyek open source harus memiliki sebuah lisensi open source . Jika sebuah proyek tidak memiliki lisensi, maka proyek tersebut bukan bersifat open source. README: Dokumen README adalah manual instruksi yang menyambut anggota komunitas baru pada sebuah proyek. Dokumen ini juga menjelaskan kenapa proyek ini berguna dan bagaimana untuk memulainya. CONTRIBUTING: Jika README membantu orang-orang menggunakan proyek, dokumentasi kontribusi membantu orang-orang untuk berkontribusi pada proyek. Dokumen ini menjelaskan jenis kontribusi seperti apa yang diperlukan dan bagaimana cara kerja dari proses kontribusinya. Meskipun tidak setiap proyek memiliki dokumen CONTRIBUTING, keberadaan dokumen ini menandakan bahwa proyek ini menerima kontribusi. CODE_OF_CONDUCT: Dokumen kode etik ( code of conduct ) menentukan aturan dasar bagi perilaku partisipan dan membantu memfasilitasi lingkungan yang kondusif dan bersahabat. Meskipun tidak setiap proyek memiliki dokumen CODE_OF_CONDUCT, keberadaan dokumen ini menandakan bahwa proyek ini menerima kontribusi. Dokumentasi lainnya: Mungkin terdapat dokumentasi tambahan, seperti tutorial, panduan, atau kebijakan lainnya, terutama pada proyek yang lebih besar. Akhirnya, proyek open source menggunakan peralatan berikut untuk mengelola diskusi. Membaca dari arsip akan memberikan gambaran tentang bagaimana komunitas berpikir dan bekerja. Issue tracker: Dimana orang-orang mendiskusikan laporan masalah yang berkaitan dengan proyek. Pull requests: Dimana orang-orang mendiskusikan dan me-review perubahan yang sedang dikerjakan. Forum diskusi atau mailing list: Beberapa proyek mungkin menggunakan media ini untuk topik diskusi (misalnya. “Bagaimana saya …“ atau “Apakah pendapat Anda tentang …“ daripada laporan kesalahan atau pengajuan fitur baru). Beberapa proyek menggunakan issue tracker untuk semua diskusi. Media chat: Beberapa proyek menggunakan media chat (seperti Slack atau IRC) untuk diskusi sehari-hari, kolaborasi, dan pertukaran yang bersifat cepat. Menemukan sebuah proyek untuk melakukan kontribusi Setelah Anda paham bagaimana proyek open source bekerja, sekarang saatnya untuk menemukan sebuah proyek untuk berkontribusi! Jika Anda belum pernah berkontribusi ke open source sebelumnya, ambil saran dari presin Amerika Serikat John F. Kennedy, yang mengatakan demikian , “(Jangan tanyakan apa yang bisa dilakukan negara kepada dirimu - tanyakan apa yang bisa engkau lakukan untuk negaramu) - Ask not what your country can do for you - ask what you can do for your country.” Berkontribusi ke open source bisa terjadi pada semua tingkatan, pada semua bagian proyek. Anda tidak perlu berpikir berlebihan tentang apa kontribusi pertama Anda atau bagaimana bentuknya. Mulailah dengan proyek yang sudah Anda gunakan, atau ingin Anda gunakan. Proyek dimana Anda akan aktif berkontribusi didalamnya adalah proyek dimana Anda akan selalu datang kembali kepadanya. Didalam proyek-proyek tersebut, setiap kali Anda mendapati tentang segala sesuatu yang bisa ditingkatkan atau berbeda, lakukan berdasarkan insting Anda. Open source bukanlah klub ekslusif; Open source dibuat oleh orang-orang seperti Anda. “Open source” hanyalah istilah keren untuk menadai bahwa masalah yang ada di dunia sebagai sesuatu yang bisa diperbaiki. Anda bisa melihat dokumen README dan menemukan tautan yang tidak valid atau kesalahan pengetikkan. Atau Anda sebagai pengguna baru dan melihat bahwa ada yang salah, atau sebuah laporan dimana Anda rasa penting untuk didokumentasikan. Daripada mengabaikannya, atau meminta orang lain untuk memperbaikinya, cari tahu apakah Anda bisa membantu dengan ikut serta didalamnya. Itulah makna sesungguhnya dari open source! 28% dari kontribusi umum pada open source adalah berupa dokumentasi, seperti kesalahan pengetikkan, pemformatan ulang, atau menuliskan terjemahan. Anda juga bisa menggunakan salah satu dari beberapa sumber daya berikut untuk mencari dan berkontribusi pada proyek baru: GitHub Explore Open Source Friday First Timers Only CodeTriage 24 Pull Requests Up For Grabs First Contributions SourceSort OpenSauced Daftar sebelum Anda berkontribusi Ketika Anda telah menemukan sebuah proyek dimana Anda hendak melakukan kontribusi, lakukan pencarian secara cepat untuk memastikan proyek tersebut sesuai untuk menerima kontribusi. Jika tidak, usaha keras Anda mungkin tidak akan mendapatkan respon. Berikut adalah daftar yang bisa digunakan untuk mengevaluasi apakah sebuah proyek sesuai untuk kontributor baru. Memenuhi definisi open source Apakah memiliki lisensi? Biasanya terdapat dokumen bernama LICENSE pada bagian atas dari repositori. Proyek secara aktif menerima kontribusi Lihat pada aktivitas commit pada branch master. Pada GitHub, Anda bisa melihat informasi ini pada homepage repositori. Kapan commit terakhir ? Berapa banyak kontributor yang dimiliki proyek? Seberapa sering orang melakukan commit? (Pada GitHub, Anda bisa mendapatkan informasi ini dengan memilih menu "Commits" pada bagian atas.) Berikutnya, lihat pada laporan masalah yang dihadapi pada proyek. Berapa banyak laporan masalah yang masih belum diselesaikan? Apakah pengelola merespon dengan cepat pada sebuah laporan masalah baru? Apakah terdapat diskusi aktif pada setiap laporan masalah yang ada? Apakah laporan masalah tersebut muncul baru-baru ini? Apakah laporan masalah yang ada sudah diselesaikan? (Pada GitHub, klik tab "closed" pada halaman Issues untuk melihat laporan masalah yang sudah terselesaikan.) Sekarang lakukan hal yang sama untuk pull request pada proyek. Berapa banyak pull request pada proyek? Apakah pengelola merespon dengan cepat terhadap pull request baru? Apakah terdapat diskusi aktif pada pull request? Apakah pull request tersebut muncul baru-baru ini? Kapan pull request diterima? (Pada GitHub, klik tab "closed" pada halaman Pull Requests untuk melihat PR yang sudah diselesaikan.) Proyek menyambut Sebuah proyek yang bersahabat dan menyambut menandai bahwa mereka sangat menerima kontributor baru. Apakah pengelola menanggapi pertanyaan pada laporan masalah dengan sangat membantu? Apakah orang-orang bersahabat pada laporan masalah, forum diskusi, dan chat (misalnya. IRC atau Slack)? Apakah dilakukan review terhadap pull request? Apakah pengelola berterima kasih kepada orang lain atas kontribusinya? Setiap kali Anda melihat diskusi yang panjang, amati respon dari pengembang inti di bagian akhir dari diskusi. Apakah mereka meringkasnya secara konstruktif dan mengambil langkah-langkah untuk mendapatkan kesimpulan tanpa mengabaikan sopan santun? Jika Anda melihat banyak perdebatan yang tidak konstruktif ( flame war ), biasanya merupakan sebuah tanda bahwa energi dihabiskan untuk berargumentasi dibandingkan untuk pengembangan proyek. — @kfogel, Producing OSS Bagaimana mengajukan kontribusi Anda telah menemukan sebuah proyek yang Anda sukai, dan Anda siap untuk membuat sebuah kontribusi. Akhirnya! Berikut adalah langkah-langkah untuk menjadikan kontribusi Anda di jalan yang benar. Berkomunikasi secara efektif Apakah Anda merupakan kontributor atau mencoba untuk bergabung dengan sebuah komunitas, bekerja dengan orang lain merupakan salah satu keahlian paling penting yang perlu diasah dalam dunia open source. [Sebagai kontributor baru,] saya menyadari bahwa saya perlu bertanya jika ingin menutup sebuah laporan masalah. Saya mengamati kode program. Setelah saya mengetahui situasinya, saya bertanya untuk pengarahan lebih lanjut. Dan akhirnya! Saya berhasil menutup sebuah laporan masalah setelah mendapatkan semua informasi relevan yang saya butuhkan. — @shubheksha, A Beginner’s Very Bumpy Journey Through The World of Open Source Sebelum Anda membuka sebuah laporan masalah atau pull request, atau bertanya pada media chat, perhatikan beberapa poin berikut untuk membantu ide Anda secara efektif. Berikan konteks. Bantu orang lain untuk memahami kondisinya. Jika Anda menjumpai sebuah kesalahan, jelaskan apa yang hendak Anda lakukan dan bagaimana mengulangi kesalahan tersebut. Jika Anda menyarankan sebuah ide baru, jelaskan kenapa Anda pikir itu merupakan ide yang baik untuk proyek (tidak hanya untuk Anda!). 😇 “X tidak berfungsi ketika saya melakukan Y” 😢 “X rusak! Tolong perbaiki.” Lakukan pekerjaan rumah Anda sebelumnya. Tidak masalah untuk tidak mengetahui beberapa hal, tetapi tunjukan bahwa Anda telah berusaha. Sebelum bertanya untuk meminta bantuan, pastikan untuk melihat dokumen README, dokumentasi, laporan masalah (terbuka atau tertutup), mailing list, dan cari Internet untuk sebuah jawaban. Orang-orang akan menghargai ketika Anda menunjukkan bahwa Anda berusaha untuk belajar. 😇 “Saya tidak yakin bagaimana mengimplementasikan X. Saya telah melihat dokumen bantuan dan tidak menemukan apapun.” 😢 “Bagaimana saya melakukan X?” Buatlah permintaan singkat dan langsung. Seperti halnya mengirimkan sebuah email, setiap kontribusi, sekecil apapun atau sepenting apapun, akan membutuhkan orang lain untuk me-reviewnya. Banyak proyek memiliki lebih banyak permintaan dibandingkan jumlah orang yang ada untuk membantu. Pastikan permintaan Anda jelas. Anda akan mendapatkan peluang lebih tinggi dimana seseorang akan ada untuk membantu Anda. 😇 “Saya ingin menulis tutorial API.” 😢 “Saya sedang mengemudi di jalan tol di suatu hari dan berhenti untuk mengisi bahan bakar, lalu saya mendapatkan ide cemerlang yang seharusnya kita lakukan, tetapi sebelum saya menjelaskan hal itu, ijinkan saya untuk menunjukkan kepada Anda…“ Buat semua komunikasi terbuka secara publik. Meskipun hal ini sangat menarik, hindari menghubungi pengelola secara pribadi kecuali Anda perlu membagikan informasi yang bersifat sensitif (misalnya masalah keamanan atau pelanggaran berat). Ketika Anda membuat semua komunikasi terbuka secara publik, banyak orang bisa belajar dan mendapatkan manfaat dari pertukaran informasi Anda. Diskusi itu sendiri bisa menjadi sebuah kontribusi. 😇 (sebagai komentar) “@-maintainer Hallo! Bagaimana saya harus melanjutkan untuk PR ini?” 😢 (sebagai email) “Hallo, maaf menganggu Anda melalui email, tetapi saya ingin tahu apakah Anda ingin melakukan review terhadap PR saya” Tidak masalah untuk bertanya (tetapi harap sabar!). Setiap orang pernah menjadi orang baru pada sebuah proyek, dan bahkan kontributor yang berpengalaman sekalipun perlu memahami kondisi ketika mereka melihat pada sebuah proyek baru. Dengan kondisi yang sama, bahkan pengelola yang sudah lama sekalipun tidak selalu memahami dengan setiap bagian dari proyek. Berikan kesabaran yang sama seperti Anda mengharapkan mereka sabar dengan Anda. 😇 “Terima kasih karena telah melihat kesalahan ini. Saya mengikuti petunjuk Anda. Berikut hasil keluarannya.” 😢 “Kenapa Anda tidak bisa memperbaiki masalah saya? Bukankah ini proyek Anda?” Hargai keputusan komunitas. Ide Anda mungkin berbeda dengan prioritas atau visi komunitas. Mereka mungkin menawarkan masukan atau memutuskan untuk tidak melanjutkan ide Anda. Meskipun sebaiknya Anda mendiskusikan dan mencoba mencari titik temu, pengelola harus menanggung tanggung jawab atas keputusan Anda jauh lebih lama dibandingkan Anda. Jika Anda tidak setuju dengan mereka, Anda tetap bisa bekerja pada fork Anda sendiri atau memulai proyek Anda sendiri. 😇 “Saya kecewa Anda tidak bisa mendukung kasus saya, tetapi seperti yang telah Anda jelaskan, masalah itu hanya akan berdampak pada sebagian kecil pengguna, dan saya bisa memahami. Terima kasih telah mendengarkan.” 😢 “Kenapa Anda tidak mendukung kasus saya? Hal ini tidak bisa saya terima!” Diatas itu semua, pertahankan kualitas. Open source terbentuk dari kolaborator dari seluruh penjuru dunia. Konteks menjadi hilang dalam berbagai bahasa, budaya, geografis, dan zona waktu. Lebih dari itu, komunikasi tertulis menjadikannya lebih susah untuk menyalurkan nada atau suasana hati. Selalu asumsikan niat baik dalam percapakan. Merupakan hal yang biasa untuk menolak sebuah ide secara halus, bertanya untuk konteks yang lebih lanjut, atau mengklarifikasi posisi Anda. Harap jadikan Internet tempat yang lebih baik dibandingkan ketika Anda menemukannya. Mengumpulkan konteks Sebelum melakukan apapun, pastikan bahwa ide Anda belum pernah didiskusikan sebelumnya. Baca dokumen README, laporan masalah (terbuka dan tertutup), mailing list, dan Stack Overflow. Anda tidak perlu menghabiskan waktu berjam-jam untuk mencari semua informasi, tetapi cukup lakukan pencarian secara cepat untuk beberapa istilah kunci. Jika Anda tidak bisa menemukan ide Anda dimanapun, Anda siap untuk bergerak. Jika proyek tersebut berada pada GitHub, Anda bisa berkomunikasi dengan membuka sebuah laporan masalah atau melakukan pull request: Laporan masalah (Issues) adalah seperti memulai percakapan atau diskusi Pull requests adalah untuk memulai pekerjaan pada sebuah solusi Untuk komunikasi yang ringan, seperti mengklarifikasi pertanyaan bagaimana, cobalah bertanya melalui Stack Overflow, IRC, Slack, atau media chat lainnya, jika ada. Sebelum Anda membuka sebuah laporan masalah atau melakukan pull request, periksa dokumen kontribusi proyek (biasanya pada dokumen bernama CONTRIBUTING, atau pada README), untuk melihat apakah Anda perlu mencantumkan informasi yang spesifik. Sebagai contoh, mereka mungkin meminta Anda untuk mengikuti sebuah template, atau mengharuskan Anda untuk menggunakan perangkat pengujian. Jika Anda hendak melakukan kontribusi yang cukup substansial, buatlah sebuah laporan masalah sebelum memulai bekerja. Sangatlah bermanfaat untuk mengamati proyek dalam kurun waktu tertentu (pada GitHub, Anda bisa memilih menu “Watch” untuk mendapatkan notifikasi dari semua percakapan), dan mengenal anggota komunitas, sebelum memulai pekerjaan yang belum tentu akan diterima. Anda akan belajar banyak dari proyek yang Anda gunakan secara aktif, “melihatnya” pada GitHub dan membaca semua laporan masalah dan PR. — @gaearon on joining projects Membuka laporan masalah Anda biasanya akan membuka sebuah laporan masalah pada situasi berikut: Melaporkan kesalahan yang tidak bisa Anda selesaikan sendiri Mendiskusikan topik tingkat tinggi atau ide (misalnya komunitas, visi, kebijakan) Mengajukan fitur baru atau ide proyek lainnya Tips untuk berkomunikasi pada laporan masalah: Jika Anda melihat laporan masalah yang masih terbuka yang hendak Anda selesaikan, berikan komentar Anda pada laporan masalah tersebut agar orang lain tahu. Dengan cara begitu, kecil kemungkinan orang lain akan mengerjakan hal yang sama. Jika sebuah laporan masalah baru saja dibuka beberapa saat yang lalu, ada kemungkinan bahwa laporan tersebut sedang dikerjakan oleh orang lain, atau sudah diperbaiki, sehingga berikan komentar untuk bertanya untuk konfirmasi sebelum memulai pekerjaan. Jika Anda membuka sebuah laporan masalah, tetapi menemukan jawabannya sendiri, berikan komentar untuk menginformasikan kepada orang lain, lalu tutup laporan masalah tersebut. Bahkan mendokumentasikan hasilnya juga merupakan sebuah kontribusi pada proyek. Membuka pull request Anda biasanya akan membuka sebuah pull request pada situasi berikut: Mengajukan perbaikan sederhana (misalnya kesalahan ketik, link tidak valid, atau kesalahan yang jelas terlihat) Mulai bekerja pada sebuah kontribusi yang sudah ditanyakan sebelumnya, atau yang sudah Anda diskusikan pada sebuah laporan masalah. Sebuah pull request tidak harus mencerminkan sebuah pekerjaan yang sudah selesai. Biasakan untuk membuka pull request di awal, sehingga orang lain bisa melihat atau memberikan masukan untuk perkembangan Anda. Tandai dengan “WIP” ( Work in Progress ) pada baris subject . Anda tetap bisa menambahkan commit lainnya. Jika proyek berada pada GitHub, berikut cara untuk membuka pull request: Fork repositori dan clone secara lokal. Hubungkan lokal Anda dengan repositori asli “ upstream ” dengan menambahkannya sebagai remote. Pull semua perubahan dari “upstream” secara berkala sehingga Anda selalu up to date dan ketika Anda mengajukan pull request Anda, merge conflict akan lebih jarang terjadi. (Lihat instruksi lebih detail disini .) Membuat sebuah branch untuk hasil pengeditan Anda. Referensikan laporan masalah yang berhubungan atau dokumentasi pendukung pada PR Anda (Misalnya. “Menutup #37.”) Sertakan tangkapan layar sebelum dan sesudah jika perubahan Anda meliputi perubahan pada HTML/CSS. Tarik dan letakkan gambar citra pada bagian body dari pull request Anda. Uji perubahan Anda! Jalankan perubahan Anda terhadap pengujian jika ada dan buat uji baru jika diperlukan. Apapun kondisinya, pastikan perubahan Anda tidak merusak proyek yang sudah ada. Kontribusi sesuai dengan gaya proyek sesuai kemampuan Anda. Hal ini berarti menggunakan indentasi, titik koma, dan komentar yang berbeda seperti yang Anda lakukan pada repositori Anda sendiri, tetapi memudahkan bagi pengelola untuk melakukan merge dan orang lain untuk memahami dan mengelolanya di masa depan. Jika ini merupakan pull request pertama Anda, lihat Make a Pull Request , yang dibuat oleh @kentcdodds sebagai sumber panduan informasi gratis. Apa yang terjadi setelah Anda mengajukan sebuah kontribusi Anda melakukannya! Selamat karena telah menjadi kontributor open source. Kami berharap ini yang pertama untuk banyak orang. Setelah Anda mengajukan kontribusi Anda, salah satu hal berikut akan terjadi: 😭 Anda tidak mendapatkan respon. Semoga Anda menguji tanda-tanda aktivitas proyek sebelum memulai sebuah kontribusi. Bahkan pada proyek yang aktif, ada kemungkinan bahwa kontribusi Anda tidak akan mendapatkan respon. Jika Anda belum mendapatkan respon lebih dari satu minggu, sangatlah masuk akal untuk bertanya pada tempat yang sama, meminta orang lain untuk melakukan review. Jika Anda mengetahui orang yang tepat untuk melakukan review terhadap kontribusi Anda, Anda bisa menyebut mereka menggunakan @-kontak pada diskusi. Jangan menghubungi orang tersebut secara pribadi; harap diingat bahwa komunikasi publik sangatlah vital bagi proyek open source. Jika Anda bertanya secara sopan dan masih tidak ada yang merespon, ada kemungkinan tidak akan ada yang merespon. Ini bukan perasaan yang menyenangkan, tetapi jangan sampai membuat Anda kecewa. Hal ini terjadi pada siapapun juga Terdapat banyak alasan masuk akal kenapa Anda tidak mendapatkan respon, termasuk kondisi pribadi yang diluar kendali Anda. Cobalah untuk mencari proyek atau cara lain untuk berkontribusi. Hal ini merupakan alasan yang bagus untuk tidak menginvestasikan waktu terlalu lama dalam membuat kontribusi sebelum anggota komunitas yang lain merespon Anda. 🚧 Seseorang meminta perubahan terhadap kontribusi Anda Sangatlah normal dimana Anda diminta untuk membuat perubahan terhadap kontribusi Anda, apakah dalam bentuk masukan terhadap ruang lingkup ide Anda atau perubahan pada kode Anda. Ketika seseorang mengharapkan perubahan, berikan respon dengan cepat. Mereka telah meluangkan waktu untuk melakukan review terhadap kontribusi Anda. Membuka sebuah PR dan meninggalkannya merupakan contoh yang buruk. Jika Anda tidak tahu bagaimana cara membuat perubahan, lakukan pengamatan terhadap masalah, lalu bertanya jika Anda memerlukannya. Jika Anda tidak memiliki waktu untuk mengerjakan laporan masalah tersebut (misalnya jika diskusi telah berjalan selama berbulan-bulan, dan kondisi Anda sudah mengalami perubahan), berikan informasi kepada pengelola sehingga mereka tidak lagi mengharapkan adanya respon dari Anda. Mungkin terdapat orang lain yang akan mengambil alih. 👎 Kontribusi Anda tidak diterima. Kontribusi Anda mungkin bisa diterima atau tidak pada akhirnya. Semoga Anda tidak menghabiskan waktu terlalu banyak. Jika Anda tidak yakin kenapa tidak diterima, sangatlah masuk akal untuk menanyakan kepada pengelola untuk masukan dan klarifikasi. Meski demikian, Anda tetap harus menghargai keputusan akhir mereka. Jangan berdebat atau bahkan menyerang. Anda selalu diijinkan untuk melakukan fork dan bekerja pada versi Anda sendiri jika Anda tidak setuju. 🎉 Kontribusi Anda diterima. Hooray! Anda telah membuat kontribusi open source! Anda berhasil! Apakah Anda baru saja membuat kontribusi pertama Anda, atau Anda mencari cara baru untuk berkontribusi, kami berharap Anda terinsipirasi untuk mengambil sebuah tindakan. Meskipun jika kontribusi Anda tidak diterima, jangan lupa untuk mengucapkan terima kasih kepada pengelola yang meluangkan waktu untuk membantu Anda. Open source terbentuk oleh orang-orang seperti Anda: satu masalah, pull request, komentar, atau tos pada satu waktu. Kembali ke semua panduan Panduan yang relevan Memulai Proyek Open Source Pelajari lebih lanjut tentang dunia open source dan bersiap-siap untuk merilis proyek Anda sendiri. Membangun Komunitas yang Ramah Membangun komunitas yang mendorong orang lain untuk menggunakan, berkontribusi, dan mempromosikan proyek Anda. Scroll to Top Kontribusi Ingin memberikan masukan? Konten halaman ini bersifat terbuka. Bantu kami untuk melakukan penyempurnaan. Kontribusi Terus berhubungan Jadilah yang pertama untuk mendengar tentang tips dan sumber daya open source terbaru GitHub. Alamat Email fine print dengan oleh dan teman-teman | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/proxmox-ve/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | Proxmox Virtual Environment | LinkedIn Skip to main content LinkedIn Proxmox Server Solutions in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Proxmox Virtual Environment Server Virtualization Software by Proxmox Server Solutions See who's skilled in this Add as skill Learn more Report this product About Proxmox Virtual Environment (Proxmox VE) is is the leading open-source platform for all-inclusive enterprise virtualization. With the central web interface, you can easily run VMs and containers, manage software-defined storage and networking functionality, high-availability clustering, and multiple integrated out-of-the-box tools like backup/restore, live migration, replication, and the firewall. Enterprises use the powerful all-in-one solution to meet the core requirements of today’s modern data centers. Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Proxmox Server Solutions products Proxmox Backup Server Proxmox Backup Server Server Backup Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/tencentglobal-cloud-virtual-machine-cvm/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | Cloud Virtual Machine (CVM) | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloud Virtual Machine (CVM) Server Virtualization Software by Tencent See who's skilled in this Add as skill Learn more Report this product About Tencent Cloud Virtual Machine offers stable, secure, resilient, and high-performance cloud computing service Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
http://choosealicense.com/licenses/gpl-2.0/ | GNU General Public License v2.0 | Choose a License Home / Licenses GNU General Public License v2.0 GNU GPLv2 The GNU GPL is the most widely used free software license and has a strong copyleft requirement. When distributing derived works, the source code of the work must be made available under the same license. There are multiple variants of the GNU GPL, each with different requirements. Permissions Conditions Limitations Commercial use Distribution Modification Private use Disclose source License and copyright notice Same license State changes Liability Warranty GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. Copy license text to clipboard Suggest this license Make a pull request to suggest this license for a project that is not licensed . Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project’s community , and keep your communication with project maintainers friendly. How to apply this license Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Optional steps The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license. Add GPL-2.0-or-later (or GPL-2.0-only to disallow future versions) to your project’s package description, if applicable (e.g., Node.js , Ruby , and Rust ). This will ensure the license is displayed in package directories. If you would like your project to adopt the GPL-3.0’s cure provision, add the text of the GPL Cooperation Commitment to a file named COMMITMENT in the same directory as your GPL-2.0 license file. Source Who’s using this license? AliSQL Discourse Jellyfin About Terms of Service Help improve this page The content of this site is licensed under the Creative Commons Attribution 3.0 Unported License . Curated with ❤️ by GitHub, Inc. and You! | 2026-01-13T09:29:15 |
https://telegram.org/dl?tme=4a8e5c6cd1b47cd7e3_11033445630626473373 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebK Telegram WebA Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/cloudflare-workers/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click#main-content | Cloudflare Workers | LinkedIn Skip to main content LinkedIn Cloudflare in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloudflare Workers Server Virtualization Software by Cloudflare See who's skilled in this Add as skill Try now Report this product About Build your next application with Cloudflare Workers Media Products media viewer No more previous content Announcing Deploy to Cloudflare Workers We think Cloudflare Workers is the best serverless tool on the market, so we wanted to make it easier for developers to deploy projects and get started building cool stuff on the platform! Our new Deploy to Cloudflare Workers site is just that — a way for both new and experienced Workers users to deploy new serverless projects directly from GitHub. In just a few clicks, we'll configure and deploy the project for you, giving you a new GitHub repo to start hacking on your next great project! What Cloudflare Workers do? Building serverless applications with Cloudflare Workers' Cron Job Scheduler and Key Value Store Learn how to build an application with the the newly announced cron job scheduler, Cron Triggers, from Cloudflare Workers. In this demo, we will explain what Cron Triggers are, how to quickly get started using them, and how to write and deploy your own. We will also review how to integrate with Workers KV, our key value store that allows you to store data at the edge and retrieve it inside your Workers' project instead of sending that data to alternative platforms such as Postgres or Firebase. No more next content Featured customers of Cloudflare Workers npm, Inc. Software Development 11,912 followers DoorDash Software Development 1,437,130 followers 23andMe Non-profit Organizations 81,297 followers Timely IT Services and IT Consulting 5,725 followers Adobe Marketo Software Development 178,692 followers Cordial Software Development 48,215 followers MaxMind Technology, Information and Internet 2,991 followers Optimizely Software Development 167,115 followers Discord Software Development 467,975 followers Broadcom Semiconductor Manufacturing 608,798 followers Glossier, Inc. Personal Care Product Manufacturing 492,298 followers ProPublica Media Production 72,236 followers Show more Show less Similar products Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Cloudflare products Argo Smart Routing Argo Smart Routing Network Management Software Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare DNS Cloudflare DNS Managed DNS Services Software Cloudflare Load Balancing Cloudflare Load Balancing Load Balancing Software Cloudflare Registrar Cloudflare Registrar Managed DNS Services Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Cloudflare SSL / TLS Cloudflare SSL / TLS SSL Certificates Software Cloudflare WAF Cloudflare WAF Web Application Firewalls (WAF) Cloudflare Web Analytics Cloudflare Web Analytics Digital Analytics Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://telegram.org/dl?tme=aeadb06e26500b500b_13487137554482671773 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebA Telegram WebK Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:15 |
https://opensource.guide/pl/starting-a-project/ | Rozpoczęcie projektu Open Source | Open Source Guides O projekcie Współpracuj العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Rozpoczęcie projektu Open Source Dowiedz się więcej o świecie open source i przygotuj się do uruchomienia własnego projektu. Spis treści „Co” i „dlaczego” oprogramowania typu open source Czy powinienem uruchomić własny projekt open source? Uruchomienie własnego projektu open source Nazewnictwo i branding twojego projektu Twoja lista kontrolna przed uruchomieniem „Co” i „dlaczego” oprogramowania typu open source Więc myślisz o rozpoczęciu pracy z oprogramowaniem typu open source? Gratulacje! Świat docenia twój wkład. Porozmawiajmy o tym, czym jest open source i dlaczego ludzie to robią. Co oznacza „open source”? To znaczy, gdy projekt jest open source każdy może swobodnie korzystać, studiować, modyfikować i rozpowszechniać Twój projekt w dowolnym celu. Uprawnienia te są egzekwowane poprzez licencję typu open source . Open source jest potężny, ponieważ obniża bariery adopcji i współpracy, umożliwiając ludziom szybkie rozprzestrzenianie i ulepszanie projektów. Również dlatego, że daje użytkownikom możliwość kontrolowania własnego przetwarzania w odniesieniu do zamkniętego źródła. Na przykład firma korzystająca z oprogramowania typu open source ma możliwość zatrudnienia kogoś, kto wprowadzi niestandardowe ulepszenia oprogramowania, zamiast polegać wyłącznie na decyzjach dostawcy zamkniętego źródła. Wolne oprogramowanie odnosi się do tego samego zestawu projektów, co otwarte źródło . Czasami zobaczysz również niniejsze warunki w połączeniu jako „bezpłatne i otwarte oprogramowanie” (FOSS) lub „wolne, darmowe i otwarte oprogramowanie” (OPLĄT). Free i libre odnoszą się do wolności, nie ceny . Dlaczego ludzie open source-ują swoją pracę? One of the most rewarding experiences I get out of using and collaborating on open source comes from the relationships that I build with other developers facing many of the same problems I am. — @kentcdodds, “How getting into Open Source has been awesome for me” Jest wiele powodów dlaczego osoba lub organizacja chciałaby otworzyć projekt. Niektóre przykłady obejmują: Współpraca: Projekty open source mogą akceptować zmiany od każdego na świecie. Exercism , na przykład, jest platformą ćwiczeń programistycznych z ponad 350 uczestnikami. Adopcja i remiksowanie: projekty open source mogą być wykorzystywane przez każdego do prawie dowolnego celu. Ludzie mogą nawet używać go do budowania innych rzeczy. WordPress , na przykład, zaczął się jako rozwidlenie istniejącego projektu o nazwie b2 . Transparentność: Każdy może sprawdzić projekt open source pod kątem błędów lub niespójności. Przejrzystość ma znaczenie dla rządów takich jak Bułgaria lub Stany Zjednoczone , regulowane branże, takie jak bankowość lub opieka zdrowotna, oraz oprogramowanie zabezpieczające, takie jak Let’s Encrypt . Open source to nie tylko oprogramowanie. Możesz otworzyć wszystko, od zbiorów danych po książki. Sprawdź GitHub Explore , aby uzyskać pomysły na to, co jeszcze możesz otworzyć. Czy open source oznacza bezpłatnie Jednym z największych losowań open source jest to, że nie kosztuje. „Bezpłatny” jest jednak produktem ubocznym ogólnej wartości open source. Ponieważ wymaga licencji typu open source że każdy może używać, modyfikować i udostępniać Twój projekt do prawie dowolnego celu, same projekty są zazwyczaj bezpłatne. Jeśli korzystanie z projektu kosztuje, każdy może legalnie wykonać kopię i zamiast tego skorzystać z darmowej wersji. W rezultacie większość projektów typu open source jest darmowa, ale „bezpłatnie” nie jest częścią definicji open source. Istnieją sposoby pobierania opłat za projekty typu open source pośrednio poprzez podwójne licencjonowanie lub ograniczone funkcje, przy jednoczesnym zachowaniu zgodności z oficjalną definicją open source. Czy powinienem uruchomić własny projekt open source? Krótka odpowiedź brzmi „tak”, ponieważ bez względu na wynik uruchomienie własnego projektu to świetny sposób, aby dowiedzieć się, jak działa open source. Jeśli nigdy wcześniej nie korzystałeś z projektu, możesz być zdenerwowany tym, co powiedzą ludzie lub czy ktoś w ogóle to zauważy. Jeśli to brzmi jak ty, nie jesteś sam! Praca open source jest jak każde inne działanie twórcze, czy to pisanie, czy malowanie. Dzielenie się pracą ze światem może być przerażające, ale jedynym sposobem na poprawę jest ćwiczenie - nawet jeśli nie masz publiczności. Jeśli nie jesteś jeszcze przekonany, poświęć chwilę, aby pomyśleć o swoich celach. Wyznaczanie celów Cele mogą pomóc Ci dowiedzieć się, nad czym pracować, w czym powiedzieć „nie” i gdzie potrzebujesz pomocy od innych. Zacznij od zadania sobie pytania: dlaczego jestem otwarty na pozyskiwanie tego projektu? Nie ma jednej właściwej odpowiedzi na to pytanie. Możesz mieć wiele celów dla jednego projektu lub różnych projektów o różnych celach. Jeśli Twoim jedynym celem jest pochwalenie się swoją pracą, możesz nawet nie chcieć wkładów, a nawet powiedzieć to w swoim README. Z drugiej strony, jeśli chcesz współpracowników, zainwestujesz czas w przejrzystą dokumentację i sprawi, że nowicjusze będą mile widziani. At some point I created a custom UIAlertView that I was using…and I decided to make it open source. So I modified it to be more dynamic and uploaded it to GitHub. I also wrote my first documentation explaining to other developers how to use it on their projects. Probably nobody ever used it because it was a simple project but I was feeling good about my contribution. — @mavris, “Self-taught Software Developers: Why Open Source is important to us” W miarę rozwoju projektu Twoja społeczność może potrzebować czegoś więcej niż tylko kodu. Odpowiadanie na problemy, przeglądanie kodu i ewangelizacja projektu to ważne zadania w projekcie typu open source. Chociaż ilość czasu poświęcanego na zadania niekodujące będzie zależeć od wielkości i zakresu projektu, powinieneś być przygotowany jako opiekun, aby zająć się nimi samodzielnie lub znaleźć kogoś, kto ci pomoże. Jeśli jesteś częścią firmy, która pozyskuje projekt, upewnij się, że Twój projekt ma wewnętrzne zasoby potrzebne do rozwoju. Będziesz chciał określić, kto jest odpowiedzialny za utrzymanie projektu po uruchomieniu i jak udostępnisz te zadania swojej społeczności. Jeśli potrzebujesz specjalnego budżetu lub personelu na promocję, operacje i utrzymanie projektu, rozpocznij te rozmowy wcześniej. As you begin to open source the project, it’s important to make sure that your management processes take into consideration the contributions and abilities of the community around your project. Don’t be afraid to involve contributors who are not employed in your business in key aspects of the project — especially if they are frequent contributors. — @captainsafia, “So you wanna open source a project, eh?” Wkład w inne projekty Jeśli Twoim celem jest nauczenie się, jak współpracować z innymi lub zrozumieć, jak działa open source, rozważ przyczynienie się do istniejącego projektu. Zacznij od projektu, którego już używasz i który kochasz. Wkład w projekt może być tak prosty, jak poprawianie literówek lub aktualizacja dokumentacji. Jeśli nie masz pewności, jak rozpocząć pracę jako współpracownik, zapoznaj się z naszym Jak przyczynić się do tworzenia otwartego oprogramowania . Uruchomienie własnego projektu open source Nie ma idealnego czasu na otwarcie swojej pracy. Możesz otworzyć pomysł, projekt w toku lub po latach zamkniętego źródła. Ogólnie rzecz biorąc, powinieneś otworzyć swój projekt, gdy czujesz się dobrze, gdy inni oglądają twoją pracę i wyrażają opinie na jej temat. Bez względu na to, na jakim etapie zdecydujesz się na otwarcie projektu, każdy projekt powinien zawierać następującą dokumentację: Open source license README Contributing guidelines Code of conduct Jako opiekun, te komponenty pomogą ci komunikować oczekiwania, zarządzać składkami i chronić prawa wszystkich osób (w tym własnych). Znacząco zwiększają twoje szanse na pozytywne doświadczenie. Jeśli Twój projekt jest w GitHub, umieszczenie tych plików w katalogu głównym z zalecanymi nazwami plików pomoże GitHub rozpoznać i automatycznie udostępnić je czytelnikom. Wybór licencji Licencja typu open source gwarantuje, że inni mogą używać, kopiować, modyfikować i wnosić wkład w projekt bez żadnych konsekwencji. Chroni również przed trudnymi sytuacjami prawnymi. Musisz dołączyć licencję podczas uruchamiania projektu typu open source. Legalna praca to nie zabawa. Dobrą wiadomością jest to, że możesz skopiować i wkleić istniejącą licencję do swojego repozytorium. Ochrona twojej ciężkiej pracy zajmie tylko chwilę. MIT , Apache 2.0 , i GPLv3 są najpopularniejszymi licencjami typu open source, ale istnieją inne opcje do wyboru. Podczas tworzenia nowego projektu w GitHub masz możliwość wybrania licencji. Dołączenie licencji open source sprawi, że Twój projekt GitHub stanie się open source. Jeśli masz inne pytania lub wątpliwości związane z aspektami prawnymi zarządzania projektem typu open source, zapewniamy Ci ochronę . Pisanie README Pliki README nie tylko wyjaśniają, jak korzystać z projektu. Wyjaśniają również, dlaczego Twój projekt ma znaczenie i co użytkownicy mogą z nim zrobić. W README spróbuj odpowiedzieć na następujące pytania: Co robi ten projekt? Dlaczego ten projekt jest przydatny? Jak zacząć? Gdzie mogę uzyskać dodatkową pomoc, jeśli jej potrzebuję? Możesz użyć swojego README, aby odpowiedzieć na inne pytania, takie jak sposób obsługi wkładów, jakie są cele projektu oraz informacje na temat licencji i atrybucji. Jeśli nie chcesz przyjmować datków lub twój projekt nie jest jeszcze gotowy do produkcji, zapisz te informacje. Better documentation means more users, less support requests, and more contributors. (…) Remember that your readers aren’t you. There are people who might come to a project who have completely different experiences. — @tracymakes, “Writing So Your Words Are Read (video)” Czasami ludzie unikają pisania pliku README, ponieważ uważają, że projekt jest niedokończony lub nie chcą wkładów. Są to bardzo dobre powody, aby napisać jeden. Aby uzyskać więcej inspiracji, spróbuj użyć przewodnika @dguo ‘Make README’ lub @PurpleBooth w szablon README napisać kompletny plik README. Po dołączeniu pliku README do katalogu głównego GitHub automatycznie wyświetli go na stronie głównej repozytorium. Pisanie swoich wytycznych Plik CONTRIBUTING mówi odbiorcom, jak wziąć udział w projekcie. Na przykład możesz podać informacje o: Jak złożyć raport o błędzie (spróbuj użyć szablonów zgłaszania problemów i pobierania ) Jak zasugerować nową funkcję Jak skonfigurować środowisko i uruchomić testy Oprócz szczegółów technicznych plik CONTRIBUTING jest także okazją do wyrażenia swoich oczekiwań dotyczących wkładów, takich jak: Rodzaje składek, których szukasz Twoja mapa drogowa lub wizja projektu W jaki sposób współpracownicy powinni (lub nie powinni) się z Tobą skontaktować Używanie ciepłego, przyjaznego tonu i oferowanie konkretnych sugestii dotyczących wkładu (takich jak pisanie dokumentacji lub tworzenie strony internetowej) może znacznie przyczynić się do tego, że nowo przybyli poczują się mile widziani i podekscytowani uczestnictwem. Na przykład Active Admin uruchamia swój przewodnik pomocniczy z: Po pierwsze, dziękuję za rozważenie włączenia się w Active Admin. Ludzie tacy jak Ty sprawiają, że Active Admin jest tak doskonałym narzędziem. Na najwcześniejszych etapach projektu plik WKŁADU może być prosty. Zawsze powinieneś wyjaśniać, jak zgłaszać błędy lub problemy z plikami, a także wszelkie wymagania techniczne (takie jak testy), aby wnieść swój wkład. Z czasem możesz dodawać inne często zadawane pytania do pliku WKŁAD. Zapisanie tych informacji oznacza, że coraz mniej osób będzie zadawać ci te same pytania w kółko. Aby uzyskać więcej pomocy w pisaniu pliku WKŁAD, sprawdź @nayafia contributing guide template lub @mozilla “How to Build a CONTRIBUTING.md” . Link do pliku CONTRIBUTING z README, dzięki czemu więcej osób go zobaczy. Jeśli umieścisz plik CONTRIBUTING w repozytorium swojego projektu , GitHub automatycznie doda link do Twojego pliku, gdy współtwórca utworzy problem lub otworzy żądanie ściągnięcia. Ustanowienie kodeksu postępowania We’ve all had experiences where we faced what was probably abuse either as a maintainer trying to explain why something had to be a certain way, or as a user…asking a simple question. (…) A code of conduct becomes an easily referenced and linkable document that indicates that your team takes constructive discourse very seriously. — @mlynch, “Making Open Source a Happier Place” Wreszcie kodeks postępowania pomaga ustalić podstawowe zasady postępowania dla uczestników projektu. Jest to szczególnie cenne, jeśli uruchamiasz projekt open source dla społeczności lub firmy. Kodeks postępowania umożliwia ci zdrowe, konstruktywne zachowanie społeczności, które zmniejszy stres jako opiekuna. Aby uzyskać więcej informacji, zapoznaj się z naszym Przewodnikiem Kodeksu Postępowania . Oprócz informowania, w jaki sposób oczekuje się, że uczestnicy będą się zachowywać, kodeks postępowania ma również na celu opisanie, do kogo odnoszą się te oczekiwania, kiedy mają zastosowanie, i co zrobić, gdy nastąpi naruszenie. Podobnie jak licencje typu open source, pojawiają się również nowe standardy kodeksów postępowania, więc nie musisz pisać własnych. Porozumienie dla współautorów to rozwijany kodeks postępowania używany przez ponad 40 000 projektów open source , w tym Kubernetes, Rails i Swift. Bez względu na to, jakiego tekstu użyjesz, powinieneś być przygotowany do egzekwowania swojego kodeksu postępowania, jeśli to konieczne. Wklej tekst bezpośrednio do pliku CODE_OF_CONDUCT w repozytorium. Zachowaj plik w katalogu głównym projektu, aby łatwo go znaleźć i połączyć go z README. Nazewnictwo i branding twojego projektu Branding to coś więcej niż efektowne logo lub chwytliwa nazwa projektu. Chodzi o to, jak mówisz o swoim projekcie i do kogo docierasz z przesłaniem. Wybór właściwej nazwy Wybierz nazwę, która jest łatwa do zapamiętania i najlepiej daje wyobrażenie o tym, co robi projekt. Na przykład: Sentry monitoruje aplikacje pod kątem zgłaszania awarii Thin to szybki i prosty serwer internetowy Ruby Jeśli bazujesz na istniejącym projekcie, użycie ich nazwy jako prefiksu może pomóc wyjaśnić, co robi twój projekt (na przykład, node-fetch przynosi window.fetch do Node.js). Rozważ przede wszystkim przejrzystość. Kalambury są zabawne, ale pamiętaj, że niektóre żarty mogą nie przekładać się na inne kultury lub osoby z różnymi doświadczeniami. Niektórzy z potencjalnych użytkowników mogą być pracownikami firmy: nie chcesz, aby czuli się niekomfortowo, gdy muszą wyjaśniać Twój projekt w pracy! Unikanie konfliktów nazw Sprawdź projekty open source o podobnej nazwie , szczególnie jeśli korzystasz z tego samego języka lub ekosystemu. Jeśli twoje imię pokrywa się z popularnym istniejącym projektem, możesz pomylić odbiorców. Jeśli chcesz, aby witryna internetowa, uchwyt na Twitterze lub inne właściwości reprezentowały Twój projekt, upewnij się, że możesz uzyskać odpowiednie nazwy. Najlepiej jest zarezerwować teraz te nazwy dla spokoju ducha, nawet jeśli jeszcze nie zamierzasz ich używać. Upewnij się, że nazwa twojego projektu nie narusza żadnych znaków towarowych. Firma może poprosić cię o późniejsze wycofanie projektu, a nawet podjęcie kroków prawnych przeciwko tobie. To po prostu nie jest warte ryzyka. Możesz sprawdzić WIPO Global Brand Database pod kątem konfliktów znaków towarowych. Jeśli pracujesz w firmie, jest to jedna z rzeczy, w których zespół prawny może ci pomóc . Na koniec wykonaj szybkie wyszukiwanie w Google nazwy swojego projektu. Czy ludzie będą mogli łatwo znaleźć Twój projekt? Czy w wynikach wyszukiwania pojawia się coś jeszcze, czego nie chciałbyś, żeby zobaczyli? To, jak piszesz (i kodujesz), wpływa również na twoją markę! Przez cały czas trwania projektu będziesz dużo pisać: CZYTELNIKI, samouczki, dokumenty społeczności, odpowiadanie na problemy, może nawet biuletyny i listy mailingowe. Niezależnie od tego, czy jest to oficjalna dokumentacja, czy zwykły e-mail, styl pisania jest częścią marki Twojego projektu. Zastanów się, w jaki sposób możesz dotrzeć do odbiorców i czy to jest ton, który chcesz przekazać. I tried to be involved with every thread on the mailing list, and showing exemplary behaviour, being nice to people, taking their issues seriously and trying to be helpful overall. After a while, people stuck around not to only ask questions, but to help with the answering as well, and to my complete delight, they mimicked my style. — @janl on CouchDB , “Sustainable Open Source” Używanie ciepłego, inkluzywnego języka (takiego jak „je”, nawet w odniesieniu do jednej osoby) może znacznie przyczynić się do tego, aby Twój projekt był przyjemny dla nowych współpracowników. Trzymaj się prostego języka, ponieważ wielu czytelników może nie być rodzimym językiem angielskim. Poza tym, jak piszesz słowa, twój styl kodowania może również stać się częścią marki twojego projektu. Angular i jQuery to dwa przykłady projektów z rygorystycznymi stylami kodowania i wytycznymi. Nie musisz pisać przewodnika po stylu dla swojego projektu, gdy dopiero zaczynasz, i może się okazać, że lubisz włączać różne style kodowania do swojego projektu. Ale powinieneś przewidzieć, w jaki sposób Twój styl pisania i kodowania może przyciągać lub zniechęcać różne typy ludzi. Najwcześniejsze etapy projektu to okazja do ustanowienia precedensu, który chcesz zobaczyć. Twoja lista kontrolna przed uruchomieniem Gotowy do otwarcia twojego projektu? Oto lista kontrolna, która pomoże. Zaznacz wszystkie pola? Jesteś gotowy! Kliknij „opublikuj” i poklep się po plecach. Dokumentacja Projekt posiada plik LICENSE z licencją typu open source Projekt posiada podstawową dokumentację (README, CONTRIBUTING, CODE_OF_CONDUCT) Nazwa jest łatwa do zapamiętania, daje pewne wyobrażenie o tym, czym jest projekt i nie koliduje z istniejącym projektem oraz nie narusza znaków towarowych Lista "issue" jest aktualna, a sprawy są przejrzyście uporządkowane i opatrzone etykietami Kod Projekt wykorzystuje spójne konwencje kodu i przejrzyste nazwy funkcji, metod oraz zmiennych Kod jest dobrze skomentowany, dokumentując intencje i skrajne przypadki W historii zmian, w problemach lub Pull Request nie ma żadnych poufnych materiałów (na przykład haseł lub innych niepublicznych informacji) Ludzie Jeśli jesteś osobą fizyczną: Rozmawiałeś z działem prawnym i/lub rozumiesz zasady dotyczące własności intelektualnej i zasad dotyczące oprogramowania open source (jeśli jesteś zatrudniony) Jeśli jesteś firmą lub organizacją: Rozmawiałeś ze swoim działem prawnym Masz plan marketingowy, aby ogłosić i promować swój projekt Ktoś jest zaangażowany w zarządzanie interakcjami społeczności (odpowiadanie na problemy, przeglądanie i łączenie pull requests) Przynajmniej dwie osoby mają dostęp administracyjny do projektu Zrobiłeś to! Gratulujemy otwartego zaopatrzenia pierwszego projektu. Bez względu na wynik, praca publiczna jest darem dla społeczności. Z każdym żądaniem zatwierdzenia, komentarza i wyciągnięcia tworzysz możliwości dla siebie i innych do nauki i rozwoju. Powrót do wszystkich przewodników Powiązane przewodniki Jak znaleźć użytkowników dla twojego projektu Rozwijaj projekt open source, przekazując go w ręce odpowiednich użytkowników. Budowanie przyjaznych społeczności Zbuduj społeczność, która zachęca ludzi do korzystania, przyczyniania się i ewangelizacji twojego projektu. Scroll to Top Współpracuj Chcesz coś zasugerować? Ta zawartość jest open source. Pomóż nam to poprawić. Współpracuj Pozostańmy w kontakcie Bądź pierwszym, który usłyszy o najnowszych wskazówkach i zasobach GitHub. Adres e-mail fine print z od i przyjaciele | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/categories/software-development-kits?trk=products_details_guest_product_category | Best Software Development Kits (SDK) | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Software Engineer (58) Developer (25) Senior Software Engineer (23) Product Manager (19) Application Developer (17) See all products Find top products in Software Development Kits (SDK) category Software used to create platform-specific applications, such as those for iOS or the .NET framework. - Utilize integrated compilers and debugger tools - Incorporate additional features and functions such advertising and push notifications - Perform analysis of application activity 299 results Meta Business SDK Software Development Kits (SDK) by Meta The Meta Business SDK gives you access to our suite of business APIs allowing you to build unique and customized solutions to serve your businesses and clients. View product MantHANA Software Development Kits (SDK) by Bosch Global Software Technologies MantHANA is Bosch’s Rapid Deployment Kit that drives hardware and technology changes during S/4 HANA implementation. By integrating country-specific expertise and SAP best practices acquired by Bosch over the years it helps accelerate the S/4 HANA journey for a successful digital transformation. The Methodology for S/4 HANA Transition • Ready process lists speeds up Requirements Analysis • Business process blueprints included for complex processes • Predefined concepts to enable early-stage activity • Detailed cutover plan to ensure ease of S/4HANA transition View product Tencent Effect SDK Software Development Kits (SDK) by Tencent Tencent Effect SDK leverages YouTu's accurate AI capabilities and Pitu's rich real-time effects to offer a wealth of services for many video processing use cases. View product Elevate Software Development Kits (SDK) by Accedo.tv Ready-to-go OTT apps with unlimited customization opportunities. Elevate condenses Accedo’s vast experience in OTT UX strategy, design, and engineering into an easy-to-deploy application framework. A solution combining the quick time to market of ready-made OTT applications with all the customization benefits of bespoke video services - the best of both worlds. View product Lyzr AI Software Development Kits (SDK) by Lyzr AI Lyzr is a low-code agent framework with an agentic approach to building generative AI applications. Its fully integrated agents come with pre-built RAG pipelines, allowing you to build and launch in minutes. With Lyzr, you can build chatbots, knowledge search, data analysis, RAG-powered apps, and multi-agent workflow automation with minimal effort. The best part is that you can get locally deployable SDKs and private APIs to run the agents on your cloud, thus eliminating all concerns related to data privacy, compliance, and latency. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights RevenueCat Software Development Kits (SDK) by RevenueCat RevenueCat gets engineers back to adding differentiating value to your apps, rather than spend their time on never-ending maintenance of subscription plumbing. Through SDKs for all mobile frameworks, support for all app stores and web, a flexible API, and native integrations with all your marketing, CRM, and other tooling, RevenueCat ensures that your customers can purchase from your across platforms, while your Product, Marketing, Growth and CRM teams can trust that the data that feeds into their tooling is clean, reliable, and accurate. View product Ready Player Me Software Development Kits (SDK) by Ready Player Me Ready Player Me provides developers with easy-to-integrate Avatar Creator and developer tools to give their users highly personalized characters to help increase retention and engagement. View product Quest Software Development Kits (SDK) by LISNR Easily create gamified customer engagement experiences with the Quest platform. Quest’s data ingestion engine goes beyond traditional loyalty to help brands incentivize the most impactful customer actions. With Quest, you’ll grow your business through repeat customers and new revenue streams, not by discounting your brand. View product Radius Software Development Kits (SDK) by LISNR One-to-many long-range ultrasonic data transfer (SDK) between devices greater than 10ft. Optimized for long-range control/reliability of data transmission. View product Dante Software Development Kits (SDK) by Audinate Dante replaces point-to-point audio & video connections with easy-to-use, scalable, flexible networking. Adopted by hundreds of manufacturers in thousands of products, Dante is the de facto standard for modern AV connectivity. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/salesforce-slack/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | Slack | LinkedIn Skip to main content LinkedIn Salesforce in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Slack Cloud Communications Platforms by Salesforce See who's skilled in this Add as skill Learn more Report this product About Slack is your work operating system. Slack is where humans with agents meet data, workflows, and apps to deliver big results, right where people love to work. Similar products Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Avaya Cloud Office Avaya Cloud Office Cloud Communications Platforms MessageBird MessageBird Cloud Communications Platforms Vonage Communications APIs Vonage Communications APIs Cloud Communications Platforms CPaaS CPaaS Cloud Communications Platforms Channelize.io: Live Stream Shopping Platform Channelize.io: Live Stream Shopping Platform Cloud Communications Platforms Sign in to see more Show more Show less Salesforce products Agentforce Agentforce Commerce Cloud Commerce Cloud E-Commerce Platforms Data Cloud Data Cloud Customer Data Platforms (CDP) Marketing Cloud Marketing Cloud Marketing Automation Software Net Zero Cloud Net Zero Cloud Data Management Platforms (DMP) Sales Cloud Sales Cloud Customer Relationship Management (CRM) Software Salesforce CRM Salesforce CRM Customer Data Platforms (CDP) Salesforce Platform Salesforce Platform Low-Code Development Platforms Tableau Tableau Business Intelligence (BI) Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2FshareArticle%3Fmini%3Dtrue%26url%3Dhttps%253A%252F%252Fdev%2Eto%252Faditya_singh_172b37651201%252F30-core-algorithm-ep-06-prefix-sum-1ii0%26title%3D30%2520Core%2520Algorithm%2520%253A%2520Ep-06%2520%253APrefix%2520Sum%26summary%3DWhy%2520Prefix%2520Sum%2520Is%2520Really%2520About%2520Making%2520Accumulated%2520Cost%2520Explicit%2520%2520%2520Many%2520performance%2E%2E%2E%26source%3DDEV%2520Community&fromSignIn=true&trk=cold_join_sign_in | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://www.lagrange.dev/defense | Defense Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY Stake $LA for 20% Expected APY TECHNOLOGY Defense DeepProve ZK Prover Network ECOSYSTEM FOUNDATION DOCS ARTICLES Blog Engineering Technology DEFENSE DEEP PROVE ZK PROVER NETWORK ECOSYSTEM FOUNDATION DOCS Articles BLOG ENGINEERING Cryptography as a Superpower Transforming mathematics into the deterrent of the 21st century. See Docs Verifiable Autonomy for Modern Defense AI now powers decisions across the defense stack • Drones • ISR pipelines • Cyber operations Verify every AI decision without revealing classified data • Ensures AI models behave as intended • Guarantees AI inputs remain untampered • Verifies AI outputs are provably correct Guaranteed integrity, even at the tactical edge Proof as a Deterrent DeepProve embeds cryptographic guarantees directly into defense AI systems: Trusted Autonomy Confirms deployed models are authentic, preventing spoofed or altered AI. Operational Integrity Proves sensor feeds and ISR data remain untampered. Action Traceability Reveals how AI reached a decision, enabling accountable autonomy. Lawful AI Enforces mission constraints and Rules of Engagement within the proof circuit. Auditable Secrecy Enables classified audits without exposing sensitive logic or data. The Cryptographic Foundation of Command DeepProve transforms verification from a manual review process into a cryptographic constant—turning AI into a provable battlefield asset. Reach Out Sign up for updates Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Resources Github DeepProve Defense Docs ZK Prover Network Ecosystem Blog ZK Coprocessor Engineering About Careers Press Kit Foundation Terms & Conditions Privacy Policy Follow © Lagrange 2025 | 2026-01-13T09:29:15 |
https://lnkd.in/guJv5vHs?trk=organization_guest_main-feed-card-text | LinkedIn LinkedIn This link will take you to a page that’s not on LinkedIn Because this is an external link, we’re unable to verify it for safety. https://deca.org.au/2026policyforum/ This experience is optimized for Chrome, Edge, and Safari Have questions? Learn more | 2026-01-13T09:29:15 |
https://lnkd.in/gTQ6eN8j?trk=organization_guest_main-feed-card-text | LinkedIn LinkedIn This link will take you to a page that’s not on LinkedIn Because this is an external link, we’re unable to verify it for safety. https://deca.org.au/resources/ This experience is optimized for Chrome, Edge, and Safari Have questions? Learn more | 2026-01-13T09:29:15 |
http://tom.preston-werner.com/ | Tom Preston-Werner Tom Preston-Werner home Blog Posts 22 Oct 2025 » Announcing PWV Fund I 30 May 2023 » RedwoodJS’ Next Epoch: All In on React Server Components 23 May 2022 » Major Version Numbers are Not Sacred 07 Apr 2022 » Introducing the Redwood Startup Fund 04 Apr 2022 » Announcing RedwoodJS 1.0 and $1M Funding 15 Jun 2020 » Committing $250k this Year to Racial Justice Efforts 23 Mar 2020 » We Are Giving $1M Toward San Francisco COVID-19 Response 04 Mar 2020 » Joining the Netlify Board to Help Shape the Future of the JAMstack 10 Nov 2016 » Snyk - Automatically Scan and Fix Ruby and Nodejs Vulnerabilities 19 Jun 2015 » Replicated - An Easier Path from SaaS to Enterprise 21 Apr 2014 » Farewell GitHub, Hello Immersive Computing 22 Nov 2011 » Open Source (Almost) Everything 03 May 2011 » Rejected Bio from The Setup 29 Mar 2011 » Ten Lessons from GitHub's First Year 11 Dec 2010 » Designer, Architect, Developer 18 Oct 2010 » Optimize for Happiness 23 Aug 2010 » Readme Driven Development 11 May 2010 » TomDoc - Reasonable Ruby Documentation 19 May 2009 » The Git Parable 17 Nov 2008 » Blogging Like a Hacker 03 Nov 2008 » How to Meet Your Next Cofounder 27 Oct 2008 » Looking back on Selling Gravatar to Automattic 18 Oct 2008 » How I Turned Down $300,000 from Microsoft to go Full-Time on GitHub Highlighted Media 02 Sep 2013 » Article: WIRED - GitHub Is Going Mainstream 09 Nov 2011 » Video: RubyConf Argentina - Optimizing For Happiness 01 Oct 2011 » Video: RubyConf - GitHub Flavored Ruby 23 Nov 2010 » Video: Erlang Factory - Mastering Git Basics Other Interviews, Talks, Etc 12 Sep 2013 » Video: Fox Business News interview 02 Sep 2013 » Article: WIRED - GitHub Is Going Mainstream 25 Jul 2013 » Video: O'Reilly Media - OSCON 2013 Interview 28 Dec 2012 » Article: NYTimes - Dreams of ‘Open’ Everything 20 Oct 2012 » Video: Startup School 2012 - People, Product, Philosophy 27 Sep 2012 » Video (Panel): Orrick - How to Build a Great Startup Culture 18 Jun 2012 » Article: GigaOm - 10 Innovators Changing the Game for Internet Infrastructure 02 Dec 2011 » Video: Northern Lights Conference - Leveling Up 12 Nov 2011 » Slides: RubyConf Uruguay - GitHub Flavored Ruby 09 Nov 2011 » Slides: RubyConf Argentina - Optimizing For Happiness 14 Apr 2011 » Video: ACCU Conference - Optimizing For Happiness 09 Apr 2011 » SitePoint Podcast: Social Coding with GitHub’s Tom Preston-Werner 10 Feb 2011 » Video: NCAR SEA: Unlocking the Secrets of Git 12 Jan 2011 » Maestros del Web: Tom Preston-Werner fundador de GitHub 11 Nov 2010 » Video: RubyConf 2010 - The Road from Ruby Hacker to Entrepreneur 16 Oct 2010 » Lambdaphant interview with Tom Preston-Werner 16 Oct 2010 » Video: Startup School - Optimize for Happiness 16 Sep 2010 » Video: @mail.ru Office Presentation 14 Sep 2010 » Video: @mail.ru Tech Forum in Moscow 11 Sep 2010 » Photo: FunConf Speech in Ireland 07 Sep 2010 » SchnitzelConf: Virality and Community 27 Aug 2010 » Video: Lone Star Ruby Conf Keynote 16 Aug 2010 » InfoQ: Erlang Factory Interview - Tom Preston-Werner and Kenneth Lundin 03 Aug 2010 » 37signals: Bootstrapped, Profitable, & Proud: GitHub 17 Jun 2010 » WebPulp.tv: Interview with GitHub CTO Tom Preston-Werner 27 Apr 2010 » The Next Web 2010: Interview about Gravatar and Online Reputation 27 Apr 2010 » TNW 2010: What I Learned From Bootstrapping a Side Project Into GitHub 19 Nov 2009 » RubyConf 2009 Talk: BERT and Ernie: Scaling your Ruby site with Erlang 21 Aug 2009 » Linux Magazine: The GitHub Hall of Fame - Jekyll Review 27 Jul 2009 » Yahoo Developer Talk: Git, GitHub, and Social Coding 22 Jul 2009 » Envy Labs: 5 Days of OSCON Interview 30 Apr 2009 » Erlang Factory 09: Mixing Erlang and Ruby with Erlectricity 23 Apr 2009 » BusinessWeek: Best Young Tech Entrepreneurs of 2009 17 Jan 2009 » RubyFringe 2008: Conceptual Algorithms 09 Oct 2008 » InfoQ: Tom Preston-Werner on Powerset, GitHub, Ruby and Erlang 11 Jul 2008 » Rubyology 65: Powerset Stars 2 of 2 05 Jul 2008 » Rubyology 65: Powerset Stars 1 of 2 13 Jun 2008 » Web 2.0 Show: GitHub (Tom Preston-Werner & Chris Wanstrath) 02 Jun 2008 » Gregg Pollack: Dave Fayram and Tom Preston-Werner at RailsConf 29 May 2008 » RailsConf 08: Two talks 18 Oct 2007 » Gravatar Blog: Automattic Acquires Gravatar 16 Aug 2007 » Steve Newcomb Blog: Interview with Tom Preston-Werner 26 Dec 2006 » WordPress Podcast: Interview with Tom Werner 02 Apr 2005 » JoshuaInk: Seven and a half questions for Tom Werner Noteworthy Open Source Projects and Specifications Jekyll: A simple, blog aware, static site generator (used for this site). Semantic Versioning: A meaningful method for incrementing version numbers. TOML: Tom's Obvious, Minimal Language. God: Ruby process monitoring framework with easy extensibility. Chronic: Ruby natural language date/time parser. TomDoc: Code documentation for humans. ProxyMachine: Layer 7 routing proxy in Ruby with Event Machine. Gollum: A simple, Git-powered wiki with a sweet API and local frontend. Grit: Object oriented Ruby bindings for Git (used by GitHub). Ernie: Ruby/Erlang Hybrid BERT-RPC server. Tom Preston-Werner Cofounder of GitHub , Chatterbug tom@mojombo.com github.com/mojombo twitter.com/mojombo | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/tencentglobal-tencent-realtime-communication-trtc/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click | Tencent Real-Time Communication (TRTC) | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Tencent Real-Time Communication (TRTC) Live Streaming Software by Tencent See who's skilled in this Add as skill Learn more Report this product About Enable audio/video calls and interactive live streaming in your application in 30 minutes Similar products Cloudflare Stream Cloudflare Stream Live Streaming Software Tango Tango Live Streaming Software BOCC BOCC Live Streaming Software Media Services Live Media Services Live Live Streaming Software Liveu Liveu Live Streaming Software Kaltura AI Video Experience Cloud Kaltura AI Video Experience Cloud Live Streaming Software Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://opensource.guide/leadership-and-governance/ | Leadership and Governance | Open Source Guides About Contribute العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Leadership and Governance Growing open source projects can benefit from formal rules for making decisions. Table of Contents Understanding governance for your growing project What are examples of formal roles used in open source projects? How do I formalize these leadership roles? When should I give someone commit access? What are some of the common governance structures for open source projects? Do I need governance docs when I launch my project? What happens if corporate employees start submitting contributions? Understanding governance for your growing project Your project is growing, people are engaged, and you’re committed to keeping this thing going. At this stage, you may be wondering how to incorporate regular project contributors into your workflow, whether it’s giving someone commit access or resolving community debates. If you have questions, we’ve got answers. What are examples of formal roles used in open source projects? Many projects follow a similar structure for contributor roles and recognition. What these roles actually mean, though, is entirely up to you. Here are a few types of roles you may recognize: Maintainer Contributor Committer For some projects, “maintainers” are the only people in a project with commit access. In other projects, they’re simply the people who are listed in the README as maintainers. A maintainer doesn’t necessarily have to be someone who writes code for your project. It could be someone who’s done a lot of work evangelizing your project, or written documentation that made the project more accessible to others. Regardless of what they do day-to-day, a maintainer is probably someone who feels responsibility over the direction of the project and is committed to improving it. A “contributor” could be anyone who comments on an issue or pull request, people who add value to the project (whether it’s triaging issues, writing code, or organizing events), or anybody with a merged pull request (perhaps the narrowest definition of a contributor). [For Node.js,] every person who shows up to comment on an issue or submit code is a member of a project’s community. Just being able to see them means that they have crossed the line from being a user to being a contributor. — @mikeal, “Healthy Open Source” The term “committer” might be used to distinguish commit access, which is a specific type of responsibility, from other forms of contribution. While you can define your project roles any way you’d like, consider using broader definitions to encourage more forms of contribution. You can use leadership roles to formally recognize people who have made outstanding contributions to your project, regardless of their technical skill. You might know me as the “inventor” of Django…but really I’m the guy who got hired to work on a thing a year after it was already made. (…) People suspect that I’m successful because of my programming skill…but I’m at best an average programmer. — @jacobian, “PyCon 2015 Keynote” (video) How do I formalize these leadership roles? Formalizing your leadership roles helps people feel ownership and tells other community members who to look to for help. For a smaller project, designating leaders can be as simple as adding their names to your README or a CONTRIBUTORS text file. For a bigger project, if you have a website, create a team page or list your project leaders there. For example, Postgres has a comprehensive team page with short profiles for each contributor. If your project has a very active contributor community, you might form a “core team” of maintainers, or even subcommittees of people who take ownership of different issue areas (for example, security, issue triaging, or community conduct). Let people self-organize and volunteer for the roles they’re most excited about, rather than assigning them. [We] supplement the core team with several “subteams”. Each subteam is focused on a specific area, e.g., language design or libraries. (…) To ensure global coordination and a strong, coherent vision for the project as a whole, each subteam is led by a member of the core team. — “Rust Governance RFC” Leadership teams may want to create a designated channel (like on IRC) or meet regularly to discuss the project (like on Gitter or Google Hangout). You can even make those meetings public so other people can listen. Cucumber-ruby , for example, hosts office hours every week . Once you’ve established leadership roles, don’t forget to document how people can attain them! Establish a clear process for how someone can become a maintainer or join a subcommittee in your project, and write it into your GOVERNANCE.md. Tools like Vossibility can help you publicly track who is (or isn’t) making contributions to the project. Documenting this information avoids the community perception that maintainers are a clique that makes its decisions privately. Finally, if your project is on GitHub, consider moving your project from your personal account to an Organization and adding at least one backup admin. GitHub Organizations make it easier to manage permissions and multiple repositories and protect your project’s legacy through shared ownership . When should I give someone commit access? Some people think you should give commit access to everybody who makes a contribution. Doing so could encourage more people to feel ownership of your project. On the other hand, especially for bigger, more complex projects, you may want to only give commit access to people who have demonstrated their commitment. There’s no one right way of doing it - do what makes you most comfortable! If your project is on GitHub, you can use protected branches to manage who can push to a particular branch, and under which circumstances. Whenever somebody sends you a pull request, give them commit access to your project. While it may sound incredibly stupid at first, using this strategy will allow you to unleash the true power of GitHub. (…) Once people have commit access, they are no longer worried that their patch might go unmerged…causing them to put much more work into it. — @felixge, “The Pull Request Hack” What are some of the common governance structures for open source projects? There are three common governance structures associated with open source projects. BDFL: BDFL stands for “Benevolent Dictator for Life”. Under this structure, one person (usually the initial author of the project) has final say on all major project decisions. Python is a classic example. Smaller projects are probably BDFL by default, because there are only one or two maintainers. A project that originated at a company might also fall into the BDFL category. Meritocracy: (Note: the term “meritocracy” carries negative connotations for some communities and has a complex social and political history .) Under a meritocracy, active project contributors (those who demonstrate “merit”) are given a formal decision making role. Decisions are usually made based on pure voting consensus. The meritocracy concept was pioneered by the Apache Foundation ; all Apache projects are meritocracies. Contributions can only be made by individuals representing themselves, not by a company. Liberal contribution: Under a liberal contribution model, the people who do the most work are recognized as most influential, but this is based on current work and not historic contributions. Major project decisions are made based on a consensus seeking process (discuss major grievances) rather than pure vote, and strive to include as many community perspectives as possible. Popular examples of projects that use a liberal contribution model include Node.js and Rust . Which one should you use? It’s up to you! Every model has advantages and trade-offs. And although they may seem quite different at first, all three models have more in common than they seem. If you’re interested in adopting one of these models, check out these templates: BDFL model template Meritocracy model template Node.js’s liberal contribution policy Do I need governance docs when I launch my project? There is no right time to write down your project’s governance, but it’s much easier to define once you’ve seen your community dynamics play out. The best (and hardest) part about open source governance is that it is shaped by the community! Some early documentation will inevitably contribute to your project’s governance, however, so start writing down what you can. For example, you can define clear expectations for behavior, or how your contributor process works, even at your project’s launch. If you’re part of a company launching an open source project, it’s worth having an internal discussion before launch about how your company expects to maintain and make decisions about the project moving forward. You may also want to publicly explain anything particular to how your company will (or won’t!) be involved with the project. We assign small teams to manage projects on GitHub who are actually working on these at Facebook. For example, React is run by a React engineer. — @caabernathy, “An inside look at open source at Facebook” What happens if corporate employees start submitting contributions? Successful open source projects get used by many people and companies, and some companies may eventually have revenue streams eventually tied to the project. For example, a company may use the project’s code as one component in a commercial service offering. As the project gets more widely used, people who have expertise in it become more in-demand - you may be one of them! - and will sometimes get paid for work they do in the project. It’s important to treat commercial activity as normal and as just another source of development energy. Paid developers shouldn’t get special treatment over unpaid ones, of course; each contribution must be evaluated on its technical merits. However, people should feel comfortable engaging in commercial activity, and feel comfortable stating their use cases when arguing in favor of a particular enhancement or feature. “Commercial” is completely compatible with “open source”. “Commercial” just means there is money involved somewhere - that the software is used in commerce, which is increasingly likely as a project gains adoption. (When open source software is used as part of a non-open-source product, the overall product is still “proprietary” software, though, like open source, it might be used for commercial or non-commercial purposes.) Like anyone else, commercially-motivated developers gain influence in the project through the quality and quantity of their contributions. Obviously, a developer who is paid for her time may be able to do more than someone who is not paid, but that’s okay: payment is just one of many possible factors that could affect how much someone does. Keep your project discussions focused on the contributions, not on the external factors that enable people to make those contributions. Do I need a legal entity to support my project? You don’t need a legal entity to support your open source project unless you’re handling money. For example, if you want to create a commercial business, you’ll want to set up a C Corp or LLC (if you’re based in the US). If you’re just doing contract work related to your open source project, you can accept money as a sole proprietor, or set up an LLC (if you’re based in the US). If you want to accept donations for your open source project, you can set up a donation button (using PayPal or Stripe, for example), but the money won’t be tax-deductible unless you are a qualifying nonprofit (a 501c3, if you’re in the US). Many projects don’t wish to go through the trouble of setting up a nonprofit, so they find a nonprofit fiscal sponsor instead. A fiscal sponsor accepts donations on your behalf, usually in exchange for a percentage of the donation. Software Freedom Conservancy , Apache Foundation , Eclipse Foundation , Linux Foundation and Open Collective are examples of organizations that serve as fiscal sponsors for open source projects. Our goal is to provide an infrastructure that communities can use to be self sustainable, thus creating an environment where everyone — contributors, backers, sponsors — get concrete benefits out of it. — @piamancini, “Moving beyond the charity framework” If your project is closely associated with a certain language or ecosystem, there may also be a related software foundation you can work with. For example, the Python Software Foundation helps support PyPI , the Python package manager, and the Node.js Foundation helps support Express.js , a Node-based framework. Back to all guides Related Guides Best Practices for Maintainers Making your life easier as an open source maintainer, from documenting processes to leveraging your community. Open Source Metrics Make informed decisions to help your open source project thrive by measuring and tracking its success. Scroll to Top Contribute Want to make a suggestion? This content is open source. Help us improve it. Contribute Stay in touch Be the first to hear about GitHub's latest open source tips and resources. Email Address fine print with by and friends | 2026-01-13T09:29:15 |
https://www.linkedin.com/checkpoint/rp/request-password-reset?session_redirect=%2Fproducts%2Ftencentglobal-tencent-realtime-communication-trtc%3FviewConnections%3Dtrue&trk=products_details_guest_face-pile-cta | Reset Password | LinkedIn Sign in Join now Forgot password We’ll send a verification code to this email or phone number if it matches an existing LinkedIn account. Email or Phone We don’t recognize that email. Did you mean {:emailSuggestion} ? We’ll send a verification code to this email or phone number if it matches an existing LinkedIn account. Next or Back LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/oracle-cloud-oracle-cloud-infrastructure-oci/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Oracle Cloud Infrastructure (OCI) | LinkedIn Skip to main content LinkedIn Oracle Cloud in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Oracle Cloud Infrastructure (OCI) Enterprise Cloud Platforms by Oracle Cloud See who's skilled in this Add as skill Learn more Report this product About Oracle Cloud Infrastructure (OCI) has all the services you need to migrate, build, and run all your IT, from existing enterprise workloads to new cloud native applications and data platforms. With more than 100 cloud infrastructure and platform services offered, OCI can help you optimize enterprise applications without costly rearchitecture, build and run cloud native or third-party apps with familiar open standards and open source tools, and harness your data with OCI services, such as Oracle MySQL Heatwave and Oracle Autonomous Database, to uncover new business value. OCI’s distributed cloud solutions are available wherever you need them, including on-premises with OCI Dedicated Region and Exadata Cloud@Customer, multicloud with Oracle Database Service for Microsoft Azure, or public cloud. OCI offers the fastest growing network of global data centers, with 41 cloud regions available to solve your toughest business challenges. This product is intended for Chief Technology Officer Vice President of Infrastructure Director of Information Technology Database Manager Engineering Manager Information Technology Manager Cloud Administrator Cloud Engineer Cloud Architect Media Products media viewer No more previous content Oracle Red Bull Racing's championship season powered by Oracle Cloud What's new and next for Oracle Cloud Infrastructure How NIBIO is fostering more sustainable forests using innovative sensors, andOCI and AI CJ Perez and SailGP make history with Oracle Cloud No more next content Featured customers of Oracle Cloud Infrastructure (OCI) Deutsche Bank Financial Services 3,196,098 followers SailGP Spectator Sports 64,588 followers Zoom IT Services and IT Consulting 640,753 followers TIM Brasil Telecommunications 659,578 followers Vodafone Telecommunications 2,488,540 followers Toyota Motor Corporation Motor Vehicle Manufacturing 2,293,377 followers Uber Internet Marketplace Platforms 3,365,124 followers FedEx Freight and Package Transportation 2,230,361 followers Show more Show less Similar products Workday Workday Enterprise Cloud Platforms Cisco+ Hybrid Cloud Cisco+ Hybrid Cloud Enterprise Cloud Platforms Cloud transformation Cloud transformation Enterprise Cloud Platforms Nutanix Central Nutanix Central Enterprise Cloud Platforms Nutanix Kubernetes Platform Nutanix Kubernetes Platform Enterprise Cloud Platforms Nutanix Enterprise AI Nutanix Enterprise AI Enterprise Cloud Platforms Sign in to see more Show more Show less Oracle Cloud products High Performance Computing on Oracle Cloud Infrastructure High Performance Computing on Oracle Cloud Infrastructure Enterprise Cloud Platforms OCI AI Infrastructure OCI AI Infrastructure Enterprise Cloud Platforms OCI Container Engine for Kubernetes OCI Container Engine for Kubernetes Container Management Software OCI Gen AI Service OCI Gen AI Service Enterprise Cloud Platforms Oracle Cloud Infrastructure Compute Oracle Cloud Infrastructure Compute Enterprise Cloud Platforms Oracle Cloud Observability and Management Oracle Cloud Observability and Management Cloud Management Platforms (CMP) Oracle Cloud@Customer Oracle Cloud@Customer Enterprise Cloud Platforms Oracle Distributed Cloud Oracle Distributed Cloud Enterprise Cloud Platforms Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://telegram.org/dl?tme=b9e0c2b0d45536d3a9_3727317574836440681 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebK Telegram WebA Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/cloudflare-workers?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Cloudflare Workers | LinkedIn Skip to main content LinkedIn Cloudflare in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloudflare Workers Server Virtualization Software by Cloudflare See who's skilled in this Add as skill Try now Report this product About Build your next application with Cloudflare Workers Media Products media viewer No more previous content Announcing Deploy to Cloudflare Workers We think Cloudflare Workers is the best serverless tool on the market, so we wanted to make it easier for developers to deploy projects and get started building cool stuff on the platform! Our new Deploy to Cloudflare Workers site is just that — a way for both new and experienced Workers users to deploy new serverless projects directly from GitHub. In just a few clicks, we'll configure and deploy the project for you, giving you a new GitHub repo to start hacking on your next great project! What Cloudflare Workers do? Building serverless applications with Cloudflare Workers' Cron Job Scheduler and Key Value Store Learn how to build an application with the the newly announced cron job scheduler, Cron Triggers, from Cloudflare Workers. In this demo, we will explain what Cron Triggers are, how to quickly get started using them, and how to write and deploy your own. We will also review how to integrate with Workers KV, our key value store that allows you to store data at the edge and retrieve it inside your Workers' project instead of sending that data to alternative platforms such as Postgres or Firebase. No more next content Featured customers of Cloudflare Workers npm, Inc. Software Development 11,912 followers DoorDash Software Development 1,437,130 followers 23andMe Non-profit Organizations 81,297 followers Timely IT Services and IT Consulting 5,725 followers Adobe Marketo Software Development 178,692 followers Cordial Software Development 48,215 followers MaxMind Technology, Information and Internet 2,991 followers Optimizely Software Development 167,115 followers Discord Software Development 467,975 followers Broadcom Semiconductor Manufacturing 608,798 followers Glossier, Inc. Personal Care Product Manufacturing 492,298 followers ProPublica Media Production 72,236 followers Show more Show less Similar products Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Cloudflare products Argo Smart Routing Argo Smart Routing Network Management Software Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare DNS Cloudflare DNS Managed DNS Services Software Cloudflare Load Balancing Cloudflare Load Balancing Load Balancing Software Cloudflare Registrar Cloudflare Registrar Managed DNS Services Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Cloudflare SSL / TLS Cloudflare SSL / TLS SSL Certificates Software Cloudflare WAF Cloudflare WAF Web Application Firewalls (WAF) Cloudflare Web Analytics Cloudflare Web Analytics Digital Analytics Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/company/npm-inc-?trk=products_details_guest_organization_name | npm, Inc. | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free npm, Inc. Software Development Oakland, CA 11,912 followers npm operates the world’s largest software registry. More than 150,000 companies use npm to build amazing things. Follow View all 18 employees Report this company About us Over 10 million software developers worldwide use npm, Inc.’s open source software and web registry to discover, share, and reuse packages of code. Our users download over 800,000 packages more than 7 billion times per week, and registry downloads have grown by more than 16x in the last two years. npm’s paid products and services offer teams and companies ways to organize, share, and secure code, integrate npm with testing and deployment tools, and bring code reuse into the enterprise. More than 150,000 companies, including BBC, Coinbase, eBay, Electronic Arts, Nvidia, and Slack rely on npm to reduce friction and build amazing things. Website http://npmjs.com External link for npm, Inc. Industry Software Development Company size 11-50 employees Headquarters Oakland, CA Type Privately Held Founded 2014 Locations Primary 1999 Harrison St Ste 1150 Oakland, CA 94612, US Get directions Employees at npm, Inc. Elad Ben Shmuel Md Raihan Patrick Oliver Tiavina MIchael Ralainirina See all employees Affiliated pages GitHub Software Development San Francisco, CA Similar pages GitHub Software Development San Francisco, CA Node.js Software Development San Francisco, CA Aikido Security Software Development React Software Development Menlo Park, California GitLab IT Services and IT Consulting San Francisco, California Microsoft Software Development Redmond, Washington Netlify Software Development San Francisco, California NPM US (New Project Media) Market Research Princeton, New Jersey NPM Recruitment Staffing and Recruiting Kandivali, 400101 ReactJS E-Learning Providers Show more similar pages Show fewer similar pages Browse jobs Cyber Security Specialist jobs 20,744 open jobs Developer jobs 258,935 open jobs Engineer jobs 555,845 open jobs Officer jobs 1,191,868 open jobs Cognos Developer jobs 1,399 open jobs Software Engineer jobs 300,699 open jobs Analyst jobs 694,057 open jobs Full Stack Engineer jobs 38,546 open jobs Legal Assistant jobs 23,617 open jobs Manager jobs 1,880,925 open jobs Intern jobs 71,196 open jobs Solutions Architect jobs 100,488 open jobs Assistant Professor jobs 13,039 open jobs Solutions Engineer jobs 92,218 open jobs Security Manager jobs 116,433 open jobs Quantitative Analyst jobs 19,570 open jobs Scientist jobs 48,969 open jobs Network Engineer jobs 173,828 open jobs Quantitative Developer jobs 11,546 open jobs Project Lead Developer jobs 118,123 open jobs Show more jobs like this Show fewer jobs like this Funding npm, Inc. 4 total rounds Last Round Secondary market Jul 11, 2019 External Crunchbase Link for last round of funding See more info on crunchbase More searches More searches Web Administrator jobs Web Editor jobs System Developer jobs Support Technician jobs Web Designer jobs Visual Designer jobs Developer jobs User Experience Designer jobs Product Designer jobs Designer jobs Engineer jobs Software Engineer jobs Coder jobs Full Stack Engineer jobs SQL Developer jobs Javascript Developer jobs Web Developer jobs Virtual Assistant jobs Firmware Engineer jobs C Developer jobs Research Analyst jobs Analyst jobs Scientist jobs Frontend Developer jobs Intern jobs Solutions Architect jobs Principal Program Manager jobs Technical Program Manager jobs Program Manager jobs Solutions Engineer jobs Mobile Engineer jobs Python Developer jobs Contract Software Engineer jobs Senior Product Manager jobs Student Software Engineer jobs Plant Director jobs Product Manager jobs Immigration Attorney jobs Process Technician jobs Software Engineering Manager jobs Maintenance Supervisor jobs Junior Software Engineer jobs Safety Manager jobs Maintenance Manager jobs Plant Manager jobs Manufacturing Engineer jobs Student jobs Technician jobs Supervisor jobs Recruiter jobs Marketing Manager jobs Director jobs Senior Network Engineer jobs Electrical Technician jobs Junior Web Developer jobs Foreperson jobs Electrician jobs Software Quality Assurance Engineer jobs Software Tester jobs Security Software Engineer jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at npm, Inc. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/categories/relational-database-management-systems?trk=products_details_guest_other_products_by_org_section_product_link_result-card_subtitle-click#main-content | Best Relational Database Management Systems | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Database Administrator (8) Chief Technology Officer (8) Chief Information Officer (5) Data Scientist (3) Information Technology Manager (3) See all products Find top products in Relational Database Management Systems category Software used to manage, maintain, and access data stored in structured tables. - Store and organize data in columns and rows - Manage simultaneous access of the same data by multiple users - Use Structured Query Language (SQL) to manipulate and view data - Establish ACID (Atomicity, Consistency, Isolation, Durability) compliance of stored data 70 results Amazon Aurora Relational Database Management Systems by Amazon Web Services (AWS) Amazon Aurora is a MySQL and PostgreSQL compatible relational database built for the cloud, that combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. View product Amazon RDS Relational Database Management Systems by Amazon Web Services (AWS) With Amazon RDS, set up, operate and scale a commercial or open source relational database in the cloud in just a few clicks while automating time-consuming administrative tasks. View product Google Cloud SQL Relational Database Management Systems by Google Cloud Cloud SQL is a fully managed service that makes it easy to set up, manage, and administer relational databases: PostgreSQL, MySQL, and SQL Server. View product Teradata Vantage Relational Database Management Systems by Teradata Teradata Vantage™ is the most complete cloud analytics and data platform for AI at scale. It combines the scalability of public clouds with the control of private clouds, all on the same portable software stack. Vantage works on public clouds like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud; hybrid multi-cloud setups; on premises; or on commodity hardware with VMware. It emphasizes fit-for-purpose compute connected through a unified data foundation, ensuring optimal performance and cost efficiency while enabling seamless data flow and collaboration across the organization. With no up-front costs and pay-as-you-go pricing, Vantage adapts to emerging needs, especially in the era of generative AI. Teradata Vantage® is the only platform with the massively parallel processing and multidimensional scalability to handle complex data workloads with the ease and flexibility needed to drive faster ROI across your enterprise. View product Cloud Native Database TDSQL-C Relational Database Management Systems by Tencent A cloud native database with high performance, storage capacity, and compatibility View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights SQL Server Relational Database Management Systems by Microsoft SQL Server Get the flexibility you need to use integrated solutions, apps, and innovations in technology with your data—wherever it lives—in the cloud, on-premises, or at the edge. View product CockroachDB Relational Database Management Systems by Cockroach Labs Run your business-critical applications across any environment — whether in the cloud, on-premises, or hybrid — with global scale and unmatched resilience. -> Scale to meet demand: as demand shifts, your CockroachDB clusters will automatically rebalance to ensure peak performance. -> Deliver always-on experiences: eliminate downtime & protect your data w/ multi-active availability & custom survival goals -> Ensure low-latency access to accurate data across the globe -> Simplify database operations CockroachDB delivers the reliability, robust consistency and ACID transactions of RDBMS, while offering the horizontal scaling and distributed architecture of NoSQL. All of this is built to thrive in any environment, ensuring effortless scalability, global availability and distribution, and continuous uptime all with a familiar, compliant SQL interface. Integrate across many systems including applications, analytics, streaming, security, logging, and observability. View product YugabyteDB Relational Database Management Systems by Yugabyte Open source is at the heart of YugabyteDB, a distributed SQL database. Join our community and see how our users are using YugabyteDB for their applications. View product SingleStoreDB Relational Database Management Systems by SingleStore SingleStore is a cloud database available on leading public clouds and delivers elastic scalability, high availability and exceptional price-performance for your applications, without the burden of managing your data infrastructure. SingleStore scales storage independently of compute and includes Jupyter notebooks, data integration services and a compute service for running AI workloads — meaning developers, ML engineers and data engineers can quickly build awesome things together. View product MariaDB Enterprise Platform Relational Database Management Systems by MariaDB MariaDB Enterprise Platform is engineered to deliver best-in-class performance, data security, replication, clustering and high availability for production workloads. MariaDB Enterprise Platform empowers modern data strategies with an end-to-end database solution, delivering consistent performance and unwavering stability for mission-critical applications in demanding environments. Eliminate database sprawl and simplify your data landscape by running all your workloads in a single, robust MariaDB environment, powered by open source technology and fortified with enterprise-grade reliability, security and support. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:15 |
http://www.jmlr.org/mloss | Journal of Machine Learning Research Home Page Papers Submissions News Scope --> Editorial Board Special Issues Open Source Software Proceedings (PMLR) Data (DMLR) Transactions (TMLR) Search Statistics Login Frequently Asked Questions Contact Us Machine Learning Open Source Software To support the open source software movement, JMLR MLOSS publishes contributions related to implementations of non-trivial machine learning algorithms, toolboxes or even languages for scientific computing. Submission instructions are available here . TorchCP: A Python Library for Conformal Prediction Jianguo Huang, Jianqing Song, Xuanning Zhou, Bingyi Jing, Hongxin Wei ; (266):1−25, 2025. [ abs ][ pdf ][ bib ] [ code ] Talent: A Tabular Analytics and Learning Toolbox Si-Yang Liu, Hao-Run Cai, Qi-Le Zhou, Huai-Hong Yin, Tao Zhou, Jun-Peng Jiang, Han-Jia Ye ; (226):1−16, 2025. [ abs ][ pdf ][ bib ] [ code ] BoFire: Bayesian Optimization Framework Intended for Real Experiments Johannes P. Dürholt, Thomas S. Asche, Johanna Kleinekorte, Gabriel Mancino-Ball, Benjamin Schiller, Simon Sung, Julian Keupp, Aaron Osburg, Toby Boyne, Ruth Misener, Rosona Eldred, Chrysoula Kappatou, Robert M. Lee, Dominik Linzner, Wagner Steuer Costa, David Walz, Niklas Wulkow, Behrang Shafei ; (204):1−7, 2025. [ abs ][ pdf ][ bib ] [ code ] WEFE: A Python Library for Measuring and Mitigating Bias in Word Embeddings Pablo Badilla, Felipe Bravo-Marquez, María José Zambrano, Jorge Pérez ; (156):1−6, 2025. [ abs ][ pdf ][ bib ] [ code ] skglm: Improving scikit-learn for Regularized Generalized Linear Models Badr Moufad, Pierre-Antoine Bannier, Quentin Bertrand, Quentin Klopfenstein, Mathurin Massias ; (149):1−6, 2025. [ abs ][ pdf ][ bib ] [ code ] GraphNeuralNetworks.jl: Deep Learning on Graphs with Julia Carlo Lucibello, Aurora Rossi ; (80):1−6, 2025. [ abs ][ pdf ][ bib ] [ code ] Ontolearn---A Framework for Large-scale OWL Class Expression Learning in Python Caglar Demir, Alkid Baci, N'Dah Jean Kouagou, Leonie Nora Sieger, Stefan Heindorf, Simon Bin, Lukas Blübaum, Alexander Bigerl, Axel-Cyrille Ngonga Ngomo ; (63):1−6, 2025. [ abs ][ pdf ][ bib ] [ code ] Lightning UQ Box: Uncertainty Quantification for Neural Networks Nils Lehmann, Nina Maria Gottschling, Jakob Gawlikowski, Adam J. Stewart, Stefan Depeweg, Eric Nalisnick ; (54):1−7, 2025. [ abs ][ pdf ][ bib ] [ code ] PFLlib: A Beginner-Friendly and Comprehensive Personalized Federated Learning Library and Benchmark Jianqing Zhang, Yang Liu, Yang Hua, Hao Wang, Tao Song, Zhengui Xue, Ruhui Ma, Jian Cao ; (50):1−10, 2025. [ abs ][ pdf ][ bib ] [ code ] gsplat: An Open-Source Library for Gaussian Splatting Vickie Ye, Ruilong Li, Justin Kerr, Matias Turkulainen, Brent Yi, Zhuoyang Pan, Otto Seiskari, Jianbo Ye, Jeffrey Hu, Matthew Tancik, Angjoo Kanazawa ; (34):1−17, 2025. [ abs ][ pdf ][ bib ] [ code ] depyf: Open the Opaque Box of PyTorch Compiler for Machine Learning Researchers Kaichao You, Runsheng Bai, Meng Cao, Jianmin Wang, Ion Stoica, Mingsheng Long ; (25):1−18, 2025. [ abs ][ pdf ][ bib ] [ code ] PyDMD: A Python Package for Robust Dynamic Mode Decomposition Sara M. Ichinaga, Francesco Andreuzzi, Nicola Demo, Marco Tezzele, Karl Lapo, Gianluigi Rozza, Steven L. Brunton, J. Nathan Kutz ; (417):1−9, 2024. [ abs ][ pdf ][ bib ] [ code ] KerasCV and KerasNLP: Multi-framework Models Matthew Watson, Divyashree Shivakumar Sreepathihalli, François Chollet, Martin Górner, Kiranbir Sodhia, Ramesh Sampath, Tirth Patel, Haifeng Jin, Neel Kovelamudi, Gabriel Rasskin, Samaneh Saadat, Luke Wood, Chen Qian, Jonathan Bischof, Ian Stenbit, Abheesht Sharma, Anshuman Mishra ; (375):1−10, 2024. [ abs ][ pdf ][ bib ] [ code ] TopoX: A Suite of Python Packages for Machine Learning on Topological Domains Mustafa Hajij, Mathilde Papillon, Florian Frantzen, Jens Agerberg, Ibrahem AlJabea, Rubén Ballester, Claudio Battiloro, Guillermo Bernárdez, Tolga Birdal, Aiden Brent, Peter Chin, Sergio Escalera, Simone Fiorellino, Odin Hoff Gardaa, Gurusankar Gopalakrishnan, Devendra Govil, Josef Hoppe, Maneel Reddy Karri, Jude Khouja, Manuel Lecha, Neal Livesay, Jan Meißner, Soham Mukherjee, Alexander Nikitin, Theodore Papamarkou, Jaro Prílepok, Karthikeyan Natesan Ramamurthy, Paul Rosen, Aldo Guzmán-Sáenz, Alessandro Salatiello, Shreyas N. Samaga, Simone Scardapane, Michael T. Schaub, Luca Scofano, Indro Spinelli, Lev Telyatnikov, Quang Truong, Robin Walters, Maosheng Yang, Olga Zaghen, Ghada Zamzmi, Ali Zia, Nina Miolane ; (374):1−8, 2024. [ abs ][ pdf ][ bib ] [ code ] PGMax: Factor Graphs for Discrete Probabilistic Graphical Models and Loopy Belief Propagation in JAX Guangyao Zhou, Antoine Dedieu, Nishanth Kumar, Wolfgang Lehrach, Shrinu Kushagra, Dileep George, Miguel Lázaro-Gredilla ; (371):1−25, 2024. [ abs ][ pdf ][ bib ] [ code ] Aequitas Flow: Streamlining Fair ML Experimentation Sérgio Jesus, Pedro Saleiro, Inês Oliveira e Silva, Beatriz M. Jorge, Rita P. Ribeiro, João Gama, Pedro Bizarro, Rayid Ghani ; (354):1−7, 2024. [ abs ][ pdf ][ bib ] [ code ] Open-Source Conversational AI with SpeechBrain 1.0 Mirco Ravanelli, Titouan Parcollet, Adel Moumen, Sylvain de Langen, Cem Subakan, Peter Plantinga, Yingzhi Wang, Pooneh Mousavi, Luca Della Libera, Artem Ploujnikov, Francesco Paissan, Davide Borra, Salah Zaiem, Zeyu Zhao, Shucong Zhang, Georgios Karakasidis, Sung-Lin Yeh, Pierre Champion, Aku Rouhe, Rudolf Braun, Florian Mai, Juan Zuluaga-Gomez, Seyed Mahed Mousavi, Andreas Nautsch, Ha Nguyen, Xuechen Liu, Sangeet Sagar, Jarod Duret, Salima Mdhaffar, Gaëlle Laperrière, Mickael Rouvier, Renato De Mori, Yannick Estève ; (333):1−11, 2024. [ abs ][ pdf ][ bib ] [ code ] RLtools: A Fast, Portable Deep Reinforcement Learning Library for Continuous Control Jonas Eschmann, Dario Albani, Giuseppe Loianno ; (301):1−19, 2024. [ abs ][ pdf ][ bib ] [ code ] PyPop7: A Pure-Python Library for Population-Based Black-Box Optimization Qiqi Duan, Guochen Zhou, Chang Shao, Zhuowei Wang, Mingyang Feng, Yuwei Huang, Yajing Tan, Yijun Yang, Qi Zhao, Yuhui Shi ; (296):1−28, 2024. [ abs ][ pdf ][ bib ] [ code ] skscope: Fast Sparsity-Constrained Optimization in Python Zezhi Wang, Junxian Zhu, Xueqin Wang, Jin Zhu, Huiyang Pen, Peng Chen, Anran Wang, Xiaoke Zhang ; (290):1−9, 2024. [ abs ][ pdf ][ bib ] [ code ] aeon: a Python Toolkit for Learning from Time Series Matthew Middlehurst, Ali Ismail-Fawaz, Antoine Guillaume, Christopher Holder, David Guijo-Rubio, Guzal Bulatova, Leonidas Tsaprounis, Lukasz Mentel, Martin Walter, Patrick Schäfer, Anthony Bagnall ; (289):1−10, 2024. [ abs ][ pdf ][ bib ] [ code ] OmniSafe: An Infrastructure for Accelerating Safe Reinforcement Learning Research Jiaming Ji, Jiayi Zhou, Borong Zhang, Juntao Dai, Xuehai Pan, Ruiyang Sun, Weidong Huang, Yiran Geng, Mickel Liu, Yaodong Yang ; (285):1−6, 2024. [ abs ][ pdf ][ bib ] [ code ] Pearl: A Production-Ready Reinforcement Learning Agent Zheqing Zhu, Rodrigo de Salvo Braz, Jalaj Bhandari, Daniel Jiang, Yi Wan, Yonathan Efroni, Liyuan Wang, Ruiyang Xu, Hongbo Guo, Alex Nikulkov, Dmytro Korenkevych, Urun Dogan, Frank Cheng, Zheng Wu, Wanqiao Xu ; (273):1−30, 2024. [ abs ][ pdf ][ bib ] [ code ] pgmpy: A Python Toolkit for Bayesian Networks Ankur Ankan, Johannes Textor ; (265):1−8, 2024. [ abs ][ pdf ][ bib ] [ code ] PromptBench: A Unified Library for Evaluation of Large Language Models Kaijie Zhu, Qinlin Zhao, Hao Chen, Jindong Wang, Xing Xie ; (254):1−22, 2024. [ abs ][ pdf ][ bib ] [ code ] Fortuna: A Library for Uncertainty Quantification in Deep Learning Gianluca Detommaso, Alberto Gasparin, Michele Donini, Matthias Seeger, Andrew Gordon Wilson, Cedric Archambeau ; (238):1−7, 2024. [ abs ][ pdf ][ bib ] [ code ] BenchMARL: Benchmarking Multi-Agent Reinforcement Learning Matteo Bettini, Amanda Prorok, Vincent Moens ; (217):1−10, 2024. [ abs ][ pdf ][ bib ] [ code ] PAMI: An Open-Source Python Library for Pattern Mining Uday Kiran Rage, Veena Pamalla, Masashi Toyoda, Masaru Kitsuregawa ; (209):1−6, 2024. [ abs ][ pdf ][ bib ] [ code ] DoWhy-GCM: An Extension of DoWhy for Causal Inference in Graphical Causal Models Patrick Blöbaum, Peter Götz, Kailash Budhathoki, Atalanti A. Mastakouri, Dominik Janzing ; (147):1−7, 2024. [ abs ][ pdf ][ bib ] [ code ] PyGOD: A Python Library for Graph Outlier Detection Kay Liu, Yingtong Dou, Xueying Ding, Xiyang Hu, Ruitong Zhang, Hao Peng, Lichao Sun, Philip S. Yu ; (141):1−9, 2024. [ abs ][ pdf ][ bib ] [ code ] OpenBox: A Python Toolkit for Generalized Black-box Optimization Huaijun Jiang, Yu Shen, Yang Li, Beicheng Xu, Sixian Du, Wentao Zhang, Ce Zhang, Bin Cui ; (120):1−11, 2024. [ abs ][ pdf ][ bib ] [ code ] QDax: A Library for Quality-Diversity and Population-based Algorithms with Hardware Acceleration Felix Chalumeau, Bryan Lim, Raphaël Boige, Maxime Allard, Luca Grillotti, Manon Flageat, Valentin Macé, Guillaume Richard, Arthur Flajolet, Thomas Pierrot, Antoine Cully ; (108):1−16, 2024. [ abs ][ pdf ][ bib ] [ code ] ptwt - The PyTorch Wavelet Toolbox Moritz Wolter, Felix Blanke, Jochen Garcke, Charles Tapley Hoyt ; (80):1−7, 2024. [ abs ][ pdf ][ bib ] [ code ] On Unbiased Estimation for Partially Observed Diffusions Jeremy Heng, Jeremie Houssineau, Ajay Jasra ; (66):1−66, 2024. [ abs ][ pdf ][ bib ] [ code ] Causal-learn: Causal Discovery in Python Yujia Zheng, Biwei Huang, Wei Chen, Joseph Ramsey, Mingming Gong, Ruichu Cai, Shohei Shimizu, Peter Spirtes, Kun Zhang ; (60):1−8, 2024. [ abs ][ pdf ][ bib ] [ code ] Invariant and Equivariant Reynolds Networks Akiyoshi Sannai, Makoto Kawano, Wataru Kumagai ; (42):1−36, 2024. [ abs ][ pdf ][ bib ] [ code ] Pygmtools: A Python Graph Matching Toolkit Runzhong Wang, Ziao Guo, Wenzheng Pan, Jiale Ma, Yikai Zhang, Nan Yang, Qi Liu, Longxuan Wei, Hanxue Zhang, Chang Liu, Zetian Jiang, Xiaokang Yang, Junchi Yan ; (33):1−7, 2024. [ abs ][ pdf ][ bib ] [ code ] Scaling Up Models and Data with t5x and seqio Adam Roberts, Hyung Won Chung, Gaurav Mishra, Anselm Levskaya, James Bradbury, Daniel Andor, Sharan Narang, Brian Lester, Colin Gaffney, Afroz Mohiuddin, Curtis Hawthorne, Aitor Lewkowycz, Alex Salcianu, Marc van Zee, Jacob Austin, Sebastian Goodman, Livio Baldini Soares, Haitang Hu, Sasha Tsvyashchenko, Aakanksha Chowdhery, Jasmijn Bastings, Jannis Bulian, Xavier Garcia, Jianmo Ni, Andrew Chen, Kathleen Kenealy, Kehang Han, Michelle Casbon, Jonathan H. Clark, Stephan Lee, Dan Garrette, James Lee-Thorp, Colin Raffel, Noam Shazeer, Marvin Ritter, Maarten Bosma, Alexandre Passos, Jeremy Maitin-Shepard, Noah Fiedel, Mark Omernick, Brennan Saeta, Ryan Sepassi, Alexander Spiridonov, Joshua Newlan, Andrea Gesmundo ; (377):1−8, 2023. [ abs ][ pdf ][ bib ] [ code ] TorchOpt: An Efficient Library for Differentiable Optimization Jie Ren*, Xidong Feng*, Bo Liu*, Xuehai Pan*, Yao Fu, Luo Mai, Yaodong Yang ; (367):1−14, 2023. [ abs ][ pdf ][ bib ] [ code ] Avalanche: A PyTorch Library for Deep Continual Learning Antonio Carta, Lorenzo Pellegrini, Andrea Cossu, Hamed Hemati, Vincenzo Lomonaco ; (363):1−6, 2023. [ abs ][ pdf ][ bib ] [ code ] MARLlib: A Scalable and Efficient Multi-agent Reinforcement Learning Library Siyi Hu, Yifan Zhong, Minquan Gao, Weixun Wang, Hao Dong, Xiaodan Liang, Zhihui Li, Xiaojun Chang, Yaodong Yang ; (315):1−23, 2023. [ abs ][ pdf ][ bib ] [ code ] Fairlearn: Assessing and Improving Fairness of AI Systems Hilde Weerts, Miroslav Dudík, Richard Edgar, Adrin Jalali, Roman Lutz, Michael Madaio ; (257):1−8, 2023. [ abs ][ pdf ][ bib ] [ code ] Torchhd: An Open Source Python Library to Support Research on Hyperdimensional Computing and Vector Symbolic Architectures Mike Heddes, Igor Nunes, Pere Vergés, Denis Kleyko, Danny Abraham, Tony Givargis, Alexandru Nicolau, Alexander Veidenbaum ; (255):1−10, 2023. [ abs ][ pdf ][ bib ] [ code ] skrl: Modular and Flexible Library for Reinforcement Learning Antonio Serrano-Muñoz, Dimitrios Chrysostomou, Simon Bøgh, Nestor Arana-Arexolaleiba ; (254):1−9, 2023. [ abs ][ pdf ][ bib ] [ code ] MultiZoo and MultiBench: A Standardized Toolkit for Multimodal Deep Learning Paul Pu Liang, Yiwei Lyu, Xiang Fan, Arav Agarwal, Yun Cheng, Louis-Philippe Morency, Ruslan Salakhutdinov ; (234):1−7, 2023. [ abs ][ pdf ][ bib ] [ code ] Merlion: End-to-End Machine Learning for Time Series Aadyot Bhatnagar, Paul Kassianik, Chenghao Liu, Tian Lan, Wenzhuo Yang, Rowan Cassius, Doyen Sahoo, Devansh Arpit, Sri Subramanian, Gerald Woo, Amrita Saha, Arun Kumar Jagota, Gokulakrishnan Gopalakrishnan, Manpreet Singh, K C Krithika, Sukumar Maddineni, Daeki Cho, Bo Zong, Yingbo Zhou, Caiming Xiong, Silvio Savarese, Steven Hoi, Huan Wang ; (226):1−6, 2023. [ abs ][ pdf ][ bib ] [ code ] LibMTL: A Python Library for Deep Multi-Task Learning Baijiong Lin, Yu Zhang ; (209):1−7, 2023. [ abs ][ pdf ][ bib ] [ code ] L0Learn: A Scalable Package for Sparse Learning using L0 Regularization Hussein Hazimeh, Rahul Mazumder, Tim Nonet ; (205):1−8, 2023. [ abs ][ pdf ][ bib ] [ code ] CodaLab Competitions: An Open Source Platform to Organize Scientific Challenges Adrien Pavao, Isabelle Guyon, Anne-Catherine Letournel, Dinh-Tuan Tran, Xavier Baro, Hugo Jair Escalante, Sergio Escalera, Tyler Thomas, Zhen Xu ; (198):1−6, 2023. [ abs ][ pdf ][ bib ] [ code ] MALib: A Parallel Framework for Population-based Multi-agent Reinforcement Learning Ming Zhou, Ziyu Wan, Hanjing Wang, Muning Wen, Runzhe Wu, Ying Wen, Yaodong Yang, Yong Yu, Jun Wang, Weinan Zhang ; (150):1−12, 2023. [ abs ][ pdf ][ bib ] [ code ] SQLFlow: An Extensible Toolkit Integrating DB and AI Jun Zhou, Ke Zhang, Lin Wang, Hua Wu, Yi Wang, ChaoChao Chen ; (116):1−9, 2023. [ abs ][ pdf ][ bib ] [ code ] FedLab: A Flexible Federated Learning Framework Dun Zeng, Siqi Liang, Xiangjing Hu, Hui Wang, Zenglin Xu ; (100):1−7, 2023. [ abs ][ pdf ][ bib ] [ code ] Quantus: An Explainable AI Toolkit for Responsible Evaluation of Neural Network Explanations and Beyond Anna Hedström, Leander Weber, Daniel Krakowczyk, Dilyara Bareeva, Franz Motzkus, Wojciech Samek, Sebastian Lapuschkin, Marina M.-C. Höhne ; (34):1−11, 2023. [ abs ][ pdf ][ bib ] [ code ] HiClass: a Python Library for Local Hierarchical Classification Compatible with Scikit-learn Fábio M. Miranda, Niklas Köhnecke, Bernhard Y. Renard ; (29):1−17, 2023. [ abs ][ pdf ][ bib ] [ code ] Impact of classification difficulty on the weight matrices spectra in Deep Learning and application to early-stopping Xuran Meng, Jeff Yao ; (28):1−40, 2023. [ abs ][ pdf ][ bib ] [ code ] Python package for causal discovery based on LiNGAM Takashi Ikeuchi, Mayumi Ide, Yan Zeng, Takashi Nicholas Maeda, Shohei Shimizu ; (14):1−8, 2023. [ abs ][ pdf ][ bib ] [ code ] AutoKeras: An AutoML Library for Deep Learning Haifeng Jin, François Chollet, Qingquan Song, Xia Hu ; (6):1−6, 2023. [ abs ][ pdf ][ bib ] [ code ] OMLT: Optimization & Machine Learning Toolkit Francesco Ceccon, Jordan Jalving, Joshua Haddad, Alexander Thebelt, Calvin Tsay, Carl D Laird, Ruth Misener ; (349):1−8, 2022. [ abs ][ pdf ][ bib ] [ code ] WarpDrive: Fast End-to-End Deep Multi-Agent Reinforcement Learning on a GPU Tian Lan, Sunil Srinivasa, Huan Wang, Stephan Zheng ; (316):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] d3rlpy: An Offline Deep Reinforcement Learning Library Takuma Seno, Michita Imai ; (315):1−20, 2022. [ abs ][ pdf ][ bib ] [ code ] JsonGrinder.jl: automated differentiable neural architecture for embedding arbitrary JSON data Šimon Mandlík, Matěj Račinský, Viliam Lisý, Tomáš Pevný ; (298):1−5, 2022. [ abs ][ pdf ][ bib ] [ code ] ReservoirComputing.jl: An Efficient and Modular Library for Reservoir Computing Models Francesco Martinuzzi, Chris Rackauckas, Anas Abdelrehim, Miguel D. Mahecha, Karin Mora ; (288):1−8, 2022. [ abs ][ pdf ][ bib ] [ code ] Deepchecks: A Library for Testing and Validating Machine Learning Models and Data Shir Chorev, Philip Tannor, Dan Ben Israel, Noam Bressler, Itay Gabbay, Nir Hutnik, Jonatan Liberman, Matan Perlmutter, Yurii Romanyshyn, Lior Rokach ; (285):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] CleanRL: High-quality Single-file Implementations of Deep Reinforcement Learning Algorithms Shengyi Huang, Rousslan Fernand Julien Dossa, Chang Ye, Jeff Braga, Dipam Chakraborty, Kinal Mehta, João G.M. Araújo ; (274):1−18, 2022. [ abs ][ pdf ][ bib ] [ code ] Tianshou: A Highly Modularized Deep Reinforcement Learning Library Jiayi Weng, Huayu Chen, Dong Yan, Kaichao You, Alexis Duburcq, Minghao Zhang, Yi Su, Hang Su, Jun Zhu ; (267):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] abess: A Fast Best-Subset Selection Library in Python and R Jin Zhu, Xueqin Wang, Liyuan Hu, Junhao Huang, Kangkang Jiang, Yanhang Zhang, Shiyun Lin, Junxian Zhu ; (202):1−7, 2022. [ abs ][ pdf ][ bib ] [ code ] InterpretDL: Explaining Deep Models in PaddlePaddle Xuhong Li, Haoyi Xiong, Xingjian Li, Xuanyu Wu, Zeyu Chen, Dejing Dou ; (197):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] ktrain: A Low-Code Library for Augmented Machine Learning Arun S. Maiya ; (158):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] Darts: User-Friendly Modern Machine Learning for Time Series Julien Herzen, Francesco Lässig, Samuele Giuliano Piazzetta, Thomas Neuer, Léo Tafti, Guillaume Raille, Tomas Van Pottelbergh, Marek Pasieka, Andrzej Skrodzki, Nicolas Huguenin, Maxime Dumonal, Jan Kościsz, Dennis Bader, Frédérick Gusset, Mounir Benheddi, Camila Williamson, Michal Kosinski, Matej Petrik, Gaël Grosch ; (124):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] solo-learn: A Library of Self-supervised Methods for Visual Representation Learning Victor Guilherme Turrisi da Costa, Enrico Fini, Moin Nabi, Nicu Sebe, Elisa Ricci ; (56):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] SMAC3: A Versatile Bayesian Optimization Package for Hyperparameter Optimization Marius Lindauer, Katharina Eggensperger, Matthias Feurer, André Biedenkapp, Difan Deng, Carolin Benjamins, Tim Ruhkopf, René Sass, Frank Hutter ; (54):1−9, 2022. [ abs ][ pdf ][ bib ] [ code ] DoubleML - An Object-Oriented Implementation of Double Machine Learning in Python Philipp Bach, Victor Chernozhukov, Malte S. Kurz, Martin Spindler ; (53):1−6, 2022. [ abs ][ pdf ][ bib ] [ code ] Toolbox for Multimodal Learn (scikit-multimodallearn) Dominique Benielli, Baptiste Bauvin, Sokol Koço, Riikka Huusari, Cécile Capponi, Hachem Kadri, François Laviolette ; (51):1−7, 2022. [ abs ][ pdf ][ bib ] [ code ] Stable-Baselines3: Reliable Reinforcement Learning Implementations Antonin Raffin, Ashley Hill, Adam Gleave, Anssi Kanervisto, Maximilian Ernestus, Noah Dormann ; (268):1−8, 2021. [ abs ][ pdf ][ bib ] [ code ] DIG: A Turnkey Library for Diving into Graph Deep Learning Research Meng Liu, Youzhi Luo, Limei Wang, Yaochen Xie, Hao Yuan, Shurui Gui, Haiyang Yu, Zhao Xu, Jingtun Zhang, Yi Liu, Keqiang Yan, Haoran Liu, Cong Fu, Bora M Oztekin, Xuan Zhang, Shuiwang Ji ; (240):1−9, 2021. [ abs ][ pdf ][ bib ] [ code ] sklvq: Scikit Learning Vector Quantization Rick van Veen, Michael Biehl, Gert-Jan de Vries ; (231):1−6, 2021. [ abs ][ pdf ][ bib ] [ code ] FATE: An Industrial Grade Platform for Collaborative Learning With Data Protection Yang Liu, Tao Fan, Tianjian Chen, Qian Xu, Qiang Yang ; (226):1−6, 2021. [ abs ][ pdf ][ bib ] [ code ] TensorHive: Management of Exclusive GPU Access for Distributed Machine Learning Workloads Paweł Rościszewski, Michał Martyniak, Filip Schodowski ; (215):1−5, 2021. [ abs ][ pdf ][ bib ] [ code ] dalex: Responsible Machine Learning with Interactive Explainability and Fairness in Python Hubert Baniecki, Wojciech Kretowicz, Piotr Piątyszek, Jakub Wiśniewski, Przemysław Biecek ; (214):1−7, 2021. [ abs ][ pdf ][ bib ] [ code ] mlr3pipelines - Flexible Machine Learning Pipelines in R Martin Binder, Florian Pfisterer, Michel Lang, Lennart Schneider, Lars Kotthoff, Bernd Bischl ; (184):1−7, 2021. [ abs ][ pdf ][ bib ] [ code ] Alibi Explain: Algorithms for Explaining Machine Learning Models Janis Klaise, Arnaud Van Looveren, Giovanni Vacanti, Alexandru Coca ; (181):1−7, 2021. [ abs ][ pdf ][ bib ] [ code ] The ensmallen library for flexible numerical optimization Ryan R. Curtin, Marcus Edel, Rahul Ganesh Prabhu, Suryoday Basak, Zhihao Lou, Conrad Sanderson ; (166):1−6, 2021. [ abs ][ pdf ][ bib ] [ code ] MushroomRL: Simplifying Reinforcement Learning Research Carlo D'Eramo, Davide Tateo, Andrea Bonarini, Marcello Restelli, Jan Peters ; (131):1−5, 2021. [ abs ][ pdf ][ bib ] [ code ] River: machine learning for streaming data in Python Jacob Montiel, Max Halford, Saulo Martiello Mastelini, Geoffrey Bolmier, Raphael Sourty, Robin Vaysse, Adil Zouitine, Heitor Murilo Gomes, Jesse Read, Talel Abdessalem, Albert Bifet ; (110):1−8, 2021. [ abs ][ pdf ][ bib ] [ code ] mvlearn: Multiview Machine Learning in Python Ronan Perry, Gavin Mischler, Richard Guo, Theodore Lee, Alexander Chang, Arman Koul, Cameron Franz, Hugo Richard, Iain Carmichael, Pierre Ablin, Alexandre Gramfort, Joshua T. Vogelstein ; (109):1−7, 2021. [ abs ][ pdf ][ bib ] [ code ] OpenML-Python: an extensible Python API for OpenML Matthias Feurer, Jan N. van Rijn, Arlind Kadra, Pieter Gijsbers, Neeratyoy Mallik, Sahithya Ravi, Andreas Müller, Joaquin Vanschoren, Frank Hutter ; (100):1−5, 2021. [ abs ][ pdf ][ bib ] [ code ] POT: Python Optimal Transport Rémi Flamary, Nicolas Courty, Alexandre Gramfort, Mokhtar Z. Alaya, Aurélie Boisbunon, Stanislas Chambon, Laetitia Chapel, Adrien Corenflos, Kilian Fatras, Nemo Fournier, Léo Gautheron, Nathalie T.H. Gayraud, Hicham Janati, Alain Rakotomamonjy, Ievgen Redko, Antoine Rolet, Antony Schutz, Vivien Seguy, Danica J. Sutherland, Romain Tavenard, Alexander Tong, Titouan Vayer ; (78):1−8, 2021. [ abs ][ pdf ][ bib ] [ code ] ChainerRL: A Deep Reinforcement Learning Library Yasuhiro Fujita, Prabhat Nagarajan, Toshiki Kataoka, Takahiro Ishikawa ; (77):1−14, 2021. [ abs ][ pdf ][ bib ] [ code ] Kernel Operations on the GPU, with Autodiff, without Memory Overflows Benjamin Charlier, Jean Feydy, Joan Alexis Glaunès, François-David Collin, Ghislain Durif ; (74):1−6, 2021. [ abs ][ pdf ][ bib ] [ code ] giotto-tda: : A Topological Data Analysis Toolkit for Machine Learning and Data Exploration Guillaume Tauzin, Umberto Lupo, Lewis Tunstall, Julian Burella Pérez, Matteo Caorsi, Anibal M. Medina-Mardones, Alberto Dassatti, Kathryn Hess ; (39):1−6, 2021. [ abs ][ pdf ][ bib ] [ code ] Pykg2vec: A Python Library for Knowledge Graph Embedding Shih-Yuan Yu, Sujit Rokka Chhetri, Arquimedes Canedo, Palash Goyal, Mohammad Abdullah Al Faruque ; (16):1−6, 2021. [ abs ][ pdf ][ bib ] [ code ] algcomparison: Comparing the Performance of Graphical Structure Learning Algorithms with TETRAD Joseph D. Ramsey, Daniel Malinsky, Kevin V. Bui ; (238):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] Geomstats: A Python Package for Riemannian Geometry in Machine Learning Nina Miolane, Nicolas Guigui, Alice Le Brigant, Johan Mathe, Benjamin Hou, Yann Thanwerdas, Stefan Heyder, Olivier Peltre, Niklas Koep, Hadi Zaatiti, Hatem Hajri, Yann Cabanes, Thomas Gerald, Paul Chauchat, Christian Shewmake, Daniel Brooks, Bernhard Kainz, Claire Donnat, Susan Holmes, Xavier Pennec ; (223):1−9, 2020. [ abs ][ pdf ][ bib ] [ code ] scikit-survival: A Library for Time-to-Event Analysis Built on Top of scikit-learn Sebastian Pölsterl ; (212):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] Scikit-network: Graph Analysis in Python Thomas Bonald, Nathan de Lara, Quentin Lutz, Bertrand Charpentier ; (185):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] apricot: Submodular selection for data summarization in Python Jacob Schreiber, Jeffrey Bilmes, William Stafford Noble ; (161):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] metric-learn: Metric Learning Algorithms in Python William de Vazelhes, CJ Carey, Yuan Tang, Nathalie Vauquier, Aurélien Bellet ; (138):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] Probabilistic Learning on Graphs via Contextual Architectures Davide Bacciu, Federico Errica, Alessio Micheli ; (134):1−39, 2020. [ abs ][ pdf ][ bib ] [ code ] AI Explainability 360: An Extensible Toolkit for Understanding Data and Machine Learning Models Vijay Arya, Rachel K. E. Bellamy, Pin-Yu Chen, Amit Dhurandhar, Michael Hind, Samuel C. Hoffman, Stephanie Houde, Q. Vera Liao, Ronny Luss, Aleksandra Mojsilović, Sami Mourad, Pablo Pedemonte, Ramya Raghavendra, John T. Richards, Prasanna Sattigeri, Karthikeyan Shanmugam, Moninder Singh, Kush R. Varshney, Dennis Wei, Yunfeng Zhang ; (130):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] Apache Mahout: Machine Learning on Distributed Dataflow Systems Robin Anil, Gokhan Capan, Isabel Drost-Fromm, Ted Dunning, Ellen Friedman, Trevor Grant, Shannon Quinn, Paritosh Ranjan, Sebastian Schelter, Özgür Yılmazel ; (127):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] Tslearn, A Machine Learning Toolkit for Time Series Data Romain Tavenard, Johann Faouzi, Gilles Vandewiele, Felix Divo, Guillaume Androz, Chester Holtz, Marie Payne, Roman Yurchak, Marc Rußwurm, Kushal Kolar, Eli Woods ; (118):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] GluonTS: Probabilistic and Neural Time Series Modeling in Python Alexander Alexandrov, Konstantinos Benidis, Michael Bohlke-Schneider, Valentin Flunkert, Jan Gasthaus, Tim Januschowski, Danielle C. Maddix, Syama Rangapuram, David Salinas, Jasper Schulz, Lorenzo Stella, Ali Caner Türkmen, Yuyang Wang ; (116):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] MFE: Towards reproducible meta-feature extraction Edesio Alcobaça, Felipe Siqueira, Adriano Rivolli, Luís P. F. Garcia, Jefferson T. Oliva, André C. P. L. F. de Carvalho ; (111):1−5, 2020. [ abs ][ pdf ][ bib ] [ code ] ThunderGBM: Fast GBDTs and Random Forests on GPUs Zeyi Wen, Hanfeng Liu, Jiashuai Shi, Qinbin Li, Bingsheng He, Jian Chen ; (108):1−5, 2020. [ abs ][ pdf ][ bib ] [ code ] AI-Toolbox: A C++ library for Reinforcement Learning and Planning (with Python Bindings) Eugenio Bargiacchi, Diederik M. Roijers, Ann Nowé ; (102):1−12, 2020. [ abs ][ pdf ][ bib ] [ code ] pyDML: A Python Library for Distance Metric Learning Juan Luis Suárez, Salvador García, Francisco Herrera ; (96):1−7, 2020. [ abs ][ pdf ][ bib ] [ code ] Cornac: A Comparative Framework for Multimodal Recommender Systems Aghiles Salah, Quoc-Tuan Truong, Hady W. Lauw ; (95):1−5, 2020. [ abs ][ pdf ][ bib ] [ code ] Kymatio: Scattering Transforms in Python Mathieu Andreux, Tomás Angles, Georgios Exarchakis, Roberto Leonarduzzi, Gaspar Rochette, Louis Thiry, John Zarka, Stéphane Mallat, Joakim Andén, Eugene Belilovsky, Joan Bruna, Vincent Lostanlen, Muawiz Chaudhary, Matthew J. Hirn, Edouard Oyallon, Sixin Zhang, Carmine Cella, Michael Eickenberg ; (60):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] GraKeL: A Graph Kernel Library in Python Giannis Siglidis, Giannis Nikolentzos, Stratis Limnios, Christos Giatsidis, Konstantinos Skianis, Michalis Vazirgiannis ; (54):1−5, 2020. [ abs ][ pdf ][ bib ] [ code ] pyts: A Python Package for Time Series Classification Johann Faouzi, Hicham Janati ; (46):1−6, 2020. [ abs ][ pdf ][ bib ] [ code ] Tensor Train Decomposition on TensorFlow (T3F) Alexander Novikov, Pavel Izmailov, Valentin Khrulkov, Michael Figurnov, Ivan Oseledets ; (30):1−7, 2020. [ abs ][ pdf ][ bib ] [ code ] ORCA: A Matlab/Octave Toolbox for Ordinal Regression Javier Sánchez-Monedero, Pedro A. Gutiérrez, María Pérez-Ortiz ; (125):1−5, 2019. [ abs ][ pdf ][ bib ] [ code ] PyOD: A Python Toolbox for Scalable Outlier Detection Yue Zhao, Zain Nasrullah, Zheng Li ; (96):1−7, 2019. [ abs ][ pdf ][ bib ] [ code ] iNNvestigate Neural Networks! Maximilian Alber, Sebastian Lapuschkin, Philipp Seegerer, Miriam Hägele, Kristof T. Schütt, Grégoire Montavon, Wojciech Samek, Klaus-Robert Müller, Sven Dähne, Pieter-Jan Kindermans ; (93):1−8, 2019. [ abs ][ pdf ][ bib ] [ code ] AffectiveTweets: a Weka Package for Analyzing Affect in Tweets Felipe Bravo-Marquez, Eibe Frank, Bernhard Pfahringer, Saif M. Mohammad ; (92):1−6, 2019. [ abs ][ pdf ][ bib ] [ code ] SMART: An Open Source Data Labeling Platform for Supervised Learning Rob Chew, Michael Wenger, Caroline Kery, Jason Nance, Keith Richards, Emily Hadley, Peter Baumgartner ; (82):1−5, 2019. [ abs ][ pdf ][ bib ] [ code ] Picasso: A Sparse Learning Library for High Dimensional Data Analysis in R and Python Jason Ge, Xingguo Li, Haoming Jiang, Han Liu, Tong Zhang, Mengdi Wang, Tuo Zhao ; (44):1−5, 2019. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Pyro: Deep Universal Probabilistic Programming Eli Bingham, Jonathan P. Chen, Martin Jankowiak, Fritz Obermeyer, Neeraj Pradhan, Theofanis Karaletsos, Rohit Singh, Paul Szerlip, Paul Horsfall, Noah D. Goodman ; (28):1−6, 2019. [ abs ][ pdf ][ bib ] [ code ] TensorLy: Tensor Learning in Python Jean Kossaifi, Yannis Panagakis, Anima Anandkumar, Maja Pantic ; (26):1−6, 2019. [ abs ][ pdf ][ bib ] [ code ] spark-crowd: A Spark Package for Learning from Crowdsourced Big Data Enrique G. Rodrigo, Juan A. Aledo, José A. Gámez ; (19):1−5, 2019. [ abs ][ pdf ][ bib ] [ code ] scikit-multilearn: A Python library for Multi-Label Classification Piotr Szymański, Tomasz Kajdanowicz ; (6):1−22, 2019. [ abs ][ pdf ][ bib ] [ code ] Seglearn: A Python Package for Learning Sequences and Time Series David M. Burns, Cari M. Whyne ; (83):1−7, 2018. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Scikit-Multiflow: A Multi-output Streaming Framework Jacob Montiel, Jesse Read, Albert Bifet, Talel Abdessalem ; (72):1−5, 2018. [ abs ][ pdf ][ bib ] [ code ] OpenEnsembles: A Python Resource for Ensemble Clustering Tom Ronan, Shawn Anastasio, Zhijie Qi, Pedro Henrique S. Vieira Tavares, Roman Sloutsky, Kristen M. Naegle ; (26):1−6, 2018. [ abs ][ pdf ][ bib ] [ webpage ] [ code ] ThunderSVM: A Fast SVM Library on GPUs and CPUs Zeyi Wen, Jiashuai Shi, Qinbin Li, Bingsheng He, Jian Chen ; (21):1−5, 2018. [ abs ][ pdf ][ bib ] [ webpage ] [ code ] ELFI: Engine for Likelihood-Free Inference Jarno Lintusaari, Henri Vuollekoski, Antti Kangasrääsiö, Kusti Skytén, Marko Järvenpää, Pekka Marttinen, Michael U. Gutmann, Aki Vehtari, Jukka Corander, Samuel Kaski ; (16):1−7, 2018. [ abs ][ pdf ][ bib ] [ webpage ] [ code ] SGDLibrary: A MATLAB library for stochastic optimization algorithms Hiroyuki Kasai ; (215):1−5, 2018. [ abs ][ pdf ][ bib ] [ code ] tick: a Python Library for Statistical Learning, with an emphasis on Hawkes Processes and Time-Dependent Models Emmanuel Bacry, Martin Bompaire, Philip Deegan, Stéphane Gaïffas, Søren V. Poulsen ; (214):1−5, 2018. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] KELP: a Kernel-based Learning Platform Simone Filice, Giuseppe Castellucci, Giovanni Da San Martino, Alessandro Moschitti, Danilo Croce, Roberto Basili ; (191):1−5, 2018. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Pycobra: A Python Toolbox for Ensemble Learning and Visualisation Benjamin Guedj, Bhargav Srinivasa Desikan ; (190):1−5, 2018. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] HyperTools: a Python Toolbox for Gaining Geometric Insights into High-Dimensional Data Andrew C. Heusser, Kirsten Ziman, Lucy L. W. Owen, Jeremy R. Manning ; (152):1−6, 2018. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] openXBOW -- Introducing the Passau Open-Source Crossmodal Bag-of-Words Toolkit Maximilian Schmitt, Björn Schuller ; (96):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] The MADP Toolbox: An Open Source Library for Planning and Learning in (Multi-)Agent Systems Frans A. Oliehoek, Matthijs T. J. Spaan, Bas Terwijn, Philipp Robbel, João V. Messias ; (89):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] GPflow: A Gaussian Process Library using TensorFlow Alexander G. de G. Matthews, Mark van der Wilk, Tom Nickson, Keisuke Fujii, Alexis Boukouvalas, Pablo León-Villagrá, Zoubin Ghahramani, James Hensman ; (40):1−6, 2017. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] GFA: Exploratory Analysis of Multiple Data Sources with Group Factor Analysis Eemeli Leppäaho, Muhammad Ammad-ud-din, Samuel Kaski ; (39):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ r-project.org ] POMDPs.jl: A Framework for Sequential Decision Making under Uncertainty Maxim Egorov, Zachary N. Sunberg, Edward Balaban, Tim A. Wheeler, Jayesh K. Gupta, Mykel J. Kochenderfer ; (26):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Auto-WEKA 2.0: Automatic model selection and hyperparameter optimization in WEKA Lars Kotthoff, Chris Thornton, Holger H. Hoos, Frank Hutter, Kevin Leyton-Brown ; (25):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] JSAT: Java Statistical Analysis Tool, a Library for Machine Learning Edward Raff ; (23):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Imbalanced-learn: A Python Toolbox to Tackle the Curse of Imbalanced Datasets in Machine Learning Guillaume Lemaître, Fernando Nogueira, Christos K. Aridas ; (17):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Refinery: An Open Source Topic Modeling Web Platform Daeil Kim, Benjamin F. Swanson, Michael C. Hughes, Erik B. Sudderth ; (12):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] SnapVX: A Network-Based Convex Optimization Solver David Hallac, Christopher Wong, Steven Diamond, Abhijit Sharang, Rok Sosič, Stephen Boyd, Jure Leskovec ; (4):1−5, 2017. [ abs ][ pdf ][ bib ] [ code ] [ stanford.edu ] fastFM: A Library for Factorization Machines Immanuel Bayer ; (184):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Megaman: Scalable Manifold Learning in Python James McQueen, Marina Meilă, Jacob VanderPlas, Zhongyue Zhang ; (148):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] JCLAL: A Java Framework for Active Learning Oscar Reyes, Eduardo Pérez, María del Carmen Rodríguez-Hernández, Habib M. Fardoun, Sebastián Ventura ; (95):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] LIBMF: A Library for Parallel Matrix Factorization in Shared-memory Systems Wei-Sheng Chin, Bo-Wen Yuan, Meng-Yuan Yang, Yong Zhuang, Yu-Chin Juan, Chih-Jen Lin ; (86):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] CVXPY: A Python-Embedded Modeling Language for Convex Optimization Steven Diamond, Stephen Boyd ; (83):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Stereo Matching by Training a Convolutional Neural Network to Compare Image Patches Jure Žbontar, Yann LeCun ; (65):1−32, 2016. [ abs ][ pdf ][ bib ] [ code ] MLlib: Machine Learning in Apache Spark Xiangrui Meng, Joseph Bradley, Burak Yavuz, Evan Sparks, Shivaram Venkataraman, Davies Liu, Jeremy Freeman, DB Tsai, Manish Amde, Sean Owen, Doris Xin, Reynold Xin, Michael J. Franklin, Reza Zadeh, Matei Zaharia, Ameet Talwalkar ; (34):1−7, 2016. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] MEKA: A Multi-label/Multi-target Extension to WEKA Jesse Read, Peter Reutemann, Bernhard Pfahringer, Geoff Holmes ; (21):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Harry: A Tool for Measuring String Similarity Konrad Rieck, Christian Wressnegger ; (9):1−5, 2016. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] partykit: A Modular Toolkit for Recursive Partytioning in R Torsten Hothorn, Achim Zeileis ; (118):3905−3909, 2015. [ abs ][ pdf ][ bib ] [ code ] CEKA: A Tool for Mining the Wisdom of Crowds Jing Zhang, Victor S. Sheng, Bryce A. Nicholson, Xindong Wu ; (88):2853−2858, 2015. [ abs ][ pdf ][ bib ] [ code ] pyGPs -- A Python Library for Gaussian Process Regression and Classification Marion Neumann, Shan Huang, Daniel E. Marthaler, Kristian Kersting ; (80):2611−2616, 2015. [ abs ][ pdf ][ bib ] [ code ] The Libra Toolkit for Probabilistic Models Daniel Lowd, Amirmohammad Rooshenas ; (75):2459−2463, 2015. [ abs ][ pdf ][ bib ] [ code ] RLPy: A Value-Function-Based Reinforcement Learning Framework for Education and Research Alborz Geramifard, Christoph Dann, Robert H. Klein, William Dabney, Jonathan P. How ; (46):1573−1578, 2015. [ abs ][ pdf ][ bib ] [ code ] Encog: Library of Interchangeable Machine Learning Models for Java and C# Jeff Heaton ; (36):1243−1247, 2015. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] The flare Package for High Dimensional Linear Regression and Precision Matrix Estimation in R Xingguo Li, Tuo Zhao, Xiaoming Yuan, Han Liu ; (18):553−557, 2015. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] Introducing CURRENNT: The Munich Open-Source CUDA RecurREnt Neural Network Toolkit Felix Weninger ; (17):547−551, 2015. [ abs ][ pdf ][ bib ] [ code ] A Classification Module for Genetic Programming Algorithms in JCLEC Alberto Cano, José María Luna, Amelia Zafra, Sebastián Ventura ; (15):491−494, 2015. [ abs ][ pdf ][ bib ] [ code ] SAMOA: Scalable Advanced Massive Online Analysis Gianmarco De Francisci Morales, Albert Bifet ; (5):149−153, 2015. [ abs ][ pdf ][ bib ] [ code ] BayesOpt: A Bayesian Optimization Library for Nonlinear Optimization, Experimental Design and Bandits Ruben Martinez-Cantin ; (115):3915−3919, 2014. [ abs ][ pdf ][ bib ] [ code ] SPMF: A Java Open-Source Pattern Mining Library Philippe Fournier-Viger, Antonio Gomariz, Ted Gueniche, Azadeh Soltani, Cheng-Wei Wu, Vincent S. Tseng ; (104):3569−3573, 2014. [ abs ][ pdf ][ bib ] [ code ] The Gesture Recognition Toolkit Nicholas Gillian, Joseph A. Paradiso ; (101):3483−3487, 2014. [ abs ][ pdf ][ bib ] [ code ] ooDACE Toolbox: A Flexible Object-Oriented Kriging Implementation Ivo Couckuyt, Tom Dhaene, Piet Demeester ; (91):3183−3186, 2014. [ abs ][ pdf ][ bib ] [ code ] pystruct - Learning Structured Prediction in Python Andreas C. Müller, Sven Behnke ; (59):2055−2060, 2014. [ abs ][ pdf ][ bib ] [ code ] Manopt, a Matlab Toolbox for Optimization on Manifolds Nicolas Boumal, Bamdev Mishra, P.-A. Absil, Rodolphe Sepulchre ; (42):1455−1459, 2014. [ abs ][ pdf ][ bib ] [ code ] Conditional Random Field with High-order Dependencies for Sequence Labeling and Segmentation Nguyen Viet Cuong, Nan Ye, Wee Sun Lee, Hai Leong Chieu ; (28):981−1009, 2014. [ abs ][ pdf ][ bib ] [ code ] LIBOL: A Library for Online Learning Algorithms Steven C.H. Hoi, Jialei Wang, Peilin Zhao ; (15):495−499, 2014. [ abs ][ pdf ][ bib ] [ code ] The FASTCLIME Package for Linear Programming and Large-Scale Precision Matrix Estimation in R Haotian Pang, Han Liu, Robert Vanderbei ; (14):489−493, 2014. [ abs ][ pdf ][ bib ] [ code ] Information Theoretical Estimators Toolbox Zoltán Szabó ; (9):283−287, 2014. [ abs ][ pdf ][ bib ] [ code ] EnsembleSVM: A Library for Ensemble Learning Using Support Vector Machines Marc Claesen, Frank De Smet, Johan A.K. Suykens, Bart De Moor ; (4):141−145, 2014. [ abs ][ pdf ][ bib ] [ code ] GURLS: A Least Squares Library for Supervised Learning Andrea Tacchetti, Pavan K. Mallapragada, Matteo Santoro, Lorenzo Rosasco ; (100):3201−3205, 2013. [ abs ][ pdf ][ bib ] [ code ] Divvy: Fast and Intuitive Exploratory Data Analysis Joshua M. Lewis, Virginia R. de Sa, Laurens van der Maaten ; (98):3159−3163, 2013. [ abs ][ pdf ][ bib ] [ code ] [ webpage ] QuantMiner for Mining Quantitative Association Rules Ansaf Salleb-Aouissi, Christel Vrain, Cyril Nortet, Xiangrong Kong, Vivek Rathod, Daniel Cassard ; (97):3153−3157, 2013. [ abs ][ pdf ][ bib ] [ code ] The CAM Software for Nonnegative Blind Source Separation in R-Java Niya Wang, Fan Meng, Li Chen, Subha Madhavan, Robert Clarke, Eric P. Hoffman, Jianhua Xuan, Yue Wang ; (88):2899−2903, 2013. [ abs ][ pdf ][ bib ] [ code ] BudgetedSVM: A Toolbox for Scalable SVM Approximations Nemanja Djuric, Liang Lan, Slobodan Vucetic, Zhuang Wang ; (84):3813−3817, 2013. [ abs ][ pdf ][ bib ] [ code ] Tapkee: An Efficient Dimension Reduction Library Sergey Lisitsyn, Christian Widmer, Fernando J. Iglesias Garcia ; (72):2355−2359, 2013. [ abs ][ pdf ][ bib ] [ code ] Orange: Data Mining Toolbox in Python Janez Demšar, Tomaž Curk, Aleš Erjavec, Črt Gorup, Tomaž Hočevar, Mitar Milutinovič, Martin Možina, Matija Polajnar, Marko Toplak, Anže Starič, Miha Štajdohar, Lan Umek, Lan Žagar, Jure Žbontar, Marinka Žitnik, Blaž Zupan ; (71):2349−2353, 2013. [ abs ][ pdf ][ bib ] [ code ] JKernelMachines: A Simple Framework for Kernel Machines David Picard, Nicolas Thome, Matthieu Cord ; (43):1417−1421, 2013. [ abs ][ pdf ][ bib ] [ code ] GPstuff: Bayesian Modeling with Gaussian Processes Jarno Vanhatalo, Jaakko Riihimäki, Jouni Hartikainen, Pasi Jylänki, Ville Tolvanen, Aki Vehtari ; (35):1175−1179, 2013. [ abs ][ pdf ][ bib ] [ code ] MLPACK: A Scalable C++ Machine Learning Library Ryan R. Curtin, James R. Cline, N. P. Slagle, William B. March, Parikshit Ram, Nishant A. Mehta, Alexander G. Gray ; (24):801−805, 2013. [ abs ][ pdf ][ bib ] [ code ] A C++ Template-Based Reinforcement Learning Library: Fitting the Code to the Mathematics Hervé Frezza-Buet, Matthieu Geist ; (18):625−628, 2013. [ abs ][ pdf ][ bib ] [ code ] SVDFeature: A Toolkit for Feature-based Collaborative Filtering Tianqi Chen, Weinan Zhang, Qiuxia Lu, Kailong Chen, Zhao Zheng, Yong Yu ; (116):3619−3622, 2012. [ abs ][ pdf ][ bib ] [ code ] DARWIN: A Framework for Machine Learning and Computer Vision Research and Development Stephen Gould ; (113):3533−3537, 2012. [ abs ][ pdf ][ bib ] [ code ] Sally: A Tool for Embedding Strings in Vector Spaces Konrad Rieck, Christian Wressnegger, Alexander Bikadorov ; (104):3247−3251, 2012. [ abs ][ pdf ][ bib ] [ code ] Oger: Modular Learning Architectures For Large-Scale Sequential Processing David Verstraeten, Benjamin Schrauwen, Sander Dieleman, Philemon Brakel, Pieter Buteneers, Dejan Pecevski ; (96):2995−2998, 2012. [ abs ][ pdf ][ bib ] [ code ] PREA: Personalized Recommendation Algorithms Toolkit Joonseok Lee, Mingxuan Sun, Guy Lebanon ; (87):2699−2703, 2012. [ abs ][ pdf ][ bib ] [ code ] A Topic Modeling Toolbox Using Belief Propagation Jia Zeng ; (73):2233−2236, 2012. [ abs ][ pdf ][ bib ] [ code ] DEAP: Evolutionary Algorithms Made Easy Félix-Antoine Fortin, François-Michel De Rainville, Marc-André Gardner, Marc Parizeau, Christian Gagné ; (70):2171−2175, 2012. [ abs ][ pdf ][ bib ] [ code ] Pattern for Python Tom De Smedt, Walter Daelemans ; (66):2063−2067, 2012. [ abs ][ pdf ][ bib ] [ code ] Jstacs: A Java Framework for Statistical Analysis and Classification of Biological Sequences Jan Grau, Jens Keilwagen, André Gohr, Berit Haldemann, Stefan Posch, Ivo Grosse ; (62):1967−1971, 2012. [ abs ][ pdf ][ bib ] [ code ] glm-ie: Generalised Linear Models Inference & Estimation Toolbox Hannes Nickisch ; (54):1699−1703, 2012. [ abs ][ pdf ][ bib ] [ code ] The huge Package for High-dimensional Undirected Graph Estimation in R Tuo Zhao, Han Liu, Kathryn Roeder, John Lafferty, Larry Wasserman ; (37):1059−1062, 2012. [ abs ][ pdf ][ bib ] [ code ] NIMFA : A Python Library for Nonnegative Matrix Factorization Marinka Žitnik, Blaž Zupan ; (30):849−853, 2012. [ abs ][ pdf ][ bib ] [ code ] GPLP: A Local and Parallel Computation Toolbox for Gaussian Process Regression Chiwoo Park, Jianhua Z. Huang, Yu Ding ; (26):775−779, 2012. [ abs ][ pdf ][ bib ] [ code ] ML-Flex: A Flexible Toolbox for Performing Classification Analyses In Parallel Stephen R. Piccolo, Lewis J. Frey ; (19):555−559, 2012. [ abs ][ pdf ][ bib ] [ code ] MULTIBOOST: A Multi-purpose Boosting Package Djalel Benbouzid, Róbert Busa-Fekete, Norman Casagrande, François-David Collin, Balázs Kégl ; (18):549−553, 2012. [ abs ][ pdf ][ bib ] [ code ] The Stationary Subspace Analysis Toolbox Jan Saputra Müller, Paul von Bünau, Frank C. Meinecke, Franz J. Király, Klaus-Robert Müller ; (93):3065−3069, 2011. [ abs ][ pdf ][ bib ] [ code ] Scikit-learn: Machine Learning in Python Fabian Pedregosa, Gaël Varoquaux, Alexandre Gramfort, Vincent Michel, Bertrand Thirion, Olivier Grisel, Mathieu Blondel, Peter Prettenhofer, Ron Weiss, Vincent Dubourg, Jake Vanderplas, Alexandre Passos, David Cournapeau, Matthieu Brucher, Matthieu Perrot, Édouard Duchesnay ; (85):2825−2830, 2011. [ abs ][ pdf ][ bib ] [ code ] LPmade: Link Prediction Made Easy Ryan N. Lichtenwalter, Nitesh V. Chawla ; (75):2489−2 | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/tencentglobal-cloud-virtual-machine-cvm/ | Cloud Virtual Machine (CVM) | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloud Virtual Machine (CVM) Server Virtualization Software by Tencent See who's skilled in this Add as skill Learn more Report this product About Tencent Cloud Virtual Machine offers stable, secure, resilient, and high-performance cloud computing service Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Fleet Manager SC//Fleet Manager Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Automation Tools Tencent Cloud Automation Tools Build Automation Tools Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/scalecomputing-hc3-virtualization-platform/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | SC//Fleet Manager | LinkedIn Skip to main content LinkedIn Scale Computing in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in SC//Fleet Manager Server Virtualization Software by Scale Computing See who's skilled in this Add as skill Learn more Report this product About We combined servers, storage, and virtualization into a single solution to make IT infrastructure easier for organizations of every size. Whether you have one IT administrator or hundreds, our award winning hyperconverged infrastructure eliminates complexity, lowers costs, and frees up management time. Using an appliance-based approach to virtualization, our Scale Computing Platform infrastructure solution is faster to deploy, easier to manage, and allows you to scale seamlessly as your organization grows. Even in an emergency with the failure of hardware components or entire appliances, Scale Computing infrastructure lets you keep critical apps – and your entire organization – up and running. This product is intended for System Administrator Information Technology Manager Chief Information Officer Director of Information Systems Network Specialist Network Administrator Media Products media viewer No more previous content Scale Computing HC3 Virtualization Platform HC3 brings together virtualization, servers, storage, and backup/disaster recovery into a single solution, eliminating the need for third-party components or licensing. The result is a highly efficient virtualization infrastructure that’s easy to use and effortless to maintain, producing substantial cost savings in both the short and long term. Scale Computing - Simplicity Engineered Scale Computing creates computing solutions that simplify IT operations by eliminating downtime and lowering IT costs. Take a look at how our innovative technology can make IT easier for you to manage. HC3 Success Story - L&B Realty Brenda Hartson gives a specific example of how the features and simplicity of Scale Computing's HC3 helped L&B avoid a disaster. No more next content Featured customers of SC//Fleet Manager Risas Dental and Braces Hospitals and Health Care 2,595 followers Holiday Inn Express Hospitality 96,389 followers Earl May Garden Centers Retail 569 followers MERIDA BIKES INTERNATIONAL Sporting Goods Manufacturing 17,166 followers Hood College Higher Education 17,711 followers Marc & Rose Hospitality 3,673 followers LiDestri Foods Food and Beverage Services 12,203 followers Soho House & Co Hospitality 390,378 followers Benchmark Computers and Electronics Manufacturing 105,382 followers Greenleaf Hospitality Group Hospitality 4,285 followers KIB Electronics Appliances, Electrical, and Electronics Manufacturing 269 followers Summit Steel and Manufacturing Machinery Manufacturing 873 followers Lindt & Sprüngli (Canada), Inc Retail 15,508 followers Blue Harbor Resort & Conference Center Hospitality 1,021 followers Genting Casinos UK Entertainment 10,429 followers Empire Airlines Aviation & Aerospace 9,650 followers Perry County Memorial Hospital Hospitals and Health Care 780 followers L&B Realty Advisors, LLP Investment Management 6,028 followers Friendly Hills Country Club Hospitality 189 followers Show more Show less Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Scale Computing products SC//HyperCore SC//HyperCore SC//Platform SC//Platform Server Virtualization Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.stanford.edu | Stanford University Skip to content Stanford University Information for: Students Faculty & Staff Families Visitors Alumni Search Menu Academics Research Health Care Campus Life Athletics Admission About News Events Search term Search Stanford: Web People Search Web Other ways to search: Map Profiles Stanford Explore Stanford Main Content A Mission Defined by Possibility At Stanford, our mission of discovery and learning is energized by a spirit of optimism and possibility that dates to our founding. Here you’ll find a place of intellectual expansiveness, wide-ranging perspectives, and freedom to explore new lines of thinking. Buzzing with ideas and innovation, approaching questions with openness and curiosity, pursuing excellence in all we do – this is Stanford. More about Stanford Campus News Stories about people, research, and innovation across the Farm In the Spotlight Why research matters Science & Engineering Rubin Observatory spots fastest-spinning asteroid of its size Health & Medicine AI-driven insurance decisions raise concerns about human oversight Science & Engineering New material changes color and texture like an octopus Business A better way to sell premade food could cut waste and boost sales In the Spotlight Stanford’s most intriguing innovations of 2025 More campus news Academics Preparing students to make meaningful contributions to society as engaged citizens and leaders in a complex world Undergraduate Education Rich learning experiences that provide a broad liberal arts foundation and deep subject-area expertise Undergraduate Education Graduate Education Unsurpassed opportunities to participate in the advancement of entire fields of knowledge Graduate Education Lifelong Learning Continuing adult education, executive and professional programs, and programs for K-12 students Lifelong Learning Seven schools in which to pursue your passions Medicine Law Humanities & Sciences Engineering Education Sustainability Business More about academics Profile of Renee Zhao “The truly impactful technologies are always based on the condition that you can freely explore.” Renee Zhao Assistant Professor of Mechanical Engineering Read more Research Driving discoveries vital to our world, our health, and our intellectual life 6,699 Inventions created by federally funded Stanford research 3,029 U.S. patents based on federally funded Stanford research 400+ Start-up companies founded based on federally funded research at Stanford 350,000+ Jobs created by companies that started with federally funded Stanford research $94 Billion Private investment in start-up companies that grew out of federally funded Stanford research $11+ trillion Market value of the top 30 companies founded by Stanford alumni More about research Profile of Khoi Young, ’25 “There’s a lot to question – that’s one of the most important things I’ll take with me from my Stanford experience.” Khoi Young, ’25 Design major and three-time NCAA gymnastics champion Read more Campus Life Building a vibrant community of creative and accomplished people from around the world Student Life A residential campus with diverse housing, exceptional dining, and over 600 student organizations Student Affairs Constructive Dialogue Uplifting academic freedom and free speech; curiosity and critical inquiry; open, inclusive exchange of ideas; and civic engagement and citizenship ePluribus Recreation & Wellness State-of-the-art facilities and fitness programs to encourage movement and play Recreation & Wellness More about campus life Profile of Helena Zhang, ’22 “Art is an outlet and a starting point for me, for what I have to say.” Helena Zhang, ’22 Graduated with a bachelor’s degree in human biology and a minor in art history Learn more The Arts Enriching the Bay Area and shaping culture with arts experiences for everyone Interdisciplinary Scholarship Innovative programs center the arts in research and education and expand the role of art across academic disciplines. Interdisciplinary Arts Museums and Public Art The Stanford campus is home to two world-class art museums and features more than 80 outdoor installations, accessible to the public 365 days a year. Cantor Arts Center Anderson Collection Live Performance Stanford Live presents a wide range of performances by artists from around the world. Stanford Live More about the arts Upcoming Events More events Health Care Advancing human health through innovative research, education, and care Stanford Medicine Leading a worldwide revolution in precision health through biomedical research, education, and clinical enterprises Stanford Medicine Stanford Health Care Leveraging expertise and advanced technology to deliver unparalleled care for each patient’s unique needs Stanford Health Care Stanford Children’s Health The only health care network in the Bay Area – and one of the few in the country – exclusively dedicated to pediatric and obstetric care Stanford Children’s Health More about health care Athletics Providing student-athletes the opportunity to achieve excellence both in competition and in the classroom Home of Champions Stanford’s 137 NCAA championships are the most for any university, a product of an unrivaled culture of excellence and continued support from the campus community National Championships Olympic Excellence The Cardinal has produced at least one medalist in every Olympics in which the U.S. has competed since 1912, totaling 335 medals from 196 medalists Medals Multidimensional Impact Stanford student-athletes have achieved local, national, and global impact through community involvement and advocacy Athlete Stories More about athletics Admission Offering extraordinary freedom to explore, to collaborate, and to challenge yourself Explore the possibilities of a Stanford education as you map out your college journey. We look for distinctive students who exhibit an abundance of energy and curiosity in their classes, activities, projects, research, and lives. Stanford meets the full financial need of every admitted undergrad who qualifies for assistance. More than two-thirds of undergrads receive some form of financial assistance. Generally, tuition is covered for families with incomes below $150,000. More about admission Facebook Twitter Instagram LinkedIn YouTube iTunes U Schools Business Education Engineering Humanities & Sciences Law Medicine Sustainability Academics Undergraduate Majors Graduate Programs Research Research Centers A - to Z Libraries Health Care Stanford Health Care Stanford Children's Health Online Learning Stanford Online About Stanford Facts History Accreditation Admission Undergraduate Graduate Financial Aid Resources Campus Map Community Engagement Directory Stanford Profiles Applying Visiting Giving Careers Faculty Positions Contact Stanford University Stanford Home Maps & Directions Search Stanford Emergency Info Terms of Use Privacy Copyright Trademarks Non-Discrimination Accessibility © Copyright Stanford University . Stanford , California 94305 . | 2026-01-13T09:29:15 |
https://group.mantle.xyz/zh | Mantle: Blockchain for Banking & On-Chain Finance 首页 Mantle 创新枢纽 资源 ZH 银行业的区块链 让加密货币融入你的日常生活。 了解更多 Mantle 的愿景 一个自由、高效、可及的金融世界 —— 由代币化技术驱动并向所有人开放。 主要业务板块 创新枢纽 MNT MNT 为 Mantle 的生态系统提供动力，是整个去中心化经济中治理、质押和推动创新的基石。 Mantle Network Mantle Network 是一款以太坊 Layer 2，它以模块化设计著称，率先采用 EigenLayer 和 EigenDA，为我们的一系列产品与应用奠定了坚实基础。 mETH Protocol mETH Protocol 是一款提供丰厚收益的 ETH 流动性质押和再质押协议。mETH 是 CEX、DApp 和货币市场中广受青睐的一种抵押资产。 Function Function 是一种去中心化比特币解决方案，它将 BTC 与 Web3 经济相融合，从而开辟出新的金融机会。 Mantle Index Four 一种机构级收益型产品，提供对一篮子顶级加密资产的多元化投资。 UR UR 是一款无国界的智能货币应用程序，可让您在一个平台上轻松实现消费与出金。 MantleX 通过利用人工智能（AI）开创去中心化系统的未来。 战略联盟 合作伙伴 国库总规模 $3,728,101,359 Mantle 国库是 Mantle 金融生态系统的核心，可确保稳定性并推动战略增长。 Treasury 76.23 % MNT $2,842,063,920 8.98 % ETH, mETH & cmETH $334,874,142 7.34 % BTC $273,985,488 6.99 % Stables $260,798,007 数据以美元为单位，更新时间为 2026 年 01 月 13 日, 09:06 UTC 由 Ecofund 催化的资本池 $200,000,000 Mantle EcoFund 由来自 Mirana Ventures 的专家提供支持，致力于支持变革性项目，并通过 PolyChain 和 Dragonfly 等 20 家领先风投机构获得顶级交易流，以此来推动生态系统增长。 了解更多 新闻室 亮点聚焦 官方博客 11 Jul, 2025 UR Early Beta Access: Now Live With Weekly $3,000 Lottery Prize Pool Ecosystem Mantle UR Users can now sign up for a UR account with limited and exclusive, by-invite-only, codes shared by selected participants of the UR Early program from July 11, 2025, 10AM UTC to Aug. 8, 10AM UTC. 了解详情 10 Jul, 2025 Mantle Becomes Strategic Investor of Digital Asset Management Firm ReserveOne Ecosystem Mantle Proud to announce our strategic investment in newly-formed digital asset management firm ReserveOne, an institutionally-governed digital asset reserve anchored in a diverse treasury strategy including Bitcoin, Ethereum and Solana. 了解详情 09 Jul, 2025 Letter to Token Holders Q3 2025 Mantle Network UR Q3 2025 onwards will be a transformative moment for Mantle and our role in the evolving global financial landscape. 了解详情 18 Jun, 2025 Mantle Launches UR (Early Contributors' Access Live) Ecosystem UR Beta testing access now live for UR — a borderless smart money app that makes it easy to spend and off-ramp, all in one place. UR is powered by Mantle Network. 了解详情 Mantle 治理 Treasury EcoFund Scouts 计划 获取 MNT 什么是 MNT 创新枢纽 Mantle Network mETH Protocol Function Mantle Index Four UR MantleX 资源 官方博客 活动 招贤纳士 品牌资源 © Mantle 2026 . All rights reserved. 隐私政策 条款 | 2026-01-13T09:29:15 |
https://opensource.guide/ko/starting-a-project/ | 오픈소스 프로젝트 시작하기 | Open Source Guides 소개 기여 العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides 오픈소스 프로젝트 시작하기 오픈소스의 세계에 대해 자세히 알아보고 여러분의 프로젝트를 시작할 준비를 해보세요. 목차 오픈소스는 “무엇”이고 “왜” 하는가? 내 오픈소스 프로젝트를 시작해야 할까요? 내 오픈소스 프로젝트 시작하기 프로젝트의 네이밍과 브랜딩 오픈소스 준비 체크리스트 오픈소스는 “무엇”이고 “왜” 하는가? 오픈소스를 시작하려고 하시나요? 축하합니다! 세상이 여러분의 기여를 높이 살 것입니다. 오픈소스란 무엇이며, 왜 사람들이 오픈소스를 사용하는지 알아봅시다. “오픈소스”란 무엇인가요? 오픈소스 프로젝트에서는 누구나 어떤 목적으로든 프로젝트를 보고, 사용하고, 수정하고, 배포할 수 있습니다. 이러한 권한은 오픈소스 라이선스 를 통해 적용됩니다. 오픈소스는 채택의 장벽을 낮춰 아이디어를 신속하게 퍼뜨릴 수 있기 때문에 강력합니다. 오픈소스가 어떻게 돌아가는지 이해하기 위해, 친구가 솥밥을 먹고 있는데 여러분이 체리 파이를 가지고 간다고 생각해 보세요. 모두가 파이를 먹을 수 있습니다. ( 사용 ) 파이가 히트를 쳤습니다! 그들은 여러분이 만들어 공개한 파이의 레시피를 찾아봅니다. ( 소스 뷰 ) 제과점 주방장인 한 친구 알렉스가 설탕을 줄이는 게 좋겠다고 조언합니다. ( 수정 ) 다른 친구인 리사는 다음 주 저녁 식사에 그 파이를 준비하고 싶다고 요청합니다. ( 배포 ) 비교해 보면, 독점 소스 과정은 레스토랑에 가서 체리 파이 한 조각을 주문할 것과 같습니다. 여러분은 파이를 먹기 위해 요금을 지불해야 하며 레스토랑은 아마 여러분에게 레시피를 알려주지 않을 것입니다. 만약 파이를 똑같이 베껴 여러분의 이름을 달고 판다면 레스토랑에서 여러분을 고소할 지도 모르죠. 왜 사람들은 자기 작업을 오픈소스로 공개하나요? One of the most rewarding experiences I get out of using and collaborating on open source comes from the relationships that I build with other developers facing many of the same problems I am. — @kentcdodds, “How getting into Open Source has been awesome for me” 사람이나 조직이 프로젝트 소스를 공개하려는 데에는 여러 가지 이유 가 있습니다. 몇 가지 예는 다음과 같습니다. 협업: 오픈소스 프로젝트는 전 세계 누구에게서든 수정을 받을 수 있습니다. 예를 들어 Exercism 은 350명이 넘는 기여자가 참여하는 프로그래밍 연습 플랫폼입니다. 채택과 재가공: 오픈소스 프로젝트는 거의 모든 용도로 누구나 사용할 수 있습니다. 심지어 사람들이 그 프로젝트를 기반으로 다른 프로젝트를 만들 수도 있습니다. 예컨대 WordPress 는 b2 라는 기존 프로젝트의 포크로 시작했습니다. 투명성: 누구나 오픈소스 프로젝트에서 오류나 불일치를 검사 할 수 있습니다. 투명성은 불가리아 나 미국 같은 정부, 은행 또는 의료 같은 규제 대상 산업, Let’s Encrypt 등의 보안 소프트웨어에는 투명성이 중요합니다. 오픈소스는 소프트웨어만을 위한 것이 아닙니다. 데이터 세트에서부터 서적에 이르기까지 모두 오픈소스로 만들 수 있습니다. GitHub Explore 에서 다른 오픈소스 아이디어를 확인해 보세요. 오픈소스는 “무료”를 의미하나요? 오픈소스의 가장 큰 매력 중 하나는 비용이 들지 않는다는 것입니다. 그러나 “무료”는 오픈소스의 전반적인 가치의 부산물에 불과합니다. 오픈소스 라이선스 는 누구나 거의 모든 목적으로 프로젝트를 사용, 수정, 공유할 수 있어야 하므로 프로젝트 자체는 무료입니다. 만약 프로젝트에서 비용을 청구한다면 누구나 합법적으로 복사본을 만들어 무료 버전을 사용할 수 있습니다. 결론적으로 대부분의 오픈소스 프로젝트는 무료이지만, “무료”는 오픈소스 정의의 일부가 아닙니다. 오픈소스의 공식적인 정의를 계속 준수하면서도 이중 라이선스 또는 제한된 기능을 통해 간접적으로 오픈소스 프로젝트 사용에 비용을 청구할 수 있는 방법이 있습니다. 내 오픈소스 프로젝트를 시작해야 할까요? 짧게 답하자면 그렇습니다. 결과가 어떻든 여러분 자신의 프로젝트를 시작하는 것이 오픈소스가 돌아가는 방식을 배우기 위한 훌륭한 방법이 되기 때문입니다. 이전에 프로젝트 소스를 공개해본 적이 없다면 누군가 뭐라고 하거나 소스를 보는 것 자체가 긴장될지도 모릅니다. 이게 여러분의 이야기처럼 들리나요? 여러분은 혼자가 아닙니다! 오픈소스 작업은 글을 쓰거나 그림을 그리는 활동과 같습니다. 여러분의 작업을 세상과 공유하기가 두려울 수도 있지만, 발전하는 방법은 연습 뿐입니다. 설령 봐주는 사람이 없더라도요. 아직 확신이 서지 않는다면 여러분의 목표가 무엇인지 잠시 생각해 보세요. 목표 설정하기 목표는 여러분이 무엇을 해야 하는지, 무엇을 하지 말아야 하는지, 어디서 도움을 받아야 하는지 찾는 데 도움이 될 수 있습니다. 먼저 왜 프로젝트를 오픈소스화하려고 하는지 자문해 보세요. 이 질문에 대해 정해진 정답은 없습니다. 한 프로젝트에 대해 여러 가지 목표를 가질 수도 있고, 각기 다른 목표를 가진 여러 프로젝트를 진행할 수도 있습니다. 여러분의 유일한 목표가 여러분의 성과를 보여주는 것이라면 기여를 원하지 않을 수도 있고 README 파일에 그렇게 적어둘 수도 있습니다. 반대로 기여자를 원한다면 명확한 문서화에 시간을 투자하고 방문자들을 환영해야 합니다. At some point I created a custom UIAlertView that I was using…and I decided to make it open source. So I modified it to be more dynamic and uploaded it to GitHub. I also wrote my first documentation explaining to other developers how to use it on their projects. Probably nobody ever used it because it was a simple project but I was feeling good about my contribution. — @mavris, “Self-taught Software Developers: Why Open Source is important to us” 프로젝트가 성장함에 따라 커뮤니티에는 단순한 코드 이상의 것이 필요할 수 있습니다. 이슈에 대응하고, 코드를 검토하고, 프로젝트를 홍보하는 것은 오픈소스 프로젝트에서 중요한 작업입니다. 코딩이 아닌 작업에 소요되는 시간은 프로젝트의 크기와 범위에 따라 다르지만, 여러분이 직접 관리자로서 문제를 해결하거나 도움을 줄 사람을 찾아야 합니다. 만약 프로젝트를 오픈소스화하는 회사의 일원이라면 프로젝트의 성공을 위해 필요한 내부 자원이 있는지 확인하세요. 공개 후 누가 프로젝트 관리 책임이 있는지, 어떻게 작업들을 커뮤니티와 공유할 것인지 파악하고 정해야 합니다. 홍보, 운영 및 프로젝트 유지를 위해 전담 예산이나 인력이 필요한 경우 이런 대화를 조기에 시작하세요. As you begin to open source the project, it’s important to make sure that your management processes take into consideration the contributions and abilities of the community around your project. Don’t be afraid to involve contributors who are not employed in your business in key aspects of the project — especially if they are frequent contributors. — @captainsafia, “So you wanna open source a project, eh?” 다른 프로젝트에 기여하기 사람들과 협업하는 방법을 배우거나 오픈소스가 어떻게 돌아가는지 이해하는 것이 목표라면 기존 프로젝트에 기여하는 것을 고려해 보세요. 여러분이 이미 애용하고 있는 프로젝트에서부터 시작하세요. 오타를 수정하거나 문서를 업데이트하는 것처럼 간단한 것으로도 기여할 수 있습니다. 기여를 시작하는 법을 잘 모르겠다면 오픈소스에 기여하는 방법 가이드 를 확인해 보세요. 내 오픈소스 프로젝트 시작하기 프로젝트를 오픈소스화할 정해진 타이밍은 없습니다. 아이디어, 진행중인 작업 혹은 수년이 지난 비공개 소스도 오픈소스화할 수 있습니다. 일반적으로 다른 사람이 여러분의 작업을 보고 피드백을 제공해도 불편할 만한 점이 없을 때 프로젝트를 오픈소스화하면 됩니다. 프로젝트를 오픈소스화하기로 결정한 시점에 상관없이 모든 프로젝트에는 다음과 같은 문서가 포함되어 있어야 합니다. 오픈소스 라이선스 README 기여 가이드라인 행동 강령 관리자는 이러한 구성 요소로 기대치를 전달하고, 기여를 관리하고, (여러분을 포함한) 모두의 법적 권리를 보호할 수 있습니다. 위 문서들은 여러분이 긍정적인 경험을 하게 될 가능성을 크게 증가시킵니다. 프로젝트가 GitHub에 있는 경우, 권장 파일 이름을 적용해 이러한 파일들을 최상위 폴더에 저장해 두면 GitHub에서 해당 파일을 인식해 자동으로 사람들에게 보여줍니다. 라이선스 선택하기 오픈소스 라이선스는 사람들이 여러분의 프로젝트에 영향을 주지 않고 사용, 복사, 수정 및 기여할 수 있도록 보장합니다. 또한 복잡하게 얽혀 있는 법적 상황으로부터 당신을 보호합니다. 오픈소스 프로젝트를 시작한다면 반드시 라이선스를 포함해야 합니다. 법률에 관한 일은 즐겁지 않습니다. 좋은 소식은 기존 라이선스를 복사해 저장소에 붙여넣을 수 있다는 것입니다. 여러분의 노력을 보호하는 데 1분이면 충분할 것입니다. MIT , Apache 2.0 , 그리고 GPLv3 가 가장 인기있는 오픈소스 라이선스지만 선택할 수있는 다른 옵션 도 있습니다. GitHub에서 새 프로젝트를 만들면 라이선스를 선택할 수 있는 옵션이 제공됩니다. 오픈소스 라이선스를 포함하면 GitHub 프로젝트를 오픈소스로 만들 수 있습니다. 오픈소스 프로젝트 관리의 법적 측면에 대해 다른 질문이나 우려되는 점이 있다면 이 내용을 참조하세요 . README 파일 작성하기 README는 프로젝트 사용 방법을 설명하는 것 이상의 일을 수행합니다. 프로젝트가 중요한 이유와 사용자가 프로젝트를 이용해 할 수 있는 작업에 대해서도 설명합니다. README에서 다음 질문에 답해 보세요. 이 프로젝트는 무슨 일을 하나요? 이 프로젝트가 유용한 이유는 무엇인가요? 어떻게 시작해야 하나요? 필요하다면 어디에서 더 많은 도움을 받을 수 있을까요? README를 사용하여 여러분이 기여를 받아들이는 방식, 프로젝트의 목표, 라이선스 및 속성에 대한 정보와 같은 다른 질문에 답할 수 있습니다. 기여를 받고 싶지 않거나, 프로젝트가 아직 준비되지 않았다면 그렇게 적어 두세요. Better documentation means more users, less support requests, and more contributors. (…) Remember that your readers aren’t you. There are people who might come to a project who have completely different experiences. — @tracymakes, “Writing So Your Words Are Read (video)” 때때로 사람들은 프로젝트가 완성되지 않았거나 기여를 원치 않기 때문에 README를 작성하지 않는 경우가 있습니다. 그것도 README를 작성할 좋은 이유입니다. @18F의 “Making READMEs Readable” 에서 더 많은 영감을 얻거나 @PurpleBooth의 README template 을 이용해 전체 README를 작성해 보세요. README 파일을 최상위 폴더에 포함시키면, GitHub가 자동으로 저장소 홈페이지에 내용을 표시합니다. 기여 가이드라인 작성하기 CONTRIBUTING 파일은 잠재 기여자들에게 프로젝트에 기여하는 방법을 알려줍니다. 예를 들어 다음 정보를 포함할 수 있습니다. 버그 보고서를 제출하는 방법 ( 이슈와 PR 템플릿 을 사용해 보세요) 새로운 기능을 제안하는 방법 환경 설정 및 테스트 실행 방법 기술적 세부 사항과 더불어 여러분이 어떤 기여를 기대하는지 전달할 수도 있습니다. 원하는 기여 유형 프로젝트 로드맵 또는 비전 기여자가 여러분과 연락하는 데 사용할 (혹은 사용하지 말아야 할) 방법 따뜻하고 친근한 어조를 사용하고, 문서나 웹사이트 작성 등 기여에 대한 구체적인 제안을 제공하는 것은 새로운 사람들이 기꺼이 기여를 만들게 하는 데 도움이 될 수 있습니다. 예를 들어 Active Admin 은 다음과 같이 기여 가이드 를 시작합니다. 먼저, Active Admin에 기여해 주셔서 감사합니다. 여러분의 기여가 Active Admin을 이렇게 훌륭한 툴로 만듭니다. 프로젝트의 초기 단계에서는 CONTRIBUTING 파일이 단순할 수 있습니다. 항상 버그 또는 파일 이슈를 보고하는 방법과 기여에 필요한 테스트 등 기술적 요구 사항을 설명해야 합니다. 시간이 지나면 자주 묻는 질문을 CONTRIBUTING 파일에 추가할 수 있습니다. 이 정보를 적어두면 같은 질문을 반복해서 하는 사람들이 줄어들 것입니다. CONTRIBUTING 파일을 작성하는 데 도움이 필요하면 @nayafia의 contributing guide template 또는 @mozilla의 “How to Build a CONTRIBUTING.md” 을 참조하세요. README에 CONTRIBUTING 파일을 링크하면 더 많은 사람들이 읽게 할 수 있습니다. CONTRIBUTING 파일을 프로젝트의 저장소에 두면 기여자가 이슈를 생성하거나 PR를 열 때 GitHub가 자동으로 링크를 생성합니다. 행동 강령 세우기 We’ve all had experiences where we faced what was probably abuse either as a maintainer trying to explain why something had to be a certain way, or as a user…asking a simple question. (…) A code of conduct becomes an easily referenced and linkable document that indicates that your team takes constructive discourse very seriously. — @mlynch, “Making Open Source a Happier Place” 마지막으로 행동 강령은 프로젝트 참가자의 행동에 대한 기본 규칙을 정하는 데 도움이 됩니다. 이는 커뮤니티나 회사의 오픈소스 프로젝트를 시작할 때 특히 유용합니다. 행동 강령은 건강하고 건설적인 커뮤니티 행동을 촉진할 수 있게 해 주는데, 이는 관리자 여러분의 스트레스를 줄여줄 것입니다. 자세한 내용은 행동강령 가이드 를 참조하세요. 행동 강령은 참여자가 어떻게 행동하기를 기대하는지 전달하는 것 외에, 이러한 기대가 누구에게 적용되는지, 언제 적용되는지, 위반할 경우 어떻게 하는지 등을 다루기도 합니다. 오픈소스 라이선스와 마찬가지로 행동 강령에 대한 새로운 표준도 있으므로 직접 작성할 필요는 없습니다. Contributor Covenant 는 Kubernetes, Rails 및 Swift를 포함한 40,000개 이상의 오픈소스 프로젝트 에서 사용되는 행동 강령입니다. 어느 것을 사용하든, 필요에 따라 행동 강령을 시행할 준비가 되어 있어야 합니다. 행동 강령을 저장소의 CODE_OF_CONDUCT 파일에 직접 붙여넣으세요. 파일을 쉽게 찾을 수 있게 프로젝트 최상위 폴더에 저장하고 README에 링크를 첨부하세요. 프로젝트의 네이밍과 브랜딩 브랜딩은 화려한 로고나 매력적인 프로젝트 이름 그 이상입니다. 브랜딩은 여러분이 프로젝트를 어떻게 생각하는지, 누구에게 여러분의 메시지를 전달하고자 하는지에 대한 것입니다. 올바른 이름 짓기 기억하기 쉬운 이름을 짓고 프로젝트가 어떤 일을 하는지 알 수 있게 하는 것이 이상적입니다. 아래의 예시를 보세요. Sentry 는 충돌 보고를 위해 앱을 모니터링합니다. Thin 은 빠르고 간단한 Ruby 웹 서버입니다. 기존 프로젝트를 기반으로 하는 경우 그 이름을 접두사로 사용하면 프로젝트가 수행하는 작업을 쉽게 파악할 수 있습니다. 예컨대 node-fetch 는 window.fetch 를 Node.js에 가져옵니다. 무엇보다 명확성을 고려하세요. 농담은 재미있지만, 어떤 농담은 다른 문화나 다른 경험을 가진 사람들에게는 이해되지 않을 수도 있음을 기억하세요. 잠재적인 사용자 중 일부는 회사 직원일 수 있습니다. 그들이 직장에서 여러분의 프로젝트를 설명하기 어렵게 만들고 싶지는 않을 것입니다! 이름 중복 피하기 비슷한 이름의 오픈소스 프로젝트가 있는지 확인하세요 . 특히 동일한 언어 또는 같은 생태계를 공유하는 경우, 이름이 기존의 인기 있는 프로젝트와 겹치면 사람들이 헷갈려 할 것입니다. 웹 사이트, Twitter 핸들 또는 다른 속성이 프로젝트를 표현하기를 원한다면 원하는 이름을 사용할 수 있는지 확인하세요. 이상적으로는, 그 이름을 아직 사용할 생각이 없더라도 마음의 평화를 위해 이름을 차지해 두는 것이 좋습니다 . 프로젝트 이름이 상표를 침해하지 않는지 확인하세요. 회사 측에서 프로젝트를 중단하거나 법적 조치를 취할 것을 요구할 수 있습니다. 리스크를 부담할 가치는 없습니다. WIPO Global Brand Database 에서 상표명이 있는지 확인할 수 있습니다. 여러분이 회사에서 일을 하고 있다면 법률팀이 도와줄 수 있을 것입니다 . 마지막으로, 프로젝트 이름을 구글에 검색해 보세요. 사람들이 프로젝트를 쉽게 찾을 수 있을까요? 검색 결과에 여러분이 원치 않는 것이 나타나지는 않나요? 당신의 글(과 코드)도 브랜드에 영향을 미칩니다! 프로젝트가 진행되는 동안 여러분은 README, 튜토리얼, 커뮤니티 문서, 이슈에 대한 답변, 뉴스레터 및 메일링 리스트까지 많은 글을 쓸 것입니다. 그것이 공식적인 문서든 평범한 이메일이든 여러분의 글 스타일은 프로젝트 브랜드의 일부입니다. 어떻게 청중에게 다가가야 좋을지, 여러분이 전달하고자 하는 어조는 무엇인지 고려하세요. I tried to be involved with every thread on the mailing list, and showing exemplary behaviour, being nice to people, taking their issues seriously and trying to be helpful overall. After a while, people stuck around not to only ask questions, but to help with the answering as well, and to my complete delight, they mimicked my style. — @janl on CouchDB , “Sustainable Open Source” 따뜻하고 포괄적인 언어(한 사람을 언급 할 때도 “그들”이라고 하듯)를 사용하면 이 프로젝트가 새로운 기여자에게 환영받는 느낌을 줄 수 있습니다. 많은 독자가 영어를 모국어로 사용하지 않을 수 있으므로 간단한 언어 사용에 충실하세요. 작문 스타일 뿐 아니라 코딩 스타일도 프로젝트 브랜드의 일부가 될 수 있습니다. Angular 와 jQuery 는 엄격한 코딩 스타일과 가이드라인을 가진 프로젝트의 두 가지 예입니다. 프로젝트를 시작할 때 스타일 가이드를 작성할 필요는 없으며, 여러분은 오히려 프로젝트에 여러 코딩 스타일이 혼재하는 것을 좋아할 수도 있습니다. 하지만 글과 코딩 스타일이 서로 다른 유형의 사람들을 끌어모으거나 단념시킬 수도 있다는 점을 예상해야 합니다. 프로젝트의 가장 초기 단계는 여러분이 원하는 선례를 만들 기회입니다. 오픈소스 준비 체크리스트 프로젝트를 오픈소스화할 준비가 되셨습니까? 다음은 도움이 되는 체크리스트입니다. 모든 칸에 체크하셨나요? 이제 출발할 준비가 되었습니다! “공개”를 클릭 하고 등을 토닥이세요. 문서 프로젝트에 오픈소스 라이선스가 적힌 LICENSE 파일이 있다. 프로젝트가 README, CONTRIBUTING, CODE_OF_CONDUCT 등 기본적인 문서를 갖추고 있다. 이름은 기억하기 쉽고, 프로젝트가 하는 일에 대한 아이디어를 제공하며, 기존 프로젝트와 충돌하거나 상표를 침해하지 않는다. 이슈 대기열이 최신 상태이며, 이슈는 깔끔하게 분류되고 라벨이 지정되어 있다. 코드 프로젝트가 일관된 코드 규칙을 사용하고 명확한 함수/메소드/변수 이름을 사용한다. 코드에 의도와 특수 상황을 담은 명확한 주석이 달려 있다. 커밋 내역, 이슈, PR에 암호나 비공개 정보 등의 민감한 자료가 없다. 사람 여러분이 개인이라면 아래를 확인하세요. (회사 직원인 경우) 법무 부서와 상담하고 회사의 IP 및 오픈소스 정책을 이해했다. 여러분이 회사나 조직이라면 아래를 확인하세요. 법무 부서와 상담했다. 프로젝트 발표 및 홍보를 위한 마케팅 계획을 마련했다. 이슈에 답변하고 PR을 리뷰 및 병합하는 등 커뮤니티 상호 작용을 관리할 담당자가 있다. 최소 두 명 이상이 프로젝트 관리 권한을 갖는다. 해냈어요! 첫번째 프로젝트를 오픈소스화한 것을 축하합니다. 결과가 어떻든 공개적으로 작업하는 것은 커뮤니티에게 좋은 선물입니다. 모든 커밋, 댓글, PR을 통해 여러분은 여러분 스스로와 다른 사람들이 배우고 성장할 기회를 창출하고 있습니다. 모든 가이드로 돌아가기 관련 가이드 프로젝트에 기여할 사람 찾기 당신의 오픈소스 프로젝트가 행복한 사용자들의 손길 아래 성장할 수 있게 만드세요. 마음을 끄는 커뮤니티 만들기 사람들이 프로젝트를 사용하고, 기여하고, 전파하도록 격려하는 커뮤니티를 만드세요. Scroll to Top 기여 제안을 하고 싶으신가요? 이 사이트는 오픈소스입니다. 개선할 수 있도록 도와주세요. 기여하기 구독 GitHub의 최신 오픈소스 팁과 리소스 관련 소식을 누구보다 먼저 들어보세요. 이메일 주소 fine print 와 친구 의 을 담은 | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/categories/server-virtualization-software?trk=products_details_guest_product_category | Best Server Virtualization Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Information Technology Manager (7) Director of Information Technology (5) System Administrator (5) Virtualization Engineer (2) Information Technology Project Manager (2) See all products Find top products in Server Virtualization Software category Software used to emulate computer systems by partitioning resources from physical hosts. - Use hypervisors to run multiple virtual machines from a single physical server - Run platform-independent environments with optimized resource distribution - Consolidate server usage with shared memory and processing - Control independent instances of guest operating systems 40 results Cloudflare Workers Server Virtualization Software by Cloudflare Build your next application with Cloudflare Workers View product Cloud Virtual Machine (CVM) Server Virtualization Software by Tencent Tencent Cloud Virtual Machine offers stable, secure, resilient, and high-performance cloud computing service View product Proxmox Virtual Environment Server Virtualization Software by Proxmox Server Solutions Proxmox Virtual Environment (Proxmox VE) is is the leading open-source platform for all-inclusive enterprise virtualization. With the central web interface, you can easily run VMs and containers, manage software-defined storage and networking functionality, high-availability clustering, and multiple integrated out-of-the-box tools like backup/restore, live migration, replication, and the firewall. Enterprises use the powerful all-in-one solution to meet the core requirements of today’s modern data centers. View product SC//Fleet Manager Server Virtualization Software by Scale Computing We combined servers, storage, and virtualization into a single solution to make IT infrastructure easier for organizations of every size. Whether you have one IT administrator or hundreds, our award winning hyperconverged infrastructure eliminates complexity, lowers costs, and frees up management time. Using an appliance-based approach to virtualization, our Scale Computing Platform infrastructure solution is faster to deploy, easier to manage, and allows you to scale seamlessly as your organization grows. Even in an emergency with the failure of hardware components or entire appliances, Scale Computing infrastructure lets you keep critical apps – and your entire organization – up and running. View product SC//Platform Server Virtualization Software by Scale Computing With edge computing, you can run applications and process data outside centralized data centers, at the edge of your network closest to where that data is created and utilized. Centrally monitor and manage hundreds or thousands of distributed edge infrastructure deployments with few or no on-site IT personnel. The award winning Scale Computing brings on-premises edge computing with high availability and disaster recovery to remote locations at an affordable entry level cost. All edge appliances can be deployed quickly, managed locally or remotely, and can self-heal almost instantly. Enjoy affordable edge computing infrastructure that is reliable, easy to deploy, and easy to use. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights BTS Sybelle Virtualization Platform Server Virtualization Software by BTS Group BTS Sybelle Virtualization Platform is a system virtualization platform that optimizes the management of virtualization infrastructure for organizations of all sizes. With high availability, scalability, advanced networking, and flexible storage capabilities at its core, it delivers reliable, enterprise-grade performance tailored to modern IT environments. View product Oracle Virtualization Server Virtualization Software by Oracle Linux Backed by affordable enterprise support for hybrid environments, Oracle Virtualization reduces operation and support costs while increasing IT efficiency and agility—on premises and in the cloud. View product StarWind SAN & NAS Server Virtualization Software by StarWind Inc. StarWind SAN & NAS is a ready-to-go Linux-based virtual machine (VM) that allows you to repurpose existing hypervisor servers into shared storage. Leveraging the power of ZFS, Linux, and StarWind SDS, the solution can transform your hypervisor servers into HCL-certified high-performance storage appliance, shared storage, or backup target. Just deploy it on top of your hypervisor and you’re good to go. View product StarWind NVMe-oF Initiator Server Virtualization Software by StarWind Inc. StarWind NVMe-oF Initiator is the only software solution on the market that brings NVMe-oF connectivity over TCP and RoCE v2 networks to performance-demanding Windows applications. It’s certified with Windows and makes NVMe-oF available for SQL and M&E workloads without the need for fibre channel, rNICs on every host, or wait for a Windows-native solution to get released and mature. View product ZStack ZSphere Server Virtualization Server Virtualization Software by ZStack International ZStack ZSphere offers a VMware vSphere‑like user experience, ready to use without additional training. It scales from 1 to 1,000 servers per cluster and includes a three‑month free trial with full features and unlimited server deployment. Key Features and Capabilities: Compatibility & Reuse: Works with multi‑architecture CPUs and multi‑brand servers, protecting existing investments. SAN Storage Support: Integrates with proprietary storage for specific SLA scenarios. AI‑Ready: Supports GPU passthrough and vGPU for AI and high‑compute workloads. Cross‑Version Hot Upgrade: Maintains business continuity during system upgrades. High Performance: SR‑IOV delivers near bare‑metal networking for demanding I/O, with VM storage performance up to millions of IOPS. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:15 |
https://x.com/funnymoneyHQ | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T09:29:15 |
https://opensource.guide/starting-a-project/ | Starting an Open Source Project | Open Source Guides About Contribute العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Starting an Open Source Project Learn more about the world of open source and get ready to launch your own project. Table of Contents The “what” and “why” of open source Should I launch my own open source project? Launching your own open source project Naming and branding your project Your pre-launch checklist The “what” and “why” of open source So you’re thinking about getting started with open source? Congratulations! The world appreciates your contribution. Let’s talk about what open source is and why people do it. What does “open source” mean? When a project is open source, that means anybody is free to use, study, modify, and distribute your project for any purpose. These permissions are enforced through an open source license . Open source is powerful because it lowers the barriers to adoption and collaboration, allowing people to spread and improve projects quickly. Also because it gives users a potential to control their own computing, relative to closed source. For example, a business using open source software has the option to hire someone to make custom improvements to the software, rather than relying exclusively on a closed source vendor’s product decisions. Free software refers to the same set of projects as open source . Sometimes you’ll also see these terms combined as “free and open source software” (FOSS) or “free, libre, and open source software” (FLOSS). Free and libre refer to freedom, not price . Why do people open source their work? One of the most rewarding experiences I get out of using and collaborating on open source comes from the relationships that I build with other developers facing many of the same problems I am. — @kentcdodds, “How getting into Open Source has been awesome for me” There are many reasons why a person or organization would want to open source a project. Some examples include: Collaboration: Open source projects can accept changes from anybody in the world. Exercism , for example, is a programming exercise platform with over 350 contributors. Adoption and remixing: Open source projects can be used by anyone for nearly any purpose. People can even use it to build other things. WordPress , for example, started as a fork of an existing project called b2 . Transparency: Anyone can inspect an open source project for errors or inconsistencies. Transparency matters to governments like Bulgaria or the United States , regulated industries like banking or healthcare, and security software like Let’s Encrypt . Open source isn’t just for software, either. You can open source everything from data sets to books. Check out GitHub Explore for ideas on what else you can open source. Does open source mean “free of charge”? One of open source’s biggest draws is that it does not cost money. “Free of charge”, however, is a byproduct of open source’s overall value. Because an open source license requires that anyone can use, modify, and share your project for nearly any purpose, projects themselves tend to be free of charge. If the project cost money to use, anyone could legally make a copy and use the free version instead. As a result, most open source projects are free, but “free of charge” is not part of the open source definition. There are ways to charge for open source projects indirectly through dual licensing or limited features, while still complying with the official definition of open source. Should I launch my own open source project? The short answer is yes, because no matter the outcome, launching your own project is a great way to learn how open source works. If you’ve never open sourced a project before, you might be nervous about what people will say, or whether anyone will notice at all. If this sounds like you, you’re not alone! Open source work is like any other creative activity, whether it’s writing or painting. It can feel scary to share your work with the world, but the only way to get better is to practice - even if you don’t have an audience. If you’re not yet convinced, take a moment to think about what your goals might be. Setting your goals Goals can help you figure out what to work on, what to say no to, and where you need help from others. Start by asking yourself, why am I open sourcing this project? There is no one right answer to this question. You may have multiple goals for a single project, or different projects with different goals. If your only goal is to show off your work, you may not even want contributions, and even say so in your README. On the other hand, if you do want contributors, you’ll invest time into clear documentation and making newcomers feel welcome. At some point I created a custom UIAlertView that I was using…and I decided to make it open source. So I modified it to be more dynamic and uploaded it to GitHub. I also wrote my first documentation explaining to other developers how to use it on their projects. Probably nobody ever used it because it was a simple project but I was feeling good about my contribution. — @mavris, “Self-taught Software Developers: Why Open Source is important to us” As your project grows, your community may need more than just code from you. Responding to issues, reviewing code, and evangelizing your project are all important tasks in an open source project. While the amount of time you spend on non-coding tasks will depend on the size and scope of your project, you should be prepared as a maintainer to address them yourself or find someone to help you. If you’re part of a company open sourcing a project, make sure your project has the internal resources it needs to thrive. You’ll want to identify who’s responsible for maintaining the project after launch, and how you’ll share those tasks with your community. If you need a dedicated budget or staffing for promotion, operations and maintaining the project, start those conversations early. As you begin to open source the project, it’s important to make sure that your management processes take into consideration the contributions and abilities of the community around your project. Don’t be afraid to involve contributors who are not employed in your business in key aspects of the project — especially if they are frequent contributors. — @captainsafia, “So you wanna open source a project, eh?” Contributing to other projects If your goal is to learn how to collaborate with others or understand how open source works, consider contributing to an existing project. Start with a project that you already use and love. Contributing to a project can be as simple as fixing typos or updating documentation. If you’re not sure how to get started as a contributor, check out our How to Contribute to Open Source guide . Launching your own open source project There is no perfect time to open source your work. You can open source an idea, a work in progress, or after years of being closed source. Generally speaking, you should open source your project when you feel comfortable having others view, and give feedback on, your work. No matter which stage you decide to open source your project, every project should include the following documentation: Open source license README Contributing guidelines Code of conduct As a maintainer, these components will help you communicate expectations, manage contributions, and protect everyone’s legal rights (including your own). They significantly increase your chances of having a positive experience. If your project is on GitHub, putting these files in your root directory with the recommended filenames will help GitHub recognize and automatically surface them to your readers. Choosing a license An open source license guarantees that others can use, copy, modify, and contribute back to your project without repercussions. It also protects you from sticky legal situations. You must include a license when you launch an open source project. Legal work is no fun. The good news is that you can copy and paste an existing license into your repository. It will only take a minute to protect your hard work. MIT , Apache 2.0 , and GPLv3 are the most popular open source licenses, but there are other options to choose from. When you create a new project on GitHub, you are given the option to select a license. Including an open source license will make your GitHub project open source. If you have other questions or concerns around the legal aspects of managing an open source project, we’ve got you covered . Writing a README READMEs do more than explain how to use your project. They also explain why your project matters, and what your users can do with it. In your README, try to answer the following questions: What does this project do? Why is this project useful? How do I get started? Where can I get more help, if I need it? You can use your README to answer other questions, like how you handle contributions, what the goals of the project are, and information about licenses and attribution. If you don’t want to accept contributions, or your project is not yet ready for production, write this information down. Better documentation means more users, less support requests, and more contributors. (…) Remember that your readers aren’t you. There are people who might come to a project who have completely different experiences. — @tracymakes, “Writing So Your Words Are Read (video)” Sometimes, people avoid writing a README because they feel like the project is unfinished, or they don’t want contributions. These are all very good reasons to write one. For more inspiration, try using @dguo’s “Make a README” guide or @PurpleBooth’s README template to write a complete README. When you include a README file in the root directory, GitHub will automatically display it on the repository homepage. Writing your contributing guidelines A CONTRIBUTING file tells your audience how to participate in your project. For example, you might include information on: How to file a bug report (try using issue and pull request templates ) How to suggest a new feature How to set up your environment and run tests In addition to technical details, a CONTRIBUTING file is an opportunity to communicate your expectations for contributions, such as: The types of contributions you’re looking for Your roadmap or vision for the project How contributors should (or should not) get in touch with you Using a warm, friendly tone and offering specific suggestions for contributions (such as writing documentation, or making a website) can go a long way in making newcomers feel welcomed and excited to participate. For example, Active Admin starts its contributing guide with: First off, thank you for considering contributing to Active Admin. It’s people like you that make Active Admin such a great tool. In the earliest stages of your project, your CONTRIBUTING file can be simple. You should always explain how to report bugs or file issues, and any technical requirements (like tests) to make a contribution. Over time, you might add other frequently asked questions to your CONTRIBUTING file. Writing down this information means fewer people will ask you the same questions over and over again. For more help with writing your CONTRIBUTING file, check out @nayafia’s contributing guide template or @mozilla’s “How to Build a CONTRIBUTING.md” . Link to your CONTRIBUTING file from your README, so more people see it. If you place the CONTRIBUTING file in your project’s repository , GitHub will automatically link to your file when a contributor creates an issue or opens a pull request. Establishing a code of conduct We’ve all had experiences where we faced what was probably abuse either as a maintainer trying to explain why something had to be a certain way, or as a user…asking a simple question. (…) A code of conduct becomes an easily referenced and linkable document that indicates that your team takes constructive discourse very seriously. — @mlynch, “Making Open Source a Happier Place” Finally, a code of conduct helps set ground rules for behavior for your project’s participants. This is especially valuable if you’re launching an open source project for a community or company. A code of conduct empowers you to facilitate healthy, constructive community behavior, which will reduce your stress as a maintainer. For more information, check out our Code of Conduct guide . In addition to communicating how you expect participants to behave, a code of conduct also tends to describe who these expectations apply to, when they apply, and what to do if a violation occurs. Much like open source licenses, there are also emerging standards for codes of conduct, so you don’t have to write your own. The Contributor Covenant is a drop-in code of conduct that is used by over 40,000 open source projects , including Kubernetes, Rails, and Swift. No matter which text you use, you should be prepared to enforce your code of conduct when necessary. Paste the text directly into a CODE_OF_CONDUCT file in your repository. Keep the file in your project’s root directory so it’s easy to find, and link to it from your README. Naming and branding your project Branding is more than a flashy logo or catchy project name. It’s about how you talk about your project, and who you reach with your message. Choosing the right name Pick a name that is easy to remember and, ideally, gives some idea of what the project does. For example: Sentry monitors apps for crash reporting Thin is a fast and simple Ruby web server If you’re building upon an existing project, using their name as a prefix can help clarify what your project does (for example, node-fetch brings window.fetch to Node.js). Consider clarity above all. Puns are fun, but remember that some jokes might not translate to other cultures or people with different experiences from you. Some of your potential users might be company employees: you don’t want to make them uncomfortable when they have to explain your project at work! Avoiding name conflicts Check for open source projects with a similar name , especially if you share the same language or ecosystem. If your name overlaps with a popular existing project, you might confuse your audience. If you want a website, Twitter handle, or other properties to represent your project, make sure you can get the names you want. Ideally, reserve those names now for peace of mind, even if you don’t intend to use them just yet. Make sure that your project’s name doesn’t infringe upon any trademarks. A company might ask you to take down your project later on, or even take legal action against you. It’s just not worth the risk. You can check the WIPO Global Brand Database for trademark conflicts. If you’re at a company, this is one of the things your legal team can help you with . Finally, do a quick Google search for your project name. Will people be able to easily find your project? Does something else appear in the search results that you wouldn’t want them to see? How you write (and code) affects your brand, too! Throughout the life of your project, you’ll do a lot of writing: READMEs, tutorials, community documents, responding to issues, maybe even newsletters and mailing lists. Whether it’s official documentation or a casual email, your writing style is part of your project’s brand. Consider how you might come across to your audience and whether that is the tone you wish to convey. I tried to be involved with every thread on the mailing list, and showing exemplary behaviour, being nice to people, taking their issues seriously and trying to be helpful overall. After a while, people stuck around not to only ask questions, but to help with the answering as well, and to my complete delight, they mimicked my style. — @janl on CouchDB , “Sustainable Open Source” Using warm, inclusive language (such as “them”, even when referring to the single person) can go a long way in making your project feel welcoming to new contributors. Stick to simple language, as many of your readers may not be native English speakers. Beyond how you write words, your coding style may also become part of your project’s brand. Angular and jQuery are two examples of projects with rigorous coding styles and guidelines. It isn’t necessary to write a style guide for your project when you’re just starting out, and you may find that you enjoy incorporating different coding styles into your project anyway. But you should anticipate how your writing and coding style might attract or discourage different types of people. The earliest stages of your project are your opportunity to set the precedent you wish to see. Your pre-launch checklist Ready to open source your project? Here’s a checklist to help. Check all the boxes? You’re ready to go! Click “publish” and pat yourself on the back. Documentation Project has a LICENSE file with an open source license Project has basic documentation (README, CONTRIBUTING, CODE_OF_CONDUCT) The name is easy to remember, gives some idea of what the project does, and does not conflict with an existing project or infringe on trademarks The issue queue is up-to-date, with issues clearly organized and labeled Code Project uses consistent code conventions and clear function/method/variable names The code is clearly commented, documenting intentions and edge cases There are no sensitive materials in the revision history, issues, or pull requests (for example, passwords or other non-public information) People If you’re an individual: You've talked to the legal department and/or understand the IP and open source policies of your company (if you're an employee somewhere) If you’re a company or organization: You've talked to your legal department You have a marketing plan for announcing and promoting the project Someone is committed to managing community interactions (responding to issues, reviewing and merging pull requests) At least two people have administrative access to the project You did it! Congratulations on open sourcing your first project. No matter the outcome, working in public is a gift to the community. With every commit, comment, and pull request, you’re creating opportunities for yourself and for others to learn and grow. Back to all guides Related Guides Finding Users for Your Project Help your open source project grow by getting it in the hands of happy users. Building Welcoming Communities Building a community that encourages people to use, contribute to, and evangelize your project. Scroll to Top Contribute Want to make a suggestion? This content is open source. Help us improve it. Contribute Stay in touch Be the first to hear about GitHub's latest open source tips and resources. Email Address fine print with by and friends | 2026-01-13T09:29:15 |
https://proceedings.mlr.press | Proceedings of Machine Learning Research | The Proceedings of Machine Learning Research (formerly JMLR Workshop and Conference Proceedings) is a series aimed specifically at publishing machine learning research presented at workshops and conferences. Each volume is separately titled and associated with a particular workshop or conference. Volumes are published online on the PMLR web site. The Series Editors are Neil D. Lawrence and Mark Reid. Proceedings of Machine Learning Research PMLR JMLR DMLR TMLR MLOSS FAQ Submission Format [ edit ] Proceedings of Machine Learning Research ISSN: 2640-3498 The Proceedings of Machine Learning Research is a series that publishes machine learning research papers presented at conferences and workshops. Each volume is separately titled and associated with a particular workshop or conference and will be published online on the PMLR web site. Authors retain copyright. Editors The Series Editor is Neil Lawrence . Please send proposals for new volumes under this series to us via e-mail: proceedings mlr.press . Each proposal should include: A brief description of the event's scope and topics to be covered. A description of the review process for the proceedings. The names and short CVs (a few lines) of the proposed Proceedings Editors. For details on how to prepare a proceedings for publication please see the Specification . For frequently asked questions on publishing proceedings please see the FAQ . Reissue Series We have launched a "reissue series" for republishing volumes of papers that are no longer on line. Our first reissues are early editions of AISTATS, AISTATS 1995 , AISTATS 1997 , AISTATS 1999 , AISTATS 2001 , AISTATS 2003 and AISTATS 2005 . To suggest volumes for the reissue series contact the editors. You will need to provide the information provided in the Proceedings Specification to provide the volume. Volume R6 Reissue of UAI 1998 Volume R0 Pre-proceedings of AISTATS 1995 Volume R5 Proceedings of AISTATS 2005 Volume R4 Proceedings of AISTATS 2003 Volume R3 Proceedings of AISTATS 2001 Volume R2 Proceedings of AISTATS 1999 Volume R1 Proceedings of AISTATS 1997 Proceedings Volume 311 Proceedings of MLCB 2025 Volume 310 Proceedings of Reliable AI Workshop at ACML Volume 305 Proceedings of CoRL 2025 Volume 299 Proceedings of CAMLIS 2025 Volume 298 Proceedings of MLHC 2025 Volume 268 AAAI 2024 Bridge Program on Continual Causality Volume 271 Proceedings of ProbNum 2025 Volume 266 Proceedings of COPA 2025 Volume 269 Proceedings of Learning on Graphs 2025 Volume 284 Proceedings of NeSy 2025 Volume 278 Proceedings of MLIC 2025 Volume 277 Proceedings of ML-DE 2025 Volume 267 Proceedings of ICML 2025 Volume 296 "I Can't Believe It's Not Better" ICLR Workshop 2025 Volume 295 Proceedings of UK AI Conference 2024 Volume 286 Proceedings of UAI 2025 Volume 294 Proceedings of European Workshop on Algorithmic Fairness Volume 293 Proceedings of AutoML 2025 Volume 280 Proceedings of CPAL 2025 Volume 287 Proceedings of CHIL 2025 Volume 292 TerraBytes at ICML 2025 Volume 275 Proceedings of CLeaR 2025 Volume 285 Proceedings of Unireps 2025 Volume 291 Proceedings of COLT 2025 Volume 290 Proceedings of ISIPTA 2025 Volume 288 Proceedings of Neurosymbolic Systems 2025 Volume 289 Proceedings of AABI 2025 Volume 283 Proceedings of L4DC 2025 Volume 279 Proceedings of Algorithmic Fairness Through the Lens of Metrics and Evaluation 2024 Volume 258 Proceedings of AISTATS 2025 Volume 281 Proceedings of The First AAAI Bridge Program on AI for Medicine and Healthcare Volume 273 Proceedings of iRAISE 2025 Volume 274 Proceedings of CoLLAs 2024 Volume 272 Proceedings of ALT 2025 Volume 259 Proceedings or ML4H 2024 Volume 264 Proceedings of Large Foundation Models for Educational Assessment Volume 260 Proceedings of ACML 2024 Volume 265 Proceedings of the Northern Lights Deep Learning Conference 2025 Volume 270 Proceedings of CoRL 2024 Volume 250 Proceedings of MIDL 2024 Volume 251 Proceedings of GRaM at ICML 2024 Volume 262 Proceedings of Efficient Natural Language and Signal Processing Workshop at NeurIPS 2024 Volume 263 Proceedings of CLDD 2024 Volume 252 Proceedings of MLHC 2024 Volume 254 Proceedings of MICCAI COMPAYL 2024 Volume 261 Proceedings of MLCB 2024 Volume 256 Proceedings of AutoML 2024 Volume 255 Proceedings of ML Meets Differential Equations Volume 244 Proceedings of UAI 2024 Volume 230 Proceedings of COPA 2024 Volume 246 Proceedings of PGM 2024 Volume 249 Proceedings of the 1st ContinualAI Unconference Volume 257 AI for Education Workshop 2024 Volume 228 Proceedings of NeuReps 2023 Volume 245 Proceedings of MLIC 2024 Volume 253 AABI 2024 Proceedings Volume 248 Proceedings of CHIL 2024 Volume 235 Proceedings of ICML 2024 Volume 247 Proceedings of COLT 2024 Volume 242 Proceedings of L4DC 2024 Volume 241 Proceedings of LIDTA 2023 Volume 243 Proceedings of UniReps Volume 226 Proceedings of the NeurIPS 2023 Gaze Meets ML Workshop Volume 239 "I Can't Believe It's Not Better" NeurIPS Workshop 2023 Volume 238 Proceedings of AISTATS 2024 Volume 231 Proceedings of Learning on Graphs 2023 Volume 236 Proceedings of CLeaR 2024 Volume 240 Proceedings of MLCB 2024 Volume 237 Proceedings of ALT 2024 Volume 222 Proceedings of ACML 2023 Volume 227 Proceedings of Medical Imaging with Deep Learning 2023 Volume 233 Proceedings of the Northern Lights Deep Learning Conference 2024 Volume 234 Proceedings of Conference on Parsimony and Learning 2024 Volume 219 Proceedings of Machine Learning for Healthcare 2023 Volume 225 Proceedings of the 3rd Machine Learning for Health Symposium Volume 207 Proceedings of the 3rd TeachML Workshop Volume 224 Proceedings of AutoML 2023 Volume 229 Proceedings of CoRL 2023 Volume 223 Proceedings of CAWS 2023 Volume 232 Proceedings of CoLLAs 2023 Volume 221 Proceedings of the 2nd Annual Topology, Algebra, and Geometry in Machine Learning (TAG-ML) Volume 220 Proceedings of the NeurIPS 2022 Competitions Track Volume 204 COPA 2023 Proceedings Volume 213 Proceedings of CLeaR 2023 Volume 218 Proceedings of KDD Workshop on Causal Discovery, Prediction and Decision 2023 Volume 195 Proceedings of COLT 2023 Volume 215 Proceedings of ISIPTA 2023 Volume 217 Proceedings of ICGI 2023 Volume 202 Proceedings of ICML 2023 Volume 216 Proceedings of UAI 2023 Volume 209 Proceedings of Conference on Health, Inference, and Learning 2023 Volume 211 Proceedings of L4DC 2023 Volume 214 Proceedings of AFCP 2022 Volume 208 Proceedings of the AAAI Bridge Symposium on Continual Causality 2023 Volume 212 Proceedings of the NeurIPS Cell Segmentation Challenge 2022 Volume 189 Proceedings of ACML 2022 Volume 206 Proceedings of AISTATS 2023 Volume 210 Proceedings of the NeurIPS 2022 Gaze Meets ML Workshop Volume 192 Proceedings of the 3rd Workshop on Self-Supervised Learning Volume 205 Proceedings of CoRL 2022 Volume 187 "I Can't Believe It's Not Better" NeurIPS Workshop 2022 Volume 201 Proceedings of ALT 2023 Volume 197 Proceedings of NeurReps Workshop 2022 Volume 182 Proceedings of MLHC 2022 Volume 203 Proceedings of Transfer Learning for NLP 2022 Volume 166 Proceedings of HEAR 2021 Volume 191 Proceedings of ECML/PKDD Workshop on Meta-Knowledge Transfer 2022 Volume 198 Proceedings of Learning on Graphs 2022 Volume 200 Proceedings of MLCB 2022 Volume 172 Proceedings of Medical Imaging with Deep Learning Volume 194 Proceedings of Geometric Deep Learning in Medical Image Analysis Volume 199 Proceedings of CoLLAs 2022 Volume 193 Proceedings of 2nd Machine Learning for Health Symposium Volume 196 Proceedings of Topological, Algebraic and Geometric Learning Workshops 2022 Volume 183 Proceedings of LIDTA 2022 Volume 181 Proceedings of the NeurIPS 2021 Workshop on Pre-registration in Machine Learning Volume 188 Proceedings of AutoML-Conf 2022 Volume 186 Proceedings of PGM 2022 Volume 190 Proceedings of MSML 2022 Volume 179 Proceedings of the 11th Symposium on Conformal and Probabilistic Prediction with Applications Volume 180 Proceedings of UAI 2022 Volume 185 Proceedings of KDD Workshop on Causal Discovery 2022 Volume 184 Proceedings of ICML 2022 Workshop on Healthcare AI and COVID-19 Volume 176 Proceedings of the NeurIPS 2021 Competitions and Demonstrations Track Volume 162 Proceedings of ICML 2022 Volume 177 Proceedings of CLeaR 2022 Volume 178 Proceedings of COLT 2022 Volume 168 Proceedings of Learning for Dynamics and Control 2022 Volume 151 Proceedings of AISTATS 2022 Volume 145 Proceedings of MSML 2021 Volume 159 Proceedings of IWSSL 2021 Volume 174 Proceedings of CHIL 2022 Volume 173 Proceedings of ICCV 2021 DYAD Workshop Volume 167 ALT 2022 Proceedings Volume 170 Proceedings of the 2nd Teaching Machine Learning and Artificial Intelligence Workshop Volume 171 Proceedings of AFCR 2021 Volume 163 "I Can't Believe It's Not Better" NeurIPS Workshop 2021 Volume 164 Proceedings of CoRL 2021 Volume 165 Proceedings of MLCB 2021 Volume 161 Proceedings of UAI 2021 Volume 160 Proceedings of Causal Analysis Workshop 2021 Volume 158 ML4H Symposium 2021 Volume 157 Proceedings of ACML 2021 Volume 149 Proceedings of Machine Learning for Healthcare 2021 Volume 155 Proceedings of CoRL 2020 Volume 154 Proceedings of LIDTA 2021 Volume 152 COPA 2021 Proceedings Volume 142 Proceedings of 2nd Workshop on Diversity in Artificial Intelligence Volume 156 Proceedings of COMPAY 2021 Volume 153 Proceedings of ICGI 2020 Volume 143 Proceedings of MIDL 2021 Volume 140 Proceedings of AAAI Workshop on Meta-Learning and MetaDL Challenge Volume 147 Proceedings of ISIPTA 2021 Volume 133 NeurIPS 2020 Competition and Demonstration Track Volume 150 Proceedings of KDD Workshop on Causal Discovery 2021 Volume 134 Proceedings of COLT 2021 Volume 148 Workshop on Preregistration in Machine Learning Volume 139 Proceedings of ICML 2021 Volume 144 Proceedings of Learning for Dynamics and Control 2021 Volume 146 Proceedings of AAAI Symposium on Survival Prediction - Algorithms, Challenges, and Applications Volume 141 Proceedings of the First Teaching Machine Learning and Artificial Intelligence Workshop Volume 130 Proceedings of AISTATS 2021 Volume 132 ALT 2021 Proceedings Volume 137 "I Can't Believe It's Not Better" NeurIPS Workshop 2020 Volume 138 Proceedings of PGM 2020 Volume 136 NeurIPS 2020 ML4H Workshop Volume 122 Proceedings of 3rd Workshop on AI in Affective Computing Volume 119 Proceedings of ICML 2020 Volume 129 Proceedings of ACML 2020 Volume 121 Proceedings of MIDL 2020 Volume 126 Proceedings of Machine Learning for Healthcare 2020 Volume 131 Proceedings of the International Workshop on Self-Supervised Learning Volume 124 Proceedings of UAI 2020 Volume 127 KDD 2020 Workshop on Causal Discovery Volume 123 NeurIPS 2019 Competition and Demonstration Track Volume 107 Proceedings of MSML 2020 Volume 128 COPA 2020 Proceedings Volume 115 Proceedings of UAI 2019 Volume 120 Proceedings of Learning for Dynamics and Control Volume 125 COLT 2020 Proceedings Volume 108 Proceedings of AISTATS 2020 Volume 116 NeurIPS 2019 ML4H Workshop Volume 86 IJCAI workshop on AI and Affective Computing Volume 118 AABI 2019 Proceedings Volume 117 ALT 2020 Proceedings Volume 106 Proceedings of Machine Learning for Healthcare 2019 Volume 101 ACML 2019 Proceedings Volume 109 Workshop on Online Recommender Systems and User Modeling 2019 Volume 105 Workshop on Conformal and Probabilistic Prediction with Applications (COPA) 2019 Volume 104 KDD Workshop on Causal Discovery 2019 Volume 103 ISIPTA 2019 Volume 102 Proceedings of MIDL 2019 Volume 97 Proceedings of ICML 2019 Volume 96 AABI 2018 Proceedings Volume 89 Proceedings of AISTATS 2019 Volume 93 ICGI 2018 Proceedings Volume 100 CoRL 2019 Volume 99 COLT 2019 Volume 98 ALT 2019 Proceedings Volume 85 Proceedings of Machine Learning for Healthcare 2018 Volume 94 LIDTA 2018 Proceedings Volume 95 ACML 2018 Proceedings Volume 87 CoRL 2018 Volume 92 2018 KDD Workshop on Causal Discovery Volume 82 Proceedings of PAPIs 2017 Volume 88 Proceedings of COST 2018 Volume 75 Proceedings of COLT 2018 Volume 80 Proceedings of ICML 2018 Volume 91 COPA 2018 Volume 90 ADE Identification Volume 83 ALT 2018 Proceedings Volume 84 AISTATS 2018 Proceedings Volume 81 FAT* 2018 Proceedings Volume 79 Open Algorithm Selection Challenge 2017 Volume 68 Proceedings of Machine Learning for Healthcare 2017 Volume 77 ACML 2017 Proceedings Volume 78 CoRL 2017 Proceedings Volume 74 LIDTA 2017 Proceedings Volume 76 ALT 2017 Proceedings Volume 72 Conference on Probabilistic Graphical Models 2018 Volume 73 2017 Workshop on Advanced Methodologies for Bayesian Networks Volume 71 Proceedings of the KDD 2017 Workshop on Anomaly Detection in Finance Volume 70 Proceedings of ICML 2017 Volume 69 MIH 2017 Proceedings Volume 67 3rd International Conference on Predictive Applications and APIs Volume 66 1st IJCAI Workshop on Artificial Intelligence in Affective Computing Volume 65 COLT 2017 Proceedings Volume 62 ISIPTA '17 Proceedings Volume 60 Workshop on Conformal and Probabilistic Prediction with Applications (COPA) 2017 Volume 58 NIPS 2016 Workshop on Imperfect Decision Makers Volume 54 AISTATS 2017 Proceedings Volume 64 AutoML 2016 Workshop Proceedings Volume 63 ACML 2016 Proceedings Volume 57 ICGI 2016 Proceedings Volume 56 Proceedings of Machine Learning for Healthcare 2016 Volume 55 NIPS 2016 Time Series Workshop Volume 53 BigMine 2016 Proceedings Volume 52 PGM 2016 Proceedings Volume 51 AISTATS 2016 Proceedings Volume 50 PAPIs 2015 Proceedings Volume 49 COLT 2016 Proceedings Volume 48 ICML 2016 Proceedings Volume 47 ECML/PKDD Workshop on Statistically Sound Data Mining 2014 Proceedings Volume 46 Neural Connectomics Workshop 2014 Proceedings Volume 45 ACML 2015 Proceedings Volume 44 NIPS Workshop on Feature Extraction 2015 Proceedings Volume 43 MLIS 2015 Proceedings Volume 42 HEPML 2014 Proceedings Volume 41 BigMine 2015 Proceedings Volume 40 COLT 2015 Proceedings Volume 39 ACML 2014 Proceedings Volume 38 AISTATS 2015 Proceedings Volume 37 ICML 2015 Proceedings Volume 36 BIGMINE 2014 Proceedings Volume 35 COLT 2014 Proceedings Volume 34 ICGI 2014 Proceedings Volume 33 AISTATS 2014 Proceedings Volume 32 ICML 2014 Proceedings Volume 31 AISTATS 2013 Proceedings Volume 30 COLT 2013 Proceedings Volume 29 ACML 2013 Proceedings Volume 28 ICML 2013 Proceedings Volume 27 Unsupervised and Transfer Learning Workshop at ICML 2011 Volume 26 On-line Trading of Exploration and Exploitation 2011 Proceedings Volume 25 ACML 2012 Proceedings Volume 24 EWRL 2012 Proceedings Volume 23 COLT 2012 Proceedings Volume 22 AISTATS 2012 Proceedings Volume 21 ICGI 2012 Proceedings Volume 20 ACML 2011 Proceedings Volume 19 COLT 2011 Proceedings Volume 18 KDD Cup 2011 Volume 17 Workshop on Applications of Pattern Analysis (WAPA) 2011 Proceedings Volume 16 Active Learning and Experimental Design Workshop Volume 15 AISTATS 2011 Proceedings Volume 14 Proceedings of the Learning to Rank Challenge Volume 13 ACML 2010 Proceedings Volume 12 NIPS Mini-Symposium on Causality in Time Series Volume 11 Workshop on Applications of Pattern Analysis (WAPA) 2010 Proceedings Volume 10 FSDM 2010 Proceedings Volume 9 AISTATS 2010 Proceedings Volume 8 Proceedings of MLSB 2009 Volume 7 Proceedings of KDD-Cup 2009 competition Volume 6 Causality: Objectives and Assessment (NIPS 2008 Workshop) Volume 5 AISTATS 2009 Proceedings Volume 4 New Challenges for Feature Selection in Data Mining and Knowledge Discovery Volume 3 Causation and Prediction Challenge (WCCI 2008) Volume 2 AISTATS 2007 Proceedings Volume 1 Gaussian Processes in Practice The proceedings were originally known as JMLR W&CP. Rebranding was finalised on 10th April 2017. The first volume to be published at the PMLR site was volume 54, the 2017 AISTATS Proceedings. The ISSN of the old proceedings was: 1938-7228. subscribe via RSS This site last compiled Wed, 31 Dec 2025 21:13:50 +0000 Github Account MLResearchPress | 2026-01-13T09:29:15 |
https://opensource.guide/starting-a-project/ | Starting an Open Source Project | Open Source Guides About Contribute العربية Български Bangla Deutsch Ελληνικά English Español Farsi Français Hindi Magyar Indonesia Italiano 日本語 한국어 Malay Nederlands Pidgin Polski Português Romanian Русский संस्कृतम् Swahili தமிழ் Türkçe 简体中文 繁體中文 Open Source Guides Starting an Open Source Project Learn more about the world of open source and get ready to launch your own project. Table of Contents The “what” and “why” of open source Should I launch my own open source project? Launching your own open source project Naming and branding your project Your pre-launch checklist The “what” and “why” of open source So you’re thinking about getting started with open source? Congratulations! The world appreciates your contribution. Let’s talk about what open source is and why people do it. What does “open source” mean? When a project is open source, that means anybody is free to use, study, modify, and distribute your project for any purpose. These permissions are enforced through an open source license . Open source is powerful because it lowers the barriers to adoption and collaboration, allowing people to spread and improve projects quickly. Also because it gives users a potential to control their own computing, relative to closed source. For example, a business using open source software has the option to hire someone to make custom improvements to the software, rather than relying exclusively on a closed source vendor’s product decisions. Free software refers to the same set of projects as open source . Sometimes you’ll also see these terms combined as “free and open source software” (FOSS) or “free, libre, and open source software” (FLOSS). Free and libre refer to freedom, not price . Why do people open source their work? One of the most rewarding experiences I get out of using and collaborating on open source comes from the relationships that I build with other developers facing many of the same problems I am. — @kentcdodds, “How getting into Open Source has been awesome for me” There are many reasons why a person or organization would want to open source a project. Some examples include: Collaboration: Open source projects can accept changes from anybody in the world. Exercism , for example, is a programming exercise platform with over 350 contributors. Adoption and remixing: Open source projects can be used by anyone for nearly any purpose. People can even use it to build other things. WordPress , for example, started as a fork of an existing project called b2 . Transparency: Anyone can inspect an open source project for errors or inconsistencies. Transparency matters to governments like Bulgaria or the United States , regulated industries like banking or healthcare, and security software like Let’s Encrypt . Open source isn’t just for software, either. You can open source everything from data sets to books. Check out GitHub Explore for ideas on what else you can open source. Does open source mean “free of charge”? One of open source’s biggest draws is that it does not cost money. “Free of charge”, however, is a byproduct of open source’s overall value. Because an open source license requires that anyone can use, modify, and share your project for nearly any purpose, projects themselves tend to be free of charge. If the project cost money to use, anyone could legally make a copy and use the free version instead. As a result, most open source projects are free, but “free of charge” is not part of the open source definition. There are ways to charge for open source projects indirectly through dual licensing or limited features, while still complying with the official definition of open source. Should I launch my own open source project? The short answer is yes, because no matter the outcome, launching your own project is a great way to learn how open source works. If you’ve never open sourced a project before, you might be nervous about what people will say, or whether anyone will notice at all. If this sounds like you, you’re not alone! Open source work is like any other creative activity, whether it’s writing or painting. It can feel scary to share your work with the world, but the only way to get better is to practice - even if you don’t have an audience. If you’re not yet convinced, take a moment to think about what your goals might be. Setting your goals Goals can help you figure out what to work on, what to say no to, and where you need help from others. Start by asking yourself, why am I open sourcing this project? There is no one right answer to this question. You may have multiple goals for a single project, or different projects with different goals. If your only goal is to show off your work, you may not even want contributions, and even say so in your README. On the other hand, if you do want contributors, you’ll invest time into clear documentation and making newcomers feel welcome. At some point I created a custom UIAlertView that I was using…and I decided to make it open source. So I modified it to be more dynamic and uploaded it to GitHub. I also wrote my first documentation explaining to other developers how to use it on their projects. Probably nobody ever used it because it was a simple project but I was feeling good about my contribution. — @mavris, “Self-taught Software Developers: Why Open Source is important to us” As your project grows, your community may need more than just code from you. Responding to issues, reviewing code, and evangelizing your project are all important tasks in an open source project. While the amount of time you spend on non-coding tasks will depend on the size and scope of your project, you should be prepared as a maintainer to address them yourself or find someone to help you. If you’re part of a company open sourcing a project, make sure your project has the internal resources it needs to thrive. You’ll want to identify who’s responsible for maintaining the project after launch, and how you’ll share those tasks with your community. If you need a dedicated budget or staffing for promotion, operations and maintaining the project, start those conversations early. As you begin to open source the project, it’s important to make sure that your management processes take into consideration the contributions and abilities of the community around your project. Don’t be afraid to involve contributors who are not employed in your business in key aspects of the project — especially if they are frequent contributors. — @captainsafia, “So you wanna open source a project, eh?” Contributing to other projects If your goal is to learn how to collaborate with others or understand how open source works, consider contributing to an existing project. Start with a project that you already use and love. Contributing to a project can be as simple as fixing typos or updating documentation. If you’re not sure how to get started as a contributor, check out our How to Contribute to Open Source guide . Launching your own open source project There is no perfect time to open source your work. You can open source an idea, a work in progress, or after years of being closed source. Generally speaking, you should open source your project when you feel comfortable having others view, and give feedback on, your work. No matter which stage you decide to open source your project, every project should include the following documentation: Open source license README Contributing guidelines Code of conduct As a maintainer, these components will help you communicate expectations, manage contributions, and protect everyone’s legal rights (including your own). They significantly increase your chances of having a positive experience. If your project is on GitHub, putting these files in your root directory with the recommended filenames will help GitHub recognize and automatically surface them to your readers. Choosing a license An open source license guarantees that others can use, copy, modify, and contribute back to your project without repercussions. It also protects you from sticky legal situations. You must include a license when you launch an open source project. Legal work is no fun. The good news is that you can copy and paste an existing license into your repository. It will only take a minute to protect your hard work. MIT , Apache 2.0 , and GPLv3 are the most popular open source licenses, but there are other options to choose from. When you create a new project on GitHub, you are given the option to select a license. Including an open source license will make your GitHub project open source. If you have other questions or concerns around the legal aspects of managing an open source project, we’ve got you covered . Writing a README READMEs do more than explain how to use your project. They also explain why your project matters, and what your users can do with it. In your README, try to answer the following questions: What does this project do? Why is this project useful? How do I get started? Where can I get more help, if I need it? You can use your README to answer other questions, like how you handle contributions, what the goals of the project are, and information about licenses and attribution. If you don’t want to accept contributions, or your project is not yet ready for production, write this information down. Better documentation means more users, less support requests, and more contributors. (…) Remember that your readers aren’t you. There are people who might come to a project who have completely different experiences. — @tracymakes, “Writing So Your Words Are Read (video)” Sometimes, people avoid writing a README because they feel like the project is unfinished, or they don’t want contributions. These are all very good reasons to write one. For more inspiration, try using @dguo’s “Make a README” guide or @PurpleBooth’s README template to write a complete README. When you include a README file in the root directory, GitHub will automatically display it on the repository homepage. Writing your contributing guidelines A CONTRIBUTING file tells your audience how to participate in your project. For example, you might include information on: How to file a bug report (try using issue and pull request templates ) How to suggest a new feature How to set up your environment and run tests In addition to technical details, a CONTRIBUTING file is an opportunity to communicate your expectations for contributions, such as: The types of contributions you’re looking for Your roadmap or vision for the project How contributors should (or should not) get in touch with you Using a warm, friendly tone and offering specific suggestions for contributions (such as writing documentation, or making a website) can go a long way in making newcomers feel welcomed and excited to participate. For example, Active Admin starts its contributing guide with: First off, thank you for considering contributing to Active Admin. It’s people like you that make Active Admin such a great tool. In the earliest stages of your project, your CONTRIBUTING file can be simple. You should always explain how to report bugs or file issues, and any technical requirements (like tests) to make a contribution. Over time, you might add other frequently asked questions to your CONTRIBUTING file. Writing down this information means fewer people will ask you the same questions over and over again. For more help with writing your CONTRIBUTING file, check out @nayafia’s contributing guide template or @mozilla’s “How to Build a CONTRIBUTING.md” . Link to your CONTRIBUTING file from your README, so more people see it. If you place the CONTRIBUTING file in your project’s repository , GitHub will automatically link to your file when a contributor creates an issue or opens a pull request. Establishing a code of conduct We’ve all had experiences where we faced what was probably abuse either as a maintainer trying to explain why something had to be a certain way, or as a user…asking a simple question. (…) A code of conduct becomes an easily referenced and linkable document that indicates that your team takes constructive discourse very seriously. — @mlynch, “Making Open Source a Happier Place” Finally, a code of conduct helps set ground rules for behavior for your project’s participants. This is especially valuable if you’re launching an open source project for a community or company. A code of conduct empowers you to facilitate healthy, constructive community behavior, which will reduce your stress as a maintainer. For more information, check out our Code of Conduct guide . In addition to communicating how you expect participants to behave, a code of conduct also tends to describe who these expectations apply to, when they apply, and what to do if a violation occurs. Much like open source licenses, there are also emerging standards for codes of conduct, so you don’t have to write your own. The Contributor Covenant is a drop-in code of conduct that is used by over 40,000 open source projects , including Kubernetes, Rails, and Swift. No matter which text you use, you should be prepared to enforce your code of conduct when necessary. Paste the text directly into a CODE_OF_CONDUCT file in your repository. Keep the file in your project’s root directory so it’s easy to find, and link to it from your README. Naming and branding your project Branding is more than a flashy logo or catchy project name. It’s about how you talk about your project, and who you reach with your message. Choosing the right name Pick a name that is easy to remember and, ideally, gives some idea of what the project does. For example: Sentry monitors apps for crash reporting Thin is a fast and simple Ruby web server If you’re building upon an existing project, using their name as a prefix can help clarify what your project does (for example, node-fetch brings window.fetch to Node.js). Consider clarity above all. Puns are fun, but remember that some jokes might not translate to other cultures or people with different experiences from you. Some of your potential users might be company employees: you don’t want to make them uncomfortable when they have to explain your project at work! Avoiding name conflicts Check for open source projects with a similar name , especially if you share the same language or ecosystem. If your name overlaps with a popular existing project, you might confuse your audience. If you want a website, Twitter handle, or other properties to represent your project, make sure you can get the names you want. Ideally, reserve those names now for peace of mind, even if you don’t intend to use them just yet. Make sure that your project’s name doesn’t infringe upon any trademarks. A company might ask you to take down your project later on, or even take legal action against you. It’s just not worth the risk. You can check the WIPO Global Brand Database for trademark conflicts. If you’re at a company, this is one of the things your legal team can help you with . Finally, do a quick Google search for your project name. Will people be able to easily find your project? Does something else appear in the search results that you wouldn’t want them to see? How you write (and code) affects your brand, too! Throughout the life of your project, you’ll do a lot of writing: READMEs, tutorials, community documents, responding to issues, maybe even newsletters and mailing lists. Whether it’s official documentation or a casual email, your writing style is part of your project’s brand. Consider how you might come across to your audience and whether that is the tone you wish to convey. I tried to be involved with every thread on the mailing list, and showing exemplary behaviour, being nice to people, taking their issues seriously and trying to be helpful overall. After a while, people stuck around not to only ask questions, but to help with the answering as well, and to my complete delight, they mimicked my style. — @janl on CouchDB , “Sustainable Open Source” Using warm, inclusive language (such as “them”, even when referring to the single person) can go a long way in making your project feel welcoming to new contributors. Stick to simple language, as many of your readers may not be native English speakers. Beyond how you write words, your coding style may also become part of your project’s brand. Angular and jQuery are two examples of projects with rigorous coding styles and guidelines. It isn’t necessary to write a style guide for your project when you’re just starting out, and you may find that you enjoy incorporating different coding styles into your project anyway. But you should anticipate how your writing and coding style might attract or discourage different types of people. The earliest stages of your project are your opportunity to set the precedent you wish to see. Your pre-launch checklist Ready to open source your project? Here’s a checklist to help. Check all the boxes? You’re ready to go! Click “publish” and pat yourself on the back. Documentation Project has a LICENSE file with an open source license Project has basic documentation (README, CONTRIBUTING, CODE_OF_CONDUCT) The name is easy to remember, gives some idea of what the project does, and does not conflict with an existing project or infringe on trademarks The issue queue is up-to-date, with issues clearly organized and labeled Code Project uses consistent code conventions and clear function/method/variable names The code is clearly commented, documenting intentions and edge cases There are no sensitive materials in the revision history, issues, or pull requests (for example, passwords or other non-public information) People If you’re an individual: You've talked to the legal department and/or understand the IP and open source policies of your company (if you're an employee somewhere) If you’re a company or organization: You've talked to your legal department You have a marketing plan for announcing and promoting the project Someone is committed to managing community interactions (responding to issues, reviewing and merging pull requests) At least two people have administrative access to the project You did it! Congratulations on open sourcing your first project. No matter the outcome, working in public is a gift to the community. With every commit, comment, and pull request, you’re creating opportunities for yourself and for others to learn and grow. Back to all guides Related Guides Finding Users for Your Project Help your open source project grow by getting it in the hands of happy users. Building Welcoming Communities Building a community that encourages people to use, contribute to, and evangelize your project. Scroll to Top Contribute Want to make a suggestion? This content is open source. Help us improve it. Contribute Stay in touch Be the first to hear about GitHub's latest open source tips and resources. Email Address fine print with by and friends | 2026-01-13T09:29:15 |
https://huggingface.co/search/full-text?type=dataset | Full Text Search - Hugging Face Hugging Face Models Datasets Spaces Community Docs Enterprise Pricing Log In Sign Up Full-text search models datasets spaces We index all model cards, dataset cards, and Spaces' app.py files. System theme Company TOS Privacy About Careers Website Models Datasets Spaces Pricing Docs | 2026-01-13T09:29:15 |
https://t.me/FuseSupportBot | Telegram: Launch @FuseSupportBot Download Support Bot (Won't DM) @FuseSupportBot Create a support ticket using this bot to send an issue request to Fuse team. Start Bot If you have Telegram , you can launch Support Bot (Won't DM) right away. | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/tencentglobal-tencent-cloud-automation-tools/ | Tencent Cloud Automation Tools | LinkedIn Skip to main content LinkedIn Tencent in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Tencent Cloud Automation Tools Build Automation Tools by Tencent See who's skilled in this Add as skill Learn more Report this product About TencentCloud Automation Tools (TAT) is a native Ops and deployment tool for CVM and Lighthouse instances. It supports automatic remote operations for instance management, batch execution of commands (Shell, Powershell, Python), and common tasks such as running automated Ops scripts, polling, installing/uninstalling software, updating applications, and installing patches. Similar products ARM ARM Build Automation Tools Tenjin Enterprise Tenjin Enterprise Build Automation Tools ElectroNeek: RPA and AI Platform Reviews ElectroNeek: RPA and AI Platform Reviews Build Automation Tools Develocity Develocity Build Automation Tools M156AD Rugged Tablet (Big Screen) M156AD Rugged Tablet (Big Screen) Build Automation Tools Rappit Developer Rappit Developer Build Automation Tools Sign in to see more Show more Show less Tencent products Cloud Native Database TDSQL-C Cloud Native Database TDSQL-C Relational Database Management Systems Cloud Object Storage (COS) Cloud Object Storage (COS) Object Storage Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Simple Email Service (SES) Simple Email Service (SES) Email Marketing Software Tencent Cloud Block Storage Tencent Cloud Block Storage Block Storage Software Tencent Cloud Instant Messaging (IM) Tencent Cloud Instant Messaging (IM) Cloud Communications Platforms Tencent Cloud Lighthouse Tencent Cloud Lighthouse Enterprise Cloud Platforms Tencent Effect SDK Tencent Effect SDK Software Development Kits (SDK) Tencent Real-Time Communication (TRTC) Tencent Real-Time Communication (TRTC) Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
http://fossmarks.org/post/ | Home About The Guide Contributors Seek Advice The Guide Chapter 1: Trademark Basics Understand the basics of trademarks, and how they apply to picking a name and logo for your project. Chapter 2: Choosing a Name or Logo What should you think about when picking a name and why, along with some helpful techniques and tips. Chapter 3: Clearing a Trademark What is 'clearing' a trademark, and when should you do it? Chapter 4: Trademark Ownership Who actually owns a trademark for a project and other considerations for community projects. Chapter 5: Registering your Trademark What's the difference between "registered" and "unregistered" trademarks, and what's the benefit of registering? Chapter 6: Commercializing your Project If monetization is an option, what else should you consider for your projects? Chapter 7: Someone Else is Using your Trademark Determine your strategy for enforcing your rights againts those infringing on your trademark. Chapter 8: Balancing Sharing v. Protecting How do you balance wanting people to use your code with protecting your trademarks? All content is licensed under the Creative Commons Attribution 4.0 International License . Thank you to the FSFE for hosting this site. | 2026-01-13T09:29:15 |
https://kabirk.com/wimmelbench#benchmark-construction | How well can LLMs see? · Kabir Khandpur HOME EMAIL --> --> How well can LLMs see? 21 Nov 2024 --> TL;DR I created Wimmelbench, a benchmark to test how well multimodal language models can find specific objects in complex illustrations. The best model (Gemini Pro) could accurately describe objects 31% of the time but struggled with precise location marking. Models performed better with larger objects and showed varying tendencies to hallucinate non-existent items. Introduction I was recently reminded of old picture books I used to own. The illustrations inside were completely hand-drawn, richly detailed scenes, packed with dozens of people, overlapping objects, and multiple activities — reminiscent of Where’s Waldo , except that you’re not hunting for a particular character. This type of illustration is called wimmelbilder , which is German for “teeming picture”. A wimmelbilder. My favourite bit is man playing the clarinet in his balcony to an audience of rooftop cats. While I’m convinced that LLMs can really “read” language, I’m less sure that they “see” images. To measure sight quantitatively, I created a small benchmark that I’m calling Wimmelbench. Wimmelbench takes inspiration from needle in a haystack . In that benchmark, a random fact (the needle) is inserted into the middle of a large piece of text (the haystack), and an LLM is asked to retrieve the fact. Most LLMs these days score close to 100% on this task. Wimmelbench is the image analogue: a model is asked to describe a small object (the needle) in a complex scene (the haystack) and draw a bounding box around it. The best multimodal language model I tested was Gemini Pro, which can accurately locate small objects 31% of the time . This increases to 73% if ‘mostly correct’ descriptions are also included. The models were much poorer at drawing bounding boxes, with Gemini scoring the best at a mean GIoU Generalized Intersection over Union . Typically a GIoU score of 0.5 and above is considered good. of 0.13 and Claude 3.6 Sonnet & GPT-4o scoring -0.5. In this post, I’ll talk about constructing the benchmark , go into more detail on the results , and offer some analysis . Aside: why not SAM? Segment Anything Model (SAM) is Meta’s foundation model for promptable segmentation in images and videos. It accepts masks, points, bounding boxes — but not text — as prompts. SAM segmenting an image SAM-based models like LISA do allow text inputs like “Segment the red car in the image”. I expect that it would score well on Wimmelbench. So why benchmark large language models? It tests how well the most general purpose, human-like models we have today understand images. I’m interested in “easy” unsaturated benchmarks that reveal a real shortcoming in current LLMs. I didn’t have easy access to the SAM-based models. It seemed like a fun project. Benchmark construction I collected 50 images from various sources on the internet, mostly from book storefronts and Behance. I searched specifically for wimmelbilder scenes that had a diverse range of objects and activities. They tended to be cartoonish since the style is so popular in children’s books. To create the ground truth dataset, I (well, mostly Claude) built a web-based annotation tool, which I used to manually write descriptions and draw bounding boxes for 84 objects in 50 images. I aimed to have a range of sizes and locations for the objects. The annotation tool In each description, I included the object’s location, distinguishing features, and relation to nearby objects. The annotations were saved to a JSON file. To visualize the range of object sizes in the dataset, I plotted the distribution of each bounding box’s area as a percentage of the total image area (figure 1). Figure 1: Distribution of (ground truth bounding box area / image area) The distribution covered a range from 0.1% to 10% of the image area, with most boxes in the 0.1% - 1% range. Ideally, I’d have hundreds of boxes and a more uniform distribution, but this looked reasonable enough to begin evaluation. Next, I asked Claude 3.6 Sonnet, Gemini 1.5 Pro, and GPT-4o Specifically claude-3-5-sonnet-20241022 , gemini-1.5-pro-002 , and gpt-4o-2024-08-06 . to do two things: first, describe a specific object in an image; second, return the bounding box coordinates around that object. I noted that the object may not be present in the image, so that I could later test how much models would hallucinate. I used a slightly different prompt All prompts are available on GitHub . for Gemini because it’s been trained to return bounding box coordinates in the format [ymin, xmin, ymax, xmax] from the range [ 0 , 1000 ] [0, 1000] [ 0 , 1000 ] . I experimented with the same format for Claude and GPT-4o, but performance was slightly worse than using the internet-standard bounding box coordinates of [x1, y1, x2, y2] with values in [ 0 , 1 ] [0, 1] [ 0 , 1 ] . I then asked Gemini 1.5 Pro to grade the accuracy of the bounding box predictions on a scale of 0-3, where: 0 : Completely incorrect or missing critical details. 1 : Partially correct but missing many important details or containing significant inaccuracies. 2 : Majorly correct with some inaccuracies or missing details. 3 : Mostly or fully correct, capturing the majority of key details and spatial relationships accurately. I tried using the smaller Gemini Flash, but Gemini Pro was closer to my own judgement — looking through its reasoning, I’d quibble with at most 10% of its ratings. It was also consistent in returning the same grades when run multiple times. See the appendix for examples of bounding box predictions and grading. You can find the full evaluation code , grading code and results in the GitHub repository. Results 1. Description accuracy All models scored a grade of 3 for about 30% of object descriptions. If we also include the mostly correct descriptions (grade 2), then Gemini outperforms the other models, scoring 73%, compared to 55% for GPT-4o and 49% for Claude (figure 2). Figure 2: Grade 2. Bounding box precision The models are much worse at predicting bounding box coordinates. For each object, I plotted the model’s Generalized Intersection over Union (GIoU) G I o U = ∣ A ∩ B ∣ ∣ A ∪ B ∣ − ∣ C \ ( A ∪ B ) ∣ ∣ C ∣ GIoU = \frac{|A\cap B|}{|A\cup B|} - \frac{|C\backslash(A\cup B)|}{|C|} G I o U = ∣ A ∪ B ∣ ∣ A ∩ B ∣ − ∣ C ∣ ∣ C \ ( A ∪ B ) ∣ , where C C C is the smallest convex hull that encloses both A A A and B B B . between the predicted and ground truth bounding boxes (figure 3). GIoU scores range from -1 to 1, where 1.0 is perfect overlap; 0.0 means no overlap; negative values indicate the predicted box is far from the target. 0.5+ is typically considered good in computer vision tasks. Gemini Pro scores the best, with a mean GIoU of 0.13. Claude and GPT-4o score -0.60 and -0.67 respectively. Figure 3: Distribution of GIoU scores 3. Hallucination rate To test how much the models would pretend to see objects that weren’t there, I asked them to locate a telescope in each of the 50 images (figure 4). GPT-4o was the biggest liar, finding a telescope in 96% of the images (!). Claude hallucinated 30% of the time, but again Gemini led the pack, only hallucinating in 12% of the images. When it did hallucinate, it tended to be with similar objects like cameras or binoculars. Figure 4: Hallucination rate Analysis Takeaways Gemini Pro scores best on both description and bounding box accuracy. Models can often describe objects well, but struggle to locate them precisely. Object size strongly influences bounding box accuracy, but not description quality. Size sometimes matters Bounding box accuracy showed a strong correlation with object size (figure 5). R 2 R^2 R 2 was ~0.5, which means that half of the variance in bounding box accuracy is explained by object size. Figure 5: GIoU vs area ratio Grade was much less correlated with object size (figure 6). Models seemed to struggle (and succeed) more equally to describe an object across a range of sizes. Figure 6: Grade vs area ratio Grade vs bounding box accuracy Grade was only weakly correlated with bounding box accuracy (figure 7). Here Gemini showed the strongest correlation: if it was able to describe an object accurately, it would tend to draw an accurate bounding box. Figure 7: Grade vs GIoU This means that a model could often describe an object in the correct place but give completely incorrect bounding box coordinates, even for large objects. When asked to describe the cartoon tiger in this image, Claude said: "There is a yellow cartoon tiger with black stripes sitting at one of the classroom tables, approximately in the middle-left portion of the image. It appears to be a stuffed animal or toy tiger sitting on a chair at a desk with some school supplies. The tiger has a typical cartoonish appearance with distinctive black stripes on yellow fur." But the bounding box prediction (drawn in red without a label) is completely incorrect. If you gave a human the same task, this wouldn’t happen — if someone could see an object, they could draw a bounding box around it. Maybe this is a prompt issue? I wouldn’t be able to guess bounding box coordinates as 0-1 ratios either, so maybe this isn’t a fair comparison. I saw a Reddit post that suggested overlaying a grid on the image and asking the model to return grid coordinates yielded better results. Perhaps performance could also improve with additional post-training techniques. Claude with computer use is somehow able to move the cursor to a pixel-perfect location on screen, which I assume is the result of specific post-training. Similar strategies would likely transfer well to determining bounding box coordinates. Gemini’s stronger performance also suggests that there are post-training steps From the Gemini docs : “For object detection, the Gemini model has been trained to provide these coordinates as relative widths or heights…” that can be taken to improve accuracy. I don’t understand the description accuracy variance Object size only explains half the variance in description accuracy: that is, the same object size would sometimes score perfectly, and other times completely incorrectly. For example, I was surprised at how well Gemini described the ‘couple kissing’: "In the bottom right corner of the image, a couple is kissing behind some large, bright green leaves. The woman has long brown hair and is wearing a red headscarf and top. The man has short brown curly hair and is wearing a bright red shirt. Just below the kissing couple, a person with short yellow hair and a yellow-green shirt is holding a knife." On the other hand, it completely fails to find the lifebuoy in the picture below, even though it’s roughly the same size as the previous object. "A child floats on an orange lifebuoy in a small pool near the bottom right of the image. The lifebuoy is round and appears inflated. Another child is jumping into the pool. A waiter in a black suit walks towards the pool, carrying a tray with drinks." The lifebuoy is actually in the top right, on the side of the lifeguard's tall chair. I don’t understand what causes the difference in ability. Future work If I had more time… Expand the dataset to several hundred objects. Test with more LLMs and also specialized vision models like SAM. Improve prompting strategies for bounding box prediction. Conclusion Wimmelbench convinced me that the big lab’s language models indeed cannot see as well as they read. I suspect part of it is due to object size, part due to post-training, and part due to tokenization and model architecture. I’d love to hear your thoughts — feel free to email me . Appendix: example results Claude Gemini GPT-4o Click to zoom in. Object Ground truth description Model description Grade GIoU Cactus A small, green cactus is potted in the window of a light gray building on the left side of the image, near the middle vertically. In the window next to it is an orange cat. Both windows are above teal awning. There appears to be a small green cactus in a pot being carried on a serving tray by one of the rabbit/bunny characters on the left side of the street. The bunny is one of two gray bunnies carrying food items on trays, likely heading towards the ‘EAT ME’ café in the scene. 0 -0.89 Elephant There is an elephant standing on two legs near the bottom-middle of the image. Its is holding a paintbrush and paint palette, wearing a purple top, and has an easel in front of it. The elephant is standing on the road. Mice are playing by its feet. Other animals are nearby. There is a large grey elephant character sitting in the center of the street scene. The elephant is wearing a purple velvet robe or jacket and appears to be painting on a canvas that’s set up on an easel. The elephant has distinctive large ears, a long trunk, and is shown in a sitting position while engaged in artistic activity. It appears to be one of the main focal points of the busy street scene, surrounded by various other animal characters. 2 -0.51 Click to zoom in. Object Ground truth description Model description Grade GIoU Cactus A small, green cactus is potted in the window of a light gray building on the left side of the image, near the middle vertically. In the window next to it is an orange cat. Both windows are above teal awning. A small, green cactus is located inside the first floor window of the grey building on the left side of the image. It is positioned on the window sill. 3 0.52 Elephant There is an elephant standing on two legs near the bottom-middle of the image. Its is holding a paintbrush and paint palette, wearing a purple top, and has an easel in front of it. The elephant is standing on the road. Mice are playing by its feet. Other animals are nearby. An elephant wearing a purple robe is painting on a canvas, standing on the street, slightly left of the image’s center. The elephant is facing left and holds a paintbrush in its trunk and a palette in its left hand. A wooden easel holds the canvas. Directly to the elephant’s right, a light gray cow seems to be giving a presentation while holding a microphone. 3 0.70 Click to zoom in. Object Ground truth description Model description Grade GIoU Cactus A small, green cactus is potted in the window of a light gray building on the left side of the image, near the middle vertically. In the window next to it is an orange cat. Both windows are above teal awning. The cactus is located in the bottom-right corner of the image. It is held by the giraffe and is green with several small red-orange flowers or spikes protruding from it. The giraffe is standing on the sidewalk next to a colorful group of animals. 0 -0.98 Elephant There is an elephant standing on two legs near the bottom-middle of the image. Its is holding a paintbrush and paint palette, wearing a purple top, and has an easel in front of it. The elephant is standing on the road. Mice are playing by its feet. Other animals are nearby. The elephant is located slightly left of center in the lower half of the image. It is wearing a purple robe and holding a paint palette and brush, standing next to an easel. The elephant appears to be engaging in painting. 3 0.31 Claude Gemini GPT-4o Object Ground truth description Model description Grade GIoU Man waving a white flag A man waving a white flag is in the top left of the image, by a broken a window. He is hung up on a light fixture by his jacket. To his right is a person falling, visible behind a broken window. Below him are people fighting each other. In the far right upper portion of the chaotic scene, there is a man waving a white flag or surrendering. He’s wearing what appears to be blue clothing and is positioned near the green paneled wall. He’s surrounded by the general mayhem of the room, with other figures nearby also in various states of distress or motion. 0 -0.94 Bowling ball A small black bowling ball is in the middle-right of the image. It is in the air, in between two men. The man on the right has punched the man on the left who is reeling backwards. The bowling ball looks like it came off left man’s hand. There is a black bowling ball visible in the chaotic scene, located in roughly the center-right portion of the image. It appears to be rolling or has been knocked loose during the mayhem, sitting on the wooden floor among the scattered people and overturned furniture. The bowling ball stands out as a small, round, black object amid the chaos of the cartoon scene. 0 -0.94 Object Ground truth description Model description Grade GIoU Man waving a white flag A man waving a white flag is in the top left of the image, by a broken a window. He is hung up on a light fixture by his jacket. To his right is a person falling, visible behind a broken window. Below him are people fighting each other. A man waving a white flag from which pieces of paper are falling is visible in the top left part of the image. He is wearing a blue suit, is seated on a short wall, and appears to be looking down at the chaotic scene below him. Behind him, one person climbs in through a broken window while another climbs out. The room has pale green walls with wood panelling. 1 0.04 Bowling ball A small black bowling ball is in the middle-right of the image. It is in the air, in between two men. The man on the right has punched the man on the left who is reeling backwards. The bowling ball looks like it came off left man’s hand. A bowling ball can be seen lying on the floor amidst the chaotic scene. It’s located slightly below the center-left portion of the image, amongst a group of people engaged in a brawl. Its color is predominantly dark gray or black. It is not in motion. It’s spatially close to a scattered pile of what appear to be pins, suggesting that it’s part of the chaotic activity in the depicted scene. 0 -0.99 Object Ground truth description Model description Grade GIoU Man waving a white flag A man waving a white flag is in the top left of the image, by a broken a window. He is hung up on a light fixture by his jacket. To his right is a person falling, visible behind a broken window. Below him are people fighting each other. The man waving a white flag is located in the bottom right portion of the image. He is wearing a white outfit, lying on the ground on his back, and holding a white flag up in the air. Nearby, there are people in animated poses, and the floor is wooden. 0 -0.98 Bowling ball A small black bowling ball is in the middle-right of the image. It is in the air, in between two men. The man on the right has punched the man on the left who is reeling backwards. The bowling ball looks like it came off left man’s hand. The bowling ball is black and located slightly to the right of the center of the image. It is on the floor in front of a group of people who appear to be crouching or dancing. The ball is near a man who is about to step on it, creating a sense of impending comedic chaos. 0 -0.85 | 2026-01-13T09:29:15 |
http://fossmarks.org/seekadvice/ | Seek Advice Seek Advice Home About The Guide Contributors Seek Advice Seek Advice Reach out to an expert Contributing Trademark Experts Anthonia Ghalamkarizadeh Hogan Lovells, Hamburg, Deutschland Pamela Chestek Chestek Legal, Raleigh, North Carolina, United States Other Trademark Experts Get listed here All content is licensed under the Creative Commons Attribution 4.0 International License . Thank you to the FSFE for hosting this site. | 2026-01-13T09:29:15 |
https://kabirk.com/wimmelbench#size-sometimes-matters | How well can LLMs see? · Kabir Khandpur HOME EMAIL --> --> How well can LLMs see? 21 Nov 2024 --> TL;DR I created Wimmelbench, a benchmark to test how well multimodal language models can find specific objects in complex illustrations. The best model (Gemini Pro) could accurately describe objects 31% of the time but struggled with precise location marking. Models performed better with larger objects and showed varying tendencies to hallucinate non-existent items. Introduction I was recently reminded of old picture books I used to own. The illustrations inside were completely hand-drawn, richly detailed scenes, packed with dozens of people, overlapping objects, and multiple activities — reminiscent of Where’s Waldo , except that you’re not hunting for a particular character. This type of illustration is called wimmelbilder , which is German for “teeming picture”. A wimmelbilder. My favourite bit is man playing the clarinet in his balcony to an audience of rooftop cats. While I’m convinced that LLMs can really “read” language, I’m less sure that they “see” images. To measure sight quantitatively, I created a small benchmark that I’m calling Wimmelbench. Wimmelbench takes inspiration from needle in a haystack . In that benchmark, a random fact (the needle) is inserted into the middle of a large piece of text (the haystack), and an LLM is asked to retrieve the fact. Most LLMs these days score close to 100% on this task. Wimmelbench is the image analogue: a model is asked to describe a small object (the needle) in a complex scene (the haystack) and draw a bounding box around it. The best multimodal language model I tested was Gemini Pro, which can accurately locate small objects 31% of the time . This increases to 73% if ‘mostly correct’ descriptions are also included. The models were much poorer at drawing bounding boxes, with Gemini scoring the best at a mean GIoU Generalized Intersection over Union . Typically a GIoU score of 0.5 and above is considered good. of 0.13 and Claude 3.6 Sonnet & GPT-4o scoring -0.5. In this post, I’ll talk about constructing the benchmark , go into more detail on the results , and offer some analysis . Aside: why not SAM? Segment Anything Model (SAM) is Meta’s foundation model for promptable segmentation in images and videos. It accepts masks, points, bounding boxes — but not text — as prompts. SAM segmenting an image SAM-based models like LISA do allow text inputs like “Segment the red car in the image”. I expect that it would score well on Wimmelbench. So why benchmark large language models? It tests how well the most general purpose, human-like models we have today understand images. I’m interested in “easy” unsaturated benchmarks that reveal a real shortcoming in current LLMs. I didn’t have easy access to the SAM-based models. It seemed like a fun project. Benchmark construction I collected 50 images from various sources on the internet, mostly from book storefronts and Behance. I searched specifically for wimmelbilder scenes that had a diverse range of objects and activities. They tended to be cartoonish since the style is so popular in children’s books. To create the ground truth dataset, I (well, mostly Claude) built a web-based annotation tool, which I used to manually write descriptions and draw bounding boxes for 84 objects in 50 images. I aimed to have a range of sizes and locations for the objects. The annotation tool In each description, I included the object’s location, distinguishing features, and relation to nearby objects. The annotations were saved to a JSON file. To visualize the range of object sizes in the dataset, I plotted the distribution of each bounding box’s area as a percentage of the total image area (figure 1). Figure 1: Distribution of (ground truth bounding box area / image area) The distribution covered a range from 0.1% to 10% of the image area, with most boxes in the 0.1% - 1% range. Ideally, I’d have hundreds of boxes and a more uniform distribution, but this looked reasonable enough to begin evaluation. Next, I asked Claude 3.6 Sonnet, Gemini 1.5 Pro, and GPT-4o Specifically claude-3-5-sonnet-20241022 , gemini-1.5-pro-002 , and gpt-4o-2024-08-06 . to do two things: first, describe a specific object in an image; second, return the bounding box coordinates around that object. I noted that the object may not be present in the image, so that I could later test how much models would hallucinate. I used a slightly different prompt All prompts are available on GitHub . for Gemini because it’s been trained to return bounding box coordinates in the format [ymin, xmin, ymax, xmax] from the range [ 0 , 1000 ] [0, 1000] [ 0 , 1000 ] . I experimented with the same format for Claude and GPT-4o, but performance was slightly worse than using the internet-standard bounding box coordinates of [x1, y1, x2, y2] with values in [ 0 , 1 ] [0, 1] [ 0 , 1 ] . I then asked Gemini 1.5 Pro to grade the accuracy of the bounding box predictions on a scale of 0-3, where: 0 : Completely incorrect or missing critical details. 1 : Partially correct but missing many important details or containing significant inaccuracies. 2 : Majorly correct with some inaccuracies or missing details. 3 : Mostly or fully correct, capturing the majority of key details and spatial relationships accurately. I tried using the smaller Gemini Flash, but Gemini Pro was closer to my own judgement — looking through its reasoning, I’d quibble with at most 10% of its ratings. It was also consistent in returning the same grades when run multiple times. See the appendix for examples of bounding box predictions and grading. You can find the full evaluation code , grading code and results in the GitHub repository. Results 1. Description accuracy All models scored a grade of 3 for about 30% of object descriptions. If we also include the mostly correct descriptions (grade 2), then Gemini outperforms the other models, scoring 73%, compared to 55% for GPT-4o and 49% for Claude (figure 2). Figure 2: Grade 2. Bounding box precision The models are much worse at predicting bounding box coordinates. For each object, I plotted the model’s Generalized Intersection over Union (GIoU) G I o U = ∣ A ∩ B ∣ ∣ A ∪ B ∣ − ∣ C \ ( A ∪ B ) ∣ ∣ C ∣ GIoU = \frac{|A\cap B|}{|A\cup B|} - \frac{|C\backslash(A\cup B)|}{|C|} G I o U = ∣ A ∪ B ∣ ∣ A ∩ B ∣ − ∣ C ∣ ∣ C \ ( A ∪ B ) ∣ , where C C C is the smallest convex hull that encloses both A A A and B B B . between the predicted and ground truth bounding boxes (figure 3). GIoU scores range from -1 to 1, where 1.0 is perfect overlap; 0.0 means no overlap; negative values indicate the predicted box is far from the target. 0.5+ is typically considered good in computer vision tasks. Gemini Pro scores the best, with a mean GIoU of 0.13. Claude and GPT-4o score -0.60 and -0.67 respectively. Figure 3: Distribution of GIoU scores 3. Hallucination rate To test how much the models would pretend to see objects that weren’t there, I asked them to locate a telescope in each of the 50 images (figure 4). GPT-4o was the biggest liar, finding a telescope in 96% of the images (!). Claude hallucinated 30% of the time, but again Gemini led the pack, only hallucinating in 12% of the images. When it did hallucinate, it tended to be with similar objects like cameras or binoculars. Figure 4: Hallucination rate Analysis Takeaways Gemini Pro scores best on both description and bounding box accuracy. Models can often describe objects well, but struggle to locate them precisely. Object size strongly influences bounding box accuracy, but not description quality. Size sometimes matters Bounding box accuracy showed a strong correlation with object size (figure 5). R 2 R^2 R 2 was ~0.5, which means that half of the variance in bounding box accuracy is explained by object size. Figure 5: GIoU vs area ratio Grade was much less correlated with object size (figure 6). Models seemed to struggle (and succeed) more equally to describe an object across a range of sizes. Figure 6: Grade vs area ratio Grade vs bounding box accuracy Grade was only weakly correlated with bounding box accuracy (figure 7). Here Gemini showed the strongest correlation: if it was able to describe an object accurately, it would tend to draw an accurate bounding box. Figure 7: Grade vs GIoU This means that a model could often describe an object in the correct place but give completely incorrect bounding box coordinates, even for large objects. When asked to describe the cartoon tiger in this image, Claude said: "There is a yellow cartoon tiger with black stripes sitting at one of the classroom tables, approximately in the middle-left portion of the image. It appears to be a stuffed animal or toy tiger sitting on a chair at a desk with some school supplies. The tiger has a typical cartoonish appearance with distinctive black stripes on yellow fur." But the bounding box prediction (drawn in red without a label) is completely incorrect. If you gave a human the same task, this wouldn’t happen — if someone could see an object, they could draw a bounding box around it. Maybe this is a prompt issue? I wouldn’t be able to guess bounding box coordinates as 0-1 ratios either, so maybe this isn’t a fair comparison. I saw a Reddit post that suggested overlaying a grid on the image and asking the model to return grid coordinates yielded better results. Perhaps performance could also improve with additional post-training techniques. Claude with computer use is somehow able to move the cursor to a pixel-perfect location on screen, which I assume is the result of specific post-training. Similar strategies would likely transfer well to determining bounding box coordinates. Gemini’s stronger performance also suggests that there are post-training steps From the Gemini docs : “For object detection, the Gemini model has been trained to provide these coordinates as relative widths or heights…” that can be taken to improve accuracy. I don’t understand the description accuracy variance Object size only explains half the variance in description accuracy: that is, the same object size would sometimes score perfectly, and other times completely incorrectly. For example, I was surprised at how well Gemini described the ‘couple kissing’: "In the bottom right corner of the image, a couple is kissing behind some large, bright green leaves. The woman has long brown hair and is wearing a red headscarf and top. The man has short brown curly hair and is wearing a bright red shirt. Just below the kissing couple, a person with short yellow hair and a yellow-green shirt is holding a knife." On the other hand, it completely fails to find the lifebuoy in the picture below, even though it’s roughly the same size as the previous object. "A child floats on an orange lifebuoy in a small pool near the bottom right of the image. The lifebuoy is round and appears inflated. Another child is jumping into the pool. A waiter in a black suit walks towards the pool, carrying a tray with drinks." The lifebuoy is actually in the top right, on the side of the lifeguard's tall chair. I don’t understand what causes the difference in ability. Future work If I had more time… Expand the dataset to several hundred objects. Test with more LLMs and also specialized vision models like SAM. Improve prompting strategies for bounding box prediction. Conclusion Wimmelbench convinced me that the big lab’s language models indeed cannot see as well as they read. I suspect part of it is due to object size, part due to post-training, and part due to tokenization and model architecture. I’d love to hear your thoughts — feel free to email me . Appendix: example results Claude Gemini GPT-4o Click to zoom in. Object Ground truth description Model description Grade GIoU Cactus A small, green cactus is potted in the window of a light gray building on the left side of the image, near the middle vertically. In the window next to it is an orange cat. Both windows are above teal awning. There appears to be a small green cactus in a pot being carried on a serving tray by one of the rabbit/bunny characters on the left side of the street. The bunny is one of two gray bunnies carrying food items on trays, likely heading towards the ‘EAT ME’ café in the scene. 0 -0.89 Elephant There is an elephant standing on two legs near the bottom-middle of the image. Its is holding a paintbrush and paint palette, wearing a purple top, and has an easel in front of it. The elephant is standing on the road. Mice are playing by its feet. Other animals are nearby. There is a large grey elephant character sitting in the center of the street scene. The elephant is wearing a purple velvet robe or jacket and appears to be painting on a canvas that’s set up on an easel. The elephant has distinctive large ears, a long trunk, and is shown in a sitting position while engaged in artistic activity. It appears to be one of the main focal points of the busy street scene, surrounded by various other animal characters. 2 -0.51 Click to zoom in. Object Ground truth description Model description Grade GIoU Cactus A small, green cactus is potted in the window of a light gray building on the left side of the image, near the middle vertically. In the window next to it is an orange cat. Both windows are above teal awning. A small, green cactus is located inside the first floor window of the grey building on the left side of the image. It is positioned on the window sill. 3 0.52 Elephant There is an elephant standing on two legs near the bottom-middle of the image. Its is holding a paintbrush and paint palette, wearing a purple top, and has an easel in front of it. The elephant is standing on the road. Mice are playing by its feet. Other animals are nearby. An elephant wearing a purple robe is painting on a canvas, standing on the street, slightly left of the image’s center. The elephant is facing left and holds a paintbrush in its trunk and a palette in its left hand. A wooden easel holds the canvas. Directly to the elephant’s right, a light gray cow seems to be giving a presentation while holding a microphone. 3 0.70 Click to zoom in. Object Ground truth description Model description Grade GIoU Cactus A small, green cactus is potted in the window of a light gray building on the left side of the image, near the middle vertically. In the window next to it is an orange cat. Both windows are above teal awning. The cactus is located in the bottom-right corner of the image. It is held by the giraffe and is green with several small red-orange flowers or spikes protruding from it. The giraffe is standing on the sidewalk next to a colorful group of animals. 0 -0.98 Elephant There is an elephant standing on two legs near the bottom-middle of the image. Its is holding a paintbrush and paint palette, wearing a purple top, and has an easel in front of it. The elephant is standing on the road. Mice are playing by its feet. Other animals are nearby. The elephant is located slightly left of center in the lower half of the image. It is wearing a purple robe and holding a paint palette and brush, standing next to an easel. The elephant appears to be engaging in painting. 3 0.31 Claude Gemini GPT-4o Object Ground truth description Model description Grade GIoU Man waving a white flag A man waving a white flag is in the top left of the image, by a broken a window. He is hung up on a light fixture by his jacket. To his right is a person falling, visible behind a broken window. Below him are people fighting each other. In the far right upper portion of the chaotic scene, there is a man waving a white flag or surrendering. He’s wearing what appears to be blue clothing and is positioned near the green paneled wall. He’s surrounded by the general mayhem of the room, with other figures nearby also in various states of distress or motion. 0 -0.94 Bowling ball A small black bowling ball is in the middle-right of the image. It is in the air, in between two men. The man on the right has punched the man on the left who is reeling backwards. The bowling ball looks like it came off left man’s hand. There is a black bowling ball visible in the chaotic scene, located in roughly the center-right portion of the image. It appears to be rolling or has been knocked loose during the mayhem, sitting on the wooden floor among the scattered people and overturned furniture. The bowling ball stands out as a small, round, black object amid the chaos of the cartoon scene. 0 -0.94 Object Ground truth description Model description Grade GIoU Man waving a white flag A man waving a white flag is in the top left of the image, by a broken a window. He is hung up on a light fixture by his jacket. To his right is a person falling, visible behind a broken window. Below him are people fighting each other. A man waving a white flag from which pieces of paper are falling is visible in the top left part of the image. He is wearing a blue suit, is seated on a short wall, and appears to be looking down at the chaotic scene below him. Behind him, one person climbs in through a broken window while another climbs out. The room has pale green walls with wood panelling. 1 0.04 Bowling ball A small black bowling ball is in the middle-right of the image. It is in the air, in between two men. The man on the right has punched the man on the left who is reeling backwards. The bowling ball looks like it came off left man’s hand. A bowling ball can be seen lying on the floor amidst the chaotic scene. It’s located slightly below the center-left portion of the image, amongst a group of people engaged in a brawl. Its color is predominantly dark gray or black. It is not in motion. It’s spatially close to a scattered pile of what appear to be pins, suggesting that it’s part of the chaotic activity in the depicted scene. 0 -0.99 Object Ground truth description Model description Grade GIoU Man waving a white flag A man waving a white flag is in the top left of the image, by a broken a window. He is hung up on a light fixture by his jacket. To his right is a person falling, visible behind a broken window. Below him are people fighting each other. The man waving a white flag is located in the bottom right portion of the image. He is wearing a white outfit, lying on the ground on his back, and holding a white flag up in the air. Nearby, there are people in animated poses, and the floor is wooden. 0 -0.98 Bowling ball A small black bowling ball is in the middle-right of the image. It is in the air, in between two men. The man on the right has punched the man on the left who is reeling backwards. The bowling ball looks like it came off left man’s hand. The bowling ball is black and located slightly to the right of the center of the image. It is on the floor in front of a group of people who appear to be crouching or dancing. The ball is near a man who is about to step on it, creating a sense of impending comedic chaos. 0 -0.85 | 2026-01-13T09:29:15 |
https://www.linkedin.com/signup/cold-join?session_redirect=%2Fservices%2Fproducts%2Ftencentglobal-tencent-effect-sdk%2F&trk=products_details_guest_nav-header-join | Sign Up | LinkedIn Make the most of your professional life Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T09:29:15 |
https://group.mantle.xyz/ko | Mantle: Blockchain for Banking & On-Chain Finance 홈 Mantle 혁신 핵심 요소 리소스 KO 금융을 위한 블록체인 암호화폐를 당신의 일상으로 자세히 알아보기 Mantle의 비전 토큰화된 기술로 구현되며 모두에게 열려 있는 금융이 자유롭고 효율적이며 접근 가능한 세상. 주요 사업 부문 혁신 핵심 요소 MNT MNT는 맨틀의 생태계를 구동하며 거버넌스, 스테이킹, 탈중앙화 경제 전반의 활성화를 위한 초석 역할을 합니다. Mantle Network 모듈형 설계와 아이겐레이어(EigenLayer) 및 아이겐DA(EigenDA)의 선도적인 도입으로 잘 알려진 이더리움 레이어 2는 맨틀의 다양한 제품과 애플리케이션의 근간을 이룹니다. mETH Protocol 수익을 극대화하는 유동성 ETH 스테이킹 및 리스테이킹 프로토콜. CEX, DeFi 앱, 그리고 머니마켓에서 담보로 널리 인정받고 있습니다. Function BTC를 Web3 경제로 연결하여 새로운 금융 기회를 여는 탈중앙화 비트코인 솔루션. Mantle Index Four 기관 등급의 수익률 상품으로, 최고의 암호화폐 자산 포트폴리오에 다양하게 노출되는 상품입니다. UR UR은 국경을 초월해 간편 결제와 오프램프를 하나로 제공하는 스마트머니 앱입니다. MantleX 인공지능(AI)을 활용하여 분산 시스템의 미래를 선도합니다. 전략적 제휴 파트너십 총 금고 $3,719,401,381 맨틀 금고는 맨틀 금융 생태계의 중심 역할을 하며 안정성을 확보하고 전략적 성장을 추진합니다. 트레저리 76.24 % MNT $2,835,858,268 8.97 % ETH, mETH & cmETH $333,637,972 7.33 % BTC $272,988,269 7 % Stables $260,627,009 금액은 미국 달러 기준입니다.13 Jan 2026, 07:19 UTC에 업데이트됨 에코펀드 촉진 자금 풀(Ecofund Catalyzed Capital Pool) $200,000,000 Mirana Ventures 전문가들의 지원을 받는 맨틀 에코펀드는 폴리체인(Polychain) 및 드래곤플라이(Dragonfly)와 같은 20개의 주요 VC를 통해 혁신적인 프로젝트를 지원하고 최고의 투자 기회를 확보함으로써 생태계 성장을 이끌고 있습니다. 자세히 알아보기 뉴스룸 스포트라이트 블로그 11 Jul, 2025 UR Early Beta Access: Now Live With Weekly $3,000 Lottery Prize Pool Ecosystem Mantle UR Users can now sign up for a UR account with limited and exclusive, by-invite-only, codes shared by selected participants of the UR Early program from July 11, 2025, 10AM UTC to Aug. 8, 10AM UTC. 자세히 10 Jul, 2025 Mantle Becomes Strategic Investor of Digital Asset Management Firm ReserveOne Ecosystem Mantle Proud to announce our strategic investment in newly-formed digital asset management firm ReserveOne, an institutionally-governed digital asset reserve anchored in a diverse treasury strategy including Bitcoin, Ethereum and Solana. 자세히 09 Jul, 2025 Letter to Token Holders Q3 2025 Mantle Network UR Q3 2025 onwards will be a transformative moment for Mantle and our role in the evolving global financial landscape. 자세히 18 Jun, 2025 Mantle Launches UR (Early Contributors' Access Live) Ecosystem UR Beta testing access now live for UR — a borderless smart money app that makes it easy to spend and off-ramp, all in one place. UR is powered by Mantle Network. 자세히 Mantle 거버넌스 트레저리 에코펀드 스카우트 프로그램 MNT 받기 MNT란 무엇인가 혁신 핵심 요소 Mantle Network mETH Protocol Function Mantle Index Four UR MantleX 리소스 블로그 이벤트 커리어 브랜드 자산 © Mantle 2026 . All rights reserved. 개인정보 보호정책 약관 | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/scalecomputing-hc3-virtualization-platform/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | SC//Fleet Manager | LinkedIn Skip to main content LinkedIn Scale Computing in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in SC//Fleet Manager Server Virtualization Software by Scale Computing See who's skilled in this Add as skill Learn more Report this product About We combined servers, storage, and virtualization into a single solution to make IT infrastructure easier for organizations of every size. Whether you have one IT administrator or hundreds, our award winning hyperconverged infrastructure eliminates complexity, lowers costs, and frees up management time. Using an appliance-based approach to virtualization, our Scale Computing Platform infrastructure solution is faster to deploy, easier to manage, and allows you to scale seamlessly as your organization grows. Even in an emergency with the failure of hardware components or entire appliances, Scale Computing infrastructure lets you keep critical apps – and your entire organization – up and running. This product is intended for System Administrator Information Technology Manager Chief Information Officer Director of Information Systems Network Specialist Network Administrator Media Products media viewer No more previous content Scale Computing HC3 Virtualization Platform HC3 brings together virtualization, servers, storage, and backup/disaster recovery into a single solution, eliminating the need for third-party components or licensing. The result is a highly efficient virtualization infrastructure that’s easy to use and effortless to maintain, producing substantial cost savings in both the short and long term. Scale Computing - Simplicity Engineered Scale Computing creates computing solutions that simplify IT operations by eliminating downtime and lowering IT costs. Take a look at how our innovative technology can make IT easier for you to manage. HC3 Success Story - L&B Realty Brenda Hartson gives a specific example of how the features and simplicity of Scale Computing's HC3 helped L&B avoid a disaster. No more next content Featured customers of SC//Fleet Manager Risas Dental and Braces Hospitals and Health Care 2,595 followers Holiday Inn Express Hospitality 96,389 followers Earl May Garden Centers Retail 569 followers MERIDA BIKES INTERNATIONAL Sporting Goods Manufacturing 17,166 followers Hood College Higher Education 17,711 followers Marc & Rose Hospitality 3,673 followers LiDestri Foods Food and Beverage Services 12,203 followers Soho House & Co Hospitality 390,378 followers Benchmark Computers and Electronics Manufacturing 105,382 followers Greenleaf Hospitality Group Hospitality 4,285 followers KIB Electronics Appliances, Electrical, and Electronics Manufacturing 269 followers Summit Steel and Manufacturing Machinery Manufacturing 873 followers Lindt & Sprüngli (Canada), Inc Retail 15,508 followers Blue Harbor Resort & Conference Center Hospitality 1,021 followers Genting Casinos UK Entertainment 10,429 followers Empire Airlines Aviation & Aerospace 9,650 followers Perry County Memorial Hospital Hospitals and Health Care 780 followers L&B Realty Advisors, LLP Investment Management 6,028 followers Friendly Hills Country Club Hospitality 189 followers Show more Show less Similar products Cloudflare Workers Cloudflare Workers Server Virtualization Software Cloud Virtual Machine (CVM) Cloud Virtual Machine (CVM) Server Virtualization Software Proxmox Virtual Environment Proxmox Virtual Environment Server Virtualization Software SC//Platform SC//Platform Server Virtualization Software BTS Sybelle Virtualization Platform BTS Sybelle Virtualization Platform Server Virtualization Software Oracle Virtualization Oracle Virtualization Server Virtualization Software Sign in to see more Show more Show less Scale Computing products SC//HyperCore SC//HyperCore SC//Platform SC//Platform Server Virtualization Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Ftencentglobal-tencent-cloud-instant-messaging-im%3FviewConnections%3Dtrue&trk=products_details_guest_face-pile-cta | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
https://lnkd.in/gSFPMRsq?trk=organization_guest_main-feed-card-text | LinkedIn LinkedIn This link will take you to a page that’s not on LinkedIn Because this is an external link, we’re unable to verify it for safety. https://open.spotify.com/show/3yc5YVwkZZXgWPQgae1pGp?si=44421b03a3894e2d This experience is optimized for Chrome, Edge, and Safari Have questions? Learn more | 2026-01-13T09:29:15 |
http://fossmarks.org/about/ | How to Use The Guide How to Use The Guide Home About The Guide Contributors Seek Advice How to Use The Guide Your Guide to Trademarks for your Free or Open Source Software Project What is this all about? This site serves as your guide from the basics of what a trademark is, to tips on choosing a name for your project, to registering a name, and what to do if someone uses your name without permission. This resource is design to be useful to both those just starting out, as well as more mature projects. Trademarks and Free & Open Source Software (or “FOSS”) are not incompatible; instead, trademarks are legal tools strongly aligned with FOSS principles. Why do we use the term FOSS? Good question, read more about it. Foundation in Trademarks A trademark is an assurance that the recipient of the goods or services is receiving a product of known source and qualities. Controlling how a FOSS project trademark is used protects the community and its software, by preventing use of the trademark in ways that are harmful to the reputation of the community or the software. This isn’t a theoretical problem, it happens fairly often . For example, it may be the case that confusion between two products with similar or identical trademarks isn’t intentional wrongdoing, but rather a matter of differing views on a project’s direction, sometimes resulting in a fork. But if both forks use the same trademark, users won’t be able to distinguish them. How to Use this Guide Simple, navigate over to The Guide and imagine you’ve created a project and are hoping to attract contributors and followers. If you’ve already done that, great, you can skip the imagining part. You’ll want to choose a name or logo that sets your project apart from other projects. Ideally, you want users to know they are using your project when they see your name or logo, and not some other software or another version of your software. Let’s get started, head over to The Guide . All content is licensed under the Creative Commons Attribution 4.0 International License . Thank you to the FSFE for hosting this site. | 2026-01-13T09:29:15 |
https://lnkd.in/gZMHEXyq?trk=organization_guest_main-feed-card-text | LinkedIn LinkedIn This link will take you to a page that’s not on LinkedIn Because this is an external link, we’re unable to verify it for safety. https://open.spotify.com/show/0SM3Mq7Y25BtpHIBMntH5S?si=39bc7ad7d2194cba This experience is optimized for Chrome, Edge, and Safari Have questions? Learn more | 2026-01-13T09:29:15 |
https://www.linkedin.com/products/categories/ddos-protection-software?trk=organization_guest_products_modal_category_link | Best DDoS Protection Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Chief Information Security Officer (11) Chief Information Officer (7) Head of Information Technology (6) Cyber Security Specialist (5) Chief Technology Officer (3) See all products Find top products in DDoS Protection Software category Software used to stop or prevent denial-of-service (DDoS) attacks, attacks on websites that use a flood of hijacked nodes to interrupt services. - Identify DDoS attacks with IP monitoring and comparison of other signatures - Redirect illegitimate traffic directed at websites and resources - Use traffic load benchmarks to detect bandwidth abnormalities and maintain baselines - Prevent downtime, sudden service failure, and delayed performance with filtering, scrubbing, and other traffic management techniques 64 results Cloudflare DDoS Protection DDoS Protection Software by Cloudflare Comprehensive DDoS Protection Built for anything connected to the Internet Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised. Cloudflare’s 51 Tbps network blocks an average of 72 billion threats per day, including some of the largest DDoS attacks in history. View product Cloudflare Spectrum DDoS Protection Software by Cloudflare Cloudflare Spectrum increases TCP and UDP security and prevents DDoS attacks for gaming, mail, SSH, and other services. View product Akamai Prolexic Routed DDoS Protection Software by Akamai Technologies Prolexic solutions provide fully managed DDoS protection for your applications, data centers, and network infrastructure. View product OVHcloud Anti-DDoS Protection DDoS Protection Software by OVHcloud Mitigate your risk of DDoS attacks and keep your services available at all times. Free with every OVH service. Learn more. View product Kona DDoS Defender DDoS Protection Software by Akamai Technologies Always-on, managed DDoS protection service to stop DDoS for critical websites and web applications. HTTP and HTTPS. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Kaspersky DDoS Protection DDoS Protection Software by Kaspersky Distributed Denial of Service (DDoS) can cause financial costs for your business. Keep your service protected with Kaspersky DDoS-Protection! View product Arbor Cloud DDoS Protection DDoS Protection Software by NETSCOUT Arbor Cloud combines on-premise DDoS defense with cloud-based traffic scrubbing services that are tightly integrated via an automated cloud signal. This multi-layered, adaptive DDoS protection approach is a proven industry best practice and is the only way to mitigate today's full spectrum of DDoS threats for both Service Providers and Enterprises, all from a single cloud DDoS protection provider. View product Attack Mitigation System DDoS Protection Software by Radware Continuously adaptive real-time DDoS services for the most sophisticated web security threats through best-in-class cloud WAF and DDoS protection technologies. View product A10 Defend - Intelligent & Automated DDoS Protection DDoS Protection Software by A10 Networks, Inc A10 Defend provides a holistic DDoS protection solution that is scalable, economical, precise, and intelligent to help customers ensure optimal user and subscriber experiences. View product Arbor Edge Defense DDoS Protection Software by NETSCOUT Arbor Edge Defense is an inline security appliance deployed at the network perimeter that can automatically detect and block inbound threats and outbound malicious communication using highly scalable, stateless technology and unique, global threat intelligence. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:15 |
https://www.linkedin.com/company/npm-inc-?trk=products_details_guest_organization_image | npm, Inc. | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free npm, Inc. Software Development Oakland, CA 11,912 followers npm operates the world’s largest software registry. More than 150,000 companies use npm to build amazing things. Follow Discover all 18 employees Report this company About us Over 10 million software developers worldwide use npm, Inc.’s open source software and web registry to discover, share, and reuse packages of code. Our users download over 800,000 packages more than 7 billion times per week, and registry downloads have grown by more than 16x in the last two years. npm’s paid products and services offer teams and companies ways to organize, share, and secure code, integrate npm with testing and deployment tools, and bring code reuse into the enterprise. More than 150,000 companies, including BBC, Coinbase, eBay, Electronic Arts, Nvidia, and Slack rely on npm to reduce friction and build amazing things. Website http://npmjs.com External link for npm, Inc. Industry Software Development Company size 11-50 employees Headquarters Oakland, CA Type Privately Held Founded 2014 Locations Primary 1999 Harrison St Ste 1150 Oakland, CA 94612, US Get directions Employees at npm, Inc. Elad Ben Shmuel Md Raihan Patrick Oliver Tiavina MIchael Ralainirina See all employees Affiliated pages GitHub Software Development San Francisco, CA Similar pages GitHub Software Development San Francisco, CA Node.js Software Development San Francisco, CA Aikido Security Software Development React Software Development Menlo Park, California GitLab IT Services and IT Consulting San Francisco, California Microsoft Software Development Redmond, Washington Netlify Software Development San Francisco, California NPM US (New Project Media) Market Research Princeton, New Jersey NPM Recruitment Staffing and Recruiting Kandivali, 400101 ReactJS E-Learning Providers Show more similar pages Show fewer similar pages Browse jobs Cyber Security Specialist jobs 20,744 open jobs Developer jobs 258,935 open jobs Engineer jobs 555,845 open jobs Officer jobs 1,191,868 open jobs Cognos Developer jobs 1,399 open jobs Software Engineer jobs 300,699 open jobs Analyst jobs 694,057 open jobs Full Stack Engineer jobs 38,546 open jobs Legal Assistant jobs 23,617 open jobs Manager jobs 1,880,925 open jobs Intern jobs 71,196 open jobs Solutions Architect jobs 100,488 open jobs Assistant Professor jobs 13,039 open jobs Solutions Engineer jobs 92,218 open jobs Security Manager jobs 116,433 open jobs Quantitative Analyst jobs 19,570 open jobs Scientist jobs 48,969 open jobs Network Engineer jobs 173,828 open jobs Quantitative Developer jobs 11,546 open jobs Project Lead Developer jobs 118,123 open jobs Show more jobs like this Show fewer jobs like this Funding npm, Inc. 4 total rounds Last Round Secondary market Jul 11, 2019 External Crunchbase Link for last round of funding See more info on crunchbase More searches More searches Web Administrator jobs Web Editor jobs System Developer jobs Support Technician jobs Web Designer jobs Visual Designer jobs Developer jobs User Experience Designer jobs Product Designer jobs Designer jobs Engineer jobs Software Engineer jobs Coder jobs Full Stack Engineer jobs SQL Developer jobs Javascript Developer jobs Web Developer jobs Virtual Assistant jobs Firmware Engineer jobs C Developer jobs Research Analyst jobs Analyst jobs Scientist jobs Frontend Developer jobs Intern jobs Solutions Architect jobs Principal Program Manager jobs Technical Program Manager jobs Program Manager jobs Solutions Engineer jobs Mobile Engineer jobs Python Developer jobs Contract Software Engineer jobs Senior Product Manager jobs Student Software Engineer jobs Plant Director jobs Product Manager jobs Immigration Attorney jobs Process Technician jobs Software Engineering Manager jobs Maintenance Supervisor jobs Junior Software Engineer jobs Safety Manager jobs Maintenance Manager jobs Plant Manager jobs Manufacturing Engineer jobs Student jobs Technician jobs Supervisor jobs Recruiter jobs Marketing Manager jobs Director jobs Senior Network Engineer jobs Electrical Technician jobs Junior Web Developer jobs Foreperson jobs Electrician jobs Software Quality Assurance Engineer jobs Software Tester jobs Security Software Engineer jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at npm, Inc. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:29:15 |
https://lnkd.in/gjmpi4kA?trk=organization_guest_main-feed-card-text | LinkedIn LinkedIn This link will take you to a page that’s not on LinkedIn Because this is an external link, we’re unable to verify it for safety. https://dkkrb.share-ap1.hsforms.com/2P78fX1gCQb-5UONcluf4TA This experience is optimized for Chrome, Edge, and Safari Have questions? Learn more | 2026-01-13T09:29:15 |
https://lnkd.in/gqAWDdxR?trk=organization_guest_main-feed-card-text | LinkedIn LinkedIn This link will take you to a page that’s not on LinkedIn Because this is an external link, we’re unable to verify it for safety. https://youtube.com/playlist?list=PLwzJL0RZdB0A6-NT_FeMKz5f-ehjzceWg&si=-fZ3TySV6mJwHs0D This experience is optimized for Chrome, Edge, and Safari Have questions? Learn more | 2026-01-13T09:29:15 |
https://telegram.org/dl?tme=c09576fdc7aaabd496_7835138110432360673 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebK Telegram WebA Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:15 |
http://fossmarks.org/contributors/ | Contributors Contributors Home About The Guide Contributors Seek Advice Contributors Those who made this project a reality Pamela S. Chestek Contributor, Editor Pamela is the principal of Chestek Legal in Raleigh, North Carolina, USA. She counsels creative communities on open source, brand, marketing and copyright matters. Prior to returning to private practice, she held in-house positions at footwear, apparel, and high technology companies and was an adjunct law professor teaching a course on trademark law and unfair competition. She is a frequent author of scholarly articles, and her blog, Property, Intangible, analyzes current intellectual property case law. Pam is admitted to practice in Connecticut, the District of Columbia, Massachusetts, New York and North Carolina, and has been certified by the North Carolina Board of Legal Specialization in Trademark Law. Weston Davis Contributor, Editor, Web Designer Based in Raleigh, North Carolina, USA, Weston is passionate about building companies around free and open source technology, having held various roles for numerous open source software companies through his career. After receiving a degree in business from Tulane University, Weston obtained his J.D. from Campbell University where he concentrated his studies on international law and policy, specifically regarding intellectual property. A constant tinkerer, Weston is a self-taught amateur developer thanks to free and open source software projects. Weston sees FOSSmarks as a way to give back to the free and open source software communities in return for his free learnings. Follow Weston on Twitter @westonkdavis. Anthonia Ghalamkarizadeh Contributor Anthonia is a passionate IP litigator based in the Hamburg office of Hogan Lovells International LLP . Anthonia protects her clients’ brands and products against all forms of online and offline misuse and advises on all aspects of trademark law and unfair competition. Her client base spans software and online services, consumer electronics and entertainment, and beauty care and healthcare. A focus of Anthonia’s work is on the integrated online enforcement of her client’s IP rights, and she works with colleagues in many jurisdictions daily. Anthonia regularly publishes on current trademark, online and unfair competition topics. In her articles, she recently explored the legal implications of adblocking and effective protection against online scams. She is a member of the Marques “Class 46” team of trademark lawyers and writes for her firm’s LimeGreen IP knowledge site and for external legal publications. Anthonia also is an active member of the European Legal Network of the Free Software Foundation Europe. Anthonia studied law with a strong international focus. She obtained her Magister Juris degree with distinction from the University of Oxford, where she was also awarded the John Morris Prize in Conflicts of Law. Rafal Malujda Contributor Rafal Malujda, LL.M., attorney-at-law, involved in open source community projects in Poland and advising IT companies on the legal aspects of their business within the European Community, especially in the context of IP protection, floss licensing and compliance. His second specialization is shipping law, where he deals also with IT systems onboard. Rafal studied law in Poland and Germany, where he did his LL.M. course on international business law and international company management. Additionally he participated in Cambridge Diploma Course in English and EU law. Rafal is a member of open source and IT organizations, also active in European Legal Network of the Free Software Foundation Europe. Please visit www.malujda.pl for more information. All content is licensed under the Creative Commons Attribution 4.0 International License . Thank you to the FSFE for hosting this site. | 2026-01-13T09:29:15 |
https://t.me/s/oasisprotocolfoundation | Oasis - Announcements – Telegram Oasis - Announcements @oasisprotocolfoundation 3.57K subscribers 418 photos 30 videos 7 files 1.5K links Oasis is a privacy-first, proof-of-stake, decentralized network. A network designed to give users back control and ownership of their data, while supporting new applications in open finance and open data. Discussion @oasisprotocolcommunity Download Telegram About Blog Apps Platform Join Oasis - Announcements 3.57K subscribers Oasis - Announcements 🎉 Afternoon TEE Party Recap — Devconnect BA ☕️ 🇦🇷 Another Afternoon TEE Party, another full house — the Oasis community showed up strong once again! 🔹 Oasis's Matej opened with a sharp, myth-busting breakdown of recent "TEE exploits”, and why secure enclaves remain essential for building trustworthy, verifiable agents. 🔹 iExec’s Rick spotlighted why real-world adoption depends on confidentiality — a mission Oasis has been pushing forward from the start. 🔹 Our panel dug into why agents must be trustless: “You want the agent fully powered by your data so it works at its best — but you don’t want that data leaking out to everyone else.” The room was full of builders, privacy geeks, and nonstop conversations… plus an Oasis poker night with special prizes 🎁 💙 Huge thanks to everyone who showed up — on to the next! 🚀 454 views 05:12 Oasis - Announcements ☕️ The Afternoon TEE Party recording is live! 🇦🇷 🔥 We covered everything from the truth behind recent “TEE exploits,” to why trustless agents and real-world privacy matter. The conversations were packed with insights from Oasis, iExec, and an incredible panel of privacy builders. If you couldn’t make it, no worries — you can watch the entire session here 👇 https://www.youtube.com/watch?v=OLMWfG-kyyg 470 views 06:25 Oasis - Announcements 🎉 Oasis Track Winners — ETHGlobal Buenos Aires 🇦🇷 After an incredible weekend of building at ETHGlobal BA, submissions for the Oasis track are in — and the results are here! Throughout the hackathon, our team powered builders working with trustless agents, confidential compute, cross-chain logic, Sapphire, ROFL, and ERC-8004 workflows. The energy at ETHGlobal BA was fantastic, and we’re proud of every team that took on the challenge. Oasis Track Winners 🥇 Void Wallet 🥈 Assura 🥉 P.A.T 4️⃣ AgentCred 5️⃣ Linda Huge congratulations to all the winners and everyone who built with Oasis this weekend. The creativity and momentum were inspiring — we can’t wait to share more about each project soon. Stay tuned for deep dives and highlights from the winning teams! 🚀 💙 605 views 04:22 Oasis - Announcements 📢 New Article: x402 — The Internet-Native Payment Standard 💰 Micropayments are finally web-native. Learn about x402, the standard making per-request charging possible, and how it enables AI Agents to transact autonomously. Crucially, see how Oasis is adding TRUST to this new economy by integrating x402 with ERC-8004 and ROFL TEEs for verifiable, confidential execution! Don't miss this deep dive! 👇 https://oasis.net/blog/x402-https-internet-native-payments oasis.net x402: The Internet-Native Payment Standard Exploring x402, the protocol unlocking micropayments and fueling the rise of an agentic economy. 665 views 09:18 Oasis - Announcements Our annual Community Town Hall is coming up soon, and we want to hear from YOU! Got questions about the Oasis ? Curious about what's next? Want to share feedback or ideas? Now's your chance to have them answered directly by the team. Submit your questions anonymously using this form: https://forms.gle/cdmK84BM1EPwx85e8 📌 Your email won't be collected – it's completely anonymous ⏰ We'll answer as many questions as possible during the Town Hall 💬 All topics welcome – tech, community, roadmap, partnerships, you name it Drop your questions and let's make this Town Hall count! See you there 🌹 Google Docs Community Town Hall '25 We're hosting our annual Community Town Hall soon ... leave your questions here, we'll try to answer them all during our town hall Form is anonymous, emails are not collected yay 🎉 401 views 09:20 Oasis - Announcements Great news everyone! I'm excited to share that the Oasis Protocol Foundation has launched a new strategic investment arm, evolving from a grants-only approach into a long-term capital strategy to support builders in Web3. 💡 First investment: SemiLiquid SemiLiquid is building custody-native credit infrastructure for real-world assets (RWAs) and is integrating Oasis Sapphire’s confidential compute stack to enable secure, privacy-preserving on-chain finance. 🔐 Why this matters RWAs are rapidly growing across DeFi and institutional markets Confidentiality and compliance are no longer optional Oasis is doubling down on privacy-first, compute-intensive infrastructure 🧠 SemiLiquid leverages Liquefaction, a protocol developed by Cornell Tech on Sapphire, to manage trade execution, policy enforcement, and breach monitoring without exposing sensitive financial data. 🤝 They’ve already completed a successful pilot with Franklin Templeton, Zodia Custody, and Ava Labs, demonstrating trustless, decentralized credit for tokenized assets while maintaining custody assurances. Today, Oasis is ensuring the future of on-chain finance is confidential and safe. Mark Kalin, Director of Operations, Oasis Protocol Foundation This marks an important step in Oasis’s evolution as a privacy-first foundation supporting real-world adoption. Find out all the details below 🔗 https://cryptonews.com/news/oasis-protocol-makes-first-strategic-investment-in-semiliquid-to-foster-rwa-infrastructure/ Cryptonews Oasis Protocol Makes First Strategic Investment in SemiLiquid Oasis Protocol Foundation has made its first strategic investment SemiLiquid, aiming to advance scalable RWA infrastructure. 325 views 16:03 Oasis - Announcements 🌹 Oasis November '25 – Month in Review is LIVE! The privacy wave keeps building and November was MASSIVE! 🔥 We're talking breakthrough tech, worldwide dev action, and upgrades that are leveling up Web3! 👀 🔹 ERC-8004 + Trustless Agents Deep Dive: How ERC-8004 enables autonomous, verifiable agents — a game-changer for privacy-first compute. 🤖 📘 🔹 ROFL Frontend Hosting SHIPPED: Full-stack confidential apps are here. Frontend + backend confidentiality, end-to-end verifiability. ⚙️ 🛠 🔹 DevConnect Buenos Aires TAKEOVER: Panels, workshops, meetups — massive Oasis presence all week. The privacy ecosystem showed up strong. 🇦🇷 ⚡️ 🔹 ETHGlobal Buenos Aires: 27 teams built on Oasis, 5 winners took home prizes. Builders chose privacy. 💡 🏆 🔹 Taiwan's FIRST RWA Hackathon: A milestone for real-world assets + confidentiality. Taiwan kicked off a new wave of privacy adoption. 🇹🇼 🎉 🔹 New Content: "Meet the Team" sessions, "Privacy Now" podcasts, and Byte-Sized Engineering updates. 🎥 ✨ 🔹 Network Upgrades: Sapphire and Cipher boosted, Oasis Core 25.8 rolled out with key improvements. 🔧 🚀 🔹 Oasis Turns 5! Five years building the privacy-first foundation for Web3 — just getting started. 🌹 🎉 🔥 Privacy isn't an afterthought. It's the engine of what's next. 🎥 Watch Now: https://youtu.be/htmnqY4DApA New month. New wins. Same mission. Let's build a better Web3 — private by design. 😎 ✨ YouTube Oasis November '25 Month in Review Oasis is a privacy-first, scalable Layer 1 network that makes confidential computing easy. Since 2018, the Oasis Network has been transforming user privacy, data protection, and cross-chain composability across decentralized finance, artificial intelligence… 348 views 16:43 Oasis - Announcements 🎄 Xmas with Oasis Is LIVE ! 🎄 It’s time to spread the gift of privacy across Web3. Complete quests on Zealy to earn 100,000 ROSE prizes! From memes to threads to AI art… creativity reigns! 📅 Runs: Dec 14 → Dec 24 🏆 Winners: Dec 26 🎁 Instructions: https://oasisrose.garden/xmas.html Join the fun and power up our privacy tree! Tag your posts with @OasisProtocol + $ROSE and climb the leaderboard. Ready. Set. Snowfall of Privacy. ❄️ 🌹 342 views 12:47 Oasis - Announcements 🎄 Daily entries have reset! 🎄 Another day, another chance to climb the leaderboard in Xmas with Oasis 🏆 🎅 Submit new memes, threads, AI art, and creations to earn more points and compete for 100,000 ROSE. 🌹 Tag @OasisProtocol + $ROSE and let the privacy snowfall continue ❄️ 👉 https://oasisrose.garden/xmas.html 415 views 09:43 Oasis - Announcements 🎄 OASIS XMAS ROFFLE IS LIVE! 🎄 Santa went onchain this year, and he's bringing up to 1,000,000 ROSE in prizes! 🎟 How to Enter: Tickets: 250 ROSE each (pay with ROSE or USDC/USDT on Base) Max 10 tickets per wallet Only 3,600 tickets available—first come, first served! 🎁 Prizes: 10 lucky winners selected randomly 1st place takes home 50% of the prize pool Winners paid automatically via Sapphire smart contract 📆 Raffle closes on Dec 23 (or when tickets sell out) 🔗 Get your tickets now: https://roffle.oasis.io 361 views edited 02:57 Oasis - Announcements 🗓 Mark your calendars: the Oasis Townhall returns! ⚡️ We’ll cover what we shipped in 2025, what’s coming in 2026, updates on new products, strategic direction, and a community Q&A. 📺 Live on X & Youtube at 4pm UTC, December 18th. https://www.youtube.com/live/mBud4M95jRo?si=g8VUKgcPBtZ5kEki YouTube Oasis End of Year Community Town Hall - 2025 📱 Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. 369 views 05:22 Oasis - Announcements 🎄 ✨ Holiday Announcement ✨ 🎄 As we head into the holiday season, please note that all weekly community activities will be paused from December 22nd to January 4th, including: - Weekly Polls - Trivia Nights - Poker Nights - Community One Leaderboard All activities will resume after the holiday break. Thank you for being an amazing community throughout the year 💙 We wish everyone a Merry Christmas 🎄 and Happy New Year 🎉 Enjoy the holidays, and we’ll see you in 2026! 🌹 491 views 09:00 Oasis - Announcements 🚀 Oasis × Carrot: Verifiable Compute for Onchain Prop Trading 🥕 Oasians, we’re teaming up with Carrot Funding to bring ROFL to onchain prop trading — replacing black-box systems with cryptographically verifiable compute 🔐 ⚙️ 💡 Why this matters 🔹 ROFL ensures every computation is executed as written and verified onchain 🔹 Parallel verification → every AWS computation will be verified by ROFL 🔹 Fairer outcomes for traders, stronger guarantees for capital providers This is another step toward eliminating trust assumptions in the broader DeFi ecosystem — powered by Oasis ROFL 🌐 ✨ 📖 Read the full details here: 🔗 https://x.com/OasisProtocol/status/2001608407208378697 463 views 03:42 Oasis - Announcements ⏰ Last Call! Oasis Xmas Roffle Closing Soon 🎄 The Oasis Xmas Roffle is ending in 🔟 hours! 🔥 Current prize pool: 270,000 ROSE — and still growing If you haven’t grabbed your tickets yet, now’s the time 👀 📋 Roffle Details 250 ROSE per ticket (pay with ROSE or USDC/USDT on Base) Max 10 tickets per wallet Only 3,600 tickets total — first come, first served 10 lucky winners selected randomly 1st place takes home 50% of the prize pool Winners paid automatically via Sapphire smart contract 👉 Don’t miss out: https://roffle.oasis.io 🎅 Santa’s about to close the gates 🚪 Xmas Roffle Xmas Roffle - Blockchain Holiday Raffle Join the Xmas Roffle - A festive blockchain raffle powered by Oasis Network. Participate and win amazing prizes this holiday season! 441 views edited 12:28 Oasis - Announcements 🎄 ✨ Xmas with Oasis — Winners Announcement! 🎉 ✨ A huge thank you to everyone who joined our Xmas with Oasis campaign, and filled the season with creativity, joy, and festive energy! From insightful X threads to hilarious memes and stunning AI art, your contributions made this holiday celebration truly magical. 🌟 🎁 Top 10 Winners (Discord handle): 🥇 pacha912 🥈 okeygalileo 🥉 fossabyte 4️⃣ jknhiggins 5️⃣ subhan123. 6️⃣ einstein4017 7️⃣ junayed200369 8️⃣ waleedslf 9️⃣ elonvictor 🔟 tiimisgod 🏆 Best in Category Awards: 🤡 Best Meme: tiimisgod 🎨 Best AI Art: fossabyte 🧵 Best X Thread: shreyansh0358 🎊 Congratulations to all our amazing winners! Your creativity and holiday spirit truly shone through, and we can't wait to see what you create next! Thank you all for bringing the holiday spirit, creativity, and positive energy into the Oasis community. The fun doesn't stop here! We've got even more amazing events planned for the new year. Stay tuned, stay private, and happy holidays! 🎅 💫 483 views 14:56 Oasis - Announcements 🚀 ROSE Wallet is Now on Google Play! 📱 Exciting news, Oasians! Our mobile wallet app is now live on Google Play. You can now manage your Oasis funds anytime, anywhere — right at your fingertips. 📲 Get it here: https://play.google.com/store/apps/details?id=net.oasis.wallet 🎉 Manage your funds, send ROSE, and interact with the Oasis ecosystem — now easier than ever! Google Play ROSE Wallet - Apps on Google Play Official non-custodial wallet for Oasis 83 views 08:20 | 2026-01-13T09:29:15 |
https://jobs.flashbots.net/jobs | Jobs Flashbots Writings Docs MEV-Boost Forum Join us dark mode Join Flashbots Join us to help solve hard problems that have asymmetric impact and strike at the core of crypto. Current job openings © 2026 Flashbots, Ltd | 2026-01-13T09:29:15 |
https://jobs.flashbots.net/_next/static/css/4a55a9a0010e827c.css | Jobs Flashbots Writings Docs MEV-Boost Forum Join us dark mode Join Flashbots Join us to help solve hard problems that have asymmetric impact and strike at the core of crypto. Current job openings © 2026 Flashbots, Ltd | 2026-01-13T09:29:15 |
https://telegram.org/dl?tme=d775ce9c2c48367d6b_11074537504454110296 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebK Telegram WebA Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:15 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fcategories%2Fweb-application-firewalls&fromSignIn=true&trk=products_seo_search_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:15 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.