zalando-howto-open-source - Open Source guidance from Zalando, Europe's largest online fashion platform

  •        84

A guide to releasing an open-source project at Zalando, Europe's largest online fashion platform. Please feel free to use this as a template for your own organization's open source planning, policymaking, and development efforts. If there's a topic we've missed, or if you have any suggestions for making this better, let us know via our Issues tracker.We're really grateful to Software Lead Weekly, cron.weekly, Chris Aniszczyk (TODO Group), the folks at Datio Engineering, Thomas Lockney of Nike, Jamie Allen at Starbucks, Richard Seroter at Pivotal, Peter Zaitsev at Percona, Jonathan Lipps at Sauce Labs, and others for spreading the word about this doc.

https://zalando.github.io/
https://github.com/zalando/zalando-howto-open-source

Tags
Implementation
License
Platform

   




Related Projects

Restful API Guidelines - A model set of guidelines for RESTful APIs, created by Zalando

  •    Javascript

Great RESTful APIs look like they were designed by a single team. This promotes API adoption, reduces friction, and enables clients to use them properly. To build APIs that meet this standard, and to answer many common questions encountered along the way of RESTful API development, the Zalando Tech team has created this comprehensive set of guidelines. We have shared it with you to inspire additional discussion and refinement within and among your teams, and contribute our learnings and suggestions to the tech community at large.

awesome-leading-and-managing - Awesome List of resources on leading people and being a manager

  •    

Since 2013-ish, Joe Goldberg, who created the original document inspiring this list, read a crap-ton of books and articles about "leadership" and "management" and took notes along the way. He shared it with friends who were transitioning to management roles and eventually decided to open-source it. Here you'll find Joe's still-public document, which provides meatier summaries of the articles you'll find listed here as well as lots of supplementary notes. In summer 2017 Lauri Apple found out about Joe's docs via Software Lead Weekly and asked Joe about posting the contents to GitHub. He gave the greenlight. Lauri changed up the format (very brief blurbs), turned the doc into an Awesome List, and has continued adding new entries ever since. Helping out with the initial upload were a team of Lauri's former colleagues at Zalando. These days the list receives contributions from people around the world.

fashion-mnist - A MNIST-like fashion product database. Benchmark :point_right:

  •    Python

Fashion-MNIST is a dataset of Zalando's article images—consisting of a training set of 60,000 examples and a test set of 10,000 examples. Each example is a 28x28 grayscale image, associated with a label from 10 classes. We intend Fashion-MNIST to serve as a direct drop-in replacement for the original MNIST dataset for benchmarking machine learning algorithms. It shares the same image size and structure of training and testing splits.

feedmereadmes - Free README editing+feedback to make your open-source projects grow

  •    

Go here for relevant articles, talks, and projects that we find inspiring. Add your own favorites via pull request. Even if you don't agree with Preston-Warner, you can still make your READMEs user-friendlier. Feedmereadmes is here to help. We define "user" to include non-developers and aim to tell compelling stories. "[C]ode isn't self-documenting" is one of our mantras, as per Mike Jang's 2015 OSCON talk offering Ten Steps to Better READMEs.

standard-readme - Standard Readme Style

  •    Shell

Standard Readme is designed for open source libraries. Although it’s historically made for Node and npm projects, it also applies to libraries in other languages and package managers. Standard Readme started with the issue originally posed by @maxogden over at feross/standard in this issue, about whether or not a tool to standardize readmes would be useful. A lot of that discussion ended up in zcei's standard-readme repository. While working on maintaining the IPFS repositories, I needed a way to standardize Readmes across that organization. This specification started as a result of that.


readme-template - README.md template for your open-source project

  •    

Short blurb about what your product does. One to two paragraph statement about your product and what it does.

readme-best-practices - Best practices for writing a README for your open source project

  •    

One of the most crucial things in your open source project is the README.md file. This repository has a ready-to-copy-paste template you can use for all your projects. The code above fetches the README-default.md file from this repository and renames it to README.md.

flair - A very simple framework for state-of-the-art NLP

  •    Python

A very simple framework for state-of-the-art NLP. Developed by Zalando Research. A powerful syntactic-semantic tagger / classifier. Flair allows you to apply our state-of-the-art models for named entity recognition (NER), part-of-speech tagging (PoS), frame sense disambiguation, chunking and classification to your text.

balanced-employee-ip-agreement - GitHub's employee IP agreement, open sourced and reusable

  •    

BEIPA takes a balanced approach to assigning control of intellectual property (IP) created by an employee. The employee maintains control unless they created the IP in their employee capacity and the IP relates to an existing or prospective company product or service, or was developed for use by the company, or was developed or promoted with existing company IP or with the company's endorsement. A company using BEIPA doesn't try to claim control of an employee's free time knowledge production, nor does it try to extend company control past the period of employment. Think of BEIPA as a commitment to employee autonomy and "work-life balance" – for the mind.BEIPA was started as a reusable version of GitHub's employee IP agreement. Your company can use BEIPA too, and modify it as needed. If you'd like to help improve BEIPA for everyone, file an issue or make a pull request. While aiming to maintain the same "balanced" policy, we're keen to see feedback and suggestions for improving BEIPA and associated documentation. Please read our contributing guidelines and instructions.

webpack-training-project - A training project for learning Webpack optimizations

  •    Javascript

A month ago, a popular open-source hosting company decided to build a new extra-light version of its main product – a site with all open-source projects it hosts. They planned that people will use this site on devices with a poor network. They called this product LitHub. As soon as LitHub started, the company realized that all developers are busy on different projects. Somehow, they managed to find a developer who agreed to create this product in their overtime. But two days ago the developer switched the department, and the company decided to hire you to finish the work.

readme-checklist - A checklist for writing READMEs

  •    

checklist.md is a checklist to help you write a README file that helps readers feel confident about your project. If you write a README by following the checklist, then your readers may more easily identify, evaluate, use, and engage with your project. Unlike README templates, this checklist helps you write the most important things first, not only what appears first in the file. You can use the checklist for both closed- and open-source projects. For more about how this checklist was created and its use, see the talk I gave at Write the Docs NA 2016, Write the Readable README.

contributing-template - Template for writing your own contributing guide

  •    

A template for writing your own contributing guide. Contributing guides are helpful documents that communicate how people can contribute to your open source project. This template is meant to be a checklist to make sure you haven’t missed anything, rather than offering guidance on philosophy or approach. Your final guidelines may differ depending on your project and needs.

Android-FloatingTutorialActivity - A light-weight, easy-to-implement, and easy-to-look-at way to do a tutorial pager or dialog on Android

  •    Kotlin

The goal of this library isn't to confine you to certain UI styles or guidelines that I have made. The goal here is to provide you with a framework that you can build off of yourself. The content of these tutorial pages can be anything you want. That said, I have provided a few examples here, of UIs that have worked well for me and that I think provide a pretty great experience. Note: the library itself is in Kotlin, which is now native to Android. I have created sample applications in both Kotlin and Java. The samples are functionally equivalent. If you would like to see the usage section of this README in Java please head to the Java-flavored README.

The Linux Bootdisk-HOWTO

  •    

The Bootdisk-HOWTO describes how to design and build your own boot/root diskettes for Linux. These disks could be used as rescue disks or to test new system components.

doc-base - Tools for the PHP documentation

  •    PHP

This directory contains source files and a setup for converting PHP's XML documentation into presentation formats like HTML and RTF. You should not have to bother with this unless you are writing documentation yourself, or if you simply are curious about how the XML stuff works. If you are interested in information about how to set up the tools needed, how to work with Git and DocBook on Linux or Windows, or what conventions you should follow when writing phpdoc files, please refer to the PHP Documentation HOWTO.

clarity - UX guidelines, HTML/CSS framework, and Angular components working together to craft exceptional experiences

  •    TypeScript

Project Clarity is an open source design system that brings together UX guidelines, an HTML/CSS framework, and Angular components. This repository includes everything you need to build, customize, test, and deploy Clarity. For complete documentation, visit the Clarity website.The easiest way to run a sample Angular application with Clarity is to use the Clarity Seed.

hall-of-fame - :trophy: Show some love to your contributors! A widget for your repo README

  •    Python

Hall-of-fame helps you show some love to your contributors. It automatically highlights your new, trending, and top contributors, and updates every hour. You can put this widget anywhere inside your README, e.g. to "Contributing" section. No maintenance is required. Every hour, Hall-of-fame looks into recent commits of your repo using GitHub API. It then selects three categories of contributors: new (those who made their first commit to your repo in the last 7 days), trending (those with most commits in the last 7 days), and top (those with most commits of all time). It then selects up to three new contributors, up to 4 trending contributors, and if total is less than 7, it fill up the remaining spots with top contributors.

all-contributors - ✨ Recognize all contributors, not just the ones who push code ✨

  •    HTML

This is a specification for recognizing contributors to an open source project in a way that rewards each and every contribution, not just code. Use the project README (or another prominent public documentation page in the project) to recognize the contributions of members of the project community.

Mailsuite (Postfix, Courier-IMAP, LDAP)

  •    

Mailsuite decribes HOWTO install, configure and run Postfix, Courier-IMAP, OpenLDAP and a Webmail application on a *NIX (Linux) system. Mailsuite provides knowledge HOWTO install from SOURCE, from RPM (RedHat) and from DEB (Debian).

javascript-design-patterns-for-humans - An ultra-simplified explanation of design patterns implemented in javascript

  •    

Design patterns are solutions to recurring problems guidelines on how to tackle certain problems. They are not classes, packages or libraries that you can plug into your application and wait for the magic to happen. These are, rather, guidelines on how to tackle certain problems in certain situations. In software engineering, a software design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. It is not a finished design that can be transformed directly into source or machine code. It is a description or template for how to solve a problem that can be used in many different situations.






We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.